mdm100 master data management

SAP AG 2006

0'0��

��

© SAP AG 2007

0'0��0DVWHU�'DWD 0DQDJHPHQW

�

� NetWeaver 2004s � 2006/Q2 � Materialnumber: 50082547

SAP AG 2006

&RS\ULJKW

&RS\ULJKW�� 6$3�$*��$OO�ULJKWV�UHVHUYHG�1R�SDUW�RI�WKLV�SXEOLFDWLRQ�PD\�EH�UHSURGXFHG�RU�WUDQVPLWWHG�LQ�DQ\�IRUP�RU�IRU�DQ\�SXUSRVH�ZLWKRXW�WKH�H[SUHVV�SHUPLVVLRQ�RI�6$3�$*��7KH�LQIRUPDWLRQ�FRQWDLQHG�KHUHLQ�PD\�EH�FKDQJHG�ZLWKRXW�SULRU�QRWLFH�

�

� Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

� Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

� IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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

� Oracle is a registered trademark of Oracle Corporation. � UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. � Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are

trademarks or registered trademarks of Citrix Systems, Inc. � HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide

Web Consortium, Massachusetts Institute of Technology. � Java is a registered trademark of Sun Microsystems, Inc. � JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology

invented and implemented by Netscape. � MaxDB is a trademark of MySQL AB, Sweden. � SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and

services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

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

� This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

� SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

� SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

� The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

SAP AG 2007

5HFRPPHQGHG .QRZOHGJH�� 1:��7HFKQRORJ\�6ROXWLRQV�

3RZHUHG�E\�6$3�1HW:HDYHU��H�OHDUQLQJ�

&RXUVH 3UHUHTXLVLWHV

�

SAP AG 2006

7KLV�FRXUVH�LV�LQWHQGHG�IRU�WKH�IROORZLQJ�DXGLHQFHV�� 3URMHFW�WHDP�PHPEHU�DQG�6ROXWLRQ�&RQVXOWDQWV�

QHHGLQJ�NQRZOHGJH�RI�0DVWHU�'DWD�0DQDJHPHQW

'XUDWLRQ�� GD\V

7DUJHW�$XGLHQFH

�

8VHU�QRWHV�� These training materials are QRW�D�WHDFK�\RXUVHOI�SURJUDP. They complement the explanations

provided by your course instructor. Space is provided on each page for you to note down additional information.

� There may not be sufficient time during the course to complete all the exercises. The exercises provide additional examples that are covered during the course. You can also work through these examples in your own time to increase your understanding of the topics.

SAP AG 2006

&RXUVH�*RDOV

7KLV�FRXUVH�ZLOO�SUHSDUH�\RX�WR�� $WWDLQ�NQRZOHGJH�RI�WKH�IHDWXUHV�DQG�RSWLRQV�WR�

VXSSRUW�D�FXVWRPHU�LPSOHPHQWDWLRQ�HPSOR\LQJ�WKH�FXUUHQW�YHUVLRQ�RI�0'0

�

SAP AG 2006

&RXUVH�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�FRXUVH��\RX�ZLOO�EH�DEOH�WR�� 'HVFULEH�WKH�IHDWXUHV�DQG�RSWLRQV�RI�0'0�LQ�WKH�

LPSOHPHQWDWLRQ�RI�D�YDULHW\�RI�,7�RU�%XVLQHVV�6FHQDULRV

�

SAP AG 2006

&RXUVH�2YHUYLHZ�'LDJUDP��

8QLW�� 0'0�2YHUYLHZ0'0�,QWURGXFWLRQ0'0�'DWD�0DQDJHU

8QLW�� 'DWD�0RGHOLQJ

,PSRUW�0DQDJHU4XDOLILHG 7DEOHV+LHUDUFKLHV

7D[RQRP\

8QLW�� $GYDQFHG�0'0�)HDWXUHV

0DWFKLQJ�0RGH:RUNIORZ5HODWLRQVKLSV

6\QGLFDWRU0'0�$XWRPDWLRQ0XOWLOLQJXDO�6XSSRUW

([SUHVVLRQV

,PSRUW�0DQDJHU�$GYDQFHG

&RQVROH

8QLW�� 2XWSXWV

�

SAP AG 2006

&RXUVH�2YHUYLHZ�'LDJUDP��

8QLW�� ,QWHJUDWLRQ�6FHQDULRV�ZLWKLQ6$3�1HW:HDYHU3RUWDO�,QWHJUDWLRQ2SHQ�&DWDORJ�,QWHJUDWLRQ;,�,QWHJUDWLRQ(&&�&RPPXQLFDWLRQ%,�,QWHJUDWLRQ

&XVWRPHU�'DWD�,QWHJUDWLRQ

0DVWHU�'DWD +DUPRQL]DWLRQ5LFK�3URGXFW�&RQWHQW�0DQDJHPHQW*OREDO�'DWD�6\QFKURQL]DWLRQ

8QLW�� ,7��%XVLQHVV�6FHQDULRV6HFXULW\�DQG�3HUPLVVLRQV

3HUIRUPDQFH

'LUHFWRU\�6HUYHU�,QWHJUDWLRQ

8QLW�� /DQGVFDSH

&RPSXWLQJ�&HQWHU�0DQDJHPHQW�6\VWHP�

�

SAP AG 2006

0DLQ�%XVLQHVV�6FHQDULR

� <RXU�FRPSDQ\�KDV�D�KHWHURJHQHRXV�,7�ODQGVFDSH�ZLWK�VHYHUDO�V\VWHPV�HDFK�FRQWDLQLQJ�WKH�PDVWHU�GDWD�REMHFWV�RI�PDWHULDOV��FXVWRPHUV��YHQGRUV��DQG�HPSOR\HHV��:KLOH�FRPPXQLFDWLQJ�PDWHULDO�LQIRUPDWLRQ�WR�YHQGRUV�DQG�FXVWRPHUV��FRQIXVLRQ�KDV�HQVXHG�ZKHUH�GLVSDUDWH�DQG�RU�FRQWUDGLFWRU\�GDWD�FRQFHUQLQJ�WKH�VDPH�PDWHULDOV�KDYH�EHHQ�VHQW�QXPHURXV�WLPHV�WR�WKH�VDPH�YHQGRU�DQG�FXVWRPHU��%HFDXVH�RI�WKLV��LW�KDV�EHHQ�YHU\�GLIILFXOW�WR�HVWDEOLVK�D�FHQWUDOL]HG�ZHE�FDWDORJ�RI�SURGXFWV�VHDUFKDEOH�E\�FXVWRPHUV�

� )XUWKHU��SRRU�GDWD�V\QFKURQL]DWLRQ�EHWZHHQ�\RXU�FRPSDQ\¶V�V\VWHPV�KDV�UHVXOWHG�LQ�VORZ�DQG�LQDFFXUDWH�SDUWQHU�DQG�VXSSOLHU�FRPPXQLFDWLRQV��<RXU�FRPSDQ\�KDV�GHFLGHG�WKDW�LW�QHHGV�D�0DVWHU�'DWD�0DQDJHPHQW�VROXWLRQ�WR�DOOHYLDWH�WKHVH�SUREOHPV�DQG�ZRXOG�OLNH�WR�XQGHUVWDQG�WKH�FDSDELOLWLHV�RI�6$3�1HW:HDYHU�0'0��

�

© SAP AG MDM100 1-1

SAP AG 2006

8QLW��0'0�2YHUYLHZ��0'0�,QWURGXFWLRQ




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�


SAP AG 2006

&RQWHQWV�� 'LVFXVVLRQ�RI�ZKDW�LV�PDVWHU�GDWD� ,QWURGXFWLRQ�WR�6$3�1HW:HDYHU�0'0� ,QWURGXFWLRQ�WR�WKH�,7�DQG�%XVLQHVV�6FHQDULRV�ZKLFK�XWLO]H

0'0

6$3�1HW:HDYHU�0'0�,QWURGXFWLRQ

�


SAP AG 2006

6$3�1HW:HDYHU�0'0�,QWURGXFWLRQ��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�QHHG�IRU�0DVWHU�'DWD�0DQDJHPHQW� $SSUHFLDWH�WKH�YDOXH�RI�6$3�0'0� ,QWURGXFWLRQ�RI�WKH�,7�DQG�%XVLQHVV�6FHQDULRV� 6HH�KRZ�0'0�ILWV�LQWR�WKH�1HW:HDYHU�VWDFN

�


SAP AG 2006

6$3�1HW:HDYHU�0'0�,QWURGXFWLRQ��%XVLQHVV�6FHQDULR

� <RXU�FRPSDQ\�ZRXOG�OLNH�WR�FRPSDUH�WKH�XVH�RI�6$3�1HW:HDYHU�0'0�WR�WKH�XVH�RI�P\6$3 (53�DV�D�PDVWHU�GDWD�UHSRVLWRU\��

�


SAP AG 2006

0DVWHU�'DWD 0DQDJHPHQW�2YHUYLHZ,7�DQG�%XVLQHVV�6FHQDULRV$UFKLWHFWXUH.H\V�WR�6XFFHVVIXO�3URMHFWV

0DVWHU�'DWD�0DQDJHPHQW�2YHUYLHZ

�


SAP AG 2006

,QFRQVLVWHQW�9LHZ�RI�%XVLQHVV�'DWD�

� 0DVWHU�GDWD�LV�JHQHUDWHG�DQG�WUDSSHG�LQ�VLORV <285�%86,1(66

�� ! �"$#&% '(&)!(��!�* �� ,+�-�.!/ �

021�*� ��3� * �& �� 4��5�5 #�6�7 8 $� �!�&* �� ":9;� "$#�<9* �� =+�>2/!.�- �

(YHU\�GHSDUWPHQW�KDV�GLIIHUHQW�LQIRUPDWLRQ�

�

� Your business today: y Departmental silos create and perpetuate their own versions of master data.


SAP AG 2006

3HUYDVLYH�&KDOOHQJHV�RI�0DVWHU�'DWD�0DQDJHPHQW

(QWHUSULVH�,QIRUPDWLRQ�0DQDJHPHQW�3UREOHP

-3�0RUJDQ�&KDVH³:LWKRXW�0DVWHU�'DWD�0DQDJHPHQW��0'0��FDSDELOLW\��ZH�EHOLHYH�LW�ZLOO�EH�FKDOOHQJLQJ�IRU�DQ\�FRPSDQ\�WR�PRYH�WR�D�VHUYLFHV�RULHQWHG�DUFKLWHFWXUH�´

3HUYDVLYH�&KDOOHQJHV�RI�0DVWHU�'DWD�0DQDJHPHQW

3URGXFW�'DWD�3UREOHP

3URGXFW�WR�0DUNHW? Failure to capitalize on

market opportunity with NPI? Lacks real-time collaboration with front office

6XSSOLHU�'DWD�3UREOHP

2SWLPL]H�3URFXUHPHQW? Lack of visibility into suppliers

and products? High spend costs

&(2��&)2��&,2? Create an IT framework that supports innovation and growth with less budget? Effectively manage all resources, including human capital, in a dynamic world of

mergers and acquisitions

&XVWRPHU�'DWD�3UREOHP

6DOHV�DQG�0DUNHWLQJ�(IIHFWLYHQHVV? Lacks one view of customers across all channels? Sub-optimal views impact customer-facing transactions

�

� Inability to reduce procurement spend costs y Inability to understand from whom and which products I buy worldwide y Same suppliers and products classified in different categories, preventing easy comparison

� Lack of customer insight to target each account with the right offer y Impacts the ability to create longer, profitable customer relationships y Lack of coherent data prevents anticipation of changing customer needs

� Inability to collaborate by sharing information with key constituents y Data silos prevent sharing information with customers, partners, suppliers, and so on y No mechanism or process to share the same information internally and externally

� Inability to modify or design new business processes y Rigid connections to data sources y Impedes innovation and differentiation

� High integration costs with other key processes y Heterogeneous landscape – lack of common infrastructure or technology platform y Multiple point-to-point solutions with new islands of information


SAP AG 2006

7KH�0DVWHU�'DWD�&KDOOHQJH

$�SUREOHP�H[SHULHQFH�E\�HYHU\�FRPSDQ\�

6\VWHP�$ 6\VWHP�%

,V�WKLV�WKH�VDPH�SURGXFW�UHSUHVHQWHG�LQ�WZR�GLIIHUHQW�ZD\V"

"@�A�A�BDCFE�G�HIJH,ALKNM OPG�B=E<Q�AJH RSJE�T�U�HWV X$BWV AZY

[ G$\=E�BDR^]ZALA�B_a`3b$cLd

� 0DVWHU�GDWD�GHVFULEHV�NH\�DUHDV�RI�\RXU�EXVLQHVVe &XVWRPHUV �QDPH��DGGUHVVHV��SKRQH�QXPEHU�e 3URGXFWV �SURGXFW�DWWULEXWHV��OLVW�SULFH�e 6XSSOLHUV �SDUHQW�HQWLW\��DGGUHVV��SDUWV�RIIHUHG�e (PSOR\HHV �,'��QDPH��WLWOH��DGGUHVV��RUJDQL]DWLRQDO�XQLW�

� 0DVWHU�GDWD�LV�VWRUHG�LQ�PXOWLSOH��GLVFRQQHFWHG�V\VWHPV�GDWDEDVHV� 8QPDQDJHG�PDVWHU�GDWD�LV�QRWRULRXVO\�LQDFFXUDWH��IXOO�RI�GLVFUHSDQFLHV��

LQFRPSOHWH��DQG�OHDGV�WR�SRRU�EXVLQHVV�GHFLVLRQV

Ogf A2Bih�V Y<QIZH�ALKjM O:G�B,E�Q�AZH RSZE�T�U�HWV X$BkV AZY

[ G�\=E$B,Rl]�ALA�B]nmZo=b�d

�

� Inability to reduce procurement spend costs y Inability to understand from whom and which products I buy worldwide y Same suppliers and products classified in different categories, preventing easy comparison

� Lack of customer insight to target each account with the right offer y Impacts the ability to create longer, profitable customer relationships y Lack of coherent data prevents anticipation of changing customer needs

� Inability to collaborate by sharing information with key constituents y Data silos prevent sharing information with customers, partners, suppliers, and so on y No mechanism or process to share the same information internally and externally

� Inability to modify or design new business processes y Rigid connections to data sources y Impedes innovation and differentiation

� High integration costs with other key processes y Heterogeneous landscape – lack of common infrastructure or technology platform y Multiple point-to-point solutions with new islands of information


SAP AG 2006

,QFRQVLVWHQW�9LHZ�RI�3DUWQHU�'DWD�

* <"�p� ��3+&q�� "�r��&��"$��:�� !�P $Dp�s�t

<285�9$/8(�&+$,17UDGLQJ�SDUWQHUV�SHUSHWXDWH�WKHLU�RZQ�YLHZV�

� 0DVWHU�GDWD�LV�JHQHUDWHG�DQG�WUDSSHG�LQ�VLORV

� 7UDGLQJ�SDUWQHU�GDWD�LQWURGXFHV�\HW�DQRWKHU�YHUVLRQ�RI�GDWD

0<1�*� �� * �� 4�&5&5 #�6 7 8 �� !�!* �� ":9L� "$#�<9* �� =+�>2/�.!- � ��

� ��P 2�� !��&�n�� <D �� !�! �"$#&% '(�)&(��!�* �� =+!-!.�/ �

1�u* �� =+ �&5 /�.v�0<��w<xP19;>�� -!6

'�"$ 3� 4! � �&4v�0��w2xP1y�z�{3� . (

�

� Your trading partners: y Trading partners perpetuate their own versions of master data. How do you share data?


SAP AG 2006

6$3�1HW:HDYHU�0'0

6$3�1HW:HDYHU�0'0One master data solution for all business processes

|}_a~J_g�F��Og� [J�Z� |N�Jm

��h<A�V Tl��RU��T�B�A;��E�H �

��Jmn� @$��_P�P_g� �2_g]��

S�A^�2h�G$�2E�Bkh�EH�V QJh�B XLH,A�KZ�<U$B �

� S:�J~ � � @$� [ ��IJIJ�L� �Jm

��h<A�V Tj��Rl�2E$T<B�2E�Y2K�AZH �

� _gd�� mnS:�Zm

��h�V ULh E2�^X�f A<R2E2ET�h2AJ��f KjCaE�G�T�T;V QJYFB�AL�

2QH�VROXWLRQ�IRU�$//�PDVWHU�GDWD�LQ�\RXU�LQGXVWU\�VSHFLILF�SURFHVV

�


SAP AG 2006

6$3�0'0�8VHV

� )DVW�VHDUFKLQJ RI�LQIRUPDWLRQ� )RUPDOL]LQJ�DQG�FRQWUROOLQJ PDVWHU�GDWD�PDQDJHPHQW�SURFHVVHV� ,PSURYLQJ�TXDOLW\�RI�UHSRUWLQJ IURP�PXOWLSOH�VRXUFHV� )LQGLQJ�GXSOLFDWH LQIRUPDWLRQ� 0HUJHUV�DQG�PLJUDWLRQV� 0DVV�RSHUDWLRQV RQ�GDWD� ([WHQGLQJ�GDWD�DFFHVVLELOLW\� ,PSURYLQJ�DQG�FRQWUROOLQJ�GDWD�TXDOLW\ OHYHOV� $QVZHULQJ�TXHVWLRQV WKDW�ZHUH�QHYHU�DVNHG

�

� The MDM system is much more than a simple database application. Rather, it is an integrated system for master data management that uses a database management system (DBMS), but completely bypasses relational DB functions for almost all searching, sorting, and retrieving of information.


SAP AG 2006

6$3�1HW:HDYHU�0'0�KDV�«

81,48(�)($785(6

0'0

3UHGHILQHG�DQG KLJKO\�IOH[LEOH�REMHFW�PRGHOV? �a�k�Z��P�;�&��;��g 2¡W�Z¢�£�¤¥�n��P¦ §¨�k��g¢P©�§Z£i�n¤��&ªZ«P��:��©Z¢;£kªL�J¤¬«:¦ �:J�L�¯®P�P�°§P©n«:«:¦�� ? ±a§J��k§¯¢J®P�°�P��!��J��£!²;�P�D�g�Z³´�°¤��n��P¦�³¯� £!²�®¥²:� µg²P¦ °¢J��J�&� µg©:�k®P P¦ �¶§Z¢:²J�J¤¥®? ·�� ¢�²��k�:«Z�:§:� £k��i�²;®:�Z��¦ �;§¸ J��£!²¨§:� ¤¹«:¦ ��®P�Z�¸¢;�:¤º«n¦D� ¢L®J£W�J�¸��®L£k®�£�®;»��g�J�n¤°´®��

²:� �P�k®P��¢:²P� ��§

&RQWHQW�H[WUDFWLRQ�DQG�PDQDJHPHQW? ¼ ¤º«Z�n�k£n®:��½�k®L£&� ��;®:¦�� ¾��°��®L£k®��&�k�n¤¿®P�Z�§Z��©:�i¢;�? À��:¤º«P�i�:²;�P�Z§:� ÁJ�¯¢J�g�;£W�:�;£:®:�Z�º�D¤´®Jµ:�´¤´®P�J®Zµ��Z¤��:�;£? Âa¦ �J¢L£��:� ¢¯®P��½«P�!�,�;£g«n©: P¦=� §P²:�,�Jµ

8QEHDWDEOH�SHUIRUPDQFH��VFDODELOLW\��DQG�IOH[LELOLW\? ÃÄ®P�J��¦ ��§¯§n� ¤½«:¦ �¨®��¢Z�n¤½«:¦ ��»��P®L£W®�§J�Z®Z¤½¦ �L§J§n¦ ? ÅÄ¢L®:¦ �L§�£k�¥¤¹�D¦�¦D� ��;§��J�}�k��¢;��i�P§? Ã�� µ�²¥«J�P�W�i��¤�®��P¢L�´«Z®P�k®Z¤��;£!�!� ¢�§Z�J®P�i¢P²

(DV\�WR�LQVWDOO�DQG�GHSOR\? Â�®L§J��;§;£k®P¦,¦ ®L£!� ��¯®P��P�n«P¦ �P�¤´�n�L£P³�� £�²��,�¶³��;�:Æ�§? Â�®L§Z�¶£i�½©J§J�ZªJ¤½��:� ¤�®n¦2£&�k®P�,�P��Zµ½�i�JÇ�©:�D�i��? È°©P¦ £&� �i©�§��P��¢;��¦�¦ ®: ��i®L£!� ��

�


SAP AG 2006

&RQVROLGDWLRQEnsure consistent master data across systems

$FWLYHO\�0DQDJLQJ�0DVWHU�'DWD

+DUPRQL]DWLRQCleanse and distribute across entire landscape

&HQWUDO�0DQDJHPHQWCentrally create consistent master data from the start

SZG$B�GÉ ��G�f V BDR

� V ��E

� �iÊ * "$s3p3��'��p��

0DVWHU�'DWD�0DQDJHPHQWË=Ì°ÍZÎkÏ;ÐJÑ¯ÒPÓJÔ&Ó´Õ:ÖLÓ�×=Ø Ô�Ù�Ø�Ú¯Û�Ô�Ñ�ÍLÛ

u�Ü 9x p� 4!"<p3 ��

��"$��4�"�� s3�!�� "$�Ý ��D�n"$�� Þi�! � "3�

�� u:w�uß,à á àâWã à ä å á æ

çDå èié

ê¥ØDÔ�ë;Ï�ÖLÔÄìZÏPÚLÛLÏ�×=Ø ÒJÓ�Ô�Ø Ï�Ú�íÒJÏ�Ø=ÚLî�ïJÖ;ÛJØ,ÚLÑZÛ�Û¯ØDÛ

Ñ;ðPÍ;ÑPÚ;ÛJØ ÐJÑ

$XWRPDWLFDOO\�DQG�FRQWLQXRXVO\�LPSURYH�GDWD�TXDOLW\

�

� Business events continuously impact data quality.


SAP AG 2006

,7�DQG�%XVLQHVV�6FHQDULRV


�


SAP AG 2006

,7�6FHQDULRV�ZLWK�6$3�0'0�

6XSSRUW�RI�FRUH�,7�VFHQDULRV�DQG�FDSDELOLWLHV� 0DVWHU�'DWD�&RQVROLGDWLRQ

ñ &OHDQVLQJ�DQG�GH�GXSOLFDWLRQñ 'DWD�QRUPDOL]DWLRQ��LQFOXGLQJ�FDWHJRUL]DWLRQ�DQG�WD[RQRP\�

PDQDJHPHQWñ 1HZ�LQWHUDFWLYH�FRQVROLGDWLRQ�FDSDELOLWLHV

� 0DVWHU�'DWD�+DUPRQL]DWLRQñ $XWRPDWHG�V\QFKURQL]DWLRQ�RI�JOREDOO\�UHOHYDQW�PDVWHU�GDWD�

LQIRUPDWLRQñ 1HZ�LQWHUDFWLYH�GLVWULEXWLRQ�FDSDELOLWLHV

� &HQWUDO�0DVWHU�'DWD�0DQDJHPHQWñ &HQWUDO�FUHDWLRQ�DQG�PDLQWHQDQFH�RI�GDWDñ 2QJRLQJ�PDVWHU�GDWD�TXDOLW\

�


SAP AG 2006

&RUH�%XVLQHVV�6FHQDULRV�ZLWK�6$3�0'0

6XSSRUW�RI�&RUH�%XVLQHVV�VFHQDULRV�DQG�FDSDELOLWLHV� 5LFK�3URGXFW�&RQWHQW�0DQDJHPHQW��53&0�

ñ 3RZHUIXO�FDSDELOLWLHV�WR�ORDG��DJJUHJDWH��DQG�VHDUFK�RQ�SDUDPHWULF�SURGXFW�GDWD�

ñ ,QWHOOLJHQW�LPDJH�PDQDJHPHQW�DQG�:HE�SULQW�SXEOLVKLQJ� *OREDO�'DWD�6\QFKURQL]DWLRQ��*'6�

ñ &RQVLVWHQW�WUDGH�LWHP�GDWD�H[FKDQJH�ZLWK�UHWDLOHUV�YLD�GDWD�KXEV�IRU�H[DPSOH��6<1&�

� &XVWRPHU�'DWD�,QWHJUDWLRQ��&',�ñ &RQVROLGDWLRQ�DQG�PDQDJHPHQW�RI�FXVWRPHU�GDWD�IURP�DOO�DYDLODEOH

VRXUFHVñ &XVWRPHU�GDWD�PDQDJHPHQW�FDSDELOLWLHV�VXFK�DV�PDWFKLQJ��

VWDQGDUGL]DWLRQ��DQG�VXUYLYRUVKLS

�


SAP AG 2006

6$3�0'0��.H\�&RQFHSWV�DW�D�*ODQFH

'HOLYHUV�D�VLQJOH�YHUVLRQ�RI�WKH�WUXWK��LQWUD�DQG�LQWHU�HQWHUSULVH

ò�ó ô�õ$ö�ó�÷;ö�ø�öù�ú$û$ü�ý<þ,ô�û�ÿ ��ö�ø=ÿ ô�û

,QWUD�(QWHUSULVH

Å��l��a�;£�� ;®LÁZ�:��iÈ�È��

�^�J®P¦ ;£!� ¢�§��J��«P¦ �´�a�i�n��©J¢;£�� Á:� £k

Inter-Enterprise

�:�:®L�� §¸·a�L®:¦D� £W°��:�k®Zµn¤��P�J£W�J�º¼ ÅÄL§;£i�Z¤°§

`��|FG$T<B=E�HZSZG$B,GOnAJY�T2AZf V K�G�BWV AZY

~PAZY�o [ _ÄI [ _ÄI �2E<Q�G$U$R

� ÿ ü�ý��Lþ,ô��$ü�ø�;ô�û3ø��$û�ø� ö�û$ö�� !"�<û�ø�#�%$�ø�ô&!'�$þ÷Lö�ø�ö� ö�û$ö%��!'�$û3ø

��þ=ÿ û�ø (*)�û<ó ÿ û��Jö�ø�ö�ó ô � $

b��<|ÄG�T�B=E�HZSZG�B=G+ZG�H=�NAZY�V ,�G$BkV AJY%-O:E�Y$BkH�G�f�|�QL��B

À��n¤½«��§n� £k�.��«n«:¦D� ¢;®L£&� �}��§

/�0 �a�i�:¢;�;§L§¥ÂÄ�;®P n¦ ��¤´�:�;£

0 �� *13 � 4�� <�� 23� �!�!41 �31�"�4�� "� t

* � �& 4 "��* "3��&4!4P��"��1�"$�� 4

�

� Master data consolidation benefits: SAP MDM ensures data integrity with master data consolidation and sets the stage for easy reuse via distribution or via business processes that directly leverage consolidated data.

� Master data harmonization benefits: SAP MDM ensures that as data changes in one application, other business applications that depend on that data are updated with a consistent view of key data as it changes in real time. This enables decision making based on accurate data.

� Central master data management benefits: With SAP MDM, a central comprehensive repository can be created with enriched content that can be used as the single source for all enterprise master data, both inter-enterprise and intra-enterprise.


SAP AG 2006

3XEOLVK

%HQHILWV��5 &RPSOH[�SURGXFW�DQG�

UHODWLRQVKLS�PDQDJHPHQW5 3ULQW�:HE�SXEOLVKLQJ��LQFOXGLQJ�

OD\RXW�DQG�SURGXFWLRQ

GEAR

Parts

687:9<;>=�? ËA@

([DPSOH� Product information is consolidated and enriched and published internally or externally

5LFK�3URGXFW�&RQWHQW�0DQDJHPHQW��53&0�

B 6DCFEHGParts

GEAR

Gears

I'J =KCHG

SPIDER GEAR

2QH�YLHZ�RI�SURGXFW�LQIRUPDWLRQ��DQ\WLPH��DQ\ZKHUH

�

� Using rich product-content management, companies can manage and exchange product data locally and globally y Manage internal content y Search electronic catalogs y Print customized catalogs y Syndicate product catalog content via multiple channels (OCI, Web, print) y Present role-based interfaces through a portal

� Key capabilities y High-performing load, aggregation and search of product data y Multidimensional search y Flexible taxonomy y Intelligent imaging and Web/print publishing y Application programming interfaces (APIs) for seamless, multiplatform integration y Scalability (up to millions of products)


SAP AG 2006

L%MAN M#OQPRPTS

*OREDO�'DWD�6\QFKURQL]DWLRQ��*'6�

U 5HGXFH�VXSSO\�FKDLQ�FRVWV�ZLWK�D�FRPSUHKHQVLYH�VROXWLRQ�IRU�FRQVXPHU�SURGXFW�FRPSDQLHV

U &HUWLILHG�WR�SXEOLVK�HQULFKHG�SURGXFW�GDWD�WR��6<1&�GDWD�SRROV�

U 8QLGLUHFWLRQDO�FRPPXQLFDWLRQ�ZLWK�6$3�5��

L%MAN M�OQPRPRS

V S PRWRMXSY%Z\[3] ^_N ` a

bAced\fegXhXiTd\j kAlAmAj iRd

/HYHUDJH�PDVWHU�GDWD�FRQVLVWHQF\�DFURVV�WKH�VXSSO\�FKDLQ

�

� Using global data synchronization, companies can manage and exchange product data locally and globally: y Reduce error-processing costs resulting from inconsistent product data y Establish channels for exchanging standardized information with data pool (for example,

1Sync) for further publication to trading partner y Implement a quick but complete solution for complying with trading-partner requirements y Integrate with mySAP ERP seamlessly and permanently y Achieve a lower total cost of ownership, since global data synchronization (GDS) is based on

your existing landscape


SAP AG 2006

U ([WHQVLYH�PDWFKLQJ�IUDPHZRUN

U 3URYLGHV�:HE�VHUYLFHV�IRU�FXVWRPHU�GDWD�DFFHVV�

U 6$3�DQG�QRQ�6$3�LQWHJUDWLRQ

$QDO\VLV

n2G�Y�E [ ��V BWhc<cL`pol~<� [ BiHK�Ogh�V U�G2Q�A>q2� �r�s�r2`<`

&XVWRPHU�'DWD�,QWHJUDWLRQ��&',�

n2G�Y<EjI�E�B,E�HDT`%t t�q�u v w [ BkH�E�E$BI�G�f AN_}f B�A8q<O�_t$c�u s�c

n<G�Y$E�I�E�B,E�HDT[ ��V BWh

c�cL`�oN~PA;H�Bkh [ B_�Ogh�V U$G2QLA8q2� �r s�r�`�s

2QH�YLHZ�RI�FXVWRPHU�LQIRUPDWLRQ��DQ\WLPH��DQ\ZKHUH

�

� CDI ensures that all relevant departments in the company have constant access to the most up-to-date and complete view of customer data available.

� CDI is an essential extension to Customer Relationship Management (CRM)


SAP AG 2006

U 8QGHUVWDQG�\RXU�PRVW�SURILWDEOH�SURGXFWV��EHVW�FXVWRPHUV��DQG�FKHDSHVW��PRVW�UHOLDEOH�YHQGRUV

U *DLQ�LQVLJKWV�E\�LQWHJUDWLQJ�WUDQVDFWLRQDO�GDWD�IURP�KHWHURJHQHRXV�V\VWHPV�ZLWK�PDVWHU�GDWD�IRU�DQDO\VLV

,PSURYHG�%XVLQHVV�,QWHOOLJHQFH

+

� mJ_g~ [ _�O � � � ~;_}�S;_ � _ =|a_ [J� �Jm

S;_ � _

]:� [ � ~�� [J[ � ~ [ � �x+ �'HOLYHU�XQLTXH�LQVLJKWV�ZLWK�DQ�LQWHJUDWHG�SODWIRUP

�


SAP AG 2006

0DVWHU�'DWD�3DFNDJHV0DVWHU�GDWD�LV�NH\�QRQ�WUDQVDFWLRQDO�LQIRUPDWLRQ�DERXW�\RXU�EXVLQHVV�

y $UWLFOHVz �}��©P¢�£:®;£W£&�!�� :©;£W�;§�ªL�� ¤¥�P�;§n� ��Z§�ª

³^�P� µ}²;£z À��¦ ��ªL§:²J®:«;�Zª;�L£k¢ 0

y %XVLQHVV�3DUWQHUVz Å�©:«:«�¦=� �P�a�Z®Z¤��Zª�«;®P�k�:�;£n�n�L£!� £kZª

®J�P��k�;§;§z �}²Z��Z�´�n©Z¤º ;�P��§ZªL�P£&²J�P��§L£k®�£�� ¢

�D�;�k��i¤¥®L£&� �g�y &XVWRPHUV

z ÀN©;§J£i�n¤´�P�a�J®Z¤¥�JªL®J�n��k�L§J§Z��§z �}²Z��Z�´�n©Z¤º ;�P��§ZªL�P£&²J�P��§L£k®�£�� ¢

�D�;�k��i¤¥®L£&� �g�y (PSOR\HHV

z Â�¤º«P¦ ��;�J��¼��ªJ�J®�¤´��ª�£!� £&¦ �ZªL®Z�n��k�L§L§z { �iµP®P�n� ¾�®L£&� ��Z®P¦J©n�P� £iªL�L£k¢ 0

y 0DWHULDOVz È^®;£��:�&� ®:¦�®;£�£!�!�D n©;£W�;§�ª;�n�D¤��P�;§�� J§Zª

³^�:� µg²;£z Å}®P¦ �L§´®��Z�º¦ �P¢;®;£�� g�¯�:®�£k®

y 3URGXFWVz �}��P��©�¢�£n®;£�£!�!�D n©;£W�;§�ª;�n�D¤��P�;§�� J§Zª

³^�:� µg²;£z À��¦ ��iªL§:²;®n«;�Zª;�L£k¢ 0

y 6XSSOLHUVz Å�©:«P«:¦,� �P�a�Z®J¤¥�Jª�«J®P�k�n�;£P�n�;£&� £W�ª

®;�:��k�;§;§z �}²Z��Z��:©�¤½ J�:�k§�ªL�P£&²J��§;£W®L£�� ¢

�D�;�k��&¤�®L£&� �g�

�


SAP AG 2006

$UFKLWHFWXUH


�


SAP AG 2006

6$3�0'0� 6WUDWHJLF�%DFNERQH�RI�(QWHUSULVH�62$

| � �k�¯À�J¢�¦ �¥È�®P�J®JµP�Z¤��n�L£

}p~Q��R�T�� Q�T� ~3�}p~T��R�T�� T�Q� ~3� ��%� � ��

��%� � ��%� � � ��%� ��%� �

Å��l��}�L£�� L®LÁZ�P�Å��l��Ä�L£�� J®LÁZ�P�

��J®:¦ L£�� ¢�§��;��«:¦ �´�a�i�n��©Z¢L£&� Á�� £i

À��:¤º«Z��§:� £i�.�l«n«:¦D� ¢;®L£&� �g�;§

�� T� � � � �� %�Q~T�T�<�8��Q� �3~Q�3� �

�>��#� �* ¡��¢�£��8¤:¥§¦<¥

)RXQGDWLRQ�IRU�(QWHUSULVH�62$U 0'0�GHOLYHUV�DQ�HQWHUSULVH�

LQIRUPDWLRQ�IRXQGDWLRQ�IRU�(QWHUSULVH�VHUYLFH�RULHQWDWHG�DUFKLWHFWXUH

U 0'0�HQDEOHV�IOH[LELOLW\�DQG�GDWD�UHXVDELOLW\�WKURXJK�ORRVHO\�FRXSOHG�EXVLQHVV�SURFHVVHV�WKDW�FDQ�DFFHVV�GDWD�HDVLO\

U %XVLQHVV�SURFHVVHV�FDQ�OHYHUDJH�0'0�WR�DXWRPDWLFDOO\�JHQHUDWH�GDWD�PRGHOV

U (QWHUSULVH�:HE�VHUYLFHV�FDQ�DFFHVV�6$3�0'0�VHDPOHVVO\�

U 6$3�$QDO\WLFV�OHYHUDJHV�0'0�DQG�6$3�1HW:HDYHU�%XVLQHVV�,QWHOOLJHQFH

¨��3� ~ � � � � �R~� ~ � ©�� T~R�ª�~3��

�


SAP AG 2006

)LUVW�6WHSV�WR�(QWHUSULVH�62$

8QLI\�GDWD8QLI\�FXVWRPHU��SURGXFW��HPSOR\HH��VXSSOLHU��DQG�XVHU�GHILQHG�GDWD�ZLWK�RQH�VROXWLRQ�WR�EXLOG�UREXVW�EXVLQHVV�SURFHVVHV

,QGXVWU\�LQVLJKWV6XSSRUWV��6<1&��FRQILJXUDEOH�IRU�RWKHU�LQGXVWULHV

(DV\�GHSOR\PHQW3UH�EXLOW�GDWD�PRGHOV��PDSSLQJV��DQG�L9LHZV

$FFHOHUDWH�QHZ�EXVLQHVV�SURFHVVHV�ZLWK�DFFXUDWH�PDVWHU�GDWD

�


SAP AG 2006

0'0�$UFKLWHFWXUH��0DMRU�%XLOGLQJ�%ORFN

¼D¤½«Z��k£PÅF�P�kÁ;�P�« Parsing« Structural Mapping« Value Mapping« Record Matching« Key Mapping

²P��°Àl¦D� �:�;£« Search / View« Data Maintenance« OCI

8VHU�,QWHUIDFH·�� ¢�²¯Àl¦�� P�J£

« Console« Data Manager« Import Manager

È�®�§;£W�P�'a®L£i®�Åa��kÁZ�P�« Core Services« Memory Cache« Database Abstraction« Repository Management

Åa��Z��D¢L®L£&� ��ÅÄ�P�WÁJ�:�« Extraction« Structural Mapping« Value Mapping« Number Assignment« Key Mapping

Å��l��Ä�L£�� ;®;ÁZ�P�<¬N¼ Å��l��Ä�L£�� ;®;ÁZ�P�H��«n«P¦�� ¢;®;£�� Åa�P�kÁJ�P�« Inbound Processing « Outbound Processing« API / Monitoring

Å��l��}�;£�� ;®LÁZ�:�¬�¼

« Image Manager« Publisher« Syndicator

®¯&®

�


SAP AG 2006

0'06HUYHU0'06HUYHU

0'0�8VHU�,QWHUIDFHV

'DWD0DQDJHU'DWD

0DQDJHU,PDJH

0DQDJHU,PDJH

0DQDJHU

3XEOLVKHU3XEOLVKHU ,PSRUW0DQDJHU,PSRUW

0DQDJHU

6\QGLFDWRU6\QGLFDWRU

/DQJXDJH�6HOHFWRU/DQJXDJH�6HOHFWRU

&RQVROH 3RUWDO3RUWDO

�

� The MDM100 course will cover the MDM Server, Console, Data Manager, Import Manager, Syndicator, and Language Selector. It will also discuss accessing MDM repositories using APIs via the SAP Portal.

� Image Manager and Publisher are covered in a different SAP course.


SAP AG 2006

3RUWDO�%DVHG�$FFHVV

y 0XOWLGLPHQVLRQDO�6HDUFKy 'LVSOD\LQJ�5HFRUG�'HWDLOV

° )LHOGV�° $WWULEXWHV° &RPSDULVRQ° 5HODWLRQVKLSV

y 'DWD�(QWU\�DQG�0DLQWHQDQFHy 9LVXDOL]DWLRQ�RI�.H\�0DSSLQJy 3HUVRQDOL]DWLRQ��0\�6HDUFK��0\�%DJV�y ,QWHJUDWLRQ�WR�8QLYHUVDO�:RUNOLVWy ,QWHU�L9LHZ FRQQHFWLYLW\y $GPLQLVWUDWLYH�RSWLRQV�DQG�XWLOLWLHV

�


SAP AG 2006

.H\V�WR�6XFFHVVIXO�3URMHFWV


�


SAP AG 2006

7KH�.H\V�WR�6XFFHVVIXO�3URMHFWV

3DUWQHU��&XVWRPHU��3URMHFWVy 7KH�ULJKW�UHDVRQ WR�VWDUW�DQ�0'0�SURMHFWy &RUSRUDWH�EX\�LQ�± EXVLQHVV�GULYHUVy &RRSHUDWLRQ RI�GLIIHUHQW�OLQHV�RI�EXVLQHVV��/2%V�y 3URSHU�VFRSLQJy 8QGHUVWDQGLQJ WHFKQLFDO�DQG�QRQ�WHFKQLFDO�OLPLWDWLRQV

�


SAP AG 2006

6FRSLQJ��%OXHSULQWLQJ��DQG�6WDIILQJ

� 'HILQLQJ�VFRSH�LV�SDUDPRXQW� $�EOXHSULQW�VKRXOG RXWOLQH�DOO�UHTXLUHPHQWV�DQG�FKDOOHQJHV� ,W�LV�KDUG�WR�JXHVWLPDWH HYHU\WKLQJ� 6WDIILQJ UHTXLUHV�PRUH�WKDQ�RQH�UHVRXUFH

�


SAP AG 2006

4XLFN�'HSOR\PHQW

± 3UH�EXLOW�GDWD�PRGHOV± 3UH�EXLOW�PDSSLQJV± 3UH�EXLOW�L9LHZV��

UHSRUWV��DQG�ZRUNIORZ± (DVLO\�FRQILJXUDEOH

3UH�EXLOW�EXVLQHVV�FRQWHQW�DFFHOHUDWHV�DGRSWLRQ²´³�µ>¶#³�·*¸ ¹º8»R¸ ³�µ

¼ º<½e¾¿³�µ<¸ ÀDº>»T¸ ³�µ

�:��Á�Â �

�:��Ã Â ¥

�#ÄFÅ�Æ*�>��Ç ��È8¢ É%Ê

�"Ë>Ë8Ì Í É ¢��XÍ ÄFÅ�Î

¥´¦<¥¦�¢ �K¢Ï¥'¢>Å�¢�È&�8¤

Ð:Ñ Ò�Ó�Ô�Õ Öp×HÕpØpÓ*Ñ�Ô8Ù>ÕpÓ�Õ×Õ Ò�Õ�Ú�Ñ�Û"Ñ Ò�ÓÜ&Ý Ô Ó�Õ�ÖQÞ�ß à�ß Ñpá<Ø�â

ã�ä�ß å�Ñ%åæ Ô Ý�ç Ñ%åDä Ô*Ñ�Ø%è�éDêìë èÔ�Ñ æ Ý Ô*Ó*Ø×�Ù<×Ù:Õ�Ó*Õ�×�Õ�Ò%Õ�Ú Ñ Ôê Ý Ô�í3îKÖ Ý áàFÕ�Ö ß å Õ�Ó�ß Ý Ò�è×HÕpÓ ç�ï�ð Û"Ñ�ÔKÚ�Ñ�èñ Ò�Ô�ß ç ï Û"Ñ Ò�Ó

×Õ%ØQÓ�Ñ�Ô8Ù>ÕpÓ�Õò>Ñ Ô ó�Ñ�Ô

99ò8ô Üxõ#ö

99

×�Ù#×ö Û æ Ý Ô Óò8Ñ Ô ó�Ñ�Ô

×�Ù#×ò&÷ Ò�åDß ç Õ3Ó Ý Ôò8Ñ�Ô*ó�Ñ�Ô

9999 ÁDø �X¤�¢�É%��ÄF¤

¥�¢&Ë>Ë8Í Å�Èù ¤�¢8Å�Î�¢ É��\Í ÄFÅ�¢8Ì�Î Ê Î��Dú

û�ü Î>Í Å � Î ÎÏÃHÄFÅ��8Å%�

�


SAP AG 2006

6$3�1HW:HDYHU�0'0�,QWURGXFWLRQ��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�QHHG�IRU�0DVWHU�'DWD�0DQDJHPHQW� $SSUHFLDWH�WKH�YDOXH�RI�6$3�0'0� ,QWURGXFWLRQ�RI�WKH�,7�DQG�%XVLQHVV�6FHQDULRV� 6HH�KRZ�0'0�ILWV�LQWR�WKH�1HW:HDYHU�VWDFN

�


SAP AG 2006

0'0�'DWD�0DQDJHU




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�


SAP AG 2006

&RQWHQWV�� 0'0�'DWD�0DQDJHU�$SSOLFDWLRQ

ý 6HDUFKLQJ DQG�PRGLI\LQJ GDWDý 6DYLQJ VHDUFKHV


�


SAP AG 2006

0'0�'DWD�0DQDJHU� 8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� ([SODLQ�WKH�YDOXH�RI�0'0�'DWD�0DQDJHU�� 8VH�0'0�'DWD�0DQDJHU�UHFRUG�PRGH�� 'HVFULEH�WKH�GHWDLOHG�IXQFWLRQV�IRU�

VHDUFKLQJ�FUHDWLQJ�UHFRUGV�DQG�DGGLQJ�GDWD�WR�WKH�H[LVWLQJ�UHSRVLWRU\

�


SAP AG 2006

0'0�'DWD�0DQDJHU��%XVLQHVV�6FHQDULR

� 7KH�XVHU�LQWHUIDFH�IRU�WKH�PDVWHU�GDWD�VSHFLDOLVW�LV�WKH�'DWD�0DQDJHU�DQG�\RX�ZRXOG�OLNH�WR�XQGHUVWDQG�WKH�FDSDELOLWLHV�RI�WKLV�WRRO��

�


SAP AG 2006

,QWURGXFWLRQ WR�'DWD 0DQDJHU

,QWURGXFWLRQ WR�'DWD 0DQDJHU6HDUFKHV6DYLQJ�6HDUFKHV

&KDQJLQJ�'DWD6XPPDU\

&KHFN�,Q�2XW�DQG�3URWHFW�

�


SAP AG 2006

0'0�'DWD�0DQDJHU��8VHU�,QWHUIDFH

0'0VHUYHU0'0VHUYHU

'DWD0DQDJHU'DWD

0DQDJHU

� 9DULRXV�PRGHV� 5HFRUG�VHDUFK� 5HFRUG�FUHDWH��PRGLI\��GHOHWH� 5HFRUG�FRPSDUH� 5HFRUG�PHUJH� :RUNIORZ�FUHDWH��H[HFXWH� 5HFRUG�DVVLJQPHQWV� .H\�0DSSLQJ

� 0DWFKLQJ� 9DOLGDWLRQ�$VVLJQPHQWV

5HSRVLWRU\

�

� This functionality can also be accessed thru the APIs or SAP Portal iViews.


SAP AG 2006

&RQQHFWLQJ�WR�WKH�'DWD�0DQDJHU

� 'RXEOH�FOLFN�'DWD�0DQDJHU�VKRUWFXW� (QWHU�5HSRVLWRU\��/DQJXDJH��DQG�8VHU

�

� The repository must be loaded before logging on to the MDM Data Manager.


SAP AG 2006

0'0�'DWD�0DQDJHU�0RGHV

� 0'0�'DWD�0DQDJHU�0RGHVý 5HFRUG�0RGHý +LHUDUFK\�0RGHý 7D[RQRP\�0RGHý 0DWFKLQJ�0RGHý )DPLO\�0RGH

�

� 5HFRUG�PRGH: Allows you to search, view, and edit the records of DQ\ WDEOH in the repository. This is the mode you will use most often, primarily to view and edit product records in the main table and subtables.

� +LHUDUFK\�PRGH: Allows you to view and edit the KLHUDUFK\�tables in the repository, including regular hierarchy tables, taxonomy tables, and the Mask table. Though you can also view and edit the records of a hierarchy table in Record mode, Hierarchy mode specifically allows you to edit the parent/child relationships and the sibling order of the hierarchy.

� 7D[RQRP\�PRGH: Allows you to view and edit the WD[RQRP\ tables in the repository. You will use this mode to create and maintain the category hierarchy used in the repository and to manage the attributes associated with each category and subcategory. Though you can also view and edit taxonomy tables in both Record and Hierarchy modes, Taxonomy mode is unique in that instead of focusing on the UHFRUGV�of the taxonomy table, it allows you to create and manage the pool of DWWULEXWHV�associated with the taxonomy table and to assign attributes to categories on a category-by-category basis.

� 0DWFKLQJ�PRGH: Matching mode supports de-duplication, and is used to identify and eliminate duplicate records within an MDM repository. The Matching Mode supports interactive, rule- and strategy-based matching of records.

� )DPLO\�PRGH: Allows you to view and edit the )DPLOLHV�table, which layers a hierarchy of families upon the taxonomy hierarchy to further break down each category into smaller groups of products. Use this mode to partition the categories of the taxonomy hierarchy by the values of other fields and/or attributes, and then to associate family data (such as an image, a paragraph, and bullets) once with each IDPLO\�of products rather than with each individual product.


SAP AG 2006

6HDUFKHV




�


SAP AG 2006

0'0�6HDUFK�$GYDQWDJHV

� 6HDUFK�RQO\�IRU�GDWD�WKDW�LV�DYDLODEOH� 1DUURZHG�VHDUFK�UHVXOWV�ZLOO�RQO\�VKRZ�UHPDLQLQJ�

DYDLODEOH�GDWD� 'ULOOGRZQ�VHDUFKHV� 0XOWLSOH�FKRLFH�VHOHFWLRQV��ERWK�$1'�DQG 25�FRQGLWLRQV�

(QWLUH&DWDORJ

'HVLUHG,WHPV

þx¸�µFÿ�· �� ¸�µ��³�¸*µ:»�� º��&»

� � � � ��

�� "!# � $ # % �'& ( �*)

(¥�¢&Å Ê ¥ ü Ì �\Í Ë&Ì �

�

� Most master data management systems use DBMS-style query forms to initiate a search and locate specific records. Users start with nothing and often end up with nothing, blindly typing in values as though looking for a needle in a haystack.

� By contrast, the MDM system features a powerful and efficient search capability called drilldown search. Drilldown search allows users to start with all of the items in the repository and then effortlessly zoom in on items of interest.


SAP AG 2006

5HFRUG�0RGH

5HFRUGV��VHDUFK�UHVXOW

6HDUFK�SDQH 5HFRUG�GHWDLOV

0'0�'DWD�0DQDJHU�LV�D�FRPELQHG�DSSOLFDWLRQ�ZKHUH�\RX�FDQ�VHDUFK�DQG�YLHZ�WKH�GDWD��DV�ZHOO�DV�FUHDWH�QHZ�DQG�PDLQWDLQ�HGLW�H[LVWLQJ�GDWD�

$GGLWLRQDOUHFRUG�LQIRUPDWLRQ

�


SAP AG 2006

7DEOH�6HOHFWLRQ

6HOHFW��IURP�WKH�GURSGRZQ�OLVW��ZKLFK�WDEOH�\RX�ZLOO�EH�VHDUFKLQJ�LQ�

�

� Record mode is used to manage the records of any table in the repository, including the main table, regular sub-tables, and object sub-tables. When you view a table in Record mode, MDM allows you to search for, browse, and edit the table records.

� Most of your work with the MDM Data Manager will probably be in Record mode, managing the product records of the main table. The process of editing product records typically involves: • Performing a search to narrow down the set of records to just the ones on which you want to work • Editing the records one after another or as a group until done


SAP AG 2006

6HDUFK�3DUDPHWHUV�+ · º>»"· ³³-,�./� ¶0�:º<½1�/2.»eº�3>¶

4 º � ³�µ�³¾65¿· ³H³7,0.��.¶��>º<½*��2¡»_º�3>¶8 .· »R¸*· �:9��·F· ³H³7,:.;�.¶<�Fº<½*�/2

=>.Fº#·�¸ ?T¸ �F¹ · ³³7,0.;�.¶��º#½1�/2

+ ½@�0�<A + ³�½e¾ þ��:º½@��2

�

� The search functionality in MDM has its own methodology. � The search starts on the full data set of the repository. Every time you change the level at the panel

(jump from one table or search option to another), the number of hits will be reduced. � This reduced data set will be the pool from which the next step is able to search. If you want to

enlarge the search criteria again, you have to release the previous restrictions and drill down again. � Release is not possible step by step; you have to release the entire search and start again.


SAP AG 2006

&RPSDUH�5HFRUGV�9LHZ

/DYHQGHU$TXD

<HOORZ

$OO�YDOXHV�DUH�5RVH�H[FHSW�ZKHUH�PDUNHG�

�

&RPSDULQJ�5HFRUGV�� In Record mode, you can select multiple records in the Records pane and use the Compare Records

command to create a table that contains a side-by-side comparison matrix. � The Compare Records command provides another convenient way to compare multiple records. Use

it to open a pop-up window with the side-by-side comparison matrix that contains a column for each selected record and a row for each of their fields and attributes (and family fields if the repository has a family table). Like multi-record selection in the Records pane, 6$3�0'0 highlights differences with background shading to indicate records that have different or missing values: � <HOORZ. The same value appears in all of the selected records (no missing values). � $TXD. The same value or NULL appears in all of the selected records (one or more missing

values). � /DYHQGHU. Different values or NULL appear in the selected records (one or more missing values). � 5RVH. Different values appear in the selected records but all the records have values (no missing

values).


SAP AG 2006

6DYLQJ�6HDUFKHV




�


SAP AG 2006

6DYLQJ�6HDUFK�5HVXOWV

Query

User who saved it

Data Manager

/RFDO�6HDUFK

Static dataQueryResults

All usersAll usersUser access

Console or Data ManagerData ManagerCreation location

0DVNV1DPHG�6HDUFK7\SH�RI�6DYHG�6HDUFK

� 7KHUH�DUH�WKUHH�ZD\V�WR�VDYH�D�VHDUFKý 1DPHG�VHDUFK��6DYHV�VHDUFK�VHOHFWLRQ�IRU�DOO�XVHUVý /RFDO�VHDUFK��6DYHV�VHDUFK�VHOHFWLRQ�IRU�FXUUHQW�XVHUý 0DVNV��$Q�DFFXPXODWLRQ�RI�VHDUFK�UHVXOWV

�

� The MDM Data Manager includes the ability to save all of the current search selections to a named search in the Named Searches table and then restore them at a later time.

� The MDM Data Manager includes the ability to save all of the current search selections to a local search in the file system and then restore them at a later time.

� Using MDM masks, you can slice a single master MDM repository of product information into an effectively unlimited number of custom virtual repositories, dramatically simplifying the maintenance of a single repository targeted at multiple audiences. Each virtual repository can contain a different subset of products from the master and appears to the user as a completely private repository.

� Unlike SQL views, product masks impose no performance penalty whatsoever and are defined at the individual product level, rather than the query level. To the user of the MDM system, they appear as simply another dimension of the multidimensional search; on the Web, a mask can be automatically applied to the published electronic catalog upon site entry, so that each user sees only the slice of the MDM repository that you want them to see.

� Masks allow you to create multiple custom subset repositories from a single master repository without duplicating the underlying product records. This guarantees consistency and synchronization of the data across updates, since there is never more than one copy of each record.


SAP AG 2006

� 1DUURZ�WKH�UHFRUGV�GLVSOD\HG�ZLWK�DV�PDQ\�RU�IHZ�VHDUFK�SDUDPHWHUV

� 7KHQ�JR�WR�6HDUFK�Æ 6DYH�DV�1DPHG�6HDUFK«

� (QWHU�D�VHDUFK�QDPH

� 7R�UHWULHYH�WKH�VHDUFK�UHVXOWV�DW�DQ\�WLPH��JR�WR�6HDUFK�Æ5HVWRUH�1DPHG�6HDUFKHV�Æ ³\RXU�VHOHFWLRQ´

1DPHG�6HDUFK

�

� Choose Save as Named Search… to store the search criteria. � Every item you add to the repository that matches the criteria will be added to the results when you

restore the saved search. � This search is available to other users. � The "Named Search" table must be created for the repository. Adding this table requires a change to

the system registry. To make this change, see relevant SAP Notes, and follow the directions. This change must be done on the MDM Server.


SAP AG 2006

� 1DUURZ�WKH�UHFRUGV�GLVSOD\HG�ZLWK�DV�PDQ\�RU�IHZ�VHDUFK�SDUDPHWHUV

� 7KHQ�JR�WR�6HDUFK�Æ 6DYH�DV�/RFDO�6HDUFK«

� (QWHU�D�VHDUFK�QDPH

� 7R�UHWULHYH�WKH�VHDUFK�UHVXOWV�DW�DQ\�WLPH��JR�WR�6HDUFK�Æ5HVWRUH�/RFDO�6HDUFK�Æ ³\RXU�VHOHFWLRQ´

/RFDO�6HDUFK

�

� This search is ONLY available to the user who created.


SAP AG 2006

0DVNV

� 1DUURZ�WKH�UHFRUGV�GLVSOD\HG�ZLWK�DV�PDQ\�RU�IHZ�VHDUFK�SDUDPHWHUV�DV�GHVLUHG

� 6HOHFW�WKDW�WKH�UHFRUGV�WKDW�ZLOO�EH�SDUW�RI�WKH�PDVN� 5LJKW�FOLFN�RQ�VHOHFWHG�

UHFRUGV�DQG�FKRRVH�$GG�WR�0DVN�Æ ³VHOHFW�D�PDVN´

� 7R�UHWULHYH�PDVN�UHVXOWV��JR�WR�0DVNV DQG�VHOHFW�\RXU�PDVN�

�

� Choosing $GG�WR�0DVN will add the search results. � Records are added to the existing mask. � With this function, you could create customer-specific repositories to ensure that certain target

groups only see the items they are supposed to see and still keep additional maintenance at an acceptable level.


SAP AG 2006

&KHFN�,Q�2XW�DQG�3URWHFW




�


SAP AG 2006

&KHFN�,Q�2XW

8VHU�FHQWULF�&KHFN�2XW – A user may check out a record. While it is checked out, this user can modify the record. Other users see the original record and cannot modify it or check it out.-RLQ�&KHFN�2XW – After a record is initially checked out, other users may join the check out This allows them to view and modify the checked out record.

�

� Sometimes there is a need to allow one or more users to edit a copy of a record over an extended period of time as part of a collaborative process ZLWKRXW�changing the original until you are ready to commit the changes, and only then make them visible to users all at once. MDM allows you to do this with a versioning mechanism known as FKHFN�RXW. Checkouts can be performed only in Record mode on the main table.

� The Check Out can be performed with several options, depending on the menu selection: � 2SHUDWLRQ�'HVFULSWLRQ�

y Check Out Exclusive => Checks out the selected records exclusively. y Check Out Nonexclusive => Checks out the selected records nonexclusively. y Check Out NewRecord Exclusive => Checks out a new record exclusively. y Check Out New Record Nonexclusive => Checks out a new record nonexclusively. y Join Checkout => Joins the selected checked out records. y Unjoin Checkout => Unjoins the selected checked out records. y Check In => Checks in the selected records to commit changes. y Roll Back => Rolls back the selected records to discard changes. y Modify Join Permissions => Specifies which roles and users can join the selected

checked out records. y All Versions => Displays all versions of all checked out records.


SAP AG 2006

&KHFN�,Q�Î &KHFN�2XW�DQG�3URWHFW

&KHFN�LQ��FKHFN�RXW�ORRNHG�DW�IURP�GLIIHUHQW�XVHUV�

��³&KHFN�RXW´�LQLWLDWRU

��³&KHFN�RXW´�SDUWQHU&KHFNHG�RXW�QRQ�H[FOXVLYHO\�ÆFDQ�EH�VKDUHG�

BDC�E�F<GHE�IKJ7L0M"EHN/F�O�LQP;R S�E�O T�U

BVC0E�F/GHE<I6J"L0MXW<J7WYE0N<F�OZL0P�R S0E;O T�[B]\/W_^<E>P"C�\�`@E<Ia\�W/IbL"WQP;C<\�`@E�Ic^0TM�C�EYF�C�E0F;GdJ-L:MXe�\�`fM�W<E�`;gh\�W�J�M C�E/`XL�P�E/`

i `*J/MjE�F0MfE<IBVC0E�F/GQE�I6J7L:MW<J7W/klEHN�F�OZL:P�R S�E�O T

BVC0E�F/GQE�I6J7L:ME:N/F/OmL�P�R S�E�O T

�

� The status of a record, whether it is checked out, Checked out exclusively, protected, etc. is displayed in a separate column.

� Working with checked out records: If you try to modify exclusively checked out records and you are not the originator of the checkout, you will get an error message in a popup telling you that the record is checked out by another person.


SAP AG 2006

&KDQJLQJ�'DWD




�


SAP AG 2006

&KDQJLQJ�'DWD�9DOXHV�LQ�5HFRUG�'HWDLO

'URSGRZQ�WUHH

6LQJOH�YDOXH�ORRNXS�FHOOV

0XOWLYDOXH ORRNXS�FHOO

�


SAP AG 2006

0'0�'DWD�0DQDJHU��4XDOLILHG�7DEOHV

$OO�TXDOLILHG�ORRNXS�DQG�VSHFLDO�WDEOHV�DUH�VKRZQ�LQ�WKH�ULJKW�FROXPQ�

�

� Each product record may be assigned to one or more qualified table records. The MDM Data Manager includes a convenient “search-within-a-search” within the qualified lookup selector dialog for narrowing down the set of qualified table records and assigning them to product records.

� You can also use it to assign the values to their corresponding qualifiers. Qualified lookup fields appear on the right side of the Record Detail tab.


SAP AG 2006

6XPPDU\




�


SAP AG 2006

0'0�'DWD�0DQDJHU��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� ([SODLQ�WKH�YDOXH�RI�0'0�'DWD�0DQDJHU�� 8VH�0'0�'DWD�0DQDJHU�UHFRUG�PRGH�� 'HVFULEH�WKH�GHWDLOHG�IXQFWLRQV�IRU�

VHDUFKLQJ�FUHDWLQJ�UHFRUGV�DQG�DGGLQJ�GDWD�WR�WKH�H[LVWLQJ�UHSRVLWRU\

�


([HUFLVHV�

8QLW�� 'DWD�0DQDJHU�1DYLJDWLRQ�7RSLF��0'0�'DWD�0DQDJHU�

At the conclusion of this exercise, you will be able to:

• 8VH�0'0�'DWD�0DQDJHU�UHFRUG�PRGH��• 'HVFULEH�WKH�GHWDLOHG�IXQFWLRQV�IRU�VHDUFKLQJ�FUHDWLQJ�

UHFRUGV�DQG�DGGLQJ�GDWD�WR�WKH�H[LVWLQJ�UHSRVLWRU\�

3XUSRVH�This script walks through the MDM Data Manager. It introduces you the Data Manager Application and gives you some “Search Practice”.

3UHUHTXLVLWHV��• MDM Repository has been created.

• Data has been entered in the repository.

• MDM Server has been started.

1-1 Logon to Repository

Connect to MDM Repository

1-1-1 Start the SAP MDM Data Manager Application

1-1-2 Press and choose LOCALHOST (Server), select Repository: Exercise_Master Æ OK


1-1-3 Type User: mdmuser+Your_letter and password: training (all lowercase)

1-1-4 Then click OK.

1-2� Introducing MDM Data Manager��SAP MDM Data Manager ÆFormer name &OLHQW

1-2-2 The left hand side is the search area. Here you can use all parameters to drill down into your repository content.

1-2-3 The upper pane shows all objects in the repository

1-2-4 The record detail pane give you all fields and attribute information for one or multiple records

1-2-5 The status row contains the information how many records do exist and how many are in the current search.


1-3 Data Manager Navigation


2-1 Search Exercises

2-1-1� Find out how many products are from the ³%RVV�+ROGLQJ��,QF�´?

Of the above, how many products are available in ³6L]H´�=�³��´ ? Æ

^+,17��Size is an attribute in the Category table.}

�&OHDU�SUHYLRXV�VHDUFK��2-1-2 How many products have an �2YHUDOO�/HQJWK�>1RP@��=��PP´�?

Or less than�³��PP´"�Æ�

�&OHDU�SUHYLRXV�VHDUFK��

2-1-3� Which �0DQXIDFWXUH�V��have a��7\SH��= �$FWLYDWRU��?Æ��&OHDU�SUHYLRXV�VHDUFK�

�2-1-4� Which parent category contains�³7LS�7\SH´�=�³3R]LGULY�´�?Æ��


2-1-5�� How many products are in the�³0DVN´�called�³&RQYHUW�´�"Æ��


2-1-6� How many records have a�³81636&´�that starts with the word�³7RRO´�?Æ�^+,17��Use the Free-Form Search.}


2-1-7� What is the ³1DPH´�of the product whose��7HPSOH�/HQJWK��=��PP��?�Æ��


2-1-8 What is the��6DOH�3ULFH��in �*HUPDQ\��for�³3DUW�1XPEHU´�=�³��´�?Æ��


2-1-9 How many items have a ³)LQLVK´ which is ³0HWDOOLF´ $1' ³0DWWH´?

^+LQW��The answer is NOT 104.}�

�&OHDU�SUHYLRXV�VHDUFK�

2-1-10 What is the key mapping for ³3DUW�1XPEHU´ = ³��´�"�


�2-1-11 What is the key mapping for ³3DUW�1XPEHU´ = ³��´�? �

�2-1-12 How many of the products that�do 127�have��,PDJH�'HWDLOV�, but has a�

³&RORU´� �³:KLWH´�?Æ�{+,17: Use Free-Form Search for Image Details then Attribute – color.}�Save your last search as a�6HDUFK�Æ�6DYH�DV�/RFDO�6HDUFK��In the dialog box enter the Search name: :KLWH�ZLWK�QR�,PDJH�'HWDLOV��

�2-1-13 We are now going to add search 4.12 to a Mask. Select all search results

(Ctrl+A) then right-click and $GG�WR�0DVN�Æ <RXUOHWWHU_:KLWH�ZLWK�QR�,PDJH�'HWDLOV��

�2-1-14� Right-click on one record and select 'XSOLFDWH. �


2-1-15 Run your Mask (open Masks sliding tab and select your mask) and note the number of records?Æ


2-1-16 Run your local saved search (go to 6HDUFK�Æ�5HVWRUH�/RFDO�6HDUFK�Æ�:KLWH�ZLWK�QR�,PDJH�'HWDLOV.) How does the total number compare to 4.13?Æ

Why the difference in total records for Mask and Local Search, when you had originally saved both with the same data?Æ

Delete the record you just created.



�


�6ROXWLRQV�

Unit: Data Manager Navigation

Topic: MDM Data Manager

2-1-1 Find out how many products are from the “Boss Holding, Inc.”? Æ �� Of the above, how many products are available in “Size” = “12” ? Æ � 2-1-2 How many products have an "Overall Length [Nom]" = "120.000 mm” ? Æ �� Or less than “120.000 mm”? Æ �� 2-1-3 Which "Manufacture(s)" have a "Type" = "Activator" ?Æ /RFWLWH�&RUSRUDWLRQ�DQG�

5XVW�2OHXP�&RUSRUDWLRQ 2-1-4 Which parent category contains “Tip Type” = “Pozidriv®” ?Æ +DQG��3RZHU��

0HFKDQLFDO��0HDVXULQJ�7RROV�

2-1-5 How many products are in the “Mask” called “Convert ” ?Æ ��

2-1-6 How many records have a “UNSPSC” that starts with the word “Tool” ?Æ ��±�

XVLQJ�)UHH�)RUP�6HDUFK� 2-1-7 What is the “Name” of the product whose "Temple Length" = "140.00 mm" ? Æ

&ULFNHW��3URWHFWLYH�(\HZHDU� 2-1-8 What is the "Sale Price" in "Germany" for “Part Number” = “3126” ?Æ ¼��

2-1-9 How many items have a “Finish” which is “Metallic” AND “Matte”? �

(You need to right-click on Finish and select Add Multi-Valued Search. Then use the Ctrl key to select Metallic and Matte.)

2-1-10 What is the key mapping for “Part Number” = “2015” ? 5��F� ��DQG�5��

��.(Hint to search quickly for 2015, sort by Part Number and then type 2015.) 2-1-11 What is the key mapping for “Part Number” = “15-000” ? 5��F� ��DQG�

�� (for the non-default value.)


2-1-12 How many of the products that do NOT have "Image Details", but has a “ Color” = “ White” ?Æ {��, but 148 with no image Save your last search as a 6HDUFK�!�6DYH�DV�/RFDO�6HDUFK�� In the dialog box enter the Search name: White with no Image Details.

2-1-13 We are now going to add search 2-1-12 to a Mask. Select all search results (Ctrl+A)

then right-click and $GG�WR�0DVN�Æ Yourletter_:KLWH�ZLWK�QR�,PDJH�'HWDLOV� 2-1-14 Right-click on one record and select 'XSOLFDWH. 2-1-15 Run your Mask (open Masks sliding tab and select your mask) and note the number

of records?Æ �� 2-1-16 Run your local saved search

(go to 6HDUFK�Æ�5HVWRUH�/RFDO�6HDUFK�Æ�:KLWH�ZLWK�QR�,PDJH�'HWDLOV.) How does the total number compare to 2-1-13? Æ 7KH�/RFDO�6HDUFK�ZLOO�KDYH�DQ�DGGLWLRQDO�UHFRUG��

Why the difference in total records for Mask and Local Search, when you had originally saved both with the same data?Æ 0DVN�±�VDYHV�D�VWDWLF�VHDUFK�UHVXOW�/RFDO�6HDUFK�±�VDYHV�D�TXHU\�ZKLFK�LV�UHFDOFXODWHG�HYHU\�WLPH�LW�LV�DFFHVVHG��

Delete the record you just created.


SAP AG 2006

8QLW��'DWD�0RGHOLQJ��&RQVROH




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�


SAP AG 2006

&RQWHQWV�� 0'0�&RQVROH

� &RQQHFWLQJ WR�0'0�6HUYHU� 7DEOH�DQG�ILHOG GHVFULSWLRQ DQG�FUHDWLRQ

0'0�&RQVROH

�


SAP AG 2006

0'0�&RQVROH��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� ([SODLQ�WKH�GLIIHUHQW�WDEOH�W\SHV�LQ�0'0�&RQVROH� ([SODLQ�WKH�XVDJH�RI�WKH�YDULRXV�WDEOHV�DQG�ILHOGV

�


SAP AG 2006

0'0�&RQVROH��%XVLQHVV�6FHQDULR

� $V�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RX�ZDQW�WR�NQRZ�KRZ�WR�KDQGOH�0'0�VHUYHUV�XVLQJ�WKH�6$3�0'0�&RQVROH��

� ,Q�RUGHU�WR�DFFXUDWHO\�PRGHO�\RXU�PDVWHU�GDWD�LQ�0'0��\RX�QHHG�WR�XQGHUVWDQG�WKH�DYDLODEOH�WDEOH�W\SHV�

� ,Q�RUGHU�WR�DFFXUDWHO\�PRGHO�\RXU�PDVWHU�GDWD�LQ�0'0��\RX�QHHG�WR�XQGHUVWDQG�WKH�DYDLODEOH�ILHOG�W\SHV��

� $V�WKLV�SURGXFW�VWRUHV�PDVWHU�GDWD�LQ�RQOLQH�UHSRVLWRULHV��LW�LV�LPSRUWDQW�IRU�\RX�WR�XQGHUVWDQG�WKH�UHSRVLWRU\�KDQGOLQJ�FDSDELOLWLHV�RI�WKH�0'0�&RQVROH��

�


SAP AG 2006

0'0�&RQVROH ,QWURGXFWLRQ5HSRVLWRU\�7DEOHV)LHOG�7\SHV$GPLQ�)ROGHU

0'0�&RQVROH ,QWURGXFWLRQ

6XPPDU\

�


SAP AG 2006

0'0�&RQVROH�8VHU�,QWHUIDFH

0'06HUYHU0'06HUYHU

&RQVROH

� &RQWUROV�0'0�6HUYHU� 5HSRVLWRU\�FUHDWLRQ� 7DEOH��ILHOG�FUHDWLRQ� 'DWD�PRGHOLQJ� +DQGOHG�E\�WKH�DGPLQLVWUDWRU '%

�

� The MDM Console allows the system manager to administer and monitor MDM Server software; to create and maintain the structure of the repositories; and control access to them. Records are not entered or managed within the MDM Console.


SAP AG 2006

&RQQHFWLQJ�WR�WKH�&RQVROH

/RFDOO\

6WHS��6HOHFW�VHUYHU

6WHS��0RXQW�VHUYHU

6WDUWXS�VWHSV�WR�FRQILJXUH�D�UHSRVLWRU\

6WHS��6WDUW�VHUYHU

�

� The MDM Console provides you with information about the MDM servers and all repositories currently connected to the servers. Each server and each repository has a colored status icon showing the current status of the repository: y Green: Server or repository is running. Users can access the data in the repository. y Red: Server or repository is stopped. There is no access to the data. y Blue: Repository is currently loading. y Grey: Repository needs to be updated; this is often the case, for example, after applying a new

build.


SAP AG 2006

5HSRVLWRU\ 7DEOHV

0'0�&RQVROH ,QWURGXFWLRQ5HSRVLWRU\�7DEOHV)LHOG�7\SHV$GPLQ�)ROGHU6XPPDU\

�


SAP AG 2006

0'0�&RQVROH��5HSRVLWRU\�6WUXFWXUH

$Q�0'0�UHSRVLWRU\�FRQVLVWV�RI�WKH�IROORZLQJ�WDEOHV�� 0DLQ�WDEOH�

5HIOHFWV�WKH�PRVW�LPSRUWDQW�REMHFW��LQ�D�SURGXFW�UHSRVLWRU\��LW�ZRXOG�EH�WKH�SURGXFW��LQFOXGLQJ�D�ILHOG�IRU�HDFK�JHQHUDO�YDOLG�SLHFH�RI�LQIRUPDWLRQ

� 6XE�WDEOHV�8VXDOO\�ORRNXS�WDEOHV��YDOXH�WDEOHV�FXVWRPL]LQJ�WDEOHV�

� 2EMHFW�WDEOHV�,QFOXGH�LPDJHV�WH[W�EORFNV�DQG�3')V

� 6SHFLDO�WDEOHV�,QFOXGHV�PDVNV��IDPLOLHV��LPDJH�YDULDQWV��UHODWLRQVKLSV��DQG�GDWD�JURXSV��KLGGHQ�

�

� 0DLQ�7DEOH: Every MDM repository has exactly one main table. The main table consists of object information. It includes an individual record for each object in the repository and an individual field for each piece of object information that applies to all of the records, such as SKU, product name, product description, manufacturer, and price for the object product. Most of the time, you will be looking at information in the main table.

� 6XE�WDEOHV: An SAP MDM repository can have any number of sub-tables. A sub-table is usually used as a lookup table to define the set of legal values to which a corresponding lookup field in the main table can be assigned; these tables hold the lookup information. For example, the main table may include a field called Manufacturer; the actual list of allowed manufacturer names would be contained in a sub-table. Only values that exist in sub-table records can be assigned to the value of the corresponding lookup field in the main table.

� 2EMHFW�WDEOHV: Object tables include the images, text blocks, and PDFs tables. An object table is a special type of lookup sub-table, where each object table is used to store a single type of object, such as images, text blocks, or PDF files. You cannot store an object directly in a main or sub-table field in an SAP MDM repository. Instead, each object is defined or imported into the repository once and then linked to a main or sub-table field as a lookup into the object table of that type.

� 6SHFLDO�WDEOHV: Special tables include the Masks, Families, Image Variants, Relationships, Roles, Users, and Data Groups tables. Each special table has its own particular behavior with respect to how it is created and how it is managed.


SAP AG 2006

1R�PDLQWHQDQFH�DOORZHG�:RUNIORZV,PDJHV7H[W�EORFNV+70/�WH[WV3')V

7DEOHV�DYDLODEOH�0DLQ�WDEOH)ODW�ORRNXS+LHUDUFKLHV7D[RQRPLHV4XDOLI\LQJ�WDEOHV0DVNV)DPLOLHV5HODWLRQVKLSV,PDJHV�YDULDQWV

2EMHFW�/LVW�

�

7DEOH�W\SHV�� A traditional SQL DBMS stores data in the records and fields (rows and columns) of a collection of

flat database tables. All tables have the same rectangular structure in SQL. A SQL database is relational because of the relationships set up between the different tables.

� In an relational DBMS (RDBMS), information about a single product can be combined from multiple tables by relating values in matching columns. This helps to eliminate redundant data; beyond that, however, an RDBMS does not support any additional structuring of the data itself.

� By contrast, the MDM System supports a variety of different table types that are specifically suited for storing, organizing, structuring, classifying, managing, and publishing product information in a product repository, including efficient support for category-specific product attributes that are inherently non-relational.


SAP AG 2006

)ODW�DQG�4XDOLILHG�/RRNXS�7DEOH

$�ORRNXS�WDEOH�LV�XVHG�WR�VWRUH�YDOXHV�WKDW�DUH�VKDUHG�E\�PDQ\�UHFRUGV�LQ�RWKHU�WDEOHV��DQG�DOVR�WR�DFW�DV�D�YDOLG�WDEOH�WKDW�GHILQHV�WKH�VHW�RI�OHJDO�YDOXHV�RI�WKH�FRUUHVSRQGLQJ�ORRNXS�ILHOG�IRU�GDWD�HQWU\�DQG�VHDUFK��

)ODW�WDEOHV� &DQ�EH�PXOWL�YDOXHG

4XDOLILHG�WDEOHV� 6WRUHV�ORRNXS�UHFRUGV� 6XSSRUWV�TXDOLILHUV� $OZD\V�PXOWL�YDOXHG

�

� A flat table is always a sub-table. It has the standard, rectangular SQL structure consisting of records and fields (rows and columns).

� A qualified table in MDM stores a set of lookup records and also supports qualifiers, or sub-fields, that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record. MDM supports multiple simultaneous qualified tables.

� Qualified tables can be used to support product applications and application-based search, and also to store any large set of sub-table records that contains fields whose values are different for each main table record, such as multiple prices for different quantities, divisions, regions, or trading partners; cross-reference part numbers; and additional distributor/supplier/customer-specific information for different distributors, suppliers, or customers.

� All lookup tables in an SAP MDM repository are sub-tables, but not all sub-tables are used as lookup tables. There are a number of subtle differences among the different types of lookup tables.

� 1RWH��SAP recommends using the singular for lookup field names (“Manufacturer”) and the plural for table names (“Manufacturers”).


SAP AG 2006

+LHUDUFK\�DQG�7D[RQRP\�7DEOHV

� +LHUDUFK\$�KLHUDUFK\�WDEOH�LV�D�VXE�WDEOH�WKDW�RUJDQL]HV�LQIRUPDWLRQ�LQ�D�KLHUDUFK\��ZKHUH�HDFK�UHFRUG�LV�UHODWHG�WR�D�SDUHQW�UHFRUG�DQG�PD\�DOVR�EH�UHODWHG�WR�VLEOLQJ�UHFRUGV�DQG�RU�FKLOG�UHFRUGV��

� 7D[RQRP\$�WD[RQRP\�LV�WKH�FODVVLILFDWLRQ�VFKHPH�WKDW�GHILQHV�WKH�FDWHJRULHV�DQG�VXEFDWHJRULHV�WKDW�DSSO\�WR�D�FROOHFWLRQ�RI�REMHFWV��

�

� A hierarchy table organizes information in a hierarchy, where each record is related to a parent record (even if the only parent is the root) and may also be related to sibling records and/or child records. The main table in an MDM repository typically contains some fields whose data may be hierarchical in nature. For example, a 0DQXIDFWXUHU field may need to accommodate division and subdivision information for manufacturers. This hierarchical information is stored in a separate, hierarchy sub-table associated with the 0DQXIDFWXUHU lookup field in the main table.

� Most of the hierarchy tables used in an MDM repository contain lookup information for fields in the main table. Other hierarchy tables in MDM include taxonomy tables, the Masks table, and the Families table. MDM supports hierarchies with an unlimited number of parent/child levels.

� 1RWH� a hierarchy table is useful even when it is flat (that is, only leaf nodes below the root), because it stores the ordered sequence of sibling records, allowing you to override the unordered sequence of values in a flat table and instead put the values in a fixed order.

� A taxonomy is the classification scheme that defines the categories and subcategories that apply to a collection of records. Categorizing records enables you to isolate subsets of records for various organizing, searching, editing and publishing purposes. A taxonomy table in MDM stores a hierarchy of categories and subcategories and also supports attributes, which are sub-fields that apply to particular categories rather than to the entire collection of records. MDM supports multiple simultaneous taxonomies.


SAP AG 2006

,PDJH��6RXQG��9LGHR��3')��DQG�%LQDU\�2EMHFWV�7DEOHV

�(DFK�REMHFW�LV�VWRUHG�DV�D�UHFRUG�LQ�WKH�WDEOH�

� $OO�DUH�VLQJOH�WDEOHV� ,PDJHV��6WRUHV�LPDJH�ILOHV� ,PDJH�9DULDQWV��7KLV�VSHFLDO�

WDEOH�LV�XVHG�WR�GHILQH�WKH�VWUXFWXUH�DQG�IRUPDW�RI�HDFK�RI�WKH�YDULDQWV�IRU�HDFK�LPDJH�

� 3')V� �2EMHFW�WDEOH�VWRUHV�3')�ILOHV

�

Single tables: y ,PDJHV: Stores image files, where each image is stored as a record in the table. y ,PDJH�9DULDQWV: Used to define the structure and format of each of the variants for each image.

Each variant is a modified version derived from an original image; the original image is never modified. This table is managed in the MDM Console and is not visible in the MDM Data Manager.

y 6RXQGV: Stores sound files, where each sound file is stored as a record in the table. y 9LGHRV: Stores video files, where each video file is stored as a record in the table. y 3')V: Stores PDF files, where each PDF is stored as a record in the table. y %LQDU\�2EMHFWV: Stores other binary object files, where each binary object file is stored as a

record in the table.


SAP AG 2006

7H[W�%ORFNV��&RS\�%ORFNV��DQG�7H[W�+70/�7DEOHV

�(DFK�REMHFW�LV�VWRUHG�DV�D�UHFRUG�LQ�WKH�WDEOH�

� $OO�DUH�VLQJOH�WDEOHV� 7H[W�%ORFNV� �2EMHFW�WDEOH�

VWRUHV�EORFNV�RI�WH[W�� &RS\�%ORFNV� �7KLV�WDEOH�

UHIHUHQFHV�RWKHU�WDEOH¶V�DWWULEXWH�YDOXHV�

� 7H[W�+70/� �2EMHFW�WDEOH�VWRUHV�EORFNV�RI�WH[W�DQG�+70/�WDJV�IRU�ODWHU�LQWHUSUHWHG�DV�+70/�

�

� 7H[W�%ORFNV stores blocks of text, where each text block is stored as a record in the table. � &RS\�%ORFNV stores block of data that point to attribute values. Used for variant data for specific

groups. � 7H[W�+70/V stores blocks of text interpreted as HTML, where each text block is stored as a record

in the table.


SAP AG 2006

6SHFLDO�7DEOHV

� $OO�DUH�VLQJOH�WDEOHV� )DPLOLHV��7KLV�WDEOH�LV�XVHG�WR�

IXUWKHU�SDUWLWLRQ�WKH�SURGXFWV�LQ�HDFK�FDWHJRU\�LQWR�VPDOOHU�JURXSV�EDVHG�XSRQ�WKH�YDOXHV�RI�RWKHU�ILHOGV�DQG�RU�DWWULEXWHV��

� 0DVNV��$�PDVN�LV�D�VQDSVKRW�RI�WKH�VHW�RI�UHFRUGV�WKDW�DUH�LQFOXGHG�LQ�WKH�PDVN��

� 5HODWLRQVKLSV��7KLV�WDEOH�LV�XVHG�WR�GHILQH�HDFK�RI�WKH�GLIIHUHQW�SURGXFW�OHYHO�UHODWLRQVKLSV��

� :RUNIORZV��7KLV�WDEOH�VWRUHV�DOO�FUHDWHG�ZRUNIORZV�

�


SAP AG 2006

)LHOG�7\SHV


�


SAP AG 2006

� (YHU\�WDEOH�PXVW�KDYH�DW�OHDVW�RQH�'LVSOD\�)LHOG�� (DFK�ILHOG�

QDPH�PXVW�EH�XQLTXH�ZLWKLQ�D�WDEOH�

� ,WHPV�FDQ�EH�UH�RUGHUHG�

)LHOG�7\SHV

�

� A Display Field for a table is a field whose value is used as: y The corresponding lookup field value for each record y The node name for the record in hierarchy trees y The name of the record in the Product Relationships dialog box

� When a table has multiple Display Fields, the value that is used for each record is the value combination among the Display Fields with each pair of values separated by a comma.

� The Display Field can be changed, but a new field must be assigned a Display Field before removing the previous field’s Display Field property.


SAP AG 2006

)LHOG�'HWDLOV

3URSHUWLHV�ZLOO�YDU\�GHSHQGLQJ�RQ�WKH�7\SH�VHOHFWHG�

�

� A traditional SQL DBMS has a standard set of relatively simple data types (such as text, integer, and real) that allow you store a VLQJOH�element of XQVWUXFWXUHG�data in each field. Beyond knowing how to accept input of and properly store each type of data, SQL has no real understanding of the internal structure of each data element.

� By contrast, an MDM repository supports a variety of compound and structured data types which, like the set of MDM table types, are specifically suited for managing information in a product repository.

� 1RWH: A 7H[W�1RUPDOL]HG field stores the actual text value, but uses the normalized value for sorting and searching. The normalized value is an upper-case version of the original with non-alphanumeric characters removed (including a-z, A-Z, and 0-9).

� 1RWH: A regular 7H[W field is faster than a 7H[W�/DUJH field; only use a 7H[W�/DUJH field if you are certain that some values will require over 4000 characters.


SAP AG 2006

� 1DPH��D�XQLTXH DQG�GHVFULSWLYH ILHOG QDPH� &RGH��D�XQLTXH ILHOG FRGH XVHG ZLWKLQ 0'0�$3,V WR�UHIHUHQFH REMHFW� 7\SH��'HILQHV WKH W\SH RI�ILHOG DQG�WKH DYDLODEOH SURSHUW\ GHWDLOV

� 5HTXLUHG��,V�WKH�ILHOG�YDOXH�UHTXLUHG��<HV�1R�"� :ULWDEOH 2QFH��'RHV�WKH�ILHOG�EHFRPH�UHDG�RQO\�DIWHU�WKH�ILUVW�VDYH��<HV�1R�"� 0DWUL[��:HE'\QSUR H[WHQGDELOLW\� 6RUW ,QGH[��DOORZV�D�ILHOG�WR�EH�VRUWDEOH LQ�WKH�5HFRUGV�PRGH�RI�WKH�0'0�'DWD�0DQDJHU�DQG�$3,V� .H\ZRUG��,QFOXGH�WKH�ILHOG�LQ�NH\ZRUG�LQGH[LQJ�VHDUFKHV��1RQH�1RUPDO�"� 'LVSOD\�)LHOG��7KH ILHOG LV GLVSOD\HG ZKHQUHIHUHQFLQJ WKLV WDEOH �<HV�1R�� 8QLTXH )LHOG��0XVW FRQWDLQ�D�XQLTXH�YDOXH�IRU�HDFK�UHFRUG��<HV�1R�� &DOFXODWHG��,I \HV��WKHQ HQWHU &DOFXODWLRQ� :LGWK��0D[LPXP�QXPEHU RI�FKDUDFWHUV� 6RUW 7\SH��&DVH�,QVHQVLWLYH��&DVH�6HQVLWLYH��RU�1XPHULF

([DPSOH RI�)LHOG 'HWDLO�IRU 7H[W

�

� Most objects within an MDM repository (e.g. tables and fields) have a &RGH property that is limited to the following characters: y A-Z y a-z y 0-9 y underscore

� 5HTXLUHG is only advisory and is used with validation expressions. � Even though a XQLTXH�ILHOG generally prevents more than one record from having the same value (or

value combination in the case of a unique field combination), multiple records are permitted to have the value NULL for the unique field. The reason for this is that while unique fields are used to distinguish between multiple records, a unique field with the value NULL means the record has not yet been fully defined and therefore should not conflict with other records that are also not yet fully defined.


SAP AG 2006

$GGLWLRQDO�,QIRUPDWLRQ

0DQ\�WDEOH�DQG�ILHOGV�SURSHUWLHV�FDQQRW�EH�FKDQJHG�DIWHU�FUHDWLRQ�� 7DEOH�W\SH� )LHOG�W\SH� 0XOWLOLQJXDO�RSWLRQ� /RRNXS�WDEOH� 0XOWL�9DOXHG

1XOO�YDOXHV�DUH�QRW�EODQN�YDOXHV�� 1XOO�LV�FRQVLGHUHG�ZKHQ�VHDUFKLQJ� ��LV�QRW�FRQVLGHUHG�QXOO

7KLQN�DERXW�\RXU�GDWD�PRGHOLQJ�EHIRUH�LPSOHPHQWLQJ�LW��

� The multilingual option will be discussed in detail in the Multilingual Support lesson.


SAP AG 2006

� :LWK�0'0��6$3�GHOLYHUV�WKH�FRQWHQW��UHSRVLWRULHV�SUHILOOHG�ZLWK�VFKHPD�LQIRUPDWLRQ��HPSW\�WDEOHV��UHODWHG�WR�DQ�6$3�5��REMHFW�PRGHO�� $UWLFOHV� %XVLQHVV�3DUWQHU� &XVWRPHU� (PSOR\HH�� 0DWHULDO� 3URGXFW� 9HQGRU

� 7KLV�HQVXUHV�DQ�HDV\��EXLOW�LQ�FRQQHFWLRQ�WR�6$3�5��DQG�P\6$3 %XVLQHVV�6XLWH�V\VWHPV�

3UHGHILQHG�5HSRVLWRU\�&RQWHQW

�

� With SAP NetWeaver MDM 5.5 and above, data models are part of the standard delivery, meaning that these object types can be used out of the box. Also included in the download of the predefined repositories are tables, fields, and remote systems, along with import and export maps, which may be edited.

� This ensures an easy, built-in connection to SAP R/3 and mySAP Business Suite systems. � $UWLFOHV is the newest repository. It incorporates the Matrix application, which uses Web Dynpro to

create product variants without creating a new product.


SAP AG 2006

$GPLQ�)ROGHU


�

� Also known as system tables. Additional Admin components are discussed in the Security lesson.


SAP AG 2006

5HPRWH�6\VWHPV

5HPRWH�V\VWHPV describe the name and the process designed to exchange data with another system.

This information will be important for further communication.

Remote systems information is part of NH\�PDSSLQJ.

� :KDW�LV�NH\�PDSSLQJ"� :KDW�YDOXH�GRHV�LW�DGG"� :KHUH�LV�LW�XVHG"� :KHUH�LV�NH\�PDSSLQJ�FRQILJXUHG"

�

� The Remote Systems table is a system table automatically created under the Admin node. � Each repository contains a default remote system (MDM), which is used from all MDM Data

Manager applications except the MDM Import Manager. � A key in MDM is a unique, remote-system-specific, and object-type-specific identifier. Different

remote systems have their own separate collection of keys. � Identification of the remote system in the MDM Import Manager and in the MDM Syndicator

triggers deployment of the correct key mapping during inbound and outbound processes. When starting the Import Manager, you must select the specific remote system for the data transfer. In the Syndicator, you have to select the remote system either during creation or execution of a syndication.

� MDM can import data from remote systems and create or update master data objects using that data. A remote system’s objects are mapped to master data objects within MDM using key mapping. A key mapping maintains the relationship between the remote system’s identifier (or key) for an object and the corresponding master data object in MDM.

� At any time, master data objects can be distributed to all known remote systems through a process known as syndication. This involves determining which master data objects need to be distributed and converting them into a form that the remote system can understand. This is done using the key mappings.

� Different remote systems can have their own separate collections of keys. � 1RWH: Key mappings are subject to the requirement that two different objects of the same type from

the same remote system cannot have the same key value.


SAP AG 2006

.H\�0DSSLQJ��6HWXS

� 5HPRWH�V\VWHPV�PXVW�EH�GHILQHG�LQ�WKH�FRQVROH

� ,Q�RUGHU�WR�XVH�5HPRWH�V\VWHPV��WKH�WDEOH�PXVW�KDYH�.H\�0DSSLQJ�VHW�WR�<HV

� $FFHVV�WKURXJK�WKH�'DWD�0DQDJHU

� )RU�HDFK�UHFRUG��RQH�RU�PDQ\�UHPRWH�V\VWHPV�DQG�WKH�UHPRWH�NH\V�FDQ�EH�VWRUHG

�

� Remote system objects are mapped to master data objects within MDM using key mapping. A key mapping maintains the relationship between the remote system identifier (or key) for an object and the corresponding master data object in MDM. A key in MDM is a unique, remote-system-specific, and object-type-specific identifier. Different remote systems can have their own separate collections of keys. Within a remote system, each type or collection of objects can have its own separate collection of keys as well. Key mappings are subject to the requirement that two different objects of the same type from the same remote system cannot have the same key value.

� Remote system objects of a particular type can map only to MDM objects of a particular type. A key can map to only one MDM object. However, an MDM object may map to multiple keys from the same remote system. When an MDM object maps to multiple keys from the same remote system, one of the keys is marked as the default key. The default key is the one that is used when syndicating a reference to the mapped MDM object.

� MDM uses the remote systems defined in the Remote Systems table within the MDM Console to store and maintain key mapping information for each record or text attribute. The only time the key mapping is viewed is by right-clicking a single record and selecting (GLW�.H\�0DSSLQJ.

� Remote systems are created under the Admin node. A remote system consists of two key properties. y Name: The display name has to be unique y Type: Determines whether the remote system can supply data for import, receive data from

syndication, or both.


SAP AG 2006

0'0�&RQVROH��([HUFLVH

*HQHUDO�JXLGHOLQHV�IRU�GHVLJQLQJ�DQ�0'0�UHSRVLWRU\� /LVW�DOO�WKH�ILHOGV�WR�EH�LQFOXGHG�LQ�WKH�UHSRVLWRU\�� 'HFLGH�ZKDW�ILHOG�W\SH�VKRXOG�DSSO\�WR�HDFK�ILHOG��,I�D�SDUWLFXODU�ILHOG�

VKRXOG�EH�D�ORRNXS�ILHOG��GHFLGH�LI�WKH�ORRNXS�WDEOH�VKRXOG�EH�IODW��KLHUDUFKLFDO��WD[RQRP\��RU�TXDOLILHG�

� )RU�HDFK�ILHOG�� GHWHUPLQH�KRZ�WKH�GDWD�VKRXOG�EH�UHSUHVHQWHG�DQG�ZKDW�GDWD�W\SH�VKRXOG�EH�XVHG��

� KRZ�WR�VWRUH�WKH�GDWD�DV�QXPHULF�YDOXHV��LQWHJHUV�RU�UHDO�QXPEHUV��FXUUHQF\��WH[W��LPDJHV��DQG�VR�RQ��

� ZKHWKHU�WKH�ILHOG�VKRXOG�EH�VLQJOH�YDOXHG�RU�PXOWL�YDOXHG��DQG�� ZKHWKHU�LW�VKRXOG�EH�D�ORRNXS�ILHOG�

� %HJLQ�H[HUFLVH�E\�ILUVW�UHDGLQJ�WKH�UHTXLUHPHQWV�GHILQHG�IRU�WKLV�H[HUFLVH�

�

� Data modeling of your repository is an important element and should involve all business groups who will be utilizing the data.

� Each lookup field in the main table becomes a searchable dimension of the repository and automatically appears in the SAP MDM Data Manager as a search tab in the Search Parameters pane in Record mode.

� Each nested lookup field in a lookup table also becomes a searchable dimension of the repository, appears in the Data Manager as a search tab when the current table is the lookup table and also appears within the search tab for the main table lookup field when the current table is the main table for multilevel search-within-a-search.


SAP AG 2006

6XPPDU\


�


SAP AG 2006

$UFKLYH�DQG�8QDUFKLYH�D�5HSRVLWRU\

z $UFKLYH�5HSRVLWRU\�± LV�D�PHFKDQLVP�WKDW�DOORZV�\RX�WR�EDFNXS�\RXU�0'0�UHSRVLWRU\�LQ�D�'%06�ZKLFK�LV�SODWIRUP�LQGHSHQGHQW�IRUPDW�

z 8QDUFKLYH 5HSRVLWRU\�± DOORZV�\RX�WR�UHVWRUH�DQ�0'0�UHSRVLWRU\�IURP�DQ�0'0�DUFKLYH�

z ([SRUW�5HSRVLWRU\�6FKHPD�± VDYHV�WKH�WDEOH�VWUXFWXUH�RI�WKH�UHSRVLWRU\�DV�DQ�;0/�ILOH��

z ,PSRUW�5HSRVLWRU\�6FKHPD�± ,PSRUWV�D�VFKHPD�DQG�PHUJHV�LW�LQWR�WKH�VHOHFWHG�0'0�UHSRVLWRU\�

�


SAP AG 2006

0'0�&RQVROH��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� ([SODLQ�WKH�GLIIHUHQW�WDEOH�W\SHV�LQ�0'0�&RQVROH� ([SODLQ�WKH�XVDJH�RI�WKH�YDULRXV�WDEOHV�DQG�ILHOGV

�


0'0�([HUFLVHV�

8QLW�� &UHDWH�D�5HSRVLWRU\�7RSLF��0'0�&RQVROH�


• ([SODLQ�WKH�GLIIHUHQW�WDEOH�W\SHV�LQ�0'0�&RQVROH�• ([SODLQ�WKH�XVDJH�RI�WKH�YDULRXV�WDEOHV�DQG�ILHOGV • &UHDWH�D�5HSRVLWRU\�

3XUSRVH�This script walks through the process of creating a repository from scratch.

7ULJJHU�The MDM tool comes empty. Repositories are available that can be unarchived and used for demonstration and training purposes. However, if you are creating a customer demo or implementing a new repository for a customer project, then you may find that an existing repository does not meet your requirements. In this case you would follow this process to create your own repository.

+LQW��For most exercises, you will find an archive file of the respository in the Archive Folder where the repository has been completed up to and including that exercise. If you are not able to complete an exercise, then unarchive the completed archive and you will be set for the next exercise.

3-1 'HVLJQ�RI�D�5HSRVLWRU\�It takes time and input from many groups to properly design an appropriate repository. In this course, as you learn more about SAP MDM, you will continually add to your repository.

3-1-1 Your customer is a distributor of household appliances and assorted supplies. They would like to store their product details in MDM. They will supply you with product details from both their New York and London offices.

3-1-2 You will store the following product information for each record: Product ID, name, long description, purchased from country, manufactured in country, sales price, is the item electric, and the weight.

3-1-3 You will also create 3 lookup tables for quicker and more reliable data entry: Business Partners, Countries, and Divisions

3-1-4 You will begin with SAP’ s default repository which contains only a main table and the required standard tables which all repositories must contain whether they are used or not.


3-2 &UHDWH�D�5HSRVLWRU\

Create a new empty repository.

3-2-1 Right-click on the server name and select context menu item “ Create Repository”

3-2-2 Logon to the DBMS Server (Note--your user login is 'dba' with password

training).


3-2-3 After logging on to the DMBS server, the repository name and port fields will be�available for entry. Fill in the following fields.

)LHOG�1DPH� 'HVFULSWLRQ�Repository

name <RXU/HWWHUB&DVHB6WXG\�

Port Number

Available Port Number – �EHWZHHQ��DQG�� Please use �� for A, �� for B, �� for C, �� for D, �� for E, �� for F, �� for G, �� for H, �� for I and �� for J

.Your repository will initially be locked. To access the repository, right click on it in the Console Hierarchy and from the context menu, choose the option Connect to Repository with user=Admin and pw=blank.

Note the repository name is text and reference only – it can be any text you choose as long as it is unique.

3-2-4 Then click )LQLVK�

3-3 9LHZ�1HZ�5HSRVLWRU\�Expand the Console Hierarchy to view the contents of your new repository ‘YourLetter_Case Study’ . There is a default main table ‘Products’ and empty tables.


3-4 &UHDWH�'LYLVLRQV�7DEOH In the MDM Console you will be fine tuning your repository structure.

Notice how the right hand side of the screen is divided into two sections. The top section lists all of the tables that belong to the repository. The lower portion is the work area for maintaining details on the table that is currently selected (highlighted in the upper section).

3-4-1 In the Console Hierarchy pane highlight your repository, right-click the “ Tables” work area and select Add Tables or from the main menu select “ Tables Æ Add”

3-4-2 The first table will be a Lookup [Flat] table for your Divisions.

3-4-3 Type in the name of the table in the “ Name” field type Divisions.

Click on Type next to determine the table type.

Pick from the drop down menu “ Flat” as the 7\SH��Set�.H\�0DSSLQJ�= Yes

Shift+Enter to save the table. Notice the table information is updated in the upper section of the screen.


3-5 &UHDWH�2WKHU�7DEOHV��

Countries and Business Partners tables should be created and Key Mapping should be turned on for these tables. Repeat the process in step 4.1 to 4.3 to create the tables Countries and Business Partners.

After this step you should have the following tables present.

Table Name Table Type Key Mapping

• Countries • Flat • Yes

• Business Partners • Flat • Yes

Result:


3-6 $GG�)LHOGV�Next you will add fields to your countries tables. You have to highlight the appropriate table in the left hand Console Hierarchy pane and the two right hand panes will change to the detailed view of the highlighted table. The logic will remain. The upper pane shows all the table fields and the lower pane shows the details of the field highlighted.

3-6-1 Select the &RXQWULHV table and right mouse click on the Fields pane.

3-6-2 Enter the new field name in the appropriate space within the Field Detail section of the screen.

3-6-3 See the image to the right for details on all the property values.

3-6-4 Click Shift+Enter to save the field.


3-7 $GG�)LHOGV�WR�WKH�0DLQ�7DEOH Select Table 3URGXFWV�and add the following fields.

3-7-1 Select the Products table and right mouse click on the Fields pane.

3-7-2 Enter the new field Name, 'LYLVLRQ, in the appropriate space within the Field Detail section.

3-7-3 Select Type = Lookup [Flat]

3-7-4 Since this is a Lookup field, you must enter the table you want the field to lookup.

Select the table ‘Divisions’ as the Lookup Table.

3-7-5 Click Shift+Enter to save the field.

�


3-7-6 Continue by adding the following fields:

Consider adding the fol Consider adding the following fields: Date modified (Time Stamp field type) and User (User Stamp field type) who last modified the record.

3-7-7 The Fields will be displayed in the MDM Data Manager in the order of appearance in the console.

7R�UHRUGHU�)LHOGV�Î right mouse-click in the fields table and select�5HRUGHU«�

)LHOG�1DPH� &RGH� )LHOG�7\SH� ([WUD�)LHOG�9DOXHV�Purchase Country Purchase_Country Lookup [Flat] Lookup table = Countries

Multi-Valued = No

Manufactured Country Manufactured_

Country

Lookup [Flat] Lookup table = Countries Multi-Valued = Yes

Sales Price Sales_Price Currency Symbol = $ Decimal places = 2 Show Fractions = No

Long Description Long_Description Text Large

Product ID ProductID Text Display Field = Yes Unique Field = Yes Width = 10

Electric Electric Boolean Display Field = Yes True Value = Y False Value = N

Weight Weight Real Decimal places = 3 Show Fractions = No


3-7-8 Highlight the field and drag it with the mouse to a new location in the list.

Move Product ID to the top of the list.

3-8 &UHDWH�5HPRWH�6\VWHP

You will now create a remote system ID which will identify the source of your records when importing them into your repository

3-8-1 Expand the Admin folder and select Remote Systems.

3-8-2 Right-click on the Remote Systems and select Add Remote System.


3-8-3 Enter the following information for your NewYork remote system:

3-8-4 Then Shift+Enter. The new remote system is now saved.

3-8-5 Create a second remote system called London as Inbound/Outbound.

3-8-6 Lastly, we want to utilize this remote system when importing data, so select the Products table from the list of Tables and change Key Mapping to Yes.

3-8-7 Shift+Enter to save your change.


3-9 /RDG�5HSRVLWRU\

3-9-1 Right mouse click on “ YourLetter_Case_Study” select Load Repository Æ Immediate as there is no need to load With Indexes as you have no data.

Note: if you receive an error on loading your repository stating that port 2000 is occupied, the server created your repository on port 2000 and another user is already using the port. In this case, in the Console, select the MDM Server localhost and find your repository in the list of repositories and change the port from 2000 to the correct port.

3-9-2 Start the SAP MDM Data Manager by double clicking on the icon on your

desktop, select Localhost using the

3-9-3 Select YourLetter_Case_ repository

9-3-1 User:�$GPLQ�9-3-2 OK


3-10 &KHFN�<RXU�5HVXOWV You have created a repository from scratch and can now log on to the Data Manager and see the structure.

�

Resume: In this Scenario you have created tables and fields in your repository. These tables and fields can now either be populated using the import tool Import Manager or manually on the Data Manager screen you see


SAP AG 2006

,PSRUW�0DQDJHU




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�


SAP AG 2006

&RQWHQWV�� 0'0�,PSRUW�0DQDJHU

� %DVLF�LPSRUW IXQFWLRQDOLW\� 6WHSV UHTXLUHG WR�SUHIRUP DQ�LPSRUW RI�GDWD

0'0�,PSRUW�0DQDJHU

�


SAP AG 2006

0'0�,PSRUW�0DQDJHU��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� ([SODLQ�WKH�YDOXH�RI�0'0�,PSRUW�0DQDJHU�� /LVW�WKH�VL[�VWHSV�IRU�GDWD�LPSRUW�ZLWK�0'0�

,PSRUW�0DQDJHU� ([SODLQ�WKH�GHWDLOHG�IXQFWLRQV�IRU�LPSRUWLQJ�

DQG�PDSSLQJ�GDWD�IURP�YDULRXV�VRXUFHV

�


SAP AG 2006

0'0�,PSRUW�0DQDJHU��%XVLQHVV�6FHQDULR

� ,Q�RUGHU�WR�ORDG�PDVWHU�GDWD�LQWR�0'0�\RX�QHHG�WR�XVH�WKH�,PSRUW�0DQDJHU�DQG�XQGHUVWDQG�LWV�IXQFWLRQDOLW\�

� $V�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RX�ZDQW�WR�NQRZ�ZKDW�RSWLRQV�DUH�DYDLODEOH�LQ�WKH�,PSRUW�0DQDJHU�IRU�WKH�WUDQVIRUPDWLRQ�RI�GDWD�DV�LW�LV�ORDGHG�LQWR�\RXU�UHSRVLWRULHV��

� <RX�DUH�DOVR�LQWHUHVWHG�LQ�KRZ�WR�DXWRPDWH�WKH�LPSRUW�SURFHVV��

�


SAP AG 2006

,PSRUW�0DQDJHU�2YHUYLHZ6L[�6WHSV�IRU�'DWD�,PSRUW6XPPDU\

,PSRUW�0DQDJHU�2YHUYLHZ

�


SAP AG 2006

*HQHUDO�&KDOOHQJHV�RI�0DQDJLQJ�'DWD

%XVLQHVV�&KDOOHQJHV�� 7LPH�FRQVXPLQJ� 5HVRXUFH�LQWHQVLYH� ([SHQVLYH

7HFKQLFDO�&KDOOHQJHV�� 5DZ�DQG�RU�GLVSDUDWH�GDWD� 1RUPDOL]DWLRQ� ,QFRPSDWLEOH�GDWD�IRUPDWV� 'LIIHUHQW�FODVVLILFDWLRQ�VFKHPDV� $JJUHJDWLRQ�DJJUDYDWLRQ� +XQGUHGV�RI�VRXUFHV�DQG�

GHVWLQDWLRQV

�


SAP AG 2006

5HDVRQV�WR�8VH�6$3�0'0�,PSRUW�0DQDJHU

� 'DWD�FDQ�EH�LPSRUWHG WR�WKH�VDPH�UHSRVLWRU\�IURP�PXOWLSOH�VRXUFHV�

� )LHOG�RULHQWDWHG�SURFHVVLQJ UDWKHU�WKDQ�UHFRUG�E\�UHFRUG�SURFHVVLQJ�

� 'LVWLQFW�YDOXH OLVWV�� $XWRPDWLF�GDWD�W\SH FRQYHUVLRQ� 9DOXH FRQYHUVLRQV�GXULQJ�LPSRUW� ([WHQGHG�WDEOH�W\SHV OLNH�KLHUDUFKLHV��WD[RQRP\��DQG�PDVNV� 6SHFLILF�ILHOG�W\SHV WKDW�FDQ�KDQGOH�SGI��LPDJHV��ORQJ�WH[W��

DQG�VRXQG� .H\�PDSSLQJ EDVHG�RQ�WKH�GDWD�VRXUFH� &DSDELOLW\�WR�VRUW DQG�UHVWUXFWXUH GDWD� &RQVLVWHQW�YLHZ RI�VRXUFH�GDWD

�


SAP AG 2006

3DUDPHWULF�,PSRUW

(IILFLHQF\�RI�SDUDPHWULF�LPSRUW�YHUVXV�SDUDPHWULF�VHDUFK�� 3DUDPHWULF�VHDUFK

/LVWV�WKH�FRPSOHWH�VHW�RI�GLVWLQFW�YDOXHV�IRU�HDFK�ILHOG�RU�DWWULEXWH�LQ�D�UHSRVLWRU\��6HOHFWLQJ�D�YDOXH�GXULQJ�D�GULOOGRZQ�VHDUFK�VHOHFWV�DOO�RI�WKH�XQGHUO\LQJ�UHFRUGV�FRQWDLQLQJ�WKDW�YDOXH�

� 3DUDPHWULF�LPSRUW/LVWV�WKH�FRPSOHWH�VHW�RI�GLVWLQFW�YDOXHV�IRU�HDFK�ILHOG�LQ�WKH�VRXUFH�GDWD��&KDQJLQJ�D�YDOXH�DV�SDUW�RI�WKH�LPSRUW��E\�PDSSLQJ�RU�FRQYHUWLQJ�LW��FKDQJHV�LW�LQ�DOO�RI�WKH�XQGHUO\LQJ�UHFRUGV�FRQWDLQLQJ�WKDW�YDOXH�

�

� Patent-pending SDUDPHWULF�LPSRUW technology � ([DPSOH – If the imported data has:

y 5000 input country records y Two unique countries in the 5000 rows

� The result will be: y Record-at-a-time processes the countries 5000 times y Field-at-a-time with distinct values process the countries twice

� Processing gain in parametric import: 4098 fewer transformations of country!


SAP AG 2006

,PSRUW0DQDJHU,PSRUW0DQDJHU

0'0�,PSRUW�0DQDJHU�8VHU�,QWHUIDFH

'DWD

� 5HFRUG�XSORDG� 5HFRUG�PDWFK� 'DWD�PDSSLQJ� 9DOXH�FRQYHUVLRQV� 6DYLQJ�RI�PDSV

0'06HUYHU0'06HUYHU

5HSRVLWRU\

7DEOHV9LHZV)LOHV

7DEOHV9LHZV)LOHV

�

� The MDM Import Manager allows the import of data into an MDM repository from any tabular or XML format with a consistent user interface and identical functional capabilities, regardless of the source file format.


SAP AG 2006

'DWD�,PSRUW

6XJJHVWLRQV� %DG�GDWD�LQ�UHVXOWV�LQ�EDG�GDWD�RXW�� /LPLW�WKH�QXPEHU�RI�UHFRUGV�WR��RU�OHVV�IRU�0'0�,PSRUW�

0DQDJHU� 9DOXH�PDSSLQJ�DQG�FRQYHUVLRQ�PXVW�EH�FRPSOHWHG� )RU�HYHU\�PDSSHG�ILHOG��HDFK�RI�LWV�YDOXHV�PXVW�EH�SURSHUO\�

FRQYHUWHG�WR�WKH�GHVWLQDWLRQ�GDWD�W\SH�� $OWHUQDWHO\��HDFK�YDOXH�PXVW�EH�PDSSHG�WR�DQ�H[LVWLQJ�RU�

QHZO\�DGGHG�GHVWLQDWLRQ�GDWD�YDOXH�5HFRUG�PDWFKLQJ� 2QH�RU�PRUH�XQLTXH�ILHOGV�PXVW�EH�LGHQWLILHG�� 7KH�0'0�,PSRUW�0DQDJHU�ZLOO�GHWHUPLQH�ZKHWKHU�WR�FUHDWH�

QHZ�UHFRUGV�RU�XSGDWH�DQG�UHSODFH�H[LVWLQJ�GHVWLQDWLRQ�UHFRUGV�

�

* The limitations of the MDM Import Manager do not apply to the MDM Server.


SAP AG 2006

6L[�6WHSV�IRU�'DWD�,PSRUW


�


SAP AG 2006

6L[�5HTXLUHG�6WHSV�IRU�,PSRUW�0DQDJHU

�� &RQQHFW�WR�UHSRVLWRU\�� &RQQHFW�WR�VRXUFH�� 6HOHFW�VRXUFH�DQG�GHVWLQDWLRQ�WDEOHV�� 0DS�ILHOGV�YDOXHV�� 0DWFK�UHFRUGV�� ,PSRUW

�

Six steps of the MDM Import Manager: � Connect to existing repository where the imported data will reside. � Connect to the source data file or database to establish programmatic access from the MDM Import

Manager to the source schemas and data. � Select the source and destination tables where the imported data will be transferred from and to. � Map fields to identify the destination field for each source field and also the type of mapping and

conversion required for the underlying data values. � Match records to specify the key fields for identifying existing records that match the source

records and whether new records should be created and existing records should be updated or replaced.

� Import records to transfer data from the file into the MDM Repository.


SAP AG 2006

� 6HOHFW�WKH�WDUJHW�5HSRVLWRU\� &OLFN�$GG�(GLW��WR�FKDQJH�

UHSRVLWRU\�VHUYHU�DQG�VHOHFW�D�UHSRVLWRU\��E\�QDPH�

� (QWHU�8VHU�QDPH� (QWHU�3DVVZRUG

� &KRRVH�1H[W�ZKHQ�GHVLUHG�UHSRVLWRU\�LV�VHOHFWHG�

��&RQQHFW�WR�5HSRVLWRU\

�

� The MDM Server must be running and the selected repository must be loaded before choosing 1H[W.


SAP AG 2006

��&RQQHFW�WR�6RXUFH

7KH�IROORZLQJ�GDWDEDVH�W\SHV�DUH�DYDLODEOH�DV�VRXUFHV�

5HDG�RQO\�RSWLRQ�� ,PSDFWV�KRZ�FHUWDLQ�,PSRUW�

0DQDJHU�RSHUDWLRQV�DUH�SURFHVVHG

� ,PSDFWV�ZKHWKHU�RU�QRW�,PSRUW�0DQDJHU�FDQ�FUHDWH�VXSSRUWLQJ�WDEOHV�LQ�WKH�VRXUFH�UHSRVLWRU\�ZKHQ�QHHGHG�RU�LI�LW�LV�IRUFHG�WR�LQ�PHPRU\�VZDSILOH RSHUDWLRQV�RQ�LWV�VHUYHU�

�

Connect to Source 7\SH�� Access, Excel and XML: “ File name” becomes active � ODBC: “ DSN” (Data Source Name), “ User” , “ Password” becomes active � SQL Server and Oracle: “ DBMS server” , “ Database” (name), “ User” , “ Password” become active

y For RDBMS, the “ Database server” is the TCP/IP hostname or address of the Database Server where you will source data *from*.

y “ Database” is the name of the logical database within the RDBMS which you will be accessing for a list of table/view names.

� The Read-only option is enabled only for source types that can be updated (Access, Oracle, SQL

Server, and XML). It is GLVDEOHG DQG�FKHFNHG for those that cannot be updated (Excel and ODBC).


SAP AG 2006

��6HOHFW�&XUUHQW�7DEOHV

6RXUFH 'HVWLQDWLRQ

<RX�PXVW�VHOHFW�D�FXUUHQW�VRXUFH�WDEOH�DQG�D�FXUUHQW�GHVWLQDWLRQ WDEOH�EHIRUH�\RX�FDQ�SHUIRUP�PRVW�RI�WKH�0'0�,PSRUW�0DQDJHU�RSHUDWLRQV�

7KH�0'0�,PSRUW�0DQDJHU�LPSRUWV�UHFRUGV�� )URP WKH�FXUUHQW�VRXUFH�WDEOH��OHIW GURSGRZQ�� ,QWR WKH�FXUUHQW�GHVWLQDWLRQ�WDEOH��ULJKW GURSGRZQ�

�


SAP AG 2006

��5HFRUG�%URZVLQJ�2SWLRQV

6RUW�$6&

6RUW�'(6&

� 7KH�0'0�,PSRUW�0DQDJHU�DOORZV�\RX�WR�EURZVH�DQG�EHFRPH�IDPLOLDU�ZLWK�VRXUFH�GDWD�LQ�VHYHUDO�GLIIHUHQW�ZD\V�

� 8VH�WKH�6RXUFH�3UHYLHZ�WDE�WR�EURZVH�DOO�RI�WKH�UHFRUGV�DQG�ILHOGV�RI�HDFK�WDEOH�LQ�D�WUDGLWLRQDO�URZ�FROXPQ�JULG�

�


SAP AG 2006

��)LHOG�0DSSLQJ

0'0�,PSRUW�0DQDJHU�XVHV�WKH�WRS�SDLU�RI�ILHOG�PDSSLQJ�JULGV�WR�GLVSOD\�

� 7KH�VHW�RI�VRXUFH�ILHOGV�IRU�WKH�³FXUUHQW´�VRXUFH�WDEOH� 7KH�VHW�RI�GHVWLQDWLRQ�ILHOGV��QHVWHG�GLVSOD\�ILHOGV��DWWULEXWHV��DQG�

TXDOLILHUV�RI�WKH�FXUUHQW�GHVWLQDWLRQ�WDEOH�DV�D�OLVW�LQ�WKH�GHVWLQDWLRQ�ILHOGV�JULG

�

� The )LHOG�PDSSLQJ grid performs both field-level mapping and value-level operations as follows: y Field level

For each source field or field combination whose data values you want to import, you can use the top pair of field mapping grids to map the field to the corresponding destination field.

y Value level For each mapped source field, you can use the bottom pair grids to map, convert, or create measurements from the underlying field values, dependent upon the mapped destination field and data type.

� MDM Import Manager takes basic field mapping capability and extends it with a powerful value mapping and conversion capability.


SAP AG 2006

7KH�ILUVW�WZR�FROXPQV�LQ�WKH�GHVWLQDWLRQ�ILHOG�GLVSOD\�DUH�RI�SDUWLFXODU�LQWHUHVW�

0DSSHG��:KHWKHU�D�VRXUFH�ILHOG�LV�PDSSHG�WR�WKH�GHVWLQDWLRQ�ILHOG�)�'�4�$��7KH�ILHOG�W\SH

� )��6WDQGDUG�GHVWLQDWLRQ�ILHOG� '��'LVSOD\�ILHOG�RI�D�ORRNXS�ZLWK�PXOWLSOH�GLVSOD\�ILHOGV� 4��4XDOLILHU� $��$WWULEXWH

��'HVWLQDWLRQ�)LHOG�'HWDLOV

�

� Each column can be sorted. In the above image, the fields are listed by name. Typing the letter “ s“ will move the selection to the first name that starts with s.


SAP AG 2006

��)LHOG�0DSSLQJ��$XWRPDS

2XWFRPH�

<RX�FDQ�DOVR�VHDUFK�IRU�PDWFKHV�RQH�ILHOG�DW�D�WLPH��ULJKW�FOLFN�RQ�WKH�VRXUFH�ILHOG�DQG�VHOHFW�)LQG�1H[W�0DWFKLQJ�'HVWLQDWLRQ�)LHOG�

�

� If automap is used, each mapped field should be verified to make sure that the correct source data is mapped to the correct destination.


SAP AG 2006

��)LHOG�$XWRPDS�&RQILJXUDWLRQV

'HIDXOW�DXWRPDS ILHOG�QDPH�PDWFKLQJ��

� 3HUIRUPLQJ�D�³FRQWDLQV´FRPSDULVRQ�DJDLQVW�WKH�GHVWLQDWLRQ�ILHOG�QDPH

� 1RUPDOL]HV��UHPRYHV�SXQFWXDWLRQ�FKDUDFWHUV�DQG�VSDFHV��ERWK�WKH�VRXUFH�DQG�GHVWLQDWLRQ�ILHOG�QDPHV�EHIRUH�SHUIRUPLQJ�WKH�FRPSDULVRQ

&RQILJXUDWLRQ�RSWLRQV�FRQWURO�KRZ�WKH�PDWFKHV�DUH�PDGH��&RQILJXUDWLRQ�Æ 2SWLRQV�Æ )LQG�PDWFKLQJ�ILHOG�

�


SAP AG 2006

��0DQXDO�)LHOG�0DSSLQJ

1RWH�WKDW�VRXUFH�'HVFULSWLRQ GLG�QRW�DXWRPDS GHVWLQDWLRQ�/RQJ�'HVFULSWLRQ�+LJKOLJKW�ERWK�DQG�FKRRVH�0DS�

2XWFRPH�

�


SAP AG 2006

��9DOXH�0DSSLQJ

9DOXH�OHYHO�PDSSLQJ�RI�VRXUFH�YDOXHV�IRUFHV�D�XVHU�WR�QRUPDOL]H�VRXUFH�GDWD��LPSOLFLWO\�GHILQLQJ�D�SUHFLVH�VHW�RI�WUDQVIRUPDWLRQUXOHV��ZKLFK�� (OLPLQDWHV�GLIIHUHQFHV�EHWZHHQ�VRXUFH�DQG�GHVWLQDWLRQ�YDOXHV� &ROODSVHV�PXOWLSOH�VRXUFH�YDOXH�YDULDWLRQV�LQWR�D�VLQJOH�GHVWLQDWLRQ�YDOXH

� $OORZV�IRU�SURSHU�PDSSLQJ�RI�PXOWLSOH�GHOLPLWHG�VRXUFH�YDOXHV�LQWR�D�PXOWL�YDOXHG�0'0�ILHOG

� 0DNHV�LV�LW�HDV\�WR�H[SOLFLWO\�DGG�QHZ�YDOXHV�WR�WKH�VHW�RI�GHVWLQDWLRQ�GRPDLQ�YDOXHV

$OO�PDSSHG�ILHOGV�RI�GDWD�W\SHV�WKDW�UHTXLUH�YDOXH�PDSSLQJV�PXVWKDYH�WKHLU�YDOXHV�PDSSHG�

�

� For each field, the MDM Import Manager collapses the set of all values down to the set of distinct values.

� Generally, the number of values will usually be dramatically smaller than the total number of records, often by several orders of magnitude.


SAP AG 2006

��9DOXH�0DSSLQJ�5HTXLUHPHQWV

%DVHG�XSRQ�WKH�FXUUHQW�WDEOH�DQG�WKH�W\SH�RI�WKH�PDSSHG�GHVWLQDWLRQ�ILHOG��WKH�0DS FKHFNER[�LQGLFDWHV�ZKHWKHU�RU�QRW�WKH�FXUUHQW�PDSSHG�VRXUFH�ILHOG�UHTXLUHV�YDOXH�PDSSLQJ��,I�FKHFNHG��\RX�PXVW�PDS�VRXUFH�WR�GHVWLQDWLRQ�YDOXHV��

7KH�0DS FKHFNER[�LV�� 'LVDEOHG�DQG�DXWRPDWLFDOO\�FKHFNHG�ZKHQ�

YDOXH�PDSSLQJ�LV�UHTXLUHG� 'LVDEOHG�DQG�DXWRPDWLFDOO\�XQFKHFNHG�

ZKHQ�YDOXH�PDSSLQJ�LV�QHLWKHU�UHTXLUHG�QRU�SHUPLWWHG

� (QDEOHG�IRU�\RX�WR�FKHFN�PDQXDOO\�ZKHQ�YDOXH�PDSSLQJ�LV�RSWLRQDO��

�

� Value mapping is RSWLRQDO�to fixed-width text fields that are: (1) promoted lookup table display fields when the current table is the main table and the lookup table has multiple display fields; and (2) actual display fields when the current table is the lookup table.

� When value mapping is required:


SAP AG 2006

��$XWRPDS�9DOXHV� 7KH�9DOXH�PDSSLQJ�DUHD�VKRZV�VRXUFH�YDOXHV��OHIW��DQG�UHSRVLWRU\

GRPDLQ�YDOXHV�RQ�WKH�ULJKW��LQ�WKLV�FDVH��WKH�UHSRVLWRU\�KDV�GRPDLQ�YDOXHV�ORDGHG��

� &OLFN�$XWRPDS�

�


SAP AG 2006

��0DQXDO�9DOXH�0DSSLQJ��$XWRPDS

$XWRPDSSLQJ ZLOO�PDS�PRVW�± EXW�QRW�DOO�± YDOXHV�

<RX�PXVW�PDQXDOO\�PDS�UHPDLQLQJ�LQGLYLGXDO�YDOXHV�

6WDWXV�SURJUHVV�LV�GLVSOD\HG�LQ�ORZHU�ULJKW�RI�VFUHHQ�

�


SAP AG 2006

��0DQXDO�9DOXH�0DSSLQJ��$GG

&75/�$WR�VHOHFW�DOO

6RXUFH�ILHOGV�WKDW�KDYH�QR�YDOXHV�LQ�WKH�UHSRVLWRU\�PXVW�EH�DGGHG��7KH�YDOXHV�FDQ�EH�ORDGHG�LQ�WKH�UHSRVLWRU\�ILUVW��VHSDUDWH�0'0�,PSRUW�0DQDJHU�³MRE´��RU�DGG�WKH�YDOXHV�KHUH�

�

� When value mapping is required, the value in the &RQYHUWHG�9DOXH column is most useful for adding�new destination values or hierarchies where it is used as the new item or node value. When mapping to existing destination values, the converted value is just a convenience for automap since each value could be manually mapped to any destination value regardless of its value.

� The�$GG button is disabled if the display field of the destination lookup field is compound and the source field is not compound or if the single destination display field is not of type Text, Text Normalized, Text Block, Integer, or Measurement.


SAP AG 2006

��0DWFK�5HFRUG�2SWLRQV

� 6$3�0'0�5HFRUG�PDWFKLQJ�DOORZV�\RX�WR�� 3HUIRUP�GHWDLOHG�PDWFKHV�RI�LQFRPLQJ�VRXUFH�UHFRUGV�WR�H[LVWLQJ�GHVWLQDWLRQ�UHFRUGV�

� (IILFLHQWO\�DQG�SUHFLVHO\�VSHFLI\�WKH�LPSRUW�DFWLRQ�IRU�HDFK�JURXS�RI�VRXUFH�UHFRUGV

� 0DNH�GHFLVLRQV�DERXW�LQGLYLGXDO�UHFRUG�KDQGOLQJ�ZKHUH�QHHGHG� 5HFRUG�PDWFKLQJ�LQ�WKH�0'0�,PSRUW�0DQDJHU�WDNHV�EDVLF�

NH\�ILHOG�PDWFKLQJ�DQG�H[WHQGV�LW�DV�IROORZV�� 0XOWLSOH�PDWFKLQJ�ILHOGV�� 0DWFKLQJ�ILHOG�FRPELQDWLRQV� 0DWFKLQJ�FRQYHUWHG�RU�PDSSHG�VRXUFH�YDOXHV�� &DVH�E\�FDVH�RSHUDWLRQV� 5HFRUG�E\�UHFRUG�RSHUDWLRQV

�

� Record matching in the MDM Import Manager takes basic key field matching and extends it as follows:�y 0XOWLSOH�PDWFKLQJ�ILHOGV: You can specify multiple matching fields for a more precise match if

no single field is completely reliable as a key field.�y 0DWFKLQJ�ILHOG�FRPELQDWLRQV: You can also specify matching field combinations if no individual

field identifies each destination record, such as when MFG and PART NO together comprise the key field.�

y 0DWFKHV�FRQYHUWHG�RU�PDSSHG�VRXUFH�YDOXHV: Rather than using the original source value, matching is based upon the normalized, converted, or mapped source value, providing for a more accurate and precise match against destination record values.�

y &DVH�E\�FDVH�RSHUDWLRQV: The matching process breaks the source records into different groups based on the type of match – exact, partial, or conflict – and then allows you to apply a different default import action – skip, create, update, or replace – to each group.�

y 5HFRUG�E\�UHFRUG�RSHUDWLRQV: For even more precise import control, the default import action for each individual source record and each matching destination record can be overwritten on a record-by-record basis.


SAP AG 2006

��0DWFK�5HFRUGV

6HOHFW�RQH�RU�PRUH�PDSSHG�ILHOGV�WKDW�ZLOO�EH�XVHG�WR�FRPSDUH�VRXUFH

UHFRUGV�WR�UHSRVLWRU\�UHFRUGV

<RX�FDQ�LGHQWLI\�RQH�RU�PRUH�PDSSHG�GHVWLQDWLRQ�ILHOGV�DV�PDWFKLQJ�ILHOGV�RU�PDWFKLQJ�ILHOG�FRPELQDWLRQV�E\�PRYLQJ�WKHP�WR�WKH�0DWFKLQJ�ILHOGV OLVW�RQ�WKH�ULJKW��

:LWK�ILHOG�YDOXH�PDSSLQJ�FRPSOHWH��WKH�IRFXV�VKLIWV�IURP�ILHOG�RULHQWHG�SURFHVVLQJ�WR�PRUH�WUDGLWLRQDO�UHFRUG�RULHQWHG�SURFHVVLQJ�

.H\�ILHOG�PDWFKLQJ�LV�WKH�FULWLFDO�VWHS� )URP�WKH�OLVW�RI�PDSSHG�ILHOGV��LGHQWLI\�WKH�NH\�ILHOG�V��WR�EH�XVHG�WR�

PDWFK�VRXUFH�UHFRUGV�WR�H[LVWLQJ�GHVWLQDWLRQ��UHSRVLWRU\��UHFRUGV�� <RX�FDQ�WKHQ�XSGDWH�RU�UHSODFH�PDWFKHG�UHFRUGV�UDWKHU�WKDQ�

FUHDWLQJ�GXSOLFDWHV�LQ�WKH�UHSRVLWRU\��

�

� Not all mapped destination types can be used for record matching. Only those that appear in the 0DSSHG�GHVWLQDWLRQ�ILHOGV list can be selected as a matching field or fields.


SAP AG 2006

��0DWFK�)LHOG�&DQGLGDWH�5HIHUHQFH

�

$YDLODEOH�DV�0DWFKLQJ�)LHOGV� 1RW�$YDLODEOH�DV�0DWFKLQJ�)LHOGV�� AutoID � Integer � Real � Currency � Date � Time � Timestamp � Text � Text Normalized � Lookup [Flat] � Lookup [Hierarchy] � Lookup [Taxonomy]

� Text Large � Lookup [Text Block] � Lookup [Text HTML] � Lookup [Qualified] � Qualifiers � Attributes � Multi-valued fields / qualifiers / attributes

1RW�DOO�PDSSHG�GHVWLQDWLRQ�W\SHV�FDQ�EH�XVHG�IRU�UHFRUG�PDWFKLQJ��7KRVH�WKDW�DSSHDU�LQ�WKH�0DSSHG�'HVWLQDWLRQ�)LHOGV OLVW�DQG�WKDW�\RX�FDQ�VHOHFW�DV�PDWFKLQJ�ILHOGV�DUH�OLVWHG�

�


SAP AG 2006

��'HIDXOW�,PSRUW�$FWLRQV��

<RX�FDQ�VHW�D�GLIIHUHQW�GHIDXOW�LPSRUW�DFWLRQ�IRU�HDFK�FRPELQDWLRQ�RI�PDWFK�FODVV�DQG�PDWFK�W\SH��

7KH�GHIDXOW�LPSRUW�DFWLRQ�LV� $XWRPDWLFDOO\�DSSOLHG�WR�HDFK�FRUUHVSRQGLQJ�VRXUFH�UHFRUG�LQ�WKH

PDWFK�FODVV�PDWFK�W\SH�JURXS� $XWRPDWLFDOO\�DSSOLHG�WR�HDFK�PDWFKLQJ�GHVWLQDWLRQ�UHFRUG�IRU�WKDW�

VRXUFH�UHFRUG

�

� The following default import actions are delivered: y Skip: Skip this source record during import processing y Create: Create a new destination record based on this source record y Update (NULL Fields Only): Update just the NULL fields of the matching existing destination record(s)

based on this source record y Update (All Mapped Fields): Update the matching existing destination record(s) with all of the mapped

fields of this source record y Replace: Replace the matching existing destination record(s) by first deleting and then creating a new

destination record. This impacts the Auto ID fields in that it deletes the old record and then creates a new record with the next, incremental Auto ID (for example, the new record will no long have the same Auto ID value).

� Considerations for Import Actions – If the source data is:

y Accurate and complete, WKHQ use the Replace import action to replace matching destination records in their entirety

y Accurate and incomplete, WKHQ use the Update (All Mapped Fields) import action to preserve unmapped fields but overwrite existing data

y Less accurate than existing destination data, WKHQ use the Update (NULL Fields Only) import action to fill in missing data but not overwrite existing data

� 1RWH: The Replace option impacts Auto ID fields in that it deletes the old record and then creates a new record with the next, incremental Auto ID (for example, the new record will no long have the same Auto ID value).


SAP AG 2006

��'HIDXOW�,PSRUW�$FWLRQV��

9DOXH�PDWFKLQJ�EUHDNV�WKH�HQWLUH�VHW�RI�VRXUFH�UHFRUGV�LQWR�VHYHUDO�GLIIHUHQW�JURXSV�EDVHG�RQ�� 0DWFK�&ODVV��1XPEHU�RI�PDWFKLQJ�GHVWLQDWLRQ�UHFRUGV� 0DWFK�7\SH��'HJUHH�RI�PDWFK

7KH�0'0�,PSRUW�0DQDJHU�LQGLFDWHV�WKH�QXPEHU�RI�UHFRUGV�LQ�HDFK�JURXS��DQG�KRZ�PDQ\�RI�WKH�UHFRUGV�LQ�HDFK�JURXS�DUH�DFWLYH��LQ�WKH�'HIDXOW�LPSRUW�DFWLRQV JULG�

�

� The 'HIDXOW�LPSRUW�DFWLRQV grid is disabled if you have not yet selected the current source and destination tables and at least one matching field.


SAP AG 2006

��'HIDXOW�,PSRUW�$FWLRQV�6HWWLQJV

�

&ROXPQV� 'HVFULSWLRQ�Active The active records in each group of source records as “P of Q”

Match Class � 1RQH�� 6LQJOH�� 0XOWLSOH

Match Type

� 1RQH�� ([DFW�� 3DUWLDO�� &RQIOLFW�

Default Import Action

� 6NLS�� &UHDWH�� 8SGDWH��18//�)LHOGV�2QO\�� 8SGDWH��$OO�0DSSHG�)LHOGV�� 5HSODFH

<RX�FDQ�VSHFLI\�WKH�GHIDXOW�LPSRUW�DFWLRQ�IRU�HDFK�JURXS�RI�VRXUFH�UHFRUGV��DQG�KDYH�WKH�DFWLRQ�DXWRPDWLFDOO\�DSSOLHG�WR�HDFK�DFWLYH�UHFRUG�LQ�WKH�JURXS�

�

� Value matching breaks the entire set of source records into several different groups based on the following:

� Match class: Number of matching destination records y None: The source record matches no destination records y Single: The source record matches exactly one destination record y Multiple: The source record matches two or more destination records

- 1RWH: “ Multiple” does not mean match on “ multiple” source/destination fields (columns) but indicates that multiple destination records match a source record based on the specified matching fields.

� Match type: Degree of match � The MDM Import Manager indicates the number of records in each group (and how many of the

records in each group are active) within the 'HIDXOW�LPSRUW�DFWLRQV grid.


SAP AG 2006

��9DOXH�0DWFK

�� "! ��$#%��'& #%��'&)(+*�,��-�.0/ -�.0/ -�.1/ 24365�798�:�;=<

113-224 Equal Exact NULL Undefined None 113-224 101-44 Not Equal None 113-224 Undefined None NULL Undefined None* NULL 101-44 Undefined None

0DWFK�W\SH�LV�EDVHG�RQ�YDOXH�PDWFKLQJ�)RU�HDFK�PDWFKLQJ�ILHOG�RU�ILHOG�FRPELQDWLRQ��WKHUH�DUH�WKUHH�

SRVVLEOH�RXWFRPHV�RI�YDOXH�PDWFKHV�DV�IROORZV�� (TXDO��(YHU\�SDLU�RI�FRUUHVSRQGLQJ�VRXUFH�DQG�GHVWLQDWLRQ�YDOXHV�

LV�HTXDO��LQFOXGLQJ�18//�WR�18//�� 8QGHILQHG��$W�OHDVW�RQH�18//�WR�QRQ�18//�KDV�EHHQ�IRXQG�LQ�WKH�

YDOXH�FRPSDULVRQ�V�� 1RW�(TXDO��$W�OHDVW�RQH�SDLU�RI�

FRUUHVSRQGLQJ�VRXUFH�DQG�GHVWLQDWLRQ�YDOXHV�LV�QRW�HTXDO�

�


SAP AG 2006

��0DWFK�7\SH

7KH�FRPELQDWLRQ�RI�YDOXH�PDWFKHV�OHDGV�WR�WKH�IROORZLQJ�PDWFK�W\SHV�

� 1RQH��1R�GHVWLQDWLRQ�YDOXH�PDWFKHV��6RXUFH�UHFRUG�LV�D�QHZ�UHFRUG�

� ([DFW��$OO�WKH�LQGLYLGXDO�YDOXH�PDWFKHV�DUH�(TXDO�� 3DUWLDO��$W�OHDVW�RQH�YDOXH�PDWFK�LV�(TXDO�DQG�DW�OHDVW�RQH�

8QGHILQHG��QR�YDOXH�PDWFKHV�DUH�1RW�(TXDO�� &RQIOLFW��$W�OHDVW�RQH�YDOXH�PDWFK�LV�(TXDO�DQG�DW�OHDVW�RQH�

YDOXH�PDWFK�LV�1RW�(TXDO� >0?A@CBED�F G6F"H'IKJ L�M�INJ ?AL OPM�Q4@+FSRTM'I�D�U RVM+I�D�UXWZYZ['F

\�]_^ ^1`Pa \C]%^ ^`%a \]%^ ^`%a bdcfe'g�h+i�jlk113-224 22345 Equal Equal Exact

113-224 NULL Equal Undefined Partial

113-224 4403 Equal Not Equal Conflict

NULL 22345 Undefined Equal Partial

113-224 22345

NULL NULL Undefined Undefined None

�

� The only match type possible with a single matching field or field combination is Exact, since either a Partial or Conflict match requires an Equal match combined with at least one other value match.

� NULLs play a part in Partial matching and need to be considered as import actions are taken.


SAP AG 2006

��3HUIRUP�'DWD�,PSRUW

'HWDLOV�RI�UHPDLQLQJ�

VWHSV�RU�VXFFHVV�

7KH�,PSRUW�FDQ�RQO\�EH�SHUIRUPHG�IURP�WKH�,PSRUW�6WDWXV WDE��,W�LV�RQO\�IURP�WKLV�WDE�WKDW�WKH�([HFXWH�,PSRUW LFRQ��EHFRPHV�DFWLYH�

�

� Imports can be performed: y When the action items on the ,PSRUW�6WDWXV tab read “ Ready to Import.” y Click the ([HFXWH�,PSRUW button or choose 5HFRUGV�Æ�([HFXWH�,PSRUW from the main menu. y The ,PSRUW�6WDWXV�7DE must be the active tab before the import can be performed.

�� $FWLRQ�,WHPV� What they mean [and the actions required]

y Map field(s): A source and destination table has been selected, but none of the fields are mapped. [Return to the 0DS�)LHOGV�9DOXHV tab and either automap or manual map the appropriate fields.]

y Map ‘Currency’ field value(s): The &XUUHQF\ field has values that are not mapped. [Go to the 0DS�)LHOGV�9DOXHV tab and select the destination field &XUUHQF\. Then at the bottom, map all values.]

y Refresh record matching step: Changes have occurred on the destination. [Go to the 0DWFK�5HFRUGV tab and click the 5HIUHVK button at the top.]

y Select import action: All records have a skip action. [Return to the 0DWFK�5HFRUGV tab and select an action for the records other than skip.]

y Ready to import: Success. [The ([HFXWH�,PSRUW icon (��) is now enabled and the import can be performed.]


SAP AG 2006

6DYHG�PDSV�� $UH�UHOHYDQW�RQO\�IRU�WKLV�UHSRVLWRU\��W\SH�RI�ILOH��DQG�WDEOHV� $UH�RQO\�VHHQ�ZKHQ�XVLQJ�WKH�FXUUHQW�UHPRWH�V\VWHP�� &RQWDLQ�FRQILJXUDWLRQ�RSWLRQV� &RQWDLQ�VRXUFH�DQG�GHVWLQDWLRQ�WDEOHV� &RQWDLQ�DOO�ILHOG�DQG�

YDOXH�PDSSLQJV� 5HFRUG�DOO�

PDWFKLQJ�FULWHULD

��6DYH�D�0DS

�


SAP AG 2006

9LHZ�5HVXOWV�LQ�0'0�'DWD�0DQDJHU

�

� Data can RQO\ be seen in the MDM Data Manager.


SAP AG 2006

6XPPDU\


�


SAP AG 2006

0'0�,PSRUW�0DQDJHU��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� ([SODLQ�WKH�YDOXH�RI�0'0�,PSRUW�0DQDJHU�� /LVW�WKH�VL[�VWHSV�IRU�GDWD�LPSRUW�ZLWK�0'0�,PSRUW�

0DQDJHU� ([SODLQ�WKH�GHWDLOHG�IXQFWLRQV�IRU�LPSRUWLQJ�DQG�

PDSSLQJ�GDWD�IURP�YDULRXV�VRXUFHV

�

� The import process is the most-used process in MDM. � List the six steps for data import with MDM Import Manager

y Connect to Repository y Connect to Source y Select source and destination tables y Map Fields/ Values y Match Records y Import Data


�([HUFLVHV�

8QLW�� 0'0�,PSRUW�0DQDJHU�([HUFLVH�7RSLF��0'0�,PSRUW�0DQDJHU�


• %DVLF�LPSRUW�IXQFWLRQDOLW\�• 6WHSV�UHTXLUHG�WR�SHUIRUP�DQ�LPSRUW�RI�GDWD

3XUSRVH��This exercise allows you to perform basic data imports using SAP MDM.

3UHUHTXLVLWHV��MDM Repository has been created [Exercise Æ Create a Repository = Case_Study]

MDM Server has been mounted and started.

Repository Case Study has been loaded. (If your repository is not loaded please go to the console and load the YourLetter_Case_Study repository.)


4-1 /RJRQ�WR�0'0�,PSRUW�0DQDJHU The Import Manager will first ask you to identify the source of the data you wish to import. The type of source you choose (i.e. .xls, xml, etc.) influences the subsequent system prompts.

4-1-1 Double-click on the SAP MDM Import Manager Icon found on the desktop.

&RQQHFW�WR�0'0�5HSRVLWRU\��

FOLFN�Æ� �MDM Server: LOCALHOST

Repository: Yourletter_Case_Study

click Æ <OK> button

Language: English [US]

User: Admin

Password: <no password>

click <1(;7> button�

�

4-1-2 Select the following information to connect to source.

&RQQHFW�WR�6RXUFH��Type: Excel

Remote System: NewYork

File Name: open and find M drive and the MDM100_71 folder.

Select file: Countries.xls

click <),1,6+ >

4-1-3 If you get an error message about a bug in Excel, click Yes to have the registry setting fixed.


4-2 %URZVH�7DEOHV��)LHOGV��DQG�5HFRUGV Familiarize yourself with the tables, fields and records that you are working with during this exercise.

4-2-1 Open up the source file using Microsoft Excel. Notice how the structure of the worksheets within the workbook compares to the Source Hierarchy in the MDM Import Manager��The files used in this exercise are:

&RXQWULHV�[OV�&DVHB6WXG\B1<�[OV

4-2-2 Click on the Source Preview tab to see the data records that you will be importing during this exercise. Note that you can sort the records with the controls at the top to quickly inspect the data for specific values.

Review the Destination Hierarchy. This represents the structure of the repository.


4-3 3UHSDUH�IRU�,PSRUW�RI�/RRNXS�7DEOHV�The Import of the following lookup tables needs to be done first.

1. Countries from file Countries.xls

2. Divisions from file Case_Study_NY.xls

4-3-1 &RXQWULHV�,PSRUW 4-3-1-1 Select source: &RXQWULHV�DQG�&RGHV� and destination: &RXQWULHV�

4-3-1-2 Go to Tab strip

4-3-1-3 First click on Automap. This will map the Name and ISO Code fields since they are exact text matches.

4-3-1-4 Since the text for Country does not match the text for Remote Key, you will have to manually map this field.

4-3-1-5 Select tab strip

4-3-1-6 Select UHPRWH�NH\. Select Add to add it as the matching field.


4-3-1-7 Select &UHDWH as default import action

4-3-1-8 Select�tab strip

4-3-1-9 Save your Map as &RXQWULHV

4-3-1-10� Execute��


4-3-2 'LYLVLRQV�,PSRUW�4-3-2-1 First the division information is stored in the file Case_Study_NY.xls.

You will need to connect to the new excel file. This can be done quickly by going to )LOH�Æ�&RQQHFW�WR�6RXUFH«

4-3-2-2� Select the Case_Study_NY.xls for the File name.

4-3-2-3� Select source: 'LYLVLRQV� and destination: 'LYLVLRQV (the table Divisions you created in your repository)

4-3-2-4� Now follow the steps above from 4-3-1-1 to 4-3-1-8 above with the import of Divisions:

• Map Division with [Remote Key] and description with Name [DF].

• Define Remote Key as a matching field.

• Change Default import action to Create.

4-3-2-5� Remember to save your completed mapping as 'LYLVLRQV.

4-3-2-6� ([HFXWH��

This completes our import of the two lookup tables. Next we need to import the records of items.


4-4 ,PSRUW�5HFRUGV�The record data is part of the same file as Divisions.

4-4-1 Select the Source and Destination tables.

4-4-2 Switch to Map Fields/Values tab and select Automap.

4-4-2-1 Verify that the mapped fields are correct.

4-4-2-2 You will need to manually map the remaining fields.

4-4-3 Your result should look like this:

4-4-4 Compare the &RXQWU\�0DQXIDFWXUHG and &RXQWU\�3XUFKDVHG value

conversion and mapping in the lower left hand corner. In the case of Country Manufactured the values are not mapped but Country Purchased is. Why?

6ROXWLRQ��:KHQ�ORDGLQJ�WKH�FRXQWULHV��WKH�FRXQWU\�FRGH�ZDV�PDSSHG�WR�WKH�UHPRWH�NH\��7KH�&RXQWU\�3XUFKDVHG�ILHOG�KDV�WKH�YDOXHV�RI�WKH�FRXQWU\�FRGH�DQG�VR�ZDV�DXWRPDWLFDOO\�PDSSHG�EHFDXVH�WKH�NH\�PDSSLQJ�KDG�DOUHDG\�EHHQ�GRQH��7KH�YDOXHV�RI�&RXQWU\�0DQXIDFWXUHG�FRQWDLQHG�WKH�FRXQWU\�QDPHV�ZKLFK�DUH�QRW�LGHQWLILHG�ZLWK�WKH�UHPRWH�NH\�


4-4-5 All values must be mapped before importing data. To map the Country Manufacturer YDOXHV click on Automap. The countries will now be mapped.

4-4-6 Next go to Match Records tab and select Product ID and click Add to add it as the Matching field.

4-4-7 Move to the Import Status tab. There will be an Action items: Map ’Electric’ field value(s).

4-4-8 You will need to go back to the Map Fields tab and map the values of the field Electric.

4-4-9 Return to the Import Status tab.

4-4-10 Also 6DYH your map as ,WHPV�0DS. Go to )LOH�Æ�6DYH�$V«

4-4-11 ([HFXWH��


4-5 ([SRUW�6DYHG�0DS� The last thing you did was to save the Items Map. We are now going to export that map

for use in another repository or another remote system.

4-5-1 Go to )LOH�Æ�([SRUW«

4-5-2 Select ,WHPV�0DS and click OK.

4-5-3 Save the map on your Citirx Desktop or in the Citrix My Documents folder as Items Map.

4-5-4 You now have an ,WHPV�0DS�PDS file that we will use in a later exercise.


4-6 5HYLHZ�5HVXOWV�LQ�WKH�'DWD�0DQDJHU�Confirm the status and review the import results in the Data Manager.

4-6-1 Open Data Manager with your Case_Study repository.

4-6-2 Select the table: 3URGXFWV in the Data Manager. There will be 9 records.

4-6-3 Switch the table selection to &RXQWULHV and verify that all 238 country records were imported and 9 division records.

4-6-4 Check out the different sliding search tabs.

4-6-5 Narrow your search by selecting the Division as Major Appliance.

4-6-6 Close the Import Manager.


SAP AG 2006

4XDOLILHG�7DEOHV




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�


SAP AG 2006

&RQWHQWV�� 4XDOLILHU�7DEOHV

m 3XUSRVH RI�TXDOLILHU WDEOHVm &UHDWLRQ�RI�TXDOLILHU WDEOHVm &UHDWLRQ�RI�TXDOLILHU ILHOGV

0'0�4XDOLILHG�7DEOHV

�


SAP AG 2006

0'0�4XDOLILHG�7DEOHV��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� ([SODLQ�WKH�SXUSRVH�RI�TXDOLILHG�ORRNXS�WDEOHV� 8QGHUVWDQG�WKH�XVDJHV�IRU�TXDOLILHG�ORRNXS�WDEOHV�� &UHDWH�D�TXDOLILHG�ORRNXS�WDEOH

�


SAP AG 2006

0'0�4XDOLILHG�7DEOHV��%XVLQHVV�6FHQDULR

� ,Q�\RXU�UHSRVLWRULHV��\RX�ZDQW�WR�PRGHO�FRQGLWLRQDO�GDWD�WR�DFFXUDWHO\�UHIOHFW�\RXU�FXUUHQW�GDWD�PRGHO�REMHFW�LQWUD�UHODWLRQVKLSV�E\�XWLOL]LQJ�TXDOLILHG�WDEOHV��

�


SAP AG 2006

4XDOLILHU /RRNXS 7DEOH�,QWURGXFWLRQ4XDOLILHG�7DEOH�8VDJH�6FHQDULRV&UHDWLRQ�RI�4XDOLILHG�/RRNXS�7DEOHV6XPPDU\

0'0�4XDOLILHU 7DEOH�,QWURGXFWLRQ

�


SAP AG 2006

0'0�4XDOLILHG /RRNXS 7DEOHV

$�TXDOLILHG�WDEOH� ,V�D�VSHFLDO�NLQG�RI�YHUVDWLOH�ORRNXS�WDEOH� &DQ�HIILFLHQWO\�VWRUH�FRPSOH[�UHODWLRQVKLSV�EHWZHHQ�D�PDLQ�

WDEOH�UHFRUGV�DQG�RQH�RU�PRUH�ORRNXS�WDEOH�UHFRUGV� 6WRUHV�D�VHW�RI�ORRNXS�UHFRUGV

�

� A qualified table is a special kind of lookup table that is extremely versatile. It can be used to efficiently store complex relationships between a main table product record and one or more lookup table records that contain various types of additional information.

� A qualified table stores a set of lookup records and also supports qualifiers, database “ sub fields” that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record.

� Qualified tables offer self-configuring, out-of-the-box support for multiple prices (including quantity price breaks), cross-reference part numbers, other distributor/supplier/customer-specific information, and product applications.


SAP AG 2006

3XUSRVH RI�4XDOLILHG /RRNXS 7DEOHV

([DPSOH�RI�FXVWRPHU¶V�DGGUHVVHV�DQG�WKH�UHTXLUHG�LQIRUPDWLRQ�DV�VHHQ�LQ�D�'%06�

� &XVWRPHU�QDPH�RU�LG� &XVWRPHU�DGGUHVVHV� 7\SH�RI�DGGUHVV

6DPH�FXVWRPHU¶V�DGGUHVVHV�DQG�DV�SURGXFHG�LQ�0'0�� &XVWRPHU�QDPH��0DLQ�WDEOH�

� 7\SH�RI�DGGUHVV��1RQ�TXDOLILHU�LQ�4XDOLILHG�ORRNXS�WDEOH�

� $GGUHVVHV��4XDOLILHU�LQ�4XDOLILHG�ORRNXS�WDEOH�

�

� A qualified lookup table is built from two types of fields; non-qualifiers and qualifiers. Non-qualifiers represent a relatively small set of shared values. In the example’s case, an address type. The qualifiers contain relevant information to specific main table records in this case the address which consists of 5 fields.


SAP AG 2006

/RRNXS�YV��4XDOLILHG�/RRNXS�7DEOH

Free-floating lookup data is not possible

Free-floating lookup data is possible

Qualified field is only possible on main table

Lookup within lookup is possible

Qualified record is maintained after main table records gets created

Lookup table records need to be maintained before main table record

Contains conditional set of records, e.g. pricing based on manufacturer and region

Contains pre-defined set of records, e.g. list of manufacturers for a product

Contains larger number of records compared to the main table

Contains relatively small number of records compared to the main table

4XDOLILHG�/RRNXS)ODW�RU�+LHUDUFK\�/RRNXS�7DEOH

�

� Examples of common lookup tables are: y Countries y Regions y Titles y Departments

� Examples of common qualifier tables are: y Prices y Sales Data y Variants


SAP AG 2006

4XDOLILHG�7DEOH�6HDUFK�'HWDLOV

$�TXDOLILHG�ORRNXS�WDEOH� %XLOGV�FRQGLWLRQDO��RQH�WR�PDQ\�

UHODWLRQVKLS� &DQ�VWRUH�µ1¶�QXPEHU�RI�FRPELQDWLRQV� ,V�DYDLODEOH�IRU�VHDUFK�DQG�SXEOLVKLQJ� &DQ�EH�SRSXODWHG�XVLQJ�,PSRUW�0DQDJHU

RU�'DWD�0DQDJHU

� ,V�RQO\�DYDLODEOH�RQ�PDLQ�WDEOH ± TXDOLILHG�ORRNXSV�RQ�VXE�WDEOHV�DUH�QRW�SRVVLEOH

� 4XDOLILHG�GDWD�LV�DOZD\V�OLQNHG�WR�PDLQ�WDEOH�GDWD�± IUHH�IORDWLQJ�GDWD�LV�QRW�SRVVLEOH

�

� Qualified table builds one-to-many relationships based on conditions e.g. if region = ‘xxx’ then price = ‘yyy’ else price = ‘zzz’ . Qualified table allows ‘N’ number of such conditional combinations.

� Qualified data can be available for searching and publishing and the qualified data can be populated using Data Manager or Import Manager.

� Qualified data can only be linked to the main table record and only to the main table record. That means, qualified data is not available as a free floating data that can be used by other main table records.

� A qualified table is used as a valid table that facilitates data entry and drill-down search, where each lookup table record often represents a valid combination of nested lookup values from which the user can select directly or indirectly using the multi-level search-within-a-search of a qualified lookup search tab.

� A qualified table provides only partial validation against lookup table values and records, since some of the sub table information is stored as qualifiers. The relationship between main table records and qualified table records is typically many-to-many.

© SAP AG MDM100 2-100

SAP AG 2006

4XDOLILHG�7DEOHV�8VDJH�6FHQDULRV

4XDOLILHU /RRNXS 7DEOH�,QWURGXFWLRQ4XDOLILHG�7DEOHV�8VDJH�6FHQDULRV&UHDWLRQ�RI�4XDOLILHG�/RRNXS�7DEOHV6XPPDU\

�

© SAP AG MDM100 2-101

SAP AG 2006

� 6FHQDULR�± 3ULFH�EUHDNV�E\�TXDQWLW\�DQG�SURGXFW

� 4XDOLILHG�7DEOH�FRQWDLQV�ILHOG�TXDQWLW\�DQG�SULFH��TXDOLILHU�

� 4XDOLILHG�ORRNXS�ILHOG�LQ�WKH�PDLQ�WDEOH�UHSODFHV�DOO�TXDQWLW\�DQG�SULFH�ILHOGV

� 3ULFLQJ�GDWD�VWRUHG�DV�TXDOLILHU�YDOXHV�DVVRFLDWHG�ZLWK�WKH�PDLQ�WDEOH

� $�PDLQ�WDEOH�DQG�TXDOLILHG�WDEOH�OLQN�LV�FUHDWHG�RQO\�IRU�SULFHV�ZLWK�SURGXFW�TXDQWLW\�FRPELQDWLRQ

8VDJH�6FHQDULR�,�² 3ULFLQJ�DQG�4XDQWLW\�%UHDN

$5.12

nporq�s

$4.80

$7.99

$3.40

tvu ors�s

$8.75

nwo4xwq

Bearing115

$8.30Wrench114

$3.44$3.48$3.51Widget113

x t o q�sn u orxvqnwoysz�{�|~}��A�

�

� Qualified lookup table is extremely versatile and can be used in many different scenarios. Pricing by quantities or pricing by manufacturer and quantities, etc are some of the examples.

� Consider the requirement of storing quantity pricing data by main table product record. Using a qualifier to store the quantity pricing data, the qualified table would have a single field Quantity and a single qualifier Price, and would contain the quantity records.

� On the main table, there will be a qualified lookup field created to link main table and qualified table. The main table records and qualified data gets linked only if actual price exists for a product and quantity relationship. This also reduces number of records stored in the qualified table.

© SAP AG MDM100 2-102

SAP AG 2006

� 6FHQDULR�± 3URGXFW�UHFRUGV�WKDW�FRQWDLQV�RQH�RU�PRUH�SDUW�QXPEHUV�E\�PDQXIDFWXUHUV

� 4XDOLILHG�WDEOH�ZLWK�VLQJOH�ILHOG�'LVWULEXWRU�DQG�VLQJOH�TXDOLILHU��3DUW�1XPEHU

� 3DUW�1XPEHU�LV�VWRUHG�DV�D�TXDOLILHU�YDOXH�DVVRFLDWHG�ZLWK�WKH�PDLQ�WDEOH�DQG�WKH�TXDOLILHU�OLQN�WDEOH

8VDJH�6FHQDULR�,,�² &URVV�5HIHUHQFH�3DUW�1XPEHUV

�Aqv�Co4x�� t�f�6o4x�n tq t or�� u��'�y�+�� }9�x�n t�Aqv�Co4x�x�� o4q u �� }v{ �x�nw�z�}9��{ �� '�+� � }�� P{v�v��} �� { � �v� } �z�{�|~}��

�

� This is a typical example of different part numbers used by manufacturers for a similar part. E.g. a sprocket has different part numbers for different manufacturers. If there is a requirement to store this information in your system then use a qualified table with manufacturer as a distinct field and part number as a qualifier.

© SAP AG MDM100 2-103

SAP AG 2006

� 6FHQDULR�± 6LQJOH�$XWRPRWLYH�SDUW�ZLWK�YDULDEOH�LQVWDOO�RSWLRQV�XVHG�LQ�PXOWLSOH�FRPELQDWLRQV�RI�PDNH��\HDU��DQG�PRGHO

� $�4XDOLILHG�WDEOH�ZLWK��TXDOLILHUV�DQG��GLVWLQFW�ILHOGV�WR�VWRUH�DSSOLFDWLRQ�VSHFLILF�GDWD

� $SSOLFDWLRQ�VSHFLILF�YDOXHV�VWRUHG�DV�TXDOLILHUV�DVVRFLDWHG�ZLWK�WKH�PDLQ�WDEOH�DQG�TXDOLILHG�OLQN�WDEOH�± UHVXOWLQJ�LQ�VLQJOH�PDLQ�WDEOH�UHFRUG

8VDJH�6FHQDULR�,,,�² $SSOLFDWLRQ�%DVHG�

�

� Here is the another example of how a qualified table can be used to store application specific, conditional information.

© SAP AG MDM100 2-104

SAP AG 2006

)LHOG�7\SHV

4XDOLILHU /RRNXS 7DEOH�,QWURGXFWLRQ4XDOLILHG�7DEOH�8VDJH�6FHQDULRV&UHDWLRQ�RI�4XDOLILHG�/RRNXS�7DEOHV6XPPDU\

�

© SAP AG MDM100 2-105

SAP AG 2006

&UHDWLQJ�D�4XDOLILHG�7DEOH�

&UHDWH�D�1HZ�7DEOH�� 5LJKW�FOLFN�RQ�WKH�7DEOHV SDQH�

DQG�FKRRVH�$GG�7DEOH�

� (QWHU�7DEOH�'HWDLOV� 1DPH�± 8QLTXH�WDEOH�QDPH� &RGH�± $�XQLTXH�WDEOH�LGHQWLILHU

� 7\SH�± 4XDOLILHG�)ODW� .H\�0DSSLQJ�± <HV�LI�LPSRUWLQJ�3ULFLQJ�LQIRUPDWLRQ�IURP�GLIIHUHQW�VRXUFHV�

�

� Creating a qualified table is as simple as any other table in MDM. To create one, make sure to select ‘Qualified Flat’ as table type.

© SAP AG MDM100 2-106

SAP AG 2006

� $GG )LHOGV�WR�4XDOLILHG 7DEOH� (QWHU )LHOG 'HWDLOV

� 7\SH��'HILQHV WKH W\SH RI�ILHOG DQG�WKH DYDLODEOHSURSHUW\ GHWDLOV

� 6HDUFK 7DE��(QDEOH DWWULEXWH LQ�WKH VHDUFK WDE �0'0�'DWD 0DQDJHU�

� 0XOWL�9DOXHG��0XOWLSOH�YDOXHV SHUPLWWHG �YDOLG RQO\IRU PHDVXUHPHQWV DQG�ILHOGV ZLWK ORRNXS WDEOHV�

� /RRNXS 7DEOH��$�SXOO�GRZQ PHQX RI�DYDLODEOH ORRNXSWDEOH�V��RU WKH RSWLRQ WR�XVH D�QHZ WDEOH �VXEWDEOH��KLHUDUFKLHV��TXDOLILHG WDEOHV��«�

� 4XDOLILHU�� f�1�' N¡'¢S£=¤ ¢C¥ ¦§¤ ¨ª©'¨�¢�¦¬«"¨«C®¬¢�¯� E¢C°l®"«C¥�±+¢'²³£��6° N¡�¢´ ©�«C¥r¤ £�²�¤y®�µ¶ �«C·�¥ ¢� ¸�¢"¨�' N¡�¢X£=¤ ¢Z¥ ¦§¤ ¨¹¦C¢+£=¤4®�¤r®Zµ¬«�¦�¦¤ =¤ �A®Z«C¥"ºA°��6º"¢C°E N¤ ¢'¨¬�Z£� =¡�¢´ ©�«C¥r¤ £�²�¤y®�µ¶£=¤ ¢C¥ ¦»y¨�¼

� &DFKH��<HV��PHDQV WKH ILHOG LV ORDGHG LQ�PHPRU\��1R��PHDQV VHDUFKHV ZLOO�WDNH ORQJHU��

)LHOG 'HWDLOV�IRU D�4XDOLILHU

�

� You need to have at least one display, non-qualifier field on the table because it forms the link with the main table.

� All types of data types except lookup (qualified flat) and (taxonomy) are possible on a field. Caching is only possible for a qualifier field. A decision for caching need to be taken if you want to cache all qualified data into memory.

� To &DFKH�RU�1RW�WR�&DFKH�� Qualifiers should almost always be cached (i.e. have their values stored in memory) using the Cache

field property for each qualifier field. � While this increases the SAP MDM memory footprint somewhat, caching a qualifier has several

distinct advantages over not caching: (1) it dramatically improves search performance; (2) it permits keyword indexing to be set for the qualifier (using the Keyword field property) to support keyword search of qualifier data; (3) it permits drill-down search by qualifier lookup values even before you have selected a single qualified table record in the qualified lookup field search tab; (4) it permits free-form search by qualifiers (both lookup and non-lookup); and (5) it causes the set of qualified links for each record to be filtered based on the qualifier search value (both lookup and non-lookup).

� 7,3 �$�TXDOLILHU�VKRXOG�QRW�EH�FDFKHG�LI�PHPRU\�LV�OLPLWHG��\RX�GR�QRW�QHHG�WR�VHDUFK�RQ�LWV�lookup values until you have already selected a qualified lookup record and the number of qualified links is huge (e.g. fifty to one hundred million links for an automotive parts repository).

© SAP AG MDM100 2-107

SAP AG 2006

/LQNLQJ�4XDOLILHG�7DEOH�WR�0DLQ�7DEOH

$GG�QHZ�ILHOG�WR�0DLQ�7DEOH� 7\SH� �/RRNXS��4XDOLILHG�)ODW�� 0XOWL�9DOXHG� �$OZD\V�<HV� /RRNXS�7DEOH� �D�TXDOLILHG�WDEOH

m 6HOHFW�IURP�H[LVWLQJ�TXDOLILHG�WDEOHV�RU�FUHDWH�QHZ�TXDOLILHG

,I�6HDUFKLQJ�UHTXLUHG�WKURXJK�'DWD�0DQDJHU�WKHQ

� 6HDUFK�7DE� �<HV

�

� Qualified lookup field is only possible on main table. Make sure to select “ Lookup [Qualified Flat] (multi-valued0” on the field type and select an existing qualified table or choose to create a new one by selecting “ New Qualified Flat Table.”

© SAP AG MDM100 2-108

SAP AG 2006

3RSXODWLQJ�4XDOLILHG�7DEOH�² 'DWD�0DQDJHU

� &OLFN�$GG�WR�FUHDWH�QHZ�TXDOLILHG�ILHOG

� 2U�VHOHFW�IURP�H[LVWLQJ�YDOXHV

� 3RSXODWH�4XDOLILHU�YDOXHV

� 6HOHFW�WKH�4XDOLILHG�9DOXH�ER[�DVVRFLDWHG�ZLWK�WKH�PDLQ�WDEOH�UHFRUG

�

� MDM Data Manager as well as import manager can populate data into qualified table. In the Data Manager, you can add or edit qualified data from the main table record by selecting a qualified record box.

� You can either add a non-qualified field or select one from existing list. Once selected, populate all qualifiers associated with the main table record.

© SAP AG MDM100 2-109

SAP AG 2006

6XPPDU\

4XDOLILHU /RRNXS 7DEOH�,QWURGXFWLRQ4XDOLILHG�7DEOHV�8VDJH�6FHQDULRV&UHDWLRQ�RI�4XDOLILHG�/RRNXS�7DEOHV6XPPDU\

�

© SAP AG MDM100 2-110

SAP AG 2006

0'0�4XDOLILHG�7DEOHV��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� ([SODLQ�WKH�SXUSRVH�RI�TXDOLILHG�ORRNXS�WDEOHV� 8QGHUVWDQG�WKH�XVDJHV�IRU�TXDOLILHG�ORRNXS�WDEOHV�� &UHDWH�D�TXDOLILHG�ORRNXS�WDEOH

�

© SAP AG MDM100 2-111

�([HUFLVHV�

8QLW�� 6$3�0'0�4XDOLILHU�([HUFLVH��7RSLF��0'0�4XDOLILHG�7DEOHV�


• ([SODLQ�WKH�SXUSRVH�RI�TXDOLILHG�ORRNXS�WDEOHV�• 8QGHUVWDQG�WKH�XVDJHV�IRU�TXDOLILHG�ORRNXS�WDEOHV��• &UHDWH�D�TXDOLILHG�ORRNXS�WDEOH�

3XUSRVH��This exercise shows you how you can expand your repository with qualified data. You will create the table and manually enter the data for the records.�The table is going to be Tax_Qualified which is based on the Country for which the item is sold. This requires that we make Tax_Qualified a qualified table which will have multiple countries. But for every item and country there will be only one Tax Code and Tax Rate. The Tax Code and Tax Rate will vary for each items based on the type and size of the item.

3UHUHTXLVLWHV��MDM Server has been mounted and started.

The repository &DVHB6WXG\ is XQORDGHG�

5-1 6WDUW�6$3�0'0�&RQVROH 5-1-1 Start the SAP MDM Console.

5-1-2 Mount and select your server.

5-1-3 Select &DVHB6WXG\ Repository and make sure that repository is unloaded.

© SAP AG MDM100 2-112

5-2 &UHDWH�D�4XDOLILHG�7DEOH 5-2-1 Create a qualified table with following information:

7DEOH�1DPH�� 7D[B4XDOLILHG�7\SH�� 4XDOLILHG�)ODW

5-2-2 Create (or Delete) the fields in the qualified table

)LHOG�1DPH� )LHOG�7\SH� ([WUD�)LHOG�9DOXHV�

Country Lookup Flat Display Field=Yes, Qualifier=No, Lookup Table=Countries

Tax Code Text Display Field=No, Width=10, Qualifier=Yes, Cache=Yes

Tax Rate Real Display Field=Yes, Decimal Places=2, Qualifier=Yes, Cache=Yes,

Name (Default Field) DELETE Display Field = No (this must be

changed in order to delete the field.

5-3 /LQN�4XDOLILHG�WR�0DLQ�7DEOH Create a qualified lookup field in the main table (Products) to link to qualified tax table (Tax_Qualified)

Field Name = Taxation

Type = Lookup (Qualified Flat) (multi valued)

Lookup Table = Tax_Qualified

Values shown to the right ÎShift+Enter to�6DYH Field

5-4 /RDG�5HSRVLWRU\�DQG�6WDUW�0'0�'DWD�0DQDJHU

Load the repository in order to start the Data Manager

© SAP AG MDM100 2-113

5-4-1 Launch the MDM Data Manager

Repository = Yourletter_Case_Study

User = Admin

Password = “ blank”

5-5 3RSXODWH�4XDOLILHG�7DEOH�ZLWK�'DWD�The qualified lookup table will be shown on the right side of the Record Detail pane.

5-5-1 Select any record in the Products table and start populating qualified data. Double click on the Taxation field in the Record Details of the selected record to open the Select Qualified Lookup Records window.

Double click on the 7D[DWLRQ table to open the Select Qualified Lookup Records window.

5-5-2 Click $GG in the bottom right corner.

5-5-3 Select a country, Belgium, and click OK.

5-5-4 Click $GG 2 more countries and select 2 more countries. Example: Canada and USA.

5-5-5 From the Available lookup records [3 of 3] window, select one Canada and click $GG.

© SAP AG MDM100 2-114

5-5-6 Create two records with the table contents:

5HFRUG�2QH�&RXQW\� �&DQDGD�

5HFRUG�7ZR�&RXQWU\� �86$�

Tax Code = 23462� Tax Code = 11248�Tax Rate = 33 Tax Rate = 20.5

After you click OK the window will close, you will need to reopen it to enter the second record.

5-6 &KHFN�WKH�5HVXOWV The end result will look like this:

5-6-1 Notice that the tax code is only displayed in the popup box. Why?

6ROXWLRQ��%HFDXVH�WKH�WD[�FRGH�ILHOG�GRHV�QRW�KDYH�WKH�ILHOG�SURSHUW\�VHW�IRU��'LVSOD\�ILHOG��

5-6-2 Now, search the main table records using 7D[DWLRQ. Reset search, if necessary and select the main table Search Parameter slide bar called Taxation.

Why does Belgium NOT show up in the list?

6ROXWLRQ��%HFDXVH�D�UHFRUG�FRQWDLQLQJ�D�YDOXH�IRU�WKH�TXDOLIHU�ILHOGV�ZDV�QRW�DGGHG�IRU�WKH�%HOJLXP�YDOXH�RI�WKH�QRQ�TXDOLILHU�

�

© SAP AG MDM100 2-115

�([HUFLVHV�

8QLW�� 6$3�0'0�4XDOLILHU�([HUFLVH��7RSLF��0'0�4XDOLILHG�7DEOHV�


• ([SODLQ�WKH�SXUSRVH�RI�TXDOLILHG�ORRNXS�WDEOHV�• 8QGHUVWDQG�WKH�XVDJHV�IRU�TXDOLILHG�ORRNXS�WDEOHV��• &UHDWH�D�TXDOLILHG�ORRNXS�WDEOH�

3XUSRVH��This exercise shows you how you can expand your repository with qualified data and import the data into the qualified table.

The table is going to be Pricings which is based on the Currency for which the item is sold. This requires that we make Pricings a qualified table which will have multiple currencies. But for every currency there will be only one price. The price will vary for each items where as the currency will be based on the same set of available currencies.

3UHUHTXLVLWHV��MDM Server has been mounted and started

Your repository &DVHB6WXG\ is XQORDGHG�

5-7 6WDUW�6$3�0'0�&RQVROH

5-7-1 Start the SAP MDM Console.

5-7-2 Mount and select your server.

5-7-3 Select &DVHB6WXG\ repository and make sure that repository is XQORDGHG.

© SAP AG MDM100 2-116

5-8 &UHDWH�D�4XDOLILHG�7DEOH

You will create a qualified table and then added non-qualifier and qualifier fields.

5-8-1 Create a qualified table with following information:

7DEOH�1DPH�� 3ULFLQJV�

7\SH�� 4XDOLILHG�)ODW

5-8-2 Create (or Delete) the fields in the qualified table: New Lookup Table Name: Currencies

)LHOG�1DPH� )LHOG�7\SH� ([WUD�)LHOG�9DOXHV�

Currency Lookup Flat

Display Field=Yes, Multi value=No, Qualifier=No, Lookup Table=New Flat Table {We want this to lookup the currency from the Currencies table but the table has not been created yet, so we will use a New Flat Table as a temporary holder.}

List Price Currency Display Field=Yes, Symbol=’ blank’ , Decimal=2, Qualifier=Yes, Cache=Yes

Name (Default field) DELETE Display Field = No (this must be changed in order to

delete the field.

5-8-3 In the Console Hierarchy, select Case_Study and on the right select Currencies Set Key Mapping =Yes.

…Change to:

5-8-4 Select the Currencies table from the left pane.

� Add a Description field: Type=Text.

© SAP AG MDM100 2-117

5-9 /LQN�4XDOLILHG�DQG�0DLQ�7DEOH

Create a qualified lookup field in the main table (Products) to link to qualified price table (Pricings)

5-9-1 Select the Product table from the Source Hierarchy

5-9-2 Add new field:

Field Name = Pricing

Type = Lookup (Qualified Flat) (multi valued)

Lookup Table = Pricings

5-9-3 Shift+Enter to�6DYH field

5-10 /RDG�5HSRVLWRU\�DQG�6WDUW�0'0�,PSRUW�0DQDJHU

The qualifier will now be populated with pricing information for the items in the Case_Study repository.

5-10-1 Load the repository.

5-10-2 Launch the MDM Import Manager:

Repository = &DVHB6WXG\ User = Admin Password = “ blank”

© SAP AG MDM100 2-118

5-10-3 Connect to Source:

Type: Excel

Remote System: NewYork

File Name: Case_Study_Qualifier.xls

5-11 3RSXODWH�7DEOHV�ZLWK�'DWD

There are 2 tables that need data imported into them:

�� Currency - Flat Lookup Table

�� Pricing - Qualifier Table

5-11-1 We will begin by populating the Currencies table as it is the Non-qualifier for the Pricing Table.

5-11-1-1 Select Source: µ&XUUHQFLHV�¶ and Destination: &XUUHQFLHV.

5-11-1-2 Select the Map Fields tab and map the following fields

5-11-1-3 Verify in the lower panes that all Source values are mapped.

5-11-1-4 Select Match Records tab

� Select Remote Key as the Matching field � Change the Default Import action to Create.

5-11-1-5 Select Import Status tab, execute, and save Map as Currencies.

5-11-1-6 After saving the map, go to )LOH�!�&ORVH. This will close the map.

© SAP AG MDM100 2-119

5-12 Next we will populate the qualified table Pricings

5-12-1 Select Source: µ,WHP�3ULFHV�¶ and Destination: 3URGXFWV. 5-12-2 Select Map Fields/Values tab and map as shown below.

Pay attention that you map the /LVW�3ULFH which is from the Qualifier table and QRW the Price from the main table. We have decided that Price needs to be in a qualified table.

5-12-3 You will need to $GG the Source values for the Currency field since the non-qualifier values (Destination values) have not been populated and are empty.

5-12-4� Select Matching Records tab and Matching on Product ID. 5-12-5 Notice that there are 2 new records which must be created and 17 Single records

that we will update (NULL Fields Only). Why do we have 2 types of Actions?

6ROXWLRQ��7KH�SUHVHQW�XSGDWH�RI�GDWD�FRQWDLQV�XSGDWHG�GDWD�IRU�UHFRUGV�SUHYLRXVO\�LPSRUWHG�DQG�LQ�DGGLWLRQ��FRQWDLQV��1(:�UHFRUGV�QRW�SUHYLRXVO\�LPSRUWHG��7KH�,PSRUW�0DQDJHU�UHFRJQL]HV��EDVHG�RQ�WKH�YDOXH�RI�WKH�0DWFKLQJ�)LHOG��WKDW�WKHVH��VLQJOH�UHFRUGV�DOUHDG\�H[LVW�LQ�WKH�UHSRVLWRU\�

© SAP AG MDM100 2-120

5-12-6� Go to Import Status

5-12-7 ([HFXWH��

5-13 &KHFN�WKH�5HVXOWV

Now, open the Data Manager and note the number of total records.

5-13-1 The price information is now displayed based on the Currency in the Pricing table below the Taxation table.

5-13-2 Notice that you have a new record with Product ID = 109. This record has only the Product ID, Name, and Pricing.

5-13-3 Now search the main table records using 3ULFLQJ�on the sliding tab. Reset search, if necessary and select the Price search bar. How many records have pricing information for the Japanese Yen?

© SAP AG MDM100 2-121

SAP AG 2006

+LHUDUFKLHV




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�

© SAP AG MDM100 2-122

SAP AG 2006

&RQWHQWV�� +LHUDUFK\�7DEOHV

½ ,QWURGXFWLRQ½ &UHDWLRQ�RI�+LHUDUFK\ 7DEOH½ 0DQXDO�DQG�LPSRUW RI�GDWD

0'0�+LHUDUFKLHV

�

© SAP AG MDM100 2-123

SAP AG 2006

0'0�+LHUDUFKLHV��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� &UHDWH�KLHUDUFK\�WDEOHV�LQ�WKH�0'0�&RQVROH� :RUN�LQ�WKH�KLHUDUFK\�PRGH�RI�WKH�0'0�'DWD�

0DQDJHU� &UHDWH�FDWHJRULHV

�

© SAP AG MDM100 2-124

SAP AG 2006

0'0�+LHUDUFKLHV��%XVLQHVV�6FHQDULR

� 6LQFH�VRPH�RI�\RXU�GDWD�UHIOHFWV�KLHUDUFKLFDO�UHODWLRQV��DV�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RX�ZDQW�WR�NQRZ�KRZ�WR�PRGHO�VRPH�RI�\RXU�GDWD�DV�KLHUDUFKLHV�

�

© SAP AG MDM100 2-125

SAP AG 2006

+LHUDUFK\ ,QWURGXFWLRQ&UHDWLQJ�D�+LHUDUFK\,PSRUWLQJ�D�+LHUDUFK\6SOLWWLQJ�D�)LHOG�LQWR�D�+LHUDUFK\6XPPDU\

+LHUDUFK\ ,QWURGXFWLRQ

�

© SAP AG MDM100 2-126

SAP AG 2006

3XUSRVH�RI�D�+LHUDUFK\�7DEOH¾ $�KLHUDUFK\�WDEOH�LV�D�WDEOH�WKDW�

VWRUHV�GDWD�LQ�D�KLHUDUFKLFDO�VWUXFWXUH�

¾ $�KLHUDUFK\�WDEOH�RUJDQL]HV�LQIRUPDWLRQ�LQ�D�KLHUDUFK\��ZKHUH�HDFK�QRGH�LV�UHODWHG�WR�D�SDUHQW�QRGH�

¾ $�KLHUDUFK\�WDEOH�FDQ�EH�XVHG�OLNH�D�IODW�ORRNXS�WDEOH�LI�\RX�ZRXOG�OLNH�WR�DUUDQJH�WKH�FRQWHQWV�LQ�DQ�RUGHU�RWKHU�WKDQ�DVFHQGLQJ��GHIDXOW�IRU�IODW�WDEOH��

¾ +LHUDUFK\�WDEOHV�FDQ�EH�XVHG�WR�UHODWH�DQ\�KLHUDUFK\�WR�WKH�PDLQ�WDEOH�LQ�WKH�UHSRVLWRU\��IRU�H[DPSOH��81636&�

� ¿ ®�¤ �¢�¦ª�P«' =¤ �®�¨¶À6 E«®�¦�«C°�¦ªÁP°��A¦6©ZÂ� E¨«C®�¦¬Àf¢C°EÃ�¤ Â�¢'¨ÄÅ��¦Z¢

�

� A hierarchy table organizes information in a hierarchy, where each node is related to a parent node (even if the only parent is the root) and may also be related to sibling nodes and/or child nodes. The main table in an MDM repository typically contains some fields whose data may be hierarchical in nature.

� Most of the hierarchy tables used in an MDM repository contain lookup information for fields in the main table.

� A single category must be able to appear in multiple places within the hierarchy. For example, in an MDM repository of product information, a Printer Accessories category might be placed under both a Printers category and an Accessories category.

� MDM supports hierarchies with an unlimited number of parent/child levels. � 1RWH: A hierarchy table is useful even when it is flat (that is, only leaf nodes below the root)

because it stores the ordered sequence of sibling records, allowing you to override the unordered sequence of values in a flat table and put the values in a fixed order.

© SAP AG MDM100 2-127

SAP AG 2006

+LHUDUFK\�7DEOHV

Æ $�KLHUDUFK\�WDEOH�W\SLFDOO\�FRQWDLQV�D�UHODWLYHO\�VPDOO�QXPEHU�RI�ORRNXS�UHFRUGV�FRPSDUHG�WR�WKH�QXPEHU�RI�PDLQ�WDEOH�UHFRUGV��

Æ 7KH�UHODWLRQVKLS�EHWZHHQ�PDLQ�WDEOH�UHFRUGV�DQG�KLHUDUFK\�ORRNXS�WDEOH�UHFRUGV�LV�W\SLFDOO\�PDQ\�WR�RQH��RU�SHUKDSV�PDQ\�WR�IHZ��LI�WKH�ORRNXS�ILHOG�LV�PXOWL�YDOXHG��

Æ ,W�LV�XVHG�DV�D�YDOLG�WDEOH�WKDW�IDFLOLWDWHV�GDWD�HQWU\�DQG�GULOOGRZQ�VHDUFK��ZKHUH�HDFK�ORRNXS�WDEOH�UHFRUG�UHSUHVHQWV�D�YDOLG�ORRNXS�YDOXH�IURP�ZKLFK�WKH�XVHU�FDQ�VHOHFW�GLUHFWO\�DQG�WKH�OLVW�RI�ORRNXS�YDOXHV�FDQ�EH�OLPLWHG�E\�PDLQ�WDEOH�VHDUFK�UHVXOWV��

1RWH��7KH�DERYH�GHWDLOV�DSSO\�WR�DOO�ORRNXS�WDEOHV��IODW��KLHUDUFK\��DQG�WD[RQRP\��

6XE�FDWHJRU\

&DWHJRU\

�

� All lookup tables in an SAP MDM repository are sub-tables, but not all sub-tables are used as lookup tables. There are a number of subtle differences among the different types of lookup tables.

� When a grid contains a hierarchy column, none of its columns will be sortable. However, the hierarchy column is automatically treated as the sorted column for typeahead seek purposes, allowing you to use typeahead seek on it.

© SAP AG MDM100 2-128

SAP AG 2006

+LHUDUFK\�&DSDELOLWLHV

� 1RQ�XQLTXH�QRGH�QDPHV DUH�VXSSRUWHG�LI�WKHUH�LV�QRW�D�VLEOLQJ�QRGH�E\�WKH�VDPH�QDPH�

� &KLOG�QRGHV�FDQ�EH�KLGGHQ LI�WKH�KLHUDUFK\�LV�QRW�XVHG�IRU�D�IDPLO\�

� 0HUJLQJ DQG�SDUWLWLRQLQJ RI�QRGHV�LV�VXSSRUWHG�� 5HQDPLQJ RI�QRGHV�LV�VXSSRUWHG�� 1RGH�FDQ�EH�DOLDVHG WR�JURXS�REMHFWV�HYHQ�ZKHQ�VHDUFKLQJ�

LQ�GLIIHUHQW�WUHHV�� 7KH�KLHUDUFK\�RUGHU LV�FRQWUROOHG�PDQXDOO\�DQG�FDQ�EH�

FKDQJHG�� 'UDJ�DQG�GURS WHFKQRORJ\�DOORZV�WKH�PRYHPHQW�RI�QRGHV�

�

� A family is a grouping used in publishing.

© SAP AG MDM100 2-129

SAP AG 2006

2WKHU�7DEOHV�8VLQJ�+LHUDUFKLHV

� 2WKHU�WDEOHV�WKDW�XVH�KLHUDUFKLHV�LQ�0'0�LQFOXGH��½ 7D[RQRP\ WDEOHV�KDYH�DGGLWLRQDO�GHWDLOV��DWWULEXWHV��DERXW�HDFK�FDWHJRU\�

½ 7KH�0DVNV WDEOH�DFWV�OLNH�D�VWHQFLO�LQ�WKDW�LW�EORFNV��³PDVNV´��DOO�PDLQ�WDEOH�UHFRUGV�IURP�YLHZ�H[FHSW�WKH�GHILQHG�VXEVHW�RI�UHFRUGV�WKDW�DUH�LQFOXGHG�LQ�WKH�PDVN�

½ )DPLOLHV WDEOHV�DUH�XVHG�WR�IXUWKHU�SDUWLWLRQ�PDLQ�WDEOH�UHFRUGV�LQ�HDFK�FDWHJRU\�LQWR�VPDOOHU�JURXSV�EDVHG�RQ�WKH�YDOXHV�RI�RWKHU�ILHOGV�DQG�RU�DWWULEXWHV�

�

� Other hierarchy tables in MDM include taxonomy tables, the Masks table, and the Families table. MDM supports hierarchies with an unlimited number of parent/child levels.

© SAP AG MDM100 2-130

SAP AG 2006

&UHDWLQJ�D�+LHUDUFK\


�

© SAP AG MDM100 2-131

SAP AG 2006

¾ 7KH�KLHUDUFK\�WDEOH�LWVHOI�DQG�WKH�ILHOGV�RI�HDFK�RI�LWV�FDWHJRULHV�DUH�FUHDWHG�DQG�GHILQHG�LQ�WKH�0'0�&RQVROH�

¾ $�KLHUDUFK\�WDEOH�LV�LGHQWLILHG�ZLWK�DQ�LFRQ�

&UHDWLRQ�RI�+LHUDUFK\�7DEOHV

¾ 7KH�1DPH ILHOG�LV�XVHG�DV�WKH�SULPDU\�GLVSOD\�ILHOG��ZKLFK�FDQQRW�EH�XQVHOHFWHG�DV�D�GLVSOD\�ILHOG��RU�LWV�ZLGWK�VHW�WR�OHVV�WKDQ��EHFDXVH�D�KLHUDUFK\�WDEOH�PXVW�KDYH�DW�OHDVW�RQH�IL[HG�ZLGWK�WH[W�GLVSOD\�ILHOG�

�

� Minimally, a hierarchy table needs a 1DPH field, but can also have other fields.

© SAP AG MDM100 2-132

SAP AG 2006

&UHDWLRQ�RI�+LHUDUFK\�)LHOG

¾ ,I�D�UHFRUG�FDQ�EH�DVVLJQHG�WR�PRUH�WKDQRQH�KLHUDUFK\�QRGH��VHOHFW�0XOWL�9DOXHG�

¾ 2QFH�WKH�KLHUDUFK\�WDEOH�LV�FUHDWHG��WKH�KLHUDUFK\�ILHOG�PXVW�EH�DGGHG�WR�WKH�UHIHUHQFLQJ�WDEOH�

�

� Once a /RRNXS�>+LHUDUFK\@ field is created, the type and multi-valued properties cannot be changed. A new field will need to be created.

© SAP AG MDM100 2-133

SAP AG 2006

&UHDWLRQ�RI�+LHUDUFK\�&DWHJRULHV

� 1RZ�WKDW�WKH�+LHUDUFK\�WDEOH�KDV�EHHQ�FUHDWHG��WKHUH�DUH�WZR�GLIIHUHQW�ZD\V�WR�SRSXODWH�WKH�WDEOH�ZLWK�FDWHJRULHV��QRGHV��½ 0DQXDO�FUHDWLRQ�RI�WKH�KLHUDUFKLFDO�VWUXFWXUH�LQ�WKH�0'0�'DWD�0DQDJHU

½ &UHDWLRQ�RI�D�KLHUDUFK\�GXULQJ�WKH�LPSRUW�SURFHVV�LQ�WKH�0'0�,PSRUW�0DQDJHU

�

© SAP AG MDM100 2-134

SAP AG 2006

0DQXDO�&UHDWLRQ�RI�&DWHJRULHV��6WHS��

� 2QO\�$GG�&KLOG LV�DYDLODEOH�IURP�WKH�URRW�

� 2QFH�D�FKLOG�LV�FUHDWHG��DGGLWLRQDO�RSWLRQV�DUH�DYDLODEOH��,Q�RXU�H[DPSOH��D�FKLOG�ZDV�DGGHG�WR�WKH�8QLWHG�6WDWHV�

� 7KH�KLHUDUFK\�FDWHJRULHV�DUH�FUHDWHG�DQG�GHILQHG�LQ�WKH�0'0�'DWD�0DQDJHU�LQ�+LHUDUFK\�PRGH�

�

© SAP AG MDM100 2-135

SAP AG 2006

0DQXDO�&UHDWLRQ�RI�&DWHJRULHV��6WHS��

� 7KH�ILQDO�RXWFRPH

� 1H[W��DGG�VLEOLQJV�

�

� When a grid contains a hierarchy column, none of its columns will be sortable. However, the hierarchy column is automatically treated as the sorted column for type-ahead seek purposes, allowing you to use type-ahead seek on it.

© SAP AG MDM100 2-136

SAP AG 2006

,Q�+LHUDUFK\�PRGH�� 5HQDPLQJ� 5HODWHG�ILHOGV

PDLQWHQDQFH� +LGH�GLVSOD\

(DV\�KLHUDUFK\�FKDQJHV�E\�GUDJ�DQG�GURS&KDQJHV�FRQVWUDLQWV�� 'HOHWH�QRGH�RSHUDWLRQ�RQO\�SRVVLEOH�LI�QR�REMHFW�LV�DVVLJQHG� 'HOHWH�RQO\�SRVVLEOH�RQ�OHDI�QRGHV��QR�FRPSOHWH�EUDQFK�

GHOHWLRQ�

+LHUDUFK\�0DLQWHQDQFH�LQ�0'0�'DWD�0DQDJHU

�

© SAP AG MDM100 2-137

SAP AG 2006

)LHOG�$VVLJQPHQW�WR�+LHUDUFK\�7DEOHV

6LQJOH�9DOXHG 0XOWL�� 9DOXHG� %\�VHOHFWLQJ�PXOWLSOH�UHFRUGV��FDWHJRU\�DVVLJQPHQW�FDQ�EH�

GRQH�VLPXOWDQHRXVO\�WR�PRUH�WKDQ�RQH�UHFRUG�

� 2QFH�FDWHJRULHV�DUH�FUHDWHG�ZLWKLQ�D�KLHUDUFK\��WKH�FDWHJRULHV�FDQ�EH�DVVLJQHG�WR�UHFRUGV�

� +LHUDUFK\�ILHOG�DVVLJQPHQW�LV�SHUIRUPHG�LQ�5HFRUG�PRGH�� *R�WR�WKH�KLHUDUFK\�ILHOG�DQG�VHOHFW�D�YDOXH�� $�ILHOG�FDQ�EH�DVVLJQHG�WR�QRQH�RU�PDQ\�KLHUDUFK\�QRGHV�

�

� For proper organization of the records within an MDM repository, a hierarchy lookup field can only be assigned the value of a leaf node in the hierarchy. However, MDM supports inner node assignments indirectly – while preserving the rule that a hierarchy lookup field be assigned only to a leaf node in the hierarchy – using an internal leaf node, a special type of leaf node that represents the internal parent node immediately above it. You can then make inner node assignments to the parent by assigning records to the internal leaf – which acts as a proxy for the parent for assignment purposes – just as you would assign records to any other leaf node.

© SAP AG MDM100 2-139

([HUFLVHV�

8QLW��'DWD�0RGHOOLQJ�7RSLF��+LHUDUFK\�FUHDWLRQ�


• Create hierarchy tables and Data in a repository

You would like to define different locations for your repository.

1-1 Before we start the creation of the repository table, please unload your repository <YourLetter_Case_Study>.

1-1-1 Therefore open your MDM Cosole and unload your repository.

1-2 Create a new table in your repository.

1-2-1 Highlight your repository and add a new table with the following data:

Name = Locations

Code = LC

Description = Locations

Type: Hierarchy

Save data.

1-3 Link this new table to your main table.

1-3-1 Open your main table and add the following field: Name: location

Type = Lookup [Hierarchy]

Multivalued = No

Lockup Table = Locations

Save data.

1-4 Load your repository and start your data manager.

1-4-1 Select hierarchy mode and your table locations. Create the following location hierarchy:

© SAP AG MDM100 2-140

United states

Æ California

ÆSanta Clara Country

Æ San Jose

Æ Milpitas

Æ Campbell

ÆAlameda Country

Æ Fremont

Æ Hayward

1-5 Once the hierarchy is created then populate a couple records with data.

© SAP AG MDM100 2-141

SAP AG 2006

,PSRUWLQJ�D�+LHUDUFK\


�

© SAP AG MDM100 2-142

SAP AG 2006

6RXUFH�+LHUDUFK\�3DUWLWLRQLQJ�6FHQDULR

Three-Phase Motors

Two-Phase Motors

One-Phase Motors

Unmounted Bearings

Mounted Bearings

Dot Matrix PrintersMotors

Inkjet PrintersBearings

Laser PrintersPrinters

Category?CATEGORY

Ç�ÈvÉ�Ê�Ë ÌvÍvÊ�Ë Î�Ì�ÏÐ Î�Ñ�ÒyÓ9È'Ï

Three-Phase MotorsThree-PhaseMotors

Two-Phase MotorsTwo-PhaseMotors

One-Phase MotorsOne-PhaseMotors

Un-mounted Bearings

Un-mountedBearings

Mounted BearingsMountedBearings

Dot Matrix PrintersDot MatrixPrinters

Inkjet PrintersInkjetPrinters

Laser PrintersLaserPrinters

Ô�ÕNÖ ×=ØwÙvÚ ÛÜÝ�Þ�ß�Ô�à�á�âwã"äCå9æÔ�à�á�â9ã'äCå9æÇ�È9É�Ê�Ë ÌvÍ9Ê�Ë Î�Ì�ÏÐ Î�Ñ�ÒyÓvÈ'Ï

6FHQDULR�¾ $Q�LQGLYLGXDO�VRXUFH�ILHOG�

&$7(*25<�GRHV�QRW�FRQWDLQ�VXIILFLHQW�LQIRUPDWLRQ�WR�EH�PDSSHG�E\�LWVHOI�WR�WKH�PRUH�GHWDLOHG�GHVWLQDWLRQ�ILHOG�

¾ 0LVVLQJ�GHWDLO�LQ�WKH�VRXUFH�ILHOG��ZKLFK�WRJHWKHU�ZLWK�&$7(*25<�FRUUHVSRQGV�WR�GHVWLQDWLRQ�ILHOG�&DWHJRU\��

6ROXWLRQ¾ &RPELQH�&$7(*25<�DQG�

68%&$7(*25<�ZLWK�SDUWLWLRQLQJ�SULRU�WR�ILHOG�PDSSLQJ�DV�D�FRPELQDWLRQ�ILHOG�WR�&DWHJRU\�

,W�LV�QRW�XQFRPPRQ�IRU�WKH�VRXUFH�ILOH�WR�EH�VWUXFWXUHG�GLIIHUHQWO\�WKDQ�WKH�GHVWLQDWLRQ�

�

� To deal with the challenge of different source and destination field structures, MDM’ s generalized partitioning mechanism allows you to combine two or more fields into field combinations and underlying values into a corresponding set of value combinations.

� In each case, you create field combinations by partitioning either an entire field or just an individual value by another field or attribute. And multiple partitions can be nested (creating hierarchy among the value combinations) or combined (merging the value combinations).

� Partitioning is one of the most powerful features of the MDM Import Manager. It is the mechanism that allows you to arbitrarily restructure electronic source data and rationalize it against destination data that has an entirely different structure.

© SAP AG MDM100 2-143

SAP AG 2006

3DUWLWLRQLQJ�D�)LHOG�E\�0XOWLSOH�)LHOGV�$WWULEXWHV

�� 6HOHFW�WKH�ILHOG�RU�YDOXH�QRGH�\RX�ZDQW�WR�SDUWLWLRQ�

�� &OLFN�RQ�WKH�3DUWLWLRQ�)LHOG�9DOXH�WDE�WR�PDNH�LW�WKH�DFWLYH�WDE��7KLV�WDE�OLVWV�DOO�WKH�LWHPV�E\�ZKLFK�\RX�FDQ�SDUWLWLRQ�WKH�VHOHFWHG�QRGH�LQ�HDFK�WUHH��UHIHU�WR�QH[W�VOLGH��

�� 6HOHFW�WKH�LWHPV�E\�ZKLFK�\RX�ZDQW�WR�SDUWLWLRQ�WKH�VHOHFWHG�QRGH�

�� &OLFN�RQ�WKH�$GG�EXWWRQ�DQG�FKRRVH�IURP�WKH�FDVFDGLQJ�PHQX�ç è)é�é¬ê"ë¹ìríCé6î ï�î éð�êCñç è)é�é¬ê"ëòÅó�ôªõ�îdí"ê'öNî ó6í

�� 0'0�SDUWLWLRQV�WKH�VHOHFWHG�QRGH�E\�WKH�VHOHFWHG�LWHPV��HLWKHU�LQGLYLGXDOO\�RU�VLPXOWDQHRXVO\��

�

© SAP AG MDM100 2-144

SAP AG 2006

0XOWLSOH�3DUWLWLRQV

� :KHQ�SDUWLWLRQLQJ�D�QRGH�E\�PRUH�WKDQ�RQH�ILHOG�RU�DWWULEXWH��HDFK�SDUWLWLRQ�LV�DSSOLHG�VHTXHQWLDOO\�

� 7KH�ILUVW�SDUWLWLRQ�LV�DSSOLHG�WR�WKH�OHDI�YDOXH�QRGH�RU�WR�HDFK�OHDI�YDOXH�QRGH�EHQHDWK�LW�WKDW�LQKHULWV�WKH�SDUWLWLRQ�WR�FUHDWH�DGGLWLRQDO�FKLOG�YDOXH�QRGHV�

� 7KH�VHFRQG�SDUWLWLRQ�LV�WKHQ�DSSOLHG�WR�WKH�QHZO\�FUHDWHG�OHDI�YDOXH�QRGHV�EHQHDWK�LW�WKDW�LQKHULW�WKH�SDUWLWLRQ�WR�FUHDWH�DGGLWLRQDO�FKLOG�YDOXH�QRGHV��

�

� You can have any number of partitioning nodes.

© SAP AG MDM100 2-145

SAP AG 2006

1HVWLQJ�� %XLOGLQJ�+LHUDUFKLHV�IURP�)LHOGV

)LHOG�³0IJU��´ LV�VHOHFWHG�LQ�6RXUFH�+LHUDUFK\�SDQH��WKLV�EHFRPHV�WKH�URRW�QRGH�LQ�WKH�SDUWLWLRQ�)LHOG�³0IJU��´ LV�DGGHG�WR�WKH�SDUWLWLRQ�RQ�WKH�3DUWLWLRQ�)LHOG�WDE

$GGLQJ�ILHOG�³0IJU��´�WR�WKH�SDUWLWLRQ�DGGV�DQRWKHU�OHYHO127(��3DUWLWLRQV�DUH�³LQKHULWHG´�IURP�RQH�OHYHO�GRZQ�WR�WKH�QH[W�DV�LQGLFDWHG�E\�WKH�,1+(5,7�FKHFNER[�DW�WKH�ERWWRP�RI�WKH�3DUWLWLRQ�WDE�

�

© SAP AG MDM100 2-146

SAP AG 2006

,QKHULWDQFH�LQ�0'0�

� :KHQ�SDUWLWLRQLQJ�DQ�LQWHUQDO�QRGH��HDFK�RI�WKH�FKLOG�QRGHV�LQKHULWV�WKH�SDUHQW¶V�SDUWLWLRQV��HDFK�RI�LWV�FKLOG�QRGHV�LQKHULWV�WKH�LQKHULWHG�SDUWLWLRQV��XQWLO�WKH�SDUWLWLRQV�DUH�LQKHULWHG�E\�DQG�DSSOLHG�WR�D�OHDI�QRGH��

� :KHQ�GLUHFWO\�SDUWLWLRQ�DQ\�LQWHUQDO�QRGH�RU�D�OHDI�YDOXH�QRGH��WKH�LQKHULWDQFH�RI�SDUWLWLRQV�IURP�QRGHV�DERYH�LW�LQ�WKH�KLHUDUFK\�LV�EURNHQ��DQG�WKH�YDOXH�QRGH�LV�SDUWLWLRQHG�RQO\�E\�WKH�ILHOGV�DQG�RU�DWWULEXWHV�VSHFLILHG�GLUHFWO\�IRU�WKDW�QRGH��

� ,QKHULWDQFH�FDQ�EH�RYHUULGGHQ�IRU�DQ\�QRGH�E\�GLUHFWO\�SDUWLWLRQLQJ�LW�LQ�WKH�KLHUDUFK\��0RUHRYHU��DQ\�FKLOG�RI�WKH�GLUHFWO\�SDUWLWLRQHG�QRGH�WKHQ�LQKHULWV�WKH�SDUWLWLRQV�RI�WKH�QRGH�XQOHVV�WKH�SDUWLWLRQLQJ�LQIRUPDWLRQ�RI�WKH�FKLOG�QRGH�LV�LWVHOI�GLUHFWO\�SDUWLWLRQHG��

�

� An internal node is a node that has at least one child node.

© SAP AG MDM100 2-147

SAP AG 2006

5HVWRUH�,QKHULWDQFH

'LUHFWO\�SDUWLWLRQLQJ�DQ�LQWHUQDO�QRGH�RU�D�OHDI�QRGH�EUHDNV�WKH LQKHULWDQFH�IRU�WKDW�QRGH��<RX�FDQ�UHVWRUH�WKH�LQKHULWDQFH�IRU�WKDW�QRGH�

÷�Ë Ì�ø�ù+Î�ÊZË Ì�ù�Ë Ó9Í�ÊdÈ9Éú+ÒyÎ�øpÈ�Ì_ûEÌvÎ�Ì�ü�Ë Ì'ý9È+Ò�Ë ÊdÈ�ù+þÿ Í�Ò4Ê�Ë Ê�Ë Î�Ì

&OLFNLQJ�RQ�WKH�1RGH�DQG�VHOHFWLQJ�WKH�,QKHULW�FKHFNER[�RQ�WKH�3DUWLWLRQLQJ�WDE�UHVWRUHV�WKH�LQKHULWHG�SDUWLWLRQ�V��DQG�UHPRYHV�WKH�SLQN�GRW�

�

� To restore inheritance for a node 1. In the appropriate hierarchy tree, select the node for which you want to restore inheritance. 2. If necessary, click on the Partition Field/Value tab to make it the active tab. 3. Check the Inherit checkbox. 4. SAP MDM restores the inheritance to the selected node.

© SAP AG MDM100 2-148

SAP AG 2006

(;(5&,6(�² ,PSRUW�D�+LHUDUFK\

� ,Q�WKH�H[HUFLVH��\RX�ZLOO�LPSRUW�D�QHZ�KLHUDUFK\�ZKLFK�LV�D�IODW�PXOWLSOH�ILHOG�KLHUDUFK\�LQ�\RXU�VRXUFH�ILOH�

� <RX�ZLOO�XWLOL]H�\RXU�NQRZOHGJH�RI�KLHUDUFKLHV�DQG�WKH�QHZ�LPSRUW�IHDWXUHV�\RX�ZHUH�MXVW�VKRZQ�LQ�WKH�SUHYLRXV�VOLGHV�

� 3URFHHG�WR�WKH�H[HUFLVH�IROORZLQJ�WKH�LQVWUXFWRU¶V�GLUHFWLRQV�

�

© SAP AG MDM100 2-149

SAP AG 2006

6XPPDU\


�

© SAP AG MDM100 2-150

SAP AG 2006

0'0�%XVLQHVV�&RQWHQW

� 6DPSOH�KLHUDUFKLHV�FDQ�EH�IRXQG�LQ�WKH�IROORZLQJ�EXVLQHVV�SDFNDJHV�

� %XVLQHVV�3DUWQHU��5HJLRQV� 0DWHULDO��81636&�&DWHJRULHV� 3URGXFW��&ODVV�+LHUDUFKLHV��&DWHJRU\�+LHUDUFKLHV��3URGXFW�+LHUDUFKLHV

�

� Additional hierarchy tables can be added to all repositories. � There is no limit to the number of hierarchy tables in a repository. � Product package has 3 hierarchies. Usually only one of the three is used but all have been supplied to

help facilitate the implementation.

© SAP AG MDM100 2-151

SAP AG 2006

+LHUDUFK\�YV��)ODW�/RRNXS�7DEOH

Unchangeable in Data Manager

FlexibleStructure

Within nested tablesWithin all levels of the hierarchy

Search

Ascending and descendingManually definedOrder

Lookup table(s) within lookup table

Any number of levelsLevels

Repository unloaded (schema changes in MDM Console)

Repository loaded (users can maintain it)

Maintenance

)ODW�/RRNXS+LHUDUFK\'LIIHUHQFHV

� 7KLQN�DERXW�KRZ�WKH�ORRNXS�WDEOH�ZLOO�EH�XVHG�� 'R�\RX�ZDQW�WR�DOORZ�XVHUV�WR�PDLQWDLQ�HQWULHV�ZLWK�GLIIHUHQW�DXWKRUL]DWLRQV"

� 'R�\RX�ZDQW�VSHFLILF�RUGHULQJ"

�

� Once a repository is loaded, flat lookup tables can not be changed without unloading the repository. � Think about a hierarchy table even if you have a flat hierarchy, because it enables you to order

entries so that they are fixed.

© SAP AG MDM100 2-152

SAP AG 2006

0'0�+LHUDUFKLHV��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� &UHDWH�KLHUDUFK\�WDEOHV�LQ�WKH�0'0�&RQVROH� :RUN�LQ�WKH�KLHUDUFK\�PRGH�RI�WKH�0'0�'DWD�

0DQDJHU� &UHDWH�FDWHJRULHV

�

© SAP AG MDM100 2-153

�([HUFLVHV�

8QLW�� 0'0�6FHQDULR��,PSRUW�D�+LHUDUFK\�

7RSLF��0'0�+LHUDUFK\�7DEOHV�


• &UHDWH�KLHUDUFK\�WDEOHV�LQ�WKH�0'0�&RQVROH�• :RUN�LQ�WKH�KLHUDUFK\�PRGH�RI�WKH�0'0�'DWD�0DQDJHU�

3XUSRVH�This script walks through the process of creating a hierarchy and the importing of the node values. We will then import the hierarchy data for each record.

6-1 2SHQ�5HSRVLWRU\�DQG�$GG�7DEOH Open your Case_Study repository and make sure it is unloaded.

6-1-1 Create a new table called Manufacturer-Hierarchies

6-1-2 Then click on the table Manufacturer-Hierarchies and add a text field of width=20 called Manufacturer Phone.

© SAP AG MDM100 2-154

6-1-3 Now link the main table to the Manufacturers-Hierarchies.

Notice that there is no Lookup [Hierarchy] (multi-valued) from the Type pull down menu. Select Lookup [Hierarchy] from Type and it will become multi-valued when you select Multi-Valued=Yes.

6-2 ,PSRUW�+LHUDUFK\

The import of the Manufacturer Hierarchy nodes will be performed first, then the item records with hierarchy information will be imported.

6-2-1 Load your repository and start the Import Manager

Use Remote System: NewYork�File name: Case_Study_Hierarchy.xls

6-2-2 Select source: 0)+LHU� and destination: 0DQXIDFWXUHU�+LHUDUFKLHV�

© SAP AG MDM100 2-155

6-2-3 Go to 3DUWLWLRQ�)LHOG��9DOXH�WDE�VWULS and

6-2-3-1 Select 0IJU�� in the Source Hierarchy pane on the left hand side.

6-2-3-2 Using the $GG function and add Mfgr(2) and Mfgr(3) to Mfg(1)

��

6-2-4 Go to tab strip

6-2-4-1 Map the field in the upper window: Mfgr(1) (Partition) from OHIW�KDQG�VLGH with Name [DF]�on the ULJKW�KDQG�VLGH�

© SAP AG MDM100 2-156

6-2-4-2 Map the values in the lower window.

Select all nodes on the�OHIW�KDQG�VLGH� Highlight the Manufacturer Hierarchy’ s root node

��0DQXIDFWXUHU�+LHUDUFK\! on the ULJKW�KDQG�VLGH and click $GG��Æ�$GG�%UDQFK�DV�&KLOG.

If the Add button is grayed out, try collapsing all nodes in the Source values before selecting.

Result will be:

6-2-5 Select tab strip

Select 1DPH�as the matching field. Select &UHDWH as Default Import action

6-2-6 Select�tab strip

6-2-6-1 Save your Map: 0DQXI�+LHUDUFKLHV

6-2-6-2� Execute��

6-2-7 Close the Import Manager.

© SAP AG MDM100 2-157

6-3 ,PSRUW�+LHUDUFK\�'DWD

With the hierarchy node values now imported into your repository, you can now import in the hierarchy data for your items. We will utilize the Items Map that we saved in first Import Exercise.

6-3-2 Close the Import Manager and then re-open your repository with the Import Manager. This will allow the Import Manager to read the previously imported hierarchy correctly.

6-3-3 Go to )LOH�!�2SHQ« and select the Items Map.

6-3-4 Go to Tab strip

6-3-5 Now most fields will be mapped for you, leaving just the Manufacturer field to map. Select 0DQXIDFWXUHU and map it to 0DQXIDFWXUHU�+LHUDUFK\.

6-3-6 At the bottom of the screen click the Automap to map the values.

6-3-7 Select tab strip

6-3-8 Make sure that Product ID [DF] is the matching field.

6-3-9 Under Default import action set the 9 Single records to 8SGDWH��1XOO�)LHOGV�2QO\�


6-3-11 ([HFXWH �

© SAP AG MDM100 2-158

6-4 5HYLHZ�5HVXOWV�LQ�WKH�'DWD�0DQDJHU Confirm the status and review the import results. Review the Hierarchy structure values and the data you imported

6-4-1 Record Mode

�� 6-4-2 Notice how Product ID = 109 which had only Name and Pricing data now has

all the fields populated.

6-4-3 Switch to�Hierarchy Mode

�


SAP AG 2006

8QLW��$GYDQFHG�0'0�)HDWXUHV��,PSRUW�0DQDJHU�$GYDQFHG




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�


SAP AG 2006

&RQWHQWV�� 0'0�,PSRUW�0DQDJHU�$GYDQFHG�)HDWXUHV

� &ORQH��DGG��DQG�UHQDPH�ILHOGV� -RLQ�WDEOH� &RQYHUWLQJ�RI�YDOXHV� 6SOLWWLQJ�ILHOGV

0'0�,PSRUW�0DQDJHU�$GYDQFHG�)HDWXUHV

�


SAP AG 2006

0'0�,PSRUW�0DQDJHU�$GYDQFHG�)HDWXUHV��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� ([SODLQ�WKH�'HWDLOHG�)XQFWLRQV�IRU�PDSSLQJ�DQG�

DGYDQFHG�WUDQVIRUPDWLRQ�ZKHQ�LPSRUW�GDWD�IURP�YDULRXV�VRXUFHV�

�


SAP AG 2006

0'0�,PSRUW�0DQDJHU�$GYDQFHG )HDWXUHV��%XVLQHVV�6FHQDULR

� $V�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RX�ZDQW�WR�LPSRUW�FRPSOH[�GDWD�LQWR�\RXU�UHSRVLWRULHV�XVLQJ�WKH�,PSRUW�0DQDJHU�

� %HFDXVH�RI�WKH�YDULHG�IRUPV�DQG�IRUPDWV�RI�GDWD�ZKLFK�QHHG�WR�EH�LPSRUWHG��\RX�QHHG�WR�XQGHUVWDQG�PRUH�DGYDQFHG�IHDWXUHV�RI�WKH�,PSRUW�0DQDJHU�WR�DFKLHYH�LPSRUW�HIILFLHQF\�

�


SAP AG 2006

&RQYHUWLQJ 9DOXHV

2YHUYLHZ&ORQLQJ�DQG�$GGLQJ�)LHOGV-RLQLQJ�D�7DEOH&RQYHUWLQJ�9DOXHV9DOXH�)LHOG�3DUWLWLRQLQJ

&RQILJXUDWLRQ 2SWLRQV6XPPDU\

6SOLWWLQJ�D�)LHOG�LQWR�D�+LHUDUFK\

�


SAP AG 2006

0'0�,PSRUW�0DQDJHU�$UFKLWHFWXUH�2YHUYLHZ

�� 7DEOHV�

9LHZV�)LOHV

"!$#%& '(*)�),+"- /.10 �

23(4- � ) %56'78#9 %6%�'�:6:;�< %�'=&

> ?A@�BDCFEHGJILKMIONLP�CRQ�SDKOT=EVU BLK,WLXY ),Z,[ !�%�' � !\'�]M^ '�_Y � #=`a& '*b Z ^ c�:Y � Z c�%6#�de'=c6#�dF^ Z cY )1f & ^ dY � #a!$dg^ dh^ Z cY i ( � Z c�]�'a!$:a^ Z cY j ^ '=& k � l #a& [ ' ( # faf ^ c6m

n ^ c�%& [ k�^ c�mpo1^ '=!\#a!�%5^ '�:qY ( #6de%=5sr�'�% Z !�k:Y .�'�:6dF^ c6#6dg^ Z c � !�'�]a^ '�_

t ^ c6u6v

t ^ c�u6v � t ^ c�w�x �iLy � 2

64/'DWD

),+"-4) '=! ]�'=! � "!$#%& 't ^ c y �=� iDy � 2

0'06HUYHU0'06HUYHU0'06HUYHU0'06HUYHUr�' f�Z :a^ d Z ! zr�' f�Z :a^ d Z ! z

��\� �

,PSRUW0DQDJHU,PSRUW0DQDJHU

�

� In the Import Manager, preparation of a source data file may include some or all of the following steps: y Join tables and then look up fields from secondary tables into the primary source table, to combine

information from multiple tables and create virtual extended source records for import. y Split fields, to break delimited field values into a hierarchy or into multiple fields, for subsequent

field-level processing on individual field values in each new field. y Partition fields, to restructure source data by combining fields into field combinations, for

subsequent field-level processing on value combinations rather than individual field values. y Map fields, the most traditional step in the import process, to identify the destination field for each

source field, and also the type of mapping and conversion required for the underlying data values. y Map and convert values, to transform and normalize source data by eliminating differences

between source and destination values, converting data types, and creating measurement values. y Match records, to specify key fields for identifying existing records that match the source records,

and whether new records should be created and existing records should be updated or replaced.


SAP AG 2006

&RQYHUWLQJ 9DOXHV




�


SAP AG 2006

&ORQLQJ�)LHOGV

&ORQH�)LHOGV� &ORQH��7R�SHUIRUP��GLIIHUHQW�RSHUDWLRQV

{ 0DSSLQJ��UHFRUG�WR�WZR�GHVWLQDWLRQ�UHFRUGV{ 0DSSLQJ�DQ�RULJLQDO�VRXUFH�YDOXH�LQWR�WKH�UHSRVLWRU\�DQG�WKHQ�DOVR�QHHGLQJ�WR�SDUWLWLRQ�RU�VSOLW�WKDW�YDOXH�RU�RWKHU�GHVWLQDWLRQ�ILHOGV«

�

� If you need to perform two different operations on a single source field, such as: (1) mapping it to two different destination fields; or (2) mapping it to one destination field by itself and also partitioning it by another source field, you can clone the field to create a copy of the original field.

� When you use the Clone Field command to create a clone of a source field, MDM creates a duplicate of the original field that contains the same data value for each source record. You can then perform subsequent processing on the clone field just as if it were an original field in the source data.

� 127(��SAP MDM cloning, adding, or splitting of fields – require that the original data source be updated with the new fields and the corresponding data values for each record.

� This update is performed automatically when you create the new fields within the MDM Import Manager but only if the data source is updateable.

Conditions under which a source is updateable: � Source type. The source Type must permit the MDM Import Manager to update its schema and insert

the additional fields of data. � Media. The media on which the data source resides must itself be updateable. If the media on which

the data source resides is read-only, such as a CD-ROM, the data source cannot be updated. � Permissions. You must have the proper file system permissions to update the file or the proper

DBMS permissions to update the schema of the database. � Read-only option. You cannot have checked the Read-Only option, which prevents SAP MDM from

updating the data source even if the other conditions would otherwise permit it.


SAP AG 2006

$GGLQJ�)LHOGV

$GG�(PSW\�)LHOGV� $GG��&RPSHQVDWLQJ�IRU�PLVVLQJ�VRXUFH�YDOXHV

{ $GG�D�ILHOG�ZKLFK�KDV�D�FRQVWDQW�YDOXH�IRU�DOO�UHFRUGV{ 8VH�LQ�FRPELQDWLRQ�ZLWK�WKH�,PSRUW�3UHYLHZ�WDE�WR�SURYLGH�YDOXHV�IRU�PLVVLQJ�UHFRUGV�ZKHUH�WKH�GHVWLQDWLRQ�YDOXH�YDULHV

�

� You can add to the source data an empty field with the single NULL value in its list of distinct values. For example, if the source data is missing a field for which all of the values would be the same (such as when data from a particular manufacturer is missing the manufacturer field), you can add a field, and then use the Map Fields/Values tab to map the single NULL value to the corresponding destination value.


SAP AG 2006

5HQDPLQJ�DQG�'HOHWLQJ�)LHOGV

� $OO�ILHOG�ZKHQ�ILUVW�FORQHG��DGGHG��RU�VSOLW�ZLOO�GLVSOD\�WKH�RULJLQDO�ILHOGQDPH�LQ�LWDOLF�

� $OO�ILHOGV�FDQ�EH�UHQDPHG��EXW�EH�DZDUH�WKDW�WKH�ILHOG�QDPH�LV�FXUUHQWO\�WKH�RQO\�UHIHUHQFH�WR�LWV�RULJLQDO�VRXUFH�

�

� Fields that you add to the Source Hierarchy tree are automatically named based on the original field name and the command that you use to create the field. You can then rename the field.


SAP AG 2006

-RLQLQJ D�7DEOH




�


SAP AG 2006

'HILQLWLRQ�RI�7DEOH�-RLQV�YV��/RRNXSV

� 7KH�0'0�,PSRUW�0DQDJHU�LPSRUWV�UHFRUGV�IURP�D�VLQJOH�WDEOH�LQWR�D�VLQJOH�WDEOH�DW�DQ\�RQH�WLPH�

� 7DEOH�-RLQV$�MRLQ�FRPELQHV�LQIRUPDWLRQ�IURP�WKH�UHFRUGV�LQ�WZR�WDEOHV�E\�XVLQJ�WKH�YDOXHV�LQ�D�SDLU�RI�PDWFKLQJ�ILHOGV�WR�PDWFK�UHFRUGV�LQ�WKH�WZR�WDEOHV�

� 7DEOH�/RRNXSV$�ORRNXS�LV�D�W\SH�RI�MRLQ�WKDW�XVHV�WKH�YDOXH�RI�WKH�SULPDU\�PDWFKLQJ�ILHOG�IRU�HDFK�UHFRUG�LQ�D�SULPDU\�WDEOH�WR�PDWFK�WKH�FRUUHVSRQGLQJ�UHFRUG�ZLWK�WKH�VDPH�YDOXH�IRU�WKH�ORRNXS�PDWFKLQJ�ILHOG�LQ�D�ORRNXS�WDEOH�DQG�WKHQ�³ORRNV�XS´�DGGLWLRQDO�LQIRUPDWLRQ�IURP�RQH�RU�PRUH�ORRNXS�ILHOGV�LQ�WKH�ORRNXS�WDEOH�UHFRUG�LQWR�WKH�SULPDU\�WDEOH�UHFRUG�

�

� For data sources that do not store relationships between tables or do not make them available through a programmatic interface, or to create additional relationships that are not explicitly defined in the data source, the MDM Import Manager allows you to manually define join relationships from a primary table to a lookup table.


SAP AG 2006

3URSHUWLHV�RI�-RLQV

6$3�0'0�-RLQV DUH�WUDQVLWLYH6$3�0'0�DXWRPDWLFDOO\�FUHDWHV�LPSOLFLW�SULPDU\�NH\�DQG�IRUHLJQ�

NH\�PDWFKLQJ�ILHOGV�| :KHQ�FUHDWLQJ�D�ILHOG�LQ�WKH�UHSRVLWRU\�RI�W\SH�/RRNXS| 7KH�YDOXH�RI�WKH�ORRNXS�ILHOG�LV�WKH�YDOXH�V��RI�WKH�GLVSOD\�ILHOG�V��RI�

WKH�ORRNXS�WDEOH�UHFRUG�0'0�,PSRUW�0DQDJHU�XVHV�OHIW�RXWHU�MRLQV�WR�FUHDWHV�WKH�ORRNXS�

H[WHQGHG�WDEOH��| 7KH�³IURP´�WDEOH�DV�WKH�SULPDU\�WDEOH�| 7KH�³WR´�WDEOH�DV�WKH�ORRNXS�WDEOH| 7KH�UHVXOW�WDEOH�LQFOXGHV�DOO�RI�WKH�SULPDU\�WDEOH�ILHOGV�DQG�HDFK�RI�

WKH�ORRNXS�ILHOGV�DQG�DOO�UHFRUGV�RI�WKH�SULPDU\�WDEOH�0'0�,PSRUW�0DQDJHU�DOORZV�\RX�WR�PDQXDOO\�GHILQH�MRLQ�

UHODWLRQVKLSV�IURP�D�SULPDU\�WDEOH�WR�D�ORRNXS�WDEOH�

� Transitive Joins: if Table A is joined to Table B and Table B is joined to Table C, Table C is effectively joined to Table A. The MDM Import Manager automatically detects this condition, displays “transitive join” Table C as the child not only of Table B but also of the joined lookup Table B node that is a child of Table A, and allows “transitive lookups” from Table C into Table A.

Common terminology and description: }

Join Combines record information from multiple tables. }

Matching Fields The pair of fields whose values are used to match records. }

Lookup Uses a join to look up related information from another table. }

Primary Table The table into which fields are looked up. }

Lookup table The table from which fields are looked up. It is the last child of the primary table. }

Primary Matching Field The matching field in the primary table. [Join] appended to the name of the primary matching field. Also added as the first child of the lookup matching field as [From: primary table,primary matching field]

} Lookup Matching Field The matching field in the lookup table. [Join] appended to the name of the lookup

matching field. Also added as the first child of the primary matching field as [From: lookup table,lookup matching field]

} Lookup Field Field looked up from the lookup table into the primary table. Added as child of the

lookup table into the primary table.


SAP AG 2006

6WHSV�RI�7DEOH�-RLQV�

'

%$

&

$� &UHDWHV�D�OLQN�EHWZHHQ�WKH�SULPDU\�PDWFKLQJ�ILHOG�LQ�WKH�SULPDU\ WDEOH�DQG�WKH�ORRNXS�PDWFKLQJ�ILHOG�LQ�WKH�ORRNXS�WDEOH�

%� $SSHQGV�>-RLQ@�WR�WKH�QDPH�RI�HDFK�PDWFKLQJ�ILHOG�LQ�WKH�WUHH�&� $GGV�WKH�FRUUHVSRQGLQJ�PDWFKLQJ�ILHOG�RI�WKH�RWKHU�WDEOH�DV�WKH�ILUVW�FKLOG�RI�HDFK�PDWFKLQJ�ILHOG�'� $GGV�WKH�ORRNXS�WDEOH�DV�WKH�ODVW�FKLOG�RI�WKH�SULPDU\�WDEOH�

�

� Steps needed to be performed to manually join a primary table for table lookup: 1. In the Source Hierarchy tree, select the field node in the primary table from which you want to

establish the join relationship. 2. Right-click on the node and choose Join from the context menu Æ select the lookup table ->

choose the matching key filed Æ system will create a child node at the end of the primary table. � NOTE: You can also drag-and-drop the primary matching field from the primary table onto the

lookup matching field in the lookup table to create the join relationship. � MDM creates the new join relationship and reflects it in the Source Hierarchy tree.


SAP AG 2006

/RRNLQJ�8S�D�)LHOG

3UH�UHTXLVLWH�| $�-RLQ�UHODWLRQVKLS�KDV�EHHQ�HVWDEOLVK�EHWZHHQ�D�SULPDU\�DQG�

ORRNXS�WDEOH�| 0'0�,PSRUW�0DQDJHU�DGGHG�D�FKLOG�QRGH�DW�WKH�HQG�RI�WKH�SULPDU\�

DEOH�&UHDWH�/RRN�8S�)LHOGV�| $W�V\VWHP�FUHDWHG�&KLOG�QRGH�Æ ULJKW�PRXVH�FOLFN��VHOHFW�

³/RRNXS´�Æ FKRRVH�ILHOG�WR�EH�ORRNHG�XS�Æ UHSHDW�DV�QHFHVVDU\�

�

� Once the join relationships have been established, you can look up fields from a lookup table into a primary table, adding the field into the list of primary table fields, and in effect, building an extended virtual record consisting of fields from the primary table and lookup fields from one or more lookup tables.

� When you use the Lookup command to look up a field from a lookup table into the primary table, the You can then perform subsequent processing on the lookup field just as if it were an original field in the source data.


SAP AG 2006

&RQYHUWLQJ 9DOXHV




�


SAP AG 2006

'LVWLQFW�)LHOGV�² 3DUDPHWULF�,PSRUW

| ,Q�FRQMXQFWLRQ�ZLWK�ILHOG�DW�D�WLPH�UDWKHU�WKDQ�UHFRUG�DW�D�WLPH�SURFHVVLQJ��GLVWLQFW�YDOXH�OLVWV�PDNH�SDUDPHWULF�LPSRUW�H[FHSWLRQ�KDQGOLQJ�PXFK�PRUH�HIILFLHQW�EHFDXVH�~ 7KH�QXPEHU�RI�GLVWLQFW�YDOXHV�IRU�HDFK�ILHOG�

LV�GUDPDWLFDOO\�VPDOOHU�WKDQ�WKH�WRWDO�QXPEHU�RI�YDOXHV�

~ (DFK�GLVWLQFW�YDOXH�UHSUHVHQWV�DQG�LV�D�SUR[\�IRU�QRW�RQO\�DOO�LQVWDQFHV�RI�WKH�YDOXH�DFURVV�WKH�HQWLUH�VHW�RI�XQGHUO\LQJ�UHFRUGV��EXW�DOVR�WKH�VXEVHW�RI�UHFRUGV�WKDW�FRQWDLQ�WKH�YDOXH�

~ ([DPLQLQJ�DQG�WKHQ�WUDQVIRUPLQJ�HDFK�VRXUFH�GDWD�YDOXH�PXVW�EH�GRQH�RQO\�RQFH�IRU�HDFK�GLVWLQFW�YDOXH�UDWKHU�WKDQ�RQFH�IRU�HDFK�LQVWDQFH�RI�WKH�YDOXH�

~ 7KH�PD[LPXP�QXPEHU�RI�H[FHSWLRQV�LV�WKH�VXP�UDWKHU�WKDQ�WKH�SURGXFW�RI�WKH�QXPEHU�RI�GLVWLQFW�YDOXHV�LQ�HDFK�PDSSHG�ILHOG�

�

� Parametric Import is a new and radically more efficient approach to importing and transforming data that is conceptually similar to parametric search, as follows: y Parametric search lists the complete set of distinct values for each field or attribute in a repository.

Selecting a value during a drill-down search selects all of the underlying records that contain that value.

y Parametric import lists the complete set of distinct values for each field in the source data. Changing a value as part of the import (by mapping or converting it) changes it in all of the underlying records that contain that value.

� The set of distinct values is meaningful primarily for fields that have a relatively small set of distinct values relative to the total number of records, not for an index or description field, where the values may be unique for each record. The MDM Import Manager warns you before displaying the values if the number of distinct values is greater than 100.


SAP AG 2006

*HQHUDWH�'LVWLQFW�9DOXHV�/LVW

&UHDWLQJ�'LVWLQFW�9DOXHV�OLVWV�HDVHV�H[FHSWLRQ�KDQGOLQJ�� 7RWDO�QXPEHU�RI�YDOXHV�OLVWHG�LV�VLJQLILFDQWO\�GHFUHDVHG� ([DPLQH��WUDQVIRUPDWLRQ�HDFK�YDOXH�RQO\�KDV�WR�EH�GRQH�RQFH� 'LVWLQFW�9DOXHV�DUH�WKH�IRXQGDWLRQ�IRU�SDUWLWLRQLQJ�ILHOGV�YDOXHV*HQHUDOO\�PRVW�XVHIXO�IRU�ORZ�FDUGLQDOLW\�WDEOHV��ZDUQLQJ�IRU�!��

GLVWLQFW�YDOXHV�LQ�D�WDEOH�1RWH��'LVWLQFW�9DOXHV�YLHZ�FDQ�DOVR�EH�DSSOLHG�WR�'HVWLQDWLRQ�+LHUDUFK\

�

� In conjunction with field-at-a-time rather than record-at-a-time processing, distinct value lists make import exception handling much more efficient because:

� The number of distinct values for each field is dramatically smaller than the total number of values. � Each distinct value represents and is a proxy for not only all instances of the value across the entire

set of underlying records, but also the subset of records that contain the value. � Examining and then transforming each source data value must be done only once for each distinct

value rather than once for each instance of the value; and as a result. � The maximum number of exceptions is the sum rather than the product of the number of distinct

values in each mapped field. � Displaying values as nodes in the tree is an optional convenience that allows you to efficiently

familiarize yourself with the set of distinct values for a field (as opposed to browsing multiple occurrences of each value in the Source Preview grid).

� Important Note on Partitioning: � The values and value combinations are automatically added when you partition a field. � By contrast, you must use the Display Distinct Values command to manually add the value nodes

prior to partitioning an individual field value.


SAP AG 2006

9DOXH�0DSSLQJ�1RWDWLRQ�5HIHUHQFH�9DOXHV�*ULG� ,FRQ� 'HVFULSWLRQ�

Value is mapped to an existing destination value.

Value is mapped to multiple existing destination values.

Value is mapped to a new destination value.

Value is mapped to multiple new destination values.

Source

Value is mapped to multiple destination values, some of which are new.

Single source value is mapped to the value.

Multiple source values are mapped to the value.

Single source value is mapped to the new value. Destination

Multiple source values are mapped to the new value.

| %OXH�,FRQV LQGLFDWH�YDOXHV�DGGHG�WR�WKH�UHSRVLWRU\¶V�GRPDLQ�YDOXHV| *UHHQ�,FRQV LQGLFDWH�YDOXHV�PDSSHG�WR�WKH�UHSRVLWRU\¶V�GRPDLQ�

YDOXHV

�


SAP AG 2006

9DOXH�0DSSLQJ�0XOWL�9DOXH�'HVWLQDWLRQ�)LHOGV

«RU�$XWRPDS��(LWKHU�ZD\��0'0�,PSRUW�0DQDJHU�LQGLFDWHV�VRXUFH�PDSSLQJV�ZKHQ�WKH�VRXUFH�ILHOG�LV�KLJKOLJKWHG�

0DS�LQGLYLGXDOO\«

�


SAP AG 2006

'HILQLQJ�&RQYHUWHG�9DOXHV�GXULQJ�,PSRUW

0XOWLSOH�VRXUFH�YDOXHV�FDQ�EH�PDSSHG�LQWR�D�VLQJOH�GHVWLQDWLRQ�YDOXH��,I�PRUH�WKDQ�RQH�YDOXH�LV�PDSSHG�WR�D�GHVWLQDWLRQ��WKHQ�D�GRXEOH�EOXH�V\PERO�ZLOO�EH�VKRZQ�

9DOXHV�ZKLFK�KDYH�EHHQ�DGGHG�IURP�VRXUFH�ZLOO�EH�FUHDWHG�ZKHQ�ZHH[HFXWH�WKH�LPSRUW�

6RXUFH�YDOXHV��9�DQG��[�DUH�PDSSHG�WR��9�LQ�WKH�UHSRVLWRU\��7KH�LFRQ�LQ�WKH�³0DSSHG�FROXPQ´�LQGLFDWHV�WKLV�PXOWL�YDOXH�PDSSLQJ�

�


SAP AG 2006

'DWD�7\SH�&RQYHUVLRQ

| 7KH�GDWD�W\SHV�RI�FRUUHVSRQGLQJ�VRXUFH�DQG�GHVWLQDWLRQ�ILHOGV�PD\�EH�GLIIHUHQW�

| ([DPSOH��ZKHQ�QXPHULF��FXUUHQF\��GDWH��WLPH��RU�%RROHDQ�VRXUFH�GDWD�DUH�HDFK�VWRUHG�DV�WH[W�YDOXHV�ZLWKLQ�WH[W�ILHOGV�

| ,Q�WKHVH�FDVHV��WKH�GDWD�W\SHV�RI�VRXUFH�GDWD�YDOXHV�DUH�DXWRPDWLFDOO\�FRQYHUWHG�ZLWKLQ�WKH�6RXUFH�9DOXHV�JULG�EDVHG�RQ�WKH�GDWD�W\SH�RI�WKH�GHVWLQDWLRQ�ILHOG�WR�ZKLFK�WKH�VRXUFH�ILHOG�LV�PDSSHG��HYHQ�ZKHQ�VWRUHG�LQ�WKH�VRXUFH�GDWD�DV�WH[W�YDOXHV�

�


SAP AG 2006

$GGLWLRQDO�6RXUFH�)LHOG�0DSSLQJ�'HWDLOV

1RWH��7KH�VWHSV�OHDGLQJ�XS�WR�ILHOG�PDSSLQJ��YDOXH�FRQYHUVLRQ��DQG�PDSSLQJ�UHTXLUH�WKDW�ILHOG�OHYHO�VHWWLQJV�IRU�VRXUFH�ILHOGV�EH�VHW�DW�WKH�SURSHU�WLPHV DQG�LQ�WKH�SURSHU�VHTXHQFH�

| $GGLWLRQDO�)LHOG�OHYHO�VHWWLQJV�ZKLFK�FDQ�DIIHFW�WKH�LPSRUW�IRU�HDFK�VRXUFH�ILHOG��7KHVH�DUH�DYDLODEOH�E\�ULJKW�PRXVH�FOLFN�RQ�D�ILHOG�

| 7R�VHW�WKH�EHORZ�YDOXHV��WKH�ILHOG�PXVW�EH�XQPDSSHG�| )LHOG�OHYHO�VHWWLQJV�IRU�HDFK�VRXUFH�ILHOG�

LQFOXGH�6HW�~ 18//�+DQGOLQJ~ &DVH�6HQVLWLYLW\~ )LHOG�0DSSLQJ�

'HOLPLWHU

�

} 18//�KDQGOLQJ: The NULL Handling option determines how NULLs are interpreted in hierarchy values and

multiple delimited values }

&DVH�VHQVLWLYLW\: The Case Sensitivity option determines how case differences are interpreted in source values. }

9DOXH�GHOLPLWHU: The value delimiter strings determine how multiple delimited values within a single field are identified and generated.

} 9DOXH�FRQYHUVLRQ�ILOWHUV : One or more value conversion filters are applied in sequence to each of the distinct

values of a field }

NULL handling, case sensitivity, and delimiters must be set EHIRUH�you field map because they affect how original values are interpreted and how converted values are generated; the NULL Handling and Case Sensitivity options also affect the VHW�of original values. By contrast, value conversion filters must be set DIWHU�you map because they depend on the destination data type.


SAP AG 2006

9DOXH�&RQYHUVLRQ�)LOWHUV��9&)�

9DOXH�FRQYHUVLRQ�ILOWHUV�DXWRPDWH�UHSHWLWLYH�DQG�HUURU�SURQH�WUDQVIRUPDWLRQV��HOLPLQDWLQJ�PDQXDO�W\SLQJ�DQG�WKH�SRVVLELOLW\�RI�XVHU�HUURU�

7KH�ILOWHUV�FDQ�EH�DSSOLHG�DW�� )LHOG�OHYHO��

~ &RQYHUVLRQV�DUH�DSSOLHG�VHTXHQWLDOO\�WR�HDFK�FRQYHUWHG�YDOXH�WKDW�KDV�QRW�EHHQ�LQGLYLGXDOO\�HGLWHG�RU�FRQYHUWHG�DW�WKH�YDOXH�OHYHO

~ &RQYHUVLRQ�VWDUWV�ZLWK�WKH�RULJLQDO�YDOXH

� 9DOXH�OHYHO��7KH�FRQYHUVLRQ�LV�DSSOLHG�WR�WKH�LQGLYLGXDO�FRQYHUWHG�YDOXHV��&RQYHUWHG�YDOXHV�UHVXOW�IURP�~ SULRU�DSSOLFDWLRQ�RI�ILHOG�OHYHO�ILOWHUV~ YDOXH�OHYHO�ILOWHUV~ PDQXDO�HGLWV

�

� For each field, you can apply one or more value conversion filters at the field level. For each value, you can apply one or more value conversion filters at the individual value level (regardless of whether or not value mapping is required.)


SAP AG 2006

0XOWLSOH�6WHS�9&)V

([DPSOH�RI�0XOWLSOH�9&)V DSSOLHG�WR�D�ILHOG�

�


SAP AG 2006

3UHYLHZ�9LUWXDO�,PSRUW�0DQXDOO\�$GMXVW

« DQG�GHVWLQDWLRQ�UHFRUGV��ZKHQ�WKHUH�LV�D�0DWFK�7\SH�" 1RQH�

<RX�FDQ�RYHUULGH�WKH�LPSRUW�EHKDYLRU�IRU�LQGLYLGXDO�VRXUFH«�

�

� When you set the Default Import Action for a group of source records, each action in the Import Action column in both the Source Records and Destination Records grids appears in gray to indicate that it is inheriting the default. When you manually set the import action for an individual source or destination record, the action then appears in black to indicate that you have overridden inheritance from the Default Import Actions grid or the Source Records grid, respectively. You can use the Inherit Default command to restore inheritance for a record.


SAP AG 2006

9DOXH )LHOG 3DUWLWLRQLQJ




�


SAP AG 2006

6RXUFH�9DOXH�)LHOG�3DUWLWLRQLQJ�6FHQDULRV

2

10 mm5

2 in20

1.5 in5

1 in3

�,�a��O�1� �� $��O�\��H�1�=�J�� 3�� 6�h� �6��F� �,�=�� ¡��M�

2 InIn2

5 mmmm5

20 mmmm20

1/4 InIn1/4

1/2 inIn1/2

�,�a��O�3� �� a�a� �=�

��R��L�=�¢ ��

��H�1�=��3� ��£

� ��6�F� �6��F� ��a�� ¡��M�

6FHQDULR�| 0LVVLQJ�WKH�XQLW�RI�PHDVXUH�

IRU�HDFK�QXPHULF�YDOXH�LQ�WKH�QXPHULF�VRXUFH�ILHOG�62&.(7�6,=(�

6ROXWLRQ| &RPELQH�62&.(7�6,=(�

DQG�62&.(7�81,7�ZLWK�SDUWLWLRQLQJ�SULRU�WR�ILHOG�PDSSLQJ�

�

� Partitioning is one of the most powerful features of the MDM Import Manager. It is the mechanism that allows you to arbitrarily restructure electronic source data and rationalize it against destination data that has an entirely different structure.


SAP AG 2006

9DOXH�)LHOG�3DUWLWLRQ�6WHSV

� 6HW�WKH�PXOWLSOH�ILHOG�GHOLPLWHU�E\�ULJKW�FOLFNLQJ�RQ�WKH�ILHOG�\RX�DUH�DERXW�WR�VSOLW�DQG�VHOHFW�6HW�6SOLW�'HOLPLWHU�Æ 6SOLW�0XOWLSOH�)LHOGV«

� 7KHQ�VHW�WKH�GHOLPLWHU�YDOXH�

� 5LJKW�FOLFN�RQ�WKH�ILHOG�DQG�VHOHFW�6SOLW�LQWR�0XOWLSOH�)LHOGV

�


SAP AG 2006

0HDVXUHPHQW�9DOXH�&UHDWLRQ

127(� 7KH�LPSRUW�FDQQRW�EH�H[HFXWHG�XQWLO�HDFK�QXPHULF�VRXUFH�GDWD�YDOXH�KDV�DQ�DVVRFLDWHG�XQLW�RI�PHDVXUH��ZKHQ�PDSSHG�WR�WDUJHW�ILHOGV�RI�GDWD�W\SH�³0HDVXUHPHQW´��

| :KHQ�PDSSLQJ�WR�GHVWLQDWLRQ�ILHOGV�WKDW�UHSUHVHQW�SK\VLFDO�PHDVXUHPHQWV��PHDVXUHPHQW�ILHOGV�DQG�QXPHULF�DWWULEXWHV��WKH�XQLWV�RI�PHDVXUH�LQ�WKH�VRXUFH�GDWD�PD\�EH��

| 0LVVLQJ�HQWLUHO\��VXFK�DV�ZKHQ�DOO�WKH�YDOXHV�LQ�D�VRXUFH�ILHOG�KDYH�WKH�VDPH�LPSOLFLW�XQLW

| ,QFRQVLVWHQW��VXFK�DV�ZKHQ�GLIIHUHQW�WH[W�VWULQJV�DUH�XVHG�WR�UHSUHVHQW�WKH�VDPH�SK\VLFDO�XQLW��H�J��LQFKHV��LQFK��LQ��RU�µ��¶�

| 'LIIHUHQW�IRU�HDFK�VRXUFH�GDWD�YDOXH�

�

� Further challenges exist based on the source value format: y A single numeric field y A single text field y In a pair of fields (one containing the numeric value and the other containing the corresponding

unit of measure string) y Field may contain multiple, delimited values

� In each of these cases: y Unit of measure strings are automatically normalized and appended to each numeric source data

value y Conversion is based on the physical dimension of the destination measurement field or numeric

attribute � If necessary, each numeric measurement value can be:

y Manually assigned for missing units y Converted to a target unit y Manually edited to override errors in source

� SAP MDM’s built-in dictionary consists of over 2000 synonyms for more than 750 units in over 70 physical dimensions. To see the entire list of potential Dimensions see SAP NetWeaver MDM Content Manager Æ Categories Æ Add Attribute. In the attribute Detail view, select “ Numeric” or “ Coupled Numeric” to view the entire list of Dimensions.


SAP AG 2006

(;(5&,6(�² ,PSRUW�0DQDJHU�$GYDQFHG��

� ,Q�WKH�H[HUFLVH��\RX�ZLOO�LPSRUW�QHZ�UHFRUGV�IURP�D�ILOH�ZKLOH�FORQLQJ�DQG�VSOLWWLQJ�ILHOGV��

� 7KH�ILOH�LV�IURP�WKH�/RQGRQ�RIILFH�VR�ORDG�LW�XVLQJ�WKH�/RQGRQ�UHPRWH�V\VWHP�


�


SAP AG 2006

6SOLWWLQJ�D�)LHOG LQWR D�+LHUDUFK\




�


SAP AG 2006

3XUSRVH�RI�6SOLWWLQJ�D�)LHOG�LQWR�D�+LHUDUFK\

� $�VRXUFH�GDWD�ILHOG�PD\�FRQWDLQ�GHOLPLWHG�YDOXHV�WKDW�LPSOLFLWO\�UHSUHVHQW�WKH�IXOO�SDWK�RI�D�OHDI�QRGH�YDOXH�LQ�D�KLHUDUFK\��

� 'HOLPLWHG�YDOXHV�UHSUHVHQW�D�KLHUDUFK\�¤ 8VH�WKH�VSOLW�WR�H[SDQG�WKH�YDOXHV�LQWR�D�KLHUDUFK\�EDVHG�RQ�WKH�VSHFLILHG�GHOLPLWHU��

¤ 6HW�VSOLW�GHOLPLWHU�EHIRUH�VSOLWWLQJ�WKH�KLHUDUFK\�

�

� You can split a field containing multiple delimited values into: y A single field containing the values expanded into a hierarchy y Multiple fields, each containing a single value


SAP AG 2006

6SOLW�LQWR�+LHUDUFK\

Printers; Dot Matrix; 1200 DPI



Printers; Inkjet; Color

Printers; Inkjet; B&W

+ Printers+ Laser+ Inkjet¦ + B&W¦ + Color+ Dot Matrix

+ 300 DPI+ 600 DPI+ 1200 DPI

Printers; Laser

¥H¦R§�¨3©4ª�«D¬$®O¯\°�±³²±³´�®,µ¶

·

¥�¦�§3¨1©/ªs«L¬

�1�,¡¸¡\��M¹��O��º�� »¼ � �=¡\�=¡e� ¼�½ �

��, ¡��M�6SOLW�WKH�&DWHJRU\ ILHOG�LQWR�D�KLHUDUFK\�ZKHUH�KLHUDUFK\�OHYHOV�DUH�GHWHUPLQHG�E\�ILHOG�GHOLPLWHUV�LQ�VRXUFH�GDWD��

:LWKLQ�,PSRUW�0DQDJHU

�

� You can use the Set Split Delimiter commands to set the delimiter strings that the MDM Import Manager uses to split values.

� Example using split into a hierarchy: y Example, “ Tools Æ Power Tools Æ Drills Æ Accessories” represents the Accessories category

for power drills in a four-level hierarchy. � Example using split into multiple fields:

y Example, “ Printers; Laser; 1200” represents a product with Category=Printers; Printer Type=Laser; and DPI=1200 dpi.

� Example using parsed field to extract into new fields – function to be released for future release: y Example, “ This 1200 dpi laser printer is excellent for home or office…” contains values for

category, printer type, and dpi.


SAP AG 2006

(;(5&,6(�² ,PSRUW�0DQDJHU�$GYDQFHG��

� ,Q�WKH�H[HUFLVH��\RX�ZLOO�LPSRUW�D�&DWHJRU\�KLHUDUFK\�± VLPLODU�WR�ZKDW�\RX�GLG�LQ�WKH�SUHYLRXV�H[HUFLVH�ZLWK�VSOLWLQJ RI�ILHOG�LQ�WKLV�H[HUFLVH�\RX�ZLOO�VSOLW�D�KLHUDUFK\

� 7KLV�OHVVRQ�ZLOO�DOVR�UHTXLUH�PRUH�PDQLSXODWLRQ�RI�WKH�VRXUFH�YDOXHV�EHIRUH�\RX�FDQ�LPSRUW�WKHP�LQ�


�


SAP AG 2006

&RQILJXUDWLRQ 2SWLRQV




�


SAP AG 2006

&RQILJXUDWLRQ�2SWLRQV

3XUSRVH¾ ,QIOXHQFH�WKH�EHKDYLRU�RI�0'0�

,PSRUW�0DQDJHU¾ 6HW�GHIDXOW�YDOXHV�DXWRPDWLFDOO\+RZ�WR¾ *R�WR�&RQILJXUDWLRQ�Æ 2SWLRQV�Æ

&RQILJXUDWLRQ�'LDORJ�ZLOO�GLVSOD\¾ &OLFN�LQ�WKH�9DOXH�FROXPQ�IRU�WKH�

RSWLRQ�VHWWLQJ�\RX�ZDQW�WR�FKDQJH�¾ ,I�WKH�YDOXH�FHOO�LV�D�GURS�GRZQ�OLVW��

VHOHFW�WKH�GHVLUHG�RSWLRQ��¾ ,I�WKH�YDOXH�FHOO�LV�DQ�HGLW�ILHOG��

GRXEOH�FOLFN�LQVLGH�WKH�ILHOG�DQG�UHSODFH�WKH�H[LVWLQJ�YDOXH�ZLWK�D�QHZ�YDOXH�

¾ &OLFN�2.�WR�VDYH�DQ\�QHZ�YDOXHV�DQG�FORVH�WKH�GLDORJ

�

Default Handling � Default Value Delimiter: split hierarchy; split multi-fields; partition combine, etc. � Default Cas Sensitivity: Case Sensitive or Insensitive � Default Null Handling: Preserve or Ignore Find Matching Field � Operator (Contains/Exact) � Special (Normalized/Unnormalized) Record Matching Rules � Perform record matching (yes or no) � Normalized Match Against Normalized Value Import � Merge duplicated source records into a single record (on or off) � Merge duplicated sub-records as a single qualifier (on or off) � Synchronize the entire Family Hierarchy after import (yes or no) � Do not update a record matching field value (yes or no) Numeric Format: decimal (.); thousand (,)


SAP AG 2006

7\SH�RI�&RQILJXUDWLRQ��

'HIDXOW�+DQGOLQJ¿ ³1XOO´�YDOXHV��3UHVHUYH�RU�,JQRUH¿ ³&DVH´��&DVH�6HQVLWLYH�RU�,QVHQVLWLYH¿ 'HOLPLWHU�6WULQJ��VSOLW�KLHUDUFK\��VSOLW�PXOWL�ILHOGV��SDUWLWLRQ�

FRPELQH�HWF�$XWR�PDSSLQJ�%DWFK�+DQGOLQJ¿ $XWRPDS��\HV�RU�QR��8QPDSSHG��LJQRUH�RU�DGG�¿ +LHUDUFK\�DXWR�PDSSLQJ��)XOO�SDWK�YV��OHDI�QRGHV�RQO\¿ 1RUPDOL]H�VRXUFH�DQG�GHVWLQDWLRQ�YDOXH��\HV�RU�QR�5HFRUG�0DWFKLQJ�5XOHV¿ 3HUIRUP�UHFRUG�PDWFKLQJ�ZKHQ�HDFK�ILHOG�ZDV�VHOHFWHG��\HV�RU�QR�¿ 1RUPDOL]HG�0DWFK�$JDLQVW�1RUPDOL]HG�9DOXH¿ ([DFW�0DWFK�$JDLQVW�1RQ�1RUPDOL]HG�9DOXH

�

� Batching Handling settings are used when doing a batch import or using the Import Server. Default Handling � “ Null” values: Preserve or Ignore � “ Case” : Case Sensitive or Insensitive � Delimiter String: split hierarchy; split multi-fields; partition combine etc. Record Matching Rules � Perform record matching when each field was selected (yes or no) � Normalized Match Against Normalized Value � Exact Match Against Non-Normalized Value


SAP AG 2006

6XPPDU\




�


SAP AG 2006

6RXUFH�+LHUDUFK\�7UHH�1RGH�5HIHUHQFH

À�Á3Â\Ã ÄDÅ³Æ�ÇÉÈ,ÊHË1Â Æ3Ã ÄÍÌRÈ1Ä3ÆaÎÏÄ,ÆOÎ3Â ÐDÇ,ÑaÒ�Â\Ç,ÐÔÓÏÑaÒFÕ�Á×Ö ØFÈDÂeÇOÙ�Ê�Â Æ�Ã$ÄÒgÈÏÑ1Ç,È�Ò�ÁOÆ3Å1ÒhÑ�Ú3Ã Æ1Û0DWFK�)LHOGV��Ë�Â Æ1Ã Ä3ÎÜÃ$Â Î�ÒgÆOÄÞÝ3Ç�Ä�Æ3ÅRß,È3È�àOÝ1áâÒgÑLÚ�Ã ÆOÎLÛ/RRNXS�)LHOGV�

ËOÈ�Ã$Ã È,ãäÂ$Ç,ÐÉÒ�ÁOÆÏÃ$Â ÎMÒHÈ�Ê1Ê�Â Æ1Ã Ä�ÎäÑ3ÅFÆäÑ�ÇOåÜÃ È1ÈLà�ÝLáæÒ¸ÑLÚ3Ã ÆMÎäÒFÈãäÁ3Â Õ3ÁâÒ�Á�ÆÏß,ÆMç�Æ�Ã,èsÒgÑ3Ú1Ã ÆéÂ ÎêØhÈ�Â$ÇOÆ,ÄDÛ/RRNXS�7DEOHV�

ë Á�ÆÉÄDÂ ÎOÒ�Â$Ç�ÕMÒLÄ3ÑMÒgÑæç,Ñ�Ã�Ý�ÆMÎäÈ3Ê1ÆOÑ,Õ,Á×Ê³Â Æ1Ã ÄÞÛ'DWD�9DOXHV��

ë Á�ÆÉÃeÂ ÎOÒDÈ,Ê1Ê�Â Æ3Ã Ä�ÎÜá,Æ�ÅLÒgÑ3Ú1Ã ÆäÑMÎ×Õ3Á3Â$Ã ÄDÅhÆ3ÇÏÈ�Ê1Æ,ÑOÕ�ÁäÒgÑ�ÚLÃ ÆÇOÈ1Ä3Æ1ÛMì í3ÈDÂ$ÇOîLÑ1á3á�Æ3Ç,Ä�Æ,Ä×ÒhÈéÓÏÑaÒ³Õ,Á3ÂeÇOÐÉÊ�Â Æ3Ã Ä,Î1Û)LHOGV��ë Á�ÆÉÃeÂ ÎOÒDÈ,Ê1ÒFÑ�Ú1Ã ÆMÎ,ï,Â�ÇäÑ�Ã�á3ÁOÑ1ÚOÆMÒ�Â ÕMÑ�ÃMÈLÅhÄ1Æ�Å Û7DEOHV��ë Á�ÆéÇOÑ�ÓÏÆ×È,ÊLÒ�ÁOÆâÎ,È�Ý1ÅhÕaÆäÊ³Â$Ã Æ×ÈDÅDÄ3ÑMÒgÑ3Ú�ÑMÎOÆ3Û)LOH�'DWDEDVH��5RRW'HVFULSWLRQ1RGH�7\SH/HYHO

�

What is displayed: � Tables, fields and data values at a minimum � Join relationships (in the source or user-defined in MDM) � Matching Fields � Lookup tables and fields � Distinct Values list


SAP AG 2006

,PSRUW�0DQDJHU�$GYDQFHG�)HDWXUHV��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� ([SODLQ�WKH�'HWDLOHG�)XQFWLRQV�IRU�PDSSLQJ�DQG�

DGYDQFHG�WUDQVIRUPDWLRQ�ZKHQ�LPSRUW�GDWD�IURP�YDULRXV�VRXUFHV�

�


�([HUFLVHV�

8QLW�� 0'0�$GYDQFH�,PSRUW�([HUFLVH��7RSLF��0'0�,PSRUW�0DQDJHU�$GYDQFHG�


• ([SODLQ�WKH�'HWDLOHG�)XQFWLRQV�IRU�PDSSLQJ�DQG�DGYDQFHG�WUDQVIRUPDWLRQ�ZKHQ�LPSRUWLQJ�GDWD�IURP�YDULRXV�VRXUFHV

3XUSRVH��This exercise allows you to perform some of the basic advance features of the MDM Import Manager.

3UHUHTXLVLWHV��MDM Repository has been created [Case_Study]


Repository Case Study has been loaded. (If your repository is not loaded please go to the console and load the Case_Study respository.)

7-1 /RJRQ�WR�0'0�,PSRUW�0DQDJHU

Skip steps 7-1-1 and 7-1-2, if you are already logged into the Import Manager and instead go to File > Connect to Source and proceed to step 7-1-3.

7-1-1 Logon to Import Manager with the following settings, user=Admin and pw=blank

7-1-2 And click on 1H[W.


7-1-3 Connect to the Source:

Type: Excel

Remote system: /RQGRQ�File name: &DVHB6WXG\B/RQGRQ�[OV

7-1-4 Then click )LQLVK. <Verify that you selected /RQGRQ as your Remote System.>

7-2 ,PSRUW�1HZ�5HFRUGV Familiarize yourself with the tables, fields and records that you are working with during this exercise. Click on the Source Preview tab to see the data records that you will be importing during this exercise. Notice some similarities with the Case_Study_NY file like similar items but they are called Inventory, the Inventory is in all lower case, ID starts with a letter, and Price is in GBP. Otherwise the remainders of the fields are identical.

7-2-1 Because of the similarity of the data we want to use the ,WHPV�0DS that we used when importing our previous data. Go to )LOH�!�2SHQ« and select the Items Map you saved in the previous Import Exercise.

There are no maps available. Why?

7KH�PDS��,WHPV�0DS��SUHYLRXVO\�VDYHG�LQYROYHV�WKH�1HZ�<RUN�UHPRWH�V\VWHP��QRW�WKH�SUHVHQW�/RQGRQ�UHPRWH�V\VWHP�

7-2-2 Go to )LOH�!�,PSRUW«

7-2-3 Select your Items Map from your desktop (in the first Import Exercise) and save it as Items Map-London.

1RWH: When you use the menu path, File > Open, you will most likely be taken to the folder MDM100_71 on the shared drive. You do not have access to copy this file as the folder is protected. Switch to your desktop to obtain the Items Map you saved in a previous exercise. If you experience difficulty, contact your trainer.

7-2-4 Go to )LOH�!�2SHQ«

7-2-5� Select Items Map-London.

One of the main reasons this map works is that the Excel tab in our source is called “ Items” . This is the name the map is looking for. If the Excel tab had a different name, then the map would QRW load.


7-2-6 Select tab strip where you will find 2 fields not mapped.

� Manually map the Source field ,QYHQWRU\ with Destination field 1DPH�>')@�

� Next you want to map ID to [Remote Key], but ID is already mapped to Product ID which is correct and you do not want to change. So you need to make a Clone of ID. Right-click on ,' in the Source Hierarchy and select Clone.

� You can now map ,'��&ORQH!�to >5HPRWH�.H\@. � Lastly, you will map Price to the qualified table Pricings but we need to

have a separate field for Currency and Price. Currently, the 2 fields are combined. We will split them into 2 fields but first we need to set the delimiter. Right-click on 3ULFH��*%3� field under the Source Hierarchy and selecting 6HW�6SOLW�'HOLPLWHU�!�6SOLW�0XOWLSOH�)LHOGV«

� Set the Delimiter to a space.

� Now right-clicking on the 3ULFH��*%3� field and selecting 6SOLW�LQWR�0XOWLSOH�)LHOGV. Notice that you now have 2 additional fields:

3ULFH��*%3��6SOLW�0XOWLSOH!�� – Which contains all the Price values.

3ULFH��*%3��6SOLW�0XOWLSOH!�� – Which contains all the Currencies.

� Map the first one to the Qualified field /LVW�3ULFH��3ULFLQJ!� � Map the second one to 3ULFLQJ.


� The 3 Price values were not automatically mapped because of 3 reasons which we will explain and resolve.

1. GBP – is not existing destination value so it must be added. Select GBP and click $GG.

2. GPB – was incorrectly entered and should have been GBP. Select GPB and 0DS it to GBP in the destination values.

3. NULL – this had no currency listed but we know from the column title that the values are in GBP so we are going to map NULL to GBP. Select NULL from the Source values and click 8QPDS. Then select the destination value of GBP and 0DS.


3URGXFW�,' should be the matching field for this step.

Set Default import actions to &UHDWH�for the 8 records.

7-2-8 Select the Import Status tab

7-2-9 Save your modified map.

7-2-10 ([HFXWH��

7-3 5HYLHZ�5HVXOWV�LQ�WKH�'DWD�0DQDJHU

If you already had the Data Manager open, then click F5 to refresh the data.

7-3-1 Sort your Product records by Product ID by clicking on Product ID header.

7-3-2 Click on each of the 8 records that you have just imported. The Product ID starts

with a letter. Each should have a Pricing in GBP.

7-3-3 Review the Product Record Detail of any record.


�([HUFLVHV�

8QLW�� 0'0�$GYDQFH�,PSRUW�&DWHJRU\�([HUFLVH�7RSLF��0'0�,PSRUW�0DQDJHU�$GYDQFHG�


• ([SODLQ�WKH�'HWDLOHG�)XQFWLRQV�IRU�PDSSLQJ�DQG�DGYDQFHG�WUDQVIRUPDWLRQ�ZKHQ�LPSRUWLQJ�GDWD�IURP�YDULRXV�VRXUFHV

3XUSRVH��This exercise allows you to perform split a category import using additional advance features using SAP MDM Import Manager.

3UHUHTXLVLWHV��MDM Repository has been created [Case_Study]


Repository Case Study has been loaded. (If your repository is not loaded please go to the console and load the Case_Study respository.)

7-4 /RJRQ�WR�0'0�,PSRUW�0DQDJHU

Skip steps 7-4-1, if you are already logged into the Import Manager and instead go to )LOH�!�&RQQHFW�WR�6RXUFH and proceed to step 7-4-2.

7-4-1 Logon to Import Manager to Your_Case_Study.

7-4-2 Connect to the Source,

Type: Excel

Remote system: 1HZ<RUN�File name: Case_Study_Cat.xls

7-4-3 Then click )LQLVK.


7-5 &DWHJRU\�,PSRUW�$ORQJ�ZLWK�5HFRUGV Familiarize yourself with the tables, fields and records that you are working with during this exercise. Notice how the structure of the worksheets within the workbook compares to the Source Hierarchy in the MDM Import Manager� 7-5-1 Click on the Source Preview tab to see the data records that you will be

importing during this exercise. Note that you can sort the records with the controls at the top to quickly inspect the data for specific values. Notice that &DWHJRU\ is actually a path of nodes with &DWHJRU\B)ODW being the name of the end node.

�7-5-2 Go to File > Open… and select the Items Map you saved in a previous Import

Exercise.

This will map 9 fields leaving the Category and Category_Flat to be mapped to the destination field: Category (created as part of the standard repository.)

7-5-3 In order to have the Category split correctly you can set the correct delimiter globally. This sets the default for all delimiters.

� Go to &RQILJXUDWLRQ�!�2SWLRQV � Set the Default value delimiters > Split Hierarchy [SH] to “�”


7-5-4 Or use the right mouse context menu on the Category to set it for this one time use.

7-5-5� In the Source Hierarchy right-click on the Category to 6SOLW�LQWR�+LHUDUFK\


7-5-6 Select Display Distinct Values to see the results of splitting the hierarchy.

The result:

7-5-7 Select tab strip 1 Manually map the Source field &DWHJRU\�6SOLW�+LHUDUFK\! with

Destination field &DWHJRU\� 2 Source values in the lower half of the screen now need to be added to

Categories. 3 Select all subnodes RQ�the�OHIW�KDQG�VLGH and &DWHJRULHV RQ�WKH�ULJKW�KDQG�

VLGH. 4 Select Add and select $GG�%UDQFK�DV�&KLOG from the drop down menu.

Result:



3URGXFW�,' should be the matching field for this step.

Set Default import action to 8SGDWH��18//�)LHOGV�2QO\��

7-5-9 Select the Import Status tab.

7-5-10 ([HFXWH


7-6 5HYLHZ�5HVXOWV�LQ�WKH�'DWD�0DQDJHU

Confirm the status and review the import results. Review the Hierarchy structure and the records you have imported.

7-6-1 Review the Hierarchy in the Data Manager in the Record and Hierarchy Modes.

7-6-2 Review the Product Record Detail for at least one record.


SAP AG 2006

7D[RQRP\




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�


SAP AG 2006

&RQWHQWV�� 7D[RQRP\�7DEOHV

� 3XUSRVH� &UHDWLRQ�RI�DWWULEXWHV� $VVLJQPHQW RI�DWWULEXWHV

0'0�7D[RQRP\

�


SAP AG 2006

0'0�7D[RQRP\��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� :RUN�LQ�WKH�WD[RQRP\�PRGH�RI�WKH�0'0�'DWD�

0DQDJHU� 8QGHUVWDQG�WKH�GLIIHUHQFHV�EHWZHHQ�DWWULEXWHV�

DQG�ILHOGV� &UHDWH�DQG�PDLQWDLQ�DWWULEXWHV

�


SAP AG 2006

0'0�7D[RQRP\��%XVLQHVV�6FHQDULR

� $V�SDUW�RI�WKH�LPSOHPHQWDWLRQ��\RX�ZRXOG�OLNH�WR�FODVVLI\�\RXU�PDVWHU�GDWD�LQ�RUGHU�WR�PDNH�VHDUFKLQJ�PRUH�HIIHFWLYH�E\�DVVLJQLQJ�PDVWHU�GDWD�UHFRUGV�WR�D�KLHUDUFK\�RI�FDWHJRULHV�GHVFULEHG�E\�DWWULEXWHV��FKDUDFWHULVWLFV��

�


SAP AG 2006

7D[RQRP\ ,QWURGXFWLRQ&UHDWLRQ�RI�D�7D[RQRP\/LQNLQJ�$WWULEXWHV�WR�&DWHJRULHV6XPPDU\$SSHQGL[�± 5HDVVLJQLQJ�$WWULEXWHV

7D[RQRP\ ,QWURGXFWLRQ

�


SAP AG 2006

7D[RQRP\ 7DEOH

� $�WD[RQRP\�WDEOH�LV�D�VSHFLDO�NLQG�RI�ORRNXS�WDEOH�� ,W�SURYLGHV�VXSSRUW�IRU�FDWHJRU\�VSHFLILF�DWWULEXWHV WKDW�FDQ�

EH�DVVLJQHG�WR�HDFK�FDWHJRU\�RQ�D�FDWHJRU\�E\�FDWHJRU\�EDVLV�

� $�WD[RQRP\�FRQWDLQV�DWWULEXWHV�WKDW�DUH�DVVLJQHG�WR�WKH�OHDI�DQG�QRQ�OHDI�QRGHV�

� $�UHFRUG�FDQ�RQO\�EH�DVVLJQHG�WR�RQH�OHDI�QRGH��QRW�PXOWLSOH�YDOXHV��DV�LQ�KLHUDUFKLHV��

� 7KH�WD[RQRP\�WDEOH�LWVHOI�DQG�WKH�WDEOH�ILHOGV�RI�HDFK�FDWHJRU\�DUH�FUHDWHG�DQG�GHILQHG�LQ�WKH�0'0�&RQVROH�

� 7KH�KLHUDUFK\�RI�FDWHJRULHV�DQG�WKHLU�DVVRFLDWHG�FDWHJRU\�VSHFLILF�DWWULEXWHV�DUH�FUHDWHG�DQG�PDQDJHG�XVLQJ�WKH�0'0�'DWD�0DQDJHU�LQ�7D[RQRP\�PRGH�RU�YLD�WKH�,PSRUW�0DQDJHU�

� ,I�DQ�DWWULEXWH�FDQ�EH�DSSOLHG�WR�DOO�PDLQ�WDEOH�UHFRUGV��\RX�PLJKW�FRQVLGHU�GHILQLQJ�LW�DV�D�ILHOG��

�

� Categorizing records enables you to isolate subsets of records for various organizing, searching, editing, and publishing purposes.

� A taxonomy table in MDM stores a hierarchy of categories and subcategories and also supports record attributes, which are database subfields that apply to particular record categories, rather than to the entire collection of records.

� In a taxonomy, a record can belong to only one leaf-node category. � MDM does support multiple taxonomies within a single repository, although it is not recommended.


SAP AG 2006

'LIIHUHQFH�%HWZHHQ�+LHUDUFK\�DQG�7D[RQRP\�0RGHV

&DWHJRULHV�DQG�FDWHJRU\�QDPHV LQ�DOSKDEHWLFDO�RUGHU

&DWHJRULHV�DQG�DWWULEXWHV LQ�DOSKDEHWLFDO�RUGHU

�

� The main difference between Hierarchy and Taxonomy modes is the fact that a taxonomy is a

category with some additional features, which are the functional assigned attributes to the various nodes.

� The attributes are used to classify and describe the products. � Attributes are inherited down the tree and give the user the ability to describe the product with

general attributes high up in the tree, with more specific attributes down the branch. � In respect to maintenance and handling, the same options and restrictions apply for both hierarchy

and taxonomy. � :RUNLQJ�ZLWK�WD[RQRP\�WDEOHV�

y Taxonomy mode is used to manage the product classification structure defined by the category records and the associated attributes of a taxonomy table. When you view a taxonomy table in Taxonomy mode, 0'0 uses a tree to display the category records of the table as a hierarchy of categories and subcategories, and a grid to list the entire pool of attributes that are associated with the taxonomy table.

y In Taxonomy mode, you can create and manage the category hierarchy, create and manage the pool of attributes, and assign attributes to categories on a category-by-category basis.

y Taxonomy mode also provides powerful functionality that allows you to flexibly restructure the taxonomy of a fully populated repository so that you can continue to refine your taxonomy even after the repository contains detailed product information a large number of products.


SAP AG 2006

'LIIHUHQFHV�%HWZHHQ�$WWULEXWHV�DQG�)LHOGV

None Coupled numericMultiple dimension data

Assigned to every recordAssigned to records that require it

Usage

Same for similar field types

Can be different for every category

Details

Console while repository is unloaded

Data ManagerMaintenance

Records and lookup tablesAvailable on attribute valuesKey mapping

Free text or predefined values

Predefined values onlyInput

Drilldown and free-form search

DrilldownSearch

Boolean, dates, integer, real, text, time, …

Text, numeric, and coupled numeric

Formats

)LHOGV��LQ�WDEOHV�$WWULEXWHV��LQ�WD[RQRP\�'LIIHUHQFHV

�

� "Key mapping" Currently, there is no key mapping at the attribute level but at the level of attribute values and class nodes only.


SAP AG 2006

&UHDWLRQ�RI�D�7D[RQRP\

7D[RQRP\ ,QWURGXFWLRQ&UHDWLRQ�RI�D�7D[RQRP\/LQNLQJ�$WWULEXWHV�WR�&DWHJRULHV6XPPDU\$SSHQGL[�± 5HDVVLJQLQJ�$WWULEXWHV

�


SAP AG 2006

� 7KH�WD[RQRP\�WDEOH�LWVHOI�DQG�WKH�ILHOGV�RI�HDFK�RI�LWV�FDWHJRULHV�DUH�FUHDWHG�DQG�GHILQHG�LQ�WKH�0'0�&RQVROH�

� $�WD[RQRP\�WDEOH�LV�LGHQWLILHG�ZLWK�WKH��LFRQ�� %\�FRQYHQWLRQ��0'0�RIWHQ�UHIHUV�WR�WKH�WD[RQRP\�WDEOH�DV�

WKH�&DWHJRULHV�WDEOH�� (YHU\�UHFRUG�VKRXOG�EHORQJ�WR�D�FDWHJRU\��EXW�LW�LV�QRW�

PDQGDWRU\�� &ODVV�QRGHV��DWWULEXWHV��OLQNV��DQG�DWWULEXWH�YDOXHV�FDQ�RQO\�

EH�FUHDWHG�LQ�WKH�0'0�'DWD�0DQDJHU�RU�LQ�WKH�0'0�,PSRUW�0DQDJHU�GXULQJ�DQ�LPSRUW�

� 6DPSOH�WD[RQRPLHV�FDQ�EH�IRXQG�LQ�WKH�IROORZLQJ�EXVLQHVV�SDFNDJHV�ð 0DWHULDO��H&ODVVð 3URGXFW��&DWHJRULHV��&ODVVHV��H&ODVV

&UHDWLRQ�RI�D�7D[RQRP\�7DEOH

�


SAP AG 2006

7D[RQRP\�0RGH

,Q�7D[RQRP\�PRGH��WKH�GURSGRZQ�PHQX�ZLOO�KLJKOLJKW�RQO\�WD[RQRP\�WDEOHV��

�

� Taxonomy mode is used to manage the product classification structure defined by the category records and the associated attributes of a taxonomy table. When you view a taxonomy table in Taxonomy mode, MDM uses a tree to display the category records of the table as a hierarchy of categories and subcategories, and a grid to list the entire pool of attributes that are associated with the taxonomy table.

� In Taxonomy mode, you can create and manage the category hierarchy, create and manage the pool of attributes, and assign attributes to categories on a category-by-category basis.

� Taxonomy mode also provides powerful functionality that allows you to flexibly restructure the taxonomy of a fully populated repository so that you can continue to refine your taxonomy even after the repository contains detailed product information a large number of products.


SAP AG 2006

7H[WV�ñ 3UHGHILQHG�OLVW�RI�YDOXHV�IRU�HQWU\��VHDUFK��DQG�FRPSDUHñ &DQ�EH�XVHG�IRU�IDPLO\�SDUWLWLRQLQJ��RQO\�LI�VLQJOH�YDOXHG�ñ ,PDJH�FDQ�EH�DWWDFKHG�WR�HYHU\�SRVVLEOH�YDOXHñ &DQ�EH�PXOWL�YDOXHGñ 7H[WV�FDQ�EH�WUDQVODWHG�LQ�LQVWDOOHG�ODQJXDJHV1XPHULF�ñ 5HDO�ZLWK�GLPHQVLRQV�XQLW�RI�PHDVXUHVñ 5DWLQJV��QRPLQDO��PLQ��PD[��DYHUDJH��W\SLFDOñ &DQ�EH�PXOWL�YDOXHG&RXSOHG�QXPHULF�ñ &RXSOHV�RI�DVVRFLDWHG�QXPHULF�YDOXHV��YDOXH�$�XQGHU�YDOXH�FRQGLWLRQ�;

([DPSOH��9DSRUL]DWLRQ�WHPSHUDWXUH�XQGHU�SUHVVXUH�FRQGLWLRQò 2QO\�WKH�ILUVW�QXPHULF�YDOXH�LV�DYDLODEOH�IRU�VHDUFK�VHOHFWLRQV

ñ 1DWLYHO\�PXOWL�YDOXHG

7D[RQRP\�$WWULEXWH�7\SHV

�

� 7H[W attributes are those whose possible values are easily expressed as a list of predefined (usually text-valued) choices. “ Color” is an example of a text attribute, as is “ Head Type” for screws. The list of text values defined for a text attribute constitutes the set of legal values for that attribute. y A text attribute is like a mini lookup table with the set of valid choices defined by the list of

attribute text values, rather than the records of a lookup table. � 1XPHULF attributes are those whose values come from a potentially continuous range of numeric

values (with or without an associated physical dimension and unit of measure). “ Socket Size” is an example of an attribute that typically should be treated as numeric. y In theory you could make a list of all possible values for socket size across the entire set of

products and make “ Socket Size” a text attribute. However, you gain certain advantages by treating it as a numeric attribute, including proper numeric sorting and the ability to convert between units (such as between inches and millimeters). Also, numeric attributes allow you to associate a physical dimension with the attribute, and then to assign to every numeric value a unit of measure chosen from the list of units applicable to that dimension.

y To allow you to organize related numeric information within a single named attribute, a numeric attribute can have up to five ratings: Nominal, Minimum, Maximum, Average, and Typical.

� &RXSOHG�QXPHULF attributes are numeric attributes where two numeric values are required to describe the attribute, such as “ horsepower @ rpm.” y A coupled numeric attribute appears as “ QDPH�GHOLPLWHU�FRXSOHGQDPH” (where “ GHOLPLWHU” is the

user-defined, attribute-specific delimiter string for the attribute). y Coupled attributes are always multi-valued.


SAP AG 2006

&RPPRQ�$WWULEXWH�3URSHUWLHV

ó $WWULEXWH�1DPH PXVW�EH�XQLTXH�

ó $WWULEXWH�$OLDV FDQ�EH�XVHG�LQ�WKH�ILQG�FRPPDQG��NH\ZRUG�VHDUFK�

ó $WWULEXWH�'HILQLWLRQ WR�SURYLGH�D�GHWDLOHG�GHVFULSWLRQ�RI�WKH�DWWULEXWH�DYDLODEOH�DIWHU�SXEOLVKLQJ�WR�SDSHU�RU�:HE

ó $WWULEXWH�,PDJH WR�DVVRFLDWH�DQ�LPDJH�ZLWK�WKH�DWWULEXWH��DYDLODEOH�DIWHU�SXEOLVKLQJ�WR�SDSHU�RU�:HE

ó 0XOWL�YDOXHG�RSWLRQ�GHILQHV�ZKHWKHU�WKH�DWWULEXWH�FDQ�VWRUH�PXOWLSOH�YDOXHV�

�

� $WWULEXWH�GHWDLOV��These are applied across all attributes. � Every attribute has a fixed set of properties that define it. &RPPRQ�SURSHUWLHV apply to all attribute

types and include Name, Alias, Definition, Attribute Image, and the Multi-valued setting.�� An attribute of any type may be PXOWL�YDOXHG to accommodate products where one attribute may

require two or more values to specify an item. For example, a software product might require a multi-valued text attribute to contain a list of the supported operating systems, such as Windows, Solaris, Unix; or Windows 95, Windows 98, Windows NT, and so on.

� Multi-valued attributes make the structure of an MDM repository dramatically simpler, more compact, and more searchable by allowing the storage of all the values corresponding to a particular data element in the same place. The alternative is having to create multiple attributes, in some cases up to a maximum of one attribute for each possible value.


SAP AG 2006

7H[W�$WWULEXWHV

7H[W�3URSHUWLHVó /LVW�RI�OHJDO�HQWULHV�

E\�FOLFNLQJ�WKH�$GGEXWWRQ

ó ,PDJH�SRVVLEOH�IRU�HDFK�YDOXH�LQ�WKH�OLVW�

�

� The definition of a text attribute includes a list of text values. This list constitutes the set of legal values for that attribute; these are the only values from which you can choose and which you can assign to the attribute during data entry.

� A text attribute is like a mini lookup table with the set of valid choices defined by the list of attribute text values, rather than the records of a lookup table.

� In addition to the Attribute Image property, the Text Value Image property allows you to associate an illustrative image with each text value. Select a text value and double-click on Text Value Image to open the Select Single Image dialog and assign an image.


SAP AG 2006

1XPHULF�$WWULEXWHV��5DWLQJV

1XPHULF�3URSHUWLHVó 5DWLQJV�

ð 1RPLQDOð 0LQLPXPð 0D[LPXPð $YHUDJHð 7\SLFDO

�

� 1XPHULF attributes are those whose values come from a potentially continuous range of numeric values (with or without an associated physical dimension and unit of measure). “ Socket Size” is an example of an attribute that typically should be treated as numeric.

� In you could make a list of all possible values for socket size across the entire set of products and make “ Socket Size” a text attribute. However, you gain certain advantages by treating it as a numeric attribute, including proper numeric sorting and the ability to convert between units (such as between inches and millimeters). Also, numeric attributes allow you to associate a physical dimension with the attribute, and then to assign to every numeric value a unit of measure chosen from the list of units applicable to that dimension.

� $WWULEXWH�5DWLQJV: To allow you to organize related numeric values within a single named attribute, a numeric attribute can be defined as having up to five ratings, each of which shares the single, common attribute definition. The default is Nominal.

� 5DWLQJ 6XIIL[ 'HVFULSWLRQ�� Nominal [Nom] The most commonly applicable default rating when just a single

measurement is associated with the attribute. � Minimum [Min] The corresponding attribute value is a minimum. � Maximum [Max] The corresponding attribute value is a maximum. � Average [Avg] The corresponding attribute value is an average. � Typical [Typ] The corresponding attribute value is a typical value. � You must specify at least one rating for a numeric attribute. � To distinguish the different ratings for a numeric attribute in attribute lists, SAP MDM appends to

the attribute name the rating abbreviation in square brackets (for example, Width [Max]). However, MDM does not append the [Nom] suffix when Nominal is the only rating specified for the attribute.


SAP AG 2006

1XPHULF�$WWULEXWHV��2SWLRQV

1XPHULF�3URSHUWLHVó 'LPHQVLRQ�ó 'HIDXOW�XQLW

�

� A numeric attribute can be defined as having an associated physical dimension, so that each numeric value you enter also includes a unit of measure chosen from the list of units applicable to that dimension. y MDM currently has built-in support for over 70 different physical dimensions and over 750

different units of measure. In addition, MDM is able to convert between different units for proper sorting of numeric values with different units within a list.

� The Dimension and Default Unit properties are dropdown lists. To specify the Dimension for a numeric attribute, select from the dropdown list of physical dimensions. To specify the Default Unit, if any, to be used by MDM for new data values, select from the dropdown list of units of measure corresponding to the selected dimension. The default value for both Dimension and Default Unit is None. y You must specify a unit of measure for each numeric value if a physical dimension is defined for

the attribute. y Just as with a numeric attribute, the physical dimension is optional for either or both coupled

dimensions of a coupled numeric attribute. � When you change the physical dimension for a numeric attribute that already has data values

assigned to it from None or from another dimension, MDM does not allow you to select None as the Default Unit and makes special use of the unit you specify to automatically repopulate the unit part of each existing attribute value. To set the Default Unit to None, first save the attribute with a Default Unit, then change the Default Unit to None and save it again.


SAP AG 2006

1XPHULF�$WWULEXWHV��'HFLPDOV

1XPHULF�3URSHUWLHVó 'HFLPDO�3ODFHV�ó 6KRZ�)UDFWLRQV

�

� You can specify two display options for a numeric (or coupled numeric) attribute: the number of decimal places to use to display numeric values, and whether or not to display fractional powers of two (specifically, 1/2, 1/4, 1/8, 1/16, 1/32, 1/64).

� The Decimal Places property is a dropdown list. To specify the Decimal Places for a numeric attribute, select from the dropdown list of values between 0 and 6. The Show Fractions option is a standard Windows checkbox; click on it to toggle the setting on and off. y The Show Fractions option only applies to units of measure that are traditionally displayed with

fractional values (for example, inches) and is ignored for units that are not typically displayed with fractional values (for example, millimeters).

y The Show Fractions option displays as fractions the fractional powers of two from 1/2 to 1/64 for absolute values between 0 and 100 (including all numerator values, such as 3/4, 5/16, and 27/64). The exceptions are for the units: Horsepower in the dimension Power (Apparent); and Cups, Pints, and Quarts in the dimension Volume, which for absolute values between 0 and 100 also display the “ odd” fractions 1/3, 2/3, 1/5, 3/5, 4/5, 1/6, and 5/6, and approximately 130 fractions of the form “ 1/x” where ‘x’ ranges from 7 to 100 in increments of 1 (for example, 1/7, 1/15, and 1/78); from 100 to 1000 in increments of 50 (for example, 1/150, 1/250, and 1/500); and from 1000 to 2000 in increments of 100 (for example, 1/1100, 1/1200, and 1/1300).


SAP AG 2006

&RXSOHG�1XPHULF�$WWULEXWHV

&RXSOHG�1XPHULFó 1DPHó 'HOLPLWHU2SWLRQV��VDPH�DV�

1XPHULF�ó 'LPHQVLRQVó 'HIDXOW�XQLWó 'HFLPDO�3ODFHV�ó 6KRZ�)UDFWLRQV

�

� Coupled numeric attributes are numeric attributes where two numeric values are required to describe the attribute, such as “ horsepower @ rpm.” y A coupled numeric attribute appears as “ name delimiter coupledname” (where “ delimiter” is the

user-defined, attribute-specific delimiter string for the attribute). y Coupled attributes are always multi-valued.

� &RXSOHG�1DPH�DQG�'HOLPLWHU: Unlike text and numeric attributes, a coupled numeric attribute has not just one, but two names: The standard attribute name that is the name for the first primary dimension, and the coupled name that is the name for the second coupled dimension. In addition, you can specify a custom delimiter string (such as @) that is used to separate the two names of the coupled attribute and also to separate each pair of numeric values. The Coupled Name and Delimiter properties of the Attribute Detail tab are standard Windows edit controls for data entry. y MDM displays the two names for a coupled attribute as “ name delimiter coupledname” (where

“ delimiter” is the delimiter string for the attribute). y The delimiter string can be different for each coupled numeric attribute.

� 3ULPDU\�DQG�&RXSOHG�'LPHQVLRQ�2SWLRQV: Just like a numeric attribute, a coupled numeric attribute has options for Dimension, Default Unit, Decimal Places, and Show Fractions. However, since a coupled attribute has two dimensions, it has two sets of settings for each of these options.


SAP AG 2006

/LQNLQJ�$WWULEXWHV�WR�&DWHJRULHV

7D[RQRP\ ,QWURGXFWLRQ&UHDWLRQ�RI�D�7D[RQRP\/LQNLQJ�$WWULEXWHV�WR�&DWHJRULHV5HDVVLJQLQJ�$WWULEXWHV6XPPDU\

�


SAP AG 2006

$VVLJQLQJ�$WWULEXWHV��/LQNLQJ�

� $WWULEXWHV�E\�WKHPVHOYHV�RQO\�GHILQH�WKH�W\SH�RI�LQIRUPDWLRQ�WKDW�LV�LQWHQGHG�WR�EH�VWRUHG�LQ�WKHP�

� $WWULEXWHV�FDQQRW�FRQWDLQ�GDWD�XQWLO�WKH�DWWULEXWH�LV�OLQNHG�WR�D�FDWHJRU\

� $Q�DWWULEXWH�FDQ�EH�OLQNHG�WR�DOO��VRPH��RU�QRQH�RI�WKH�FDWHJRULHV

� (DFK�FDWHJRU\�FDQ�KDYH�LWV�RZQ�VHW�RI�DWWULEXWH�V�� 7R�OLQN�DWWULEXWHV�WR�FDWHJRULHV��\RX�PXVW�EH�LQ�7D[RQRP\�

PRGH� 7KH�ILQDO�HIIHFW�FDQ�DOVR�EH�VHHQ�LQ�WKH�5HFRUG�PRGH

�

� Every taxonomy table has a pool of attributes associated with it. From this pool you can link attributes to one or more individual categories on a category-by-category basis. MDM allows you to manage the pool of attributes associated with a taxonomy table in Taxonomy mode. In MDM, attributes are associated with categories.

� In MDM, an attribute is like a field, but one that applies only to a subset of the records in a table. By contrast, a field is part of every record in a table. If a particular attribute can be applied to every product in a repository, it should be set up as a field in the main table. For example, every product in a repository probably has an item number; therefore Item Number should be defined in the database as a field, and not as an attribute.


SAP AG 2006

/LQNLQJ�$WWULEXWHV

� 6HOHFW�WKH�FDWHJRU\�RU�VXEFDWHJRU\�WR�ZKLFK�WKH�DWWULEXWH�ZLOO�EH�OLQNHG�

� 5LJKW�FOLFN�RQ�DWWULEXWH�DQG�FKRRVH�/LQN� $Q�LFRQ�WKDW�ORRNV�OLNH�D�FKDLQ�OLQN��ZLOO�EH�WR�WKH�OHIW�RI�

WKH�DWWULEXWH� ,I�DQ�LFRQ�KDV�D�QXPEHU�QH[W�WR�LW��LW�PHDQV�WKDW�LW�LV�

LQKHULWLQJ�WKH�DWWULEXWH�IURP�D�KLJKHU�FDWHJRU\��7KH�QXPEHU�LQGLFDWHV�KRZ�PDQ\�OHYHOV�DERYH�

�


SAP AG 2006

3ULRULW\��$WWULEXWH�3URSHUWLHV

� 7R�FKDQJH�WKH�SULRULW\��ULJKW�FOLFN�DQG�VHOHFW�3ULRULW\�Æ �OHYHO!�

� 7KH�SULRULW\�OHYHO�GHWHUPLQHV�WKH�OLVWLQJ�RUGHU�RI�WKH�DWWULEXWHIRU�D�FDWHJRU\�QRGH�

� %\�GHIDXOW��DOO�DWWULEXWHV�UHFHLYH�D�SULRULW\�OHYHO�RI�1RUPDO�� 7KH�3ULRULW\�DWWULEXWH�LV�VSHFLILHG�E\�WH[W�YDOXHV�RU�QXPHULF�

YDOXHV��

�

� Unlike the other properties of an attribute, which apply across all categories to which the attribute is linked, priority can be set on a category-by-category (link-by-link) basis. In other words, the same attribute may have different priorities for different categories to reflect the different importance it might have for each category.

� MDM automatically assigns a priority of Normal [50] when you first link the attribute. � You cannot set the priority of an attribute if the current category is an alias or if the attribute is

inherited rather than linked directly to the current category. � You cannot specify numeric priorities (nor are they displayed in the Attributes pane) unless $OORZ�

&XVWRP�3ULRULWLHV has been enabled in the $WWULEXWHV tab of the &RQILJXUDWLRQ�2SWLRQV dialog.


SAP AG 2006

$WWULEXWH�8VDJH

� 7KH�LWHPV�LQ�EODFN�DUH�OLQNHG�WR�WKH�VHOHFWHG�DWWULEXWH�

� ,W�LV�LPSRUWDQW�WR�DVVLJQ�WKH�DSSURSULDWH�DWWULEXWHV�WR�WKH�FRUUHFW�FDWHJRULHV��7R�VHH�ZKLFK�FDWHJRULHV�DQ�DWWULEXWH�LV�DVVLJQHG�WR��VHOHFW�WKH�DWWULEXWH�DQG�WKHQ�FOLFN�RQ�WKH�8VDJH WDE�

�

� The 8VDJH tab contains a partial version of the category tree that includes: y All of its nodes expanded y Just enough tree structure to display those nodes to which the attribute is linked in black y All other nodes highlighted in gray


SAP AG 2006

(QWU\�RI�$WWULEXWH�'DWD�LQ�'DWD�0DQDJHU

$WWULEXWH�ZLOO�RQO\��EH�GLVSOD\HG�ZKHQ�D�UHFRUG�LV�DVVLJQHG�WR�WKH�FDWHJRU\�FRQWDLQLQJ�WKDW�DWWULEXWH�

�

� The three examples are from the same respository. With each category having similar attributes like color and resistance, they contain a larger number of different attributes. Also, the order of the attributes can vary based on the category.


SAP AG 2006

(;(5&,6(�² 7D[RQRP\

� ,Q�WKH�H[HUFLVH��\RX�PDQXDOO\�FUHDWH�DOO��WKUHH�W\SHV�RI�DWWULEXWHV��

� <RX�ZLOO�WKHQ�SURFHHG�WR�OLQN�WKH�DWWULEXWHV�WR�WKHLU�LQWHQGHG�FDWHJRULHV�

� $QG�ILQDOO\�DVVLJQ�DWWULEXWH�YDOXHV�WR�D�UHFRUG�� 3URFHHG�WR�WKH�H[HUFLVH�IROORZLQJ�WKH�LQVWUXFWRU¶V�GLUHFWLRQV�

�


SAP AG 2006

6XPPDU\

7D[RQRP\ ,QWURGXFWLRQ&UHDWLRQ�RI�D�7D[RQRP\/LQNLQJ�$WWULEXWHV�WR�&DWHJRULHV6XPPDU\$SSHQGL[�� 5HDVVLJQLQJ�$WWULEXWHV

�


SAP AG 2006

7D[RQRP\�6XPPDU\

ó 3XUSRVH��$�WD[RQRP\�DVVLJQV�REMHFWV�WR�D�VSHFLDO�KLHUDUFK\�DQG�FRQWDLQV�DWWULEXWHV��ZKLFK�DUH�DVVLJQHG�WR�WKH�QRGHV

ó &RQVWUDLQWV�ð 5HFRUGV�FDQ�RQO\�EH�DVVLJQHG�WR�RQH�OHDI�QRGH��QRW�PXOWLSOH�YDOXHV�DV�LQ�+LHUDUFKLHV�

ð 2QO\�RQH�WD[RQRP\�LQ�WKH�UHSRVLWRU\�LV�FRQVLGHUHG�E\�IDPLOLHVó %HQHILWV�

ð $WWULEXWHV�DUH�GLVSOD\HG�RQFH�WKH�UHFRUG�LV�DVVLJQHG�WR�WKH�WD[RQRP\

ð 7D[RQRP\�PDLQWHQDQFH�LV�SHUIRUPHG�ZLWKLQ�WKH�'DWD�0DQDJHUð 7D[RQRP\�DWWULEXWHV�VXSSRUW�FRXSOHG�QXPHULF�DWWULEXWHV��YDOXH�%�XQGHU�FRQGLWLRQ�YDOXH�$�

ó ,I�DQ�DWWULEXWH�FDQ�EH�DSSOLHG�WR�DOO�PDLQ�WDEOH�UHFRUGV��\RX�FDQ�GHILQH�LW�DV�D�ILHOG��+RZHYHU��\RX�PXVW�DOVR�WKLQN�DERXW�WKH�FRQVHTXHQFHV�IRU�PDLQWHQDQFH�DQG�$3,�FDOOV�IRU�VHDUFKHV�

�

� A taxonomy lookup table typically contains a relatively small number of lookup records compared to the number of main table records.

� It is used as a valid table that facilitates data entry and drilldown search, where each lookup table record represents a valid lookup value from which the user can select, and the list of lookup values can be limited by main table search results.

� A taxonomy lookup table provides full validation against lookup table values and records, since all of the sub-table information is stored in the records of the lookup table.

� The relationship between main table records and taxonomy lookup table records is typically many-to-one (or perhaps many-to-few, if the lookup field is multi-valued).

� 1RWH: The above details apply to all lookup tables (flat, hierarchy, and taxonomy.)


SAP AG 2006

7D[RQRP\�$WWULEXWHV��$GGLWLRQDO�,QIRUPDWLRQ

$WWULEXWHV�ó &DQ�EH�DVVLJQHG�WR�DQ\�OHYHO�RI�WKH�KLHUDUFK\��FUHDWLQJ�LQKHULWDQFH�

LQ�FKLOG�QRGHV��LQKHULWDQFH�FDQQRW�EH�UHPRYHG�ó &DQ�EH�DVVLJQHG�WR�PXOWLSOH�QRGHV��LQ�GLIIHUHQW�EUDQFK�ó &DQQRW�EH�PDQGDWRU\��

ñ :RUNDURXQG��,I�WKH�WD[RQRP\�DVVLJQPHQW�LV�PDQGDWRU\��D�YDOLGDWLRQ�JURXS�FDQ�FKHFN�WKH�YDOXH��EXW�LW�LV�QRW�YDOLG�IRU�WKH�,PSRUW�0DQDJHU�

ó +DYH�QR�GHIDXOW�YDOXHó &DQ�UHO\�RQ�SULRULW\�WR�FKDQJH�WKH�GLVSOD\�RUGHU�RI�DWWULEXWHV�LQ�

0'0�'DWD�0DQDJHU��DGGLWLRQDO�VHWWLQJV�0'0�'DWD�0DQDJHU�XQGHU�&RQILJXUDWLRQ�Æ 2SWLRQV�

�

� The $OORZ�FXVWRP�SULRULWLHV option must be set to <HV for numbering priorities.


SAP AG 2006

0'0�7D[RQRP\��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� :RUN�LQ�WKH�WD[RQRP\�PRGH�RI�WKH�0'0�'DWD�

0DQDJHU� 8QGHUVWDQG�WKH�GLIIHUHQFHV�EHWZHHQ�DWWULEXWHV�DQG�

ILHOGV� &UHDWH�DQG�PDLQWDLQ�DWWULEXWHV

�


SAP AG 2006

5HDVVLJQLQJ�$WWULEXWHV

7D[RQRP\ ,QWURGXFWLRQ&UHDWLRQ�RI�D�7D[RQRP\/LQNLQJ�$WWULEXWHV�WR�&DWHJRULHV6XPPDU\$SSHQGL[�� 5HDVVLJQLQJ�$WWULEXWHV

�


SAP AG 2006

$WWULEXWH�5HDVVLJQPHQWV

([DPSOH�6WDUW�VLWXDWLRQ��3URGXFW�3RORBQHFNBVKLUW�KDV�WKH�DWWULEXWH�$UP�/HQJWK�DQG�KDV�EHHQ�DVVLJQHG�WR�FDWHJRU\�:RRO�*DOOHU\�

3URGXFW�7URXVHU�6XLW�KDV�EHHQ�DVVLJQHG�WR�FDWHJRU\�WURXVHU�VXLWV�DQG�GRHV�QRW�KDYH�WKH�DWWULEXWH�$UP�OHQJWK�

$WWULEXWH�DVVLJQPHQW�PXVW�EH�WUHDWHG�FDUHIXOO\�VR�DV�QRW�WR�MHRSDUGL]H�WKH�UHSRVLWRU\�REMHFWLYHV�

�


SAP AG 2006

5HDVVLJQLQJ�$WWULEXWHV

,I�QRZ��LQ�HUURU��WKH�SURGXFW�3RORBQHFNBVKLUW�LV�OLQNHG�WR�WKH�FDWHJRU\��WURXVHU�VXLWV��WKH�IROORZLQJ�ZDUQLQJ�ZLOO�DSSHDU�

,I�\RX�FRQILUP�WKLV�ZLWK�2.��WKH�DWWULEXWH�$UP�/HQJWK�ZLOO�EH�DGGHG�WR�WKH�WURXVHU�VXLWV�FDWHJRU\�

,I�\RX�UHDOL]H�WKDW�WKLV�LV�ZURQJ�DQG�UH�FDWHJRUL]H�SURGXFW�3RORBQHFNBVKLUW��WKH�DWWULEXWH�$UP�/HQJWK�ZLOO�UHVLGH�LQ�WKH�FDWHJRU\�WURXVHU�VXLWV�

�


SAP AG 2006

7UDQVIHUULQJ�5HFRUGV�%HWZHHQ�1RGHV

<RX�KDYH�WR�PDQXDOO\�XQOLQN�WKH�DVVLJQPHQW�RI�$UP�/HQJWK�WR�FDWHJRU\�WURXVHU�VXLWV�

�

� If, during the process, the product Polo-neck-shirt uses one of the trouser-suit-specific attributes, such as color, this attribute will be added to the wool gallery category when you transfer the product back to its correct category.

� Imagine the product you transfer in error has 20 attributes, and all attributes will be assigned to the wrong category. In addition, the product will immediately inherit all attributes from the new category and all levels above this new category.

� If you do not realize this immediately, it might be extremely difficult to roll this back into the status before the wrong transfer.

� If you have to move products from and to categories and many attributes are involved, use a Dummy category with none of its own attributes.


SAP AG 2006

7D[RQRP\�� $GYDQFHGó &KDQJLQJ�D�KLHUDUFK\�WUHH

ô %H�FDUHIXO�RI�LQKHULWHG�DWWULEXWHVó &RQYHUWLQJ�DWWULEXWHV�W\SHVó 0HUJLQJ�DWWULEXWHVó 6SOLW�QXPHULF�PXOWL�UDWLQJ�DWWULEXWHVó 3DUWLWLRQLQJ�FDWHJRULHV�IROORZLQJ�

DWWULEXWHVó &RQVROLGDWLQJ�FDWHJRULHVó 6SOLWWLQJ�PXOWL�OLQNHG�DWWULEXWH�WR�RQH�

IRU�HDFK�FDWHJRU\ó 0DNH�PDWFKLQJ�VHWV��$XWRPDWLF�

UHODWLRQVKLSV�EHWZHHQ�REMHFWV�EDVHG�RQ�FRPPRQ�DWWULEXWHV�YDOXHV��UHVXOW�RQO\�DYDLODEOH�ZLWKLQ�$3,�FDOOV�

ó &KDQJH�DWWULEXWHV�GHILQLWLRQ��H[WHQG�YDOXHV�OLVW��DGG�UDWLQJV��DQG�VR�RQ�

�


SAP AG 2006

,QGLUHFW�&KDQJHV�:LWKLQ�'DWD�0DQDJHU

� &KDQJLQJ�WKH�REMHFW�DVVLJQPHQW WR�FDWHJRULHV�ZKHQ�HGLWLQJ�UHFRUGV�FDQ�OHDG�WR�WD[RQRP\�FKDQJHV�

� ,I�D�QRQ�YDOXDWHG�DWWULEXWH�GRHV�QRW�H[LVW�LQ�WKH�WDUJHW�FDWHJRU\��WKH�DWWULEXWH�ZLOO�QRW�EH�OLQNHG�WR�WKH�WDUJHW�FDWHJRU\�õ 1R�LPSDFW�RQ�WKH�WD[RQRP\õ $WWULEXWH�LV�QR�ORQJHU�DYDLODEOH�IRU�WKH�REMHFW

� ,I�D�YDOXDWHG�DWWULEXWH�GRHV�QRW�H[LVW�LQ�WKH�WDUJHW�FDWHJRU\��WKH�DWWULEXWH�ZLOO�EH�OLQNHG�WR�WKH�WDUJHW�FDWHJRU\��FKDQJLQJ�WD[RQRP\�GHILQLWLRQ��õ %H�YHU\�FDUHIXO�ZKHQ�FKDQJLQJ�FDWHJRU\�DVVLJQPHQWõ 3UHYHQW�VXFK�FKDQJH�LI�QHFHVVDU\�E\�XVLQJ�UROHV�GHILQLWLRQV

�


�([HUFLVHV�

8QLW�� 0DQXDOO\�&UHDWH�DQG�/LQN�$WWULEXWHV�7RSLF�� 0'0�7D[RQRP\�7DEOH�


• :RUN�LQ�WKH�WD[RQRP\�PRGH�RI�WKH�0'0�'DWD�0DQDJHU�• 8QGHUVWDQG�WKH�GLIIHUHQFHV�EHWZHHQ�DWWULEXWHV�DQG�ILHOGV�• &UHDWH�DQG�PDLQWDLQ�DWWULEXWHV�

As part of the implementation, you would like to classify your master data in order to make searching more effective by assigning master data records to a hierarchy of categories described by attributes (characteristics).

3XUSRVH�This exercise illustrates the taxonomy maintenance. We will manually create taxonomy attributes in your Case_Study repository.

3UH�5HTXLVLWHV�� The repository has been created.

� The data model and taxonomy has been pre-determined. This exercise does not cover how to determine taxonomies.

� The repository is loaded.

8-1 6WDUW�6$3�0'0�'DWD�0DQDJHU

You will be using your existing Case_Study repository and the taxonomy called Category. This taxonomy was created as the default taxonomy when you first created your_Case_Study.

8-1-1 Make sure that your Case_Study repository is loaded.

8-1-2 Start the SAP MDM Data Manager application.


8-2 7UDQVLWLRQ�WR�WKH�7D[RQRP\�0RGH

8-2-1 Navigate to the Taxonomy Mode. Click the ‘7’ icon from the QDYLJDWLRQ�EDU��

If you do not see the nodes, right-click on Categories and select ([SDQG�%UDQFK or ([SDQG�(QWLUH�%UDQFK.

8-3 &UHDWH�7H[W�$WWULEXWHV 8-3-1 In the Attributes pane, right-click and�$GG�8-3-2 Enter a name for the new attribute

1DPH� $WWULEXWH�9DOXHV�Color White, Red, Blue,

Green, Black

8-3-3 Determine the type of attribute you are creating. Click�� .


8-3-4 Click to add possible values for the attribute. Enter “:KLWH��5HG��%OXH��*UHHQ��%ODFN” as a valid entry.

1RWH�that you can use drag and drop to change the list order or even sort it with the right-click.

8-3-5 Press�Shift+Enter to save the attribute for a final result that looks like this:

8-3-6 Repeat steps 8-3-1 to 8-3-5 with the following values:

1DPH� $WWULEXWH�9DOXHV�Accent Color White, Red, Blue,

Green, Black

Finish Metallic, Gloss, Satin, Matte.


8-4 &UHDWH�1XPHULF�$WWULEXWHV 8-4-1 Select $WWULEXWHV�Î�$GG�$WWULEXWH�from the menu bar. 8-4-2 Enter a name for the new attribute

1DPH� $WWULEXWH�9DOXHV�

Quantity

Nominal, Dimension = Quantity, Default unit = each, Decimal Places = 0 Multi-valued = yes

8-4-3 Determine the type of attribute you are creating. Click

8-4-4 Set the Attribute Detail as follows:

8-4-5 Shift+Enter to save the attribute.

8-4-6 Repeat steps 4.1 to 4.5 with the following values:


1DPH� $WWULEXWH�9DOXHV�

Item Height

Nominal, Dimension = Length, Default unit = centimeters, Decimal Places = 2 Multi-valued = yes

Item Width


Item Depth


Tip: You can copy and paste existing attributes.


8-5 &UHDWH�&RXSOHG�1XPHULF�$WWULEXWH

8-5-1 Select $WWULEXWHV�Î�$GG�$WWULEXWH�from the menu bar.

8-5-2 Determine the type of attribute you are creating. Click

8-5�3 (QWHU a name for the new attribute

1DPH� 'HOLPLWHU� &RXSOHG�QDPH�Width “ X “ /HQJWK

8-5-4 Enter a Dimensions for option and coupled option Dimension = /HQJWK

8-5-5 Enter Default Unit for both option and coupled option = FHQWLPHWHUV� 8-5-6 Enter Decimal Places = �.

8-5-7 Shift+Enter to save the attribute.

8-6 /LQNLQJ�RI�$WWULEXWHV Check that you have selected the Categories taxonomy in the drop-down list. We are

going to link attributes to specific nodes.

8-6-1 Right-click on Categories and select Expand Entire Branch or double-click on the root node “ categories” to open the tree.

8-6-2 Select “$SSOLDQFH” node and look for attribute “&RORU” .

8-6-2-1 Select attribute to enable the Link button and click on the button. Note that “$SSOLDQFH” is now in bold because it has at least one linked attribute.

8-6-2-2 Select “/DUJH” node under Appliance. The indicates that the attribute &RORU is inherited from the node 1 level higher.

8-6-2-3 Select�³3RUWDEOH´�node under Appliance. The indicates that the attribute &RORU is inherited from the node 2 level higher.

8-6-3 Now link the following attributes to the Appliance node: 4XDQWLW\��,WHP�+HLJKW��,WHP�'HSWK��DQG�,WHP�:LGWK. You can select all of these attributes as one time and link them.

8-6-4 Now select the�$FFHVVRU\�node and�link DOO the attributes.�8-6-5 Select the�7RRO�node and�link the following attributes:�4XDQWLW\��,WHP�+HLJKW��

,WHP�'HSWK��DQG�$FFHQW�&RORU. You can use your Ctrl key to select multiple attributes.


8-6-6 You can verify what nodes an attribute is linked to by selecting the attribute and then switching to the 8VDJH tab.�Below is the Quantity usage.

Compared to the Color attribute usages:


8-7 5HVXOWV You have created attributes and linked them to a sub-tree(s) in the taxonomy. In the Record view, you are now able to assign attribute values to each record.

�8-7-1 Enter the following information for 3 different records, which have been

assigned to the category of Stationary.:

)LHOG�1DPH� 5HFRUG�� 5HFRUG�� 5HFRUG��Category Stationary Stationary Stationary

Color White White Blue

Item Depth 32 cm 30 cm 32 cm

Item Height 34 cm 34 cm 34 cm

Item Width 28 cm 26 cm ‘blank’

Quantity 1 1 1 You can select all three records at the same time and enter the similar data.

8-7-2 Now you will change Record 3 from Stationary to Tool > Small > House.

Notice that &RORU and ,WHP�:LGWK are blue because they are not currently linked attributes for the selected Category.

8-7-3 Shift+Enter to save your change.


8-7-4 A Confirm Record Save dialog box will open.

Notice that Item Width is not listed because it had not values in the field and therefore will not be added as a new attribute. MDM is attempting to conserve all data.

8-7-5 Click on OK.

8-7-6 Now switch to the Taxonomy mode and expand the Tool tree. Notice how House is now in bold because it has a direct link.


8-8 6SOLW�$WWULEXWH�/LQN

If a particular category needed to have a modified attribute but you have already populated the records with data of a similar attribute, you can split the attribute. You can also do this before populating the record with data.��8-8-1 Select $SSOLDQFH node.

8-8-2 Right-click on the “&RORU” attribute and select the “ split” .

8-8-3 Select the split option to only split for the selected category (less impact if many categories are linked) and press the OK button.

Now you have 2 attributes with the same values but with different names and the split one is now only linked to the Appliance nodes.

You can now add different selections in the Color [Appliance] attribute without affecting the other Color attribute.


8-9 3DUWLWLRQLQJ�D�&DWHJRU\

If a taxonomy hierarchy does not have enough detail so that too many main table records are assigned to a particular leaf-node category, you can partition it into multiple child categories according to the values of a specified single-valued.

8-9-1 Select the Tool > Small > House node.

8-9-2 Right-click on the “ House” category and select “ partition” .

Note the only available value is the one that is a direct link verses a level 1 or 2 link.

8-9-3 The end result will look like this:

© SAP AG MDM100 3-101

SAP AG 2006

([SUHVVLRQV




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�

© SAP AG MDM100 3-102

SAP AG 2006

&RQWHQWV�� ([SUHVVLRQV

ö &DOFXODWLRQVö 9DOLGDWLRQVö $VVLJQPHQWV

0'0�([SUHVVLRQV

�

© SAP AG MDM100 3-103

SAP AG 2006

0'0�([SUHVVLRQV��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�&DOFXODWLRQV��9DOLGDWLRQ��DQG�

$VVLJQPHQW�([SUHVVLRQ�8VDJHV� :RUN�ZLWK�WKH�([SUHVVLRQ�(GLWRU

�

© SAP AG MDM100 3-104

SAP AG 2006

0'0�([SUHVVLRQV��%XVLQHVV�6FHQDULR

� $V�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RX�ZDQW�WR�NQRZ�ZKDW�IXQFWLRQDOLW\�FDQ�KHOS�WR�EXLOG�DQG�YDOLGDWH�GDWD�LQWHJULW\�LQ�\RXU�6$3�0'0�UHSRVLWRULHV��

�

© SAP AG MDM100 3-105

SAP AG 2006

([SUHVVLRQV ,QWURGXFWLRQ&UHDWLRQ�RI�D�([SUHVVLRQV([SUHVVLRQ�(GLWRU([HFXWLRQ�RI�([SUHVVLRQV

([SUHVVLRQV ,QWURGXFWLRQ

6XPPDU\

�

© SAP AG MDM100 3-106

SAP AG 2006

([SUHVVLRQV

� 0'0�H[SUHVVLRQV�DUH�([FHO�OLNH�IRUPXODV�WKDW�DUH�HYDOXDWHG�E\�0'0�DQG�UHWXUQ�D�GLVWLQFW�YDOXH�IRU�HDFK�UHFRUG�

� 7KH\�FDQ�EH�XVHG�WR�SHUIRUP�WHVWV�WKDW�LPSOHPHQW�VRSKLVWLFDWHG�EXVLQHVV�ORJLF�WKDW�JRHV�EH\RQG�VLPSOH�GDWD�LQWHJULW\�FKHFNV�

� ([SUHVVLRQV�FDQ�ö 5HIHUHQFH�ILHOGV��DWWULEXWHV��DQG�TXDOLILHUVö $FFHVV�ORRNXS�YDOXHV��ORRNXS�UHFRUGV��DQG�QHVWHG�ORRNXS�UHFRUGVö 1DYLJDWH�KLHUDUFK\��SDUHQW�FKLOG��DQG�VLEOLQJ�UHODWLRQVKLSV�WR�DFFHVV�UHODWHG�UHFRUGV

ö 5HIHUHQFH�WKH�RULJLQDO�GDWD�YDOXHV�RI�D�FKHFNHG�RXW�UHFRUGö 3HUIRUP�DULWKPHWLF��VWULQJ��DQG�ORJLFDO�RSHUDWLRQV�ö &DOO�EXLOW�LQ�IXQFWLRQVö 5HIHUHQFH�RWKHU�SUHYLRXVO\�GHILQHG�H[SUHVVLRQV

�

© SAP AG MDM100 3-107

SAP AG 2006

&UHDWLRQ�RI�([SUHVVLRQV

([SUHVVLRQV ,QWURGXFWLRQ([SUHVVLRQV�8VDJHV([SUHVVLRQ�(GLWRU([HFXWLRQ�RI�([SUHVVLRQV6XPPDU\

�

© SAP AG MDM100 3-108

SAP AG 2006

([SUHVVLRQV 8VDJH

� ([SUHVVLRQV�DSSHDU�ZLWKLQ�0'0�LQ�D�YDULHW\�RI�FRQWH[WV��7KHLU�UHVXOWV�DUH�LQWHUSUHWHG�DFFRUGLQJO\�DV�IROORZV�÷ &DOFXODWHG�ILHOGV��&DOFXODWLRQ�H[SUHVVLRQV�UHVXOW�LV�WKH�UHDG�RQO\�FDOFXODWHG�ILHOG�YDOXH�EDVHG�RQ�RWKHU�ILHOGV�RU�DWWULEXWHV�IRU�HDFK�UHFRUG�

÷ 9DOLGDWLRQV��9DOLGDWLRQ�H[SUHVVLRQV�UHVXOW�LV�WKH�%RROHDQ�VXFFHVV�RU�IDLOXUH�RI�WKH�YDOLGDWLRQ�IRU�HDFK�UHFRUG�

÷ $VVLJQPHQWV��$VVLJQPHQW�H[SUHVVLRQV�UHVXOW�LV�DVVLJQHG�WR�WKH�YDOXH�RI�WKH�VSHFLILHG�XVHU�HGLWDEOH�ILHOG�IRU�HDFK�UHFRUG�

�

� &DOFXODWLRQ expressions are defined in the MDM Console. � 9DOLGDWLRQ expressions are defined and executed in the MDM Data Manager. � $VVLJQPHQW expressions are defined and executed in the MDM Data Manager.

© SAP AG MDM100 3-109

SAP AG 2006

&DOFXODWHG )LHOG

$�&DOFXODWHG�)LHOG�LV�D�ILHOG�W\SH�ZKLFK�LV�GHILQHG�LQ�WKH�0'0�&RQVROH��

� &DOFXODWHG�LV�DYDLODEOH�IRU�7\SH�� %RROHDQ� &XUUHQF\� ,QWHJHU� 5HDO� 7H[W

� 6HW�&DOFXODWHG WR�<HV� 7KHQ�WKH�&DOFXODWLRQ LV�DYDLODEOH

DV�D�&DOFXODWLRQ�([SUHVVLRQ

�

� MDM evaluates a expression based on the data values of the referenced fields, attributes, and qualifiers of that record and the data values of any referenced records related to that record.

© SAP AG MDM100 3-110

SAP AG 2006

9DOLGDWLRQV

9DOLGDWLRQ�([SUHVVLRQV�� 5HWXUQ�D�%RROHDQ�VXFFHVV�RU�IDLOXUH�UHVXOW�� 'HILQH�FRPSOH[�WHVWV�IRU�DOO�W\SHV�RI�FRQGLWLRQV�DQG�WKHQ�UXQ�

WKRVH�WHVWV�DJDLQVW�D�JURXS�RI�RQH�RU�PRUH�UHFRUGV��DOO�ZLWKRXW�XVLQJ�D�TXHU\�ODQJXDJH�

� &DQ�EH�DVVLJQHG�WR�RQH�RU�PRUH�YDOLGDWLRQ�JURXSV�÷ (DFK�YDOLGDWLRQ�JURXS�LV�D�VHW�RI�YDOLGDWLRQV�WKDW�FDQ�EH�FRQYHQLHQWO\�H[HFXWHG�DV�D�JURXS�ZLWK�D�VLQJOH�VHOHFWLRQ�UDWKHU�WKDQ�IRUFLQJ�\RX�WR�UXQ�HDFK�LQGLYLGXDO�YDOLGDWLRQ�VHSDUDWHO\�

�

� Validation expressions can be used to perform all sorts of tests that implement sophisticated business logic that goes far beyond simple data integrity checks, including: y Making sure required fields and other fields that are required when another field has a particular

value all have a non-NULL value. y Making sure non-lookup fields that do not have pick lists to enforce data integrity have a legal

value (e.g. Price > 0). y Comparing the values of different fields to make sure the relative values are legal (e.g. Price >

Cost). � Compared to a transactional system, where data integrity tends to be absolute and all data must be

entered perfectly before the record is saved, MDM is a data management system with records that evolve and are enriched over their lifecycle. Moreover, since data in MDM is not linked to a single process or business application, there may be different validations and business rules that are applicable in different circumstances. As a result, MDM data entry and validations tend to be fairly flexible and forgiving rather than overbearing, to avoid encouraging a user to put junk values into fields that cannot be empty.

© SAP AG MDM100 3-111

SAP AG 2006

9DOLGDWLRQ�3URSHUWLHV÷ 1DPH��7KH�YDOLGDWLRQ�QDPH�÷ 'HVFULSWLRQ��7KH�YDOLGDWLRQ�GHVFULSWLRQ�÷ 7DEOH��7KH�WDEOH�RQ�ZKLFK�WKH�YDOLGDWLRQ�

RSHUDWHV�÷ %UDQFK�9DOXH��7KH�WD[RQRP\�ORRNXS�

ILHOG�YDOXH�RQ�ZKLFK�D�EUDQFK�EUDQFKHV�÷ *URXS��7KH�YDOLGDWLRQ�JURXSV�WR�ZKLFK�

WKH�YDOLGDWLRQ�EHORQJV�÷ 9DOLGDWLRQ��7KH�YDOLGDWLRQ�H[SUHVVLRQ�LWVHOI�÷ (UURU�0HVVDJH��7KH�HUURU�PHVVDJH�WR�GLVSOD\�ZKHQ�WKH�YDOLGDWLRQ�IDLOV�÷ $XWRPDWLF�([HFXWLRQ��:KHWKHU�RU�QRW�WR�UXQ�WKH�YDOLGDWLRQ�

DXWRPDWLFDOO\�HDFK�WLPH�\RX�VDYH�D�UHFRUG�DQG�ZKHWKHU�LW�LV�DGYLVRU\��ZDUQLQJ��RU�HQIRUFHG��HUURU��

÷ &DOODEOH��:KHWKHU�RU�QRW�WKH�H[SUHVVLRQ�VKRXOG�DSSHDU�LQ�WKH�GURS�GRZQ�OLVW�RI�IXQFWLRQV�VR�WKDW�LV�FDOODEOH�E\�RWKHU�YDOLGDWLRQV��<HV�1R�"

�

� The Validations tab (tab in bottom-right pane) contains a multi-object properties grid that consists of two subpanes: (1) the Validations pane, which lists the user-defined validations; and (2) the Properties pane, which lists the set of properties for each user-defined validation. Use the Validations tab to add, rename, delete and duplicate user-defined validations, and to view and edit validation properties.

© SAP AG MDM100 3-112

SAP AG 2006

$VVLJQPHQWV

� $VVLJQPHQW�H[SUHVVLRQV�UHWXUQ�D�GDWD�YDOXH�RI�DQ\�W\SH� <RX�FDQ�XVH�WKH�$VVLJQPHQWV WDE�WR�DGG��UHQDPH��GHOHWH��

DQG�GXSOLFDWH�DVVLJQPHQWV��DQG�WR�YLHZ�DQG�HGLW�DVVLJQPHQW�SURSHUWLHV�

�

� Like validations, MDM assignments are MDM expressions, except that: instead of returning a Boolean success or failure result, they can return a data value of any type; and instead of displaying the expression result for each record in a column in the Records pane, they can assign it to the value of the specified user-editable field.

© SAP AG MDM100 3-113

SAP AG 2006

$VVLJQPHQW 3URSHUWLHV÷ 1DPH��7KH�DVVLJQPHQW�QDPH�÷ 'HVFULSWLRQ��7KH�DVVLJQPHQW�

GHVFULSWLRQ�÷ 7DEOH��7KH�WDEOH�RQ�ZKLFK�WKH�

DVVLJQPHQW�RSHUDWHV�÷ %UDQFK�9DOXH��7KH�WD[RQRP\�

ORRNXS�ILHOG�YDOXH�RQ�ZKLFK�D�EUDQFK�EUDQFKHV�

÷ $VVLJQPHQW��7KH�DVVLJQPHQW�H[SUHVVLRQ�LWVHOI�÷ $VVLJQPHQW�)LHOG��7KH�ILHOG�WR�ZKLFK�WR�DVVLJQ�WKH�H[SUHVVLRQ�

UHVXOW�

�

� The Assignments tab contains a multi-object properties grid that consists of two subpanes: (1) the Assignments pane, which lists the user-defined assignments; and (2) the Properties pane, which lists the set of properties for each user-defined assignment.

© SAP AG MDM100 3-114

SAP AG 2006

([SUHVVLRQ�(GLWRU

7D[RQRP\ ,QWURGXFWLRQ&UHDWLRQ�RI�D�([SUHVVLRQV([SUHVVLRQ�(GLWRU([HFXWLRQ�RI�([SUHVVLRQV6XPPDU\

�

© SAP AG MDM100 3-115

SAP AG 2006

([SUHVVLRQ�(GLWRUV

� 7KH�VDPH�H[SUHVVLRQ�HGLWRU�LV�XVHG�IRU�&DOFXODWLRQV��9DOLGDWLRQV��DQG�$VVLJQPHQWV

�

� The expression associated with a calculated field, a validation, or an assignment is defined and edited using the same expression editor within the applicable expression dialog.

© SAP AG MDM100 3-116

SAP AG 2006

([SUHVVLRQ�(GLWRU�'LDORJ

� $Q�H[SUHVVLRQ�FRQVLVWV�RI�ILHOG�QDPHV��DWWULEXWH�QDPHV��TXDOLILHU�QDPHV��ORRNXS�YDOXHV��DWWULEXWH�WH[W�YDOXHV��RSHUDWRUV��DQG�IXQFWLRQV�

� 7KH�DYDLODEOH�RSWLRQV�LV�EDVHG�RQ�WKH�H[SUHVVLRQ�W\SH�DQG�ZKDW�LV�FUHDWHG�ZLWKLQ�WKH�UHSRVLWRU\��

�

� NOTE �,I�\RX�PDQXDOO\�W\SH�ILHOG��DWWULEXWH��TXDOLILHUV��RSHUDWRUV��DQG�IXQFWLRQ�QDPHV��0'0�automatically tokenizes the text you have just typed when you press Space, and highlights these tokens in blue.

� NOTE �<RX�PXVW�XVH�WKH�WRROEDU�EXWWRQV�WR�HQWHU�ORRNXS�YDOXHV��WH[W�DWWULEXWH�YDOXHV��DQG�measurement values (consisting of a number and a unit of measure). MDM highlights these tokens in magenta.

© SAP AG MDM100 3-117

SAP AG 2006

([SUHVVLRQ�(GLWRU�² )LHOGV

� )LHOGV��&KRRVH�IURP�WKH�GURS�GRZQ�OLVW�RI�ILHOGV�DQG�IRU�HDFK�ORRNXS�IURP�WKH�FDVFDGLQJ�PHQX�RI�ILHOGV�

� >2ULJLQDO@�LV�XVHG�ZKHQ�FRPSDULQJ�WKH�RULJLQDO�YDOXH�ZLWK�D�WUDQVIRUPHG�YDOXH�

� >5HFRUG@� �5HFRUG�,'

�

� An MDM expression can access not only the fields of the record itself, but also the record id and corresponding fields and data values of the virtual extended record.

� Specifically, the expression dialog can: (1) reference the record ids, fields, and data values of lookup records and nested lookup records; (2) navigate hierarchy, parent/child, and sibling relationships to reference the record ids, fields, and data values of related records; and (3) reference the original data values of a checked out record.

� The term “ field” includes fields, attributes, and qualifiers. � The [Record] virtual field is the id of the lookup or related record itself; it allows you to check if two

records are the same.

© SAP AG MDM100 3-118

SAP AG 2006

([SUHVVLRQ�(GLWRU�² 5HODWLRQVKLSV

� 5HODWLRQVKLSV��&KRRVH�IURP�WKH�GURS�GRZQ�OLVW�RI�UHODWLRQVKLSV��DQG�WKHQ�IURP�WKH�FDVFDGLQJ�PHQX�RI�ILHOGV�

�

� You can navigate a parent/child hierarchy relationship to reference the records and fields only a single level up or down.

� For a same-table relationship, the drop-down list cascades to the same set of fields as the Fields toolbar button and to any other relationships; each relationship can participate at most once in a navigation once either side is included.

© SAP AG MDM100 3-119

SAP AG 2006

([SUHVVLRQ�(GLWRU�² /RRNXSV

� /RRNXSV��&KRRVH�IURP�WKH�GURS�GRZQ�OLVW�RI�ORRNXSV�DQG�WKHQ�IURP�WKH�SRSXS�RI�ORRNXS�YDOXHV�

� 7KH�OLVW�RI�ORRNXS�ILHOGV�RI�WKH�FXUUHQW�WDEOH�IRU�DFFHVV�WR�WKHLU�ORRNXS�YDOXHV

� 7KH�HQWLUH�OLVW�RI�ORRNXS�WDEOHV�IRU�DFFHVV�WR�ORRNXS�YDOXHV�WKDW�DUH�QHVWHG�EHQHDWK�WKH�FXUUHQW�WDEOH�WKURXJK�LWV�ORRNXS�ILHOGV�

�

© SAP AG MDM100 3-120

SAP AG 2006

([SUHVVLRQ�(GLWRU�² 2SHUDWRUV�DQG�)XQFWLRQV

� 2SHUDWRUV��&KRRVH�IURP�WKH�GURS�GRZQ�OLVW�RI�RSHUDWRUV�

� )XQFWLRQV��&KRRVH�IURP�WKH�GURS�GRZQ�OLVW�RI�IXQFWLRQV�

�

© SAP AG MDM100 3-121

SAP AG 2006

([HFXWLRQ�RI�([SUHVVLRQV

([SUHVVLRQV ,QWURGXFWLRQ&UHDWLRQ�RI�D�([SUHVVLRQV([SUHVVLRQ�(GLWRU([HFXWLRQ�RI�([SUHVVLRQV6XPPDU\

�

© SAP AG MDM100 3-122

SAP AG 2006

0DQXDO�([HFXWLRQ�RI�([SUHVVLRQV

� &DOFXODWLRQV� 2Q�FUHDWLRQ�RI�D�QHZ�UHFRUG� %\�UHFDOFXODWLQJ�WKH�UHFRUG

� 9DOLGDWLRQV� 0DQXDOO\�� 3HUIRUPHG�GXULQJ�ZRUNIORZ�SURFHVV

� $VVLJQPHQWV� 0DQXDOO\�� ,QYRNHG�GXULQJ�ZRUNIORZ�SURFHVV

�

© SAP AG MDM100 3-123

SAP AG 2006

([HFXWLQJ�D�&DOFXODWHG�)LHOG

� 1HZ�UHFRUG�DGGLWLRQ�RU�LPSRUW� $IWHU�HGLWV��ULJKW�FOLFN�RQ�UHFRUG�DQG

FKRRVH�5HFDOFXODWH�

�

� The expression result is the read-only calculated field value based on other fields or attributes for each record.

© SAP AG MDM100 3-124

SAP AG 2006

0DQXDO�([HFXWLRQ�RI�9DOLGDWLRQV

� $IWHU�HGLWV��ULJKW�FOLFN�RQ�UHFRUG�DQG�FKRRVH�9DOLGDWLRQV�Æ([HFXWH�Æ VHOHFW�QDPH�RI�RSHUDWLRQ�

� 0'0�UXQV�WKH�YDOLGDWLRQV�DQG�GLVSOD\V�D�PHVVDJH�LQGLFDWLQJ�VXFFHVV�RU�IDLOXUH��

� &OLFN�2. WR�FORVH�WKH�GLDORJ�� 0'0�DGGV�D�YDOLGDWLRQ�UHVXOW�FROXPQ�IRU�HDFK�UHFRUG�

�

� See lesson “ Workflow” to see how validations are performed automatically.

© SAP AG MDM100 3-125

SAP AG 2006

0DQXDO�([HFXWLRQ�RI�$VVLJQPHQWV

� $IWHU�HGLWV��ULJKW�FOLFN�RQ�UHFRUG�DQG�FKRRVH�$VVLJQPHQW�Æ([HFXWH�Æ VHOHFW�QDPH�RI�RSHUDWLRQ�

� 0'0�UXQV�WKH�DVVLJQPHQW�DQG�GLVSOD\V�D�PHVVDJH�LQGLFDWLQJ�VXFFHVV�RU�IDLOXUH��

� &OLFN�2. WR�FORVH�WKH�GLDORJ�� 0'0�DGGV�DQ�$VVLJQPHQW�5HVXOW FROXPQ�IRU�HDFK�UHFRUG�

�

� Assignments are always invoked manually. � See lesson “ Workflow” to see how assignments are invoked automatically but must still be

processed manually.

© SAP AG MDM100 3-126

SAP AG 2006

6XPPDU\

([SUHVVLRQV ,QWURGXFWLRQ&UHDWLRQ�RI�D�([SUHVVLRQV([SUHVVLRQ�(GLWRU([HFXWLRQ�RI�([SUHVVLRQV6XPPDU\

�

© SAP AG MDM100 3-127

SAP AG 2006

0'0�([SUHVVLRQV��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�&DOFXODWLRQV��9DOLGDWLRQ��DQG�

$VVLJQPHQW�([SUHVVLRQ�8VDJHV� :RUN�ZLWK�WKH�([SUHVVLRQ�(GLWRU

�

© SAP AG MDM100 3-129

�([HUFLVHV�

8QLW�� 9DOLGDWLRQ�([SUHVVLRQ�7RSLF�� 0'0�'DWD�0DQDJHU�([SUHVVLRQV�


• 8QGHUVWDQG�&DOFXODWLRQV��9DOLGDWLRQ��DQG�$VVLJQPHQW�([SUHVVLRQ�8VDJHV�

• :RUN�ZLWK�WKH�([SUHVVLRQ�(GLWRU�

�$V�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RX�ZDQW�WR�NQRZ�ZKDW�IXQFWLRQDOLW\�FDQ�KHOS�WR�EXLOG�DQG�YDOLGDWH�GDWD�LQWHJULW\�LQ�\RXU�6$3�0'0�UHSRVLWRULHV��

3XUSRVH�This exercise will show you how to use the Expressions Editor to create three validations. The Expressions Editor is the tool used for Calculations and Assignments.

3UH�5HTXLVLWHV�� The repository has been created.

� The repository is loaded.

9-1 6WDUW�6$3�0'0�'DWD�0DQDJHU

You will be using your existing Case_Study repository and create the following three validations in the MDM Data Manager.

• /RQJ�'HVFULSWLRQ��(PSW\: Test that the Long Description field has data.

• ,WHP�ZLWK�3ULFLQJ: Test that a record has at least one price in the pricing table

• &DWHJRU\�)LHOG�3RSXODWHG: Test that a specific attribute is populated for a specific category.

9-1-1 Make sure that YourLetter_Case_Study repository is loaded.

9-1-2 Start the SAP MDM Data Manager application.

© SAP AG MDM100 3-130

9-2 /RQJ�'HVFULSWLRQ�9DOLGDWLRQ

All validations are created in the Data Manager under the Validation tab. You will start by creating a validation that tests to see that the Long Description field has data.

9-2-1 Right-click under Validation and select Add Validation

9-2-2 Enter the name: /RQJ�'HVFULSWLRQ��(PSW\

9-2-2-1 Double-click on [Validation Expression]

9-2-2-2 Select from Functions, IS_NOT_NULL

9-2-2-3 Select from Fields, Long Description

9-2-2-4 For an end result of ,6B127B18//�/RQJ�'HVFULSWLRQ� and click OK.

9-2-2-5 In the Error Message enter: The Long Description field is empty. Please populate this field before proceeding.

9-2-2-6 For Automatic Execution = Warning.

9-2-2-7 Set Callable = Yes.

9-2-3 Now select Product ID = A700

9-2-4 Right-click on the record select 9DOLGDWLRQV�!�([HFXWH�!�/RQJ�'HVFULSWLRQ��(PSW\.

9-2-5 Your Error Message will be displayed in a Record Validation(s) Complete dialog box. Click OK.

9-2-6 A new column will now appear in the Records pane. A red ; will be in front of record A700.

9-2-7 Now let’s run the test on all records. By doing a Ctrl+A and then right-click 9DOLGDWLRQV�!�([HFXWH�!�/RQJ�'HVFULSWLRQ�±�(PSW\�

9-2-8 You can sort the new column by clicking on it. The end results should look like this:

© SAP AG MDM100 3-131

9-3 ,WHP�ZLWK�3ULFLQJ�9DOLGDWLRQ

� You will create a validation that tests to see that records have at least one price in the Pricing table.


9-3-2 Enter the name: ,WHP�ZLWK�3ULFLQJ


9-3-2-2 Select from Functions, COUNT

9-3-2-3 Select from Fields, Pricing > [Record] – this will give you the number of records.

9-3-2-4 Next complete the formula with >0.

9-3-2-5 The result is COUNT(Pricing.[Record])>0 and click OK.

9-3-2-6 In the Error Message enter: Please enter at least one price in the Pricing table.

9-3-2-7 For Automatic Execution = Warning.

9-3-2-8 Set Callable = Yes.

9-3-3 Now select Product ID = B400 and delete all contents of the Pricing table. In the Record Detail for B400, double click on the Pricing field. In the column, Select lookup records, select *%3 and click Remove and then click 2..

9-3-4 Select all records.

9-3-5 Right-click 9DOLGDWLRQV�!�([HFXWH�!�,WHP�ZLWK�3ULFLQJ�

9-4 &DWHJRU\�)LHOG�3RSXODWHG

You will create a validation that tests to see that records are populated with a Category and if the Category = Stationary also has a value set for Quantity.


9-4-2 Enter the name: &DWHJRU\�)LHOG�3RSXODWHG


9-4-2-2 Select from Functions, IS_NOT_NULL

9-4-2-3 Select from Fields, Category > [Record]

9-4-2-4 The result is ,6B127B18//�&DWHJRU\�>5HFRUG@� and click OK.

9-4-2-5 In the Error Message enter: Category not populated.

9-4-2-6 For Automatic Execution = None.

9-4-2-7 Set Callable = No.

9-4-2-8 Save this validation.

© SAP AG MDM100 3-132

9-4-3 Select all records.

9-4-4 Right-click 9DOLGDWLRQV�!�([HFXWH�!��&DWHJRU\�)LHOG�3RSXODWHG� 9-4-5 Ten records will fail the validation. Nine because they had no Category

assigned to them. And 1 because the Category was Stationary but the Quantity attribute was not populated. Note that there are also 2 records that passed the validation that had the Category set to Stationary but had a Quantity of 1.

© SAP AG MDM100 3-133

SAP AG 2006

0DWFKLQJ�0RGH




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�

© SAP AG MDM100 3-134

SAP AG 2006

&RQWHQWV�� 'DWD�0DQDJHU�0DWFKLQJ�0RGH

'DWD�0DQDJHU�0DWFKLQJ�0RGH

�

© SAP AG MDM100 3-135

SAP AG 2006

0'0�0DWFKLQJ�0RGH��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�0DWFKLQJ�0RGH�� &UHDWH�WUDQVIRUPDWLRQ�UXOHV� 'HILQH�UXOHV� 6HW�XS�D�PDWFKLQJ�VWUDWHJLHV

�

© SAP AG MDM100 3-136

SAP AG 2006

'DWD�0DQDJHU�0DWFKLQJ�0RGH��%XVLQHVV�6FHQDULR

� :LWK�GXSOLFDWH�UHFRUGV�D�SRWHQWLDO��\RX�ZDQW�WR�NQRZ�KRZ�WR�HIILFLHQWO\�LGHQWLI\�GXSOLFDWH�UHFRUGV�E\�GHYHORSLQJ�DQ�HIIHFWLYH�PDWFKLQJ�VWUDWHJ\�DIWHU�LPSRUWLQJ�GDWD�LQWR�UHSRVLWRULHV��

�

© SAP AG MDM100 3-137

SAP AG 2006

'DWD 0DQDJHU�0DWFKLQJ 0RGH'DWD�0DQDJHU�0DWFK��0HUJH�&RQFHSWV'DWD�0DQDJHU�0DWFKLQJ�3URFHVV6XPPDU\

'DWD 0DQDJHU�0DWFKLQJ 0RGH

�

© SAP AG MDM100 3-138

SAP AG 2006

'DWD 0DQDJHU�0DWFKLQJ 0RGH�² 1HZ�LQ�63��

1HZ�0'0�0DWFKLQJ�)XQFWLRQDOLW\ø (QDEOHV�PDWFKLQJ�DQG�PHUJLQJ�

WR�VXSSRUW�WKH�GH�GXSOLFDWLRQ�RI�UHFRUGV�LQ�D�VLQJOH�HQYLURQPHQW

ø /RFDWH�LGHQWLFDO�DQG�GXSOLFDWH�UHFRUGV�ZLWKLQ�DQ�0'0�UHSRVLWRU\�IRU�FRQVROLGDWLRQ

ø 0DWFKLQJ�SURFHVV�LV�H[SRVHG�LQ�WKH�0'0�'DWD�0DQDJHU�DQG�VXSSRUWV�LQWHUDFWLYH��VWUDWHJ\�EDVHG�PDWFKLQJ�

ø $�PDWFKLQJ�VWUDWHJ\�FDQ�EH�DSSOLHG�WR�DQG�DJDLQVW�VHOHFWHGUHFRUGV��VHDUFK�UHVXOWV��RU�DOOUHFRUGV�RI�WKH�UHSRVLWRU\

�

© SAP AG MDM100 3-139

SAP AG 2006

6$3�0'0�,PSURYHV�'DWD�4XDOLW\

)XQFWLRQDO�DUHDV�RI�0'0�IXQFWLRQDOLW\�WKDW�UHODWH�WR�GDWD�TXDOLW\ø 'DWD�FOHDQVLQJ��1RUPDOL]DWLRQ�DQG�VWDQGDUGL]DWLRQ�RI�LQIRUPDWLRQ

ù 5HPRYDO�RI�QRQ�VLJQLILFDWLRQ�SXQFWXDWLRQ�DQG�VWDQGDUGL]DWLRQ�RI�WHUPV�XVHG�ZLWKLQ�D�ILHOG

ø 5XOHV�DQG�VWUDWHJLHV��'HILQLWLRQ�RI�UXOHV�WR�EH�XVHG�DQG�VWUDWHJLHV�WKDW�LPSOHPHQW�WKRVH�UXOHV�LQ�D�PL[�DQG�PDWFK�DSSURDFKù 'H�GXSOLFDWLRQù 0DWFKLQJ��DQG�PHUJLQJ��RI�REMHFWV�WR�REWDLQ�XQDPELJXRXV�DQG�FRQVLVWHQW�GDWD

1DWLYH�IHDWXUHV�RI�0'0�JXDUDQWHH�KLJK�TXDOLW\�VWDQGDUGV�IRU�PDVWHU�GDWD�WKURXJKRXW�WKH�HQWHUSULVH�

�

© SAP AG MDM100 3-140

SAP AG 2006

'DWD�0DQDJHU�0DWFK��0HUJH�&RQFHSWV


�

© SAP AG MDM100 3-141

SAP AG 2006

'DWD�0DQDJHU�0DWFKLQJ�0RGH��3URFHVV�)ORZ

�� 7UDQVIRUPDWLRQVú &UHDWH�D�YLUWXDO�ILHOG�WKDW�LV�D�

WUDQVIRUPHG�DQG�QRUPDOL]HG�YHUVLRQ�RI�D�ILHOG�LQ�WKH�UHSRVLWRU\

�� 5XOHVú 'HILQH�PDWFKLQJ�UXOHV�IRU�FRPSDULQJ�

ILHOG�YDOXHV�EHWZHHQ�UHFRUG�SDLUV�� 6WUDWHJLHV

ú $SSO\�D�PDWFKLQJ�VWUDWHJ\�WR�UHFRUGV�LQ�WKH�UHSRVLWRU\

ø 0'0�PDWFKLQJ�LV�UHFRUG�FHQWULFú (DFK�UHFRUG�KDV�LWV�RZQ�PDWFKLQJ�JURXS�RI�

]HUR�RU�PRUH�SRWHQWLDO�PDWFKHVú 0DWFKLQJ�VWUDWHJ\�LV�DSSOLHG�LQGLYLGXDOO\�WR�HDFK�

VHOHFWHG�UHFRUG�DQG�WKH�SRWHQWLDO�PDWFKHV�DUH�SODFHG�LQ�D�PDWFKLQJ�JURXS�IRU�HDFK�UHFRUG

�

© SAP AG MDM100 3-142

SAP AG 2006

0DWFKLQJ�0RGH

,QLWLDWH�0'0�'DWD�0DQDJHU�0DWFKLQJ�PRGH�

�

� Initiate MDM Data Manager Matching mode to display the appropriate working area for matching.

© SAP AG MDM100 3-143

SAP AG 2006

��7UDQVIRUPDWLRQV��1RUPDOL]DWLRQ

7UDQVIRUPDWLRQV�QRUPDOL]H�WKH�GDWD�E\�UHPRYLQJ�FKDQJLQJ�QRQ�VSHFLILF�LQIRUPDWLRQ��VXFK�DV�ø 3UHIL[HV DQG�VDOXWDWLRQV��'U��0U��0UV��3URI�ø 6XIIL[HV��-U��6U�ø &RPPRQ�DFURQ\PV��6W��/WG��*PE+��70��ø 3XQFWXDWLRQ PDUNVø &KDUDFWHUV��g WR�2(�� WR�2(��b WR�$(��c WR�$$��h WR�8(��Ë WR�,��e WR�

(��È WR�$��Ï WR�2��f WR�1

,03257$17��.HHS�LQ�PLQG�WKDW�GLIIHUHQW�ODQJXDJHV�DQG�FRXQWULHV �/WG��DQG�*PE+��IRU�H[DPSOH��PD\�KDYH�GLIIHUHQW�DEEUHYLDWLRQV

�

� Select the 7UDQVIRUPDWLRQV tab (while in Matching mode). � Many data elements, such as product descriptions, contain special characters that do not have any

semantic meaning, like dots, hyphens, and commas. Since these could potentially prevent identical real-world entities from being viewed as one and the same, they need to be removed. Characters can be eliminated from the product description by substituting each one with a blank.

� Transformations can be performed on single fields only. � After defining transformations, MDM creates new transformed fields that are given the suffix [XFM]

and that can be referenced when defining matching rules. A matching strategy is composed from one or more matching rules.

© SAP AG MDM100 3-144

SAP AG 2006

� 5LJKW�FOLFN�LQVLGH�WKH�7UDQVIRUPDWLRQV�DUHD�WR�DGG�D�QHZ�7UDQVIRUPDWLRQ

� (QWHU�D�QDPH�DQG�VHOHFW�D�GHVLUHG�ILHOG�IURP�GURSGRZQ�OLVW

� )LHOG�PXVW�EH�RI�W\SH�7H[W�RU�,QWHJHU

� )LHOG�PXVW�EH�VLQJOH�YDOXH

��7UDQVIRUPDWLRQV�7DE

� 7UDQVIRUPDWLRQV�UHSUHVHQW�IURP�WR�SDLUV�RI�YDOXHV�WR�EH�XVHG�ZKHQ�QRUPDOL]LQJ�GDWD�ZLWKLQ�D�ILHOG

�

� The 7UDQVIRUPDWLRQV tab allows you to create a virtual field that contains transformed values rather than the original source values.

� The Preview in the Properties area helps you to verify your transformation. � If you want to remove a value, leave the 7R property empty. � The )URP token is not case sensitive. This means that “ corp” will replace “ corp” , “ CORP” , and

“ Corp” . � The Transformation list is processed from top to bottom.

� Transformation can be reordered to influence the sequence in which they are processed.

© SAP AG MDM100 3-145

SAP AG 2006

� 8QGHU�6XEVWLWXWLRQV��GRXEOH�FOLFN�)URP ILHOG�

� (QWHU�WKH�FKDUDFWHU�RU�FKDUDFWHU�VWULQJ�WR�EH�UHSODFHG�

� 8QGHU�6XEVWLWXWLRQV��GRXEOH�FOLFN�7R ILHOG�

� (QWHU�WKH�FKDUDFWHU�RU�FKDUDFWHU�VWULQJ�WR�UHSODFH�WKH�)URP FKDUDFWHU�RU�FKDUDFWHU�VWULQJ�

� ,I�WKH�UHSRVLWRU\�LV�SRSXODWHG��WKH�3UHYLHZVKRZV�WKH�UHVXOW�RI�WKH�WUDQVIRUPDWLRQ�

��7UDQVIRUPDWLRQV��6XEVWLWXWLRQV

�

� It is helpful to define generic transitions first and to use it as a template for other transformations. y Duplicate the transformation and rename it.

� You do not have to use all transformations in the matching rules. � This is helpful to verify the effect of the transformation and identify potentially missing

transformations.

© SAP AG MDM100 3-146

SAP AG 2006

��5XOHV

� 5XOHV�GHILQH�ZHLJKWV�LQ�FDVH�RI�HTXDOLW\ù 9DOXHV�RI�ILHOGV��RU�ILHOGV�FRPELQDWLRQV��DUH�FRPSDUHGù 'HILQH�JLYHQ�ZHLJKW�ZKHQ�FRPSDULVRQ�VXFFHHGV�RU�IDLOVù ([DPSOH�

û 1RUPDOL]HG�DGGUHVV�PDWFKHV�Æ ��SRLQWVû =LS�FRGH�GRHV�QRW�PDWFK�Æ ��SRLQWV

� &RPSDULVRQ�FDQ�DOVR�EH�SHUIRUPHG�DIWHU�WRNHQL]LQJ�YDOXHVù 7RNHQV�DUH�LQGLYLGXDO�SLHFHV�RI�GDWD�ZLWKLQ�D�ILHOG

�

� Fields that originate from qualified tables (qualifier fields) can be a small problem in Support Package 04 when used as token equals because the Qualified record serves as one entire field comprised of the individual fields in the Qualified table.

� Matching on qualifiers will be supported with SP05.

© SAP AG MDM100 3-147

SAP AG 2006

��5XOHV�7DE

� 3URYLGH�WKH�IROORZLQJ�LQIRUPDWLRQ�ø 1DPH��5XOH�QDPHø )XQFWLRQ��6HOHFW�

HLWKHU�(TXDOV RU�7RNHQ�(TXDOV

ø )LHOGV��6HOHFW�IURP�GURSGRZQ��PD\�ZDQW�WR�XVH�ILHOG�GHILQHG�LQ�7UDQVIRUPDWLRQ�

ø 6XFFHVV��6FRUH�WR�DOORZ�ZKHQ�PDWFK�RFFXUV

ø )DLOXUH��6FRUH�WR�LQFOXGH�ZKHQ�QR�PDWFK��FRXOG�EH�QHJDWLYH�YDOXH�ø 8QGHILQHG��6FRUH�WR�LQFOXGH�LI�ILHOG�LV�1XOO

�

� The 5XOHV tab allows you to define matching rules for comparing values of record pairs. � Select the 5XOHV tab. � Right-click in the Rules area to add a new rule. � The matching functions include Equals (exact field match) and Token Equals (match on one or more

tokens). � Equals matches content of the entire field. � Token Equals splits the text into tokens and searches for a match on each token in the field (word

order not important). � Click on fields; a list of all available fields is displayed. Select the relevant fields for the current

matching rule. � Rules can be made up of single or multiple fields � 1RWH that all transformed fields are also displayed in the list. They can be identified by their name

and the suffix [XFM]. � Success defines the score if there is a match. � Failure is the score if there is no match. Negative values can also be assigned if there was no match

and the score needs to be reduced. � Undefined defines the score if the content of a field is compared with a null value (for example

record A has a description and record B has no description).

© SAP AG MDM100 3-148

SAP AG 2006

(TXDOV�)XQFWLRQ

9HQG� 9HQG�1DPH 9HQG�6WUHHW

B4819 Ben and Jerry’s

Record 1

9HQG� 9HQG�1DPH9HQG�6WUHHW

B4820

Ben & Jerry’s Corp.

9HQG� 9HQG�1DPH9HQG�6WUHHW

B4821

Ben & Jerry’s

Record 2

Record 3

,Q�WKH�H[DPSOH�DERYH��XVLQJ�WKH�IXQFWLRQ�(TXDOV�ZRXOG�UHWXUQ��PDWFKHV�IRU�9HQGRU�1DPH ILHOG�,I�WKH�9HQGRU�1DPH ILHOG�ZDV�WUDQVIRUPHG�ZLWK�VXEVWLWXWLRQV��Æ µDQG¶��&RUS��ÆEODQN��WKHQ�DOO�WKUHH�9HQGRU�1DPH ILHOGV�ZRXOG�EH�FRQVLGHUHG�HTXDO�

9HQG�0DWFKLQJ�)LHOG��7UDQVIRUPDWLRQ�)LHOG

9HQG�1DPHBen and Jerry’s

9HQG�1DPH>;)0@

Ben and Jerry’s

9HQG�1DPH>;)0@Ben and Jerry’s

9HQG�1DPH>;)0@

7KH�(TXDOV�IXQFWLRQ�FRPSDUHV�WKH�HQWLUH�YDOXH�RI�WKH�PDWFK�ILHOG��ILHOGV�FDQ�EH�FRPELQHG�IRU�PDWFKLQJ�DOVR�

�

� The set of functions will increase over time, making MDM matching highly extensible. � If you specify more than one field, the comparison is made on the combined fields.

© SAP AG MDM100 3-149

SAP AG 2006

7RNHQ�(TXDOV�)XQFWLRQ

7KH�7RNHQ�(TXDOV�IXQFWLRQ�FRPSDUHV�WKH�YDOXH�RI�WKH�WRNHQV�VHSDUDWHO\��ILHOGV�FDQ�DOVR�EH�FRPELQHG�IRU�PDWFKLQJ��

PDWFKLQJ�ILHOGV

7KUHH�QHZ�ILHOGV�IRU�PDWFKLQJWKH�9HQG1DPH

7KUHH�QHZ�ILHOGV�IRU�PDWFKLQJWKH�9HQG6WUHHW

9,$�9,7725,2�9(1(72*5283�%$&28�'$//2=$��9HQG6WUHHW9HQG1DPH9HQG�

üLýLþ�ÿ�� ü�� ü1ý�þ�ÿ �� ü�� ü1ýDþÿ�� ü�� üLýDþ�ÿ ��eü�� ü1ý�þ�ÿ�� ü�� ü1ý�þ�ÿ �� ü��

�� !#"�� $�!�%�%��'& (') ! (*) ü1ü ��+) � (*, , ü �

5HFRUG��

�

� Each unique token within the field is considered separately.

© SAP AG MDM100 3-150

SAP AG 2006

7RNHQ�(TXDOV�)XQFWLRQ�6FRULQJ

9HQG�9HQG�1DPH 9HQG�6WUHHW

A4819 Group Bacou Dalloz

Record 1

9HQG� 9HQG�1DPH

6FRUHYV��5HF��

A5219

Group Dalloz %DNRX

3 of 3 = 100%

9HQG� 9HQG�1DPHA5789

Bacou Dalloz Group

2 of 4 = 50%

Record 2

Record 3

9HQG�0DWFKLQJ�)LHOG 6FRUH

YV��5HF��

2 of 4 = 50%

9HQG�1DPH

,Q�WKH�H[DPSOH�EHORZ��XVLQJ�WKH�7RNHQ�(TXDOV�IXQFWLRQ�ZRXOG�UHWXUQ�FDOFXODWHG�VFRUHV�IRU�UHFRUGV��DQG��EDVHG�RQ�9HQGRU1DPH�

�

� The total number of tokens is the accumulation of the number of unique tokens when comparing two records. � Record 1 vs. Record 2 has a total of three unique tokens and all three match. � Record 1 vs. Record 3 has a total of four unique tokens, and two of the four match. � Record 2 vs. Record 3 has a total of four unique tokens, and two of the four match.

� The matching score vs. Record 1 percentage (from table above) is applied to the corresponding rule’s score and then added to the total score.

© SAP AG MDM100 3-151

SAP AG 2006

��6WUDWHJLHV�7DE

6WUDWHJLHV�XVH�UXOHV�WR�FUHDWH�D�PDWFK�VFRUHø ,Q�WKH�6WUDWHJLHV WDE��\RX�GHILQH�PDWFKLQJ�VWUDWHJLHV�FRQVLVWLQJ�RI�

PDWFKLQJ�UXOHV��/RZ�DQG�+LJK�7KUHVKROG�DUH�XVHG�WR�FODVVLI\�WKH�PDWFKLQJ�UHVXOWV�DQG�PXVW�EH�VHW�PDQXDOO\�

ø 7KH�PDWFK�VFRUH�LV�FDOFXODWHGIURP�DOO�WKH�DFWLYH�UXOHV LQ�WKH�VWUDWHJ\

ø 0LQLPXP�VFRUH��/RZHVW�SRVVLEOH�VFRUH��FDOFXODWHG�DXWRPDWLFDOO\�

ø 0D[LPXP�VFRUH��+LJKHVW�SRVVLEOH�VFRUH��FDOFXODWHG�DXWRPDWLFDOO\�

ø +LJK�WKUHVKROG��5HFRUGV�DUH�YHU\�OLNHO\�GXSOLFDWHV

ø /RZ�WKUHVKROG��5HFRUGV�DUH�YHU\�OLNHO\�QRW�GXSOLFDWHV

�

� Select the 6WUDWHJLHV tab. � Right-click in the Strategies area to add a new strategy. � Scoring Rules shows a list of all defined rules. By selecting the ,QFOXGH flag, a rule is added to the

matching strategy. � Minimum and maximum scores are automatically calculated based on the rules in effect (checked) in

the strategy.

© SAP AG MDM100 3-152

SAP AG 2006

'DWD�0DQDJHU�0DWFKLQJ�3URFHVV


�

© SAP AG MDM100 3-153

SAP AG 2006

5XQ�0DWFKLQJ

� 0DWFKLQJ�PRGH�RIIHUV�VHYHUDO�ZD\V�WR�PDWFK�UHFRUGV�

� 7R�H[HFXWH�PDWFKLQJ��VHOHFW�RQH�RU�PRUH�UHFRUGV�IURP�WKH�UHFRUG�VHW�DQG�ULJKW�FOLFN�

� 6HOHFW�0DWFK�5HFRUGV IURP�WKH�FRQWH[W�PHQX�ù 6HOHFWHG�YV��6HOHFWHGù 6HOHFWHG�YV��5HVXOWVù 6HOHFWHG�YV��$OOù 5HVXOWV�YV��5HVXOWVù 5HVXOWV�YV��$OO�ù $OO�YV��$OO

�

� Several options are available for matching: � Selected vs. Selected: Evaluation of the manually selected records versus themselves. � Selected vs. Results: Evaluation of the manually selected records versus the current record set

which could be narrowed by a search or mask. � Selected vs. All: Evaluation of the manually selected records versus the entire repository. � Results vs. Results: Evaluation of the record set versus themselves. � Results vs. All: Evaluation of the current record set versus the entire repository. � All vs. All: Evaluation of all records compared to the entire repository.

© SAP AG MDM100 3-154

SAP AG 2006

,GHQWLI\�3RWHQWLDO�'XSOLFDWHV

ø &RXQW�GHILQHV�WKH�QXPEHU�RI�UHFRUGV�WKDW�PDWFK�WKH�VHOHFWHG�UHFRUG�

ø &ODVV�DQG�6FRUH�UHIOHFW�WKH�UHVXOW�RI�WKH�PDWFKLQJ�

ø 6ZLWFK�WR�WKH�0DWFKHVWDE�WR�GLVSOD\�WKH�UHFRUGV�WKDW�PDWFK�WKH�VHOHFWHG�UHFRUG�

ø 7KLV�WDE�ZLOO�VKRZ�PDWFKLQJ�UHFRUGV�LQ�GHWDLO�

8WLOL]LQJ�WKH�VFRULQJ�VWUDWHJLHV��ZH�FDQ�EHWWHU�LGHQWLI\�WKRVH�UHFRUGV�WKDW�DUH�SRWHQWLDO�GXSOLFDWHV�

�

� Only the highest score is displayed in the Records view. � You can check the detailed scoring for each rule of the strategy.

© SAP AG MDM100 3-155

SAP AG 2006

0HUJH�'XSOLFDWHV

ø 6HOHFW�WKH�UHFRUGV�\RX�ZDQW�WR�PHUJH�E\�VHWWLQJ�WKH�,QFOXGHFKHFNER[

ø 6ZLWFK�WR�WKH�0HUJH WDEø 6FUHHQ�VKRZV�DOO�VHOHFWHG�UHFRUGV�

DQG�WKH�UHFRUG�RQ�ZKLFK�WKH�PDWFK�ZDV�SHUIRUPHG�

ø ,GHQWLFDO�GDWD�LV�GLVSOD\HG�LQ�%/$&.ø 'LIIHUHQW�GDWD�LV�GLVSOD\HG�LQ�5('ø 2QH�UHFRUG�ZLWK�

18//�GDWD�LV�LQ�%/8(

�

� You can check the detailed scoring for each rule of the strategy. � You have several options for updating the merged record:

� If the fields are correct, right-click on the 0HUJHG�5HFRUG column heading and select either: - Set All Equal: Moves all fields that have equal values into the merged record - Set All Equal or Null: Moves all fields that have equal or null values into the merged record

� Field values for those fields not merged automatically can be managed one at a time: y Double-click on the record value you want to send to the merged record to transfer the value.

© SAP AG MDM100 3-156

SAP AG 2006

6LQJOH�5HFRUG�5HVXOWLQJ�IURP�0HUJH��

� $V�D�UHVXOW�RI�WKH�PHUJH��WKH�IROORZLQJ�ZLOO�WDNH�SODFH�ù 0DWFKLQJ�UHFRUGV�ZLOO�EH�UHSODFHG�E\�D�VLQJOH�PHUJHG�UHFRUGù .H\�PDSSLQJV�IURP�RULJLQDO�UHFRUGV�ZLOO�EH�FRSLHG�WR�WKH�PHUJHG�UHFRUG

1RWH��WKH�PHUJHG�UHFRUG�FRQWDLQV�RQO\�RQH�RI�WKH�ROG�SDUW�QXPEHUV��7KH�UHFRUGV�KDYH�EHHQ�PHUJHG�LQWR�D�QHZ�VLQJOH�UHFRUG�

�

� You cannot merge records when some are checked in and others are checked out. You FDQ compare them.

� Partner ID/MDM-ID (auto ID) is kept in the background automatically.

© SAP AG MDM100 3-157

SAP AG 2006

6LQJOH�5HFRUG�5HVXOWLQJ�IURP�0HUJH��

- 2QFH�WKH�QHZ�PHUJHG�UHFRUG�KDV�EHHQ�SRSXODWHG��ULJKW�FOLFN�DQ\ZKHUH�LQVLGH�WKH�0HUJHG�5HFRUG FROXPQ��QRW�RQ�WKH�KHDGHU�URZ��WR�PHUJH�WKH�UHFRUG�

- :KHQ�\RX�FRQILUP�WKH�PHVVDJH��WKH�UHFRUGV�DUH�PHUJHG�

- 7KH�RULJLQDO�UHFRUG�GDWD�LV�QRZ�UHSODFHG�ZLWK�WKH�PHUJHG�UHFRUG�GDWD�DQG�WKH�NH\�PDSSLQJ�LQIRUPDWLRQ�RI�WKH�RULJLQDO�UHFRUGV�LV�DSSHQGHG�WR�WKH�PHUJHG�UHFRUG�DXWRPDWLFDOO\�

�

� You cannot merge records when some are checked in and others are checked out. You FDQ compare them.

� A new record number (autoID) is assigned to the new record. � Partner ID/MDM-ID (auto ID) is kept in the background automatically. � Business processes must be in place to support the new merged record.

© SAP AG MDM100 3-158

SAP AG 2006

6XPPDU\


�

© SAP AG MDM100 3-159

SAP AG 2006

0'0�0DWFKLQJ�0RGH��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�0DWFKLQJ�0RGH�� &UHDWH�WUDQVIRUPDWLRQ�UXOHV� 'HILQH�UXOHV� 6HW�XS�D�PDWFKLQJ�VWUDWHJLHV

�

© SAP AG MDM100 3-161

�([HUFLVHV�

8QLW�� 6$3�0'0�0DWFKLQJ�0RGH�7RSLF�� 0'0�0DWFKLQJ�0RGH�


• 8QGHUVWDQG�WKH�0DWFKLQJ�0RGH��• &UHDWH�WUDQVIRUPDWLRQ�UXOHV�• 'HILQH�UXOHV�• 6HW�XS�D�PDWFKLQJ�VWUDWHJLHV��

:LWK�GXSOLFDWH�UHFRUGV�D�SRWHQWLDO��\RX�ZDQW�WR�NQRZ�KRZ�WR�HIILFLHQWO\�LGHQWLI\�GXSOLFDWH�UHFRUGV�E\�GHYHORSLQJ�DQ�HIIHFWLYH�PDWFKLQJ�VWUDWHJ\�DIWHU�LPSRUWLQJ�GDWD�LQWR�UHSRVLWRULHV��

3XUSRVH��This exercise shows you how to compare records for possible duplication. In YourLetter_Case_Study repository you have so far entered data from the NewYork and London remote systems. The Data is similar but is it the same data? We will investigate that topic in this exercise.

3UHUHTXLVLWHV��MDM Server has been mounted and started

The repository &DVHB6WXG\ is ORDGHG� �10-1� 6WDUW�6$3�0'0�'DWD�0DQDJHU�

Start the SAP MDM Data Manager Application.

10-1-1 Connect to MDM Repository�Repository: Yourletter_Case_Study�User: Admin and OK.

10-1-2 Take note of the number of records you have in your repository.

© SAP AG MDM100 3-162

�� 0DWFKLQJ�&ULWHULD

Matching criteria can only defined in the Matching Mode of the Data Manager. There are 3 steps in defining the matching criteria:

• Transformations - normalize the data by removing/changing non-specific information.

• Rules - define weights in case of equality.

• Strategies - use rules to create a match score.

10-2-1 Switch to the Matching Mode.

�� 'HILQLQJ�7UDQVIRUPDWLRQV In transformation, you will define what changes are required within your data so that unique records can be compared to each other. We will apply some basic transformations.

10-3-1 Select the Transformation tab.

10-3-2 Right-click under Transformations on the left and select $GG�7UDQVIRUPDWLRQ.

10-3-2-1 Name the new transformation: 5HPRYH�([WUD�&KDUDFWHUV� You will now define the transformation.

10-3-2-2 Select the Field = Name

10-3-2-3 Under Substitutions add the following with each To = space (not a blank).

© SAP AG MDM100 3-163

10-3-2-4 In our current set of data will only need to use the first substitution but we will keep the rest for future records. You can see the results of your substitutions by clicking on a record and then examining the Preview area.

10-3-2-5 Shift+Enter to save.

10-3-3 Right-click under Transformations on the left and select $GG�7UDQVIRUPDWLRQ.

10-3-3-1 Name the new transformation: &KDQJH�3URGXFW�1DPHV� You will now define the transformation.

10-3-3-2 Select the Field = Name

10-3-3-3 Under Substitutions add to the From = icebox and To = refrigerator.

10-3-3-4 Select Product ID A330 to see the results of your substitutions in the Preview area.

10-3-3-5 Shift+Enter to save.

10-4 'HILQLQJ�5XOHV In the Rules tab, you will define two rules that will be applied. Here they are in English terms:

If 3URGXFW�1DPH is the same give 40 points and if 'LYLVLRQ is the same then give 10 points.

10-4-1 Click on the Rules tab

10-4-2 Right-click under Rules and $GG�5XOH.

10-4-3 Name the first rule: 3URGXFW�1DPH�5XOH

© SAP AG MDM100 3-164

10-4-4 Set the properties as follows:

3URSHUWLHV�1DPH� 9DOXH�Function Token Equals

Fields Change Product Names [XFM]

Success 40

Failure 0

10-4-5 Shift+Enter to save.

10-4-6 Repeat steps 4.1 to 4.5 for the rule: 'LYLVLRQ�5XOH�with the following properties.

3URSHUWLHV�1DPH� 9DOXH�Function Equals

Fields Division

Success 10

Failure 0

Undefined 5

10-5 'HILQLQJ�6WUDWHJLHV Now that we have defined the transformation and rules, you will need to define how you are going to apply them.

10-5-1 Click on the Strategies tab.

10-5-2 Right-click under Strategies and $GG�6WUDWHJ\.

10-5-3 Name the rule: 3URGXFW�6WUDWHJ\.

© SAP AG MDM100 3-165

10-5-4 You will include both Scoring Rules by placing a check in the Include column.

Note that the Max Score will not be updated until you save the strategy.


10-5-6 Set the Threshold so that you can determine when a record should be flagged as a High (green), Low (blue), or below the Low (red) match.

3URSHUWLHV�1DPH� 9DOXH�High Threshold 40

Low threshold 30


10-6 $SSO\LQJ�WKH�0DWFKLQJ�6WUDWHJ\�WR��5HFRUG

You will now apply your strategy to 1 record in the repository. You must be in the Matching Mode to perform the following steps.

10-6-1 Sort your records by Product ID and select Product ID = 102 (Hand Dryer).

10-6-2 Now right-click on the above selected record and select 0DWFKLQJ�!�6HOHFWHG�YV�5HVXOWV�!�3URGXFW�6WUDWHJ\��This is the same as choosing�0DWFKLQJ�!�6HOHFWHG�YV�$OO�!�3URGXFW�6WUDWHJ\�since you have not applied any filters or narrowed the search of your results.

You will now see 3 new columns called [Count], [Class], and [Score]. The values tell you that there is 1 matching record which is in the threshold of High with a total score of 50.

© SAP AG MDM100 3-166

10-6-3 Now to see what records match your selected record, switch to the Matches tab.

The Product ID, B100, is a match.

10-6-4 You will now start the merging process first confirming that the records are actually the same and then merge them. Click on the Include box in front of B100 record and proceed to the next step.

10-7 0HUJLQJ�'XSOLFDWH�5HFRUGV 10-7-1 Switch to the Merge tab.

The various colors help to identify similar text. Black = identical, Red = different, Blue = one field is NULL.

© SAP AG MDM100 3-167

10-7-2 You now realize that they are the same record and want to merge them into one record. You must decide on the following tactics:

All Black text will be used in the new merged record.

All Red text will be taken from Product ID, 102.

All Blue text will be added to the final record.

10-7-3 Now right-click on the title bar: hand-dryer (B100) and select Set All. Notice that the text is still colored for Hand Dryer (102).

10-7-4 Now, you will move the text from Hand Dryer (102) into the [Merge Record] column. Right-click on the field, Hand Dryer, and right-click. Select Set.

10-7-5 Repeat step 6.7 for the values: Bathroom, Deluxe hand held steamer…, and Benneton KG.

10-7-6 For the value USD, right-click and select Append. You will now have both GBP and USD values in the Pricing field.

10-7-7 Now right-click anywhere in the [Merge Record] column and select Merge Records.

10-7-8 You will get a Confirmation box that says:

The reason being that Sales Price has $30 in the Hand Dryer record but Null for the [Merged Record]. Click Yes to proceed.

© SAP AG MDM100 3-168

10-8 9HULI\�0HUJH�DQG�.H\�0DSSLQJV In this step you will go back to Record Mode to examine the results of your merge.

10-8-1 Click on Record Mode. Notice that you have one less record than before. You no longer have record 102.

10-8-2 Select Product B100. Notice that it has the correct data and it has the GBP and USD Pricing data.

10-8-3 Right-click on the selected record and select Edit Key Mappings.

Here you will see the keys for both remote systems.

10-9 $SSO\LQJ�WKH�0DWFKLQJ�6WUDWHJ\�WR�$OO�5HFRUGV Now you will compare all records in your repository to see if there are any more matches.

10-9-1 Switch modes to Matching mode and right click on any record 0DWFKLQJ�!�$OO�YV�$OO�!�3URGXFW�6WUDWHJ\ which will give you the same result as 0DWFKLQJ�!�5HVXOWV�YV�5HVXOWV�!�3URGXFW�6WUDWHJ\ and 0DWFKLQJ�!�5HVXOWV�YV�$OO�!�3URGXFW�6WUDWHJ\�

10-9-2 Click on the column header [Score] to resort the list.

The value in the [Score] column is the highest score received by that record. Remember a record can have more than one matching record. Some records match 2 other records while others match only 1 or none.

© SAP AG MDM100 3-169

10-9-3 Start by selecting record 101 which has 2 matches and switch to the Matches tab.

You will now see 2 records. The record 106 is definitely NOT a match as it is a portable cloths washer. But the A340 appears to be a match.

10-9-4 Click on the Include box in front of A340 record.

10-9-5 Switch to the Merge tab.

10-9-6 Set the [Merge Record] to this:

Most of the information is from record 101, but notice the Product ID and Pricing.

10-9-7 Now right-click anywhere in the [Merge Record] column and select Merge Records.

10-9-8 Then go to Record mode and examine Record Details for A340.

© SAP AG MDM100 3-171

SAP AG 2006

:RUNIORZ




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�

© SAP AG MDM100 3-172

SAP AG 2006

&RQWHQWV�� ([SODQDWLRQ�RI�:RUNIORZ�7DE�ZLWKLQ�0'0� 'HWDLOV�RI�9LVLR�FRPSRQHQWV�XVHG�E\�0'0

0'0�:RUNIORZ

�

© SAP AG MDM100 3-173

SAP AG 2006

0'0�:RUNIORZ��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� ([SODLQ�WKH�GLIIHUHQW�HOHPHQWV�RI�D�ZRUNIORZ� 5XQ�D�VLPSOH�ZRUNIORZ

�

© SAP AG MDM100 3-174

SAP AG 2006

0'0�:RUNIORZ��%XVLQHVV�6FHQDULR

� $V�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RX�ZDQW�WR�NQRZ�ZKDW�IXQFWLRQDOLW\�FDQ�KHOS�WR�HQIRUFH�GDWD�LQWHJULW\�LQ�\RXU�6$3�0'0�UHSRVLWRULHV�

�

© SAP AG MDM100 3-175

SAP AG 2006

0'0�:RUNIORZ ,QWURGXFWLRQ&UHDWLRQ�RI�DQ�0'0�:RUNIORZ5XQQLQJ�DQ�0'0�:RUNIORZ6XPPDU\

0'0�:RUNIORZ ,QWURGXFWLRQ

�

© SAP AG MDM100 3-176

SAP AG 2006

0'0�:RUNIORZ�,QWURGXFWLRQ

� 7KH�0'0�:RUNIORZ�HQDEOHV�WKH�RUFKHVWUDWLRQ�RI�SDUDOOHO�DQG�VHTXHQWLDO�DFWLYLWLHV�DW�WKH�GDWD�PDQDJHPHQW�OHYHO��LQFOXGLQJ�XVHU�WDVNV��YDOLGDWLRQV��DQG�DSSURYDOV�

� $�XVHU�IULHQGO\��GHVLJQ�WLPH�HQYLURQPHQW�DOORZV�TXLFN�DQG�HDV\�FUHDWLRQ�DQG�PDQLSXODWLRQ�E\�HQG�XVHUV�

� *URXSV�RI�UHFRUGV�FDQ�EH�PRYHG�WKURXJK�WKH�ZRUNIORZ�DW�UXQWLPH�DV�ORJLFDO�SDFNDJHV��SURYLGLQJ�TXLFN�DFFHVV�WR�WKH�UHOHYDQW�GDWD�

� )OH[LEOH�DJHQW�DVVLJQPHQW�LV�EDVHG�RQ�XVHUV�RU�UROHV�� (PEHGGHG�YDOLGDWLRQV�SURYLGH�GDWD�TXDOLW\�FKHFNV�DW�DQ\�

WLPH�LQ�WKH�SURFHVV�

�

� MDM Workflows consist of a sequence of steps that allow you to orchestrate a series of operations including user tasks, validations, and approvals to automate business processes at the data management level.

© SAP AG MDM100 3-177

SAP AG 2006

:RUNIORZ�7HUPLQRORJ\

� :RUNIORZ��D�VHTXHQFH�RI�VWHSV�WKDW�DOORZ�\RX�WR�RUFKHVWUDWH�D�VHULHV�RI�RSHUDWLRQV�WKDW�LQFOXGH�XVHU�WDVNV��YDOLGDWLRQV��DQG�DSSURYDOV��DXWRPDWLQJ�EXVLQHVV�SURFHVVHV�DW�WKH�GDWD�PDQDJHPHQW�OHYHO�

� 6WHS��D�HOHPHQW�ZLWKLQ�D�ZRUNIORZ�WKDW�UHTXLUHV�SURFHVVLQJ�E\�D�XVHU�

� 7KUHDG��D�VHTXHQFH�RI�RQH�RU�PRUH�VWHSV�LQ�D�JURXS�RU�LQ�D�EUDQFK�RI�D�ZRUNIORZ�

� 7DVN��VKRZLQJ�XS�LQ�HDFK�XVHU¶V�LQERXQG�WDVN�TXHXH�ZLWKLQ�WKH�0'0�'DWD�0DQDJHU��UHDG\�IRU�SURFHVVLQJ�E\�WKH�XVHU�

� -RE��FRQVLVWV�RI�WKH�JURXS�RI�UHFRUGV�WKDW�PRYH�WKURXJK�HDFK�VWHS�LQ�WKH�ZRUNIORZ�DV�D�VHULHV�RI�WDVNV�

�

© SAP AG MDM100 3-178

SAP AG 2006

*UDSKLFDO�ZRUNIORZ�GHILQLWLRQ�HQYLURQPHQW . 3UHGHILQHG�HOHPHQWV�IRU��

/ 0�132�4�53687:9 ;�9 7:9 2<1/ =>5�?@9 A�537:9 B�C81ED<5�F�F�4GBE;85 ? 1

5�CHAICHB�7G9 J:9 63587:9 B�C31/ K�4LB�682<1H1NM�BAE2 ?@9OCEP

QLR 4S5�C�6ET�D8M�2�4LP�2ED8P�4LB�U FHV. $JHQW�DVVLJQPHQW�

/ 0�132�4XW R 58132EA/ Y>B? 2EW R 581H2HA

. $SSURYDO�GHILQLWLRQV�/ Z+9@CHP�? 2[B4�MIU ? 7:9\F�? 2]5�F�F�4GBE;82 4^1/ =>5�4G9 BU31_5�F F�4XBE;E5�?`7Sa�FH231 Q 1E23b�UH2�C87G9 5�? DH63BC36 U�4:4S2�C37LD<5�C8a]1 9OCHP�? 23V

. 7LPHRXW�GHILQLWLRQV�/ c�9 M�23B�U87^1_JSB4�9 7d2�4S5<7e9 BCN68a36 ? 2<1[5�CHA�AU 4L5<7:9 B�C]7:9 M�2H1/ f�U87dB M�587d2HAgC�BE7:9 JX9@6<587:9 BCH1 R 53132EA�BC_7:9 M�23B�U87d1

Microsoft Visio Professional license required for design time

0'0�:RUNIORZ�'HVLJQ�7LPH��06�9LVLR��

�

� The flow diagram representing a workflow is designed using a Microsoft Visio plug-in, making workflow definition directly accessible.

� Microsoft Visio is a familiar desktop application that is part of the popular Microsoft Office Suite, which is readily available and easy-to-use. This makes MDM Workflow definition directly accessible even to end users, who do not need to install or learn more complex process-modeling applications.

� The Visio plug-in includes a straightforward MDM workflow stencil of roughly a dozen shapes that embodies all of the workflow design-time functionality and features the familiar three-pane structure typical of Win32 MDM applications. The plug-in is installed when the MDMWorkflowInstall application is installed.

© SAP AG MDM100 3-179

SAP AG 2006

. :RUNIORZ�H[HFXWLRQ/ hiB4Gj`J:? BEkl9OC3187S5 C36H2<1 Q m B R 1HV�635 C R 2�1H7d5 4d7d2HA R 5<1H2HA�B�C]7GTH2�53;E5�9@? 5 R ? 2]k�B4GjnJ:? B�k

A�2<J:9\C�9 7:9 BC81/ hiB4Gj`J:? BEko7S581�jp1[P4LB�U�FH2HA R a]137d587GU31/ q+5�C R 2�7:4G9 P P�2�4L23A R a�9 MrF3B4d7LD36ETE5�CEP�2�D85�CHA�5HA�A

. 5HFRUG�DVVLJQPHQW/ s_U ? 7:9@F�? 2N4X236HB�4XA�1_6H5�C R 2]581H1�9 PC32EAN7LB�5�k�B�4:jpJ:? BEk/ f�1E1 9 P�CH23AI4S236HB�4LAE1[5�4S2_A�9 1�F ? 58a32EA�5 U37dB�M�5<7X9 6<5 ?@? a�kNTH2�C_2pt�2E6EUH7:9@C�PN5�k�B4Gj`J:? BEku7d581�j

. ,QWHJUDWHG�YDOLGDWLRQV/ =>5�?@9 A�537:9 B�C81[635�C R 2�FH2�4dJSB4LM�2HA�5<7�4GU�C87e9 M�2�7SB�6�TH2E6Ej�A�587S5_bUE5�?O9 7Sa/ vH5�9@? 2HA�;85�?@9 A�537:9 B�C81�F�4S28;32�C<7�T85 CEA�B�;H2�4�BEJ�k�B�4GjwJ:? BHko7S531�jn1

. -RE�VSOLWWLQJ/ xEB R 1N685�C R 2]1�F�?\9 7�9\C87SB�1�U R W m B R 1/ v U�4d7XT�2�4�F 4XB�682<1E1 9@CEP�6<5 C[A�9 JyJd2�4 R 5<1�2HA�BC_A 2<J:9\C�9 7:9 BC31

. 0RQLWRULQJ/ f�1E1 9 P�CH23ANk�B�4ejnJX? B�kuB�k]CH2�4d1zTH5<;E2�JGU�?@?`;�9 1�9 R 9O?O9 7^aNBC_7:T32[B�;H2 4d5�?\?3F 4LB�P4X2<1H1/ {*9 187SB�4Sa�? B PgF�4:BE;�9 A�281NA�2<7S5�9\? 1NBC_5�F F�4XB�;32�4d1[5�CHA�7:9 M�2�?@9OC3231

0'0�:RUNIORZ�5XQWLPH��'DWD�0DQDJHU�

�

© SAP AG MDM100 3-180

SAP AG 2006


&UHDWLRQ�RI�DQ�0'0�:RUNIORZ

�

© SAP AG MDM100 3-181

SAP AG 2006

&UHDWLRQ�RI�D�:RUNIORZ��3UHUHTXLVLWHV

� 0DNH�VXUH�WKH�IROORZLQJ�KDYH�EHHQ�FRPSOHWHG�EHIRUH�FUHDWLQJ�D�ZRUNIORZ�| 9DOLGDWLRQV| $VVLJQPHQWV| 8VHUV��ZLWK�H�PDLOV��DQG�5ROHV

� 9LVLR�PXVW�EH�LQVWDOOHG�IRU�WKH�FUHDWRU�RI�WKH�ZRUNIORZ

�

© SAP AG MDM100 3-182

SAP AG 2006

$GG�1HZ�:RUNIORZ

�� ,Q�5HFRUG�PRGH��FKDQJH�WDEOH�WR�:RUNIORZV�

�� 5LJKW�FOLFN�LQ�ULJKW�SDQH�6HOHFW�$GG�

�� (QWHU�1DPH�6HOHFW�7DEOH�&KRRVH�2ZQHU��$FWLYH��DQG7ULJJHU�DFWLRQV��} 0DQXDO} 5HFRUG�$GG} 5HFRUG�,PSRUW} 5HFRUG�8SGDWH

�� &OLFN�RQ�:RUNIORZ�

�

� Name: The workflow name � Description: The workflow description � Table: The table on which the workflow operates � Workflow: The Microsoft Visio workflow object itself � Owner: The user who owns the workflow and has complete control � Active: Whether the workflow is active (Yes/No) � Trigger Action: The actions that triggers the workflow; Trigger Actions can be multi-valued

y Manual y Record Add y Record Import y Record Update

� Max Records Launch: The maximum number of records that can be added to the workflow before it is launched automatically y Autolaunch=Threshold (autolaunch based on record count) y 0 means launch job automatically as soon as it is created

� Max Time Launch: The maximum amount of time that the workflow can remain unlaunched before it is launched automatically y Autolaunch=Threshold y 0 means do not autolaunch based on unlaunched time

© SAP AG MDM100 3-183

SAP AG 2006

0'0�:RUNIORZ�(GLWRU��'HVLJQ�7LPH7KH�ZRUNIORZ�HGLWRU�FRQVLVWV�RI�WKH�IROORZLQJ�FRPSRQHQWV

hiB4Gj~f�4d2E5

6WHS�3URSHUWLHV�SDQH

9LVLR�GUDZLQJ�SDQH

:RUNIORZ�6WHQFLO�SDQH

�

� The flow diagram is designed using a Microsoft Visio plug-in that is loaded automatically when you edit the Workflow field of a Workflow record.

� :RUNIORZ�6WHQFLO�SDQH: The left pane contains the collection of Visio shapes correspondending to workflow step types and connectors.

� 9LVLR�GUDZLQJ�SDQH: The top-right pane contains the Visio drawing representing the MDM Workflow.

� 6WHS�3URSHUWLHV�SDQH: The bottom-right pane contains the properties of the step selected in the Visio drawing.

� When a step shape is selected in the Visio drawing, the Step Properties pane contains a grid with a list of properties for the step.

© SAP AG MDM100 3-184

SAP AG 2006

&UHDWH�DQ�0'0�:RUNIORZ

} %\ GUDJJLQJ DQG�GURSSLQJ��\RX FDQ DGG VKDSHV WR�WKH 9LVLR�GUDZLQJSDQH�

} (YHQ�WKH�FRQQHFWRUV�FDQ�EH�SODFHG�YLD�GUDJ�DQG�GURS�

�

� Every drawing must have a Start and a Stop shape. � Every shape must be connected to another shape. � Start and Stop each have only one connector. � Specify the properties for each step in the Step Properties pane and then press 6+,)7�(17(5 to

save changes to the step you are editing. � You can press�(6& to discard unsaved changes and restore the steps to the prior state.

© SAP AG MDM100 3-185

SAP AG 2006

3UHGHILQHG�HOHPHQWV�0'0�:RUNIORZ�6WHQFLO

�

� MDM Workflow emphasizes self-regulating logic rather than command-and-control and features a relatively small number of step types for conceptual and design simplicity. At the same time, these simple self-contained steps can be combined to build sophisticated workflows that are flexible, configurable, and self-evident.

© SAP AG MDM100 3-186

SAP AG 2006

7KH�ILUVW�VWHS�RI�WKH�ZRUNIORZ�PXVW�KDYH�H[DFWO\�RQH�6WDUW�VWHS�} 1DPH��7KH�VWHS�QDPH} &KHFN�2XW�5HFRUGV��:KHWKHU�WR�FKHFN�RXW�WKH�UHFRUGV�DW�

EHJLQQLQJ�RI�MRE��<HV�1R�} 'XUDWLRQ�7LPHRXW��7KH�OHQJWK�RI�WLPH�DOORFDWHG�WR�WKH�MRE} &&��1RWLILFDWLRQ��,Q�DGGLWLRQ�WR�WKH�DVVLJQHH��ZKRP�WR�QRWLI\�YLD�

HPDLO�ZKHQ�WKH�ZRUNIORZ�WLPHRXW�KDV�H[SLUHG��>2ZQHU@��OLVW�RI�XVHUV�

} 6HQG�1H[W�6WHS��:KHWKHU�MXVW�WKH�RZQHU�RU�WKH�ILQDO�DVVLJQHH�FDQVHQG�WR�WKH�QH[W�VWHS�ZKHQ�D�VWHS�LV�FRPSOHWH��>2ZQHU@��>$Q\RQH@�

} 6SOLW�-RE��:KHWKHU�MXVW�WKH�RZQHU�RU�WKH�DVVLJQHH�FDQ�VSOLW�WKH�MRE�LQWR�PXOWLSOH�VXE�MREV��>2ZQHU@��>$Q\RQH@�

6WHS�3URSHUWLHV��6WDUW

Required element in workflow

�

© SAP AG MDM100 3-187

SAP AG 2006

} $�SURFHVV�VWHS�LQGLFDWHV�DQ\�XVHU�DFWLRQ��} $�ZRUNIORZ�PD\�KDYH�DQ\�QXPEHU�RI�3URFHVV�VWHSV��HDFK�RI�

ZKLFK�KDV�RQH�LQSXW�DQG�RQH�RXWSXW�

} $VVLJQHH�7\SH��8VHU�RU�5ROH

} ([HFXWLRQ�7\SH�. $OO�FRQFXUUHQW��$OO�XVHUV�DUH�DVVLJQHG�WR�WKLV�

WDVN��EXW�RQO\�RQH�QHHGV�WR�SDVV�LW�RQ�. $OO�6HTXHQWLDO�5DQGRP��$OO�DVVLJQHHV�PXVW�SHUIRUP�WKH

VWHS��(DFK�DVVLJQHH�FDQ�GR�VR�RQH�DW�D�WLPH�LQ�DQ\�RUGHU�. $OO�6HTXHQWLDO�2UGHUHG��$OO�DVVLJQHHV�PXVW�SHUIRUP�WKH�VWHS��(DFK�

DVVLJQHH�FDQ�GR�VR�RQH�DW�D�WLPH�LQ�WKH�RUGHU�OLVWHG�LQ�WKH�VWHS��. $Q\�6LQJOH��$Q\�XVHU�FDQ�DFFHSW�LW�DQG�IRUZDUG�LW�RQ�

6WHS�3URSHUWLHV��3URFHVV

�

� MDM allows you to specify the Execution Type property for each step as it relates to: y Whether any single assignee or all of them must perform the step y If all of them, sequential or parallel execution among the multiple assignees of the step

© SAP AG MDM100 3-188

SAP AG 2006

6WHS�3URSHUWLHV��9DOLGDWH

} $XWRPDWLF�UXQV�D�YDOLGDWLRQ�RU�YDOLGDWLRQ�JURXS�} $�IDLOXUH�NLFNV�WKH�ZRUNIORZ�EDFN�WR�WKH�SUHYLRXV�VWHS�} 9DOLGDWLRQ��6HOHFW�D�VLQJOH�YDOLGDWLRQ�RU�YDOLGDWLRQ�JURXS} 6SOLW�)DLOHG�5HFRUGV��<HV�1R��

:KHWKHU�WR�DXWRPDWLFDOO\�VSOLW�WKH�IDLOHG�UHFRUGV�DQG�DOORZ�WKH�VXFFHVVIXO�UHFRUGV�WR�SURFHHG�� 1R� (YHU\�,WHUDWLRQ� ,WHUDWLRQ�7KUHVKROG

} ,WHUDWLRQ�7KUHVKROG��:LOO�VHQG�DQ�H�PDLO�WR�WKH�&&��1RWLILFDWLRQ�DIWHU�WKH�WRWDO�QXPEHU�RI�DWWHPSWV

�

� A Validate step runs a validation or validation group against the records in the job. � A validation failure of any record in any of the validations kicks the workflow back to the previous

step. � A Validation step has one input and one output;

© SAP AG MDM100 3-189

SAP AG 2006

6WHS�3URSHUWLHV��$VVLJQ

1RWH��,I�DQ\�RI�WKH�UHFRUGV�IDLO��WKH�MRE�LV�NLFNHG�EDFN�WR�WKH�SUHYLRXV�VWHS�

� 8VHG�WR�H[HFXWH�DQ�DOUHDG\�FUHDWHG�DVVLJQPHQW�

� $VVLJQPHQW��6HOHFW�WKH�DVVLJQPHQWH[SUHVVLRQ�\RX�ZDQW�WR�KDYH�SHUIRUPHG

�

� An Assign step runs an assignment against the records in the job. An assignment failure of any record causes the entire step to fail and appear as a task for the Workflow owner.

© SAP AG MDM100 3-190

SAP AG 2006

6WHS�3URSHUWLHV��1RWLI\

� 8VHV�WKH�H�PDLO�DGGUHVV�GHILQHG�IRU�WKH�XVHU�LQ�WKH�7R�OLVW

� 7R��:KR�WKH�QRWLILFDWLRQ�ZLOO�EH�VHQW�WR� 6XEMHFW��+HDGLQJ�RI�WKH�QRWLILFDWLRQ� (�PDLO�%RG\��7KH�WH[W�PHVVDJH�RI�WKH�H�PDLO

�

� MDM workflow can send e-mail notifications when a step has exceeded its allotted time or number of iterations. The notification from the Workflow owner is sent to all assignees who have received but not yet completed the step along with a CC to the specified users.

� 1RWH� You must add a Mail Server entry in the mds.ini for every repository that uses workflow (e.g. “ Mail Server=mail.domain.com” ).

© SAP AG MDM100 3-191

SAP AG 2006

} 0XVW�EH�YLHZHG�E\�D�SHUVRQ�EHIRUH�SURFHHGLQJ��} 8VHG�WR�VHQG�WKH�ZRUNIORZ�EDFN�WR�SUHYLRXV�VWHS�} ,WHUDWLRQ�7KUHVKROG��,I�GLVDSSURYHG��

LW�ZLOO�VHQG�WKH�HQWLUH�JURXS�EDFN�WR�SUHYLRXV�VWHS�

} 'XUDWLRQ�7LPHRXW��$PRXQW�RI�WLPH�EHIRUH�VHQGLQJ�DQ�H�PDLO�WR�&&��1RWLILFDWLRQ�XVHU�V�

} 6SOLW�-RE��:KR�KDV�SHUPLVVLRQ�WR�VSOLW�WKH�MRE

6WHS�3URSHUWLHV��$SSURYH

1RWH��,I�DQ\�RI�WKH�UHFRUGV�DUH�GLVDSSURYHG�E\�DQ\�RI�WKH�DSSURYHUV��WKH�MRE�LV�NLFNHG�EDFN�WR�WKH�SUHYLRXV�VWHS�

�

� An Approve step seeks user approval for the records in the job. A disapproval of any record by any of the approvers kicks the Workflow back to the previous step.

© SAP AG MDM100 3-192

SAP AG 2006

6WHS�3URSHUWLHV��%UDQFK

� 6HSDUDWHV�WKH�ZRUNIORZ�LQWR�DQ\�QXPEHU�RI�EUDQFKHV�

� %DVHG�RQ�D�FRQGLWLRQ��GLUHFWV�WR�ZKLFK�EUDQFK�WKH�UHFRUG�ZLOO�PRYH�

� 9DOLGDWLRQV��6HOHFWLRQ�RI�D�YDOLGDWLRQ�RU�YDOLGDWLRQ�JURXS

�

� A Branch step breaks a single job into multiple concurrent subjobs, each of which follows the applicable thread in parallel and contains the subset of records that passed the validation associated with that branch.

© SAP AG MDM100 3-193

SAP AG 2006

� $�PHUJH�UHFRPELQHV�VRPH�RU�DOO�RI�WKH�PXOWLSOH�SDUDOOHO�WKUHDGV�FUHDWHG�E\�D�EUDQFK�VWHS�LQWR�D�VLQJOH�WKUHDG�

� $W�UXQWLPH��WKH�PHUJH�GRHV�QRW�UHFRPELQH�WKH�PXOWLSOH�VXE�MREV�FUHDWHG�E\�WKH�EUDQFK�LQWR�D�VLQJOH�MRE�

6WHS�3URSHUWLHV��0HUJH

�

� Even if you subsequently use a Merge step to recombine the multiple parallel threads created by the Branch step, the Merge does not recombine the multiple subjobs created by the Branch into a single job.

� Use a Group step if you want the parallel threads to be recombined into a single job.

© SAP AG MDM100 3-194

SAP AG 2006

� 7KH�PDWFK�UXQV�D�PDWFKLQJ�VWUDWHJ\� 'XUDWLRQ�7LPHRXW��$PRXQW�RI�HODSVHG�WLPH�WR�DOORZ�

EHIRUH�VHQGLQJ�D�QRWLILFDWLRQ�� 6WUDWHJ\��7KH�PDWFKLQJ�VWUDWHJ\�WR�UXQ�DJDLQVW�WKH�MRE�� 0DWFK�5HFRUGV�6FRSH��

7KH�VFRSH�RI�PDWFKLQJ�| 5HFRUGV�YV��5HFRUGV| 5HFRUGV�YV��$OO

6WHS�3URSHUWLHV��0DWFK

�

© SAP AG MDM100 3-195

SAP AG 2006

6WHS�3URSHUWLHV��&RQQHFW

� $OORZV�FRQQHFWLRQ�RI�HOHPHQWV�WKDW�DUH�QRW�QH[W�WR�HDFK�RWKHU�RU�IURP�PXOWLSOH�SDJHV�RI�ZRUNIORZ��

� 7DUJHW�6WHS��'LVSOD\V�FRQQHFWLRQV�WR�DYDLODEOH�LQSXWV�

�

� A Connect step is effectively a connector and is convenient when two steps that need to be connected are either not adjacent or on different pages of the Microsoft Visio diagram.

© SAP AG MDM100 3-196

SAP AG 2006

6WHS�3URSHUWLHV��*URXS

� $OORZV�PXOWLSOH�SURFHVVHV�WR�UXQ�DW�WKH�VDPH�WLPH� 7KH�VWHS�W\SHV�WKDW�DUH�YDOLG�ZLWKLQ�D�*URXS�VWHS�

LQFOXGH�| 3URFHVV�| *URXS| &RQQHFW| 1RWLI\

� ([HFXWLRQ�7\SH��7KH�RUGHU�LQ�ZKLFK�WKH�SURFHVVHV�ZLOO�EH�SURFHVVHG�

�

� The Group step groups the individual steps within the Group box and allows either any one of them to be executed or all of them to be executed in sequence or in parallel.

� Any number of steps or threads may appear within a Group step, which has one input and one output.

© SAP AG MDM100 3-197

SAP AG 2006

} 7KH�ILQDO�VWHS�LQ�WKH�ZRUNIORZ�} 0RUH�WKDQ�RQH�VWRS�LV�DOORZHG�} 1DPH��7KH�VWHS�QDPH} /DXQFK��7KH�QH[W�ZRUNIORZ�WR�

ODXQFK} 5HFRUG�&KHFNRXW��$FWLRQ�WR�

WDNH�LI�WKH�MRE�UHFRUGV�DUH�FKHFNHG�RXW�� &KHFN�,Q��&KHFN�LQ�LI�FKHFNHG�

RXW��HOVH�QR�DFWLRQ� 5ROO�%DFN��5ROO�EDFN�LI�FKHFNHG�

RXW��HOVH�QR�DFWLRQ� &DVFDGH��7DNH�FKHFNHG�RXW�

VWDWH�DQG�FDVFDGH�LI�ODXQFKHG�WR�QH[W�ZRUNIORZ

6WHS�3URSHUWLHV��6WRS

�Required element in workflow

�

© SAP AG MDM100 3-198

SAP AG 2006

&UHDWH�DQ�0'0�:RUNIORZ

*HQHUDO�VWHSV�WR�FUHDWH�D�:RUNIORZ�� $GG�D�QHZ�ZRUNIORZ�LQ�WKH�0'0�'DWD�0DQDJHU�� 0RGHO�WKH�ZRUNIORZ�XVLQJ�WKH�ZRUNIORZ�HGLWRU

�

� Each Workflow record is stored in the Workflows table. � You create a Workflow by making the Workflows table the current table and adding a new record. � The new record includes the Workflow object, which is a Microsoft Visio file stored in the

repository.

© SAP AG MDM100 3-199

SAP AG 2006

6DYH�:RUNIORZ

��$FWLYDWLRQ�RI�WKH�ZRUNIORZ�RFFXUV�LQ�WKH�0'0�'DWD�0DQDJHU�

��6DYH�\RXU�:RUNIORZ�

�

© SAP AG MDM100 3-200

SAP AG 2006


5XQQLQJ DQ�0'0�:RUNIORZ

�

© SAP AG MDM100 3-201

SAP AG 2006

5XQ�0'0�:RUNIORZ

�� *R�WR�WKH�0'0�'DWD�0DQDJHU�VHOHFW�WKH�3URGXFW�WDEOH�� 6HOHFW�WKH�:RUNIORZV WDE�� +LJKOLJKW�WKH�UHFRUGV�\RX�ZDQW�WR�EH�SDUW�RI�WKH�ZRUNIORZ�� 5LJKW�FOLFN�DQG�VHOHFW�:RUNIORZV�Æ $GG�WR�MRE�Æ �VHOHFW�WKH�MRE!��

��

��

© SAP AG MDM100 3-202

SAP AG 2006

0DQXDO�/DXQFK�RI�0'0�:RUNIORZ

7KH�:RUNIORZ�LV�QRZ�LQ�WKH�UHSRVLWRU\��UHDG\�IRU�ODXQFK�

�

� Zero hours for automatic launch.

© SAP AG MDM100 3-203

SAP AG 2006

5XQ�0'0�:RUNIORZ

� ,Q�WKH�:RUNIORZ WDE��ULJKW�FOLFN�LQ�WKH�7DVNV�SDQH�WR�ODXQFK�WKH�:RUNIORZ�

� $IWHU�/DXQFK��WKH�:RUNIORZ�LV�GHOLYHUHG�WR�WKH�QH[W�VWHS��

�

© SAP AG MDM100 3-204

SAP AG 2006

6HOHFW�:RUNIORZ�5HFRUGV

} 7KH�:RUNIORZ�SUHVHQWV�WKH�REMHFWV�WKDW�KDYH�EHHQ�DVVLJQHG�WR�WKHZRUNIORZ�

} 7KH�VWHS�RZQHU�UHVSRQVLEOH�KDV�GLIIHUHQW�VWDWXVHV�WR�ZRUN�RQ��5HFHLYHG�LV�WKH�ILUVW�RQH�

�

© SAP AG MDM100 3-205

SAP AG 2006

6HQG�WR�1H[W�$JHQW

} $IWHU�WKH�VWHS�WDVN�KDV�EHHQ�SHUIRUPHG��WKH�XVHU�KDV�WKH�RSWLRQ�WR��6HQG�1H[W�DQG�$SSURYH��GHSHQGLQJ�RQ�WKH�:RUNIORZ�VHWXS!�

} 7KH�:RUNIORZ�ZLOO�GLVDSSHDU�IURP�WKH�7DVNV�SDQH�DQG�LV�VHQW�WR�WKH�QH[W�VWHS�RZQHU�RI�WKH�ZRUNIORZ�

�

� Sometimes, you may not care who sends a job from one process step to the next. In these cases, the last assignee to finish processing the current step is the one who sends it to the next one. Alternately, when each process step is completed, you may wish control of the job to pass back to the Workflow owner, who can decide whether to push it to a particular assignee or allow it to be pulled by any of the assignees of the next step.

� Whether any user or just the owner can send to the next step is based on the Send Next Step property of the Start step.

© SAP AG MDM100 3-206

SAP AG 2006

$VVXPH

� $V�WKH�ZRUNIORZ�RZQHU��\RX�FDQ�DVVXPH�FRQWURO�RI�D�MRE�} 5LJKW�FOLFN�RQ�WKH�MRE} 6HOHFW�$VVXPH

� 8SRQ�DVVXPLQJ�WKH�MRE��WKH�XVHU�DVVLJQHG�WR�WKH�MRE�ZLOO�QRZ�EH�WKH�RZQHU�

�

� 1RWH: When you assume a task that is Received by another user, it is simply removed from that user’s inbound task queue and placed into yours. By contrast, when you assume a task that is Available to another user, it is also removed from the inbound task queue of all of the other users to whom it was previously Available.

© SAP AG MDM100 3-207

SAP AG 2006

$VVLJQ

� $V�WKH�ZRUNIORZ�RZQHU��\RX�FDQ�DVVLJQ�XVHUV�WR�D�MRE�} 5LJKW�FOLFN�RQ�WKH�MRE} 6HOHFW�$VVLJQ} 7KHQ�VHOHFW�D�XVHU

� 0'0�DVVLJQV�WKH�WDVN�DQG�XSGDWHV�WKH�7DVNV�SDQH�RI�WKH�:RUNIORZV�WDE�

�

� 1RWH: You can assign the task to any of the assignee users of the step as long as the Execution Type of the step is not All Concurrent.

© SAP AG MDM100 3-208

SAP AG 2006

0DUN�DV�'RQH

$QRWKHU�RSWLRQ�IRU�ZRUNIORZ�VWHS�XVHU�'RQH�ZKLFK�LV�WKH�ILQDO�DSSURYDO�VWHSV��,Q�WKLV�VWHS��D�QHZ�FROXPQ�ZLOO�DSSHDU�LQ�WKH�5HFRUGV�SDQH�WKDW�GLVSOD\V�WKH�QDPH�RI�WKH�DSSURYHU��GHSHQGLQJ�RQ�WKH�VWHS�VHWWLQJV��

�

© SAP AG MDM100 3-209

SAP AG 2006


6XPPDU\

�

© SAP AG MDM100 3-210

SAP AG 2006

0'0�:RUNIORZ�6XPPDU\

� 0'0�:RUNIORZ�IXQFWLRQDOLWLHV�DUH�D�WLJKWO\�LQWHJUDWHG�FRPSRQHQW�RI�WKH�0'0�'DWD�0DQDJHU�

� 7KH�XQGHUO\LQJ�0'0�ZRUNIORZ�HQJLQH�IHDWXUHV�D�QXPEHU�RI�LQQRYDWLRQV�WKDW�PDNH�GHVLJQLQJ��PRGLI\LQJ��DQG�H[HFXWLQJ�ZRUNIORZV�IDVW�DQG�HDV\�IRU�HYHQ�WKH�PRVW�QRQ�WHFKQLFDO�0'0�XVHU�

� :RUNIORZV�MREV�PRYH�IURP�VWHS�WR�VWHS��VKRZLQJ�XS�DV�WDVNV�LQ�HDFK�DVVLJQHG�XVHU¶V�LQERXQG�WDVN�TXHXH�ZLWKLQ�WKH�'DWD�0DQDJHU��UHDG\�IRU�SURFHVVLQJ�E\�WKDW�XVHU�

�

© SAP AG MDM100 3-211

SAP AG 2006

0'0�:RUNIORZ��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� ([SODLQ�WKH�GLIIHUHQW�HOHPHQWV�RI�D�ZRUNIORZ� &UHDWH�D�VLPSOH�ZRUNIORZ

�

© SAP AG MDM100 3-212

SAP AG 2006

$SSHQGL[�� 5HSRVLWRU\ 2EMHFWV��'DWD *URXSV

7KH�UHSRVLWRU\�PD\�FRQWDLQ�ORWV�RI�LPDJHV��WH[W�EORFNV��DQG�3')�ILOHV��7KHVH�REMHFWV�DOVR�QHHG�WR�EH�RUJDQL]HG�VR�WKDW�LW�LV�SRVVLEOH�WR�ORFDWH�DQ�REMHFW�RU�JURXS�RI�REMHFWV�IRU�OLQNLQJ�WR�D�SDUWLFXODU�UHFRUG�7KH�RUJDQL]DWLRQ�RI�ULFK�SURGXFW�FRQWHQW�LV�GRQH�WKURXJK�'DWD�*URXSV��ZKLFK�LV�D�KLHUDUFK\�IRU�WKHVH�UHSRVLWRU\�REMHFWV�

1RWH��<RX�ZLOO�VHH�'DWD�*URXSV�ILUVW�KDQG�LQ�WKLV�H[HUFLVH��

'DWD�*URXS�,0$*(6

�

Data Groups: � A large product repository may contain huge amount of products, and these products can be

organized within SAP MDM into a hierarchical taxonomy of categories and subcategories. � The data groups hierarchy is a parallel classification scheme used to organize objects into subgroups

called data groups. For example, you might have separate data groups for Product Images, Category Icons, and Manufacturer Logos.

© SAP AG MDM100 3-213

SAP AG 2006

2UJDQL]LQJ 5LFK 3URGXFW &RQWHQW��'DWD *URXSV

1RWH��'DWD JURXSV DUH LQWHUQDO 6$3�0'0�WDEOHV QRW GLVSOD\HG LQ�WKH&RQVROH DQG�DYDLODEOH XSRQ UHSRVLWRU\ FUHDWLRQ�

3XUSRVH RI�'DWD *URXSV��LV WR�SURYLGH D�FRPPRQ KLHUDUFK\ IRUDOO�REMHFW GDWD XVHG WR�RUGHU�DQG�VSHHG XS�WKH VHDUFK��,W LV DOVR�XVHG WR�UHGXFH WKH QXPEHU RI�REMHFWV GLVSOD\HG LQ�WKH XVHULQWHUIDFH�([DPSOHV�� 3LFWXUHV�FDQ EH JURXSHG E\ W\SH

�SKRWR��'�&$'�GHVFULSWLRQ��«�� 7H[W�EORFNV FDQ EH JURXSHG

IROORZLQJ WKHLU XVDJH FRQWH[W

�

� In SAP MDM, each object is assigned to a data group when it is first created or imported into the system. A data group is simply a group of objects, and the set of data groups is organized into a hierarchy similar to the taxonomy hierarchy.

� This table stores the hierarchy of data groups that is used to break the entire set of objects in the repository into manageable subgroups. This table is created automatically and does not appear anywhere in the MDM Console, nor can it be edited directly in the MDM Data Manager.

� It can be modified using MDM Data Manager commands and dialogs.

© SAP AG MDM100 3-214

SAP AG 2006

'DWD�*URXSV�([DPSOH�LQ�'DWD�0DQDJHU

6HOHFWLRQ�RI�REMHFW�LQ'DWD�*URXSV�KLHUDUFK\

5HVXOW

�

� Select from the hierarchy of available Data Groups � Click the $'' button � Those objects belonging to that hierarchy appear in the window Available images � Then those objects are available for selection in main table records

© SAP AG MDM100 3-215

SAP AG 2006

(GLWLQJ�'DWD�*URXSV�ZLWKLQ�'DWD�0DQDJHU

�

� Use menu path in the Data Manager y Objects > Edit Data Groups

© SAP AG MDM100 3-216

SAP AG 2006

0'0�:RUNIORZ��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� ([SODLQ�WKH�GLIIHUHQW�HOHPHQWV�RI�D�ZRUNIORZ� 5XQ�D�VLPSOH�ZRUNIORZ

�

© SAP AG MDM100 3-217

�([HUFLVHV�

8QLW�� 0'0�6FHQDULR��:RUNIORZ�([HUFLVH�7RSLF�� 0'0�:RUNIORZ�


• Explain the different elements of a workflow

• Execute a simple workflow

3XUSRVH�This script walks through the MDM Workflow. It introduces the functionality of the Workflow within MDM 5.5 and gives you some practice in execution a workflow.

3UHUHTXLVLWHV��• MDM Repository has been supplied to you and is ready for importing

• MDM Server has been mounted and started

• Import Manager ready to use for importing new excel sheet to start the workflow

1 'HVLJQ�RI�:RUNIORZ��,QIRUPDWLRQ�2QO\�127(��'R�QRW�H[HFXWH��7KH�KDQGV�RQ�H[HUFLVH�EHJLQV�ZLWK�VWHS��The Workflow has been designed as the following. For the Workflow design, the program Visio professional is needed. The MDM training landscape does QRW have this program installed. Therefore, Step 1, which follows, is designed so that you can see how the workflow has been constructed. It is not intended for you to duplicate this in the “ yourletter_Exercise_Workflow” Repository. You can see the screenshot of the design as an explanation of the workflow.

© SAP AG MDM100 3-218

The workflow starts and is owned by user &KDUOHV. The first step is received by user 0LNH. This user should assign images��

Afterwards the workflow runs into a validation step.

Then the workflow is received by user +HOHQ.

She is supposed to fill in categories

© SAP AG MDM100 3-219

Her entries are being validates by the next validation step.

Afterwards user 0DMRULH receives the workflow and is supposed to add all new objects to the appropriate distribution mask.

Afterwards the owner &KDUOHV needs to approve the workflow finally.

As soon as this is done an email will be sent to Ulla Schmidt-Koecher automatically. Now that the steps of the workflow are clear we can execute the steps of the workflow.

2 /RDG�DQG�/RJRQ�WR�5HSRVLWRU\

First, you must load and connect to \RXUOHWWHUB([HUFLVHB:RUNIORZ repository

2-1 Start the SAP MDM Console.

2-2 Access yourletter_Exercise_Workflow Repository. Right click on it and from the context menu select the option Connect to Repository with User=admin and password=blank.

2-3 Load yourletter_Exercise_Workflow Repository.

2-4 Once it is loaded (it will take a minute) then start the Data Manager Application.

2-5 Press and choose LOCALHOST (Server), select Repository: Yourletter_Exercise_Workflow → OK

© SAP AG MDM100 3-220

2-6 Type &KDUOHV as Username and OK

3 6HW�WKH�9DOLGDWLRQV In this Step the validation processes for the workflow are started. In the workflow there are two Validation steps required which need completion: ,PDJH�9DOLGDWLRQ and &DWHJRU\�)LOOHG"�>:RUNIORZB&DWHJRU\@�validation.

3-1 Click on the tab 9DOLGDWLRQ� 3-2 First complete the ,PDJH�9DOLGDWLRQ.

Enter the Error message:�2QH�RU�PXOWLSOH�UHFRUGV�GR�QRW�KDYH�DQ�LPDJH��SOHDVH�FKHFN�DQG�IROORZ�XS��In the line Automatic “ Execution” “ Warning” should be selected.

In the line “ Callable” there should be “ Yes” selected.

3-3 In the 3URSHUWLHV pane click on to in the line 9DOLGDWLRQ�to set the Validation Expression.

© SAP AG MDM100 3-221

3-4 Click on the button )XQFWLRQV and select “ IS_NOT_NULL” .

Then click on the button )LHOGV and select Images. Click 2.�

3-5 Next complete the Category filled? Validation

Please go again to the Validation tab strip.

Now select the validation &DWHJRU\�ILOOHG" and check the details of the Validation expression. It should say BRANCH(Category). This is the master validation for a validation tree that can include category validations and attributes.

3-6 Please find the already created branch Category filled? [Workflow_Category] in order to complete its expression.

Click on the Validation expression and add the following information using the drop down menu on the right hand side of the validation expression screen.

Confirm with OK.

© SAP AG MDM100 3-222

3-7 Now enter the message text in the start screen of the &DWHJRU\�ILOOHG" validation settings.

Enter: 2QH�RU�PXOWLSOH�UHFRUGV�GR�QRW�EHORQJ�WR�WKH�FRUUHFW�FDWHJRU\�DQG�RU�GR�QRW�IXOILOO�WKH�FDWHJRU\�VSHFLILF�UHTXLUHPHQWV��

4 6WDUW�DQG�&KHFN�WKH�:RUNIORZ�4-1 Choose table :RUNIORZV in Data Manager Application��

Check if Workflow is set to Active = “ Yes” and Trigger Actions = “ Manual” .

© SAP AG MDM100 3-223

4-2 Go back to the Record Mode and sort the records ascending for column Part Number. Select 5 records that start with �XVN. (see screenshot) Right mouse click on them and select :RUNIORZV�!�$GG�WR�-RE!�1HZ�2EMHFWV�WR�UHSRVLWRU\

© SAP AG MDM100 3-224

4-3 Go to the Workflow tab strip select the workflow > right mouse click ODXQFK the workflow. The workflow will start now and Mike will receive it.

1RWH��6RPHWLPHV�DIWHU�DGGLQJ�UHFRUGV�WR�WKH�ZRUNIORZ�MRE��WKH�MRE�WKHQ�LV�ODXQFKHG�ZLWKRXW�IXUWKHU�DFWLRQ� The workflow task should now appear in the corresponding part of the screen.

You can see that the status is set to Received by user Mike.

4-4 Exit the Data Manager and log on as user 0LNH.

User 0LNH is supposed to DVVLJQ�LPDJHV for 5 records. Please go the record

mode.

© SAP AG MDM100 3-225

4-5 Highlight the workflow in the :RUNIORZ�tab.

Go to tab strip Record Detail and select only 4 records.

Then go to field ,PDJHV and double-click it:

Choose an arbitrary image.

If you do not see any images, you can get images in the $YDLODEOH�LPDJHV window by selecting the 'DWD�*URXS tab as seen below, select 0DQXIDFWXUHU�/RJRV and then click the $GG button.

© SAP AG MDM100 3-226

Press OK and return. You will get the following message

Confirm OK.

Go to your workflow, right mouse click > Send Next Step. You will get the following message.

Check your records and correct the one which is indicated wrong.

��

Mark the Workflow and with a right mouse click. You can pass it on to the next recipient:

The validation is executed in the background.

Send the workflow again to the next step owner > Helen.

© SAP AG MDM100 3-227

Exit the Data Manager and log on with user�+HOHQ.

Helen is supposed to fill in categories and attributes.

Go to the tab strip Workflow and click on the workflow.

Go to tab strip Record Details and choose all 5 records.

Delete the existing category, if one exists, and assign the new one – “:RUNIORZB&DWHJRU\” . Select also a new type such as “ ,QGXVWULDO�3DLQW” and new colors, such as “EODFN“ and “ UHG” .

Save by pressing Shift+Enter.

Afterwards go back to tab strip Workflow and send the workflow to the next user.

© SAP AG MDM100 3-228

The Group is owned by user 0DMRULH so please exit the Data Manager with user +HOHQ and log on with user 0DMRULH.

0DMRULH has received two workflows, because there are two tasks within her assigned group.

Choose the first one and go to Record details:

© SAP AG MDM100 3-229

Select Table “0DVNV”

Right click in the Records pane and choose $GG

$GG a new 0DVN called “'LVWULEXWLRQ” .

And VDYH using Shift+Enter.

© SAP AG MDM100 3-230

Return to the products table and select all 5 products. With a right mouse click select Add to Mask

'LVWULEXWLRQ��

��Return to the Workflow tab and mark the Workflow as GRQH.

��

© SAP AG MDM100 3-231

Select the last workflow and set the item status (field) of all 5 records in the record detail view to item status ³$FWLYH” .

Return to Workflow view and forward the workflow to the approver:

Exit the Data Manager and log on as User &KDUOHV.

© SAP AG MDM100 3-232

Highlight all the records with Ctrl-A and right click to reveal the context menu. From the context menu choose the option, Mark as Approved.

1RWH��Since the previous step was a group step with two processes in it, you may see two processes here for Charles to approve. If this is the case, select the VHFRQG�WDVN to mark the records as approved. The first step of two will QRW show the approval option.�

Approve all records singly or all in one. 1RWH� Approval of records is done from the context menu of the records in the Records pane, not from the context menu of the workflow task.

© SAP AG MDM100 3-233

Return to your workflow tab and mark the workflow as done.

Status will change to complete. An email will be send to the sales representative.

If required the workflow can be deleted from the view. Choose GHOHWH from the context menu of the entry in the view to finally delete the workflow.

The workflow will be deleted from the users workflow view.

© SAP AG MDM100 3-235

SAP AG 2006

5HODWLRQVKLSV




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�

© SAP AG MDM100 3-236

SAP AG 2006

&RQWHQWV�� 3DUHQW�FKLOG�UHODWLRQVKLSV� 6LEOLQJ�UHODWLRQVKLSV

0'0�5HODWLRQVKLSV

�

© SAP AG MDM100 3-237

SAP AG 2006

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 9LHZ�UHODWLRQVKLSV�EHWZHHQ�REMHFWV� &UHDWH�UHODWLRQVKLSV�EHWZHHQ�REMHFWV� 8VH�DQG�PDLQWDLQ�UHODWLRQVKLSV

0'0�5HODWLRQVKLSV��8QLW�2EMHFWLYHV

�

© SAP AG MDM100 3-238

SAP AG 2006

0'0�5HODWLRQVKLSV��%XVLQHVV�6FHQDULR

� 6$3�0'0�DOORZV�\RX�WR�FUHDWH�UHODWLRQVKLSV�EHWZHHQ�SURGXFWV��<RX�ZRXOG�OLNH�WR�XQGHUVWDQG�KRZ�WKHVH�FDQ�EH�XVHG�LQ�\RXU�FRPSDQ\��

�

© SAP AG MDM100 3-239

SAP AG 2006

7\SHV�RI�5HODWLRQVKLSV3URGXFW�/HYHO�5HODWLRQVKLSV6XPPDU\

7\SHV�RI�5HODWLRQVKLSV

�

© SAP AG MDM100 3-240

SAP AG 2006

7\SHV�RI�5HODWLRQVKLSV

� 3URGXFW�OHYHO�UHODWLRQVKLS<RX�FDQ�GHILQH�D�UHODWLRQVKLS�EHWZHHQ�WZR�RU�PRUH�LQGLYLGXDO�REMHFWV��)RU�H[DPSOH��\RX�FDQ�GHILQH�D�SDUWLFXODU�ZDVKHU�GU\HU�FRPELQDWLRQ�DV�EHLQJ�UHODWHG�EHFDXVH�WKH\�DUH�GHVLJQHG�WR�VWDFN�RQH�RQ�WRS�RI�DQRWKHU��7KLV�DSSURDFK�LV�YHU\�SUHFLVH��EXW�DOVR�KDV�DGGLWLRQDO�RYHUKHDG�EHFDXVH�HDFK�UHODWLRQVKLS�PXVW�EH�LQGLYLGXDOO\�GHILQHG�DQG�QHZ�SURGXFWV�WKDW�DUH�DGGHG�WR�WKH�UHSRVLWRU\�QHHG�WR�EH�DGGHG�PDQXDOO\�DV�PHPEHUV�RI�WKH�UHODWLRQVKLS�

� &DWHJRU\�OHYHO�UHODWLRQVKLS <RX�FDQ�DOVR�GHILQH�D�UHODWLRQVKLS�EHWZHHQ�WZR�REMHFW�FDWHJRULHV��)RU�H[DPSOH��\RX�FDQ�GHILQH�WKH�FDWHJRULHV�:DVKHUV�DQG�'U\HUV�DV�EHLQJ�UHODWHG��7KLV�DSSURDFK�LV�PRUH�HIILFLHQW�QRW�RQO\�WR�GHILQH��EXW DOVR�WR�PDLQWDLQ�EHFDXVH�QHZ�SURGXFWV�WKDW�DUH�DGGHG�WR�HLWKHU�FDWHJRU\�DXWRPDWLFDOO\�SDUWLFLSDWH�LQ�WKH�UHODWLRQVKLS��+RZHYHU��WKLV�DSSURDFK�GRHV�QRW�SURYLGH�YHU\�JUDQXODU�FRQWURO�RYHU�WKH�PHPEHUV�RI�WKH�UHODWLRQVKLS�

�+� �[�� H��3�3�3��g�@��_�+��@� � � �O�H��+�� d�3��

�

� 3URGXFW�OHYHO�UHODWLRQVKLS: Each type of product-level relationship corresponds to a real-world relationship between main table records and/or non-main table records. y Product-level relationships can be used to store not only relationships between products but also

between products and other records of additional information, establishing the traditional one-to-many relationship between main table records and sub-table records

� &DWHJRU\�OHYHO�UHODWLRQVKLS: The matching-sets facility of MDM allows you to define category-level relationships. A matching set�is a pair of related categories where some or all of the products in each category are related to one another. You can define a matching set as either ELGLUHFWLRQDO�(for a sibling-type relationship) or XQLGLUHFWLRQDO�(for a parent/child-type relationship). y Category-level relationships are defined within the MDM Data Manager in Taxonomy mode using

matching sets and is used during publication.

© SAP AG MDM100 3-241

SAP AG 2006

7\SHV�RI�3URGXFW�/HYHO�5HODWLRQVKLSV

� $ VLEOLQJ�UHODWLRQVKLS UHODWHV�D�JURXS�RI�PDLQ�WDEOH�SURGXFW�UHFRUGV�WKDW�DUH�HTXLYDOHQW�DQG�RU�LQWHUFKDQJHDEOH�IURP�VRPH�PHUFKDQGLVLQJ�RU�VWUXFWXUDO�VWDQGSRLQW�

� $�SDUHQW�FKLOG�UHODWLRQVKLSUHODWHV�D�JURXS�RI�UHFRUGV�WKDW�DUH�QRW�HTXLYDOHQW�ZKHUH�RQH�RI�WKHP�LV�WKH�SDUHQW�DQG�WKH�UHVW�RI�WKHP�DUH�WKH�FKLOGUHQ��

�w��`�p�H�E�^� ��\�p� ¢¡w£¤ ¡*¥�¦[§E�p�\¨�©�� pª«�¡�«¬w£�'®+¦_®��`¯'°H� ±«�¡�¬²@��\�p³�´��Hµ«�¡p ®+� ¶p�\°n�n°n·O�E®�°E¸��w�¬�¡ ¤�`°<¹E� �º��¶n»#¼��±p½`°<�p�\¨¬�¡�«®�°H�p� �y°3�¬�¡�¬´ °3¯~¾8¸¿�y�p�pÀ3±��y�`¯ ¢¡p ÁH�n¯+�À�¼�µ

�3�\°8¨3¸w¶��\�8Â

ÃnÄGÄeÅÇÆÈ�É ÊËÇÌÇÍÎpÏ Æ�Ð Ï Ì Å ÌeÑ ÄÒ ËÇÓ Å ÌeÑ ÔÎ8Õ¿Ö É Í

´��\°p��À3�<³ ³ �8×À�� ½p³ � ��¹

�

� SAP NetWeaver MDM supports two basic types of product-level relationships. � A SDUHQW�FKLOG�UHODWLRQVKLS relates a group of records that are not equivalent, where one of them is

the parent and the rest of them are the children. A parent/child relationship within a single table (for example, main/main or sub-table/sub-table) can be multilevel in that you can recursively traverse from a parent to its children, from a child to its children, and so on. y Parent/child relationships are asymmetric. In other words, if A, B, and C are in a group of related

parent/child records and A is the parent of B and C, then B is the child of A and the sibling of C, and C is the child of A and the sibling of B.

� A VLEOLQJ relationship relates a group of main table product records that are equivalent and/or interchangeable from some merchandising or structural standpoint. y Sibling relationships are symmetric. In other words, if A, B, and C are in a single group of sibling

records, then A is related to its siblings B and C, B is related to its siblings A and C, and C is related to its siblings A and B.

y Examples of sibling relationships include “ cross-sells” and “ interchange products.” Examples of parent/child relationships include “ assemblies and components” and “ kits and parts.”

y The sibling relationship itself is like a parent/child relationship without the parent, while the siblings in the sibling relationship are like the sibling children in the parent/child relationship.

y A record can only belong to at most one group of related sibling records, but it can belong to multiple parent/child groups.

© SAP AG MDM100 3-242

SAP AG 2006

([DPSOHV�RI�3URGXFW�/HYHO�5HODWLRQVKLSV

� Interchange productsSubtable1/Subtable2

� Parts and subparts� Bill of material

Subtables/Subtables

� Bundles� Interchange groups

Sub-tables/Main

� Kits and parts� Cross reference part numbers

Main/Sub-tables

� Assembly� Upsell� Accessories� Consumables� Replacements� Interchange products (one preferred)

Main/Main

3DUHQW�&KLOG

� Cross-sell (related products)� Interchange products (all equal)

Main6LEOLQJ([DPSOHV7DEOH�V�7\SH

�

� The tables of a parent/child relationship can be of type Main, Flat, Hierarchy, or Qualified (but not of table type Taxonomy).

� If a relationship embodies both sibling and parent/child data, and/or the parent/child data relates records both within the main table and between the main table and one or more sub-tables, you can create multiple independent product relationships to store the data and then combine them at the presentation layer into a K\EULG relationship.

� An LQWHUFKDQJH is an alternate product that can be substituted for a given product, where both are main table product records in the repository. If the interchange products records are completely equivalent, use a sibling product relationship to represent this information; if one of the group of interchange products is the preferred product, use a parent/child relationship.

� By contrast, a FURVV�UHIHUHQFH is an alternate part number for a given product that can be used to find the main table product record but that is not itself a product record; use a parent/child relationship (main/subable) to represent this information. y When the cross-reference part numbers come from a known set of alternate sources, you can

instead use a qualified table to represent this information, which improves the ability to search by the cross-reference part number information.

© SAP AG MDM100 3-243

SAP AG 2006

3URGXFW�/HYHO 5HODWLRQVKLSV

7\SHV RI�5HODWLRQVKLSV3URGXFW�/HYHO�5HODWLRQVKLSV6XPPDU\

�

© SAP AG MDM100 3-244

SAP AG 2006

� 7KH�UHODWLRQVKLS�WDEOH�LV�GHILQHG�LQ�WKH�0'0�&RQVROH�� (DFK�REMHFW�LQ�WKH�WDEOH�GHILQHV�D�SURGXFW�OHYHO�UHODWLRQVKLS�� <RX�FDQ�DGG��PRGLI\��DQG�GHOHWH�SURGXFW�UHODWLRQVKLSV�MXVW�OLNH�ILHOGV�RI�D�QRUPDO�WDEOH�� 7KH�WDEOH�SURSHUWLHV�DUH�

Ø Ù�ÚHÛ � Ü ÝÞ� � � ß��H�� ÚEÛ �N�Eà�áÇ�8��d�� Ú á:� ��H��OâØ ã�ä â3��Ü ã ä â3�N�Hà��S� � Ú áX� ��<��@â��3��O�E��<àe�O�3�H�

åyæ+�@��O�O�H�� Ú �S��3áyçº�#� �@� �èØ Ù�ÚHÛ �� Ü éê� Ú á áG�3� Ù�ÚEÛ � Ú â â �@� �<�[ád�

åL� Ú �S��3áyçy�'��º� ��èØ Ù�ÚHÛ �_ë�Ü ã �3�� ÚHÛ �[�Eà áG�3��S�8ìH��d�3��d� � Ú á:� ��8�� OâØ í�Ú �� á:� ��Ü ã �E��S�3�H��L��î ��âH�� á:�@��\�]áX�H�

�H�3ß��H��H�H�Ø í�Ú ��ï��Eß��@�X�3��Ü éð�3�3á:�3��E��á�áG�H�N�S��3��S�g� �

�L�3ß� �@�S�E��åOñ+�<�8ç Ù � èØ í�Ú �[ò]� Ú �3áX� á ä Ü ã �8��d��3��L�I� Ú � Ú ß�� Ú �3áX� á ä

Ú �8�E� �� Ú áS�3�[ó[� á:�� áåd��8à Ú �� á�� ônèØ � Ú �S��8á ã�Ú �� Ü � Ú �S��3á�á Ú � � �N�Hà�áe�3��L� � Ú á:� ��H��\âØ �~��@� � ã�Ú �� Ü �#��@� �[á Ú �� [�Eà�á:�3��L�� Ú á:�@��3��ºâ

5HODWLRQVKLS�7DEOH�&UHDWLRQ

�

� A single table named Relationships is used to define each of the different record-level relationships. Each relationship can be either bidirectional (sibling) or unidirectional (parent/child). This table is managed in the MDM Console and is not visible in the MDM Data Manager, although the relationships between records can themselves be created and edited in Record mode.

� Relationship records consist of a predefined set of fields and are user-created in the MDM Console. Each record defines a particular product-level relationship, chosen from among several different basic structural relationship types. Each type of relationship (for example, parent/child) corresponds to a real-world product relationship (for example, assemblies and components). For each relationship defined in the MDM Console, you specify the related products and/or non-products for each main table product in Record mode within the MDM Data Manager.

� 1RWH: A relationship defines the type of relationship, but does not specify any of the records that participate in that relationship. For each relationship defined in the MDM Console, you specify the related products and/or non-products for each record in Record mode within the MDM Data Manager.

© SAP AG MDM100 3-245

SAP AG 2006

� $OO�UHODWLRQVKLSV�DUH�YLHZDEOH�LQ�'DWD�0DQDJHU��5HFRUG�PRGH�� (DFK�UHFRUG�ZLOO�VKRZ�D�UHODWLRQVKLS�WDEOH�LQ�WKH�IDU�ULJKW�FROXPQ�RI�WKH�5HFRUG�'HWDLOV�

� 7KH�UHODWLRQVKLS�WDEOH�OLVWV�DOO�UHODWLRQVKLSV�GHILQHG�LQ�WKH�FRQVROH�ZLWK�D�>QXPEHU�JUHDWHU�WKDQ�RQH@�DIWHU�HDFK�UHODWLRQVKLS��VKRZLQJ�WKH�WRWDO�FRXQW�RI�UHODWHG�UHFRUGV��,Q�WKH�DERYH�H[DPSOH��WKH�UHFRUG�LV�DQ�DFFHVVRU\�WR��RWKHU�LWHPV�DQG�D�VLEOLQJ�WR�RQH�LWHP�� )RU�HDFK�3DUHQW�&KLOG�UHODWLRQVKLS��WZR�UHODWLRQVKLSV�ZLOO�EH�GLVSOD\HG��VLQFH�WKH�UHFRUG�FDQ�HLWKHU�EH�WKH�SDUHQW�RU�WKH�FKLOG

9LHZLQJ�5HODWLRQVKLSV�)LHOGV

�

� For each product-level relationship, the 5HODWLRQVKLSV field in the 5HFRUG�'HWDLO tab displays a count for the number of related records.

� To view the actual related records, open the 5HODWLRQVKLSV dialog box and move from tab to tab.

© SAP AG MDM100 3-246

SAP AG 2006

� %\�GRXEOH�FOLFNLQJ�RQ�D�UHODWLRQVKLS�WDEOH��D�5HODWLRQVKLSV GLDORJ�ER[�ZLOO�RSHQ��

� &OLFN�WKURXJK�WKH�WDEV�WR�YLHZ�WKH�RWKHUUHODWLRQVKLSV�

� 7KH�DQFKRU�VKRZVWKH�UHFRUG�EHLQJ�UHIHUHQFHG�

� %\�GRXEOH�FOLFNLQJ�RQ�DQ\�UHFRUG��\RX�FDQ�VHH�WKH�QHZ�UHFRUG¶V��UHODWLRQVKLSV�

9LHZLQJ�5HODWLRQVKLSV�5HFRUGV

�

� The MDM Data Manager includes a dialog box for reviewing, adding (linking), and removing (unlinking) related records for each product-level relationship. You access the window from the Relationships field, which appears on the right side of the Record Detail tab.

� Having a record remain anchored in the Relationships dialog box allows you to navigate the records in the repository so that you can relate additional records to the anchor record for each product-level relationship. You do this by: 1. Changing the selected records in the Records grid (if necessary, by changing the search selections

and the corresponding search results and even the current table itself) 2. Adding the new related records

� You can change the anchor record to an entirely unrelated record by double-clicking on a record in the Records grid outside the Relationships dialog box to make it the new anchor record.

� Note: You can open the Relationships dialog box only if a single record is selected in the Records grid.

� Note: When zero records are selected or more than one record is selected in the Records grid, the Relationships field is disabled and highlighted in read-only gray.

© SAP AG MDM100 3-247

SAP AG 2006

� $OO�UHODWLRQVKLSV�DUH�FUHDWHG�LQ�'DWD�0DQDJHU�5HFRUG�PRGH�

� 'RXEOH�FOLFN�WKH�VLEOLQJ�UHODWLRQVKLS�QDPH�LQ�WKH�5HODWLRQVKLS ILHOG�WR�RSHQ�WKH�5HODWLRQVKLS�IRU�3DUW�1XPEHU GLDORJ�ER[�

&UHDWLQJ�6LEOLQJ�5HODWLRQVKLSV

1RWH��7KH�VLEOLQJ�UHODWLRQVKLS�ZLOO�QRW�KDYH�D�EUDFNHWHG�QDPH�DIWHU�LW�

1RWH��7KLV�ER[�FDQ�EH�PRYHG�DQG�UHVL]HG�

�

� A sibling relationship always relates main table product records. A sibling relationship relates a group of main table records that are equivalent and/or interchangeable from some merchandising or structural standpoint.

� &DXWLRQ: Any changes you make to the set of related records are immediately saved to the repository.

© SAP AG MDM100 3-248

SAP AG 2006

� :LWK�WKH�5HODWLRQVKLS�ER[�RSHQ��UHWXUQ�WR�WKH�OLVW�RI�UHFRUGV�

� <RX�PD\�QRZ�VHDUFK��VFUROO��DQG�DSSO\�PDVNV�WR�ILQG�WKH�VLEOLQJ�UHFRUG�

&UHDWLQJ�6LEOLQJ�5HODWLRQVKLSV��

1RWH��7KH�5HODWLRQVKLSER[ZLOO�UHPDLQ�RSHQ�EXW�ZLOO�EH�JUD\HG�RXW�

�

© SAP AG MDM100 3-249

SAP AG 2006

� 2QFH�\RX�KDYH�IRXQG�WKH�UHFRUG��RU�UHFRUGV��\RX�ZRXOG�OLNH�WR�DGG�WR�WKH�VLEOLQJ�UHODWLRQVKLS��FKHFN�ILUVW�WKDW�WKH\�GR�QRW�EHORZ�WR�DQRWKHU�VLEOLQJ�UHODWLRQVKLS��

� ,I�\RX�ZLVK�WR�DGG�WKLV�UHFRUG��DQG�DOO�RWKHU�UHODWHG�VLEOLQJV��WR�WKH�DQFKRUHG�UHFRUG��FOLFN�DQG�GUDJ�WKH�UHFRUG�WR�WKH�RSHQ�ZLQGRZ�LQWKH�5HODWLRQVKLS�ER[�

&UHDWLQJ�6LEOLQJ�5HODWLRQVKLSV��

�

© SAP AG MDM100 3-250

SAP AG 2006

� ,I�\RX�KDYH�DGGHG�D�QHZ�UHFRUG�DV�D�VLEOLQJ�WR�DQRWKHU�UHFRUG�DQG�LW�EURXJKW�LQ�LWV�RWKHU�VLEOLQJV��\RX�FDQ�VSOLW�WKH�UHODWLRQVKLS�E\ ULJKW�FOLFNLQJ�RQ�WKH�UHFRUGV�\RX�ZRXOG�OLNH�WR�UHPDLQ�LQ�RQH�JURXS�

� 7KH�VSOLW�ZLOO�UHPRYH�WKH�XQVHOHFWHG�UHFRUGV�� ,I�WKHUH�ZDV�PRUH�WKDQ�RQH�XQVHOHFWHG�UHFRUG��LW�ZLOO�FRPELQH�WKHP�DQG�PDNH�WKHP�VLEOLQJV��

6SOLWWLQJ�6LEOLQJ�5HODWLRQVKLSV

�

© SAP AG MDM100 3-251

SAP AG 2006

&UHDWLQJ�3DUHQW�&KLOG�5HODWLRQVKLSV

� 3DUHQWV�FDQ�KDYH�DQ\�QXPEHU�RI�FKLOGUHQ��ZKR�DUH�QRW�QHFHVVDULO\�VLEOLQJV�� &KLOGUHQ�FDQ�DOVR�KDYH�DQ\�QXPEHU�RI�SDUHQWV�� $�SDUHQW�FDQ�DOVR�EH�D�FKLOG�� $�FKLOG�FDQ�EH�D�SDUHQW�� $�UHFRUG�FDQQRW�EH�D�SDUHQW�FKLOG�RI�LWVHOI�

�

� A parent/child relationship relates a group of records that are not equivalent where one of them is the parent and the rest of them are the children.

� A parent/child relationship can relate records within a single table or between any two tables. Specifically, it can relate: y Records within the products of the main table (for example, “ products and accessories” ) y Between product records of the main table and non-product records of a sub-table in either

direction (for example, “ kits and parts” [main/sub-table] or “ bundles and products” [sub-table/main])

y Records within the non-products of a single sub-table (for example, “ parts and subparts” ) y Between non-product records of one sub-table and non-product records of a different sub-table

(for example, “ interchange part number groups” )

© SAP AG MDM100 3-252

SAP AG 2006

6XPPDU\

7\SHV RI�5HODWLRQVKLSV3URGXFW�/HYHO�5HODWLRQVKLSV6XPPDU\

�

© SAP AG MDM100 3-253

SAP AG 2006

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 9LHZ�UHODWLRQVKLSV�EHWZHHQ�REMHFWV� &UHDWH�UHODWLRQVKLSV�EHWZHHQ�REMHFWV� 8VH�DQG�PDLQWDLQ�UHODWLRQVKLSV

0'0�5HODWLRQVKLSV��8QLW�6XPPDU\

�


SAP AG 2006

8QLW��2XWSXWV��6\QGLFDWRU




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�


SAP AG 2006

&RQWHQWV�� 0'0�6\QGLFDWRU

0'0�6\QGLFDWRU

�


SAP AG 2006

0'0�6\QGLFDWRU��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� ([SODLQ�WKH�9DOXH�RI�WKH�0'0�6\QGLFDWRU� 'HVFULEH�0'0�6\QGLFDWRU RSWLRQV� ([SODLQ�KRZ�WR�VHW�XS�D�V\QGLFDWLRQ��ZKLFK�

PRGXOHV�DUH�LQYROYHG��DQG�WKH�SUHUHTXLVLWHV

�


SAP AG 2006

0'0�6\QGLFDWRU��%XVLQHVV�6FHQDULR

� 6LQFH�\RX�ZLOO�EH�KDUPRQL]LQJ�PDVWHU�GDWD�DIWHU�FRQVROLGDWLRQ��\RX�ZDQW�WR�NQRZ�ZKDW�RSWLRQV�DUH�DYDLODEOH�LQ�WKH�0'0�6\QGLFDWRU IRU�WKH�V\QGLFDWLRQ�RI�GDWD�IURP�6$3�0'0�WR�\RXU�YDULRXV�FOLHQW�V\VWHPV�

�


SAP AG 2006

)XQFWLRQDO 'HVFULSWLRQ RI�0'0�6\QGLFDWRU(LJKW�6WHSV�RI�WKH�6\QGLFDWLRQ�3URFHVV$GYDQFHG�6\QGLFDWLRQ6XPPDU\

)XQFWLRQDO 'HVFULSWLRQ RI�0'0�6\QGLFDWRU

�


SAP AG 2006

0'0�6\QGLFDWRU

� ([WUDFWLRQ�IURP�WKH�UHSRVLWRU\�EDVHG�RQ�D�JLYHQ�VWUXFWXUH�

� ([WUDFWLRQ�RI�GHGLFDWHG�REMHFWV�SHU�VHOHFWLRQ

� 6LQJOH�WDUJHW�GLVWULEXWLRQ� 5HJDUGLQJ�WKH�UHOHYDQW�NH\�PDSSLQJ�RQ�

YDULRXV�OHYHOV�� 5HFRUG�NH\�PDSSLQJ� /RRNXS�NH\�PDSSLQJ

� ;0/�ILOH�FUHDWLRQ�IRU�6$3�1HW:HDYHU�;,� &UHDWLQJ�RQH�;0/�ILOH�IRU�DOO�UHFRUGV�� &UHDWLQJ�RQH�;0/�ILOH�IRU�HDFK�UHFRUG

� &DSDELOLW\�WR�H[SRUW�RQO\�QHZ�RU�PRGLILHG�UHFRUGV�VLQFH�ODVW�V\QGLFDWLRQ


0'06HUYHU0'06HUYHU5HSRVLWRU\

)LOH�V�)LOH�V�

�

� The timely and efficient distribution of master data to remote systems is an integral part of a sound master data management strategy. The MDM Syndicator provides an innovative and flexible solution to this problem, ensuring that users throughout your enterprise have access to the same, up-to-date version of your master data.

� Using the same, intuitive interface as other MDM applications, the MDM Syndicator allows you to select record data from an MDM repository and completely restructure it to fit the needs of any remote system without modifying the source data itself.

� Moreover, you can use the MDM Syndicator to create reusable syndication maps, meaning the actual syndication of data can be performed by users without intimate knowledge of the data nor its structure.


SAP AG 2006


6L[�6WHSV�RI�WKH�6\QGLFDWRU 3URFHVV

�


SAP AG 2006

6HWWLQJ�8S�DQG�([HFXWLQJ�D�6\QGLFDWLRQ

�� &RQQHFW�WR�0'0�5HSRVLWRU\�� 6HOHFW�'HVWLQDWLRQ�3URSHUWLHV��RSWLRQDO�� 6HW�0DS�3URSHUWLHV�� 6HW�'HVWLQDWLRQ�,WHPV�3URSHUWLHV�� &RPSOHWH�,WHP�0DSSLQJ�� 3UHYLHZ�;0/�ILOH�� 6HOHFW�UHFRUGV�IRU�V\QGLFDWLRQ�� ([HFXWH�V\QGLFDWLRQ

�


SAP AG 2006

��&RQQHFW�WR�0'0�5HSRVLWRU\

� 6HOHFW�\RXU�5HSRVLWRU\�� 6HOHFW�/DQJXDJH� 8VHU� 3DVVZRUG

�


SAP AG 2006

��6HOHFW�'HVWLQDWLRQ�3URSHUWLHV��2SWLRQDO�

� ,I�\RX�KDYH�D�SUHGHILQHG�VFKHPD��\RX�ZLOO�XVH�WKLV�RSWLRQ�� %\�GHIDXOW��WKH�GHVWLQDWLRQ�ZLOO�EH�D�IODW�ILOH�ZLWKRXW�D�

VFKHPD�DQG�WKH�UHPRWH�V\VWHP�ZLOO�EH�0'0�� &KRRVH�)LOH�Æ 'HVWLQDWLRQ�3URSHUWLHV�

�


SAP AG 2006

��0DS�3URSHUWLHV�7DE

7KH�HOHPHQWV�WKDW�FDQ�EH�DOWHUHG�ZLOO�YDU\�EDVHG�RQ�WKH�W\SH�RI�GHVWLQDWLRQ�ILOH�

6\QGLFDWH�RQO\�WKH�UHFRUGV�WKDW�KDYH�VRXUFH�V\VWHP�NH\�LQIRUPDWLRQ�

6\QGLFDWH�RQO\�WKH�UHFRUGV�WKDW�KDYH�FKDQJHG�VLQFH�WKH�ODVW�V\QGLFDWLRQ�

�

� 6XSSUHVV�8QFKDQJHG�5HFRUGV, if checked, will exclude records from the syndication that have not been modified since the last syndication.

� 6XSSUHVV�5HFRUGV�:LWKRXW�.H\, if checked, will only include records within the selection that have key information.


SAP AG 2006

��'HVWLQDWLRQ�,WHPV�7DE

'HWHUPLQH�GHOLPLWHU�VW\OH�IRU�H[SRUWLQJ�KLHUDUFKLHV

6HW�IL[HG�YHUVXV�YDULDEOH�WH[W�ZLGWKV

�


SAP AG 2006

��,WHP�0DSSLQJ�7DE

0DS�WKH�6RXUFH�,WHPV��WKH�0'0�5HSRVLWRU\�LWHPV��WR�WKH�DSSURSULDWH�'HVWLQDWLRQ�,WHPV��

�

� If one Source Item maps to multiple Destination Items, right-click on the source item and create a clone of it. You can then map both the clone and the original items to the appropriate Destination Items.

� If you are mapping structures to structures, it is important to map not only the fields within the structure, but also the element itself.


SAP AG 2006

��'HVWLQDWLRQ�3UHYLHZ�7DE

3UHYLHZ�WKH�IRUPDW�WKDW�ZLOO�EH�JHQHUDWHG�DQG�PDNH�DGMXVWPHQWV�WR�WKH�'HVWLQDWLRQ�,WHPV�DQG�,WHP�0DSSLQJ�DV�QHFHVVDU\�

�

� The syndication shows the first 10 records in the 3UHYLHZ tab. � In the MDM Syndicator, you are not able to edit the XML file. It is read only.


SAP AG 2006

��6HOHFW�5HFRUGV�IRU�6\QGLFDWLRQ

8VH�)UHH�)RUP��SDUDPHWHUV��VDYHG�VHDUFKHV��RU�PDVNV�WR�QDUURZ�WKH�UHFRUGV�IRU�V\QGLFDWLRQ��7KLV�LV�WKH�VDPH�VHDUFK�EHKDYLRU�DV�LV�XVHG�LQ�WKH�0'0�'DWD�0DQDJHU�

�


SAP AG 2006

��6HDUFK�6HOHFWLRQV�7DE

�

� The resulting output can be narrowed by applying a search result.


SAP AG 2006

��([HFXWH�WKH�6\QGLFDWLRQ

� &KRRVH�WKH�([HFXWH LFRQ��WR�VWDUW�WKH�V\QGLFDWLRQ�� 0'0�ZLOO�FUHDWH�WKH�DSSURSULDWH�;0/�ILOH�V��IRU�IXUWKHU�

SURFHVVLQJ�

�

� Select the appropriate folder on the FTP server and assign a prefix for the XML files. This is where the XML files will be stored and where SAP NetWeaver XI will pick them up for further processing when a batch process or port is used.


SAP AG 2006


$GYDQFHG�6\QGLFDWLRQ

�


SAP AG 2006

'HILQH�WKH�7DUJHW�)LOH�)RUPDW

� /RFDWH��RU�FUHDWH��DQ�;6'�GRFXPHQW�WKDW�UHSUHVHQWV�WKH�VWUXFWXUH�RI�WKH�GDWD�WKDW�ZLOO�EH�V\QGLFDWHG��

� :KHQ�V\QGLFDWLQJ�WR�;0/��WKH�0'0�6\QGLFDWRU DOORZV�WKH�XVHU�WR�DVVLJQ�DQ�DSSURSULDWH�;6'��DQ�;0/�VFKHPD��7KH�;6'�FRQWDLQV�WKH�GHILQLWLRQV�RI�WKH�RXWSXW�ILHOGV��WKHLU�KLHUDUFKLHV��DQG�WKHLU�FKDUDFWHULVWLFV�

� 7KH�;6'�ILOH�LV�XVHG�WR�FUHDWH�D�VWUXFWXUH�WR�PDS�WR�ZLWKLQ�WKH�V\QGLFDWLRQ�EHLQJ�FUHDWHG�

� 7KH�;6'�ILOH�LV�SURYLGHG�E\�6$3�ZLWK�DOO�GHOLYHUHG�EXVLQHVV�UHSRVLWRULHV�

�

� Use of the SAP XI Integration Repository can supply you with XSDs for the Idoc types used to connect to your repository.

� For specifics on using Microsoft Access to create XSD files or creating XSD files from scratch, see the how-to guide, “How To Use the MDM Syndicator to Syndicate Repository Data Using Complex XML Types.”


SAP AG 2006

3URSHUWLHV�RI�&XVWRP�,WHPV

6WDWLF�LQIRUPDWLRQ�FDQ�EH�SUHGHILQHG�XQGHU�WKH�&XVWRP�,WHPV WDE�

0DS�WKH�QHZO\�FUHDWHG�LWHP�WR�D�DSSURSULDWH�ILHOG�LQ�WKH�WDUJHW�VWUXFWXUH��

7R�VHH�WKH�UHVXOWV��FKRRVH�WKH�3UHYLHZ WDE�

�


SAP AG 2006

0HUJHG�,WHPV

�� !�

6RXUFH�)LOH

0DWFKLQJ�)LHOG

"$#&%('*)�+,.- +0/ 1324#5 +0'*60+ 5HVXOW�)LOH

�

� In the merged items properties, you can specify a source table that contains information about which items need to be merged into the existing information.

� You must specify a key that allows the system to allocate the correct record. The syndication will result in a output with merged information based on the specified key.


SAP AG 2006


6XPPDU\

�


SAP AG 2006

0'0�6\QGLFDWRU��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� ([SODLQ�WKH�9DOXH�RI�WKH�0'0�6\QGLFDWRU� 'HVFULEH�0'0�6\QGLFDWRU RSWLRQV� ([SODLQ�KRZ�WR�VHW�XS�D�V\QGLFDWLRQ��ZKLFK�

PRGXOHV�DUH�LQYROYHG��DQG�WKH�SUHUHTXLVLWHV

�


�([HUFLVHV�

8QLW��6$3�0'0�6FHQDULR��0'0�6\QGLFDWRU�7RSLF��0'0�6\QGLFDWRU�


• ([SODLQ�WKH�9DOXH�RI�WKH�0'0�6\QGLFDWRU��• 'HVFULEH�0'0�6\QGLFDWRU�RSWLRQV�• ([SODLQ�KRZ�WR�VHW�XS�D�V\QGLFDWLRQ��ZKLFK�PRGXOHV�DUH�LQYROYHG��

DQG�WKH�SUHUHTXLVLWHV

6LQFH�\RX�ZLOO�EH�KDUPRQL]LQJ�PDVWHU�GDWD�DIWHU�FRQVROLGDWLRQ��\RX�ZDQW�WR�NQRZ�ZKDW�RSWLRQV�DUH�DYDLODEOH�LQ�WKH�0'0�6\QGLFDWRU�IRU�WKH�V\QGLFDWLRQ�RI�GDWD�IURP�6$3�0'0�WR�\RXU�YDULRXV�FOLHQW�V\VWHPV��

�

3XUSRVH�This script walks through the MDM Syndicator. The Syndicator is a map-based application. It uses maps to determine what source data is going to be syndicated from the MDM repository, where to put the data in the syndication file, which remote system is going to receive the syndicated data, and how the data will be formatted when it gets there. You will create an output file for the NewYork remote system.

3UHUHTXLVLWHV�

MDM Repository has been created. Data has been entered in the repository. MDM Server has been mounted and started.

13-1 /RJRQ�WR�0'0�6\QGLFDWRU

The Syndicators purpose it to export information from MDM. Your Yourletter_Case_Study repository must be loaded before proceeding. 13-1-1 Double-click on the MDM Syndicator shortcut 13-1-2 Connect to MDM Repository

Repository: Yourletter_Case_Study�User: Admin

13-1-3 Click OK.


13-2 'HVWLQDWLRQ�3URSHUWLHV The first thing that you must determine is what sort of output you are …

13-2-1 Go to File Æ Destination Properties…

13-2-2 The Destination Properties window will open. The properties available to you are based on the Type selected. With a Type: Flat, there are only the Remote systems, New York, London and MDM. Select New York.

13-2-3 Click OK.

13-2-4 Make sure that the Products table is your selected table.

13-3 'HVWLQDWLRQ�,WHPV Since you are not using an existing schema, there are no Destination Items to map your fields to. But under the Destination Items tab, you can create fields that you want to output.

13-3-1 Switch to the Destination Items tab.

13-3-2 Right-click select $GG�'HVWLQDWLRQ�,WHP. You will create these 6 items: Product ID, Product Name, Product ID with Name, Division, Currency, and Price.

13-3-3 Shift+Enter to save each entry.

13-4 $GG�&XVWRP�,WHPV In the previous step, you created a field called Product ID with Name, but this field does not exist in the source. That is where Custom Items come in.

13-4-1 Switch to Custom Items tab.

13-4-2 Right-click select $GG�&XVWRP�,WHP� 13-4-3 Enter Product ID.Name. You will use a period between the Product ID and

Name.

13-4-4 Double-click on the Formula field and then click on the arrow to the right of Formula and select Product ID [DF].

13-4-5 Then type a “.” (a period without quotes) after Product ID.

13-4-6 Now click on the arrow again and select Name [DF]


13-4-7 First double-click on the Formula field then right-click on the item and select Include Value Only.


13-5 6DYH�6\QGLFDWLRQ�0DS

Before moving on you are going to save the work you have done so far. You should repeat this step often.

13-5-1 Go to )LOH�>�6DYH�$V«

13-5-2 Type in Products - NY for your map name.

13-5-3 Click OK to Save.

13-6 ,WHP�0DSSLQJ

In the Item Mapping tab, you will be able to map the Source items to the Destination items that you created in step13-3.

13-6-1 Switch to the Item Mapping tab.

13-6-2 Select the following Source items and map to the Destination items.

6RXUFH�LWHPV� 'HVWLQDWLRQ�LWHPV�[Remote Key] > [Value] Product ID

Name [DF] Product Name

Division > [Remote Key] Division

Pricing > Currency > [Remote Key] Currency

Pricing > List Price [DF] Price

Product ID.Name Product ID with Name

13-6-3 Save your map.


13-7 'HVWLQDWLRQ�3UHYLHZ

You can verify your output before executing the Syndicator by going to the Destination Preview tab.

13-7-1 Switch to the Destination Preview tab.

13-8 0DSSLQJ�3URSHUWLHV Since you are not using an existing schema, there are no Destination Items to map.

13-8-1 Switch to the Mapping Properties tab.

13-8-2 Enable Suppress Unchanged Records.

13-8-3 Enable Suppress Records without Keys.

13-8-4 Save your map.

13-9 ([HFXWH

After checking one more time in your Destination Preview tab, you are ready to execute the Syndicator.

13-9-1 Click ([HFXWH�� .

13-9-2 A Save As window will open. Save the file as Export-Product.txt on your desktop or My Documents folder.

13-10 ([DPLQH�5HVXOWV�You saved your syndication file on your desktop. You will now take a look at the file.

13-10-1 Go to your desktop and double-click on Export – Product.txt.

13-10-2 Open file to see the final output.

+LQW: If you get an error and you would like to export the data a second time, please deselect "Suppress Unchanged Records" and re-export.


SAP AG 2006

0'0�$XWRPDWLRQ




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�


SAP AG 2006

&RQWHQWV�� 0'0�,PSRUW�%DWFK� 0'0�,PSRUW�6HUYHU� 0'0�6\QGLFDWLRQ�6HUYHU

0'0�$XWRPDWLRQ

�


SAP AG 2006

0'0�$XWRPDWLRQ��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 'HVFULEH�LQERXQG�SURFHVV�XVLQJ�0'0�,PSRUW�

0DQDJHU�%DWFK�DQG�RU�0'0�,PSRUW�6HUYHU� 'HVFULEH�RXWERXQG�SURFHVV�XVLQJ�0'0�6\QGLFDWLRQ�

6HUYHU

�


SAP AG 2006

0'0�$XWRPDWLRQ��%XVLQHVV�6FHQDULR

� $V�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RX�DUH�LQWHUHVWHG�LQ�KRZ�WR�DXWRPDWH�WKH�LPSRUW�DQG�V\QGLFDWLRQ�SURFHVVHV��

� ,Q�RUGHU�WR�ORDG�PDVWHU�GDWD�LQWR�0'0�LQ�WKH�EDFNJURXQG�\RX�QHHG�WR�XVH�WKH�,PSRUW�6HUYHU�DQG�XQGHUVWDQG�LWV�IXQFWLRQDOLW\�

� ,Q�RUGHU�WR�V\QGLFDWH�PDVWHU�GDWD�IURP�0'0�LQ�WKH�EDFNJURXQG�\RX�QHHG�WR�XVH�WKH�6\QGLFDWLRQ�6HUYHU�DQG�XQGHUVWDQG�LWV�IXQFWLRQDOLW\�

�


SAP AG 2006

%DWFK�,PSRUW&UHDWLQJ�3RUWV,PSRUW�6HUYHU6\QGLFDWRU 6HUYHU

%DWFK�,PSRUW

6XPPDU\

�


SAP AG 2006

� :KLOH�WKH�,PSRUW�0DQDJHU�DQG�WKH�6\QGLFDWRU RIIHU�H[WHQVLYH�IXQFWLRQDOLW\�ZKLOH�LPSRUWLQJ�DQG�H[SRUWLQJ�GDWD��WKH\�FDQ�RQO\�EH�UXQ�PDQXDOO\��

� 7KH�EDWFK�YHUVLRQ�RI�WKH�0'0�,PSRUW�0DQDJHU�FDQ�SHUIRUP�RQH�RU�PRUH�LPSRUWV�IURP�D�FRPPDQG�OLQH��

� %DWFK�SURFHVVLQJ�LV�VXEMHFW�WR�WKH�IROORZLQJ�FRQVLGHUDWLRQV�7 $OO�FRQILJXUDWLRQ�UHJDUGLQJ�WKH�EDWFK�LPSRUW�VKRXOG�EH�FUHDWHG�

XVLQJ�WKH�0'0�,PSRUW�0DQDJHU�DQG�VDYHG�LQ�DQ�LPSRUW�PDS�7 7KH�$XWRPDS�8QPDSSHG�9DOXHV�FRQILJXUDWLRQ�RSWLRQ�DOORZV�

\RX�WR�VSHFLI\�ZKHWKHU�RU�QRW�WR�DWWHPSW�WR�DXWRPDS XQPDSSHG�YDOXHV��

7 7KH�'HIDXOW�%DWFK�8QPDSSHG�9DOXH�+DQGOLQJ�FRQILJXUDWLRQ�RSWLRQ�DOORZV�\RX�WR�VSHFLI\�ZKHWKHU�WR�LJQRUH�RU�DGG�XQPDSSHG�YDOXHV�RU�WR�PDS�WR�DQ�H[LVWLQJ�GHVWLQDWLRQ�GDWD�YDOXH�

0'0�$XWRPDWLRQ

�

� You can use the batch version of the MDM Import Manager to perform one or more imports in batch mode, invoking the batch executable from a command line using a previously saved import map.


SAP AG 2006

� $XWRPDSSLQJ EDWFK�KDQGOLQJ8 $XWRPDS��\HV�RU�QR��8 8QPDSSHG�

�LJQRUH�RU�DGG�8 +LHUDUFK\�DXWR�PDSSLQJ��

)XOO�SDWK�YV��OHDI�QRGHV�RQO\

8 1RUPDOL]H�VRXUFH�DQG�GHVWLQDWLRQ�YDOXH��\HV�RU�QR�

� 7KHVH�VHWWLQJV�DUH�VDYHG�ZLWK�WKH�PDS�DQG�DSSOLHG�ZKHQ�UXQQLQJ�,PSRUW0DQDJHU%DWFK�H[H��7KH�VHWWLQJV�SURYLGH�GHIDXOWV�IRU�KDQGOLQJ�YDOXHV�IRXQG�LQ�WKH�VRXUFH�WKDW�ZHUH�QRW�SUHVHQW�ZKHQ�VDYLQJ�WKH�0$3�ILOH�

,PSRUW�0DQDJHU�&RQILJXUDWLRQ�2SWLRQV�IRU�%DWFK

�

� These configuration options settings provide defaults for handling values found in the source that were not present when the MAP file was saved.

� Performing the data import with batch runs provides many advantages: y Schedule import of data to outside of work hours. y Schedule import of data from one database into MDM. y Improve import performance by eliminating screen updates during the import process.

� The MDM Import Manager provides Provide logs for unattended sessions for verification and check of a successful execution.

� To prepare a batch run, the following steps need to be performed: 1. Configure the “job” using the MDM Import Manager GUI.

- Set configuration options for MDM Import Manager batch. - Setup the MDM Import Manager from source to destination and save .MAP file.

2. Configure .INI file with default values for batch run. 3. Schedule the batch execution. 4. Consult log files for error/success.


SAP AG 2006

7\SHV�RI�&RQILJXUDWLRQ

� 'HIDXOW�KDQGOLQJ8 1XOO�YDOXHV��3UHVHUYH�RU�,JQRUH8 &DVH��&DVH�VHQVLWLYH�RU�FDVH�LQVHQVLWLYH8 'HOLPLWHU�VWULQJ��6SOLW�KLHUDUFK\��VSOLW�PXOWL�ILHOGV��SDUWLWLRQ��

FRPELQH��DQG�VR�RQ� $XWRPDSSLQJ EDWFK�KDQGOLQJ

8 $XWRPDS��\HV�RU�QR��8QPDSSHG��LJQRUH�RU�DGG�8 +LHUDUFK\�DXWR�PDSSLQJ��)XOO�SDWK�YV��OHDI�QRGHV�RQO\8 1RUPDOL]H�VRXUFH�DQG�GHVWLQDWLRQ�YDOXH��\HV�RU�QR�

� 5HFRUG�PDWFKLQJ�UXOHV8 3HUIRUP�UHFRUG�PDWFKLQJ�ZKHQ�HDFK�ILHOG�LV�VHOHFWHG�

�\HV�RU�QR�8 1RUPDOL]HG�PDWFK�DJDLQVW�QRUPDOL]HG�YDOXH8 ([DFW�PDWFK�DJDLQVW�QRQ�QRUPDOL]HG�YDOXH

�


SAP AG 2006

%DWFK�([HFXWLRQ

� 7KH�0'0�,PSRUW�0DQDJHU�EDWFK�FDQ�EH�H[HFXWHG�E\�DQ\�VFKHGXOLQJ�WRRO�WKDW�VXSSRUWV�VFKHGXOLQJ�RI�:LQGRZV�FRPPDQG�OLQH�H[HFXWDEOHV�

� &RPPDQG�OLQH�H[HFXWLRQ�7 ,PSRUW0DQDJHU%DWFK�H[H´��,1,��ILOHQDPH�LQL!��0$3��PDSQDPH!

� :KHUH�9 �,1,�ILOH9 �PDS�QDPH!�UHIHUV�WR�D�PDSSLQJ�VWRUHG�LQ�WKH�UHSRVLWRU\

� <RX�PXVW�SXW�LQ�WKH�IXOO�SDWK�QDPH�IRU�WKH�WZR�ILOHQDPH�SDUDPHWHUV�LI�WKH\�GR�QRW�H[LVW�LQ�WKH�VDPH�GLUHFWRU\�DV�WKH�0'0�,PSRUW�0DQDJHU�EDWFK�H[HFXWDEOH�

�

� Log files are stored in the same directory as the MDM Import Manager executable: y ImportManagerBatch.log is appended by each execution of the MDM Import Manager batch

executable. y ImportManagerError.log documents any errors encountered during the batch process (file is

appended).�� Tip for troubleshooting: The /VERSION command line option displays software version

information.


SAP AG 2006

�,1,�)LOH�&RQILJXUDWLRQ�IRU�%DWFK�5XQ

7 7KH�IROORZLQJ�HQWULHV�DUH�H[DPSOHV�RI��,1,�ILOH�VHWWLQJV��$�FRPSOHWH�OLVW�FDQ�EH�IRXQG�LQ�0'0�,PSRUW�0DQDJHU�EDWFK�GRFXPHQWDWLRQ�: ;=<�> 2�+('.? < 2*)0@�ACBEDFB: G "$#H%('*)I+�J: K0L0M +INO"QPSR > +0'4TU+0': V -W/ +YX < 5 +IN: Z ? ; "["�+0'4TU+0'*N LU< X(\]+O+: Z^< 2 <(_O<�> +UNO` M0M /W- +I1 ;a<> 2�+0'cb 5YdIdUd: ef> +0'*N >U<: g&<>U>�h #&'*1(N: i + < 1Hj�#kX0/ L NI, < / > +: G�Z + > 2!-cX < 2l- #kXIJ: i + M # > - 24#k' L NO` M&M /C- +O1Ub 5 <U> 2�+0': "�+�'4TU+0'!N�monpR V: g #&'�2*NIqOrq0r: ef> +0'*NO`�1 5 -cX: g&<>U>�h #&'*1(N

�


SAP AG 2006

%DWFK ,PSRUW&UHDWLQJ�3RUWV,PSRUW�6HUYHU6\QGLFDWRU 6HUYHU6XPPDU\

&UHDWLQJ 3RUWV

�


SAP AG 2006

%HQHILWV�RI�3RUWV

� 3RUWV�DUH�GHVLJQHG�WR�UHPRYH�LQERXQG�DQG�RXWERXQG�SURFHVVLQJ�FRPSOH[LW\�DQG�XVHU�HUURUV�E\�GHILQLQJ�LQ�WKH�0'0�&RQVROH�WKH�IROORZLQJ�W\SHV�RI�SRUWV�

� ,QERXQG��0'0�,PSRUW�0DQDJHU�8 6HOHFW�WKH�UHPRWH�V\VWHP�WKDW�RULJLQDWHG�WKH�GDWD�8 ,GHQWLI\�WKH�ORFDWLRQ�ZKHUH�VRXUFH�GDWD�ILOHV�DUH�ZDLWLQJ�WR�EH�

ORDGHG�8 6HOHFW�D�VRXUFH�GDWD�ILOH�8 6HOHFW�WKH�DSSOLFDEOH�0'0�,PSRUW�0DQDJHU�PDS�

� 2XWERXQG��0'0�6\QGLFDWRU�8 6HOHFW�WKH�UHPRWH�V\VWHP�WKDW�ZLOO�UHFHLYH�WKH�GDWD�8 6HOHFW�WKH�DSSOLFDEOH�0'0�6\QGLFDWRU PDS�8 ,GHQWLI\�WKH�ORFDWLRQ�ZKHUH�GDWD�ILOHV�VKRXOG�EH�SODFHG�IRU�

GHOLYHU\�

�

� With remote systems as a foundation, an MDM port encapsulates all of the configuration and logistical information associated with inbound and outbound processing of data from these remote systems. In so doing, it simplifies the process of: (1) delivery and consolidation of raw data from remote systems into MDM using the MDM Import Manager; and (2) extraction and distribution of data from MDM to remote systems using the MDM Syndicator.

� In each case, the port represents the logical point of contact between MDM and the outside world (e.g. XI or a user of the MDM Import Manager). Within the MDM Import Manager and MDM Syndicator, it represents the physical staging location of data and a logical handle by which to identify all of the encapsulated information.

� 1RWH: Along with simplifying the user interaction, ports also lay the foundation for future automation of the consolidation and distribution processes within MDM.


SAP AG 2006

&UHDWLQJ�3RUWV�LQ�0'0�&RQVROH

3RUWV�DUH�FUHDWHG��HGLWHG��DQG�GHOHWHG�ZKHQ�WKH�UHSRVLWRU\�LV�XQORDGHG�

$�SRUW�7\SH�LV�HLWKHU�LQERXQG��RXWERXQG��RU�ERWK)RUPDW

�

� The Ports table is a system table under the Admin node in the Console hierarchy in the MDM Console. It contains configuration and logistical information associated with consolidation and distribution of MDM data.

� You can manually add, modify, and delete ports for an MDM repository by editing the ports records of the Ports table.


SAP AG 2006

&UHDWLQJ�3RUW�)ROGHUV

s^t0u*v�t(ukwyx$z�{�zH|Iz�}Ot~ t0�I�0}(� {��&u!�x��Eu*tI��{�� k��0�(�It~ tO��{4tps^�U}I{�tO��(��t

s$�k��u*��t��0�W� t�}� ��(�E� tU}s^{�z�{.�I}Y�(�E� t�}

� 7KH�SRUW�FUHDWHG�ZLOO�EH�VDYHG�XQGHU�3URJUDP�)LOHV�Æ0'0��Æ 6HUYHU�

� 1HZ�ILOHV�DUH�SODFHG�LQ�WKH�5HDG\ IROGHU�� 2QFH�WKH�ILOH�LV�LPSRUWHG��WKH�ILOH�ZLOO�EH�PRYHG�WR�WKH�

$UFKLYH IROGHU��

�

� The files associated with ports are stored in a shared file system location with a fixed directory structure beneath a configurable root. The root must be accessible to both MDM and its location is specified in the mds.ini file.


SAP AG 2006


,PSRUW�6HUYHU

�


SAP AG 2006

� 7KH�0DVWHU�'DWD�,PSRUW�6HUYHU��0',6��DXWRPDWHV�WKH�WDVN�RI�LPSRUWLQJ�PDVWHU�GDWD�LQWR�0'0�UHSRVLWRULHV��,W�LV�GHVLJQHG�WR�UHGXFH�WKH�SURFHVVLQJ�FRPSOH[LW\��UHVRXUFH�UHTXLUHPHQWV��DQG�RSSRUWXQLW\�IRU�XVHU�HUURU�FRPPRQ�WR�GDWD�LPSRUW�WDVNV��ZKLOH�DW�WKH�VDPH�WLPH�HQVXULQJ�WKDW�WKH�PRVW�XS�WR�GDWH�YHUVLRQV�RI�\RXU�PDVWHU�GDWD�DUH�VWRUHG�LQ�WKH�UHSRVLWRU\�

� ,Q�DGGLWLRQ��VLJQLILFDQW�GHSOR\PHQW�DQG�VFDODELOLW\�EHQHILWV�FDQ�DOVR�EH�JDLQHG�E\�UXQQLQJ�LPSRUWV�IURP�0',6�UDWKHU�WKDQ�WKURXJK�WKH�,PSRUW�0DQDJHU�

,PSRUW�6HUYHU

�


SAP AG 2006

0'0�,PSRUW�6HUYHU8V

H�&D

VH ��S��c��c�o� ��U�C�]�¡ ��¢ ��O¢ ��£ £ ¤¦¥4�C��[§��¢ �I¨��U¨��c��¡©��o�Oª¦��«��¬��W�ª��a ��O�E��Iª�� «¢ ��= ��Iª��ª�� c��«��F��I�W�o ��C��¢ ª�®=�]¥��O¨]�C��c�¡¢ �S ��O� ��o�©��]¯°®I�c�U¨�ª��S �c��±E�� §¢ ��²¥��C�U�³¥*�C�Uª��

´�]ª��µ �c��¢ ª�®¡±�¢ �¡ ��O� �O�F��

®��ª��E��¢ �Oª�²¶ ��ª·©��·¨��¢ £ ¢ ¸��a¢ ª¦��I¢ �*¢ �IªQ��¡¹Fº�¹¼» �= ]�O� �0¹��ª��®��I�U» �¡ ]�I�E�O¹��ª��®��O©��«

½ ¾ ¿ À Á Â Ã À Ä ÅÆ!ÇcÆ�È É*Ê ËWÌ Í ÎcÏ Ì Ð Ï Ì

Æ4Ç�Æ�ÎCÏEÌ Ð ÏEÌÆ!ÇcÆ�È É*Ê ËWÌ Í Æ*Ñ Ò Ñ Ó Ï ÌÔ Õ�ÖcÈ ×Ø �·u*t�z�{�tÙz0�� I�ku4{k�3z(�Ù�k��tIÚUz0�O�Ûu4tOÜ4�I}Itp��Ý&{!Þ�tß�3z0�pÝ*�&u&Ý.�U{l�0u4tµ}0�&�(u4�Itp�(z�{�z

� �Û�O�ku�{Hàp� {�ÞO�&�I{HzH�U�ß�f�Ut0u4zU{4�ku��W�U{�t0u4vIt(�I{.� �&�Ø á �O�tp{.ÞItÙ�0zU{�z3� }3�0t0�W� vUt0u4t0�â|I�ps^ã¡ä�åFæ�&�pzß}(�ItI�� Ý�� 3��ku�{!ÚI� {0àp�E�C�z(�{4�H�Yz�{.� �Uz0�E� �Ù�0t{��(� �(ç]tI�ÙàÙ� {�Þ(�E�Ùzp�O�f��Ý�� f�(u4z0|0� ta{.� �Yt3�W�I{�t0u�vIzH�]z��â|Ot

è �ItH�ItU��Ý4�ku^� �Û�O�&u4{��0u!�(��t�}I}H�E�O�Ø �kÞItÙ�k�U{*�U�H�3tß��Ý&{!ÞItY� �Û��&u�{^�(u!�(��tI}U}0�W��â� }��(�O�(z{4tO��&u$�Itàé�3zU}�{*t0u&�0zU{�z

u4tI�I�Hu!��}��E�p{.ÞItYu4t0�0�I}H� {!�&u4�pz(�O�â� �(��Ý!�C� tU}ß��ÝH{.ÞItßt0�U{��Eu*t3� �(zI��(u4�(�It�}�}

)HDWXUHV

Ø ê z�}U{�t0u&�0zU{�zY� �Û�O�ku�{�}Ù�z&��|Itpt�zI}(�W� �ßz(�I{4�H�3z�{*tU�3zH�O�âuë�0�Y�W�µ{�ÞIt�|IzO��ç�&u!�k�(�O�Ø ì �â�U}Ot(uf�C�I{�t0u4zI��{.� �f��u*t è �(�Eu*t��Ø ä^u!��v0� �0tU}Ù�Y�f�0� {*�ku��E��Uz(�Iz�|H�W�E� {!� t�}µÝ!�kuk�0z�{�z�� â�O�&u*{Ø í �Iz0|0� t�}µ}��Uz0� z(|(�E�W� {��pz(�I�â� �0zU�[|Uz0� z��O�(�C�I�ÙÝ!�ku&�0zU{�z3� ��O�&u4{�}

%HQHILWV

$XWRPDWHG�,PSRUW

�


SAP AG 2006

0'0�,PSRUW�6HUYHU�6HWXS7HFKQLFDO�'HWDLOV

î 6HUYLFH�fÞIt ��k� }(ïC�E�(�]Ý��E� t Ý*zU��C�W� {�z�{4t�} �O�k��Ýl� �k�0u!z�{�� &��Iz0u4zO��tU{�t0u �0ÞIz��0�0t�}pÝ4�ku&{.ÞItß��z��W�p}It(u�vH� ��tµz�}àat0�E�]zI}ß�0tUÝ�z0�H� {��I}&�ItU�0� Ý.� �p}It{4{.�W�O��}µÝ.�Hu}O�k�0u!�It�c�0tU}�{��W�IzU{!�E�&��E�â�O�&u*{^|Ut(ÞIzUvH� �ku�ï

î 3RUWVí �O��z��O}(�(� z�{�t�}Ùz0�W��OÝ({�ÞIt3��k�IÝ.� �f�(u4z�{.� �&�Ùz(�U�� 0�k� }O{�� z(�U�E�OÝ��ku!�3zI{�� f�pz�}O}O�0�� z{4t��ßàp� {�Þ��C�H|I�k�H�I�z0�O��k�{ë|U�^�(�O�Û�0u!�H�t�}I}H�E��Ýk��z�{*zaÝ.u.�k�ð��E� tH�{}I�U}U{�t��Ù}(ïí(ñ {�t0�0�OtO�Û�O�ku4{(Ý4�f� �0t0u&}U{.u��{.�(u4tµ{*��}U{4�fu4t3� �0��Ý.�E� tI}

î 5XQWLPHs��W�I��tY|U�Ù�0t�Ý.�c�� {!�E�&�ßzµ}Ut0u*vH� ��t �(�Ht}Y��{^ÞIzUvOtµzò æ Ú�{.ÞOt ê x ê æ �Û�O�Hu�{Hs$t(u�vIt0u&Ý.�(�O�{.� �k�Uz0�c� {��Ù�3zI��|It��ÞItO�0ç�tI�[�}H�C�I�3{�ÞUtp{4�H�&� }ßz�vOz0�E� z0|0� tß�k�ß{!ÞIt�(� z�{�Ý!�ku!�ó�k�aàÙÞ(� �(Þµ{.ÞOta}It0u*v(� �tY� }3�0t0�(� ��ItO�

î 0RQLWRULQJ�&DSDELOLWLHVs^{�t0��Ü*|U��Üc}I{�tH�pz0��&� {H{.u4z0�E��Ý({�ÞIt3�E�â�O�&u*{kz��O�zp}�{4zU{.��}��E�O�f� �Uz�{��W�I�3àßÞOt�{.ÞOt�uH{.ÞOt3� �Û��fu�{}(�O�I�Ut�tI�(tO�Y�ku^�O�0{.ï �^ÞUt�}Ot�� H�ÙÝ.�C� t�}Ùz0u4tzI�I��t�}I}0�C|�� tµv0� z ê x ê �¦�k��}(�H� t ï

ô�õëö ÷ëõlö�øFù�ú.û úlüýú!þëõÿ õ��ýþ�� û ��ö �ù�� ö õ��.û� ��ÿ õ�� ýû õ(ô��lþ�û õ�� ö û

ô��ö ��õ�� õ�þ� �� õ!þô�û ú�û��ëþ �� õ.þ

�� ! "$#�% & ')(+*-,/.��10�2�0 3�4 35*6,/'7� 8�'7�/*92�% (;: � % < =;: % ��>�(

?@A

� �� õ.þB/CED/F�G HI J�DEFEG H

�

� Service The mdis.ini file facilitates configuration parameter changes for the main service as well as default/specific settings for source/destination import behavior.

� Ports Encapsulates all of the configuration and logistical information associated with inbound and outbound processing of data from remote systems. An extended port folder structure exists to store log files.

� Runtime Since by definition a service does not have a user interface, the MDM Import Server functionality may be checked using the tools available on the platform on which the service is deployed.

� Monitoring Capabilities Step-by-step audit trail of the import and a status indicating whether the import succeeded or not. These log files are accessible via MDM Console.


SAP AG 2006

6\QGLFDWRU 6HUYHU


�


SAP AG 2006

� 7KH�0DVWHU�'DWD�6\QGLFDWLRQ�6HUYHU��0'66��DXWRPDWHV�WKH�WDVN�RI�V\QGLFDWLQJ�PDVWHU�GDWD�IURP�0'0�UHSRVLWRULHV��,W�LV�GHVLJQHG�WR�UHGXFH�WKH�SURFHVVLQJ�FRPSOH[LW\��UHVRXUFH�UHTXLUHPHQWV��DQG�RSSRUWXQLW\�IRU�XVHU�HUURU�FRPPRQ�WR�GDWD�H[SRUW�WDVNV��ZKLOH�DW�WKH�VDPH�WLPH�HQVXULQJ�WKDW�WKH�PRVW�XS�WR�GDWH�YHUVLRQV�RI�\RXU�PDVWHU�GDWD�DUH�DYDLODEOH�WR�V\VWHPV�WKURXJKRXW�\RXU�RUJDQL]DWLRQ�

� ,Q�DGGLWLRQ��VLJQLILFDQW�GHSOR\PHQW�DQG�VFDODELOLW\�EHQHILWV�FDQ�DOVR�EH�JDLQHG�E\�RIIORDGLQJ�V\QGLFDWLRQV�IURP�WKH�FRPSXWHU�UXQQLQJ�WKH�6\QGLFDWRU WR�D�PDFKLQH�UXQQLQJ�0'66�

� 'ULYLQJ�WKHVH�EHQHILWV�DUH�WZR�NH\�IHDWXUHV�RI�0'66�7 3RUW�GULYHQ��6LPSO\�FUHDWH�DQ�RXWERXQG�UHSRVLWRU\�SRUW�DQG�

0'66�NHHSV�LW�SRSXODWHG�ZLWK�WKH�IUHVKHVW�PDVWHU�GDWD�7 0DS�EDVHG��(DFK�V\QGLFDWLRQ�LV�SHUIRUPHG�DFFRUGLQJ�WR�WKH�

SUHGHILQHG�V\QGLFDWLRQ�PDS�DVVRFLDWHG�ZLWK�WKH�RXWERXQG�SRUW�

6\QGLFDWRU 6HUYHU

�

� The strength of the Syndicator is its interactive map-making capabilities. Through its connection to the source MDM repository, you have full awareness of the tables, records, fields, and attributes available for syndication. You can then use the Syndicator to customize repository data for syndication to specific remote systems and save this customization to maps for later re-use. The Syndicator can also be used to syndicate records to any location on your file system.

� The strength of MDSS, by contrast, is automation. MDSS requires no user intervention to syndicate records from an MDM repository. Instead, it relies on maps created previously with the Syndicator to syndicate records to outbound MDM ports. Syndications are executed 24 hours a day, seven days a week, until either MDSS or MDM Server are stopped.


SAP AG 2006

0'0�6\QGLFDWLRQ�6HUYHU

s^�(�I�k� �z�{�t��3z�}O{�t(uk�(z{4z3u*tI�U�&u.��}Y�Ot0u�� H�k� ��z0�E� �µ{*��0tUÝ.�W��tU��t�}U{��W�UzI{�� k�I}|Iz}It��f�µ{lÞUtµt ñ {4t(�I�0tO�â�0�Hu4{H�O�k�O�Ut��U{

�fÞ0� }Ù�U�H��O�&�Ot0�U{H}UtH�Iz0u4z�{4t�}µ{lÞUt3�U�&u*t��(u*�(�tU}I}(�E��0Ýk�3zI}U{�t0uf�0z{4zßt ñ �I�ku�{{4�3z�|�zO�0ç��ku*�f�0��â�(u*�H��tU}I}LKC}Ot(u4v0� �ItNM�Ý.u.�(� Ý.u!�k�U{*Ü�t0�I�Û�(u*�H�Ut�}U}H�E�O�KC}U�(�0�H� �zI{.� �f�ß�(t(��t(u�zI{�� f�OM

��z��|Ot��U{��E�E� P�tO�â�c�pzU�H�k� {.� �k�p{4� ê x ê s^�(�O�k� �zU{!�&u

Ø �·u*t�z�{�tÙza}U�(�O�k�E��z{�� k�Ù�k��t�Úz(�O�âu*tOÜ4�I}�tp��ÝH{.ÞItµ}I�(��&� �Uz{�� ^�µÝ*�kuHÝ!�O{!�(u4t3��z}U{*tHu��z�{�zÙt ñ ��ku�{0àÙ� {.Þ��k��{&z0�I�ß�^��t(u�zU{!�&u��E�I{4t(u�vOt��U{.� �k�

Ø x�t0�E� vIt�u*}Ù�3z�}O{4t�uk�(z�{�z3u!tU�I�ku!��}pzU}ß�Hz�{�zpÝ.�E� t�}QKct0ï �&ï Ú]å ê � �3tU}I}IzO��t�}�M�{��k�I{.|��&�H�O��I�ku�{�}ß{.u�� H��t0u4t0�â|��Ùza}H� �â�(� tß}O�0ÞUtI�f�(�E�c�I�Y��tO�OÞIzH�(� }��

Ø �kÞItÙ�k�U{*�U�H�3tß��Ý&{!ÞItßt ñ �I�ku�{^� }Ù�(z�{�zµÝ.�W� tU}LK�t�ï �kï Ú]å ê � �Yt}I}OzI�0tI}RM�Ý!�&uHÝ!�(u4{�ÞUt0u�0u!�0��tI}U}(�E��â|O�ps^ãoä�å·æ�z0��â� �(�ÙÝl�E� tU}3��Ý({.ÞItpt(�I{.�Wu4ta}I�(�O�^� ��z{l� �k�Y�(u*�H��tU}�}

Ø ê z�}U{�t0u&�0zU{�zßt ñ �O�ku4{�}Ù�Iz��|Utµt�z}(�W� �pz(�I{4�H�3z�{4tI�3zH�O�âul�(�Y�W�µ{�ÞIt�|IzO�Oç��&u*�f�(�O�Ø ì �â�U}Ot(uf�C�I{�t0u4zI��{.� �f��u*t è �(�Eu*t��Ø ä^u!��v0� �0tU}Ù�Y�f�0� {*�ku��E��Uz(�Iz�|H�W�E� {!� t�}µÝ!�kuk�0z�{�zÙt ñ ��ku�{Ø í �Iz0|0� t�}µ}��Uz0� z(|(�E�W� {��pz(�I�â� �0zU�[|Uz0� z��O�(�C�I�ÙÝ!�ku&�0zU{�zµt ñ ��ku�{�}

)HDWXUHV

%HQHILWV

$XWRPDWHG�([SRUW8V

H�&DV

H

½ ¾ ¿ À Á Â Ã À Ä ÅÆ4Ç�ÆÎS Ò TU V Ñ Í U ËEÒ*ÎcÏ Ì Ð ÏEÌ

Æ4Ç�Æ�ÎCÏEÌ Ð ÏEÌÆ*Ç�Æ�ÎWS Ò TU V Ñ Í ËCÌÔ Õ�ÖcÈ ×

�


SAP AG 2006

0'0�6\QGLFDWLRQ�6HUYHU�6HWXS7HFKQLFDO�'HWDLOV

Ø s�t0u�v(� �Ut�fÞIt ��}U}HïE�C��Ý.�W� t Ý�zI�0�W�W� {�z�{4t�} �U�&�IÝ.� �k�(u4zU{�� k��Iz0u4zO��tU{�t0u �0ÞIz��0�0t�}pÝ4�ku&{.ÞItß��z��W�p}It(u�vH� ��tµz�}àat0�E�]zI}ß�0tUÝ�z0�H� {��C}&�UtI�� Ý�� p}Ut�{�{l�E�O�0}µÝ*�ku}O�k�0u!�It�c�0tU}�{��W�IzU{!�E�&�ßt ñ ��ku�{f|Ot0ÞIzUvH� �ku

Ø äk�ku�{�}í �O��z��O}(�(� z�{�t�}Ùz0�W��OÝ({�ÞIt3��k�IÝ.� �f�(u4z�{.� �&�Ùz(�U�� 0�k� }O{�� z(�U�E�OÝ��ku!�3zI{�� f�pz�}O}O�0�� z{4t��ßàp� {�Þ�W�0|O�f�(�O�3zH�O��f�U{�|O�&�H�O�Û�(u*�(�Ut}I}(�C�I��Ý&�0z{!zÝ�u*�H�ð��E� t0��{H}U�U}O{�tO�Ù}Hïí(ñ {�t0�0�OtO�Û�O�ku4{(Ý4�f� �0t0u&}U{.u��{.�(u4tµ{*��}U{4�fu4t3� �0�Ý��E� t�}

Ø ~ �(��{.�E�3ts��W�I��tY|U�Ù�0t�Ý.�c�� {!�E�&�ßzµ}Ut0u*vH� ��t �(�Ht}Y��{^ÞIzUvOtµzò æ Ú�{.ÞOt ê x ê s^�(�I�k�E�z�{.� �k�ps$t�u4vIt�uHÝë��0��{.� �&�Oz0�E� {��Yz��|Otp�0ÞItI��ç�tO�Û�U}0�W��Ù{�ÞIta{.��k� }ßz�vIz(�W� z0|(� tX �&�µ{lÞItY�(� z�{�Ý4�ku!�ó�k�µàÙÞ0� �0Þµ{�ÞItµ}Ot0u�v(� �It�� }�0t0�0�E��Ut��

Ø ê �&�(� {*�Hul�C�O��z��Iz(|(�E�W� {�� tU}s^{�t0��Ü*|U��Üc}I{�tH�pz0��&� {H{.u4z0�E��Ý({�ÞItpt ñ �0�Hu4{kz��O��z}U{�z�{ë�}Y�C�O�&� �UzU{!�C�O�ßàÙÞUt�{ëÞ�t(uH{�ÞItpt ñ �0�Hu4{}(�O�I�Ut�tI�(tO�Y�ku^�O�0{.ï�fÞIt}�t�� H�ÙÝ.�C� tU}ßz0u*tµz��U�t�}O}(�E|(� tµv(� z ê x ê��k��}��k� t

ô�õlö ÷lõëö�øFù]ú.û úlüëú.þëõÿ õ��ýþ�� û ��ö �ù�� ö õE��û� ��ÿ õ��Y��û õ0ô��þ�û õ�� ö û

ù�ú.û úZ�� õ.þ� ��[�� õ.þ?@A

�� !�"$#�% & ')(+*-,E.��10+2E0 3�4 3�*\,/'7� 8�'7�/*92�% (;: � % < =;: % ��> (

� �� õ.þBEC/DEF�G HI J�DEF/G H

�

� Service The mdss.ini file facilitates configuration parameter changes for the main service as well as default/specific settings for source/destination import behavior.

� Ports Encapsulates all of the configuration and logistical information associated with inbound and outbound processing of data from remote systems. An extended port folder structure exists to store log files.

� Runtime Since by definition a service does not have a user interface, the MDM Syndicator Server functionality may be checked using the tools available on the platform on which the service is deployed.

� Monitoring Capabilities Step-by-step audit trail of the import and a status indicating whether the import succeeded or not. These log files are accessible via MDM Console.


SAP AG 2006

6XPPDU\


�


SAP AG 2006

0'0�$XWRPDWLRQ��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 'HVFULEH�LQERXQG�SURFHVV�XVLQJ�0'0�,PSRUW�

0DQDJHU�%DWFK�DQG�RU�0'0�,PSRUW�6HUYHU� 'HVFULEH�RXWERXQG�SURFHVV�XVLQJ�0'0�6\QGLFDWLRQ�

6HUYHU

�


�([HUFLVHV�

8QLW�� 5HPRWH�6\VWHP�3RUWV�7RSLF�� 0'0�$XWRPDWLRQ�


• &UHDWH�D�UHSRVLWRU\�SRUW�• 6HH�DQG�XQGHUVWDQG�WKH�IROGHU�VWUXFWXUH�FUHDWHG�E\�WKH�SRUW�

2QH�RI�WKH�RQJRLQJ�SURFHVVHV�LV�WR�XSGDWH�\RXU�&DVHB6WXG\�UHS�GDWD��,Q�RUGHU�WR�DXWRPDWH�WKH�SURFHVV�\RX�ZDQW�WR�PDNH�LPSRUW�RI�WKH�GDWD�URXWLQH��7KLV�FDQ�EH�GRQH�E\�FUHDWLQJ�D�SRUW��

3XUSRVH�This script walks through the process of setting up ports for MDM Remote Systems in order to enable the automation of imports and syndications.

14-1 Create Remote System Inbound Ports

We will now add Remote System import (inbound) ports to <RXU/HWWHUB&DVHB6WXG\�repository.

14-1-1 In the Console Hierarchy Pane click on the server where your repository is mounted.

14-1-2 From the list of repositories, click on the repository you wish to modify and unload the repository immediately.


14-1-3 In the list of repository tables, select the Ports table.

14-1-4 In the Ports upper pane, right click to add a port.


14-1-5 Enter the following information for the inbound port:

• Name: New York Inbound

• Type: Inbound

• Remote System: NewYork

• Format field: Excel


14-2 Create Outbound Port:

We will now add Remote System syndication (outbound) ports to your Case_Study repository.

14-2-1 In the Ports detail, right click to add a port.

14-2-2 Enter the following information.




14-2-5 From the list of repositories, click on the repository you wish to modify and load the repository immediately.

14-3 Examine the Remote System Ports

You will now manually examine the Remote System Ports you have created.

14-3-1 Open Windows Explorer in your WTS session and navigate to the directory:

� *��3URJUDP�)LOHV�6$3�0'0��6HUYHU�'LVWULEXWLRQV��14-3-2 Under the folder Distributions, you should find two sub-folders, Inbound and

Outbound and when you expand them, you should see the following:

14-3-3 Exit Windows Explorer.


SAP AG 2006

0XOWLOLQJXDO�6XSSRUW




7D[RQRP\




([SUHVVLRQV


&RQVROH

8QLW�� 2XWSXWV

�


SAP AG 2006

&RQWHQWV�� 0XOWLOLQJXDO�GDWD�� 0XOWLOLQJXDO�GDWD�VWUXFWXUH� 0XOWLOLQJXDO�0'0�*8,V

0'0�0XOWLOLQJXDO�6XSSRUW

�


SAP AG 2006

0'0�0XOWLOLQJXDO�6XSSRUW��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 'HVFULEH�KRZ�0'0�VXSSRUWV�PXOWLSOH�ODQJXDJH�GDWD�

UHFRUGV�� ([SODLQ�PXOWLSOH�ODQJXDJH�VXSSRUW�XVLQJ�WKH�

ODQJXDJH�VHOHFWRU�IRU�0'0�DSSOLFDWLRQV

�


SAP AG 2006

0'0�0XOWLOLQJXDO�6XSSRUW��%XVLQHVV�6FHQDULR

� $V�D�JOREDO�FRPSDQ\��\RX�QHHG�WR�NQRZ�KRZ�6$3�0'0�UHSRVLWRULHV�FDQ�DFFRPPRGDWH�PXOWLSOH�ODQJXDJHV��

�


SAP AG 2006

0XOWLOLQJXDO�'DWD0XOWLOLQJXDO�'DWD�(QWU\�DQG�([SRUW/DQJXDJH�6HOHFWRU6XPPDU\

0XOWLOLQJXDO�'DWD

�


SAP AG 2006

3XUSRVH�RI�0XOWLSOH�/DQJXDJH�6XSSRUW

7KHUH�DUH�WKUHH�PDLQ�DUHDV�WKDW�XWLOL]H�GLIIHUHQW�ODQJXDJHV�� 'DWD�HQWU\��'DWD�LQ�PXOWLSOH�ODQJXDJHV

] $FFHVVLQJ�PXOWLOLQJXDO�GDWD�LQ�RUGHU�WR�SHUIRUP�D�MRE] 0RGLI\LQJ�RU�DGGLQJ�GDWD�GHWDLOV�LQ�GLIIHUHQW�ODQJXDJHV

� 6WUXFWXUH��$YDLODEOH�IRU�DOO�DVVLJQHG�GDWD�ODQJXDJHV] 7DEOH�QDPHV] )LHOG�QDPHV

� 0'0�$SSOLFDWLRQV��'LVSOD\LQJ�GLIIHUHQW�ODQJXDJH] 'DWD�0DQDJHU] ,PSRUW�0DQDJHU] 6\QGLFDWRU] 2WKHU�0'0�&RPSRQHQWV

�


SAP AG 2006

$�W\SLFDO�WDEOH�ZLWK�WKUHH�FRORU�ILHOGV�IRU�WKUHH�ODQJXDJHV

$Q�0'0�WDEOH�ZLWK�WKUHH�ODQJXDJH�OD\HUV

/DQJXDJHV�$YDLODEOH�:KHQ�'LVSOD\LQJ�'DWD

%ODX%OHX%OXH7�6KLUW��*U�Q9HUW*UHHQ7�6KLUW��5RW5RXJH5HG7�6KLUW��&RORU��*HU�&RORU��)UH�&RORU��(QJ�3URGXFW3DUW�1XPEHU

%ODX*U�Q5RW

)DUEH3URGXNW7HLOQHPPHU

%OHX9HUW

5RXJH&RORXU3URGXLW^N_�`[a�bWc\deagf h-ikj a�l�a

mon�prqQs�t

u p n�tRv�w

x tOyZz{ | w

%OXH7�6KLUW��*UHHQ7�6KLUW��5HG7�6KLUW��&RORU�3URGXFW3DUW�1XPEHU

�

� The typical table contains three color fields side by side, one for each language (English, French, and German). These can be used to store the multilingual color data within the table. Unfortunately, the system knows nothing of the relationship among the fields, so it cannot offer the user a language-centric view of the data, and the user has no way of knowing that the fields are related (except that the field names have been tagged with the corresponding language). The field names themselves exist only in English.

� MDM multiple layers efficiently organize and structure both multilingual data and metadata, with a single color field containing multiple data buckets – rather than multiple color fields that are completely unrelated and multiple language-specific field names for all of the fields.


SAP AG 2006

� ,Q�WKH�0'0�&RQVROH��HDFK�UHSRVLWRU\�FDQ�EH�VHW�XS�ZLWK�RQH�RU�PRUH�ODQJXDJHV�

� 3ULPDU\�DQG�VHFRQGDU\�ODQJXDJHV�FDQ�EH�GHWHUPLQHG�

� :KHQ�FUHDWLQJ�GHIDXOW�ILHOGV��WKH\�ZLOO�EH�VKRZQ�LQ�DOO�ODQJXDJHV�WKDW�KDYH�EHHQ�GHVLJQDWHG�IRU�WKDW�UHSRVLWRU\�

/DQJXDJHV�6HOHFWLRQ�LQ�0'0�&RQVROH

�

� Language inheritance is set for each language and is defined by the administrator as the ordering of all the other languages of the repository, split into primary inheritance (for languages whose values are close enough to the current language to be acceptable for publishing), and secondary inheritance (for languages whose values are too different from the current language to be acceptable for publishing, but are perhaps useful during data entry and/or translation). y A ### separates the sets of primary and secondary inheritance languages.

� When a new language is added to the repository, MDM automatically adds the new language to the end of the secondary inheritance for all other languages, places all other languages in the secondary inheritance for the new language, and adds values in the new language for: (a) those tables whose names are fixed (for example, the Images and Families tables); (b) those tables and fields with a default name that has not been changed (for example,the Products and Categories tables, and the Name field in each table); and (c) those Boolean values whose default has not been changed (for example, True and False).

� MDM provides translated menus, table headers, and basic settings for the different languages; however, for the creation of new fields and tables, it does not provide any translations. y Exception: The default Name field is available in all languages.

� When the repository-specific language order changes, MDM immediately refreshes the Console hierarchy with applicable table names based on the new primary language and/or inheritance.


SAP AG 2006

} 'DWD�&RQVROH�VHWXS

} 'DWD�ZLOO�EH�FRORU�FRGHG�] %ODFN��7KH�YDOXH�LV�IURP�WKH�FXUUHQW�ODQJXDJH�] *UHHQ��7KH�YDOXH�LV�IURP�D�SULPDU\�LQKHULWHG�ODQJXDJH�] 0DURRQ��7KH�YDOXH�LV�IURP�D�VHFRQGDU\�LQKHULWHG�ODQJXDJH�

} ([DPSOH�DV�VHHQ�LQ�WKH�0'0�'DWD�0DQDJHU�

'DWD�/DQJXDJH�,QKHULWDQFH

6PDOO(QJOLVK�>86@18//*HUPDQ�>'(@6PDOO(QJOLVK�>86@18//(QJOLVK�>*%@6PDOO�DFWXDO�YDOXH!6PDOO(QJOLVK�>86@'LVSOD\�9DOXH,QKHULW�)URP$FWXDO�9DOXH/DQJXDJH

�

� Primary inheritance is intended for languages that share the same character set as the primary language and where words are spelled the same for the most part, for example, English (US) and English (UK).

� Secondary inheritance is intended for languages that do not share the same character set, for example, English (US) and Chinese (CN).


SAP AG 2006

0XOWLOLQJXDO�6XSSRUW�6XPPDU\

All other properties~ Name~ Alias~ Definition~ Image~ Text Value~ Text Value Image~ Text Value Description

Taxonomy metadata

All other data types�$�Y�� k��1� � ��+� � � � � �R��k�1�

~ Text~ Text Large

� � �\�+��Q�� R��1��

~ Boolean1~ Images~ Text Blocks~ Text HTMLs~ PDFs

Repository data

Repository nameTable nameField name

Repository structure

1RQ�/LQJXDO0XOWLOLQJXDO(OHPHQW&RQVROH�VHWXS

�

� Only certain data types can be defined as multilingual, while objects (that is, images, text blocks, and PDFs) are always multilingual. You can define the applicable data types as multilingual.


SAP AG 2006

0XOWLOLQJXDO�'DWD�(QWU\�DQG�([SRUW


�


SAP AG 2006

� 0DQXDO�HQWU\�YLD�WKH�0'0�'DWD�0DQDJHU�XVLQJ�WKH�/DQJXDJH�'HWDLO WDE

� ,PSRUWLQJ�RI�ODQJXDJHV�YLD�WKH�0'0�,PSRUW�0DQDJHU

0XOWLOLQJXDO�'DWD�(QWU\

�

� Record language support provides multilingual functionality for all text objects. Text fields in records can be stored in multiple languages. MDM does not provide any translations.

� The sequence of the languages displayed is defined in the Console. The first language is always the menu language; the order of the other languages is then derived from the settings in the Console.

� For fields supporting multiple languages, the target language is chosen in the source to target field mapping.


SAP AG 2006

,PSRUW��([SRUW

0'0�'DWD�0DQDJHU�([SRUW

} 0XOWLODQJXDJH�H[SRUW�ODQJXDJH�OD\HU�WDE�IRU�VSHFLILF�ODQJXDJH�H[SRUW�RI�UHFRUGV�DQG�DWWULEXWH�WH[W�YDOXHV�

} 0XOWLODQJXDJH�LPSRUW�WR�LPSRUW�PXOWLODQJXDJH UHFRUG�ILHOG�GDWD�DQG�DWWULEXWH�WH[W�YDOXHV

] 5HODWLRQVKLS�([SRUW�2SWLRQV�GLDORJ�ER[

] $WWULEXWH�7H[W�9DOXH�LPSRUW��H[SRUW

�

� With MDM import and export capabilities, it is possible to select a group of records and export it with all language-relevant texts to Excel, for example, to perform the translation or to check the translation.


SAP AG 2006

/DQJXDJH 6HOHFWRU


�


SAP AG 2006

/DQJXDJH�6HOHFWRU��(IIHFW�RQ�8VHU�,QWHUIDFHV

0'06HUYHU0'06HUYHU

'DWD0DQDJHU'DWD

0DQDJHU,PDJH

0DQDJHU,PDJH

0DQDJHU

3XEOLVKHU3XEOLVKHU ,PSRUW0DQDJHU,PSRUW0DQDJHU


/DQJXDJH�6HOHFWRU/DQJXDJH�6HOHFWRU

�


SAP AG 2006

0'0�/DQJXDJH�6HOHFWRU

� 6HSDUDWH�LQVWDOODWLRQ�XQGHU�*8,B&OLHQWV

� 6KRZQ�LQ�WKLV�OHVVRQ��WKH�ODQJXDJH�VHOHFWHG�LV�UHIOHFWHG�LQ�

] 'DWD�0DQDJHU] ,PSRUW�0DQDJHU] 6\QGLFDWRU

� *HUPDQ�LV�VHOHFWHG

�

� At this printing, 16 languages are supported for the MDM Applications. � Install file: MDMLanguageSelectorInstall.exe


SAP AG 2006

� &RQQHFW�WR�UHSRVLWRU\

� (UURU�PHVVDJHV

/DQJXDJH�6HOHFWRU��(IIHFWV�LQ�'DWD�0DQDJHU�

� 'DWD�0DQDJHU�PHQX

�

� German is the selected language for the MDM applications. � French is the selected data and structure language.


SAP AG 2006

/DQJXDJH�6HOHFWRU��(IIHFWV�LQ�,PSRUW�0DQDJHU�

� &RQQHFW�WR�UHSRVLWRU\� &RQQHFW�WR�VRXUFH

� ,PSRUW�0DQDJHU�PHQX

�



SAP AG 2006

/DQJXDJH�6HOHFWRU��(IIHFWV�LQ�6\QGLFDWRU�

� &RQQHFW�WR�UHSRVLWRU\

� 6\QGLFDWRU PHQX

�



SAP AG 2006

6XPPDU\


�


SAP AG 2006

0'0�0XOWLOLQJXDO�6XSSRUW��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 'HVFULEH�KRZ�0'0�VXSSRUWV�PXOWLSOH�ODQJXDJH�GDWD�

UHFRUGV� ([SODLQ�PXOWLSOH�ODQJXDJH�VXSSRUW�XVLQJ�WKH�

ODQJXDJH�VHOHFWRU�IRU�0'0�DSSOLFDWLRQV

�


�([HUFLVHV�

8QLW�� 0'0�6FHQDULR��0XOWLOLQJXDO�5HSRVLWRU\�7RSLF�� 0'0�0XOWLOLQJXDO�6XSSRUW�


• Describe how MDM supports multiple language data records

• Explain multiple language support using the language selector for MDM applications

As a global company you want to know how MDM can support the use of multiple languages.

�3XUSRVH�This script walks through the process of setting up and importing multilingual data into a repository with English, German, and Spanish languages.


15-1 0DNH�WKH�5HSRVLWRU\�0XOWLOLQJXDO We will now add German and Spanish to your YourLetter_Case_Study repository which by default was originally created in English.


15-1-2 From the list of repositories click on the repository you wish to modify.

15-1-3 In the Repositories Detail pane, activate the drop down selections window by double clicking on the white cell to the right of the Languages row.

15-1-4 Double-click the languages you want to add Spanish [ES] and German [DE].

15-1-5 Click Yes on the Confirm Changes dialog

15-1-6 Next determine which languages will be primary and secondary languages.

The primary languages is the one to the left of the ### and the secondary are to the right. See example below:



15-2 $GG�0XOWLOLQJXDO�7DEOH�DQG�)LHOG�1DPHV Now that the repository has 3 languages, you can add the table and field names for the new languages.

15-2-1 Select your repository from the Console Hierarchy.

15-2-2 Select from the Tables list your Products main table. Notice that there is already a German and Spanish name under the table detail. Whereas for the Pricings table that you created their will be no German or Spanish names.

15-2-3 Now select the Product main table from the Console Hierarchy.

Only text fields have the multilingual property. But not necessarily all text fields should be multilingual. For example, Product ID is a text field, but will always be the same no matter which language you are viewing the data in. A currency or Boolean field which cannot be set to multilingual can have different symbols or values based on the language.

15-2-4 Click on the field, Name. Notice that since this is a default field, it has all languages populated.


15-3 0DQXDOO\�(QWHU�/DQJXDJHV You will now manually enter German and Spanish words.

15-3-1 Open Data Manager and log in to your Case_Study repository.

15-3-2 Select record with the Product ID = 100

15-3-3 Switch to the Language Detail tab.

15-3-4 For German type in Geschirrspuler. Why did the color of the text change

from maroon to black?

15-3-5 Shift+Enter to save your changes.

15-3-6 Keep the Data Manager open as you will return later in this exercise.

15-4 ,PSRUW�/DQJXDJHV By using the Import Manager, all language fields can be can be populated at the same time as the rest of your data. In this part of the exercise we will only be adding the new languages.

15-4-1 Open the Import Manager and select YourLetter_Case_Study repository.

15-4-2 Set Connect to Source to: Remote system = NewYork File name = Case_Study_Languages.xls


15-4-3 Select your source: ,WHP�ZLWK�/DQJXDJHV� and destination: 3URGXFWV. 15-4-4 Switch to tab strip Notice that on the right side you

have 3 entries for Names.


15-4-5 Map the following names: Item to Name [DF] Item-German to Name [DF] Item-Spanish to Nombre [DF] ID to Product ID [DF]

15-4-6 Switch to the tab

15-4-7 Select Product ID and click $GG.

15-4-8 Set Default Action for 8 of 8 to 8SGDWH��18//�)LHOGV�2QO\�.

15-4-9 Switch to the tab

15-4-10 ([HFXWH

15-5 5HVXOWV Switch to the Data Manager.

15-5-1 Select F5 (Function 5 key of your key board) to refresh the data.

15-5-2 Select the record with Product ID = 100. The result should look like below.

Notice how even special characters (like ä) were imported in for Product 103.

15-5-3 Now close the Data Manager and log back in with the Language = German [DE].

15-5-4 Go to records with Product ID = 100 and you will see that Name is now

Geschirrspuler and the Product table is now Produkte


SAP AG 2006

8QLW��/DQGVFDSH��6HFXULW\�DQG�3HUPLVVLRQV





3HUIRUPDQFH




�


SAP AG 2006

&RQWHQWV�� 5HSRVLWRU\�VHFXULW\�DQG�XVHU�PDQDJHPHQW� &RQVROH�VHFXULW\

0'0�6HFXULW\�DQG�8VHU�0DQDJHPHQW

�


SAP AG 2006

0'0�6HFXULW\�DQG�8VHU�0DQDJHPHQW��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 'HILQH�DQG�PDLQWDLQ�0'0�UROHV�DQG�XVHUV� 0RQLWRU�0'0�/RJRQV� 'HILQH�FKDQJH�WUDFNLQJ

�


SAP AG 2006

0'0�6HFXULW\�DQG�8VHU�0DQDJHPHQW��%XVLQHVV�6FHQDULR

� 7R�SUHVHUYH�WKH�GDWD�LQWHJULW\�RI�\RXU�PDVWHU�GDWD��\RX�ZDQW�WR�OHDUQ�DERXW�WKH�RSWLRQV�IRU�VHFXULW\�DQG�XVHU�PDQDJHPHQW�LQ�6$3�0'0��

�


SAP AG 2006

6XPPDU\

&KDQJH�7UDFNLQJ0'0�&RQVROH�6HFXULW\

2YHUYLHZ6HFXULW\�DQG�8VHU�0DQDJHPHQW

5ROHV8VHUV/RJRQV

0'0�6HFXULW\�DQG�8VHU�0DQDJHPHQW��2YHUYLHZ

�


SAP AG 2006

0'0�6HFXULW\�DQG�8VHU�0DQDJHPHQW��&RPSRQHQWV

0'0�VXSSRUWV�D�IOH[LEOH��PXOWLGLPHQVLRQDO�VHFXULW\�VFKHPH�WKDW�SURYLGHV�PRUH�JUDQXODU�FRQWURO�RYHU�ZKLFK�XVHUV�FDQ�DFFHVV�DQ�0'0�UHSRVLWRU\��ZKLFK�IXQFWLRQV�WKH\�FDQ�SHUIRUP��DQG�ZKLFK�WDEOHV��ILHOGV��DQG�UHFRUGV�WKH\�FDQ�DFFHVV�

2YHUYLHZ 0'0�6HFXULW\�DQG�8VHU�$GPLQLVWUDWLRQ�LV�PDLQWDLQHG�LQ�WKH�0'0�&RQVROH��SHU�UHSRVLWRU\��XQGHU�WKH�$GPLQ�QRGH�)RXU�0'0�WDEOHV�DUH�XWLOL]HG�IRU�0'0�6HFXULW\�DQG�8VHU�$GPLQLVWUDWLRQ�� 5ROHV�� 8VHUV�� /RJLQV�� &KDQJH�7UDFNLQJ

�

� MDM Security and User Administration is maintained in the MDM Console, per repository, under the Admin node.

� Four MDM tables are utilized for MDM Security and User Administration: Roles, Users, Logins and Change Tracking. These tables are part of the MDM System tables. They are situated under the Admin node and generated by the system upon creation of a repository. These tables cannot be deleted.

� A traditional SQL DBMS allows you to define basic user-level security to prevent unauthorized access to the database. You can specify the tables to which each user has access, granting at the table level either: y No access to the table y Complete read/write access to the table, including access to all of its fields and records

� By contrast, MDM supports a more flexible, multidimensional security scheme that provides more granular control over which users can access an MDM repository, which functions they can perform, and which tables, fields, and records they can access.

� The MDM security scheme is configured in the MDM Console and includes the following components: y Users y Roles

- Privileges - Constraints

y Logons y Change tracking y Password access to the MDM Console


SAP AG 2006

6XPPDU\



5ROHV8VHUV/RJRQV

6HFXULW\�DQG�8VHU�0DQDJHPHQW��5ROHV

�


SAP AG 2006

0'0�UROHV�DUH�DGGHG�DV�UHFRUGV�WR�WKH�5ROHV�WDEOH��

)RU�HDFK�UROH�DGGHG��GHILQH�SULYLOHJHV�DQG�FRQVWUDLQWV�XVLQJ�WKH�IROORZLQJ�WDEV�

�� 5ROH�'HWDLO�� )XQFWLRQV�� 7DEOHV��)LHOGV�

$�UROH�KDV�WKH�IROORZLQJ�SURSHUWLHV�

�� 1DPH��7KH�UROH�QDPH�� 'HVFULSWLRQ��$�GHVFULSWLRQ�RI�

WKH�UROH�� 8VHUV��7KH�OLVW�RI�XVHUV�

DVVRFLDWHG�ZLWK�WKH�UROH

5ROHV

5ROHV

�

� Each role specifies a set of privileges to access each of the repository’s tables, fields, lookup record values, and records, and to perform each of the repository functions. The same role can be assigned to more than one user.

� The Roles table is an MDM system table with a predefined set of fields and records that appear in the Roles pane of the MDM Console.

� Each record you add to the Roles table in the MDM Console defines a particular role. For each role added, you define privileges, and constraints using the Role Detail, Functions, and Tables & Fields tabs.

� When you first create a new MDM repository, MDM automatically creates: y The Roles table (as a child of the Admin node of the Console hierarchy tree) y A role named Admin that cannot be deleted and has all privileges and no constraints y A role named Everyone that cannot be edited or deleted, has administrator-defined privileges and

constraints, and is automatically held by every MDM user on the system


SAP AG 2006

)XQFWLRQV

7KH�IXQFWLRQDO�SULYLOHJHV�IRU�D�UROH�DUH�GHILQHG�LQ�WKH�)XQFWLRQV WDE�)XQFWLRQ�SULYLOHJHV�DUH�DVVRFLDWHG�ZLWK�D�OHDI�QRGH�LQ�WKH�KLHUDUFK\�LQ�WKH�1DPHFROXPQ�)RU�HDFK�IXQFWLRQ��\RX�FDQ�VHOHFW�DFFHVV�VHWWLQJV��VSHFLI\LQJ�ZKHWKHU�WKH�IXQFWLRQ�FDQ�EH�H[HFXWHG�E\�WKH�UROH�

�

� For each repository function, you can either prevent or allow the role to perform the function. � The functional privileges for a role are displayed in a hierarchy in the Name column in a grid within

the Functions tab. Each of the functions is associated with a leaf node in the hierarchy, and are organized into groups using the internal nodes. For each function, you can specify either of the following access settings by selecting from the radio button grid control in the Access column: y Execute: The function can be executed y None: The function cannot be executed

� The setting of the root node of the Functions hierarchy determines the default privilege for new functions that are added to updated versions of the MDM software.

� You can change all functions to the same setting, as a group, by changing the default setting of the root node. MDM prompts you to confirm that you want to change the access settings for all functions to the new default.


SAP AG 2006

7DEOHV�DQG�)LHOGV

7DEOH�DQG�ILHOG�SULYLOHJHV�IRU�D�UROH�DUH�GHILQHG�LQ�WKH�7DEOHV�DQG�)LHOGV WDE�7DEOH�DQG�ILHOG�SULYLOHJHV�DUH�DVVRFLDWHG�ZLWK�D�OHDI�QRGH�LQ�WKH�KLHUDUFK\�LQ�WKH�1DPHFROXPQ��)RU�HDFK�WDEOH�DQG�ILHOG��\RX�FDQ�VHOHFW�DFFHVV�VHWWLQJV��VSHFLI\LQJ�ZKHWKHU�WKH�WDEOH�DQG�ILHOG�LV�5HDG�2QO\�RU�5HDG�:ULWH�

�

� For each table and field, you can grant the role full read/write access or read-only access. � The table and field privileges for a role are displayed in a hierarchy in the Name column in a grid

within the Tables and Fields tab. � Each normal table is represented by an internal node, and each of its fields by a leaf node. For each

field, you can specify any of the following access settings by selecting from the radio button grid control in the Access column: y Read/Write: The field value can be read and written y Read-Only: The field value can be read but cannot be written

� The setting of the root node of the Tables and Fields hierarchy determines the default privilege for new tables added to the MDM repository. Similarly, for normal tables, the setting for each table node determines the default privilege for new fields added to the table. Finally, the setting for each field node determines the actual access level for the field.

� You can change all the tables and fields to the same setting as a group by changing the default setting of the root node. MDM prompts you to confirm that you want to change the access settings for all tables and fields to the new default.


SAP AG 2006

7DEOHV�DQG�)LHOGV�� &RQVWUDLQWV

7KH�UROH�ZLOO�RQO\�VHH�UHFRUGV�IURP�WKH�VHOHFWHG�FDWHJRULHV

7KH�UHFRUG�FRQVWUDLQWV�IRU�D�UROH�DUH�GHILQHG�LQ�WKH�7DEOHV�DQG�)LHOGV WDE�5HFRUG�FRQVWUDLQWV�DOORZ�\RX�WR�FUHDWH�YLUWXDO�VXEVHW�UHSRVLWRULHV�SHU�UROH��7KHVH�VXEVHWV�DUH�G\QDPLF� EDVHG�RQ�VHOHFWLRQV�RI�PDVNV�DQG�RU�ORRNXS�WDEOH�YDOXHV��2QO\�PDLQ�WDEOH�UHFRUGV�WKDW�IDOO�ZLWKLQ�WKH�FRQVWUDLQHG�UHFRUG�VHW�ZLOO�EH�YLVLEOH�WR�WKH�UROH�

�

� The record constraints for a role are displayed in the Constraints column of the grid within the Tables and Fields tab.

� Record constraints are selections of masks and/or other lookup table records that allow you to create virtual subset repositories on a per-role basis. These subsets are dynamic in that they can be based not only on masks but also on lookup values. Only main table records that fall within the constrained record set will ever be visible or known to the role.

� For the Masks table and for each lookup table that is referenced by at least one single-valued lookup field and no multi-valued lookup fields, you can specify constraints by selecting which masks or lookup values – and therefore which main table records – should be visible and accessible for the role. For each table for which you can assign constraints, the value in the Constraints column is as follows: y [ALL]: Table not constrained y [n]: Table constrained to include ‘n’ selected records

� You cannot manually create the [0] case (that is, ‘n’ equals 0), which sometimes occurs if all the records to which a role is constrained are replaced or deleted. This prevents the role from gaining full access to the entire set of records in the table. Also, if the role has access to all replaced records, it will have access to all replacement records. You add constraints by selecting one or more values from the dropdown control for multiple-item selection in the Constraints column.


SAP AG 2006

5ROH�6XPPDU\

)RU�D�UROH�WR�SHUIRUP�DQ�RSHUDWLRQ�LQ�0'0��WKH\�PXVW�KDYH�� )XQFWLRQDO�DFFHVV� 'HIDXOW�LV�([HFXWH� )LHOG�DQG�WDEOH�DFFHVV� 'HIDXOW�LV�5HDG�:ULWH� &RQVWUDLQWV� $FFHVV�WR�WKH�GHILQHG�UHFRUG)RU�H[DPSOH��WR�DGG�DQ�LPDJH�WR�DQ�0'0�UHSRVLWRU\��\RX�PXVW�

KDYH�$GG�5HFRUGV�IXQFWLRQDO�DFFHVV�DQG�:ULWH�DFFHVV�WR�WKH�,PDJHV�WDEOH��+DYLQJ�RQO\�RQH�RI�WKHVH�ULJKWV�LV�LQVXIILFLHQW�

�

� The access settings in the Functions tab control the rights to execute a given function (the functions roughly correspond to the menu options of the MDM Data Manager). Similarly, the access settings in the Tables and Fields tab control rights to each of the tables and fields. This includes the main table, lookup tables, object tables (Images, Text Blocks, PDFs, etc.), the Masks table, the Families table, and publications. To perform an operation, you must have both functional access (the ability to perform the given function), object access (the ability to read/write the object(s) on which the operation is being performed), and record access (pursuant to the record constraints).

� For example, to add an image to an MDM repository, you must have Add Records functional access and Write access to the Images table. Having only one of those rights is insufficient.

� When a user belongs to multiple roles, MDM separately calculates the rights for each role – based on the functional privileges, the object privileges, and the record constraints – and then combines the rights of those roles with an OR.


SAP AG 2006

6XPPDU\



5ROHV8VHUV/RJRQV

6HFXULW\�DQG�8VHU�0DQDJHPHQW��8VHUV

�


SAP AG 2006

8VHUV

8VHUV

0'0�XVHUV�DUH�DGGHG�DV�UHFRUGV�WR�WKH�8VHUV�WDEOH��$�XVHU�KDV�WKH�IROORZLQJ�SURSHUWLHV�GHILQHG�LQ�WKH�8VHU�'HWDLO WDE�� 1DPH��7KH�XVHU�QDPH�� )XOO�1DPH��7KH�IXOO�QDPH�RI��

WKH�XVHU�� 'HVFULSWLRQ��$�GHVFULSWLRQ�RI�

WKH�XVHU� � 3DVVZRUG��7KH�XVHU�SDVVZRUG�

�GLVSOD\HG�DV�³ ´� � 5ROHV��7KH�OLVW�RI�UROHV�

DVVRFLDWHG�ZLWK�WKH�XVHU�� (PDLO�$GGUHVV��7KH�H�PDLO�

DGGUHVV�RI�WKH�XVHU��IRU�ZRUNIORZ�QRWLILFDWLRQV�

�

� Users represent an entity that can log on to and access the repository. A user has a user name and password. A user is assigned to one or more roles that collectively specify the complete set of privileges for that particular user.

� The Users table is an MDM system table with a predefined set of fields and records that appear in the top-right Users pane of the MDM Console. Each record that you add in the MDM Console defines a particular user who has access to the MDM Repository, along with the roles associated with that user.

� When you first create a new MDM repository, MDM automatically creates: y The Users table (as a child of the Admin node of the Console hierarchy tree); y A user named Admin that cannot be deleted, with no password, that is assigned to the Admin role

� The properties for each user are directly editable in the User Detail pane. � The functions to create or remove a user from the repository are accessible via the context menu in

the Users section of the screen. � User details cannot be changed while the repository is loaded.


SAP AG 2006

8VHU�'HWDLO�² $VVLJQLQJ�5ROHV

� ,Q�WKH�8VHU�'HWDLO�VHFWLRQ�RI�WKH�VFUHHQ��\RX�FDQ�DVVLJQ�RQH�RU�PXOWLSOH�UROHV�WR�WKH�XVHU�

� <RX�FDQ�VHOHFW�ZKLFK�UROH�V��WR�DVVLJQ�WR�HDFK�XVHU�IURP�WKH�SUHGHILQHG�DYDLODEOH�UROHV�

� 7KH�VHOHFWHG�UROH�V��ZLOO�DSSHDU�LQ�WKH�6HOHFWHG�UROHV�SDQH�

�

� In the User Detail section of the screen, you can assign one or multiple roles to the selected user. � You can select which role(s) to assign to each user from the predefined available roles. � The selected role(s) will appear in the Selected Roles pane.


SAP AG 2006

6XPPDU\



5ROHV8VHUV/RJRQV

6HFXULW\�DQG�8VHU�0DQDJHPHQW��/RJRQV

�


SAP AG 2006

/RJRQV

/RJJHG�LQ�8VHUV

1RQH of the properties are directly editable in the /RJLQ�'HWDLO pane, which is read-only.

0'0�ORJJHG�RQ�XVHUV�DUH�ORJJHG�RQ�WR�WKH�/RJLQV�WDEOH��7KLV�HQDEOHV�PRQLWRULQJ�RI�FRQQHFWLRQ�DFWLYLW\�0'0�ORJV�WKH�IROORZLQJ�LQIRUPDWLRQ�LQ�WKH�/RJLQ�'HWDLOWDE�� 1DPH��7KH�XVHU�QDPH�� +RVW�1DPH��7KH�V\VWHP�RQ�

ZKLFK�0'0�LV�UXQQLQJ�� $SSOLFDWLRQ�1DPH��7KH�0'0�

DSSOLFDWLRQ��H�J��'DWD�0DQDJHU�� /RJLQ�7LPH��7KH�GDWH�DQG�WLPH�

WKH�FRQQHFWLRQ�ZDV�HVWDEOLVKHG � /DVW�$FWLYLW\�7LPH��7KH�GDWH�

DQG�WLPH�WKH�FRQQHFWLRQ�ZDV�ODVW�DFFHVVHG

�

� The Logins table is an MDM system table with a predefined set of fields and records that appear in the top-right /RJLQV pane of the MDM Console. Each record that MDM maintains corresponds to a currently connected MDM client application, along with the connection time and time since last access, allowing you to monitor connection activity.

� Entries will be shown as long as the user is logged on to an MDM application. No history of user logons is available!

� None of the properties are directly editable in the /RJLQ�'HWDLO pane, which is read-only. � By default, the MDM Console automatically updates the logon information in the /RJLQV pane

every 60 seconds. You can edit the Refresh Rate Æ Login Status node in the &RQILJXUDWLRQ�2SWLRQV dialog to change how often this update occurs.

� You can press )� to update the logon information in the /RJLQV pane immediately.


SAP AG 2006

6XPPDU\



5ROHV8VHUV/RJRQV

6HFXULW\�DQG�8VHU�0DQDJHPHQW��&KDQJH�7UDFNLQJ

�


SAP AG 2006

&KDQJH�7UDFNLQJ

Change tracking information LV�QRW�GLUHFWO\�YLVLEOH in MDM. Change tracking can be reported using an In-database (for example, via third-party SQL reporting tool) or extracted to a data warehouse (for example, BI).

� &KDQJH�WUDFNLQJ�IXQFWLRQDOLW\�FDQ�EH�DFWLYDWHG�RQO\�E\�DQ�DGPLQLVWUDWRU��

� %\�GHIDXOW��FKDQJH�WUDFNLQJ�LV�WXUQHG�RII��ZKLFK�PHDQV�QR�WUDFNLQJ�LV�DFWLYDWHG�

� &KDQJH�WUDFNLQJ�LV�GHILQHG�LQ�WKH�&KDQJH�7UDFNLQJ�WDEOH�

� &KDQJH�WUDFNLQJ�FDQ�EH�GHILQHG�IRU�WKH�WDEOHV�DQG�ILHOGV�GLVSOD\HG�LQ�WKH�KLHUDUFK\�LQ�WKH�1DPH�FROXPQ�

� &KDQJH�WUDFNLQJ�FDQ�EH�FUHDWHG�XSRQ�DGGLQJ��PRGLI\LQJ��RU�GHOHWLQJ�D�UHFRUG�

� &KDQJH�WUDFNLQJ�VWRUHV�WKH�GDWH��WKH�WLPH��WKH�XVHU��WKH�ROG�YDOXH��DQG�WKH�QHZ�YDOXH�RI�WKH�FKDQJH�

�

� The Change Tracking table is an MDM system table with a predefined set of fields and records that are not directly visible in either the MDM Console or the MDM Data Manager. Each record is created automatically by MDM when the value of any field that you are tracking is changed.

� For each change, MDM records the date, the time, the user who made the change, the old value, and the new value. The change tracking settings for the tables and fields are displayed in a hierarchy in the Name column in a grid within the Change Tracking Settings pane. For each field, you can specify whether to track changes of the following types by selecting from the radio button grid control in the corresponding column: y Track Adds: Track new field value when a record is added y Track Modifies: Track old and new values when the field is modified y Track Deletes: Track old field value when a record is deleted

� For each type of change you can track, the setting of the root node of the Tables and Fields hierarchy determines the default setting for new tables added to the MDM repository. Similarly, for normal tables, the setting for each table node determines the default setting for new fields added to the table. Finally, the setting for each field node determines the actual setting for the field.

� The list of fields includes the following virtual fields: (1) field [Attributes] in the main table, which you can use to track changes to the attribute values of a taxonomy lookup field; and (2) [Attributes] in a taxonomy table, which you can use to track the addition of new attributes, the deletion of existing attributes, and changes to the attribute name.

� You can only change the settings for the Change Tracking table for an MDM repository that is mounted and unloaded.

� You can change all the tables and fields to the same setting as a group by changing the default setting of the root node.

� &DXWLRQ: Enabling change tracking can dramatically degrade MDM system performance when records are modified.


SAP AG 2006

6XPPDU\



5ROHV8VHUV/RJRQV

0'0�&RQVROH�6HFXULW\

�


SAP AG 2006

0'0�&RQVROH�6HFXULW\��6HUYHU

A user with access to the MDM Console has access to all connected MDM servers and their repositories. For example, a user can change security settings for repositories or delete full repositories!

$�SDVVZRUG�FDQ�EH�VHW�IRU�WKH�VHUYHU�YLD�WKH�VHUYHU¶V�FRQWH[W�PHQX�LQ�WKH�0'0�&RQVROH�7KH�VHUYHU�FDQ�WKHQ�EH�PRXQWHG�EXW�WKH�SDVVZRUG�LV�UHTXLUHG�WR�VWDUW�WKH�VHUYHU�

�

� To enable password protection for an unprotected MDM Server or to change your existing MDM Server password: y In the Console Hierarchy tree, right-click on the MDM server whose password you want to set or

reset and choose Change Password from the context menu. Alternately, select the tree node and choose MDM Servers Æ Change Password from the main menu.

y MDM opens the Change Password for MDM Server dialog and prompts you to enter the old password (if one exists) and the new password. Type the old password, type the new password, type the new password again for confirmation, and click OK.

� 1RWH: If the top-right pane is currently displaying the list of MDM servers, you can also right-click on the MDM server in the grid and choose Change Password from the context menu.


SAP AG 2006

0'0�&RQVROH�6HFXULW\�YLD�WKH�2SHUDWLQJ�6\VWHP

6HWWLQJ�0'6�6FRQH WR�HPSW\�GHOHWHV�WKH�SDVVZRUG�IRU�WKH�0'0�6HUYHU�

7KH�RSHUDWLQJ�V\VWHP��IRU�H[DPSOH��:LQGRZV�6HUYHU��$GYDQFHG�/LQX[��PXVW�FRQWURO�DFFHVV�WR�WKH�DSSOLFDWLRQ�YLD�RSHUDWLQJ�V\VWHP�XVHU�PDQDJHPHQW�7KH�RSHUDWLQJ�V\VWHP�PXVW�UHVWULFW�DFFHVV�WR�WKH�0'0�6HUYHU�GLUHFWRU\�DQG�RU�WR�LPSRUWDQW�ILOHV��HVSHFLDOO\�WR�PGV�LQL �� 1RWH��%\�FKDQJLQJ�WKH�PGP�LQL ILOH�LQ�WKH�0'0�VHUYHU�GLUHFWRU\��H�J��

*��3URJUDP�)LOHV��6$3�0'0��6HUYHU��WKH�SDVVZRUG�IRU�WKH�WKH6$3�0'0�VHUYHU�FDQ�EH�HDVLO\�GHOHWHG�

�


SAP AG 2006

6XPPDU\



5ROHV8VHUV/RJRQV

6XPPDU\

�


SAP AG 2006

6XPPDU\

� 6$3�0'0�XVHV�UHSRVLWRU\�EDVHG�VHFXULW\�DQG�XVHU�PDQDJHPHQW�

� $FFHVV�LV�RUJDQL]HG�YLD�UROHV�ZLWK�SULYLOHJHV�DQG�FRQVWUDLQWV�RQ�IXQFWLRQV�DQG�ILHOG�OHYHO�DFFHVV�IRU�HDFK�UHSRVLWRU\�

� 5ROH�GHVLJQ�KDV�WR�EH�SODQQHG�DSSURSULDWHO\��GXH�WR�WKH�OLQNDJH�EHWZHHQ�WDEOH�DQG�ILHOG�DFFHVV�DQG�FRUUHVSRQGLQJ�IXQFWLRQDOLWLHV��

� $FWXDO�ORJRQ�VWDWXV�IRU�HDFK�UHSRVLWRU\�FDQ�EH�PRQLWRUHG�� 1R�UHFRUGV�DUH�NHSW�RQ�XVHU�DFWLYLWLHV��H[FHSW�FKDQJH�KLVWRU\�� $FFHVV�WR�0'0�VHUYHUV�DQG�PDQDJHPHQW�YLD�WKH�0'0�

&RQVROH�KDV�WR�EH�SURWHFW�E\�WKH�XQGHUO\LQJ�RSHUDWLQJ�V\VWHP�� &RPPXQLFDWLRQ�EHWZHHQ�WKH�0'0�6HUYHU�DQG�PRGXOHV�LV�QRW�

SURWHFWHG�

�


SAP AG 2006

0'0�6HFXULW\��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 'HILQH�DQG�PDLQWDLQ�0'0�UROHV�DQG�XVHUV� 0RQLWRU�0'0�/RJRQV� 'HILQH�FKDQJH�WUDFNLQJ

�


�([HUFLVHV�

8QLW�� 0'0�6HFXULW\�([HUFLVH��7RSLF�� &UHDWLQJ�5ROHV�DQG�8VHUV��


• Create users within your MDM repository

• Create roles to provided limited access to functions and data within your repository

• Assign roles to users

To preserve the data integrity of your master data you want to be able to create users with limited access to your repository.

�3XUSRVH�This exercise allows you to limit users’ permissions within the MDM Data Manager. You will set the security using the SAP MDM Console.

The business scenario is as follows:

• You want to restrict the end user to avoid accidental deletion of records in your Case_Study Repository

• You want to limit the records that the user can see based on the Category.

3UHUHTXLVLWHV�• MDM Repository has been created

• MDM Repository has been loaded

�


16-1 6WDUW�WKH�6$3�0'0�&RQVROH

In the MDM Console, you will define roles, set permissions, and assign users to the roles.

16-1-1 Start the SAP MDM Console and open your Yourletter_Case_Study repository.

16-1-2 Make sure your repository is unloaded.

16-1-3 Expand the “Admin” node in your Yourletter_Case_Study repository.

16-2 'HILQH�D�5ROH

Create a role with the following information: Role Name: Enduser_Role Description: Role with limited permissions Users: You can leave it blank for now.

16-2-1 In the SAP MDM Console under the <RXUOHWWHUB&DVHB6WXG\ Repository, expand “Admin” node and highlight “Roles”.

16-2-2 Right mouse click at the right upper Roles pane and select “Add Role”.

16-2-3 At the bottom right pane, click on “Role Detail” Tab, if not highlighted > enter the name: Enduser_Role and description. You can leave the ‘Users’ field blank for now. You will populate this field once you have created a new user

16-2-4 Shift+Enter to save your work.


16-3 'HILQH�3ULYLOHJHV In this step, you will define the privileges for the Enduser_Role

Allow the following privileges for your Enduser_Role:

Records: Disallow “ Delete“

Hierarchy: Allow access to only some nodes

16-3-1 Continue from step 16-2-3, click the “ Functions” Tab.

Select “ None” for “ Records > Delete Records”

Select “ None” for “ Hierarchies > Move Nodes within Hierarchy”

16-3-2 You can choose to further limit the permission by going to the Tables and Fields tab and limiting what fields can be written to.



16-4 'HILQH�&RQVWUDLQW�DW�)LHOG�/HYHO In this step, you will define the constraints for the ENDUSER_Role to limit access to only three category leaf nodes.

16-4-1 Click the Tables and Fields tab.

16-4-2 At the Categories open the drop down in the Constraints column where you see [ALL].

16-4-3 Select the following available values: Accessory > Small > House > Bathroom Appliance > Large > Portable Appliance > Small > House > Bathroom

16-4-4 Double-click to move the values to the right.



16-5 &UHDWH�D�8VHU

In this step, you will create a user to be assigned to the Enduser_Role that you created previously.

16-5-1 Expand the “ Admin” tab under the <RXUOHWWHUB&DVHB6WXG\ Repository.

16-5-2 Select “ Users” sub-node.

16-5-3 In the “ Users” pane, right mouse click and select $GG�8VHU. 16-5-4 In the User Detail pane, enter the following:

Name = Enduser01 Description = End User tester 01 Password = training Roles = Enduser_Role

16-5-5 Shift+Enter to save your work

16-6 7HVW�WKH�5HVXOW You will now test your new users by logging on to the SAP MDM Data Manager.

16-6-1 Logon to the SAP MDM Data Manager with Enduser01.

16-6-2 In Record Mode, attempt to delete a record

16-6-3 You will be asked “ You are about to delete 1 record.” Click OK.

16-6-4 You will get the Error Deleting Record “ Insufficient rights for operation.”

16-6-5 Next switch to Hierarchy Mode and make sure the Categories table is

selected.

16-6-6 You will only see the nodes Accessory and Appliance. Click and drag Appliance to the Categories node.

16-6-7 Insert as Child.

16-6-8 You will get the Error Moving Tree Item.


SAP AG 2006






3HUIRUPDQFH




�


SAP AG 2006

&RQWHQWV�� 0'0�,QWHJUDWLRQ�ZLWK�D�'LUHFWRU\�6HUYHU


�

�

�


SAP AG 2006

'LUHFWRU\�6HUYHU�,QWHJUDWLRQ��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 'HVFULEH�WKH�LQWHJUDWLRQ�RI�'LUHFWRU\�6HUYHUV��XVLQJ�

/'$3��ZLWK�0'0�6HFXULW\� 'HVFULEH�KRZ�D�'LUHFWRU\�6HUYHU�FDQ�IDFLOLWDWH�0'0�

6HFXULW\

�


SAP AG 2006

'LUHFWRU\�6HUYHU�,QWHJUDWLRQ��%XVLQHVV�6FHQDULR

� 7R�SUHVHUYH�WKH�GDWD�LQWHJULW\�RI�\RXU�PDVWHU�GDWD��\RX�ZDQW�WR�OHDUQ�DERXW�WKH�RSWLRQV�IRU�VHFXULW\�XVLQJ�D�GLUHFWRU\�VHUYHU�ZLWK�0'0��

�


SAP AG 2006

3URSHUWLHV�RI�'LUHFWRU\�6HUYHUV

� 'LUHFWRU\�6HUYHUV DFW DV�D�FHQWUDO GHSRVLWRU\ IRU GDWD WKDW LVXVHG E\ YDULRXV DSSOLFDWLRQV�

� 7\SLFDOO\��LQIRUPDWLRQ�DERXW�XVHUV��GRFXPHQWV��RU�KDUGZDUH�UHVRXUFHV�LV�VWRUHG�± KRZHYHU��DQ\�RWKHU�REMHFWV�FRXOG�DOVR�EH�VWRUHG�

� 7KH�GLUHFWRU\�VHUYHU�LV�DFFHVVHG�XVLQJ�D�VWDQGDUGL]HG�SURWRFRO��VXFK�DV�/'$3��/LJKWZHLJKW�'LUHFWRU\�$FFHVV�3URWRFRO��;��'$3��'LUHFWRU\�$FFHVV�3URWRFRO��RU�'60/��'LUHFWRU\�6HUYLFHV�0DUNXS�/DQJXDJH��

�

� Simply put, a directory server is a sort of database that allows a company to control, configure and distribute user privileges, rights, and access from a single location.

� Without a directory server, the system manager is forced to maintain familiarity with the proprietary access control mechanism offered by each software product, and to use each one to separately maintain access control information every time an employee is hired, moves, changes job within the organization, and so on.

� Imagine a company with thousands of employees and dozens of programs requiring access control, and it becomes clear how much of a burden it can be to manage access control without a directory server.

� By contrast, by using MDM in conjunction with a directory server, MDM customers can manage access control information in a single location with a common, familiar interface of their choosing.

� Lightweight Directory Access Protocol (LDAP) is the most common protocol used to connect to a directory server. In fact in many cases the terms directory server and LDAP are often used interchangeably.


SAP AG 2006

([DPSOH�6FHQDULR�ZLWK�D�'LUHFWRU\�6HUYLFH

��

��! �"$#&%�')(�*�+�",�.-

/10,2 3#&4

5 �64 �6��7.81%��:9<;= �>

�?"$7��6�@ �3�64A#AB� :"C# 8D%�+

( @?E (�*�+�"!�.-F+

G�H�I�JLK�MON�PQ�R3S3Q.T PVU

W�XZY Q�[M Q ML\ W�X�Y ]_^

+�*�+�",�3-

( @�E/ %�",��C�6�C# +��E 8D�=", �4

( @`Ea �6b @ (

c P�Med [ K Tf.UOP [XDg:h`i M i ULd [ Ked i Q M

�

� LDAP acts as a lookup into a directory, very similar to using a telephone book. For example, you can perform a general search, such as one that returns all instances of “ Mary Lamb.” In BigFoot, this returns 100+ records in the United States. Or you can restrict the search by adding “ in California” to the search, which then returns 6 records.

� It turns out that the BigFoot search engine is based on an LDAP directory that includes “ Name” and “ State” lookup categories. Owners of LDAP directories can retrieve additional fields, categories, or attributes, such as “ Telephone Numbers,” “ Primary Automobile,” “ Hair Color,” or “ MDM User Type.” This additional information can be used as well for additional selection criteria.

� For MDM to support LDAP, SAP has designated the information that MDM will be querying from and that must be entered and maintained within the customer’ s LDAP database/directory.

� Using LDAP within MDM conforms to the following guidelines: y The customer is responsible for the maintenance and design of their LDAP directory. They must

inform MDM of several LDAP directory fields and attributes so that MDM can properly search for user information. Unless an existing field is used, the customer must create one attribute field (named as desired) for MDM use.

y The MDM software adds no records to the LDAP directory, nor does it otherwise manage or make any design changes to its structure. It only performs “ lookups” from the LDAP directory to read its contents.

y Single sign-on is not supported. Instead, MDM client software prompts the user for name and password. It was done this way for simplicity, interoperability with UNIX systems, and flexibility with various client programs or network configurations such as VPNs.


SAP AG 2006

6$3�0'0�DQG�/'$3

:K\�'LUHFWRU\�6HUYHU"�� 8VLQJ�6$3�0'0�LQ�FRQMXQFWLRQ�ZLWK�'LUHFWRU\�6HUYHU��'6��

0'0�FXVWRPHUV�FDQ�PDQDJH�DFFHVV�FRQWURO�LQIRUPDWLRQ�LQ�D�VLQJOH�ORFDWLRQ�ZLWK�D�FRPPRQ��IDPLOLDU�LQWHUIDFH�RI�WKHLU�FKRLFH�

+RZ�GRHV�/'$3�:RUN"/'$3�DFWV�DV�D�ORRNXS�LQWR�D�GLUHFWRU\�� 3HUIRUP�D�JHQHUDO�VHDUFK�� 5HVWULFW�WKH�VHDUFK�E\�DGGLQJ�PDVNV�WR�WKH�VHDUFK)RU�0'0�WR�VXSSRUW�'6��6$3�KDV�GHVLJQDWHG�WKH�LQIRUPDWLRQ�

WKDW�0'0�ZLOO�EH�TXHU\LQJ�IURP�DQG�WKDW�PXVW�EH�HQWHUHG�DQG�PDLQWDLQHG�ZLWKLQ�WKH�FXVWRPHU¶V�'6�GDWDEDVH�GLUHFWRU\�

�

� LDAP (Lightweight Directory Access Protocol) within the SAP MDM system


SAP AG 2006

/'$3�² /LJKWZHLJKW�'LUHFWRU\�$FFHVV�3URWRFRO

� 6$3�0'0�UHTXLUHV�MXVW�RQH�DGGLWLRQDO�ILHOG�RQ�DQ�/'$3�'LUHFWRU\�6HUYHU��0'05ROHV

� PGV�LQL PXVW�EH�FXVWRPL]HG�ZLWK�DQ�/'$3�VHFWLRQ�WR�HQDEOH�XVH�RI�WKH�VHUYLFH�

� ,Q�FDVH�RI�DQ�HUURU�ZKHQ�FRQQHFWLQJ�WR�WKH�'LUHFWRU\�6HUYHU��IDOOEDFN�XVHUV�DQG�UROHV�FDQ�EH�GHILQHG�LQ�0'0�

[MDM LDAP]j6k�@?E #l%nm1+.��o 5 �$p��

Server=192.168.100.198

Server Port=389

Base DN=o=sap,c=US

Admin Name=Manager

Admin Password=secret

Admin Identifier=cn

User Identifier=uid

MDM Roles Algorithm=TraverseSearch

MDM Roles Attribute=MDMRoles

MDM Email Attribute=mail

Trace Level=0q �4A4&b� .B3rs#&%nmZ+��.o 5 ��p��

Fallback Roles=guest

Fallback Username=Monkey

Fallback Password=chatter

�

� The customer is responsible for the maintenance and design of their Directory Server (DS). They must inform SAP MDM about the directories and attributes to assure a proper communication.

� The MDM LDAP fields are defined or created and then populated by the customer in the customer’ s DS. Presently, MDM requires the addition of only one attribute field (unless an existing field is used): MDMRoles – a list of role names separated by semicolons (;)

� Since DS can allow multiple instances of an attribute, MDM will concatenate multiple entries as though they were in a single record separated by semicolons (;).

� All LDAP access is performed by the MDM Server. Clients of the MDM Server provide MDMUserName/MDMUserPass values, which MDM then validates with DS.

� DS contact information and other parameters relevant to MDM are maintained in the secure mds.ini file in a separate section named >0'0�/'$3@��If this section is absent, then DS use is disabled.

� If the MDM Server is not using LDAP (i.e. LDAP in Use=False), it will proceed with its traditional MDM-specific user authorization. By contrast, if the MDM Server is configured to use DS and is unable to find the Directory Server or connect to it via the MDMSystemManager, it will completely prevent any access to the MDM system, unless fallback parameters are specified.


SAP AG 2006

2sk_2 (1�6�<t��6�

0'0�&RPPXQLFDWLRQ�ZLWK�D�'LUHFWRU\�6HUYHU

u�vewVxeyez {Ax�|A}~O� y�ve|O{A�e�L� v~ u�x�� v1{&�e�L� v

@ B�B��:+.+s+�"��6�:+D�� m�+��4 8�'.+n8�%�"$7�� 2sk_2�k �"! 2 6%� �'3��# "$7 ^ �3�383+6# "�8��!*�� .-��3�.mZ+��C�Z .-n�.�� 6%.� E �+�+��8��3�_2�k�2�k �", 2 6%� .'6��B�81%6%��.B�"<+F"!8�"$7�� 2Fk�2 (��=t��3�� 6%.�n+��%3�.+F"�7��)m1+.�� k �"� ��3�_2�k�2 (��=t��Zb�#&%3�.+�"$8 j3k�@�E�k #&�!�.B:"!8D�,*��,p�+�#&%�'n"$7.�� 3�� 3-��"!��,+ j�k�@�E.� ] 8.+�"�� j�k�@�E3�DE 8��!"��

j�k�@?E3��@ ��-�#A%�� .-��.� j6k�@?E��@ ��-�#�% E �+�+.��.��p��+�"$#A%3'F" 7��nm�+�� k �¡;�8��Zp�+��3� ��2�k�2 ��3�!;!8D��-F+4 868�r�p6�n#l%�"�8 k #��,�.B�"!8D�,*�(��!t��

¢ �_2�k�2 ;$#A%.�.+�£�B6%�o�m�+�� Z .-n�.¤O��,��"��C# ��t��+�# " �¥ �_2�k�2 (��=t��6"C�!*�"�8�b�#�%.�F"�8 k #A��.B�"�8��*�(��,t�� 3'� �#A%�p�+6#&%.'n"C7�� k �� %.��6��83t�# ��.� E :+�+��8�� ¦3�Z5 7��§t3 �4Ap.��+�83;� �"="$� #Ab�p�"!��( @`E�2�k�2 ^ 8D4 �:+F 3��+��6%3�F"�8 2�k�2 (��3�!t��3�¨ � �§%�" 7��§+.��t��6��"C7��np�+��.��"! �#&4 +� 6%.��!��"C�C# ��t��3�©�!8D4 �:+� 3��FB�8�-�� !�3��s# "$7�" 7��$��83+�# "�8��!*.�:;�8��76# B�7s �B.B��+�+��` �+��Dp��+�",��b�*s"$7��np�+��6� �s2�k�2 'D�! �%�"<+F �B�B��+�+)b� :+3��n81%� �+�+6# '1%��3�©�!8D4 ��+ �

k #A�!��B:"�8��!*s(��t�� 2�k�2ªk :"! 2 6%� �'3��

123

4 5

6 7

66/

f�UOP [« f.UOP [�¬�

«¯® ¬ ® S3Q�T PeU

�

� Consider the mds.ini example from the previous slide. With these parameters, LDAP authorization by the MDM Server proceeds according to the following steps:

1. MDM receives a connection request from a client process which includes a UserName and UserPassword.

2. MDM binds to the LDAP server using six parameters: LDAP_Host, LDAP_Port, LDAP_AdminName, LDAP_AdminPass, LDAP_AdminIdentifier, and LDAP_BaseDN.

This can fail if any of the six parameter values are inaccurate. 3. As Admin, MDM searches for the full User DN (Distinguished Name) combining User Identifier

and Base DN. Failure occurs if anything other than a single entry is retrieved. 4. MDM finds “ uid=8VHU1DPH” where baseDN=“ o=sap,c=US.” This returns a full DN, such as

“ cn=Joe Cat, ou=Development, ou=Engineering, ou=People, o=sap, c=US.” 5. MDM then attempts to bind to the LDAP server using this DN and the provided password. If this

fails, the user is prevented from logging into the MDM system. 6. Using the full DN returned above, MDM collects and concatenates the MDMRoles for every level of

the tree, from individual user up to and including the Base DN. First, MDM gets the roles for the individual user (“ cn=Joe Cat, ou=Development, ou=Engineering, ou=People, o=sap, c=US” ), then his immediate group (“ ou=Development, ou=Engineering, ou=People, o=sap, c=US” ), the next group (“ ou=Engineering, ou=People, o=sap, c=US” ), and stops at the base DN (“ o=sap, c=US” ).

7. The list of role names is then compared to those in the MDM system to determine which are valid. Roles not found are assumed to be associated with another MDM repository and are ignored (if this is a result of a typo, the user will likely notice that he is unable to perform certain expected activities).


SAP AG 2006

/'$3�)DOOEDFN

)DOOEDFN�RSWLRQ�'HIDXOW�VHWWLQJV�LQ�FDVH�RI�

HUURU

° ,Q�FDVH�RI�DQ�HUURU�ZKHQ�FRQQHFWLQJ�WR�WKH�/'$3�GLUHFWRU\��IDOOEDFN�XVHUV�DQG�UROHV�FDQ�EH�GHILQHG�WR�DOORZ�DFFHVV�WR�WKH�UHSRVLWRU\�

° ,I�QR�IDOOEDFN�LV�GHILQHG��WKH�0'0�6HUYHU�ZLOO�QRW�DOORZ�DFFHVV�WR�WKH�UHSRVLWRU\�LQ�FDVH�RI�DQ�/'$3�HUURU�± 7KH�/'$3�VHUYHU�FDQQRW�EH�UHDFKHG�± 7KH�XVHU�QDPH�GRHV�QRW�H[LVW�RQ�WKDW�VHUYHU�± 1R�YDOLG�UROHV�DUH�SURYLGHG�

�

� When the MDM Server is using LDAP (i.e. LDAP in Use=True) user validation can fail for several reasons, including: the LDAP Server cannot be reached; the username does not exist on that server; or no valid roles are provided. When Fallback in Use=True, then the other Fallback parameters come into play after a failure, as follows: y If the username is validated in DS, but no LDAP supplied roles can be validated, MDM will

retrieve Fallback Roles from the mds.ini file. If absent or no specified roles are valid, the user login fails. This is a good method for a transitional step between validating user login in LDAP and actually populating LDAP with role information.

y If the username is not validated in LDAP because either the user does not exist in LDAP, or the LDAP server is unreachable, then MDM will attempt to validate that user against the traditional, internal MDM methodology. With this method, the username (and accompanying roles) must already be defined in the particular MDM repository. This may be valuable for select usernames that you wish to maintain in MDM in addition to LDAP.

y If the previous step still fails, you can still allow MDM access by specifying Fallback Username and Fallback Password. The username must exist within the MDM repository requested. Since this fallback method essentially allows anonymous access, you should take great care in defining the roles given to this username. However, it can be useful for certain circumstances where you need to give access prior to assigning general users roles in your DS.


SAP AG 2006

'LUHFWRU\�6HUYHU�² 5HVWULFWLRQV�DQG�/LPLWDWLRQV

5HVWULFWLRQV�DQG�/LPLWDWLRQV� 0'0�&RQVROH�XVHUV�GR�QRW�UXQ�XQGHU�'LUHFWRU\�6HUYHU�LQ�WKH�

LQLWLDO�UHOHDVH�RI�WKLV�IXQFWLRQDOLW\�� 6LQJOH�6LJQ�2Q��662��LV�QRW�VXSSRUWHG�'LUHFWRU\�6HUYHU�(UURU�+DQGOLQJ� (UURUV�WKDW�RFFXU�GXH�WR�'LUHFWRU\�6HUYHU�IDLOXUHV�DUH�

UHWXUQHG�WR�WKH�FOLHQW�DSSOLFDWLRQ��7KHUHIRUH��\RX�DUH�OLNHO\�WRUHFHLYH�UHSRUWV�IURP�FOLHQWV�ZKHQ�WKHUH�DUH�SUREOHPV�ZLWK�\RXU�'LUHFWRU\�6HUYHU�VHUYLFH�

�


SAP AG 2006

'LUHFWRU\�6HUYHU�,QWHJUDWLRQ��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 'HVFULEH�WKH�LQWHJUDWLRQ�RI�'LUHFWRU\�6HUYHUV��XVLQJ�

/'$3��ZLWK�0'0�6HFXULW\� 'HVFULEH�KRZ�D�'LUHFWRU\�6HUYHU�FDQ�IDFLOLWDWH�0'0�

6HFXULW\

�


SAP AG 2006

&RPSXWLQJ�&HQWHU 0DQDJHPHQW�6\VWHP





3HUIRUPDQFH




�


SAP AG 2006

&RQWHQWV�� 0RQLWRULQJ�0'0�YLD�&&06�

,QWURGXFWLRQ�WR�&&06�0RQLWRULQJ

�


SAP AG 2006

,QWURGXFWLRQ�WR�&&06�0RQLWRULQJ��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 'HVFULEH�WKH�PRQLWRULQJ�RI�0'0�YLD�&&06

�


SAP AG 2006

,QWURGXFWLRQ�WR�&&06�0RQLWRULQJ��%XVLQHVV�6FHQDULR

� $V�SDUW�RI�\RXU�RYHUDOO�V\VWHP�PRQLWRULQJ�VWUDWHJ\�\RX�ZDQW�WR�NQRZ�KRZ�WR�LQFRUSRUDWH�6$3�0'0�ZLWKLQ�\RXU�H[LVWLQJ�&RPSXWLQJ�&HQWHU�0DQDJHPHQW�6\VWHP��&&06��HQYLURQPHQW�

�


SAP AG 2006

,QWURGXFWLRQ�WR�&&06

1RQ�6$3 FRPSRQHQW²3³e´¶µ · ³�¸�µ ´¶¹ºO» ¹e¼ » ´�·

1RQ�6$3�%DVLV FRPSRQHQW².³L´�µ · ³�¸Aµ ´¶¹ºe» ¹�¼ » ´�·

&(1

6$3�FRPSRQHQW IRUFHQWUDO PRQLWRULQJ

( @�E¾½ �+6# + ¢ � ¿ �%��©7�# 'D7.�3�

6$3�LQVWDQFH².³L´�µ · ³e¸Aµ ´¶¹ºe» ¹�¼ » ´�·

( @?E©a ��b @ ( ¦.�l��¿ 6%.��76# '17��3�

6$3�LQVWDQFH²3³e´¶µ · ³e¸&µ ´�¹ºL» ¹�¼ » ´�·

´&(1³�VLJQLILHV WKH FHQWUDO PRQLWRULQJ V\VWHP��,WV 6,'�FDQ EH GLIIHUHQW��H�J��´0&�³�

�

� Many components are involved in the flow of a business process in a modern IT system architecture. These components must be monitored, as both a gradual reduction in performance and a sudden breakdown of a component could seriously affect productivity. It is a task of the administrator to monitor the system landscape proactively, and not only in the case of errors.

� Monitoring should be organized as efficiently as possible. There is not enough time for an administrator to log on to each host component to check its status. An efficient monitoring structure should be able to display the entire system landscape at a glance centrally. If an error occurs, the person responsible should be automatically notified. Tools should be provided for the analysis of errors that provide detailed information about the problem across the system.

� Components with SAP Basis Systems or SAP Web Application Server (SAP Web AS) can directly be included into a central monitoring environment using the CCMS alert monitoring architecture.

� Components without SAP Basis are connected using CCMS agents. � Each component collects its own monitoring data using the infrastructure and stores it locally in the

main memory. This part of the main memory is called the PRQLWRULQJ�VHJPHQW. You can configure the size of the monitoring segment.

� The central monitoring system collects the monitoring data for the components and displays it in various views. Throughout this course material "CEN" is used to signify this central monitoring system. The actual SID can be chosen differently. In this way, you have a central view of the entire system landscape. If errors occur, you can jump directly from the central monitoring system to the appropriate component to pinpoint a problem by detailed analysis.

� The central monitoring system (CEN) should be hosted on a system with high availability and a high basis release such as SAP Web AS 6.40.


SAP AG 2006

7KH�$OHUW�0RQLWRU

® Q M i d Q.[ i MLN?À [ PePG T P h P:M�d�U

X T T d [ PeP?M Q g PeU

Á Â »�Ã ¸ »CÄ » ´¶·¶³e´ »6Ã¶Å�ÆCÄ µ Ç$È�É³e¸LÉ ³�¹�µ Ç ÈCÉ�³eÊ!Ë » Ç$·Á º�Ì ¼�¼�È¶¸Aµ Í » È É » ¸ · Ä È ´�ÎÃ ¸ ³ Ã È$¹�ÈC· » · ³ Å µ ¹ Å » ¸´¶³�Î »CÄ

Á Â » Ç » µ Ï » Î�È$· È�È ´¶Î�¼6È ÆÇ¶¸ » ÈC· » È�É » ¸ · ÄÁ Ð Ä » ÎVÈ$· È�Ñ ³e¸VÈ ´¶È É Æ Ä µ ÄÈ¶É » ¸ · Ä

Ò i P�Ó

® Q M i d Q�[ i MLN?Ô�Õ¶ÖlPOI�d

® Q M i d Q�[ i MLN X dld [ i Õ�×�dlPLU

�

� The CCMS has an object-based monitoring architecture that simplifies the task of monitoring several SAP systems. This monitoring architecture integrates information from the entire SAP environment to present an easy-to-manage overview of the condition of the SAP systems and their environment. The information is displayed in a tree-based structure.

� All nodes of the tree-based structure are called 0RQLWRULQJ�7UHH�(OHPHQW��07(�. � The information gathered by the data collectors is assigned to monitoring attributes. Monitoring

attributes are the leaf nodes of the tree. They represent physical characteristics or messages related to a monitoring object. For example, the monitoring object 'DWD�$UHD�(for MaxDB) has the monitoring attributes 7RWDO�'DWD�6SDFH, )UHH�'DWD�6SDFH�and 8VHG�'DWD�6SDFH. All nodes above the level of Monitor Attributes only help to locate the right "leaf node".

� For each monitoring attribute, alerts are displayed if configurable threshold conditions are met.


SAP AG 2006

$JHQWV

$JHQW¬ Ked�KW ×:Ø:Ø T i P [¬ K�dlKW ×:Ø:Ø T i P [

( @�E (�*�+�"!�3-Ù;�8D�Ú��3%�"$�� 64 2 8D%�# "�8D�C#A%3'

c G

-$9$

-$9$,QWHUIDFH

6$326&2/

([WHUQDO&RPSRQHQWV

([WHUQDO6RIWZDUH

$OHUW�)LOH

( @`E¡Û %�+."= 6%3B��².³e´¶µ · ³�¸&µ ´¶¹ºO» ¹e¼ » ´�·

Y [�Q I�PeULUY [�Q I�PeULU

/RJ�)LOH

�

� Until recently, individual monitoring tasks could not be dealt with, or could only be insufficiently dealt with. For example, CCMS could not monitor components based on SAP R/3 3.x and non-SAP components centrally. Additional data bottlenecks occurred at times when the remote component had low performance because it would return data slowly.

� The agent concept in central monitoring deals with these bottlenecks. � CCMS agents are stand-alone processes that act as an RFC server to a central monitoring system.

Agents are fully supported, if CEN has an SAP Basis 4.6C or higher. � The CCMS agent on the monitored system (e.g. PC on which the MDM Server is installed) collects

monitoring information, such as the availability of the MDM Server or MDM log files, or OS Collector data about the system status. This data is provided to the central monitoring system on which the CCMS agent is registered via RFC. The CCMS agent can be registered on more than one monitoring system, but one of these monitoring systems plays the role of the central monitoring system (CEN).

� In the CEN, the data is stored in the CCMS database and can be displayed with transaction RZ20 in different monitoring collections.


SAP AG 2006

0'0�6HUYHU�0RQLWRU�7HPSODWH

�

� Start CCMS monitoring in the CEN with transaction RZ20. You can find the new MDM monitoring template here. One part of the template is “ MDM Server Monitoring” .

� Use Note 889580 to get the latest SP04 monitoring templates for MDM 5.5 SP04. � After importing the new templates, you should see the following submonitors in the collection:

y GDS Console Monitoring y MDM ABAP API Monitoring y MDM Server Monitoring

� Double-click 0'0�6HUYHU�0RQLWRULQJ to jump to the MDM Server monitoring tree. � The MDM_CCMS plug-in provides communication between the CCMS agent and the MDM Server

to get all monitoring data. The complete monitoring tree shown in the central monitoring system (CEN) below the “ MDM Server Monitoring” is delivered.


SAP AG 2006

0'0�6HUYHU�0RQLWRULQJ

�

� If the MDM Server is not up and running, the Performance and Repositories subtrees cannot display any data (this is obvious because the MDM Server delivers this data).

� In the CCMS you can set thresholds at which the flag should be displayed in green, yellow, or red. � If a threshold value is violated, an auto-reaction method can be started automatically by the CCMS

system (e.g. send an e-mail if the server is no longer available). � See the standard CCMS documentation about defining the auto-reaction in CCMS.


SAP AG 2006

6HUYHU�$YDLODELOLW\�0RQLWRULQJ�

�

� Availability and heartbeat monitoring is now also available for the Import Server, Syndication Server and Layout Server.


SAP AG 2006

5HSRVLWRU\�$YDLODELOLW\�0RQLWRULQJ�

�

� Availability and heartbeat monitoring is available for the MDM repositories running on the MDM server.

� It is not sufficient to provide an alerting mechanism for MDM Servers that are stopped and that should be up and running.

� It is also important to store the status of all repositories from different MDM Servers in the central monitor. For example, if a repository is unloaded from the Console, the CEN is informed by the CCMS about this status and can send an alert.

� If the MDM Server is running on a host in this subtree, the availability of all mounted repositories is displayed.

� The status can be: y mounted (not loaded) y running (loaded)


SAP AG 2006

0'0�6HUYHU�$WWULEXWHV

�

� For each type of MDM Server (MDM Server, MDM Import Server, MDM Syndicator Server, MDM Layout Server), the CCMS can display additional information, such as: y Host name on which the server is running y Server release, including build number (e.g. Version 5.5 SP4 (5.5.32.31) ) y Build type (e.g. Unofficial Development Build) y Build number of the CCMS plug-in (for self-monitoring) y System uptime (seconds since last start) y Number of client logons (such as Data Manager) y Number of Web logons y Number of mounted repositories on the server y Number of running repositories on the server


SAP AG 2006

1HZ�9LHZ�IRU�/RJ�)LOH�'LVSOD\

�

� IN MDM 5.5 SP03, the MDM log files collected by the SAPCCMSR Logmon feature were displayed as plain text xml. Since the result was not very readable, two additional views to the MDM log files are provided. y SAP standard LogViewer (SAP LV) format

- The log file can be transformed dynamically to standard SAP LV format. This allows you to download the file and display it in the SAP LogViewer. The SAP LogViewer is available in different variants:

- Embedded SAP LV, e.g. in SAP Solution Manager - Standalone SAP Standard LV – An SAP standard LogViewer is available as part of each SAP

NetWeaver J2EE installation y MDM standard log viewing format

- When you display MDM log files in the MDM Console, you see an attractive and readable browser-based format of the log files. With the new CCMS analysis methods delivered with MDM 5.5. SP04, you can present the MDM log files in the CEN system in the same schema as in the MDM Console.


SAP AG 2006

,QWURGXFWLRQ�WR�&&06�0RQLWRULQJ��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 'HVFULEH�WKH�PRQLWRULQJ�RI�0'0�YLD�&&06

�


SAP AG 2006

3HUIRUPDQFH





3HUIRUPDQFH




�


SAP AG 2006

0'0�3HUIRUPDQFH

&RQWHQWV�� 7RSRORJ\�UHFRPPHQGDWLRQV� 'DWDEDVH�VXJJHVWLRQV

�


SAP AG 2006

0'0�3HUIRUPDQFH��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� ([SODLQ�WKH�0'0�SHUIRUPDQFH�DGYDQWDJHV�RYHU�64/�

'%06� 'HVFULEH�ODQGVFDSH�DQG�RSWLPL]DWLRQ�WLSV� ([SODLQ�EDFNXS�DQG�UHFRYHU\�RSWLRQV

�


SAP AG 2006

0'0�3HUIRUPDQFH��%XVLQHVV�6FHQDULR

� <RX�ZDQW�WR�NQRZ�SULRU�WR�EHJLQQLQJ�WKH�LPSOHPHQWDWLRQ�WKH�RSWLRQV�IRU�GHYHORSLQJ�D�V\VWHP�ODQGVFDSH��

� :KHQ�\RX�LPSOHPHQW�\RXU�6$3�0'0�V\VWHP�ODQGVFDSH��\RX�ZDQW�WR�NQRZ�KRZ�WR�DFKLHYH�WKH�EHVW�SRVVLEOH�SHUIRUPDQFH�IURP�0'0�

�


SAP AG 2006

3HUIRUPDQFH�$GYDQWDJHV/DQGVFDSH�2SWLPL]DWLRQ�7LSV'%06�2SWLPL]DWLRQ�7LSV6XPPDU\

3HUIRUPDQFH�$GYDQWDJHV

�


SAP AG 2006

3HUIRUPDQFH�$GYDQWDJHV

0DLQ�3HUIRUPDQFH�$GYDQWDJH�0'0�RIIHUV�VHDUFKHV�WKDW�DUH�RUGHUV�RI�PDJQLWXGH�IDVWHU�WKDQ�DQ�64/�'%06�DORQH�WKURXJK�FDFKLQJ�RI�UHSRVLWRU\�GDWD�0LQRU�3HUIRUPDQFH�$GYDQWDJH�0'0�XVHV�PDVNV�LQVWHDG�RI�64/�YLHZV�° :LWKLQ�DQ�64/�EDVHG�'%06��\RX�FDQ�XVH�YLHZV�WR�SUHFLVHO\�FRQWURO�

ILHOG� DQG�UHFRUG�OHYHO�DFFHVV�E\�YDULRXV�XVHUV��+RZHYHU��YLHZV�DUH�FXPEHUVRPH�WR�PDQDJH�DQG��PRUH�LPSRUWDQWO\��GHJUDGH�V\VWHP�UHVSRQVH��RIWHQ�FUHDWLQJ�VHYHUH�SHUIRUPDQFH�ERWWOHQHFNV�

° 8QOLNH�64/�YLHZV��0'0�PDVNV�LPSRVH�QR�SHUIRUPDQFH�SHQDOW\�ZKDWVRHYHU��DQG�DUH�GHILQHG�DW�WKH�LQGLYLGXDO�UHFRUG�OHYHO�UDWKHU�WKDQ�WKH�TXHU\�OHYHO�

�

� See MDM 5.5 Support Package 04 sizing guide. � Change tracking has not proven to be a significant performance draw.

y Performance depends on: - Speed of the database - Number of fields being tracked

� 32-bit versus 64-bit operating systems have not proven to significantly impact performance. � Changes in the “ chunk size” in MDIS and MDSS can affect performance.

y Chunk size: Number of records before a DB commit is made - Has DB locking implications


SAP AG 2006

/DQGVFDSH�2SWLPL]DWLRQ�7LSV


�


SAP AG 2006

6$3�1HW:HDYHU�0'0�7RSRORJ\

0'0&OLHQWV

'%066HYHU

0'06HUYHU

0'0&RQVROH

° $OO�FRPSRQHQWV�FDQ�EH�LQVWDOOHG�RQ�RQH�PDFKLQH�EXW�D��7LHU�ODQGVFDSH�LV�UHFRPPHQGHG�

° 0'0�6HUYHU��6$3�0'0�0RGXOHV�DQG�'%06�6HUYHU�VKRXOG�EH�LQVWDOOHG�RQ�GLIIHUHQW�V\VWHPV�

° 0'0�&RQVROH�LV�D�OLJKWZHLJKW�DSSOLFDWLRQ�DQG�FDQ�EH�LQVWDOOHG�DW DQ\�ZRUNVWDWLRQ�RU�VHUYHU�SHU�\RXU�FKRLFH

�

� By moderate size, we mean that a machine has enough memory to run both the MDM Server and the DBMS engine. When the repository is large, typically having more than 1 million records, or when the amount of memory the MDM Server uses is greater than physical memory, it is probably best to distribute the components.

� When the DBMS Server component is also running other, non-SAP NetWeaver MDM databases or

applications, it may also be best to separate these components. The MDM Console uses few resources and should be located mainly for the convenience or security of your system.


SAP AG 2006

6$3�1HW:HDYHU�0'0�7RSRORJ\��

• 6XFK�D�WRSRORJ\�LV�HDVLHU�WR�PDQDJH�DQG�LV�UHFRPPHQGHG�ZKHQ�D�FXVWRPHU�UHSRVLWRU\�LV�RI�PRGHUDWH�VL]H�DQG�WKH�0'0�6HUYHU�LV�WKH�RQO\�GDWDEDVH�XVHU�

• 7KHUH�PD\�EH�FDVHV��WKRXJK��ZKHQ�WKH�SHUIRUPDQFH�RI�D�GLVWULEXWHG�ODQGVFDSH�LV�EHWWHU

• 0HPRU\�LV�IUDJPHQWHG�WR�VHUYH�GLIIHUHQW�DSSOLFDWLRQV

'%06�

0'0�6HUYHU�&RQVROH

0'0&OLHQW

0'0&OLHQW

0'0&OLHQW

° )RU�D�VPDOO�VL]HG�V\VWHP��HQRXJK�PHPRU\�DQG�OHVV�WKDQ�D�PLOOLRQ�UHFRUGV��D�VLQJOH�PDFKLQH�PD\�EH�DEOH�WR�UXQ�WKH�'%06�6HUYHU�DQG0'0�6HUYHU�DQG�0'0�&RQVROH�

�

� There is a tradeoff for choosing an optimal landscape between network and server resources. In case when both, MDM server and DBMS are installed on one system there is no network waste. On the other hand, in this case both components share the system‘s resources. One should analyze and estimate the required memory and CPU resources and install MDM server together with the DBMS if the repository isn‘t too big. If it‘s not the case then the components must be installed on different systems and performance deterioration due to network communication is compromized (see Network configuration for details)

� “ Small sized system“ should be defined carfuly. The number of the records can be relatively small but the repository‘s complexity may wipe off the meaning of the small system.

� One-box option is a working approach for a development environment but should be analyzed in each particular case if it‘s appropriate for a production due to the above comments


SAP AG 2006

0DVWHU�6ODYH

Master

Ü?Ý:Þ�ßlà3á�âZÝ�ß�Ý�ã�Ý�Þ�à

ä à3å�Ý3á<Ý:ß=à�æäZç Ý:è�à�â�Ý�ß<Ý�ã�Ý:Þ:à

élê�å�ß�ë êDì�Ý ç í

Slave

Slave

Synchronization request

Synchronization request

Separated DB

äZç Ý:è�à�â�Ý�ß<Ý�ã�Ý:Þ:àShared slave DB

READ ONLY ACCESS

î 6ODYHV�DUH�UHDG�RQO\�VQDSVKRW�FRSLHV�RI�WKH�PDVWHU

î 0D\�VKDUH�RQH�VODYH�'%�RU�XVH�HDFK�GHGLFDWHG

î 0DVWHU�LV�QRW�DZDUH�RI�LWV�VODYHV��EXW�VODYHV�DUH�DZDUH�RI�WKHLU�PDVWHU�

î 6ODYHV�LQLWLDWH�V\QFKURQL]DWLRQ�UHTXHVWV��RI�GHOWDV�FKDQJHV�

î 6\QFKURQL]DWLRQ�LV�FDUULHG�RXW�YLD�ï &RQVROHï &RPPDQG�OLQH�LQWHUIDFH�

FDQ�EH�VFKHGXOHG* At least one slave DB is required

�

� A master can have multiple slaves.


SAP AG 2006

0DVWHU�6ODYH��1RUPDOL]DWLRQ

� 7R�³QRUPDOL]H´ D�VODYH�PHDQV�WR�UHPRYH�LW�IURP�WKH�³FOXVWHU´ DQG�WR�GHVWUR\�WKH�PDVWHU�VODYH�UHODWLRQVKLSV�

� %\�QRUPDOL]LQJ�D�VODYH�ð ,W�EHFRPHV�DQ�LQGHSHQGHQW�

1RUPDO�VHUYHUð 1R�QRWLRQ�RI�WKH�SUHYLRXV�PDVWHUð &DQQRW�XQGR�WKH�RSHUDWLRQð 6ODYH�KDV�WR�KDYH�D�GHGLFDWHG�

VODYH�'%

�

� Once a slave has been “ separated,” it becomes a master. � Once a slave has been normalized, access can be changed to read/write. � If a master has more than one slaves then they can share the same slave DB


SAP AG 2006

6FDOH�LQ�YV��6FDOH�RXW�&OXVWHULQJ

î 0RUH�H[SHQVLYHî 0RUH�PDLQWHQDQFH

î 0RUH�VWDEOHî 0D\�EH�GHSOR\HG�RQ�D�

FURVV�26�JURXS

6FDOH�RXW

î 3RUW�FRQILJXUDWLRQ�LV�UHTXLUHG

î 6LQJOH�SRLQW�RI�IDLOXUH�

î /HVV�UHVRXUFHV�DUH�QHHGHG

6FDOH�LQ&RQV3URV

:H�DVVXPH�WKDW�DOO�UHSRVLWRULHV�DUH�EXLOW�IURP�WKH�VDPH�VFKHPD�DQG�DUH�LQ�D�PDVWHU�VODYH�UHODWLRQVKLS�

ñ 6FDOH�LQ��6HYHUDO�UHSRVLWRULHV��VODYHV�DQG�RU�PDVWHU��PRXQWHG�RQ�WKH�VDPH�0'0�VHUYHU�EXW�GLIIHUHQW�SRUWV

ñ 6FDOH�RXW��6HYHUDO�UHSRVLWRULHV�PRXQWHG�RQ�GLIIHUHQW�0'0�VHUYHUV

�


SAP AG 2006

/RDG�%DODQFLQJ

ò?ó�ß�ë è.àÜ�Ý:Þ�ß<à�á

Master DB

Periodical synchronization requests

ä�ç Ý�è�à ä�ç Ý�è�àä�ç Ý�è.à

Read-only cluster

ô�à�Ý�æ�õ,ö¾á$ë ßlà§÷3Ý�ß=à ôZà�Ý�æ�õAê1ì ç ø ÷�Ý�ßlà

Slave DB(s)

ù�Ý�Þ�Þ�ë è.àÜ�Ý�Þ:ß<à6á

Application cluster *

7KLUG�SDUW\�DSSOLFDWLRQ�FOXVWHU�LV�XVHG�WR�GLDJQRVH�PDVWHU�VHUYHU�VWDWXV�DQG��FDUU\�RXW�VZLWFK�RYHU�LQ�FDVH�RI�D�IDLOXUH�

�

� Open source selections are available at hardware and software levels.


SAP AG 2006

3RUW�)OLS�2YHU

0'0�6HUYHU0DVWHU0DVWHU 0'0�FRQVXPHUV

0DVWHU�SRUW

6ODYH6ODYH0DVWHU�SRUW

� �5H�ORDGLQJ�SURGXFWLRQ�UHSRVLWRU\�PD\�WDNH�WLPH

� $�UHSRVLWRU\�FDQ�EH�ORDGHG�ZLWKRXW�SRUW�ELQGLQJ

� 5HSRVLWRU\�IOLS�RYHU�FDQ�EH�GRQH�E\�SRUW�ELQGLQJ�WKH�VODYH�WR�WKH�PDVWHU�SRUW

�

� If a repository needs to be reloaded it may take significant time, especially when the repository is full of records. For a production environment it‘s crucial to minimize the time when the master (write-access) repository down. The Port Flip-over technique helps here:

� Load a slave repository without a port assigned � Put the original repository down (and at the same time freeing the port it was using) � Bind the freed port to the slave repository (at this point we‘ve got a read-only repository running in a

slave mode. It‘s only an interim solution to let the master to reload. It‘s better than having another slave running on its own port since the external applications don‘t need to be reconfigured on the other port)

� Now we load it without port binding and when it‘s ready we stop the slave, free the port, and bind it back to the up and running master


SAP AG 2006

&RPSDULQJ�5HFRYHU\�6ROXWLRQV

ñ &RVW�RI�WKLUG�SDUW\�DSSOLFDWLRQ

ñ &RVW�RI�FRQILJXULQJ

ñ 'RZQ�WLPH�LV�PLQLPDOñ 0DVWHU�LV�DYDLODEOH�IDVWHU

6ZLWFK�RYHU

ñ 1R�ZULWH�DFFHVV�GXULQJ�UHVWDUWLQJ�RI�PDVWHU

ñ 5HFRQQHFWLRQ�WR�VODYHV�LV�WUDQVSDUHQW�IRU�FOLHQWV

ñ /HVV�GRZQ�WLPH�WKDQ�LQ�WKH�³RQH�PDVWHU�RQO\´ VROXWLRQ

3RUW�IOLS�RYHU

ñ (YHQ�LI�D�VODYH�H[LVWV��DOO�FOLHQWV�KDYH�WR�UHFRQILJXUH�FRQQHFWLRQ�VHWWLQJV�WR�UH�FRQQHFW

ñ 1R�DGGLWLRQDO�FRQILJXUDWLRQ2XW�RI�WKH�ER[

&RQV3URV6ROXWLRQ

�


SAP AG 2006

%DFNXS�DQG�5HFRYHU\

� %DFNXS�RSWLRQV�ð 6$3�0'0�EDFNXS�PD\�EH�SHUIRUPHG�IURP�DQ�XSGDWHG�VODYH�WR�

PLQLPL]H�WKH�SHUIRUPDQFH�LPSDFW�ð '%�QDWLYH�EDFNXS�PD\�EH�LPSOHPHQWHG��XVXDOO\�WKHUH�LV�DQ�

H[LVWLQJ�EDFNXS�'%�SROLF\�LQ�SODFH� 5HFRYHU\�RSWLRQV�

ð /RDG�DQ�DUFKLYH��(VVHQWLDOO\�FUHDWH�D�QHZ�'%ð 1RUPDOL]H�D�VODYH��0XFK�IDVWHU�EXW�UHTXLUHV�V\VWHP�DGMXVWPHQWVð 5HFRYHU�YLD�QDWLYH�'%�PHWKRGV

�


SAP AG 2006

([DPSOH�RI�6L]LQJ�2SWLRQV

0'0'DWD�0DQDJHUV

'%066HYHU

0'0�6HUYHU�

0'0�&RQVROH

0'0�VHUYHU�UHTXLUHPHQWV�î !��*%�5$0î )DVW�&38�V�î 17)6�ILOH�V\VWHP��:LQGRZV�î 6HW��*%�PHPRU\�DOORFDWLRQî 7&3�,3�GDWD�WUDQVIHUî 6SHFLDO�VHWWLQJV�IRU�HDFK�

VHUYHU�RSWLPL]HV�WKH�PDFKLQHV�IRU�WKHLU�SXUSRVH��H�J��'%06�VHUYHU�VSHFLDOL]HG�IRU�'%�XVDJH�

�

� MDM Server Requirements are dynamic and depend upon many factors as described in the MDM Sizing Guide.

� The ABAP SAPS numbers are about equivalent to a SQL Insert or Update command, where single

field of a single SQL table is being affected for updates, and an entire row of a single table is affected for Inserts. This allows more operations in a single thread of execution and makes it easier to have concurrent threads operating on the same collection of tables. The ABAP data access is basically direct SQL access with no caching or acceleration of complex searches so there is very little memory required and even less dependency on synchronization between tables, allowing more concurrent operations. In MDM, read access does scale with CPUs in that more queries can be performed, although they will still each take just as long (or longer once CPUs are maxed out). At present we use a hardware dependent CPU Sizing for MDM.


SAP AG 2006

0HPRU\�5HFRPPHQGDWLRQV

0HPRU\�KDV�WKH�ELJJHVW�LPSDFW�RQ�SHUIRUPDQFH�0'0�6HUYHU�ORDGV�D�VLJQLILFDQW�SDUW�RI�WKH�UHSRVLWRU\�LQWR�

PHPRU\�RI�WKH�PDFKLQH�UXQQLQJ�WKH�6HUYHU�,I�WKH�DSSOLFDWLRQ�UHTXLUHV�PRUH�WKDQ��RI�WKH�PHPRU\�DOORFDEOH�

IRU�WKH�DSSOLFDWLRQ�WKLV�ZLOO�KDYH�FULWLFDO�LPSDFW�RQ�WKH�SHUIRUPDQFH

� 6\VWHP�ZLOO�VWDUW�VZDSSLQJ�SURFHVVHV�DQG�GDWD�WR�WKH�KDUG�GULYH�RI�WKH�PDFKLQH

� 3HUIRUPDQFH�DGYDQWDJH�RI�6$3�0'0�ZLOO�EH�ORVW��

�


SAP AG 2006

6L]LQJ�([SHULHQFH

î 7KH�FULWLFDO�WKUHVKROG�RI��*%�RI�5$0�FDQ�EH�UHDFKHG�E\�UHSRVLWRULHVï !�2QH�PLOOLRQ�UHFRUGV�ZLWK�ULFK�FRQWHQW�VWRUHG�LQ�WKH�UHSRVLWRU\ï ��PLOOLRQ�UHFRUGV�ZLWK�OLWWOH�ULFK�FRQWHQW�VWRUHG�LQ�WKH�UHSRVLWRU\

î ,I�WKH�UHFRUGV�DUH�VWRUHG�LQ�PRUH�WKDQ�RQH�UHSRVLWRU\��WKHUH�LV�D�KLJKHU�PHPRU\�XVDJH�EHFDXVH�WKH�VWUXFWXUH�RI�HDFK�UHSRVLWRU\�PXVW�EH�ORDGHG�DV�ZHOO��

î 7UDLQLQJ�VFHQDULR�DSSUR[LPDWLRQ�ï 0'0�VHUYHU�LV�RQO\�DSSOLFDWLRQ�UXQQLQJï ��5HSRVLWRULHV�ORDGHGï ��SURGXFWV�ZLWK�ORWV�RI�RULJLQDOVÆ ��SURGXFWV�Æ DSSUR[LPDWHO\�

��0%�RI�PHPRU\�XVHG��ZLWK�RYHUKHDG�IURP�GLIIHUHQW�UHSRVLWRU\�DQG�ZLWKRXW�26�

î :HE�VHUYHU�ï ([SHULHQFH��$W�OHDVW��*%�RI�PHPRU\�RQ�WKH�PDFKLQH�UXQQLQJ�WKH�:HE�

VHUYHU

�


SAP AG 2006

1HWZRUN�5HFRPPHQGDWLRQV

� $OO�0'0�DQG�'%06�VHUYHUV�VKRXOG�EH�LQVWDOOHG�LQ�RQH�/$1�ZLWK�D�EDFNERQH�RI��*ESV��

� 1HWZRUN�FRQQHFWLRQ�EHWZHHQ�0'0�6HUYHUV�DQG�0'0�FOLHQWV�VKRXOG�EH�DW�OHDVW��0ESV�

� ,Q�VFHQDULRV�ZKHQ�FOLHQW�DSSOLFDWLRQV�FRQQHFW�WR�WKH�VHUYHUV�RYHU�VORZ�QHWZRUNV��:$1��IRU�LQVWDQFH��VHULRXV�SHUIRUPDQFH�LPSURYHPHQWV�FDQ�EH�JDLQHG�IURP�LQVWDOOLQJ�WKH�FOLHQWV�RQ�D�7HUPLQDO�6HUYHU�V\VWHPV��H�J��&LWUL[��ZKLFK�UHVLGHV�LQ�WKH�VDPH�³TXLFN´ /$1�ZLWK�0'0�VHUYHUV�

�


SAP AG 2006

'%06�2SWLPL]DWLRQ�7LSV


�


SAP AG 2006

'%06�5HFRPPHQGDWLRQV�

� 6SHHG�RI�KDUG�GULYHV�LV�HVVHQWLDO�IRU�SHUIRUPDQFH��6$3�0'0�VFHQDULR��LPSDFW�RQ�WKH�VSHHG�RI�ORDGLQJ�D�UHSRVLWRU\��ZULWH�DQG�PRGLI\�UHSRVLWRULHV�RU�GDWD�

� 5$,'��IRU�'%06�6HUYHU�KDUG�GULYHV�LV�UHFRPPHQGHG� 8VH�RQH�QHWZRUN�FRQQHFWRU�GHYLFH�SHU�FRQQHFWHG�0'0�6HUYHU�

LQ�RUGHU�WR�LQFUHDVH�WKH�SRVVLEOH�UDWHV�IRU�LQSXW�RXWSXW�DQG�WR�EDODQFH�WKH�,�2�ORDG

� '%06�VKRXOG�EH�EDODQFHG�E\�PHPRU\�XVDJH� $�:ULWH�%DFN�&DFKH�HTXLSPHQW�RI�'%06�LV�FULWLFDO�IRU�0'0�

SHUIRUPDQFH�GXULQJ�,PSRUW�RSHUDWLRQV� 0'0�WDNHV�DGYDQWDJH�RI�WKH�ODWHVW�XSGDWHV�DQG�LPSURYHPHQWV�

RI�WKH�XQGHUO\LQJ�'%06� &ULWLFDO�'%06�,VVXH��%DFNXS�DQG�5HVWRUH�DFWLRQ�VKRXOG�EH�

VFKHGXOHG�GXULQJ�QRQ�SHDN�KRXUV�LQ�RUGHU�QRW�WR�QHJDWLYHO\�LPSDFW�SHUIRUPDQFH

�


SAP AG 2006

2SWLPL]HG�6$3�1HW:HDYHU�0'0�3HUIRUPDQFH

• ,I�'%06�DQG�0'0�6HUYHU�DUH�RQ�WKH�VDPH�PDFKLQH��GHILQH�DQ�$OLDV�WKDW�XVHV�D�³ORFDO´SURWRFRO�UDWKHU�WKDQ�7&3�XVLQJ�WKH�&OLHQW�&RQILJXUDWLRQ�$VVLVWDQW��LQFUHDVH�RQ�XQ�DUFKLYLQJ

'%�

• ,I�'%06�DQG�0'0�6HUYHU�DUH�RQ�WKH�VDPH�PDFKLQH�XVH�WKH�2UDFOH�1HW��$VVLVWDQW�WR�GHILQH�D�/LVWHQHU�DGGUHVV�DQG�ORFDO�6HUYLFH�QDPH�WKDW�XVHV�WKH�,3&�SURWRFRO�UDWKHU�WKDQ�7&3��LQFUHDVH�RQ�XQ�DUFKLYLQJ

• 6HSDUDWH�KDUG�GLVFV�VKRXOG�EH�XVHG�IRU�PDLQ�GDWD�DQG�LQGLFHV

2UDFOH

• 0DLQ�GDWD�ILOH��PGI��DQG�WUDQVDFWLRQ�ORJ�ILOH��OGI��DUH�ORFDWHG�RQ�GLIIHUHQW�VSLQGOHV

• ��SHUIRUPDQFH�LPSURYHPHQW�64/�6HUYHU

'HVFULSWLRQ'%06

0DNLQJ�D�IHZ�PLQRU�DGMXVWPHQW�ZLWK�6$3�0'0�DQG�RU�WKH�'%06�VHUYHU�FDQ�HQKDQFH�VHDUFK�DQG�XSGDWH�SHUIRUPDQFH�E\�XS�WR��

�


SAP AG 2006

6XPPDU\


�


SAP AG 2006

6XPPDU\

� 6$3�0'0�VXSSRUWV�D�WKUHH�WLHU�ODQGVFDSH�DQG�SURYLGHV�PXOWLSOH�GHVLJQ�RSWLRQV�IRU�KLJK�DYDLODELOLW\�DQG�VFDODELOLW\��ð 0'0�VHUYHU��6$3�0'0�DSSOLFDWLRQV��DQG�'%06�VHUYHU

� 2YHUDOO��6$3�0'0�SHUIRUPDQFH�GHSHQGV�RQ�WKH�XQGHUO\LQJ�'%06�VHUYHU��DV�ZHOO�DV�RQ�WKH�FRQQHFWLRQ�SURWRFRO�XVHG�

� 0LQRU�FKDQJHV�LQ�WKH�VHWWLQJV�IRU�WKH�'%06�RU�WKH�FRQQHFWLRQ�ZLWK�WKH�'%06�FDQ�LQFUHDVH�SHUIRUPDQFH�XS�WR��

� 0HPRU\�LV�FULWLFDO�DQG�WKH�0'0�6HUYHU�VKRXOG�QRW�H[FHHG��RI�WKH�DOORFDEOH�PHPRU\�

�


SAP AG 2006

0'0�3HUIRUPDQFH��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� ([SODLQ�0'0�SHUIRUPDQFH�DGYDQWDJHV�RYHU�64/�

'%06�DORQH� 'HVFULEH�ODQGVFDSH�DQG�'%06�RSWLPL]DWLRQ�WLSV� ([SODLQ�EDFNXS�DQG�UHFRYHU�RSWLRQV

�


SAP AG 2006

$SSHQGL[��

��0'0��3&0��3&0

3ULQW

,%0�$,;+3�8;6816RODULV

/LQX[��ELW

:LQ��ELW

:LQ��ELW

6HDUFKHV�SHU�+RXU

6FHQDULR&38�8WLOL]DWLRQ��

�


SAP AG 2006

$SSHQGL[��

��0'0

��3&0

��3&03ULQW

��Q�D��Q�D��

��Q�D��Q�D��

��Q�D��Q�D��

��

,%0�$,;+3�8;6816RODULV

/LQX[��ELW

:LQ��ELW

:LQ��ELW

6HDUFKHV�SHU�+RXU

6FHQDULR0HPRU\�8VDJH�*%

Q�D� 7KLV�FRQILJXUDWLRQ�UHTXLUHV�D��ELW�+:��26��0'0�HQYLURQPHQW�


SAP AG 2006

8QLW��,QWHJUDWLRQ�6FHQDULRV��3RUWDO�,QWHJUDWLRQ





3HUIRUPDQFH




�


SAP AG 2006

&RQWHQWV�� 8VH�RI�3RUWDO�WR�DFFHVV�0'0�GDWD�

0'0�,QWHJUDWLRQ�ZLWK�(QWHUSULVH�3RUWDO

�


SAP AG 2006

0'0�,QWHJUDWLRQ�ZLWK�(QWHUSULVH�3RUWDO��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� ([SODLQ�WKH�FRQILJXUDWLRQ�VHWXS�EHWZHHQ�6$3�3RUWDO�

DQG�0'0��

�


SAP AG 2006

0'0�,QWHJUDWLRQ�ZLWK�(QWHUSULVH�3RUWDO��%XVLQHVV�6FHQDULR

� $V�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RX�PLJKW�ZDQW�WR�LPSOHPHQW�DQ�(QWHUSULVH�3RUWDO�DQG�NQRZ�KRZ�6$3�0'0�LQWHJUDWHV�ZLWK�\RXU�FRPSDQLHV�3RUWDO�

�


SAP AG 2006

3RUWDO�FRQWHQW�LV�DYDLODEOH�DV�D�EXVLQHVV�SDFNDJH�DQG�LQFOXGHV�ERWK�WHFKQRORJ\�FRPSRQHQWV�VXFK�DV�-DYD�L9LHZV�DQG�UHDG\�WR�XVH�SDJHV�DQG�ZRUNVHWV�

3RUWDO�%XVLQHVV�3DFNDJH��

�� ! "��#$��%�%�'&� ��'�� "��#$��(�%�'&

'HWDLOV6HDUFK�5HVXOW�L9LHZ,WHP�'HWDLOV�L9LHZ

) ��*'�,+��%�) ��'��*'�-+.��%� ) �(��/�(�103254��6�) ��%�703254��/�

�

� Enterprise Portal business packages include features such as: y Predefined portal content for shipped template repositories y Quick enablement of Web access to any repository through wizards y Search Result iView:

- Standardized access via Open Catalog Interface (OCI) y Item Details iView:

- Configurable arrangement of displayed information in tabs - Maintain, delete, and create master data objects - Grouping of fields in header and multiple tabs


SAP AG 2006

3RUWDO�%XVLQHVV�3DFNDJH��

6KLSSHG�3RUWDO�&RQWHQW

3UHGHILQHG�3RUWDO�5ROHV

3DJHV�DQG�:RUNVHWV

'RFXPHQWDWLRQ

'HWDLOV

�

� Shipped portal content includes: y Predefined portal roles

- Master Data Administrator - Master Data Expert - Business Expert - OCI Subscribers (for OCI usage)

y Pages and worksets - Includes ready-to-use worksets and pages for the shipped repositories - Customer, material, vendor, employee for searching, maintaining and analyzing master

data y Documentation

- Detailed documentation on customization of shipped content and configuration for user-specific repositories is available.


SAP AG 2006

6$3�3RUWDO�(QDEOHPHQW

'HVLJQ�WLPH

7KH�L9LHZ /LEUDU\�SURYLGHV�D�VHW�RI�L9LHZV�WR�VHDUFK�DQ�UHSRVLWRU\�LQ�PXOWLSOH�GLPHQVLRQV�

�

� The iView Library provides a set of iViews to search an MDM repository in multiple dimensions. � By mixing and matching iViews, portal administrators can design and configure a collection of

specialized portal pages for a specific set of user requirements, offering one or more highly tailored interfaces to the same or multiple MDM repositories.

� The iViews are: y Fully adaptive to the schema structure of the MDM repository to which they are connected y Fully collaborative with other iViews on the page


SAP AG 2006

+LHUDUFK\�VHDUFK )RU�VHOHFWLQJ�QRGHV�LQ�KLHUDUFKLFDO��WD[RQRP\�ORRNXS�WDEOHV

$WWULEXWH�VHDUFK )RU�VHOHFWLQJ�DWWULEXWH�YDOXHV�FRQQHFWHG�WR�WD[RQRP\�QRGHV

7H[W�VHDUFK )RU�SHUIRUPLQJ�D�IUHH�IRUP�NH\ZRUG�VHDUFK3LFN�OLVW�VHDUFK

+LHUDUFK\�VHDUFK

$WWULEXWH�VHDUFK

7H[W�VHDUFK

6$3�3RUWDO�L9LHZ ([DPSOHV��

3LFN�OLVW�VHDUFK )RU�VHOHFWLQJ�YDOXHV�IURP�IODW�RU�KLHUDUFKLFDO�ORRNXS�WDEOHV

�

� All iViews can be used multiple times. � Correlation is made between iView and repository.


SAP AG 2006

5HSRVLWRU\�6WDWXV�'LVSOD\

&RPSDULVRQ�9LHZ

4XDOLILHG�)LHOG�6HDUFK


([WHQGLQJ�H[LVWLQJ�0'0�L9LHZ IXQFWLRQDOLW\�

�

� Extending existing MDM iView functionality: y Search iViews: Free-form search iView and qualified field search y Display iViews: Comparison view and relationship display y Data entry and maintenance (CRUD) now includes hierarchy fields and qualified fields y First MDM consolidation functionality (key mapping iView) y Personalization (“My Basket,” saved search) y New administrative options and utilities (MDM online help, repository status display)


SAP AG 2006

7KH�IROORZLQJ�FDSDELOLWLHV�DUH�DOVR�DYDLODEOH�IRU�L9LHZV�

6HDUFK�VWDWH

5HVXOW�VHW,WHP�GHWDLOV

5HVXOW�VHW 6KRZ�WKH�FXUUHQW�UHVXOW�OLVW,WHP�GHWDLOV 6KRZ�UHFRUG�GHWDLOV�EDVHG�RQ�D�VHOHFWHG�UHFRUG�LQ�

WKH�UHVXOW�OLVW

6HDUFK�VWDWH 6KRZ�WKH�FXUUHQW�VHDUFK�VWDWH


�

� Infrastructure improvements: y Dataset infrastructure y iView editor wizards for maintenance and customization y Improved page refresh behavior and performance (client framework)) y Multilingual foundation: language independent connectivity y Portal content translation y Business package to include business partner and product objects y Integration with universal worklist (UWL) (display of workflow job records) y Inter-iView connectivity and UI integration (client-site eventing with MDM and non-MDM

iViews and Web applications)


SAP AG 2006

6$3�3RUWDO�(YHQWLQJ

�

� Based on the selected item in the Record Set iView, the details will be displayed in the Item Details iView.


SAP AG 2006

0'0�,QWHJUDWLRQ�ZLWK�(QWHUSULVH�3RUWDO��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8VH�WKH�3RUWDO�WR�DFFHVV�0'0�GDWD�

�


�([HUFLVHV�

8QLW�� 3RUWDO�,QWHJUDWLRQ�7RSLF�� 0'0�(QWHUSULVH�3RUWDO�,QWHJUDWLRQ�


• Explain the integration of MDM repository data into Enterprise Portal

As part of this implementation, you might want to implement an Enterprise Portal and know how SAP MDM integrates with your companies Portal to provide a “thin client” environment for Data Manager users.

3XUSRVH�This script describes the integration of MDM with the SAP NetWeaver Portal.

3UHUHTXLVLWHV��• MDM Repository has been supplied to you and is ready for importing

• MDM Server has been mounted and started

• SAP NetWeaver Portal is running

• MDM Business Packages have been installed on the Portal

• Create a user in your repository which is assigned the Admin role and has a password of your choosing (must not be blank).

Example: Admin2

PWD: Training

Roles: Admin

• Repository "yourletter_CaseStudy" is running


20-1 /RJRQ�WR�WKH 3RUWDO�*R�WR�WKH�&RQVROH�DQG�LQ�WKH�&RQVROH�+LHUDUFK\�ILQG�\RXU�UHSRVLWRU\��([SDQG�WKH�$GPLQ�QRGH�DQG�VHOHFW�WKH�8VHUV�WDEOH��,Q�WKH�OLVW�RI�XVHUV��ILQG�WKH�XVHU�3RUWDO�DQG�FKDQJH�WKH�SDVVZRUG WUDLQLQJ��

20-1-1 Log on to the Portal as shown below with user ID: mdm100-## and password: training. Your instructor will provide the URL and the number to be substituted for ##.

It will be necessary for you to change your initial password, and so you will be presented with the following screen:

Reenter your initial password, and then enter your new password twice. Once logged in, you will be presented with the following:


20-2 &UHDWH�D�6\VWHP�2EMHFW

Create a system object using the system administration role in the Portal.

20-2-1 In top-level navigation, select the System Administration role. Then select the workset System Configuration.

20-2-2 In the central part of the screen, expand the folder Portal Content.

20-2-3 Right click on the folder MDM100, and select New Æ System (from template).


20-2-4 This will start the New System wizard. In Step 1: Template Selection, choose the template MDM System. Choose Next.

20-2-5 In Step 2: General Properties enter the System Name and System ID. Use “MDM_<your_server_name>_<your_letter>”, e.g. MDM_twdf0125_A. Click Next.

20-2-6 In Step 3: MDM Server Properties, enter the name of your MDM Server, e.g.

twdf0125. Leave the password field blank. Choose Next.

20-2-7 In Step 4: Select Repository, choose your case study repository from the drop down list. Choose Next.

20-2-8 In Step 5: Select Language, leave the default value and choose Next.

20-2-9 In Step 6: Summary your screen should look like this. Choose Finish.


20-2-10 On the next screen select the first radio button Open the object for editing.

20-2-11 You should now be presented with the following screen:

From the Display drop down list, select System Aliases.


20-2-12 For the system alias, enter a unique value, perhaps something like MDM_<your_server>_<your_letter>. Choose Add.

20-2-13 Choose Save. You are now ready to setup your user mapping.

20-3 6HW�WKH�8VHU�0DSSLQJ

Set the User Mapping In order for the Portal to access your repository, the Portal must supply user credentials to your repository by user mapping.

20-3-1 In top-level navigation, choose User Administration.�20-3-2 Under Identity Management, you should see a search page. Enter your user

Portal user ID and choose Go.


20-3-3 Select your user in the list. You should see the following screen.

20-3-4 In the bottom half of the screen select the tabstrip User Mapping for System Access (you may need to use the scroll icon to scroll through the tabs--User Mapping for System Access is the last tab). Click on Modify, and select your MDM System Alias from the list. Under mapping data enter the user and the password from your MDM repository which you created in the Console in the first step (Admin2/Training). Click Save.


20-4 &UHDWH�ILUVW�L9LHZ

We now need to create the iViews, and then arrange these iViews on a portal page. We will start with an iView to enable keyword search in your Case Study repository.

20-4-1 In top level navigation, choose Content Administration. This will take you to the Portal Content Studio. Expand the folder Portal Content, and locate the folder MDM100.

20-4-2 Right click on the MDM100 folder and choose New Æ iView. This will start

the iView wizard. On the first screen leave the defaults and click Next.

20-4-3 In the next screen, Step 1, choose the template MDM Search texts. Click

Next.


20-4-4 In the next screen, Step 2, enter a name and unique ID for the iView, perhaps MDM_<your_letter>_Text_Search.

20-4-5 In Step 3, select the Alias for your MDM server from the dropdown list. Click Next.

20-4-6 In Step 4, choose the table that you want to perform the text search on. This should be the main table.

20-4-7 In Step 5, choose the fields that you want to search by keywords. The diagram below is based on the Exercise_Master repository, and so the field names are different.

20-4-8 On the summary screen, choose Finish. In the final step of the iView wizard, choose the radio button ‘Open object for editing’ and click OK. You should see the following screen:

Note that you can change the fields that will available in your iView from here if

you need to. Click on Preview to see your new iView.


Congratulations on creating your first iView!

20-5 &UHDWH�DGGLWLRQDO�L9LHZV We now need to create additional iViews. These next steps will allow you to create iViews to enable further searching, and also see the results of the search, and finally to view the record details.

20-5-1 Close your iView preview, and on the iView maintenance screen, choose Close. Now repeat steps 20-4-1 and 20-4-2 from above.

20-5-2 This time the iView template to select is the MDM Hierarchy Search template.

20-5-3 Create a new iView using the template MDM Result Set, and call it MDM_<your_letter>_Result_Set. In Step 5 of the Wizard choose the option Table Records.

20-5-4 In Step 6, leave the default value Yes. In Step 7, you have the ability to choose which fields will appear in the result set. Choose the fields Product ID, Product Name and Manufacturer Hierarchy.

20-5-5 In Step 8, choose whether you would like users of this iView to be allowed to perform a comparison. If you choose Yes, in Step 9 you will be asked to choose which fields will be used in the comparison.

20-5-6 In Step 10, choose No. We will not be using OCI integration with our iView.

20-5-7 On the summary page, choose Finish, and on the final screen of the wizard choose the radio button to open the object for editing, and click OK. Note the options for maintaining this iView, such as setting column widths. Preview your iView. Once finished, Close the iView.

20-5-8 Create a new iView based on the template MDM Item Details. Call the iView MDM_<your_letter>_Item_Details.

20-5-9 In Step 5 of the Wizard, you can choose whether your iView supports creation of new records, editing of existing records, and/or deletion of records. Mark all these fields as Yes. Click Next.


20-5-10 Over the next steps of the iView wizard you get to design the layout of your iView. This iView has a header area, which may include multiple columns, and then a data area which is broken up into tabstrips, where each tabstrip can also have multiple columns. Using the settings you can also set the changeability and position of each field. The example below explains this layout. Arrange your fields to your liking.

20-5-11 Once complete, again choose the radio button to open the object for editing,

and click OK. Once again, take note of the maintenance options available. A preview at this point is not appropriate. Why not? Close the iView.

20-6 &UHDWH�3RUWDO�SDJH

The last thing we need to do here is to create a page to group together the iViews

20-6-1 Right click on the folder MDM100 and choose New Æ Page. In the first step give your page a name and ID – use something like MDM_<your_letter>_Page. Click Next.

20-6-2 In Step 2, use the default page template.

20-6-3 In Step 3, choose the layout for your page. Normally 2 Columns (Narrow:Wide) works well here.

20-6-4 On the summary page click on Finish. The option to open for object for editing will be selected by default. Leave this as is, and click OK.

20-6-5 On the page maintenance screen we need now to add the iViews. With the page maintenance open, right click on the Text Search iView in the Portal directory, and choose Add iView to Page Æ Delta Link.

'DWD�DUHD�

+HDGHU�DUHD�


20-6-6 The iView should now appear on the page, as shown above. Repeat for the

other iViews. Once all iViews are added, click on Save, and then change to the Page Layout screen using the radio buttons marked above.

20-6-7 Using drag and drop, arrange the iViews between the page columns as shown below:

Choose preview to see your page. You’ve now completed your MDM portal page!

�


SAP AG 2006

2SHQ�&DWDORJ ,QWHJUDWLRQ





3HUIRUPDQFH




�


SAP AG 2006

&RQWHQWV�� ,QWHJUDWLRQ�RI�0'0�5HSRVLWRU\�YLD�2SHQ�&DWDORJ ,QWHUIDFH�

�2&,�

2&,�,QWHJUDWLRQ

�


SAP AG 2006

2&,�,QWHJUDWLRQ��/HVVRQ�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�OHVVRQ��\RX�ZLOO�EH�DEOH�WR�� 'HVFULEH�2&,�,QWHJUDWLRQ

�


SAP AG 2006

2&,�,QWHJUDWLRQ��%XVLQHVV�6FHQDULR

� 3RRU�GDWD�V\QFKURQL]DWLRQ�EHWZHHQ�\RXU�FRPSDQ\¶V�V\VWHPV�KDV�UHVXOWHG�LQ�VORZ�DQG�LQDFFXUDWH�SDUWQHU�DQG�VXSSOLHU�FRPPXQLFDWLRQV��<RXU�FRPSDQ\�KDV�GHFLGHG�WKDW�LW�QHHGV�D�0DVWHU�'DWD�0DQDJHPHQW�VROXWLRQ�WR�DOOHYLDWH�WKHVH�SUREOHPV��DQG�KDV�GHFLGHG�WR�LPSOHPHQW�6$3�0'0��

� $V�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RXU�FRPSDQ\�PLJKW�ZDQW�WR�LQWHJUDWH�LWV�ZHE�FDWDORJ�ZLWK�DQ�RUGHU�IXOILOOPHQW�V\VWHP�VR�\RXU�FXVWRPHUV�FDQ�RUGHU�GLUHFWO\��7R�WKLV�HQG�\RX�ZDQW�WR�OHDUQ�DERXW�WKH�2&,�LQWHUIDFH�ZKLFK�FDQ�PDNH�WKLV�SRVVLEOH��

�


SAP AG 2006

2&,�DV�SDUW�RI�53&0�%XVLQHVV�6FHQDULR

5LFK�3URGXFW�&RQWHQW�0DQDJHPHQW8:9!;=<>9�? @ A6BDC�E5FG6H EDBDCIEJFDE�; H @ G6K8:9�;D<59!? @ A/BDC�E5FG>H EDBDC�E5FDE6; H @ G>KL 9/B>AMA>BDC�BL 9/BJANA>BDC�B 8 H EJBDCIE L B=O59!PQC8 H EJBDCIE L B=O59!PQC

R P6S�? @ < K CT9VUWE/SR P6S�? @ < K CT9VUWE/S

R P/S6? @ < K CX9ZYJB/YJE HR P>S�? @ < K CT93Y5B/YJE H

[ 3DJH�OD\RXW�IRU�SURGXFW�FDWDORJV�Æ 6$3�0'0�3XEOLVKHU[ 5HWULHYH�SURGXFW�LQIRUPDWLRQ�IURP�D�6$3�0'0�UHSRVLWRU\�YLD�2&,� \I]Z^�_'`�acb�d(b'e f'gihI`�d%_'j%k(b�l�_�m

�


SAP AG 2006

53&0�² 2SHQ�&DWDORJ�,QWHUIDFH��2&,�

)HDWXUHVnporq ^'^�f�j%d�f�k:b'e�e�s�b�`�t'b�d�f�j%ui^�b'j%dTviw�`�]xaxh�^'j�f�d�f'l�f$enzy `�{�b�`!l�_!ti|}_�v q e d o _/d�w ~Mw _/��w d�{1]xaMh/l�b�^�b:��w�e�w d�w _�vn a�f�`�k�w g q j(_�d�{!_ o}�M�� _�dT��_�b��_'j}��r��]MaMh>��w b�w ~Vw _��w �/b'j�tn �3b�^1]xa�h5k�w _�e t'vZd(f�j(_'^�f!v�w d�f�j%uZk�w _'e t'v

n hI`�l'e q t'_�v1b�e�e�j�_�� q w�j�_�t"]MaMh5k q `�l�d�w f$`�b'eIw d%u�d(f�l�f�`�`�_!l�d:b�` o}�M�� _�dT��_�b��_'j��V�j�_�^�f�v:w d(f�j(u�d(f�b�� q v:w�`!_�v�v7b'^:^'e�w l�b�d�w f�`�f q d��%f!k(��d�{�_'�(�!f��

%HQHILWV

o _�b�j�l�{�k(f�j.^'j�f't q l/d%v�w�`7b'` o��N�� _�dT��_�b��_�j$�7�r��j(_'^!f'v:w d�f�j(u!�/b!t�t�d�{�_�s�d�f�bv!_'e _�l�d�w f�`�e�w v�d��>d�j(b�`�v�k�_�j'd�{�_7t�b/d(b3d�f�b1v:{�f�^:^'w�`�g�l�{�b'j%d��l�f�si^:e _�d%_�b'`�t�f�j�t'_�j�� q v�w�`�_�v�v1b'^�^�e�w l/b�d�w f$`�v"e�wI�5_ o}�x�"o |��3� o��M� aM|r��b'`'t�f'd�{�_�j�v1l�b:`�`�f��l�b'e�e6b'`o$�x� �1�r�j%_�^�f�v�w d�f�j(uZb�`�t q v�_�w d�b�v1b�`�_6�!d�_�j�`�b'e�^�j�f:t q l6d�l�b�d%b'e f�g� }��w b�]Maxh��8V

H�&DVH

¡ A6AZY H 9�A!P G CX<rCT9C K Er<5E6? E G C�@ 9�;�? @ <JC¡ A6AZY H 9�A�P G CX<cC�9C K Er<JE/? E G C�@ 9�;�? @ <JC

8�B/? ?¢B/;c£ ¡.R3¤ EDC�¥�EJBQ¦5E H§�¨'§ H E6Y>95<�@ C�9 H O©�<5EJB HXG>KWª 9 H Y H 9�A�P G C�<8�B/? ?«B/;c£ ¡.R3¤ E=CI¥�EJBQ¦5E H§�¨'§ H E�Y>95<�@ CX9 H O©1<5EDB HIG6KWª 9 H Y H 9�A�P G C�<

¬ H B6;=< ª E H Y H 9�A�P G CX<WC�9C K Ec< K 9!Y/Y�@ ;D G B H C9 ª C K ExS6PD</@ ;=EJ<J<rB�Y>Y�? ®¬ H B6;=< ª E H Y H 9�A�P G CX<WC�9C K Ec< K 9!Y/Y�@ ;D G B H C9 ª C K ExS6P=<�@ ;=EJ<D<�B�Y>Y/? ® 8�9/¯NY�? E=CTEWB/;JAM° H A/E H8�9�¯NY�? EDCTEWB/;JAM° H A/E H

± 8$PQ<5CX9�¯�E H�G B/;�? E=¦JE H B56EcC K Er£ ¡}RN§�¨�§ G BJCIB/? 96 ª P/; G C%@ 9!;=B/? @ CIOWU K @ G�K @ <rBr<�P6SD<5EDC�9 ª £ ¡}RN§r¨�§ ®

$FFHVV�XQLILHG�SURGXFW�GDWD�YLD�2&,

�


SAP AG 2006

$UFKLWHFWXUH�2YHUYLHZ

650�6HUYHU

,QWUDQHW

6HUYLFH�3URYLGHU

8VHU

² ;QCTE H ;=E=C³ H 9>U}<5E H

,QWHUQHW

6HUYLFH�3URYLGHU

�

� The user here is working with an 650�6HUYHU�application, which displays the available catalogs. The user calls up one of these, selects the required products, and then transfers the product data back to the 650�6HUYHU�application


SAP AG 2006

´ � 7KH�650�6HUYHU�DSSOLFDWLQ VKRZV�WKH�DYDLODEOH�VHUYLFH�SURYLGHUV��SURGXFW�FDWDORJV�UHVS��YHQGRU�GLUHFWRULHV��

µ � $IWHU�WKH�XVHU�KDV�FKRVHQ�RQH�RI�WKHP��WKH�XVHU�ZLOO�EH�UGLUHFWHGWR�WKH�DFFRUGLQJ�ZHE�VLWH��7KHUIRUH WKH�SDUDPHWHUV�ZLOO�EH�XVHG��WKDW�KDYH�EHHQ�PDLQWDLQHG�LQ�WKH�650�6HUYHU�FXVWRPL]LQJ�SUHYLRXVO\�

2&,�� &DOO�RI�WKH�VHUYLFHV

650�6HUYHU

² ;QCTE H ;=E=C³ H 9>U}<5E H

6HUYLFH�3URYLGHU

¶ ®5·�¸ L B/;JAYJB H B>¯�EJC�E H <¹ ®6º ¬6¬�R H E>»�PJE=<JCU�@ C K ·�¸ L B/;JAYJB H B>¯VEDC�E H <

�

� In order for a product catalog to be called up via the Intranet or Internet, its URL must be known in the 650�6HUYHU. If the product catalog requires additional parameters for the call-up (for example, log-on names or language identifier), these must also be known in the 650�6HUYHU�before the call-up.


SAP AG 2006

´ � 7KH�VHUYLFH�SURYLGHU�FUHDWHV�D�+70/�SDJH�FRQWDLQLQJ�RFL�RSLFRPSOLDQW�GDWD�

µ � 7KH�XVHU�VHQGV�WKLV�GDWD�WR�WKH�650�6HUYHU�¼ � 7KH�650�6HUYHU�DSSOLFDWLRQ�WDNHV�RYHU�WKLV�GDWD�

6HQGLQJ�'DWD�WR�WKH�6$3�650�6HUYHU�$SSOLFDWLRQ

650�6HUYHU

² ;QCTE H ;=E=C³ H 9>U}<5E H

6HUYLFH�3URYLGHU

½ ®5º ¬�¬�R ¸!E5»�PJE=<DCUV@ C KWª 9 H ¯¾A6BDCXB¶ ®5¿>9 H ¯ G 9!;QCTB6@ ;6@ ;J°}8 ² À ° R�² A>BJCXBM@ ;cBº ¬!§�L YJBJ/E

¹ ®«<�P6S6¯x@ C

�

� A HTML form is used to transfer the selected product data to the 650�6HUYHU. This form is part of a HTML page that must be created by the catalog. This page (the last page that is displayed by the catalog) is sent to the user’s browser. The user can now send the form from this page to the 650�6HUYHU�application that then takes over the form data.

� In order that you can transfer the data from the catalog to the 650�6HUYHU�via the user’s browser, the return URL must be inserted into the $FWLRQ�attribute of the HTML form created by the catalog (the $FWLRQ�attribute of the form is the URL to which the form data is sent).

� The data to be transferred is transported within the input fields of the form; the field names must adhere to the syntax specified below. The 7\SH�attribute of the input fields should be WH[W�or KLGGHQ. The HTTP method recommended in all cases is POST because using GET can lead to browser-dependent length restrictions.


SAP AG 2006

6HWWLQJV�LQ�WKH�650�6HUYHU

�

� The URL and the catalog parameters are defined in the Implementation Guide (IMG) for 6XSSOLHU�5HODWLRQVKLS�0DQDJHPHQW��650�6HUYHU� �0DVWHU�'DWD� �'HILQH�([WHUQDO�:HE�6HUYLFHV��&DWDORJV��9HQGRU�/LVWV�HWF��. In the technical settings you can set GET or POST as the HTTP method for the call-up, the standard value is POST. The user’ s browser is then used to call up the catalog using the URL and the parameters.

� Depending on the situation, other parameters besides those defined in the Implementation Guide (IMG) for 6XSSOLHU�5HODWLRQVKLS�0DQDJHPHQW�can also be transferred to the catalog on call-up. These might be, for example, to provide the catalog with generic data or to trigger specific functions in the catalog.

� You can find the complete documentation on these in the description of the IMG activity ('HILQH�([WHUQDO�:HE�6HUYLFHV��&DWDORJV��9HQGRU�/LVWV�HWF��.

� The return URL is required so that the data from the catalog can be transferred back to the 650�6HUYHU�application via the user’ s browser. The catalog must place it in the $FWLRQ�attribute of the transfer form. The return URL is also transferred to the catalog as a parameter. It usually contains other parameters (see below) that must first be extracted and placed in separate input fields (of type KLGGHQ) of the form.


SAP AG 2006

2&,�² )XUWKHU�,QIRUPDWLRQ7HFKQLFDO�'HWDLOV

L9LHZ�:L]DUG�WR�FRQILJXUH�6$3�0'0�2&,ÁJÂ�Ã�Ä ÅÆÂ:Å¢ÇÆÈ�Â'ÇÆÅ�É$Ä É

Ê>Ë Â�Ì�Ä Ã Í�Î Â Ë«Ï«Ð Ä Ñ Ï Î Í

Ê ÂÆÒ Â�Ì�Ñ Ð Â�ÇÆÎ Ì¢Ó'Ñ ÇÆÔ¢Ò Â

Õ Ó ÏQÐ Â!ÉDÄ Ð«Ë Ò Ç�Í:Ì Ï Ò ÖQÈ�Å Ð

Õ>Ï ÅÆÃ�Ä Î�È3× Õ6Ø�Ð Ö Ë¢Ë¢Ï Î Ñ

Ù!Ç Ë × Õ/Ø Ú Ì�Ç�Ñ ÇÆÒ ÏQÛ Ã�Ä Â�Ò É Ð

Õ Ó¢Â�ÌÆÜ�Ì Ï ÅÆÃ Ä Û Ö«Î Ç�Ñ�Ä Ï Å

&RQILJXUDWLRQ�LQ�H�J��6$3�650ÁJÂ�Ã�Ä ÅÆÂ!Ý'Â�Ô Ð ÂÆÎ ÞÆÄ Ì�Â Ð

Ù!Ç¢Ä ÅÆÑ Ç�Ä Å�Ì�ÇÆÒ Ò Ð Ñ Î�Ö¢Ì�Ñ�ÖQÎ Â

ß/É«É Ê ß�à.áJÂ�Ñ âWÂ�Ç�Þ�ÂÆÎÙ'Á6ÙNÌ�Ç�Ñ Ç�Ò ÏQÛ�ã6ä6å

�

� The OCI fields are mapped to the MDM repository fields in the Map OCI/catalog fields step above as part of the creation of the OCI compliant iViews.

� The following fields are required fields in all cases: y Either NEW_ITEM-DESCRIPTION[n] or NEW_ITEM-MATNR[n] must be filled. Only one

of the two should be filled. y NEW_ITEM-QUANTITY[n]

� The following fields are required fields depending on conditions: y NEW_ITEM-UNIT[n] if NEW_ITEM-MATNR[n] has not been filled y NEW_ITEM-CURRENCY[n] if NEW_ITEM-PRICE[n] has been filled y NEW_ITEM-EXT_SCHEMA_TYPE[n] if NEW_ITEM-EXT_CATEGORY_ID[n] or

NEW_ITEM-EXT_CATEGORY[n] are used y NEW_ITEM-EXT_QUOTE_ID[n] if NEW_ITEM-EXT_QUOTE_ITEM[n] has been used y NEW_ITEM-CONTRACT[n] if NEW_ITEM-CONTRACT_ITEM[n] has been used

� All other fields are optional. � There are four fields in the interface that describe product numbers:

y NEW_ITEM-MATNR[n]: The product number in the SRM System of the purchaser y NEW_ITEM-VENDORMAT[n]: The vendor’ s product number y NEW_ITEM-MANUFACTMAT[n]: The manufacturer’ s product number y NEW_ITEM-EXT_PRODUCT_ID[n]: The number that uniquely identifies the product in the

catalog. � These product numbers may not be mixed or used for other purposes; in particular the field

NEW_ITEM-MATNR[n] may only be filled if the product number in the customer system is known to the catalog.


SAP AG 2006

2&,�² $UFKLWHFWXUH�DQG�'DWD�)ORZo$�x��y `�d�_�j�^'j�w v�_ � f�j%d(b'e

� q v'w�`!_/v�v � ^:^�e�w l/b�d�w f$`�v�e�wI�5_ o��M�æo |r�

ç ½

|._'^�f'v�w d�f�j�u

¶ ¹è

8�B6? ? G BDCIB6? 9��U�@ C K ·:¸ L B/;DA3Y5B H B5¯�EDCXE H <º ¬/¬'R H ED»!P=ED<DC/UV@ C K ·�¸ L B/;JAZYDB H B6¯�EQCXE H <

¶¹

&DOOLQJ�WKH�H[WHUQDO�FDWDORJ

5HWXUQ�IURP�WKH�FDWDORJ¿59 H ¯ G 9�;=CXB/@ ;/@ ;JM°}8 ² A/BJCIBx@ ;�º ¬�§�LVé 9 H5ê §�LJë£�P6S>¯N@ C

½è

º ¬/¬'R H ED»!P=ED<DC/UV@ C K C K EVA6BDC�Bç

�

� The catalog is normally displayed in a separate browser window. This window is both opened and closed again via the SRM Server application.


SAP AG 2006

2&,�,QWHJUDWLRQ��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 'HVFULEH�2&,�,QWHJUDWLRQ

�


SAP AG 2006

;,�,QWHJUDWLRQ





3HUIRUPDQFH




�


SAP AG 2006

&RQWHQWV�� 6$3�1HW:HDYHU�;,�,QWHJUDWLRQ�ZLWK�0'0

6$3�1HW:HDYHU�;,�,QWHJUDWLRQ

�


SAP AG 2006

6$3�1HW:HDYHU�;,�,QWHJUDWLRQ��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� /LVW�WKH�FRPSRQHQWV�RI�6$3�1HW:HDYHU�;,� 'HVFULEH�WKH�6$3�1HW:HDYHU�;,�$GDSWHU�(QJLQH� /LVW�WKH�VWHSV�QHHGHG�WR�VHW�XS�WKH�FRQQHFWLRQ�

EHWZHHQ�WKH�0DVWHU�'DWD�6HUYHU��6$3�1HW:HDYHU�;,��DQG�UHPRWH�V\VWHPV

�


SAP AG 2006

6$3�1HW:HDYHU�;,�,QWHJUDWLRQ��%XVLQHVV�6FHQDULR

� $V�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RX�ZDQW�WR�NQRZ�KRZ�6$3�;,�FDQ�KHOS�LPSRUW�GDWD�WR�DQG�H[SRUW�GDWD�IURP�\RXU�6$3�0'0�UHSRVLWRULHV�

�


SAP AG 2006

$UFKLWHFWXUH DQG�&RPSRQHQWV,QWHJUDWLRQ�'LUHFWRU\0DMRU�6WHSV�IRU�,QWHJUDWLRQ

$UFKLWHFWXUH�DQG�&RPSRQHQWV

�


SAP AG 2006

,QWHJUDWLRQ�(QJLQH�%XV�,QIUDVWUXFWXUH6KDUHG�FHQWUDO�NQRZOHGJH�

VPDOO�QXPEHU�RI�SRLQW�WR�SRLQW�FRQQHFWLRQV

'LUHFW�&RQQHFWLRQV,QWHJUDWLRQ�FKDOOHQJH�&RPSOH[LW\�JURZLQJ�

TXDGUDWLFDOO\�

'DWDEDVH�,QWHJUDWLRQ,QWHJUDWLRQ�E\�VLQJOH�FHQWUDOL]HG�GDWD�

PRGHO

(QWHUSULVH�5HVRXUFH3ODQQLQJ

,QWHU�,QWUD�(QWHUSULVH&RRSHUDWLRQ

&ROODERUDWLYH%XVLQHVV

,QWHU�6\VWHP�,QWHJUDWLRQ�(YROXWLRQ

�

� How integration has evolved at SAP: � At first, there was single database integration in a single centralized data model – in one system with

several applications one database (for example, an R/3 system with MM, SD, CO, FI, HR, and so on), with the applications having access to the data structures across the components. Integration in this case is and was fairly easy.

� Then SAP and third-party vendors provided other solutions, such as CRM and SRM. These solutions and their respective systems needed to be integrated into the ERP environment (for example, an R/3 back-end system). This brought added complexity and the beginning of many individual point-to-point connections.

� With the SAP NetWeaver Exchange Infrastructure and collaborative business, SAP approaches the integration challenge from a different angle. The basic idea is to provide a runtime infrastructure that allows heterogeneous systems to be tied together with fewer connections and, at the same time, to connect those applications and let messages flow from one application to the other.

� SAP XI provides all the capabilities that an integration and applications platform requires to develop, integrate, and run solutions following an enterprise services architecture.


SAP AG 2006

aWb�e�ear_'`�d%_'j

y | �

ì _�l'{:`�w l�b'eo u�v�d(_�s�v�$í �

�îb'j��>_/d� `�b�e u�v�w v

ì j(b�t�wI`!g

o aM�

�Wf'l q s�_'`�d�îb'`�b�g�_!s�_�`�d

_�� o b'e _�v

y � � j(f�l q j(_!s�_�`�d

,QWHU�6\VWHP�(QDEOHG E\ 6$3�1HW:HDYHU ;,�

�

� SAP NetWeaver XI is the technology foundation that enables SAP to realize the enterprise services architecture vision. With SAP NetWeaver and the enterprise services architecture, you benefit from the next level of application flexibility, and the power to integrate solutions quickly across the enterprise and beyond.

� SAP NetWeaver XI enables users to: y Develop cross-system applications that exchange a multitude of system messages using the

runtime infrastructure offering synchronous or asynchronous communication y Develop new platform-independent interfaces or connect existing interfaces to the runtime using

adapters y Produce a bird’ s eye view of the collaboration process using business scenarios to derive the

interfaces and mappings required from them y Adjust message values and structures for the receiver using mappings y Centrally maintain the message flow between logical systems in the system landscape using

logical routing y Control system access using logon data y Describe the system landscape as the foundation for the description of the collaborative process

using System Landscape Directory content � SAP XI is based on general standards to enable external systems to integrate. At the center of the

infrastructure is an XML-based communication that uses HTTP. The application-specific contents are transferred in messages in a user-defined XML schema from the sender to the receiver using the Integration Server.


SAP AG 2006

,QWHJUDWLRQ�'LUHFWRU\


�


SAP AG 2006

£ ¡.R¡ Y�Y/? @ G B=C(@ 9�;

¬ K @ H A/ï R B H CIO¡ Y�Y/? @ G BDC�@ 9�;

¬ K @ H A�ï R B H C�O§ @ A6A!? EQUWB H E8:9�¯xY>9�;JE6;DC

§ B HTð E=C(Y/? B G E À³ PD</@ ;DED<J<R B H C�;=E H

,QWHJUDWLRQ�6HUYHU

6\VWHP�/DQGVFDSH�'LUHFWRU\��6/'�

� q v�w�`�_�v�v � j�f'l�_�v�v y `!g�wI`�_

h�`�d�_�g�j(b�d�w f�` y `!g�wI`�_

� t'b�^�d%_'j y `�g�w�`!_

| q `�d�w�s�_3�¾f�j��!_�`!l�{&HQWUDO�0RQLWRULQJ,QWHJUDWLRQ�%XLOGHU

,QWHJUDWLRQ5HSRVLWRU\

,QWHJUDWLRQ'LUHFWRU\

6$3�1HW:HDYHU ;,�$UFKLWHFWXUH

�

� Senders and receivers that exchange messages using the Integration Server are separated from one another. This separation makes it easier to connect systems that are technologically different. Every system that can exchange messages with the Integration Server can also exchange messages with all other systems connected to the Integration Server. SAP XI supports the following methods of communication with the Integration Server: y Direct communication using proxies, which you generate in the application systems using a

description in Web Services Description Language (WSDL) y Communication using adapters; in this case, you create interfaces for message exchange in the

application system, or use existing interfaces


SAP AG 2006

0'0�GHILQHG�DV�D�EXVLQHVV�V\VWHP

6$3�1HW:HDYHU ;,�6\VWHP�/DQGVFDSH�'LUHFWRU\

�

� The System Landscape Directory (SLD) is the central information provider in a system landscape. � The SLD contains two types of information: component information and information about all

available SAP products and components, including their versions. � If there are any third-party products in the system landscape, they are also registered here. At design

time of the integration objects, the component information is extracted from the SLD to define business scenarios.

� The landscape description contains all installed systems in a system landscape. When a collaborative business process is configured, the landscape description is needed to determine the system information of the business partners involved.

� You enter all the technical systems of the system landscape in the SLD. This includes host names and other technical attributes, as well as information on the software component installed on a server.

� Assign a business system name to each technical system. This business system name is required for scenario configuration as the name for the sender and receiver systems.


SAP AG 2006

6WUXFWXUH�RI�2XWERXQG�,QWHUIDFH

6WUXFWXUH�RI,QERXQG�,QWHUIDFH

+773 5)&

6WUXFWXUH�DQG�9DOXH�0DSSLQJ

&RQQHFWRU

&RQYHUVLRQ�WR5HFHLYHU�3URWRFRO

6$3�1HW:HDYHU ;,�,QWHJUDWLRQ�'LUHFWRU\��'HVLJQ�7LPH��

�

� When sender and receiver systems are of different types or from different suppliers, they often do not support the same communication methodology. Frequently, the interface structure of the output interface of the sending system deviates from the inbound structure of the inbound interface of the receiving system.

� In this case, the structure of the sending system must be transformed into the structure of the receiving system using a program or a connector system. In a mapping program, the suitable fields must be assigned to each other, allowing the field values to be converted. Some connector systems offer a graphic mapping tool to accomplish this.


SAP AG 2006

6$3�1HW:HDYHU ;,�,QWHJUDWLRQ�'LUHFWRU\��'HVLJQ�7LPH��

�

� The Integration Repository contains the interfaces of the software components you are using. In some cases, you can import them to the Integration Repository; in some cases, you have to create them manually.

� Save mapping rules for structure mapping and value mapping for each external interface. There is a graphical mapping tool for this purpose. Alternately, you can create mapping programs in Java or XSLT.

� The Integration Repository only stores information relating to the development objects of a software component. For these objects, it is not important whether and on which server the software component is actually installed.


SAP AG 2006

6\VWHP��5ROH��

3URFHVV6WHS

6\VWHP��5ROH��

3URFHVV6WHS

2XWERXQG,QWHUIDFH

,QERXQG�,QWHUIDFH

,QWHUIDFHV�8VHGDQG�&RUUHVSRQGLQJ�

0DSSLQJ

6$3�1HW:HDYHU ;,�,QWHJUDWLRQ�5HSRVLWRU\�'HVLJQ�7LPH��

�

� If business processes in a distributed system landscape are illustrated, then the sequence of the process steps must be guaranteed. This can take place manually or by utilizing workflow tools. For each system transition, an interface must be implemented. Either the sender system supports a technology that allows a message to be dispatched to a receiver system, or a middleware tool must be used.

� The Integration Repository contains the interfaces of the software components you are using. In some cases, you can import them to the Integration Repository; in some cases, you have to create them manually.

� Save mapping rules for structure mapping and value mapping for each external interface. There is a graphical mapping tool for this purpose. Alternately, you can create mapping programs in Java or XSLT


SAP AG 2006

6RIWZDUH&RPSRQHQW��

2XWERXQG,QWHUIDFH

,QERXQG,QWHUIDFH

,QWHJUDWLRQ�5HSRVLWRU\

2XWER

XQG�,

QWHUID

FH

,QERX

QG�,Q

WHUIDF

H

6WUXFWXUH6WUXFWXUHDQGDQG9DOXH9DOXH

0DSSLQJ0DSSLQJ



�

� The Integration Repository only stores information relating to the development objects of a software component. For these objects, it is not important whether and on which server the software component is actually installed.

� To implement business processes in a distributed system landscape, you have to configure business scenarios containing exact information on the business systems between which you want to send a message. The system saves this configuration in the Integration Directory. The rules define which business system and which inbound interface a document is sent to once it has been sent from a business system with a particular outbound interface to the Integration Server.


SAP AG 2006


%XVLQHVV�6\VWHP�%%XVLQHVV�6\VWHP�$

6HQGHU�6HUYLFH

5HFHLYHU6HUYLFH

2XWERXQG,QWHUIDFH

,QERXQG,QWHUIDFH



�

� The Integration Repository is a container for all interfaces, independent of platform. Definition of mappings for later use from the Integration Directory and proxy runtime also retrieves the information to create the proxy objects from this repository. Shared knowledge applications.

� The Integration Repository and Integration Directory are the central tools for the design and configuration of the collaborative process.

� The Integration Server has several functions, including receiver determination, mapping, and communication services (sending and receiving messages from other runtime components of SAP XI using HTTP). Without the Integration Server, there would be no communication.


SAP AG 2006

5HFHLYHU�GHWHUPLQDWLRQ�IRU�D�EXVLQHVV�V\VWHP

6$3�1HW:HDYHU ;,�,QWHJUDWLRQ�5HSRVLWRU\�'HVLJQ�7LPH��5HFHLYHU�'HWHUPLQDWLRQ


�


SAP AG 2006

:HE�$6�! ��$%$3�RU�-�((

:HE�$6�! ��$%$3�RU�-�((

)LOH

'DWDEDVH

6$3�� )LOH$GDSWHU

��$GDSWHU

,'RF,'RF$GDSWHU$GDSWHU

5)&5)&$GDSWHU$GDSWHU

��$GDSWHU

/RFDO�,QWHJUDWLRQ�(QJLQH�JHQHUDWHV��

UHFHLYHV�PHVVDJHV�LQ�;,�IRUPDW

6$3�1HW:HDYHU ;,�$GDSWHU�(QJLQH

�

� The Adapter Engine provides adapters, which you use to: y Communicate with SAP R/3 systems using the RFC adapter y Enable data exchange with the SAP Business Connector y Exchange data with external systems using a file interface or an FTP file server/FTP adapter y Access databases using a Java Database Connectivity (JDBC) adapter y Communicate with messaging systems using the Java Message Service adapter y Integrate remote clients or Web service providers using the SOAP adapter y Connect marketplaces and e-mail servers to the Integration Engine marketplace adapter

� The connected systems transfer IDocs to standard IDoc tRFC outbound processing or receive IDocs from standard IDoc tRFC inbound processing.

� No additional installations on business systems are required, but some configuration must be performed: y The IDoc type of the sender and receiver systems must be imported into the Integration

Repository. y The SAP XI IDoc ports of sender and receiver systems must be maintained on the Integration

Server. y In the System Landscape Directory, the logical system names of sender and receiver systems

must be assigned to the clients of the technical SAP systems.


SAP AG 2006

%XVLQHVV�6\VWHP�$ %XVLQHVV�6\VWHP�%


5HFHLYHU�,GHQWLILFDWLRQ

,QWHUIDFH�'HWHUPLQDWLRQ

0DSSLQJ


0HVVDJH�6SOLW

7HFKQLFDO�5RXWLQJ

&DOO�$GDSWHU

6$3�1HW:HDYHU ;,�,QWHJUDWLRQ�6HUYHU��5XQWLPH�

�

� The task of the exchange infrastructure is to receive messages for various master data clients (MDCs) or Master Data Servers (MDS) to process the messages and distribute them.

� XI has a pipeline service that ensures that the routing information will be analyzed, that the physical systems will be determined, and that the mapping activities are being executed

� The SAP NetWeaver Exchange Infrastructure (SAP XI) is the integration platform between the systems of a master data management system landscape. Integration occurs through the exchange of XML messages. SAP XI distributes (routing), transforms (mapping), and transports the messages that are exchanged between the systems.

� The processing procedure begins in the Integration Server pipeline as soon as the message reaches the Integration Server in XI format. y First, the receiver and the receiver inbound interface are determined using the configuration

data. This step is called logical routing. y Next, the pipeline determines the technical method for contacting the receiver. This is called

technical routing. If necessary, a mapping program is executed after configuration to map the outbound interface to the inbound interface.

y Finally, the message is sent to the target system or corresponding adapter.


SAP AG 2006

0DMRU�6WHSV�IRU�,QWHJUDWLRQ


�


SAP AG 2006

&RQILJXUDWLRQ��&RQQHFWLQJ�D�5HPRWH�6\VWHP

0DMRU�FRQILJXUDWLRQ�VWHSVñ 6$3�1HW:HDYHU�;,�FRQILJXUDWLRQ

ò 'HILQLWLRQ�RI�DOO�UHPRWH�V\VWHPV�LQ�6$3�1HW:HDYHU�;,�DQG�LQ�WKH�6\VWHP�/DQGVFDSH�'LUHFWRU\��6/'�

ò ,QVWDOODWLRQ�RI�6$3�1HW:HDYHU�;,�UHSRVLWRU\�FRQWHQW�IRU�6$3�0'0�VFHQDULRV

ò &RQILJXUDWLRQ�RI�LQWHJUDWLRQ�VFHQDULR�V��LQ�6$3�1HW:HDYHU�;,�GLUHFWRU\ñ 0'6�FRQILJXUDWLRQ

ò 'HILQLWLRQ�D�UHPRWH V\VWHP IRU HYHU\ V\VWHPò &UHDWLRQ�RI�VHQGLQJ�UHFHLYLQJ GLUHFWRU\ VWUXFWXUH IRU )73�VHUYHU XWLOL]LQJ

UHPRWH V\VWHP SRUWVò &UHDWLRQ�PRGLILFDWLRQ�RI�,PSRUW�DQG�6\QGLFDWLRQ�PDSV

ñ 6$3�1HW:HDYHU�;,�PDSSLQJò 0HVVDJH�URXWLQJ�DQG�PDSSLQJ��LI�QHFHVVDU\�

�

� Five steps need to be performed before any communication can be established. � With SAP XI 3.0 and MDM, you will deliver business scenarios that will already have some of the

steps implemented, but some are still to be performed by the user. y Step 1: Create business system as service. y Step 2: Create communication channel for each business service. If the system can communicate

through different channels, then create all possible channel types if necessary. y Step 3: Create receiver agreement between the systems. y Step 4: Interface determination:

- Here you see for the first time the software component mentioned; there are some special requirements regarding this software component in relation to the customizing ID mapping.

- To modify this software component, the customer needs to copy the SAP standard delivered software component into its own namespace. The customer is able to modify to create archives for the customized ID mapping.


SAP AG 2006

&RQQHFWLRQ�%HWZHHQ�6$3�1HW:HDYHU�;,�DQG�0'6

6$3�1HW:HDYHU6$36$3:HE�$6��:HE�$6��

óMô�õ'ö�÷%ø'ù}ú}û!ü�ý�û!ø

þVÿ��

ÿ��ó�ô'õ'ö�÷%ø'ù

� ��ó�ô�õ'ö!÷�ø�ù

��ó�ô'õ'ö�÷(ø�ù

�îõ��÷(ø�ù��.õ�÷(õ�îõ'û�õ�ü'ø��ø�û�÷��

��õ��ý�� ø�� !÷(ø��

!�" # $%�&�')(+*,$�-

�

� Receiver determination to complete the combination. � The mapping creates a relationship from one object to another one if the target object is clearly

defined. If there is more than one object on the target side, the mapping information has to be enhanced by some rules about how to identify the correct object. These rules are stored in the xpath information, where the rules have to be entered directly into the established communication agreement because they might only be valid for this particular combination.

� In MDM, you will see some of these xpath expressions. � Configure an FTP server on the MDS. � Create a send folder for outbound messages using outbound port(s) for remote system(s). � Create receive folder for inbound messages using inbound port(s) for remote system(s).


SAP AG 2006

&RQQHFWLRQ�%HWZHHQ�6$3�1HW:HDYHU�;,�DQG�5HPRWH�6\VWHPV

6$3�1HW:HDYHU6$36$3:HE�$6��:HE�$6��

ó�ô'õ'ö�÷(ø�ù}ú}û�ü�ý�û!ø

�$ó.�"þ�ÿ

ÿ,��óMô'õ�ö�÷%ø'ù

�/��óVô'õ�ö�÷%ø'ù

5HPRWH�6\VWHPV5HPRWH�6\VWHPV

6$3�:HE�$6��

��ó0�1� 23�54�� 6�� ó0�7�8�9�

6$3�:HE�$6�! ��

��ó0�1� 23�4�� :�;�ú.û�÷�ø�ù�ö�ù�ý ��ø

<óMô�õ'ö�÷%ø'ù

��/õ��JþVÿ

�

� Image shows a mixture of two approaches: 1. Use the central adapter engine on the integration server and connect to the MDM server machine

via an FTP server. 2. install an adapter engine locally on the MDM server machine and access the distributions folder

locally � Remote systems running on SAP Web AS < 6.40 connect to SAP XI via the IDoc adapter. � Remote systems running on Web AS >= 6.40 can also connect to SAP XI via a local integration

engine and proxies. If proxies are used, the same configuration as with MDS is needed.


SAP AG 2006

6$3�1HW:HDYHU�;,�,QWHJUDWLRQ��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� /LVW�WKH�FRPSRQHQWV�RI�6$3�1HW:HDYHU�;,� 'HVFULEH�WKH�6$3�1HW:HDYHU�;,�$GDSWHU�(QJLQH� /LVW�WKH�VWHSV�QHHGHG�WR�VHW�XS�WKH�FRQQHFWLRQ�

EHWZHHQ�WKH�0DVWHU�'DWD�6HUYHU��6$3�1HW:HDYHU�;,��DQG�UHPRWH�V\VWHPV

�


SAP AG 2006

(&&�&RPPXQLFDWLRQ





3HUIRUPDQFH




�


SAP AG 2006

&RQWHQWV�� 6$3�(QWHUSULVH�&HQWUDO�&RPSRQHQW��(&&��&RPPXQLFDWLRQ�

ZLWK�0'0

6$3�(&&�&RPPXQLFDWLRQ�ZLWK�0'0

�


SAP AG 2006

6$3�(&&�&RPPXQLFDWLRQ�ZLWK�0'0��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�0'0�SUHGHILQHG�FRQWHQW�LV�WLHG�

FORVHO\�ZLWK�6$3�(&&

�


SAP AG 2006

6$3�(&&�&RPPXQLFDWLRQ�ZLWK�0'0��%XVLQHVV�6FHQDULR

� $V�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RX�ZDQW�WR�NQRZ�KRZ�WR�FRPPXQLFDWH�GDWD�IURP�\RXU�6$3�(&&�V\VWHP�V��WR�6$3�0'0�IRU�FRQVROLGDWLRQ�DQG�RU�KDUPRQL]DWLRQ�

� 7KLV�FRPPXQLFDWLRQ�ZLOO�EH�LPSRUWDQW�ZKHQHYHU�\RXU�FRPSDQ\�GHFLGHV�WR�LPSOHPHQW�WKH�,7�VFHQDULR��&HQWUDO�0DVWHU�'DWD�0DQDJHPHQW�

�


SAP AG 2006

5HPRWH�6\VWHP�&RQQHFWLYLW\�WR�0'0

0'6

,1%281',17(5�

287%281',17(5�

=?>�@BAC�A0DFE DGIH�J > GLKMH =ONP�Q @ H =SR N HTPVUR W�X HY W)CJ�G R Q WON�= U =ON Q A@ HTP N> P+J�K R Z QP�Q >[C U=?NL>MN Y =GFH[\

5HPRWH6\VWHP�H�J��5��

!O]^_ $)- `+$)-

�$ó.�"þ�ÿ

þa�b��/��a;ÿc��;ø�÷dT�

ImportServer

SyndicationServer

��8�2(ÿ��

'%

�

� The SAP ECC plug-in PI_Basis enables the use of mass IDocs for extraction of master data objects. � SAP ECC object deltas can be sent to MDM via a push scenario. � Change pointer in SAP ECC can trigger extraction. � Utilization of MDM remote system port concept.


SAP AG 2006

7UDQVDFWLRQ�FRGH��0'0B&/17B(;75

&RPPXQLFDWLRQ�ZLWK�6$3�(&&

�

� The SAP ECC plug-in PI_Basis enables the use of mass (or bulk) IDocs for the object types: y Material: MATMDM y Customer: DEBMDM y Supplier (Vendor): CREMDM

� Mass IDocs are generated using transaction code mdm_clnt_extr.


SAP AG 2006

&RPPXQLFDWLRQ�LQ�6$3�(&&

Distributing Master DataConsolidating Master DataLoading Master Data

e�$Sfag�*3$h?i+h *3$�fj$Mk l[k m_ %�^5n�opo�q

r/srsT'?*3'tr�')uO'Ml�$)-r srv f.(Mg�-�*r�')uO'Ml)$�-_ %B^awxv

r/sr_ i u+&[" yO'?*zg�-

{ |I} N+~�� V�L��~L��I�c~ �� O�{ ��} =O�I�I� ��F�p��~ �� I�x�L��I�� T� ��R

{ D } =?��I� ��~��?�� x�p��I��V��T� �x�� I��

{ �I}?G �F�I��V�� I�� ~ �O�0�c� � �� { �I} N+~ �� ?~��I�� p�I� ��O�d� �I�I� �

{ �I} =+�I��~ ��F� �p��~ �?�� V��F� � ��O�� I�I� �� ~ �I�I� � �F�� { I}VJ �F��L��+~L��V��V�� L�V�I� �

{ ¡I¡�} =?��I� �� V��V�T�?�� { ¡�|�} =?��I� ��~ �L�� p��I��L��T� �p� �F~ �V��I�I� �F�x¢��L� � � �p� �� £�¤�¥z¦I§©¨�ª�§�«�¤�¦�§©¨[�� E

{ ¡�¬I} AT��I��~ �I��I� �O~c��x��+�©��I�� p� �� I�I� ��

{ ¡��} =?��I� ��~ �I�I�F� �I��I�I�V�I�

{ �} =O�I�� 0�c~ �F��I� �?~��p�p��L�� x��A G

7\SLFDO�FRPPXQLFDWLRQ�LQ�6$3�(&&�XVLQJ�6$3�;,

{ ¡�}?P �I��?~ � � ��V��L�� I�

�

� Local extraction is the push scenario for SAP ECC objects. The SAP ECC extractors can be used to send data from SAP ECC and fill the new SAP MDM-specific bulk IDocs.

� Delta load from SAP ECC uses a selection of data according to change pointers in SAP ECC. � Mass IDocs to enable SAP ECC communication are available for inbound to MDM.�


SAP AG 2006

0DWUL[�3URGXFW

Visualize product variants from SAP ECC and or other systems to consolidate and maintain this particular type of product quickly and efficiently. Upload matrix products, add new variants and masters to consolidate information. Publish in Web catalogs, print catalogs, or distribute to connected systems.

8VH�&

DVH

ñ '\QDPLF�FUHDWLRQ�DQG�PDLQWHQDQFH�RI�SURGXFW�YDULDQWVñ 6$3�(&&�5HWDLO�YDULDQW�DUWLFOH��VHW�DUWLFOH��GLVSOD\�DUWLFOH��SUH�SDFNHG�

DUWLFOH��VLQJOH�DUWLFOHñ 6$3�(&&�5HWDLO�FKDUDFWHULVWLFV�DQG�PHUFKDQGLVH�KLHUDUFKLHV�LQ�

LQERXQG�DQG�RXWERXQG�SURFHVV�DYDLODEOHñ 5HWDLO�%20�VXSSRUWHG�LQ�LQERXQG�DQG�RXWERXQG�SURFHVVñ 'HOWD�XSGDWH�IURP�6$3�(&&

)HDWXUHV

®�¯S° ±�²V³a³S²�´z²®�¯S° ±�²V³a³S²�´z²µ[¶ ° ¶L· ´�³M²L´,² ´3± ¶L¸ ´º¹3² · ´µ[¶ ° ¶O· ´�³M²L´,² ´,± ¶L¸ ´º¹3² · ´ » ²O¼ ½+´,²+¼ ½ ³S²�´3²�¾· ±�½O¿?±)° ¼ ³M²V´ ¶ ³M²L´,²S¾· ¹ ¶ ²V´ ¶9ÀV¶FÁaÂ ²?¯�¯M¼ ½OÃ» ²+¼ ½O´3²+¼ ½ ³+²V´3²S¾· ±�½O¿?±)° ¼ ³S²L´ ¶ ³M²L´,²S¾· ¹ ¶ ²V´ ¶9ÀL¶FÁaÂ ²?¯�¯M¼ ½OÃ

Ä ¸ ´º¹º² · ´�³�²�´3²BÅ3¹,± Â¹ ¶ ¯+±M¿M¼ ´3±)¹ ÁÆ ¼ ² µ)Á ½O³)¼ · ²F´3±�¹Ä ¸ ´º¹3² · ´�³�²�´3²BÅ3¹,± Â¹ ¶ ¯+±M¿+¼ ´,±)¹ ÁÆ ¼ ² µ)Á ½O³)¼ · ²F´,±�¹

®T¯M° ±�²L³ ´,±µ�Ç�È ÄSÉÉ®T¯M° ±�²L³ ´,±µ�Ç�È Ä�ÉÉ

0'0

�


SAP AG 2006

0DWUL[�3URGXFW�'HWDLOV

ñ 6$3�GHOLYHUV�D�PDWUL[�HQDEOHG�UHSRVLWRU\�ò ([WUDFWLRQ�UHSRUWV�WR�UHWULHYH�WKH�YDULRXV�GDWD�

IURP�6$3�(&&�5HWDLO� FKHFN�WDEOHV��PHUFKDQGLVH�KLHUDUFK\��FKDUDFWHULVWLFV

ò 0'0�,PSRUW�0DQDJHU�PDSV�WR�XSORDG�GDWD�LQWR�0'0�UHSRVLWRU\

ò 7KH�:HE�DSSOLFDWLRQ�WR�LPSRUW�WKH�KLHUDUFK\�DQG�FKDUDFWHULVWLF�LQIRUPDWLRQ�LQWR�WKH�UHSRVLWRU\

ò :HE�$6�EDVHG�IXQFWLRQDOLW\�WR�VXSSRUW�0DWUL[�SURGXFW�PDLQWHQDQFH�DQG�FUHDWLRQ

ò )XOO�VXSSRUW�RI�WD[RQRP\�HQULFKPHQWò $OO�NQRZQ�IHDWXUHV�RI�WKH�SDUDPHWULF�VHDUFK

Ê )XOO�VXSSRUW�RI�OD\RXW�DQG�SULQWLQJ�IHDWXUHV

�


SAP AG 2006

1HZ�%XVLQHVV�&RQWHQW��3URGXFW��

3URGXFW�'DWD�0RGHO�'HOLYHUHG�DV�0'0�5HSRVLWRU\ñ 0DWFKLQJ�UHOHYDQW�ILHOGV�

�*7,1��'HVFULSWLRQ��%DVH�820��3URGXFW�7\SH��7D[��&DWHJRULHV��&ODVVLILFDWLRQ��0DQXIDFWXUHU�,QIRUPDWLRQ��DQG�VR�RQ�

ñ ,PSRUW�PDSV�WR�ORDG�UHIHUHQFH�GDWD�DQG�SURGXFW�PDVWHU�GDWD

ñ 5HPRWH�V\VWHP�H[WUDFWRUVñ ;6'�ILOHVñ 3RUWV

�


SAP AG 2006

� 6XSSRUWV�H[WHUQDO�DQG�LQWHUQDO�FODVVLILFDWLRQVÊ &50��650��(&&�FDWHJRULHV�DQG�KLHUDUFKLHVÊ H&ODVVÊ 81636&

� $VVLJQPHQW�RI�SURGXFW�UHFRUGV�WR�PXOWLSOH�FODVVHV� $VVLJQPHQW�RI�SURGXFW�UHFRUGV�WR�LQQHU�QRGH�FODVVHV�LQ�

6$3�(&&��KLHUDUFK\�ILHOGV�� 3UHGHILQHG�V\QGLFDWLRQ�PDSV�IRU�%,�LQWHJUDWLRQ� 1HZ�6$3�1HW:HDYHU�;,�FRQWHQW��ZKLFK�VXSSRUWV�D�IDVW�

FRQILJXUDWLRQ�RI�PDVWHU�GDWD�H[FKDQJH�EHWZHHQ�V\VWHPV

1HZ�%XVLQHVV�&RQWHQW��3URGXFW��

�


SAP AG 2006

1HZ�%XVLQHVV�&RQWHQW��%XVLQHVV�3DUWQHU

%XVLQHVV�3DUWQHU�'DWD�0RGHO�'HOLYHUHG�DV�0'0�5HSRVLWRU\ñ 0DWFKLQJ�UHOHYDQW�ILHOGV�

�&RPPRQ�'DWD��$GGUHVVHV��&RPPXQLFDWLRQ�'DWD��5ROHV��DQG�VR�RQ�

ñ (QDEOHV�GHSRVLWLQJ�RI�DGGLWLRQDO�XQLTXH�LGHQWLILFDWLRQ�QXPEHUV��H�J��'XQ��%UDGVWUHHW�,'�

ñ ,PSRUW�PDSV�WR�ORDG�UHIHUHQFH�GDWD�DQG�EXVLQHVV�SDUWQHU�PDVWHU�GDWD�

ñ 5HPRWH�V\VWHP�H[WUDFWRUVñ ;6'�ILOHVñ 3RUWV

�


SAP AG 2006

6$3�(&&�&RPPXQLFDWLRQ�ZLWK�0'0��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�KRZ�0'0�SUHGHILQHG�FRQWHQW�LV�WLHG�

FORVHO\�ZLWK�6$3�(&&

�


SAP AG 2006

%,�,QWHJUDWLRQ





3HUIRUPDQFH




�


SAP AG 2006

&RQWHQWV�� 6$3�%,�,QWHJUDWLRQ

6$3�%,�,QWHJUDWLRQ

�


SAP AG 2006

6$3�%,�,QWHJUDWLRQ��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 'HVFULEH�WKH�LQWHJUDWLRQ�RI�0'0�ZLWK�6$3�%,

�


SAP AG 2006

6$3�%,�,QWHJUDWLRQ��%XVLQHVV�6FHQDULR

� $V�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RX�ZDQW�WR�KDUPRQL]H�\RXU�PDVWHU�GDWD�ZLWK�\RXU�6$3�%,�V\VWHP�DQG�\RX�ZDQW�WR�NQRZ�KRZ�6$3�0'0�LQWHJUDWHV�ZLWK�\RXU�6$3�%,�V\VWHP�

�


SAP AG 2006

6$3�%,�,QWHJUDWLRQ��5DWLRQDOH

:K\�VKRXOG�EXVLQHVVHV�LQFRUSRUDWH�

PDVWHU�GDWD�PDQDJHPHQW�LQWR�WKHLU�H[LVWLQJ�%,�SURFHVVHV"

7KH�DQVZHU�LV��'DWD�4XDOLW\�

�


SAP AG 2006

6$3�%,�,QWHJUDWLRQ��,PSDFW�RI�'DWD�4XDOLW\��

0DVWHU�GDWD�TXDOLW\�KDV�DQ�LPSDFW�RQ�WUDQVDFWLRQDO�DQG�DQDO\WLFDO�GDWD

� ,QDFFXUDWH�PDVWHU�GDWD�FDQ�KDPSHU�JR�WR�PDUNHW�HIIHFWLYHQHVV�

� ,QDFFXUDWH�PDVWHU�GDWD�LPSDFWV�FXVWRPHU�IDFLQJ�WUDQVDFWLRQV

� 6XSSOLHU�GDWD�SUREOHPV�OHDG�WR�VXE�RSWLPDO�SURFXUHPHQW�GHFLVLRQV

� /DFN�RI�FRQVLVWHQW�LQIRUPDWLRQ�DIIHFWV�DELOLW\�WR�PDNH�VWUDWHJLF�GHFLVLRQV�WKDW�VXSSRUW�LQQRYDWLRQ�DQG�JURZWK

�


SAP AG 2006

3URGXFW�WR�0DUNHW• Ë�Ì�Í�ÎcÏÐ�Ñ5ÒdÓÕÔ)ÌxÖÍ Ò©ÌÎcÍ ×�ÑØÓ�ÙÚ ÌÐIÛSÑ�ÒxÓ�ÖpÖ�ÓxÐdÒIÏ�ÙÍ Ò©Ü5ÝÞÍ ÒIßà9á�â• ã�Ì�ÔTÛSäåÐdÑ[Ì�ÎSÒ�Í Ú ÑÔ�Ó�Î�Î Ì�æ�ÓxÐdÌ[ÒIÍ Ó�Ù5ÝØÍ ÒIß�ç�Ð�Ó�Ù�ÒÓ�çzçIÍ Ô�Ñ

2SWLPL]H�3URFXUHPHQW• ã�Ì�Ô�Û�Ó�çpèpÍ ä�Í,æ�Í�Î�Í Ò©ÜåÍcÙ�ÒdÓä�Ï�Ö�Ö�Î�Í ÑÐ©äÞÌÙTéêÖ�Ð�Ó�éxÏTÔ)Òzä• ë/Í ì�ßbä�Ö[Ñ�Ù�éíÔ�ÓTä�Òzä

&(2�&)2�&,2î ï Ð©Ñ�Ì�Ò©ÑbÌÙ â ð ç�ÐdÌ Ú Ñ�ÝbÓ�ÐIÛ8Ò�ß[Ì�Òpä�ÏÖpÖ�ÓxÐdÒ©äåÍ,ÙTÙÓTè�Ì[Ò�Í Ó�ÙbÌpÙ�éíì�Ð�Ó�Ý.Ò�ß5ÝØÍ Ò�ßåÎ Ñ�ä[äæ�Ï�épìÑ�Òî ñ ÌTÙ�Ì�ì�ÑÞÌÎ�Î[ÐdÑ�ä�Ó�ÏÐ�Ô�Ñ)äíÍ,Ù�ÔTÎcÏ�é�ÍcÙ�ì7ß�Ï Ú ÌÙØÔ)Ì�Ö�Í Ò�ÌÎSÑ)çdç©Ñ�Ô[Ò�Í è[ÑÎ ÜåÍ�ÙòÌbéÜÙ�Ì Ú Í ÔÝ5ÓxÐIÎ éíÓTç Ú ÑÐ�ìÑTÐdäØÌÙéòÌ�Ô�óxÏ�Í äÍ Ò�Í�ÓxÙ[ä

&XVWRPHU�'DWD�3UREOHP 3URGXFW�'DWD�3UREOHP 6XSSOLHU�'DWD�3UREOHP

(QWHUSULVH�,QIRUPDWLRQ�0DQDJHPHQW�3UREOHP

6$3�%,�,QWHJUDWLRQ��,PSDFW�RI�'DWD�4XDOLW\��

Pervasive Challenges of Master Data Quality

6DOHV�DQG�0DUNHWLQJ�(IIHFWLYHQHVVî ã[Ì�ÔÛSäØÓ�Ù[ÑbèÍ Ñ)ÝôÓTçÔ�Ï[ä�Ò�Ó Ú ÑÐ©äÞÌ[ÔÐ�ÓTä[äbÌ�Î,ÎÔ�ß�Ì�ÙpÙ[ÑÎ äî õ Ï�æ�ö©Ó�Ö�Ò�Í Ú Ì�ÎMèpÍ Ñ)Ý0äÍ Ú Ö�Ì�Ô�ÒzäØÔ�Ï[ä[Ò�Ó Ú ÑÐ�ç�Ì�Ô�Í,ÙTìÒ�ÐdÌÙ�ä�ÌTÔ)Ò�Í Ó�Ù�ä

�

÷ Inability to reduce procurement spend costs

y Inability to understand from whom and which products I buy worldwide y Same suppliers and products classified in different categories, preventing easy comparison ÷

Lack of customer insights to target each account with the right offer y Impacts the ability to create longer, profitable customer relationships y Lack of coherent data prevents anticipation of changing customer needs ÷

Inability to collaborate by sharing information with key constituents y Data silos prevent sharing information with customers, partners, suppliers, etc. y No mechanism or process to share the same information internally and externally ÷

Inability to modify or design new business processes y Rigid connections to data sources y Impedes innovation and differentiation ÷

High integration costs with other key processes y Heterogeneous landscape – lack of common infrastructure or technology platform y Multiple point-to-point solutions with new islands of information


SAP AG 2006

6$3�%,�,QWHJUDWLRQ��([DPSOH�IURP�6$3�%,�5HSRUWLQJ6$3�1HW:HDYHU�%,�UHSRUWLQJ�EHIRUH�WKH�6$3�0'0�FRQVROLGDWLRQ�VWHS�

6$3�1HW:HDYHU�%,�UHSRUWLQJ�DIWHU�WKH�6$3�0'0�FRQVROLGDWLRQ�VWHS�

�


SAP AG 2006

6$3�%,�,QWHJUDWLRQ��%HQHILWV�RI�0'0�,QFOXVLRQ

0DVWHU�'DWD�0DQDJHPHQW�� 3URYLGHV�D�VLQJOH�YHUVLRQ�RI�WKH�WUXWK� 6ROYHV�FULWLFDO�GDWD�LQWHJUDWLRQ�SUREOHPV�RXW�RI�WKH�ER[� 5HGXFHV�WKH�FRVW�RI�UHZRUN�GXH�WR�RXW�RI�GDWH�GDWD� 3URYLGHV�UHDO�WLPH�LQVLJKWV� 6LPSOLILHV�QHZ�GDWD�DFTXLVLWLRQV��L�H��PHUJHUV�DQG�DFTXLVLWLRQV�� 3URYLGHV�IOH[LELOLW\�� 5HGXFHV�WKH�QHHG�IRU�UHGXQGDQW�PDVWHU�GDWD�VWRUDJH��LI�XVLQJ�UHPRWH�PDVWHU�GDWD�� ,QFUHDVHV�WKH�VSHHG�WR�UHVSRQG�WR�FKDQJHV� ,V�HVVHQWLDO�IRU�DFKLHYLQJ�(QWHUSULVH�62$

�


SAP AG 2006

6$3�%,�,QWHJUDWLRQ��6KRUW�7HUP�*RDO

ø�ùcú ûü[ý+þcÿ�� ûTü�ýOþ,ÿ ��

��

� �� ý��

0DVWHU�'DWD�&RQVROLGDWLRQõ�� á ñ�� ñ Ì�épéTÑTéÞÒ©ÓÕÌTÙÑ��pÍ ä[Ò�Í3Ù[ì � â ä�Ô[ÑTÙ�ÌÐ�Í Ó"!� â Ô�ÌÖ�ÌæÍcÎ,Í Ò�Í Ñ[äØÓTç õ#� áà Ñ)Ò%$jÑ�Ì�è[ÑÐxÌ�Ð�ÑòÏ�ä�Ñ�éåÒ©ÓêÔ�Ó�Ù�Ò©ÌÍ�ÙÒ�ß�Ñ Ú Ì�&�ÓpÐ�Í Ò�ÜØÓç�Ì�Ò©ÒIÐIÍ�æ�Ï�Ò©Ñ�ä�ÝÞßÍcÎ Ñõ�� á ñ�� ñ ä[Ò�Ó�ÐdÑ�äòÓ�Ù�Î Ü�ÒIß�ÓTä�ÑÐdÑÎ Ñ[è[ÌpÙ[ÒTç�ÓpÐ Ú Ì�Ò�Ô�ß�Í,Ù�ì('é�ÏÖ�ÎcÍ Ô�Ì)Ò�ÑåÍ é�ÑÙ[ÒIÍ ç�Í Ô[Ì[Ò�Í Ó�Ù�! õ)� áñ*�/ñ ÑÙ[Ìæ�Î Ñ�äíß�Ì�Ð Ú Ó�Ù�Í ×�Ì[Ò�Í Ó�ÙÌÙ�éÕÔ�Ð�Ó�ä[ä�öcä�Ü[ä�Ò©Ñ Ú ÌÙ[Ì�Î Ü[Ò�Í�Ô�ä+!

, ��- ü�ý � ü/. � 01��2� ü�ý ù,43 � . � 5��6��ý � . ��

0'0

ñ7�9ñ

ñ7�9ñ

8 . ü 5�� .�9 :�8 . ü 5�� .�9 :�8 . ü 5�� .�9 :�

. ü 5�� .�9 :�. ü 5�� .;9 ��

�� 9 ��

. ü 5�� .�9 :�

%,

<>=@?BADC E2FHG IDJ

�

� By consolidating Business Intelligence (BI) data with SAP NetWeaver, you can update BI master data info objects to provide a solid base for cross-company reporting, such as global spend analyses.

� Point to point connection between SAP NetWeaver MDM and SAP NetWeaver BI using MDM’ s ABAP API.

� SAP NetWeaver repository is generated based on BI InfoObject as a template. � BI keeps its knowledge of local object keys in the various systems, but it receives additional

information regarding consolidation from SAP MDM. The transactional dataflow within SAP BI is not affected.

� SAP NetWeaver BI SAP NetWeaver MDM How-To Guide to create and operate the repository with relevant mapping structures for scenario 6$3�1HW:HDYHU�%,Æ�6$3�1HW:HDYHU�0'0Æ�6$3�1HW:HDYHU�%, available

� SAP R/3 related repositories 0DWHULDO��&XVWRPHU�9HQGRU have been enhanced with 6$3�1HW:HDYHU�%,�LQWHJUDWLRQ relevant content Æ import maps, syndication maps for the appropriate SAP NetWeaver BI Info Object

� Key information for multiple client systems available within one syndication � Delta update functionality available for SAP NetWeaver BI scenarios � Fully automated inbound process for the scenarios with R/3 source � Fully automated outbound process with XI integration for all scenarios � Semi automated inbound process for the 6$3�1HW:HDYHU�%,Æ�6$3�1HW:HDYHU�0'0Æ�6$3�1HW:HDYHU�%,


SAP AG 2006

6$3�%,�,QWHJUDWLRQ��&UHDWLRQ�RI�0'0�,'

� &UHDWLRQ�RI�XQLTXH�.(<�0'0�,'�� &RQVROLGDWLRQ�DQG�PHUJLQJ�LQ�WKH�0'0�'DWD�0DQDJHU�EHIRUH�GLVWULEXWLRQ�LV�H[HFXWHG�LQ�WKH�0'0�6\QGLFDWRU�

�

� Creation of MDM ID is done by: y first enabling key mapping for a repoistory‘s main table y Adding the MDM ID to the repository using the field type, AutoID y Mapping the local key to the remote key

� Consolidation and identification of duplicates takes place using the Data Manager‘s Matching Mode � Syndication takes place with a repository‘s Client Systems using both the MDM ID and the Remote

Key


SAP AG 2006

ñ7�9ñ

ñ7�9ñ

8 . ü 5�� .�9 :�8 . ü 5�� .�9 :�8 . ü 5�� .�9 :�

. ü 5�� .�9 :�. ü 5�� .;9 ��

�� 9 ��

. ü 5�� .�9 :�

%,

<>=@?BADC E2FHG IDJ

6$3�%,�,QWHJUDWLRQ��/RQJ�7HUP�*RDO

ø[ùcú ûü�ýOþ,ÿ ��K�� ûTü�ýMþ�ÿ��K;�

�+�

, ��K�ML � :�� ý;�

&HQWUDOO\�0DQDJHG�0DVWHU�'DWDõ�� á ñ�� ñ Ì[äbÒIß[ÑÞÔ)ÑpÙ[Ò�Ð�ÌTÎ)éÌ�ÒdÌíß�Ï�æ�Ò�ÓÔ[Ó�Ù�äÓ�Î�Í éÌ)ÒdÑbÌ�ÙTéêÍ é�ÑÙ�Ò�Í ç©Üòé�ÏTÖxÎ�Í Ô�Ì[Ò©Ñ�äÔ[Ó�Ù�Ò�Ì�Í�Ù�ÍcÙ�ìòÒ�ß�ÑØì�Î Ó�æ�Ì�Î�Î ÜåÐdÑÎ Ñ�è[Ì�Ù[Òpé�Ì�Ò©ÌÌ�ÒzÒ�Ð�Í�æpÏ[Ò©Ñ[ä"!� â Ô)ÌÖTÌæÍcÎcÍ Ò�Í Ñ�äØÓ�ç õ)� ájà Ñ[Ò$jÑTÌ�è[ÑÐ�ÌÐdÑÏ[Ò�Í�ÎcÍ ×)Ñ�éÞç�ÓxÐpÒ�ß[ÑòÍ3Ù[ä�ÒdÌ�Ù�Ô�ÑbÝbß�ÑÐdÑ5Ò�ß�ÑÚ Ì;&�ÓxÐ�Í ÒdÜØÓ�çxÌ�ÒzÒ�Ð�Ícæ�Ï�Ò©Ñ�äÞÌÐdÑ�ä�Ò�ÓxÐ�Ñ�éÞçdÓ�ÐÌÙ�ÌTÎ Ü[äpÍ äÕÖ�Ï�Ð�ÖÓTä[Ñ[ä+!ï ÓxÙ[äTÓ�Î�Í é�Ì[Ò�Í�Ó�Ù�äTÔ)ÑÙTÌÐIÍ ÓÞÝbß�Ñ�Ð�ÑbéÌ[Ò©ÌòÍ ää�ß�ÌTÐ�ÑTéØÝbÍ Ò�ß õ#� á ñ��/ñ ÌÙ�é/'ºÓxÐ�ÓTÒ�ß[ÑÐÓ�Ö�ÒIÍ Ó�Ù[äòÓTç õ#� á ñ��/ñ ÌTÐ�ÑôèÍ ÌæÎ Ñ"!

N�OQP6R�ST%UWV O%X U S

T0'0

�

� Point to point connection between SAP NetWeaver MDM and SAP NetWeaver BI utilizing MDM’ s ABAP API.

� SAP NetWeaver MDM repository can be generated based on BI InfoObject as a template. � BI keeps its knowledge of local object keys in the various systems, but it receives additional

information regarding consolidation from SAP MDM. The transactional dataflow within SAP BI is not affected.

� SAP NetWeaver BI SAP NetWeaver MDM How-To Guide to create and operate the repository with relevant mapping structures for scenario 6$3�1HW:HDYHU�%,Æ�6$3�1HW:HDYHU�0'0Æ�6$3�1HW:HDYHU�%, available

� SAP R/3 related repositories 0DWHULDO��&XVWRPHU�9HQGRU have been enhanced with 6$3�1HW:HDYHU�%,�LQWHJUDWLRQ relevant content Æ import maps, syndication maps for the appropriate SAP NetWeaver BI InfoObject

� Key information for multiple client systems available within one syndication � Delta update functionality available for SAP NetWeaver BI scenarios � Fully automated inbound process for the scenarios with R/3 source � Fully automated outbound process with XI integration for all scenarios � Semi automated inbound process for the 6$3�1HW:HDYHU�%,Æ�6$3�1HW:HDYHU�0'0Æ�6$3�1HW:HDYHU�%,


SAP AG 2006

6$3�%,�,QWHJUDWLRQ��'LUHFW�&DOO�'XULQJ�'DWD�6WDJLQJ

'DWD�6WDJLQJ�LV�GRQH�E\�5RXWLQH�LQ�7UDQVIRUPDWLRQ�5XOHV

�


SAP AG 2006

6$3�%,�,QWHJUDWLRQ��'LUHFW�&DOO�'XULQJ�'DWD�6WDJLQJ

�


SAP AG 2006

6$3�%,�,QWHJUDWLRQ��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 'HVFULEH�WKH�LQWHJUDWLRQ�RI�0'0�ZLWK�6$3�%,

�


SAP AG 2006

8QLW��,7��%XVLQHVV�6FHQDULRV��0DVWHU�'DWD�+DUPRQL]DWLRQ





3HUIRUPDQFH




�


SAP AG 2006

&RQWHQWV�� 0DVWHU�'DWD�+DUPRQL]DWLRQ�6FHQDULR�ZLWKLQ�0'0

0'0�0DVWHU�'DWD�+DUPRQL]DWLRQ

�


SAP AG 2006

0'0�0DVWHU�'DWD�+DUPRQL]DWLRQ��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 'HVFULEH�WKH�6$3�0'0�VFHQDULR�YDULDQW�

0DVWHU�'DWD�+DUPRQL]DWLRQ�� /LVW�WKH�VWHSV�WR�EH�SHUIRUPHG�IRU�0DVWHU�'DWD�

+DUPRQL]DWLRQ

�


SAP AG 2006

0'0�0DVWHU�'DWD�+DUPRQL]DWLRQ��%XVLQHVV�6FHQDULR

� 6LQFH�\RX�ZLOO�EH�KDUPRQL]LQJ�PDVWHU�GDWD�DIWHU�FRQVROLGDWLRQ��\RX�ZDQW�WR�NQRZ�ZKDW�RSWLRQV�DUH�DYDLODEOH�WKH�LPSRUW�RI�GDWD�IURP�DQG�V\QGLFDWLRQ�RI�GDWD�IURP�6$3�0'0�WR�\RXU�YDULRXV�V\VWHPV�XVLQJ�6$3�;,�

� <RX�DUH�SDUWLFXODUO\�LQWHUHVWHG�LQ�LPSRUWLQJ�FRQWURO�WDEOH�GDWD�IURP�6$3�(53�WR�SRSXODWH�ORRNXS�WDEOHV�LQ�6$3�0'0�

�


SAP AG 2006

0DVWHU�'DWD�+DUPRQL]DWLRQ%HQHILWV�� "!"��$#%��&��'"'�(%# ��# &)� *�&��+��"�-,�� #.��"'�'�(/# ��0# &�� "'��1&��2�0�� 0 ��'�� 232# �4�5�5��&)��# ��)��6�# �37&"8:9;�<$�"��=�5��># �?�"��"�"! ��@#/�$�A��(B��# C$�* �� ,�(/#.�"!$�"��"# ��#/&?�2C$� 9�#/�"!>,��"�$&��2�� A��2�"��D

�?��FEG��%HI��6��:�5��

�J�� ( <��# ��)�&)'�( @�G�K&��)��0# 6 # ��<

LM&�C>'"&"��# �=��N'�'�(/# ��0# &G��

OKP Q%R S T=U VOKU T=WYX[Z[ZB\4TAV^]=T=_�X�_%R Z`?a%bdcfe g h^i?j klglm;bfcdn

o ��#p��>�G�K& ��@q.��=�!)�A��# &?�

r�sftYuwvpxNy"z�z{v|G}l~w�� z�z^v.�:ufs^�� s^� v�� ~B�B� sfv.uB��z�� x

y��"� ~^� r�sftYuwvpxNy"z�z{v �G� z^v��^� �B�

� uf�;�^�[� �lvA� z��Loading and ConsolidatingMaster Data

� &HQWUDO�UHSRVLWRU\� 0DWFKLQJ�DQG�

PHUJLQJ� 7UDFN�FKDQJHV� ,'�PDSSLQJ� 6WDJLQJ

� � �fv=�[� ��wv=� �;�� sf�fvYu�� swv%s

�


SAP AG 2006

5HPRWH�6\VWHP�&RQQHFWLYLW\�WR�0'0

0'06(59(5

�w��"�^�J� � �¡�¢�£ � ¡d¤;¢ �f¥¦{§ � ¢ �^¨ ¥ ¢"¦d©¢"ª ¥;« ¢ ª{¬ �¦{§ � ¢ ¥ § � © �f¥ § �� ¢"¦ ¥� ¦;£�¤ ¨ §¦{§ �� ©�l¥l�;¥ ª �¡ ¢�®

5HPR

WH�6\

VWHP

5HPR

WH�6\

VWHP

¯�° ��G �=6� �

¯�° ��: ��6��

�?�N�±E:��[H²��6�"��³´q ��µE-��YHF��6� � ³´q

q C¶'�&?�[��G �A6��

�G<��?# ��0# &?��: ��6��

,1%281',17(5�

287%281',17(5�

,1%281',17(5�

287%281',17(5�

·"¸w¹"º» ¼�½ c ºg+¾.c;¿

À�Á k

�w��{�J�+� �¡4¢�£ � ¡d¤;¢ �w¥¦{§ � ¢ �;¨ ¥ ¢ ¦ ©¨ ¬ « ¢�ª^¬ �¦�§ � ¢ ¥ § � © �f¥ § �� ¢"¦ ¥� ¦;£�¤ ¨ §¦{§ �� ©�f¥ �^¥ ª �¡ ¢�®

À�Á k·"¸w¹ º» ¼�½ c ºg ¾%cB¿

'%

�


SAP AG 2006

6FHQDULR�6WHSV��5HWULHYH�&RQWURO�'DWD�IURP�6$3�(53([WUDFW�WKH�GDWD�IURP�6$3�(53��FRQWURO�WDEOH�LQIRUPDWLRQ�

7UDQVDFWLRQ�&RGH��6(��

�


SAP AG 2006

7UDQVDFWLRQ�FRGH��0'0B&/17B(;75

6FHQDULR�6WHSV��5HWULHYH�0DVWHU�'DWD�IURP�6$3�(53

�

� The SAP R/3 plug-on PI_Basis enables the use of mass (or bulk) IDocs for the object types: y Material Æ MATMDM y Customer Æ DEBMDM y Supplier ( Vendor) Æ CREMDM

� Mass IDocs are generated using transaction code mdm_clnt_extr.


SAP AG 2006


6$3�1HW:HDYHU ;,�,QWHJUDWLRQ�5HSRVLWRU\�5HFHLYHU�'HWHUPLQDWLRQ

�

� The SAP NetWeaver XI Repository does not have an entry in the repository for material and/or vendor because the IDoc structure is used to transmit the data.

� You only need to configure the regular steps in SAP NetWeaver XI configuration. � The transmission from RFC IDoc structure to XML will be handled via the SAP NetWeaver XI IDoc

Adapter.


SAP AG 2006

6$3�1HW:HDYHU�;,��;6'�)LOH�*HQHUDWLRQ

�

� The export file is a generated XSD file from SAP XI, based on a special IDoc type to support the syndication.

� The XSD file will be the basis for the to-be-created XML message when the data is retrieved from the repository.


SAP AG 2006

0'0�6\QGLFDWRU��;6'�)LOH�

;6'��(PSOR\HH

�

� The above graphic depicts the XML file view of the generated XSD file for the master data object Employee.

� The XSD document can be modified in a tool such as Altova XMLSpy.


SAP AG 2006

6\QGLFDWLRQ�(IIHFWV�DQG�.H\�0DSSLQJ�,PSRUW�0DS

.H\�0DSSLQJ,WHP�0DSSLQJ

�

� By default (in the predefined syndication maps), the remote system record ID of the IDoc is mapped to the remote key of the SAP MDM record.

� If the record is already merged, it might have multiple remote keys. � An XML message will be created for each of the keys for the current and appropriate client system.


SAP AG 2006

.H\�0DSSLQJ

0HUJHG�UHFRUGV

6\QGLFDWLRQ�UHOHYDQW

2QH�UHFRUG

�

� There are different types of key mapping. � The key mapping for records is relevant for the source system and the source system key. � The key mapping for lookup records is also relevant to the 'HIDXOW flag in the syndication.


SAP AG 2006

([HUFLVH�([SODQDWLRQ��0'+�([HUFLVH�2YHUYLHZ

7KH�H[HUFLVH�GHVFULEHV�WKH�FXUUHQW�VXSSRUWHG�,7�VFHQDULR�ZLWK�D�IRFXV�RQ�WKH�GDWD�WUDQVIHU�IURP�6$3�(53��WR�6$3�(53��ZLWK�PDQXDO�GDWD��GH�GXSOLFDWLRQ�DQG�D�UHFRUG�PHUJH�

�� 6$3�(53�FXVWRPHU�WR�6$3�1HW:HDYHU�;,�� 6$3�1HW:HDYHU�;,�WR�WKH�0'0�,PSRUW�0DQJHU�� 0'0�,PSRUW�0DQDJHU�LQWR�WKH�UHSRVLWRU\�

&XVWRPHUB;; �JURXS�GHSHQGHQW�� 5HSRVLWRU\�GH�GXSOLFDWLRQ�DQG�UHFRUG�PHUJH�� &KDQJH�UHFRUGV�� 0'0�6\QGLFDWRU GLVWULEXWLRQ�WR�6$3�(53�� &KHFN�WKH�UHFRUG�LQ�6$3�(53��

�


SAP AG 2006

0'0�0DVWHU�'DWD�+DUPRQL]DWLRQ��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 'HVFULEH�WKH�6$3�0'0�VFHQDULR�YDULDQW�0DVWHU�'DWD�

+DUPRQL]DWLRQ�� /LVW�WKH�VWHSV�WR�EH�SHUIRUPHG�IRU�0DVWHU�'DWD�

+DUPRQL]DWLRQ

�


�([HUFLVHV�

8QLW�� 0DVWHU�'DWD�+DUPRQL]DWLRQ�7RSLF�� 0DVWHU�'DWD�+DUPRQL]DWLRQ�


• Describe the SAP MDM scenario variant Master Data Harmonization

• List the steps to be performed for Master Data Harmonization

Since you will be harmonizing master data after consolidation, you want to know what options are available the import of data from and syndication of data from SAP MDM to your various systems using SAP XI.

You are particularly interested in importing control table data from SAP ERP to populate lookup tables in SAP MDM.

�

/DQGVFDSH�RYHUYLHZ�

This exercise guides you through a master data consolidation and harmonization scenario using SAP MDM 5.5 and ECC, Client 803 and Client 803.

�

3XUSRVH

This exercise is to demonstrate the process flow in a MDM master data consolidation-harmonization IT scenario.

You will transfer data from Client 803 via Import Manager to the SAP predefined Customer repository and via the MDM Syndicator back to Client 803. Both directions will use the XI and the file directory to transfer the xml files.


1 &RQQHFW�WR�WKH�;,�VHUYHU

1-1� If you have the MDM landscape open, please close it by using the menu path: Start �/RJ�2II�

1-2 From the Citrix sessions enter the path:

1-3 Enter the current XI SID and Host, which you will receive from your instructor and click on OK:


Confimation about the connection will appear, confirm the pop-up with OK

2 Connect to ECC Clients 803 and 804�

2-1 Your instructor will guide you in placing the assigned ECC system into the SAP logon dialog box.

2-2 With the SAP Logon dialog box, highlight the system you have entered as the ECC system according to the instructors directions and press "Log on." The Client field will probably default to "800." Change the default value to "803."

2-3 Type in the user: mdm100-##, where ## is the group number assigned by your instructor

2-4 Password: initial (all lowercase as passwords are case-sensitive).

2-5 Once you logon, you will be asked to replace the initial password with another (minimum 6 case-sensitive characters) and enter the new password twice.

2-6 5HSHDW�the steps above�(��through��)�in Client 804��


3 Extract Customer Master Data via IDOC/XML

3-1 In ECC Client 803 go to Transaction code “MDM_CLNT_EXTR”

3-2 Create a new extraction:

Variant: Customer_Username (e.g. CUSTOMER_##) The username will be obtained from the instructor and corresponds to the Target System in this transaction.

Description: Nice to have but not mandatory

Extraction Object: enter “CUSTOMER_EXTRACT” or choose it from the value help

Target System: enter your target system (mdm-0##) or choose it from the value help. The target system name should end in your group number which was assigned earlier by the instructor at the beginning of the exercise (## = your group number).

Distribution Mode: choose or enter “I” for Initial

Block Size: enter 100 and press “Enter”


3-3 Double click on the “ E1KNA1M” element and enter a search value for the Field “ SORTL” (search term).

The search value is “ US” and enter the value in both the “ From Value” and “ To Value” fields.

3-4 Save your extraction variant by pressing “ Save”

3-5 Start your extraction by pressing “ Start Extraction”


3-6 If you want to see the results of the extraction, use transaction code WE05. Make sure that the data range includes tomorrow’s date and click the Execute button. See the results below:

4 5HPRWH�FRQQHFWLRQ�WR�WKH�0'0�6HUYHU�

4-1 From your Citrix session enter the Remote Desktop Connection.


4-2 Enter under Computer the server name of your current MDM Server then click on Options:

4-3 Select the “ Options” button:

4-4 Select the tab Local Resources:

4-5 Select the “ More…: button. You may not have a “ More…” button, but instead you will see the check box “ Drives” listed instead.

4-6 Enable there Disk drives as you see here:

4-7 Click the “ OK” button:

4-8 Enter the MDM Username (mdmusera-mdmuserj) and password provided by the trainer and click on the Connect button


4-9 Confirm the resulting pop up dialog box.


5 &RQILUP�WKH�;,�GULYH�RQ�\RXU�0'0�VHUYHU�

5-1 On the server open My Computer:

The drive X from your WTS connection should be visible:

1RWH: the server name for the X: drive may differ from the illustration.


6 8QDUFKLYH�WKH�&XVWRPHU�5HSRVLWRU\

6-1 Go to the MDM Console, unarchive the repository ‘YourLetter_Customer’ by logging in to the DBMS Server Localhost with user=dba and password=training.

6-2 Wait until you receive a message that your repository has been successfully unarchived. Select the option “ No” to see the detailed results.

6-3 Then “ Select the repository “ Yourletter_Customer” , right mouse click and click on “ Connect to Repository” with user=admin.

6-4 Then “ Select the repository “ Yourletter_Customer” , right mouse click and click on “ Load Immediate” to load your repository in preparation for loading.

6-5 If you encounter a message saying that the repository could not be loaded because the port is busy, acknowledge the message with “ OK.” Then highlight the MDM server, “ localhost” and in the list of repositories, select your repository and change the port to another port number that is not being used. Make sure the new port number is at least “ 5” away from the highest port listed in the list of repositories. Then continue with loading your repository as in 6-4 above.


7 /RDG�5HSRVLWRU\�8VLQJ�,PSRUW�0DQDJHU

7-1 To start the Import Manager, double click on the SAP MDM Import Manager Icon.

7-2 After selecting the MDM Server you are able to select the needed repository.

Server: LOCALHOST

Repository: Yourletter_Customer

7-3 Then login to your Customer_# repository with:


User: Admin

Password: leave it blank

7-4 And select the “ Next” button.

7-5 On the next dialog box, enter the following:

Import Type: XML Schema

Remote system: MDC R/3

XML Schema: DEBMDM06


7-6 Press the Button and go to: My Computer on the left side

7-6-1 on the right side double click the X: drive

7-6-2 open the folder: MDM_group## (where ## is your group number)

7-6-3 open the folder File_Receiver##

7-6-4 select the xml file: ##_DEBMDM.DEBMDM06_<date&time stamp>.xml

7-6-7 press the button: Finish

7-7 In the Import Manager go to “ File” Æ “ Open”

7-8 Choose the map “ 00_DEBMDM06_R3”


7-9 After clicking OK you can see the Field mapping on the Tab

almost completely performed.

7-9-1 Map values for the field “ TITLE<E1BPAD1VL>” by adding the value(s) to the destination domain.

7-9-2 Map values for the field “&28175<��&ORQH!��(�%3$'�9/!�>3DUWLWLRQ@´� by adding these values to the destination domain.


7-10 The Match Records Tab displays all records to be imported, choose “Create” for matching type “None”

7-11 Import Status

The mapping should provide you with a full field and value mapping error free in the tab strip Import.

7-12 Import Status tab strip. You can execute the syndication. Please select the red

exclamation mark button from the upper command bar.

7-13 Confirm the advice window by clicking on the OK Button.


8 Check and Manage Your Data Using Data Manager

8-1 Start the Data Manager by double clicking on the SAP MDM Data Manager Icon and load the customer repository.

MDM Server: LOCALHOST

Repository: Customer


User: Admin


Confirm selection pressing the “ OK” button.

The repository should contain six entries.

8-2 Merge the records with record id’s B1000 and B1001. These records are identical except for Country, Region and Address Time Zone. Make B1001 the merged record.

8-3 Once you have merged the records, look at the key mappings for the merged record.

8-4 Once again select all the records and change the field “ Search Term” to include your letter as follows: “ yourletterUS” so that your search term looks like: AUS, BUS, CUS or DUS.

8-5 Using the table drop down box, select the table “ Titles” so that you can change the key mapping for the titles you previously imported into your repository.

8-6 Right-click on the first entry and choose the option “ Edit Key Mappings.”


8-7 In the “ Edit Record Key Mappings” dialog box, select the “ Add” button to add an additional key mapping for the same remote system, MDC_R/3, for each of the three records in the Titles table as follows: 1RWH��'RQW�FKDQJH�RQO\�RQH�UHFRUG�DQG�GR�QRW�DGG�DOO��YDOXHV�LQWR�RQH�UHFRUG��003 Company 004 Mr 005 Mrs

8-8 After each addition, you will see the check mark in the “ Default” box change from the record you imported to the record you added. This will be the record which will be syndicated.

8-9 Create an additional records by duplicating B1005 with New Customer Id: %��, where ## (## = group name) will be directed by your instructor and with new Customer Name as your name in the format, "last name, first name." Also create a key mapping for this record for the remote system MDC R/3 with the local key as the MDM value.

9 6\QGLFDWRU

9-1 Double click the Syndicator Icon and choose the Yourletter_Customer repository

Repository: Yourletter_Customer


User: Admin


9-2 Open File Æ Destination Properties and select:


9-3 In the next dialog box, enter the following:

Type: XML Schema

Remote system: MDC R3

XML schema: DEBMDM06_R3

Root: DEBMDM06

Click the “ OK” button

9-4 Then use the menu path: File �2SHQ�DQG�FKDQJH�WKH�5HPRWH�V\VWHP�WR�

“ MDC R/3” and then select from the available maps, the map: DEBMDM06_R3 as seen below:

The mapping is done automatically; go to the “ Preview Pane” to see a preview of the generated XML File.

9-5 Press to start the syndication.


9-6 The output file from the Syndicator must have “ DEBMDM” (in all capital letters) in the name, so that XI knows which interface to use. For the output file, use the name “ DEBMDM_##.xml” where “ ##” is your group number. �0DNH�VXUH�WKDW�³'(%0'0´�LV�LQ�DOO�FDSLWDO�OHWWHUV��

9-7 Save the DEBMDM_##.xml file in the appropriate folder on the XI: drive—X:/MDM_group##/File_Sender##

9-8 The notification box delivers status information of the Syndication process

9-9 The files were extracted to the specific folder.

The output file from the Syndicator must have “ DEBMDM” in the name, so that XI knows which interface to use. Use the same “ DEBMDM_##.xml”

The notification box delivers status information of the Syndication process

10 &KHFN�5HVXOWV�LQ�(&&�&OLHQW��

10-1 Log off of the MDM landscape and return to the Citrix session.

10-2 Logon on to the ECC system, but this time go to Client 804.

10-3 Run transaction “ XD03” by typing the transaction code “ XD03” in the Command Field as seen below.

10-4 Press the button and switch in the opening window to tab “ Customers (general)” .


10-5 In order to search all the Customers starting with your group name, place your cursor in the Customer field and use the F4 function key.

In the dialog box, enter “ your_letterUS” in the search term field.

Click Enter. You should now see a list of your.

Select one from the list and double-click it. This will put the selection into the Customer field on the previous screen and then click Enter.

You will now see your customer. Check the search term to make sure that the entry in the Search Term field is the search term you created in the Data Manager.

Note: You will probably see an informational message about the title: “ Form of address key XX is not defined.” Because ECC is using Business Address Services Central Address Management, there is an additional step which can be taken, but is not essential. The following graphic explains this additional step and its reason.


SAP AG 2006

5LFK�3URGXFW�&RQWHQW�0DQDJHPHQW





3HUIRUPDQFH




�


SAP AG 2006

&RQWHQWV�� 5LFK�3URGXFW�&RQWHQW�0DQDJHPHQW�LQWURGXFWLRQ

0'0�5LFK�3URGXFW�&RQWHQW�0DQDJHPHQW

�


SAP AG 2006

0'0�5LFK�3URGXFW�&RQWHQW�0DQDJHPHQW��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 8QGHUVWDQG�WKH�SXUSRVH�RI�SXEOLVKLQJ��SULQW�DQG�

ZHE��ZLWK�0'0

�


SAP AG 2006

5LFK�3URGXFW�&RQWHQW�0DQDJHPHQW��%XVLQHVV�6FHQDULR

� 6LQFH�\RXU�FRPSDQ\�ZDQWV�D�ZHE�FDWDORJ�RI�SURGXFWV��\RX�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKH�RSWLRQV�IRU�WKH�LQFOXVLRQ�RI�GDWD�DQG�LPDJHV�IURP�\RXU�SURGXFW�UHSRVLWRU\�

�


SAP AG 2006

$�'\QDPLF�3ULQWHG�,QGXVWULDO�&DWDORJ

7KH�&KDOOHQJH� ��SDJHV� ��LWHPV� :HLJKV�ILYH�SRXQGV� 3URGXFWLRQ�VWDII�RI��SHUVRQV� 2YHU��PLOOLRQ�WR�OD\�RXW� ��SHU�FRS\�WR�SULQW� ��SHU�FRS\�WR�PDLO� 3XEOLVKHG�RQFH�D�\HDU��RU�QHYHU�)URP�WKLV�W\SH�RI�SXEOLVKHG�GDWD�WR�DQ�HOHFWURQLF�YHUVLRQ�«

�


SAP AG 2006

0'0�5LFK�3URGXFW�&RQWHQW�0DQDJHPHQW�LQ�$FWLRQ

³,W�ZDV�D�PLUDFOH��:KDW�ZRXOG�KDYH�WDNHQ�XV�D�GD\�ZH�ZHUH�DEOH�WR�GR�LQ�IRXU�PLQXWHV��0RUH�LPSRUWDQWO\��XVLQJ�WKH�6$3�1HW:HDYHU�0'0�V\VWHP��ZH�GLVFRYHUHG�GDWD�GLVFUHSDQFLHV�WKDWZHUH�YLUWXDOO\�LPSRVVLEOH�WR�LGHQWLI\�XVLQJ�WKH�ROG�WRROV�´Paul Peloquin, BD

%'�8VHV�0'0�53&0�IRU�6HFRQG�*HQHUDWLRQ�+HDOWKFDUH�'HSOR\PHQW

6RPH�VWHSV�WR�JR�«�


SAP AG 2006

3URGXFW�&RQWHQW�0DQDJHPHQW 5HTXLUHPHQWV

Â 2EMHFWLYHV�IRU�D�SURGXFW�FDWDORJ�DQG�SXEOLVKLQJ�V\VWHPÃ 6WRUH�DQG�VWUXFWXUH�ULFK�SURGXFW�GDWD�FRQWHQWÃ &UHDWH�D�FODVVLILFDWLRQ�WD[RQRP\�ZLWK�FDWHJRU\�VSHFLILF�

DWWULEXWHVÃ 6WRUH�DQG�PDQDJH�SURGXFW�UHODWLRQVKLS�LQIRUPDWLRQÃ 6WRUH�LPDJHV�DQG�XQVWUXFWXUHG�FRQWHQW�LQ�WKH�FDWDORJÃ ,PSRUW�UDZ�GDWD�IURP�D�YDULHW\�RI�VRXUFHVÃ 0DLQWDLQ�GDWD�LQWHJULW\Ã 6\QGLFDWH�DQG�SXEOLVK�FRQWHQW�WR�D�YDULHW\�RI�IRUPDWV�DQG�

SODWIRUPVÃ 2EWDLQ�D�KLJK�SHUIRUPDQFH�GXULQJ�VHDUFKLQJ�DQG�ORFDWLQJ�

SURGXFWV�LQ�D�YDULHW\�RI�ZD\V��HYHQ�RQ�YHU\�ODUJH�FDWDORJV�FRQWDLQLQJ�PLOOLRQV�RI�SURGXFWV

Ã &UHDWH�D�XVHU�IULHQGO\�DSSOLFDWLRQ�ZLWK�IHDWXUHV�WKDW�DUH�FRPSUHKHQVLYH�DQG�LQWXLWLYH

�


SAP AG 2006

3&0�5HTXLUHPHQW� 0'0�53&0�2IIHULQJV

5LFK�DQG�VWUXFWXUHG�SURGXFW�FRQWHQW�LV�HVVHQWLDO�IRU�D�SURGXFW�FDWDORJÄ 0'0�53&0�FRQWDLQV�PXOWLSOH�GDWD�HOHPHQWV

Å Æ�Ç È�É Ê Ë�Ì ÍGÇ/Î�Í=Ì?ÏKÐ$Ñ�Ò0Ç Ì?Î2Ó�Ì�Ð1Ð@Ì?Î5ÒAÌ$Ñ É/É�Ô�Ï=Ì�Ê?Õ�Ó�ÒYËÖ Ñ�Ï[ÒG×MÕ"Ð¶Ø�È�ÏAÙ�Ê È�Ë"Ó�Ï4Ç/Ô�Ò0Ç/Ì�Î

Å Ú-È�Ò�Ñ Ç/É È�ÊÛÔ ÏKÌ Ê�Õ�Ó^Ò�Ë�Ô�È"Ó"Ç Í0Ç Ó�Ñ�Ò�Ç Ì?Î�ËÜ Ò=Ò0Ï�ÇpØ�Õ�Ò=È�Ë

Å Ü Ê Ê?Ç Ò4Ç Ì?Î�Ñ�É�Õ�Î�Ë�Ò0Ï4Õ�Ó�Ò�Õ�Ï=È�Ê@Ó�ÌGÎ�Ò[È�Î�ÒÝ Ð Ñ�Þ"È�Ë"Ù Ö ÚßÆ�Ë Ù�Ð È ÏKÓ"à�Ñ�Î�Ê?Ç á�Ç/Î�Þ$Ò[È�â�Ò[Ë

Ä 0'0�53&0�SURGXFW�FODVVLILFDWLRQÅ ã�ÏAÞ"Ñ Î�Ç á^È�Ë1Ô ÏKÌ�Ê)Õ�Ó�Ò[Ë$Ç%Î�Ò=Ì$ÑäÒ�Ñ�â"ÌGÎ�Ì Ð$åÅ ã�Í[Í�È Ï�Ë2Ñ"Ï4Ø Ç Ò0Ï=Ñ Ï=å1à�Ç È Ï=Ñ ÏAÓ à�å2Ì"Í)Ó�Ñ�Ò=È�Þ Ì?Ï�Ç È�ËÑ�Î�Ê Ë�Õ Ø"Ó�Ñ�Ò=È�Þ�Ì�Ï4Ç È�Ë

Å Ü Î�å$Î�Õ"Ð¶Ø�È Ï?Ì�Í:É È�æ�È É Ë$ÇpÎ�Ò+à�È à�Ç È Ï=Ñ ÏAÓ à�åÅ Ü Ó�Ñ�Ò[È"Þ�Ì)ÏAå�Ó�Ñ�Î5Ñ�Ô�Ô�È�Ñ Ï:Ç/Î2Ð�Õ É Ò0Ç.Ô É È@Ô�É Ñ�Ó�È�Ëç Ç Ò0à�ÇpÎ�Ò4à�È à)Ç È Ï=Ñ ÏAÓ à�å

Ä 0'0�53&0�DOORZV�SURGXFW�UHODWLRQVKLSV�WR�HQDEOH�GLVSOD\�RI�è é Ò0Ï�Õ�Ó�Ò�Õ�Ï=Ñ É�Ï=È�É Ñ�Ò�Ç Ì?Î�Ë�à ÇpÔ�Ëè ê Ç Ò[Ëè ë Õ Î�Ê�É È�Ëè ì Ñ�ÒAÓ�à�Ç/Î"Þ é È�Ò�Ë

�


SAP AG 2006


'DWD�0DQDJHU�PDLQWHQDQFH�± VHDUFK�± UHVXOW�YLHZ

�


SAP AG 2006

6HDUFK�E\�NH\ZRUG��HWF��

:HE�6ROXWLRQ��

(OHFWURQLF�FDWDORJ�ZLWK�PXOWLSOH�VHDUFK�FDSDELOLWLHV

�

� Web catalogs can be achieved using MDM Publisher or by using APIs.


SAP AG 2006


6SHFLILFDWLRQ�RI�WKH�VHOHFWLRQ�YLD�DWWULEXWH�YDOXHV

�


SAP AG 2006


&RPSDULVRQ�RI�WKH�VHOHFWHG�LWHPV

�


SAP AG 2006

3DSHU�3ULQWHG�6ROXWLRQ�

/D\RXW�DQG�SULQW�SRVVLELOLWLHV

�

� Ensure correct positioning of family objects in relation to page, spread and/or other families � Paginate document before handing over to DTP � Publish content to DTP by spread, page, or publication � Allow exact geometry and x/y object positioning/sizing � Enable DTP-compatible keyboard shortcuts to accelerate production � Provide special character style tagging (e.g., for trademarks)


SAP AG 2006

0'0�5LFK�3URGXFW�&RQWHQW�0DQDJHPHQW��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 8QGHUVWDQG�WKH�SXUSRVH�RI�SXEOLVKLQJ��SULQW�DQG�

ZHE��ZLWK�0'0

�


SAP AG 2006

*OREDO�'DWD�6\QFKURQL]DWLRQ





3HUIRUPDQFH




�


SAP AG 2006

&RQWHQWV�� 2YHUYLHZ�RI�0'0�JOREDO�GDWD�V\QFKURQL]DWLRQ��*'6�� ([SODQDWLRQ�RI�UHDVRQV�IRU�XVLQJ�*'6� *'6�XVHU�LQWHUIDFHV

0'0�DQG�*OREDO�'DWD�6\QFKURQL]DWLRQ��*'6�

�


SAP AG 2006

0'0�DQG�*OREDO�'DWD�6\QFKURQL]DWLRQ��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� ([SODLQ�WKH�SXUSRVH�RI�*'6� /LVW�WKH�UHDVRQV�IRU�XVLQJ�*'6

�


SAP AG 2006

0'0�DQG�*OREDO�'DWD�6\QFKURQL]DWLRQ��%XVLQHVV�6FHQDULR

� $V�SDUW�RI�WKLV�LPSOHPHQWDWLRQ��\RX�PLJKW�ZDQW�WR�V\QFKURQL]H�\RXU�SURGXFW�GDWD�DV�WUDGH�GDWD�ZLWK�D�JOREDO�GDWD�SRRO�RU�VHUYLFH�PDUNHWSODFH�LQ�WKH�IXWXUH��\RX�ZDQW�WR�IDPLOLDUL]H�\RXUVHOI�ZLWK�WKLV�IXQFWLRQDOLW\�

�


SAP AG 2006

,QWURGXFWLRQ6ROXWLRQ�2YHUYLHZ8VHU�,QWHUIDFHV


6XPPDU\

�


SAP AG 2006

7KH�&RQVXPHU�3URGXFW�,QGXVWU\�(FRV\VWHP

íïî�ð^ñ�ò�ó/ó

ô/õ?ö ÷�ø�ù ñ0ú2û?ð�î"ð{ó

ü à�Ñ Î Þ�È�Ë1Ç/Î é Ì�Ó�Ç È�Ò[åÑ"Î�Ê¶ýÕ�Ð@Ñ Îë È à�Ñ�æ�Ç Ì)Ï

ü à�Ñ Î Þ�È�Ë1Ç/Î é Ì�Ó�Ç È�Ò[åÑ Î�Ê¶ýÕ�Ð@Ñ Îë È à�Ñ�æ)Ç Ì)Ï

þ É Ì?Ø�Ñ"Éÿ È�Ó�È�Ë�Ë�Ç Ì?Îþ É Ì?Ø�Ñ"É

ÿ È�Ó�È�Ë�Ë�Ç Ì�Î

� È�Ó"à)Î�Ì?É/Ì Þ åÚ-È�æ�È"É/Ì?Ô�Ð È�Î�Ò� È�Ó"à)Î�Ì?É Ì�Þ åÚ-È�æ�È É/Ì?Ô�Ð È�Î�Ò

Æ�Ì�Ì�Ê é Ñ�Í=È�Ò�å

Ý Î�Ò�È Ï�Î�Ñ�ÒKÇ/Ì)Î�Ñ ÉpÇ á^Ñ�Ò0Ç Ì?Î

þ É Ì?Ø"Ñ Éé Ò[Ñ�Î�Ê�Ñ ÏAÊ?Ç á�Ñ�Ò�Ç Ì?Îü Ì)ÉpÉ Ñ�Ø�Ì?Ï=Ñ�ÒKÇ æ�Èë Õ�Ë�ÇpÎ�È�Ë�ËÖ ÏKÌ Ó�È�Ë�Ë�È�Ë

ë��ëIì Ñ"Ï��^È�Ò4Ô É Ñ�Ó�È�Ë

Staffing

� ��

�� !� "#�! �$

�&%#��'�(��"*)+ �#$#�-, .$0/1 "�'"#��2� �3�� #�-4*��2� �3�

57698;:=<3>@?BA�C3D3C@E

ü Ö ì Ñ Î�Õ�ÍAÑ�Ó^Ò4Õ ÏAÈ Ï ÿ È�Ò=Ñ"Ç.É È ÏÚMÇ Ë�ÒKÏ�ÇpØ)Õ�Ò�Ç Ì?Îé Õ�Ô�Ô É.Ç È Ï ü Ì?Î�Ë)Õ"Ð È Ï

F �@) �0��.�!G�H("*).4-� �"#�/JI=��#�@)K ��"*�* � � � ��# � �� 2� �3�

�*�!LM� �-�!�!4!�� @�

��-��!�K� � !� "#�! �$

1 "��*� , "#)��ON9)'�-�#L�P%#��.�(�0"#)

+ �!$#�!, K$0/1 "��"*�*2� �@�

576�8M:=<3>@?BA�C3D�C@E

þ Ì"æ�È Ï4Î"Ð$È Î�Òÿ È�Þ?Õ�É Ñ�Ò+Ç Ì?Î�Ëþ Ì"æ�È"Ï+Î"Ð$È Î�Òÿ È�Þ�Õ�É Ñ�Ò+Ç Ì?Î�Ë

�

� The ecosystem of consumer product (CP) manufacturers faces a variety of challenges. � Global recession and changes in society influence the consumer and require CP manufacturers to

continously to adapt new circumstances. � On an industry level, the development of global standards like EPC and GS1 and growing

internationalization lead to the increased importance of collaboration between manufacturers and their retail trading partners.


SAP AG 2006

/DFN�RI�*OREDO�'DWD 6\QFKURQL]DWLRQ

• 0XOWLSOH�V\VWHPV�DQG�LQWHUIDFHV�• &RQIOLFWLQJ�LWHP�GHILQLWLRQV�• 3URSULHWDU\�6.8�QXPEHUV�YV��

VWDQGDUG�($1�8&&�QXPEHUV�• 6ORZ�SURGXFW�XSGDWHV�YLD�PXOWLSOH�

FKDQQHOV�DQG�V\VWHPV• &KDOOHQJHV�RI�JHWWLQJ�QHZ�

SURGXFWV�WR�PDUNHW�• ,QFRUUHFW��UHWXUQHG�VKLSPHQWV• 'HGXFWLRQV�DQG�ORVW�VKHOI�WLPH

:H GR�QRW VSHDN WKH VDPH ODQJXDJH�ì Ñ"Î�Õ�Í�Ñ�Ó�ÒKÕ�Ï=È Ï

ÿ È�Ò�Ñ Ç/É È Ï�Ë

Q Ô�Ò=ÌSR(T�UÈ Ï�ÏKÌ)Ï:Ï=Ñ�Ò�ÈØ�È�Ò ç È�È�Î

Ð Ñ Î�Õ�ÍAÑ�Ó�Ò+Õ"ÏAÈ"ÏÑ Î�Ê>ÏAÈ�Ò[Ñ�Ç/É È"ÏÓ�Ì?Î�Ò=È Î�Ò�V

�

� Lack of global data synchronization significantly impacts your value chain.


SAP AG 2006

.H\�WR�&ROODERUDWLRQ LV 6\QFKURQL]HG 'DWD

7KH�FRQWLQXRXV�KDUPRQL]DWLRQ�RI�GDWD�DWWULEXWH�YDOXHV�EHWZHHQ�WZR�RU�PRUH�GLIIHUHQW�V\VWHPV�ZLWK�WKH�HQG�UHVXOW�EHLQJ�WKH�VDPH�GDWD�DWWULEXWH�YDOXHV�

LQ�DOO�V\VWHPV�

0DQXIDFWXUHUV 5HWDLOHUVþ É Ì)Ø�Ñ É ÿ È�Þ?Ç Ë�ÒKÏKå

6\QFKURQL]DWLRQWYX#Z'X;[@\(\9] WYX#Z.XM[@\(\9]

�


SAP AG 2006

%HQHILWV�IRU�0DQXIDFWXUHUV

• ,QFUHDVH�6DOHV^ 6SHHG�WR�PDUNHW^ 2Q�VKHOI�DYDLODELOLW\

• ,PSURYH�3URGXFWLYLW\^ ,WHP�PDLQWHQDQFH�DQG�SXEOLFDWLRQ�HIIRUW^ (UURU�UHFRQFLOLDWLRQ�HIIRUWV

• 5HGXFH�&RVWV^ 7UDQVSRUW�FRVWV^ )HZHU�UHWXUQV

• 'DWD�4XDOLW\^ ,PSURYHG�FRQILGHQFH^ 6DPH�PHVVDJH�HYHU\ZKHUH

�


SAP AG 2006

6HFRQG�:DYH�RI�*'6�LV�$ERXW�WR�+LW

Gartner, March 2006, Gain Value Sooner With a Clear Understanding of the Global Data Synchronization Road Map

Forrester 2005, Shared Strategy Study, Consumer Goods, Technology and RIS News

• *'6�WRGD\^ )HZ�YLVLRQDU\�UHWDLOHUV�DQG�PDQXIDFWXUHUV^ 0DQXIDFWXUHUV�WKDW�PXVW�FRPSO\�ZLWK�D�UHWDLOHU¶V�PDQGDWH^ 7KH�PRVW�DGYDQFHG�SURMHFWV�DUH�WKRVH�WKDW�DUH�EXVLQHVV��

DQG�QRW�GULYHQ�E\�,7• )XWXUH�WUHQGV

^ 0RUH�WKDQ�RQH�ILIWK�RI�PDQXIDFWXUHUV�HYDOXDWLQJ�GDWD�V\QF^ 0DQXIDFWXUHUV�DQG�UHWDLOHUV�ORRN�IRU�LQWHJUDWHG�VROXWLRQV�UDWKHU

WKDQ�SXUH�GDWD�V\QFKURQL]DWLRQ�VROXWLRQV^ 'DWD�LV�WUHDWHG�DV�D�VWUDWHJLF�DVVHW^ /HYHUDJH�H[LVWLQJ�FROODERUDWLRQ��H�J��UHYLWDOL]H�SURFHVVHV�OLNH

&ROODERUDWLYH�3ODQQLQJ��)RUHFDVWLQJ�DQG�5HSOHQLVKPHQW�^ 0HUJH�5),'�ZLWK�*'6�^ $OLJQ�GLIIHUHQW�LQLWLDWLYHV�WRZDUG�RQH�PDVWHU�GDWD�VWUDWHJ\

�

� Collaborative Planning, Forecasting and Replenishment (CPFR) � Radio Frequency Identification (RFID)


SAP AG 2006



6XPPDU\

�


SAP AG 2006

'HILQLWLRQ�DQG�.H\�&DSDELOLWLHV

'HILQLWLRQÂ 0DQDJH�WUDGH�LWHP�H[FKDQJH�EHWZHHQ�&3*�PDQXIDFWXUHUV�DQG�

UHWDLOHUV�YLD�D�FHUWLILHG�GDWD�SRRO�RI�WKH�*'61

.H\ FDSDELOLWLHVÂ /HDQ�DQG�IRFXVHG�*'6�Â 6HDPOHVV�DQG�SHUPDQHQW�LQWHJUDWLRQ�ZLWK�EDFN�HQGÂ )OH[LEOH�HQG�WR�HQG�VROXWLRQÂ /HYHUDJHV�0'0�WHFKQRORJ\Â )LWV�RQ�WRS�RI�H[LVWLQJ�V\VWHP�ODQGVFDSH��ORZ�7&2�

�

� Lean and focused GDS solution y Easy to use y Ensures data quality y Manages communication process

� Seamless and permanent integration with back end y Back-end integration is the most important feature because integration will drive the positive

effects of GDS y GDS goes commodity developing towards process automation

� Flexible end-to-end solution y Enhances and adapts to customer requirements

� Leverages MDM technology y First step to a full MDM scenario, though it does not require other MDM scenarios, for

example, product content management � Fits on top of existing system landscape

y Low TCO


SAP AG 2006

6$3�1HW:HDYHU

Ü Ô"Ô�É/Ç/Ó�Ñ�Ò0Ç Ì?Î Ö É Ñ�ÒYÍ0Ì?ÏAÐ

7KH�0DQXIDFWXUHU·V�3URFHVV�)ORZ

5HWDL

OHU

þ Ú é

_-ñ ð^ò ù.`põYaÛù ñ+ò ö ð`Yù ð3bdc&e�fwð9g ù/øih ñ�c�bb@ò ù ð^ñ ` ò�ó9b@ò ø)ù ð^ñ ö ò ù ò

j ö ö�`.õ�alknm�oñ ð^óYð�î^ò õ?ù g9c õ?ù ð õ?ùù c ù ñ�ò ö ð `Yù ð�b ø

p�X�q�r�s3t!up�X-q3r�s@t!u

v â"Ó�à�Ñ�Î�Þ"È Ý Î�Í0ÏAÑ�Ë�Ò0Ï+Õ�Ó�Ò4Õ ÏAÈwx yzw{ |}~ ��

� � � �� '�� ó'c�ò ö�`.õ&ab>ò ù ð{ñ ` ò�ó9b1ò ø�ù ð^ñö ò ù ò `põ)ù c k�m�o

Ú:Ñ�Ò[Ñ Ö Ì�Ì)É

ü ÏAÈ�Ñ�Ò�È�ÒKÏ=Ñ�Ê�ÈÇ Ò�È�Ð Ë

ü Ï=È�Ñ�Ò�È�ÒKÏ=Ñ�Ê�ÈÇ Ò�È�Ð Ë

� Ì Ñ"Ê v:ÿßÖÐ$Ñ�Ò=È"Ï4Ç Ñ É�Ê Ñ�Ò�Ñ� Ì Ñ"Ê v�ÿÖÐ Ñ�Ò�È Ï�Ç Ñ É�Ê�Ñ�Ò=Ñ

v Î�à�Ñ)Î�Ó�È þ Ú éÏ=È É È�æ�Ñ�Î�Ò?Ç%Î�Í=Ìv Î�à�Ñ�Î�Ó�È þ Ú éÏ=È É È�æ�Ñ�Î�Ò?Ç%Î�ÍAÌ

ÿ È�Þ�Ç Ë�Ò�È Ï ç Ç Ò�àÊ Ñ�Ò=Ñ@Ô�Ì�Ì)É

ÿ È�Þ?Ç Ë�Ò=È"Ï ç Ç ÒKàÊ"Ñ�Ò�Ñ1Ô�Ì�Ì?É

� ��

Ö Õ�Ø�É/Ç Ë)à�ÒKÌÒ0ÏAÑ�Ê?Ç/Î"Þ>Ô"Ñ Ï�Ò�Î�È Ï=ËÖ Õ�Ø ÉpÇ Ë)à�ÒKÌ

Ò0Ï=Ñ�Ê?Ç/Î"Þ>Ô"Ñ Ï�ÒKÎ"È Ï�Ë

� ð a=` ø)ù ð�ñ `.õYaù ñ�ò ö ð `[ù ð@b ø

� ð(� ÷ ð ø ù'`põYaù ñ4ò ö�`/õ&a� ò�ñ ù.õ ð^ñòYg ù.` c õ

�ß÷ e�ó ` øY�&`põPaù ñ4ò ö ð `[ù ð3b øù c ù ñ4ò ö9`põ&a� ò�ñ ù.õ ð^ñ ø

�

� Product data is extracted from the back end, for example, an SAP ERP system.

From the material master in ERP, some attributes are extracted into an IDoc and sent to SAP XI. Here, the IDoc is mapped to an XML message.

� Trade item objects are derived from the extracted data. In the GDS console, the trade items are created as objects from the information coming from ERP.

� Trade Items are enhanced with GDS-relevant attributes. Since the SAP definition of a SKU is different from the GS1 standard definition of a trade item, the new trade needs to be enhanced accordingly.

� A trade items message is created and sent to the AS2 adaptor. The trade item(s) is send to the data pool; the first step is to register a trade item with the data pool and the registry.

� The message is changed to a data-pool-specific format and forwarded to the data pool. The third-party adaptor (we have tested and certified only Seeburger, and we have a reseller agreement with Seeburger) is needed to transfer the XML message in the data-pool-specific format (AS2).

� A confirmation message is sent back from the data pool. The data pool confirms the successful reception and processing of the sent message.

� Confirmation/Rejection messages are sent back from the trading partners. GDS offers feedback from trading partners if they accept or reject a trade item.


SAP AG 2006



6XPPDU\

�


SAP AG 2006

*'6�&RQVROH

�


SAP AG 2006

8VHU�,QWHUIDFHV�

• 7KLQ�FOLHQW• ,QWXLWLYH�DQG�HDV\�WR�XVH• &XVWRPL]DEOH�VHDUFK�ILHOGV• 6LPSOH��VWDQGDUG�UROH�VHW

� (GLWRU��&DQ�DGG�DQG�PRGLI\�WKH�WUDGH�LWHP�GDWD�VWRUHG�LQ�WKH�V\VWHP

� 8VHU��/LNH�(GLWRU��EXW�FDQ�DOVR�UHJLVWHU�DQG�SXEOLVK�WUDGH�LWHPV

� $GPLQ��KDV�DOO�WKH�SULYLOHJHV�RI�WKH�XVHU�EXW�DOVR�KDV�DFFHVV�WR�WKH�PHWDGDWD�WDEOHV�DQG�WKH�XVHU�GHILQLWLRQ�WDEOHV

� &DQ�EH�HQKDQFHG�ZLWK�DGGLWLRQDO�UROHV�DQG�FRQVWUDLQWV

�


SAP AG 2006

8VHU�,QWHUIDFH�&RQILJXUDWLRQV

• 6XSSRUW�IRU�XVHU�GHILQHG�ILHOGV� $GG�ILHOGV�DQG�WDEOHV�WR�WKH�XQGHUO\LQJ�0'0�VFKHPD� 1HZ�LQERXQG�DQG�RXWERXQG�PRGXOHV�WR�VXSSRUW�LPSRUW�DQG�H[SRUW�

UHJDUGOHVV�RI�WKH�VFKHPD� 'HILQH�WKH�DSSHDUDQFH�RI�ILHOGV�LQ�WKH�*7,1�0DLQWHQDQFH WDE��HQDEOLQJ�

DGGLQJ��PRYLQJ�RU�UHPRYLQJ�WDEV��JURXSV�DQG�ILHOGV��DQG�GHILQLWLRQ�RI��GHIDXOW�YDOXHV�DQG�PDQGDWRU\�FRQVWUDLQWV

�


SAP AG 2006

8VHU�,QWHUIDFH�&RQILJXUDWLRQV��'HWDLOHG 9LHZ

�


SAP AG 2006

8VDELOLW\��9DOLGDWLRQ�RI�7UDGH�,WHPV

• 7R�HQVXUH�WKDW�DOO�VHOHFWHG�LWHPV�DUH�UHDG\�IRU�UHJLVWUDWLRQ��FOLFN�9DOLGDWHDW�WKH�ERWWRP�RI�WKH�OLVW�

• ,I�DOO�LWHPV�KDYH�EHHQ�YDOLGDWHG��FOLFN�%DFN DQG�FRQWLQXH�WR�WKH�QH[W�VWHS�

• 7R�FRUUHFW�IDLOHG�LWHPV��FOLFN�0RGLI\��7KH�*7,1�0DLQWHQDQFH VFUHHQ�LV�GLVSOD\HG�IRU�\RX�WR�HGLW�WKH�LWHP�LQIRUPDWLRQ�

�


SAP AG 2006

8VDELOLW\��7UDGLQJ�3DUWQHU�)HHGEDFN

7KH�8&&QHW�:RUNOLVW VFUHHQ�LV�GLVSOD\HG��OLVWLQJ�DOO�SXEOLVKHG�LWHPV�WKDW�WUDGH�SDUWQHUV�KDYH�UHVSRQGHG�WR�LQ�WKH�8&&QHW�ZRUNOLVW�

�


SAP AG 2006



6XPPDU\

�


SAP AG 2006

0'0�DQG�*OREDO�'DWD�6\QFKURQL]DWLRQ��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� ([SODLQ�WKH�SXUSRVH�RI�*'6� /LVW�WKH�UHDVRQV�IRU�XVLQJ�*'6

�


SAP AG 2006






3HUIRUPDQFH




�


SAP AG 2006

&RQWHQWV�� &XVWRPHU 'DWD ,QWHJUDWLRQ�6FHQDULR ZLWKLQ 0'0

&XVWRPHU�'DWD�,QWHJUDWLRQ��&',�

�


SAP AG 2006

&XVWRPHU�'DWD�,QWHJUDWLRQ��8QLW�2EMHFWLYHV

$IWHU�FRPSOHWLQJ�WKLV�XQLW��\RX�ZLOO�EH�DEOH�WR�� 'LVFXVV�WKH�0'0�&XVWRPHU�'DWD�,QWHJUDWLRQ�

%XVLQHVV�6FHQDULR

�


SAP AG 2006

&XVWRPHU�'DWD�,QWHJUDWLRQ��%XVLQHVV�6FHQDULR

� Your company maintains customer master data in a heterogeneous landscape of systems of various types and each system requires different information other than the basic name and address data.

� Without an application and overall strategy for managing master data, customer data can be modified in multiple systems by multiple people, leading to inconsistent data across the IT landscape.

� Your company anticipates that MDM will be able to solve this problem.

�


SAP AG 2006

:KDW�,V�&XVWRPHU�'DWD�,QWHJUDWLRQ"

&XVWRPHU�'DWD�,QWHJUDWLRQ��&',�� Is the process of consolidating and managing

customer data from all available sources

� Ensures that all relevant departments in the company have constant access to the most up-to-date and complete view of customer data available

� Is an essential extension to Customer Relationship Management (CRM)

�

� Why is CDI so important? y Improve cross-sell and up-sell efforts by providing a complete picture of

the existing customer relationship y Streamline business processes by eliminating manual rework caused by bad

data y Reduce costs by centralizing the management of customer data y Coordinate customer processes across business units and locations more

efficiently y Enable accurate analyses on a consolidated basis in order to make better

business decisions � What are the benefits?

y 360° view of customers and customer interactions y Easier maintenance of customer data – change once and propagate

many y Reduced marketing costs with less duplication and greater

personalization y Accuracy and reliability of all customer data-related analyses


SAP AG 2006

6$3�0'0�² &',�%XVLQHVV�6FHQDULR

&',�%XVLQHVV�6FHQDULR� Based on in-memory MDM core engine

� Provides Web services* to access customer data

� Features integration in SAP NetWeaver

� Offers tight integration with SAP CRM* and ECC

6$3�1HW:HDYHU�0'0�� ,V�D�H[WHQVLYH�IUDPHZRUN�IRU�PRGHOLQJ�EXVLQHVV�VFHQDULRV� 'HOLYHUV�NH\�FDSDELOLWLHV�WR�UXQ�,7��EXVLQHVV�VFHQDULRV� .H\�HQDEOHU�WR�PRYH�WR�D�VHUYLFH�RULHQWHG�DUFKLWHFWXUH

�� &�(� � ��(� �(��.¡7��£¢�¤=¥-¤B¦£§ ¦Y�#�!¨£©�


SAP AG 2006


,Q�PHPRU\�&DFKH([SUHVVLRQ��9DOLGDWLRQ

'DWD�0DQDJHPHQW

0'0�&

RUH 6HDUFK��,QGH[LQJ $XWKRUL]DWLRQ

,PSRUW�6HUYLFHV 6\QGLFDWLRQ�6HUYLFHV:RUNIORZ0HWD�0RGHO

5HSRVLWRU\

&',�9LVLRQ�² %XLOGLQJ�%ORFNV�DQG�3URFHVVHV

/RDGLQJ0DVWHU�'DWD

&RQVROLGDWLQJ0DVWHU�'DWD

0DLQWDLQLQJ0DVWHU�'DWD

ª�«3¬-

'LVWULEXWLQJ0DVWHU�'DWD

®P¯�¬(°�±!².«9¯ ³

´µ¬@¶

·(¸*¹�¹�ºn´�¬*» ¼3½

¾µ¸*» «À¿�Á-9¸@¶

´ÂÁ@¯.Ã3Á

Ä ¯KÁ!¬*»'Á*Å'Æ(9Ç »

Æ9°@¯�Ç ¼(½

È »'¬@°!3¬@¯.�Ç ¹�Á

¿�Ç ±!»É¯ Ç Ê(¸*»'Á

Æ�Ë-»É¯K¬!¼*»

´µ¬@¶

�


SAP AG 2006

&',�%XVLQHVV�6FHQDULR�² �

&RUH�&',�&DSDELOLWLHV� $G�KRF�DQG�VHPL�DXWRPDWHG�PDWFKLQJ�ZLWK�H[FOXVLRQ�VXSSRUW��

VLPXODWLRQ��DQG�UXOHV�WXQLQJ� %DVLF�VXUYLYRUVKLS�UXOHV�IRU�PHUJH� 2SHQ�LQWHUIDFHV�WR�WKLUG�SDUW\�GDWD�TXDOLW\�YHQGRUV�� ([WHQGHG�FRQVROLGDWLRQ�VFHQDULR�IRU�EXVLQHVV�SDUWQHUV� ,QLWLDO�VHW�RI�:HE�VHUYLFHV�VXSSRUWLQJ�&',�SURFHVVHV� ([WHQGHG�LQWHJUDWLRQ�WR�6$3�&50�DQG�(53� ,QIUDVWUXFWXUH�VXSSRUWLQJ�LQWHJUDWLRQ�WR�QRQ�6$3�&50�V\VWHPV

&RUH�&',�FDSDELOLWLHV�DOUHDG\�DYDLODEOH�WRGD\

�


SAP AG 2006

)XUWKHU�HQKDQFHG�&',�FDSDELOLWLHV� $XWRPDWLRQ�RI�SURFHVVLQJ�LQFOXGLQJ�H[FHSWLRQ�KDQGOLQJ� $GYDQFHG�VXUYLYRUVKLS�UXOHV�IRU�PHUJLQJ� 9HUVLRQLQJ� &HQWUDO�FUHDWLRQ�RI�REMHFWV�ZLWK�LPPHGLDWH�GLVWULEXWLRQ� $GGLWLRQDO�&',�UHODWHG�:HE�VHUYLFHV� $GYDQFHG�PDVWHU�GDWD�SURILOLQJ�FDSDELOLWLHV

(6$�FRPSOLDQW�&',�VROXWLRQ� ([WHQGHG�GDWD�PRGHOLQJ�FDSDELOLWLHV�ZLWK�VXSSRUW�IRU�GHHSO\�

VWUXFWXUHG�REMHFWV� 9HUVLRQ�UROOEDFN� )XOO�SURGXFW�DQG�EXVLQHVV�SDUWQHU�REMHFW�PRGHO�FRYHUDJH

&',�%XVLQHVV�6FHQDULR�² �

&',�EXVLQHVV�VFHQDULR�ZLOO�EHQHILW�IURP�FRUH�HQKDQFHPHQWV

�


SAP AG 2006

&',�%XVLQHVV�6FHQDULR�² 6XPPDU\�

&RQVROLGDWH�DQG�0DQDJH�&XVWRPHU�'DWD� )OH[LEOH�GDWD�KXE�WKDW�DOORZV�DXWRQRP\�RI�

FXVWRPHU�GDWD�IURP�EXVLQHVV�DSSOLFDWLRQV� %XVLQHVV�3DUWQHU�GDWD�PRGHO�WKDW�VXSSRUWV�ERWK�

%�%��%�&�LQWHUDFWLRQV� 3UH�SDFNHG�LQWHJUDWLRQ�WR�6$3�&50 �DQG�(53�� 3UH�LQWHJUDWHG�ZLWK�6$3�1HW:HDYHU��LQFOXGLQJ�

&',�VSHFLILF�:HE�VHUYLFHV� &XVWRPHU�GDWD�PDQDJHPHQW�FDSDELOLWLHV�VXFK�

DV�PDWFKLQJ��VWDQGDUGL]DWLRQ��DQG�VXUYLYRUVKLS� ,QWHUIDFHV�WR�WKLUG�SDUW\�GDWD�TXDOLW\�WRROV�DQG�

FRQWHQW�SURYLGHUV�� 8QEHDWDEOH�SHUIRUPDQFH�EDVHG�RQ�WKH�LQ�

PHPRU\�0'0�FRUH�HQJLQHÌ3Í@Î�Í!Ï Ð Í-Ñ3Ð ÒnÓPÏ�Ô�Õ×Ö-ØÂÙÀÚ7Ò!Ô�Û;Ò�Í3Î*Ò*Ü�Ý�Þ&Ýàß#á ß�Ö(ÙYâ�ã�


SAP AG 2006

&XVWRPHU�'DWD�,QWHJUDWLRQ��8QLW�6XPPDU\

<RX�VKRXOG�QRZ�EH�DEOH�WR�� 'LVFXVV�WKH�0'0�&XVWRPHU�'DWD�,QWHJUDWLRQ�

%XVLQHVV�6FHQDULR

�

mdm100 master data management

Documents

sap products

sap netweaver

dqdjhphqw sap ag

fhqdulrv sap ag

hdyhu hohduqlqj sap

registered trademarks

dqdjhphqw xudwlrq gdv

oo uljkwv uhvhuyhg sap