BW Unicode R/3 MDMP. Product Management Global Solutions International Development, SAP AG. Product Management BI, SAP AG

Transcription

1 BW Unicode R/3 MDMP Example to extract customer master data from a mixed code page system into a Unicode system Product Management Global Solutions International Development, SAP AG Product Management BI, SAP AG

2 Agenda Motivation MDMP Extraction Simple Case MDMP Extraction Special Case Technical Prerequisites Appendix: Determining critical DataSources and InfoObjects SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 2

3 Motivation BW 3.1 Content is the first BW release to be rolled out using Unicode A motivation for BW under Unicode is, that data in multiple languages needs to be analyzed R/3 supports multiple code pages (MDMP technology) The code page is derived from the logon language Characters defined in different code pages may use the same hex value BW does not support MDMP The connection between a Unicode and a non-unicode system requires a clear definition, out of which code page the data is When sending data from MDMP to Unicode, a hex value is sent Without a language information, this hex code can not be assigned to a character, as more than one character is using this hex value in MDMP For data not being language dependent, a project solution must be found. This presentation will give an example extracting customer master data SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 3

4 Simple Case: Language-Dependent Data In this case you have a table in your R/3 containing the language key like this one: Note: It will be mandatory, that the data (characters) match the code page assigned to the language key It is forbidden to have e.g. Japanese data in an English data line The extraction from an MDMP system will extract the data according to the code page assigned to a specific language SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 4

5 Simple Case: Extraction of Language-Dependent Data Customer Data SAP BW Standard Extractor for customer data kicked off in the SAP BW system { Extractor will Convert language Dependent data According to the Language key No additional setup is needed SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 5

6 Special Case: Language-Independent Master Data In this case you have a table in your R/3 containing no language key like this one: SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 6

7 Special Case: Language-Independent Master Data Customer Data Standard Extractor for customer data kicked off in the SAP BW system xxxxxxxxxxxxx xxx xxxxxxxxxxx xxxxxxxxx xxxxx xxxxxxxxxxxxxxxxxxx SAP BW xxxxxxxx Corrupted for MDMP Data xxx xxxxxxxxxx xxxxx xxx xxxxxxx { SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 7

8 Special Case: Language-Independent Master Data To determine the correct source code page, you ll have to find an attribute that defines the source. In this example, the code page of the customer can be determined out of the country where the customer lives. We can assume that customers living in China are written in Chinese characters. If you have determined an attribute that segregates the different code pages within the table you have basically two possibilities: Simulate a language field extraction like in the Simple Case by appending a language field to the extract structure and filling it e.g. via a custumer exit Split the extraction process into several and define the source language/source code page for each SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 8

9 Special Case: Language-Independent Master Data Alternative 1: Simulate a language field extraction like in the Simple Case by appending a language field to the extract structure and filling it e.g. via a custumer exit Example DataSource 0CUSTOMER_TEXT has extract structure ROXAX40167 Extract structure ROXAX40167 can be appended by a language field like SPRAS; this field has to be of DDIC type LANG Mark the field (component) in the structure as a language field in SE11 (flag text lang ) This field is only available as of basis 6.10; before it chooses automatically the first field of type LANG in the structure Be sure that this field is filled in the extraction (e.g. via customer exit) This reduces the special case to the simple case and the correct conversion is done automatically SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 9

10 Special Case: Language-Independent Master Data Alternative 2: Split the extraction process into several and define the source language/source code page for each One connection to the source system is always linked to one code page, which is basically defined by the logon language in the SM37- batch job running the extraction A Latin-1 connection (e.g. language French or German) can extract all Latin-1-texts correctly into Unicode A Cyrillic connection converts Russian texts correctly into Unicode The extraction job must be split in several ones. The number of extraction jobs (InfoPackages) equals the number of different code pages in the source system table To set up the batch job language correctly, be sure that logon language field of the source system definition in transaction SM59 is empty and overwrite the logon language in transaction SM37 (step definition) for all extraction jobs (InfoPackages) SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 10

11 Special Case: Alternative II Extraction for Latin-1 Countries Customer Data SAP BW Extraction of all customers, where the country belongs to Western Europe Logon language = DE SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 11

12 Special Case: Alternative II Extraction for Cyrillic speaking Countries Customer Data SAP BW Extraction of all customers, where the country belongs to Cyrillic speaking world Logon language = RU SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 12

13 Special Case: Alternative II Extraction for China Customer Data SAP BW Extraction of all customers, where the country is China Logon language = ZH SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 13

14 Special Case: Alternative II Summary: Selective Data Extraction Customer Data Extraction Country = Cyrillic Extraction Country = China Extraction Country = China SAP BW SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 14

15 Technical Prerequisites BW 3.1 Content: Support Package 10 or higher Source System (R/3): Service API 3.0B SP5 or higher; this is contained in the component PI_BASIS SP3 or higher SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 15

16 Appendix: Determining critical DataSources and InfoObjects In the beginning of a project for MDMP-extraction it is good to know which DataSources belong to the special case, i.e. manual work is necessary. The following coding (for the source system) may help to find these DataSources. If you want to know the BW InfoObjects that are not language-dependent, then implement the second code in your BW system. SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 16

17 Appendix: Source Codes Determine all language-independent Source System DataSources: REPORT ZUC_LANGINDEP_DATASOURCES. tables: ROOSFIELD. select * from ROOSFIELD where objvers = 'A' and ( field = 'LANGU' or field = 'SPRAS' ) and ( selection = 'A' or selection = '2' or selection = '3' or selection = '4' ). write / roosfield-oltpsource. endselect. Determine all BW InfoObjects that are language-independent: REPORT ZUC_LANGINDEP_INFOOBJECTS. tables: RSDCHABAS. select * from RSDCHABAS where objvers = 'A' and nolangu = 'X'. write / rsdchabas-chabasnm. endselect. SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 17

18 Copyright 2003 SAP AG. All Rights Reserved No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server 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, z/os, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA 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, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML 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. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mysap, mysap.com 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 trademarks of their respective companies. SAP AG 2002, BW Unicode R/3 MDMP, PM Global Solutions 18