7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
1/18
BW Unic ode R/3 MDMP
Example to extract customer master data from a
mixed code page system into a Unicode system
Product Management Global SolutionsInternational Development, SAP AG
Product Management BI, SAP AG
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
2/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 2
Agenda
Motivation
MDMP Extraction Simple Case
MDMP Extraction Special Case
Technical Prerequisites
Appendix: Determining critical DataSources and InfoObjects
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
3/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 3
Mot iva t ion
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 needsto 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 aclear 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 exampleextracting customer master data
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
4/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 4
Sim ple Case: Language-Dependent Dat a
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 thecode 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 dataaccording to the code page assigned to a specific language
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
5/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 5
Sim ple Case: Ex t rac t ion of Language-DependentData
Customer Data SAP BW
Standard Extractor forcustomer data kicked off
in the SAP BW system
{Extractor willConvert
languageDependent dataAccording to theLanguage key
No additionalsetup is needed
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
6/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 6
Spec ia l Case: Language-Independent Mast er Data
In this case you have a table in your R/3 containing no language key like
this one:
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
7/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 7
Spec ia l Case: Language-Independent Mast er Data
Customer Data SAP BW
Standard Extractor forcustomer data kicked off
in the SAP BW system
{
Corrup
tedfor
MDMPData
Corrup
tedfor
MDMPDataxxx xxx
xxxxxxxx
xxxxxxxxxx
xxxxx
xxx
xxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxx
xxxxxxxxx
xxxxxxxxxxx
xxxxxxxxxxxxx
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
8/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 8
Spec ia l Case: Language-Independent Mast er Data
To determine the correct source code page, youll have to find an
attribute that defines the source. In this example, the code page ofthe customer can be determined out of the country where thecustomer lives. We can assume that customers living in China arewritten 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 sourcelanguage/source code page for each
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
9/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 9
Spec ia l Case: Language-Independent Mast er Data
Alternative 1: Simulate a language field extraction like in the
Simple Case by appending a language field to the extractstructure and filling it e.g. via a custumer exit
Example DataSource 0CUSTOMER_TEXT has extract structureROXAX40167
Extract structure ROXAX40167 can be appended by a language field likeSPRAS; 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
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
10/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 10
Spec ia l Case: Language-Independent Mast er 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 allLatin-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 ofextraction jobs (InfoPackages) equals the number of different codepages 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 allextraction jobs (InfoPackages)
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
11/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 11
Spec ia l Case: A l te rna t ive I I Ex t rac t ion fo r La t in -1Countr ies
Customer Data SAP BW
Extraction of allcustomers, where the
country belongs toWestern Europe
Logon language = DE
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
12/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 12
Spec ia l Case: A l te rna t ive I I Ex t rac t ion fo r Cyr i l l icspeak ing Countr ies
Customer Data SAP BW
Extraction of allcustomers, where the
country belongs to Cyrillicspeaking world
Logon language = RU
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
13/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 13
Specia l Case: A l t ernat ive I I Ex t ract ion for China
Customer Data SAP BW
Extraction of allcustomers, where the
country is China
Logon language = ZH
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
14/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 14
Spec ia l Case: A l te rna t ive I I Summ ary : Se lec t i veData Ex t rac t ion
Customer Data SAP BW
ExtractionCountry = China
ExtractionCountry = China
ExtractionCountry = Cyrillic
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
15/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 15
Technic a l Prerequis i tes
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 componentPI_BASIS 2002.1 SP3 or higher
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
16/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 16
Append ix : De te rm in ing c r i t i ca l Da taSources andInfoObjects
In the beginning of a project for MDMP-extraction it isgood to know which DataSources belong to thespecial case, i.e. manual work is necessary.
The following coding (for the source system) may helpto find these DataSources.
If you want to know the BW InfoObjects that are notlanguage-dependent, then implement the second codein your BW system.
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
17/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 17
Appendix : Sourc e 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.
7/31/2019 BW 3.1 Content Unicode and MDMP Extraction.ppt
18/18
SAP AG 2002, BW UnicodeR/3 MDMP, PM Global Solutions 18
No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission 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 othersoftware vendors.
Microsoft, WINDOWS, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks ofMicrosoft 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 andother 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 astheir respective logos are trademarks or registered trademarks of SAP AG in Germany and in several othercountries all over the world. All other product and service names mentioned are trademarks of their respectivecompanies.
Copyr ight 2003 SAP AG. Al l Right s Reserved