on 07-30-2009 8:00 AM
We are on 4.7x110 MDMP. We wish to do an system copy based on R3load to another server. According the note Note 516246 - INST: System Copy for SAP Systems based on SAP Web AS 6.20, we need to enter the dbcodepage = MDMP during the import, but there is no mention of the code page to be entered during export, do we use MDMP or stick to the default 1100.
Hi Thom,
On MDMP systems, R3load 6.x automatically uses a dummy code page called "MDMP", which indicates "do no conversion".
MDMP code page entry can be seen in the *.TOC file. So you no need to select a different code page while export.
For import you have to follow the manual correction as said in Note 516246.
System copy of MDMP system:
PROBLEM:
If you copy an MDMP system using the R3load unload/load method, then you have to enter 'MDMP' as DB code page on the dialog screen 'General Load Parameters' during the import phase. The XML files delivered with the installation pack will not allow to enter non-numeric values (like MDMP) as DB code page.
SOLUTION:
Edit the file dialog.xml in your installation directory before you start the installation:
1. Search for the string 'fiDBCodePage_i'.
2. Correct the line two lines further down by removing the 'type="numeric"' instruction:
OLD: <value maxlength="4" minlength="4" type="numeric">1100</value>
NEW: <value maxlength="4" minlength="4" >1100</value>
3. Repeat step 1.+ 2., because this correction has to be done twice!
Thanks,
Surendra
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi guys, just some updates, i managed to do the MDMP system copy succesfully.
Export using default cp 1100 (the export *.TOC files shows cp=MDMP ) and import using cp MDMP.
I think irrespective of what you enter as the export codepage, SAP can detect it is a MDMP source system and set the
cp accordingly during r3load export.
Edited by: Thom on Aug 13, 2009 1:41 PM
> I think irrespective of what you enter as the export codepage, SAP can detect it is a MDMP source system and set the
> cp accordingly during r3load export.
For the export - yes. "newer" versions of R3load can handle that.
but you must do the changes for the import, otherwise the system will import everything using 1100 (or 1160) and hence destroying the non-1100 data.
Markus
Dear Markus,
our case is almost the same like Thom's : exported in codepage 1100 and imported with MDMP in order to get the right migration key. After database upload during the importing we get the error rfc connection error in step "starting RFC job" . when we login to the system using SAPgui there are 2 error :
1. CONVERT_TSTMP_INCONSISTENT_TAB
we solved this problem after applying OSS note
2. No valid GUI codepage for language E (system codepage 1100)
and also we check there is no profile in the system.
Any comment ?
Thanks in advance
Aryanto/Engkan Tan
PS:
we also run RSCP0013 and we see :
Character set of SAPgui 1100
Char. set of appl. server 1100
we assume Character set of SAPgui should be 1160.
Dear Markus,
Using program RSCPINST we found the screen :
TCP0F: Frontend code pages
Some frontend code pages are missing in the table TCP0F.
You have to extend TCP0F with the languages displayed
in the table below. For details please refer to note 178893.
DE German
EN English
JA Japanese
from note 178893 we execute function module NLS_GET_FRONTEND_CP :
Test for function group S_NLS_2
Function module NLS_GET_FRONTEND_CP
Upper/lower case
Runtime: 517 Microseconds
Exception NO_FRONTEND_CP_FOUND
Import parameters Value
LANGU EN
FETYPE MS
Export parameters Value
FRONTEND_CODEPAGE 0000
Some how the front end code page still problem
please advice
Thanks in advance
Aryanto/Engkan Tan
User | Count |
---|---|
86 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.