Livecache changes during SCM Unicode conversion

I am starting a unicode conversion of our SCM system which was just upgraded to 7.01. Before the conversion, our liveCache database was on a different host than our SCM system so we moved it to the same hardware. The process we used was to do a backup of the current liveCache, create a new instance on the new hardware and then do a restore of that liveCache from the original liveCache's backup.
For the Unicode conversion can we use this same process, but before restoring the liveCache, change the _UNICODE = 'YES' parameter for the liveCache? I read note 632357, but it didn't seem like that was neccessary, if I just created a new instance of liveCache where the SCM system target would land, changed the parameter and then did a restore from the backup?

Hello George,
1) The _UNICODE liveCache parameter should have the same value in the target liveCache instance as you have in the source liveCache instance, if you would like to do the
u201CHomogenous liveCache copy using backup/restoreu2019 using the SAP note:
457425 Homogenous liveCache copy using backup/restore
2) If you are planning to convert your system/liveCache to Unicode you have to follow all steps given in the SAP Note No. 632357.
3) If you have problems to follow the steps recommended in the SAP Note No. 632357, please create the SAP message to the component BC-DB-LCA, so we could discuss your issues in details.
Thank you and best regards, Natalia Khlopina

Similar Messages

During the Unicode conversion , Cluster table export taken too much time ap

Dear All
during the Unicode conversion , Cluster table export taken too much time approximately 24 hours of 6 tables , could you please advise , how can we reduse the time
thanks
Jainnedra

Hello,
Use latest R3load from market place.
also refer note
Note 1019362 - Very long run times during SPUMG scans
Regards,
Nitin Salunkhe

SCM Unicode Conversion - Initialize LC or not??

We have recently upgraded our non unicode SCM 5.0 systems to SCM7 EhP3 and we now want to convert these systems to Unicode.
We will be running most of the unicode conversions in situ, ie run all the unicode conversion steps and /SAPAPO/OM_LC_DOWNLOAD_UPLOAD (A&B) , export the database, drop the original non unicode system, reinstall a unicode SCM system and then import the database, followed by /SAPAPO/OM_LC_DOWNLOAD_UPLOAD (C) etc..
On one of the servers however we have 2 SCM systems installed and will use the unicode conversion to move one of the SCM systems to a new server during the database export/import phase, so finally down to my questions!
1) For the in situ Unicode conversions, I take it that we DO NOT have to initialize LC when reinstalling the Unicode SCM system and that we can use param_put DEFAULT_CODE Unicode and alter user SAP<SID> DEFAULTCODE UNICODE before running Step C of /SAPAPO/OM_LC_DOWNLOAD_UPLOAD?
2) For the Unicode conversion including the database export/import (homogenous system copy) to the new server, do we have to initalize livecache as part of the SCM install?
Regards,
Mark

Hi Mark,
Please cehck below thread,
Restore backup of a Non Unicode to a Unicode Live Cache
1319517 - Unicode Collection Note
BR
AKJ

Unicode conversion with MDMP, Errors in various TC´s SAINT , SNOTE,

Hallo All,
We perform CU&UC of R/3 4.6C sandbox system to the ERP 6.0 EHP5.
Currently the upgrade phase is completed and Unicode conversion should
be started (we are in the step "Additional Preparation Steps in NW 7.02
non-UC" in the CU&UC guide).
In various transactions (PFCG - Generating of profiles, SPAM/SAINT ) we
received an error "SAP characters 00367 and 00065 are not unique in
character set 1180". As a workaround we temporarily deleted Polish
language (PL) in program RSCPINST and activated (so only codepage 1100
was active). Currently we have activated the Polish language again.
In the source 4.6C system TMB (created by System Copy from productive
system PMB) there was also the configuration in RSCPINST of more than 1
codepage (1100, 1401) and in TCPDB table 1180 codepage was configured
(see attached pictures).
Our question :
How is it possible to avoid this situation in upgrades of following
system (IMB, QMB, PMB)? Could this configuration cause any
problems/inconsistencies during/after Unicode conversion export &
import ?
Regards Peter Gauer

Hello Nils,
After upgrade, before unicode conversion we got the following error message in PFCG, SAINT,..
"SAP characters 00367 and 00065 are not unique in character set 1180"
I got the information from T-Systems that they excluded polish languages out of RSCINST,
then codepage 1100 was used, than T-Systems added polish language again to have the original situation.
First message I got with the simulation (choose blank latin-1)
The required language combination is supported
only in Unicode systems
Please refer to SAP Note 73606.
Now I Choose: 4EU, EuropTranslit
and simulation showed no message above, but went to the next page.
see below
S e l e c t e d   S e t t i n g s :
Language(s):
EN (E) English
FR (F) French
DE (D) German
PL (L) Polish
ES (S) Spanish
Country code:
4EU    EuropTranslit
R e s u l t s :
Code page configuration type:
Non-Unicode - Single Code Page configuration
Processed language entry:
DEFLS
Language(s) and Corresponding Code Page(s):
EN (E) 1180   Transliteration from Latin-2 (...) to Latin-1
FR (F) 1180   Transliteration from Latin-2 (...) to Latin-1
DE (D) 1180   Transliteration from Latin-2 (...) to Latin-1
PL (L) 1180   Transliteration from Latin-2 (...) to Latin-1
ES (S) 1180   Transliteration from Latin-2 (...) to Latin-1
T a s k s :
Required OS locales and their current status:
Locale installed     = the locale is installed correctly
Set locale failed    = the locale needs to be corrected on the app server
citmb07_TMB_07       de_DE.ISO-8859-1               Locale installed
                     en_US.ISO-8859-1               Locale installed
                     fr_FR.ISO-8859-1               Locale installed
                     de_DE.ISO-8859-1               Locale installed
                     es_ES.ISO-8859-1               Locale installed
Required profile parameter modifications:
RSCPINST does NOT change the value of profile parameter.
Please check the value of below parameter(s) after activation.
1) Please update zcsa/installed_languages.
    e.g. Copy the new value and paste it into a field in transaction RZ10
New:                  DEFLS
Current (sorted):
citmb07_TMB_07       DEFLS
2) Please proceed with Check result for below parameter(s):
OK     Checked and no inconsistency found.
Regards Peter

Alignment all out after unicode conversion

The system is now unicode compliant.
The purchase order, invoice that has Chinese text as line item are all printed out of alignment.
It had pushed the next field towards the right.
I understand it is becuase of the unicode character / bytes difference.
Can someone shared with me how can I modified the sapscript to get it back in alignment?
Please provide a sample.
Thanks
bye

Hi,
I have read the thread before. It doesn't help in my case.
To share it with you,
I realised that I can place a length field after the field.
Previously I could use &EKPO-TZX01(40)&. Now I had to remove it to &EKPO-TZX01&.
it works for some but not all sapscripts.
For those that doesn't work, I will have to changed it as well as setting the tab using a separate paragraph.
So much to change after this unicode conversion.
Thanks

Unicode conversion - space allocation

Hi All -
We are starting to look at converting our system to Unicode this summer, and I'm worried that we have enough space allocated on UNIX box to allow for successful conversion!
I have read the Unicode conversion guide for allocating additional space to tablespaces on the database, but does anyone have any words of caution / wisdsom for non-tablespace related space needs during a Unicode conversion? For example, I think I have all our /oracle/[sid]/sapdata directories accounted for - I am just trying to determine if I'm missing anything else.
Input is appreciated. Thanks!
Abby

Hi Abby,
additional Hardware requirements due to Unicode are described in SAP note 1139642.
There are no general rules for the additional hardware components needed for a Unicode conversion.
This highly depends on your planned scenario (One Server inplace / new Unicode server) and your downtime requirements. But even knowing the details no one will be able to give exact figures.
If you are lucky, you might find someone who did a similar scenario on comparable hardware.
However we highly recommend to plan for a Sandbox conversion (with a copy of your PRD system), which will be the best approach to find out reliable downtime figures and possible hardware bottlenecks.
Please also have a look at SAP note 857081.
Best regards,
Nils Buerckel
SAP AG

Unicode conversion causing OCRA, OCRB, and MICR lines to output as symbols

Hi,
I am tesing the printing of SAPScript invoices in a Unicode converted sandbox copy of our production system. When viewing the OTF output of an invoice I noticed that the line for postal barcode using OCR-B font is producing # symbols instead of numbers reprsenting the postal zip code. This works in the Non-Unicode environment on our production server.
The printer is an HPLJ8150. The device type for the printer that is used for the invoice, is ZHP8150, which uses the base device type of HPLJ8000. The character set is 1116, which is ISO 8859-1.
Can anyone tell me how to go about correcting this problem?
Any help will be greatly appreciated.
Thanks,
Mark

Hi Nils,
Thank you for the information. I have created a new message in the Form Printing forum. Since this is something that was changed after the unicode conversion, I think I will leave this message open a little while longer incase someone who experienced this type of issue is looking in this forum.
Two things I should add. One, the font used for the device type is working in a Non-Unicode production system at this time. Two, the OTF output of the spool is not printed on our printer but is instead converted to XML and the resulting file is FTP'd to a third party for printing. So the zip code that is represented by the bar code font is just the numerical text that is in the OTF output which is sent in the XML file.
Regards,
Mark

MDMP Unicode Conversion problem during ECC upgrade

hi Experts,
I met a problem when upgrade from 4.6c to ecc 6.
in 4.6c, some key users made some chinese written entries in table field while he/she was logon as English, so, the language field in this entry is "EN" although the actual language was written by chinese, after upgrade to ECC6, we found the chinese words became messy code, maybe it was due to the chinese were encoded by english codepage during conversion, my question is, how can I avoid this? I really don't want this happen in our PRD upgrade.
The second question is: if a field contains both chinese and english, then, which language should it be assigned? english or chinese? I'm afraid if we assign this word as "EN" in vocabulary, then, after upgrade, the chinese part will be messy code.
Thank you for your kind suggestions.
Freshman

Hi,
you can either use transaction SUMG (manually) to repair the entries ( you have to add the according table - please check unicode conversion guide for details) or you need to change the language key in the table to Chinese if you want the Unicode conversion to convert the data correctly.
To your second question: If the English texts are restricted to US7ASCII characters ("normal" English without special characters) those texts containing Chinese and English words can (and must !) be assigned to ZH, as US7ASCII characters are included in the Chinese code page.
Best regards,
Nilsn Buerckel

Could you pls give the details about the Unicode conversion during Upgrade

Hi,
Can anyone give details about the Unicode conversion during SAP Upgradation fro 4.6C to ECC6.
Waiting for quick response
Best Regards,
Padhy

Hi,
These are the few points i gathered during my upgradation project.
Before starting any upgradation project, it is necessary to take up the back-up of the existing systems. As we are going to upgrade the entire system, we will be changing so many things and if something happens, without back-up, we will be in a trouble.
So it is advised to keep a back-up of the existing system.
Say for example we have the existing system E4B which is of Version 4.6C. Now we want to upgrade it to Version 4.7. Let us see how we can do it.
Version upgrades not only means that we need to run the new Version CD over the existing Version System but only involves some other thing.
Version Upgrade involves the following Steps.
Say we want to upgrade for Version 4.7 from Version 4.6, which is in the System E4B. Now we created one more system called as E1B in which the upgradation for Version 4.7 can be done.
First copy the entire E4B system into the E1B System which is created for Version 4.7.
Apply the Version 4.7 CD provided by SAP over the E1B System.
Now check whether all the functionalities that was in E4B system works fine with E1B system also.
Thus the Version Upgrade involves two steps.
1. SAP Upgradation with the help of the CD
2. Manual Upgradation.
1. SAP Upgradation with the help of the CD
This is nothing but after taking the copy of the existing system into a new system, the upgradation CD from SAP is applied over the new system.
2. Manual Upgradation.
This Manual Upgradation involves
2.1 Upgradation of Standard Objects
2.1.1 SPAU Objects
2.1.2 SPDD Objects
2.2 Upgradation of Custom Objects.
Upgradation of Custom Objects can be placed under the following three categories.
Unicode Compliance
Retrofit
Upgrade
Please Find below some of the common Unicode Errors and their solutions
1. Error:
In case of Translate Error; Dangerous use of Translate in Multilingual system.
Correction:
To correct the Error occurring on TRANSLATE statement use this additional statement before the Translate statement.
SET LOCALE LANGUAGE sy-langu.
This statement defines the Text Environment of all the programs & internal sessions in the language specified in the LANGUAGE KEY, which in this case is sy-langu, i.e. the log on language of the user.
2. Error:
In case of Open Dataset Error; Encoding Addition must be included.
Correction:
This Error occurs only when the MODE is TEXT.
To correct the Error occurring on OPEN DATASET statement use this statement instead.
OPEN DATASET dataset_name FOR access IN TEXT MODE ENCODING DEFAULT.
Where: dataset_name NAME OF THE DATASET.
Access INPUT or OUTPUT or APPENDING or UPDATE.
DEFAULT - Corresponds to UTF-8 in UNICODE systems &
NON_UNICODE in NON-UNICODE systems.
3. Error:
In case of the usage of the Obsolete FM UPLOAD/DOWNLOAD or WS_UPLOAD/DOWNLOAD; Function module UPLOAD is flagged as obsolete.
Correction:
The FM GUI_DOWNLOAD/UPLOAD is used.
The variations to be made in the parameters of the FM:
1. Filename It must be of STRING type.
2. Filetype DAT is not used any longer, instead ASC is used.
3. Field Separator The default value SPACE is used, incase for a TAB separated file X can be used.
4. Error:
In case of CURRENCY/UNIT Addition Error; Use addition CURRENCY/UNIT when outputting.
Correction:
The CURRENCY addition specifies the currency-dependant decimal places for the output of the data objects of type i or p. To obtain the currency-key, the field CURRKEY of the table TCURX is used. The system determines the number of the decimal places from the field CURRDEC of the selected CURRKEY.
To correct this error follow the following method:
WRITE: /3 'TOTAL',' ', TOTAL.
WRITE: /3 TOTAL, , TOTAL CURRENCY 2. --- Where 2is the Currency Key for Getting 2 decimal places.
5. Error:
In case of TYPE X Error; Variable must be of C, N, D, T or STRING type.
Correction:
We need to change all the Type X (Hexadecimal) variables to Type C with their values unchanged.
So the method to be followed is:-
1. Load the definition of the class CL_ABAP_CONV_IN_CE or CL_ABAP_CHAR_UTILITIES.
2. Declare the variable as Type C, and use the method UCCP(XXXX) of the class CL_ABAP_CONV_IN_CE where XXXX represents the 8-bit Hexadecimal value and incase the variable holds a Hex value for a Horizontal Tab , then the Attribute HORIZONTAL_TAB of the class CL_ABAP_CHAR_UTILITIES can be used directly instead of using the method UCCP.
E.g.:
i) *DATA: TAB TYPE X VALUE 09, Tab character
CLASS: CL_ABAP_CHAR_UTILITIES DEFINITION LOAD.
DATA TAB TYPE C VALUE CL_ABAP_CHAR_UTILITIES=>HORIZONTAL_TAB.
ii) * DATA: CHAR TYPE X VALUE 160.
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA CHAR TYPE C.
CHAR = CL_ABAP_CONV_IN_CE=>UCCP(00AO).
(Here 00A0 is the Hexadecimal equivalent of the decimal 160).
3. Incase the TYPE X Variable has a length more than 1, then an internal table must be created for the variable.
E.g.:
CLASS: CL_ABAP_CONV_IN_CE DEFINITION LOAD.
DATA : LF(2) TYPE X VALUE 'F5CD'.
DATA : BEGIN OF LF,
A1 TYPE C,
A2 TYPE C,
END OF LF.
LF-A1 = CL_ABAP_CONV_IN_CE=>UCCP('00F5').
LF-A2 = CL_ABAP_CONV_IN_CE=>UCCP('00CD').
6. Error:
In case of the Character -Error; The Character -cant appear in names in Unicode Programs.
Correction:
The Character -(Hyphen) appearing in Variable names is replaced by the character _ (Under Score) for Unicode/Upgrade Compliance.
E.g.:
*wk-belnr LIKE bkpf-belnr,
*wk-xblnr LIKE bkpf-xblnr,
*wk-date LIKE sy-datum,
*wk-wrbtr LIKE bseg-wrbtr,
*wk-name1 LIKE lfa1-name1,
*wk-voucher(8) TYPE c.
wk_belnr LIKE bkpf-belnr,
wk_xblnr LIKE bkpf-xblnr,
wk_date LIKE sy-datum,
wk_wrbtr LIKE bseg-wrbtr,
wk_name1 LIKE lfa1-name1,
wk_voucher(8) TYPE c.
7. Error:
In case of The SUBMIT-TO-SAP-SPOOL Error; you should not use the statement SUBMIT-TO-SAP-SPOOL without the WITHOUT SPOOL DYNPRO addition.
Correction:
1. Declare variables of type PRI_PARAMS, ARC_PARAMS, and a variable of TYPE C which would be used as a VALID FLAG.
2. Call the FM GET_PRINT_PARAMETERS:
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
3. Use the SUBMIT-TO-SAP-SPOOL statement.
E.g.:
     submit zrppt500
     using selection-set 'AUTO3'
     with res_no eq lo_rsnum
     with sreserv in preserv
     to sap-spool destination p_dest
     immediately 'X'. "print immediate
DATA: print_parameters type pri_params,
archive_parameters type arc_params,
valid_flag(1) type c.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
ARCHIVE_MODE = '3'
DESTINATION = P_DEST
IMMEDIATELY = 'X'
IMPORTING
OUT_ARCHIVE_PARAMETERS = archive_parameters
OUT_PARAMETERS = print_parameters
VALID = valid_flag
EXCEPTIONS
INVALID_PRINT_PARAMS = 2
OTHERS = 4
Submit zrppt500
Using selection-set 'AUTO3'
With res_no eq lo_rsnum
with sreserv in preserv
to sap-spool
SPOOL PARAMETERS PRINT_PARAMETERS
ARCHIVE PARAMETERS ARCHIVE_PARAMETERS
WITHOUT SPOOL DYNPRO.
8. Error:
In case of Message Error; Number of WITH fields and number of Place Holders are not same .
Correction:
Split the statement after WITH into the same number as the place holder for that Message ID.
E.g.:
1. * MESSAGE E045.
MESSAGE E045 WITH '' ''.
2. in program ZIPI0801
     Start of change for ECC6
     message e398(00) with 'Could not find access sequence'
     'for condition type:'
     p_ptype.
message e398(00) with 'Could not find '
'access sequence'
'for condition type:'
p_ptype.
     End of change made for ECC6
9. Error:
In case of Move between 2 different Structures; The structures are not mutually convertible in a Unicode program.
Correction:
Make both the Data Types compatible and then assign the contents.
E.g.:
The statement move retainage_text to temp_text. Gives an error, where RETAINAGE_TEXT is an internal table and TEMP_TEXT is a string of length 200.
A Feasible solution for this is to specify from which position to which position of the string, the fields of RETAINAGE_TEXT should be assigned.
TEMP_TEXT+0(1) = RETAINAGE_TEXT-DQ1.
TEMP_TEXT+1(1) = RETAINAGE_TEXT-HEX.
TEMP_TEXT+2(20) = RETAINAGE_TEXT-FILLER1.
TEMP_TEXT+22(15) = RETAINAGE_TEXT-AMT_DUE.
TEMP_TEXT+37(8) = RETAINAGE_TEXT-TEXT.
TEMP_TEXT+45(10) = RETAINAGE_TEXT-DUE_DATE.
TEMP_TEXT+55(1) = RETAINAGE_TEXT-DQ2.
10. Error:
In case of no description found; add a GUI title.
Correction:
In this type of error gui title is generally missing so add a GUI title to the module pool.
11. Error:
In case of writing internal or transparent table
Correction:
Write individual fields.
E.g.:
WRITE: / EXT. --> EXT should be a character type field
WRITE: / EXT-ZZSTATE, EXT-LINE_NO, EXT-LINE_TXT, EXT-AMT, EXT-ZZSKUQTY.
12. Error:
In case of combination reference table/field S541-UMMENGE does not exist
Correction:
Was due to error in reference table S541. TABLE S541 has errors
1)Foreign key S541- ZZMARKET (ZZMARKET AND KATR2 point to different domains)
2)Foreign key S541-ZZACQUIGRP (ZZACQUIGRP AND KATR8 point to different domains)
Changed the domain of ZZMARKET (from ZMKCODE to ATTR2)
And that of ZMKCODE (from ZACCODE to ATTR8)
13. Error:
In case of KEY does not exist
Correction:
The reference table for field KBETR was KNOV earlier changed it to RV61A as KNOV was in turn referring to RV61A.
14. Error:
Incase of WRITE statement, Literals that take more than one line is not permitted in Unicode systems.
Correction: To correct this error, we need to align the spaces accordingly so that the statement doesnt go beyond the line.
15. Error:
Incase of Data statement, The data type ZWFHTML can be enhanced in any way. After a structure enhancement, this assignment or parameter might be syntactically incorrect..
Correction: To correct this error, instead of like in the Data statement, use type.
16. Error:
Incase of DESCRIBE statement, DESCRIBE can be used only with IN BYTE... Or IN CHARACTER mode in Unicode systems.
Correction: To correct this error, use additional text, IN BYTE MODE / IN CHARACTER MODE along with this statement.
CHARACTER MODE is added when the data object is of flat/ character type.
BYTE MODE is added when the data object is a deep structure.
Syntax: DESCRIBE FIELD data_obj : LENGTH blen IN BYTE MODE,
LENGTH clen IN CHARACTER MODE.
Where blen and clen must be of type I.
17. Error:
Incase of DO-LOOP Error, In Do loop range addition needed
Correction:
An internal tables is declared and the two fields (VARYING field and NEXT field) were
Included inside the internal table
E.g.: In program SAPMZP02
DO 11 TIMES
     VARYING STATION_STATE FROM STATION1 NEXT STATION2. ECC6
CASE SYST-INDEX.
WHEN 1
STATION_STATE = STATION1.
WHEN 2
STATION_STATE = STATION2.
WHEN 3
STATION_STATE = STATION3.
WHEN 4
STATION_STATE = STATION4.
WHEN 5
STATION_STATE = STATION5.
WHEN 6
STATION_STATE = STATION6.
WHEN 7
STATION_STATE = STATION7.
WHEN 8
STATION_STATE = STATION8.
WHEN 9
STATION_STATE = STATION9.
WHEN 10
STATION_STATE = STATION10.
WHEN 11
STATION_STATE = STATION11.
18. Error:
Incase of the parameter QUEUE-ID Error, QUEUE-ID is neither a parameter nor a select option in program rsbdcbtc.
Correction:
The parameter in program rsbdcbtc is QUEUE_ID and so is changed in this program
E.g.: In program Z_CARRIER_EDI_INTERFACE
     submit rsbdcbtc with queue-id = apqi-qid and return. "ECC6
     The parameter name changed by replacing '-' with '_' as in program rsbdcbtc "ECC6
Submit rsbdcbtc with queue_id = apqi-qid and return. "ECC6
19. Error:
Incase of EPC Error, Field symbol <TOT_FLD> is not assigned to a field .
Correction:
This error couldn't be rectified as the error occurs in a Standard SAP include- LSVIMF29.
The OS Note - 1036943 needs to be applied.
Error:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE.
Correct:
OPEN DATASET P_FILE FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
Error:
Constants : c_tab type x value '09' .
Correct:
Constants : c_tab type abap_char1 value cl_abap_char_utilities=>horizontal_tab .
Error:
Data : begin of output_options occurs 0 . Include structure ssfcompop.
Data : end of output_options .
Correct:
Data : output_options type standard table of ssfcompop with header line .
Error:
PARAMETERS : NAST TYPE NAST .
Correct:
PARAMETERS : NAST TYPE NAST NO-DISPLAY .
Replace WS_DOWNLOAD and WS_UPLOAD by
GUI_UPLOAD and GUI_DOWNLOAD and check the import and export parameter types , do the changes accordingly. Because FILENAME paramater type is different because of this it will give dump.
For issue during Issue using SO_NEW_DOCUMENT_ATT_SEND_API1 Function module, the solution is After this FM we should put COMMIT WORK.
Issue:
Moving data from one structure to another structure if those two structures are not compatible
Solution:
we should use move-corresponding or field by filed we need to move it.
If database structures are different in 4.6c and ECC6.0,
Then we should go with append structure concept.
While testing the report if it gives dump at Select query level or any database or view level,then just goto that table or view and goto the data base utility(se14) adjust the database. But make sure that selected radio button in se14 transaction should be activate and adjust database
Also Check this link.
http://help.sap.com/saphelp_nw04/helpdata/en/62/3f2cadb35311d5993800508b6b8b11/frameset.htm
Reward points if helpful.
Regards,
Ramya

Error in Import during unicode conversion

Hello,
I am doing Combined upgrade and unicode conversion to ECC6 SR3.
Upgrade is completed sucessfully. During import i get an error stating :
bSl Trace: Error 959 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-959 occurred when executing SQL stmt (parse error offset=92)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "REPOLOAD~0" ON "REPOLOAD" ( "PROGNAME", "R3STATE", "MACH" ) TABLESPACE PSAPSID620 STORAGE (INITIAL 209
7152 NEXT 0000010240K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
DbSlExecute: rc = 99
(SQL error 959)
error message returned by DbSl:
ORA-00959: tablespace 'PSAPSID620' does not exist
This tablespace doesnt exist as it was upgraded to PSAPSID700.
I checked DBLORA.TPL and it has two references of 620 :
index storage parameters
loc: APPL0 PSAP@SCHEMAID@                 0000
     APPL1 PSAP@SCHEMAID@                   0000
     APPL2 PSAP@SCHEMAID@                  0000
     CLUST PSAP@SCHEMAID@                  0000
     DDIM PSAPDIMI                                      0000
     DFACT PSAPFACTI                                0000
     DODS PSAPODSI                                   0000
     POOL PSAP@SCHEMAID@                  0000
     SDIC PSAP@SCHEMAID@                     0
     SDOCU PSAP@SCHEMAID@                  0000
     *SLDEF PSAP@SCHEMAID@620              0000*
     *SLEXC PSAP@SCHEMAID@620            0000
     SLOAD PSAP@SCHEMAID@                  0000
     SPROT PSAP@SCHEMAID@                   0000
     SSDEF PSAP@SCHEMAID@700              0000
     SSEXC PSAP@SCHEMAID@700              0000
Thanks,
FBK

Hi Volker,
Thank you very much. Stupid error :-).
I also did step 2 with fixr3owns yesterday with SAPINST and then it worked. I got to step 3 "iSeries Installation Step", but got an error in SAPINST when "Creating infrastructure for SAP system BND". I logged off SAPINST, patched CRTR3SYS and started SAPINST again and then got the error in step 2 wirh fixr3owns.
I´m now past step 2 and in step 3 "iSeries Installation Step". And I get the same error as I got yesterday...
From the job log:
TMKSVR request processor: request was successful
Processing request from client 10.96.220.5:4350.
EXECUTE CRTR3SYS SID(BND) GLOBALHOST('SAP002') FORCEPROF(*NO)
ADBHOST('SAP002') 1 N
Keyword GLOBALHOST not valid for this command.
Keyword FORCEPROF not valid for this command.
Keyword ADBHOST not valid for this command.
Error found on CRTR3SYS command.
Errors occurred in command.
error: call_AS400_command: "CPF0006" caught after "CRTR3SYS SID(BND)
GLOBALHOST('SAP002') FORCEPROF(*NO) ADBHOST('SAP002')"
I can run "CRTR3SYS SID(BND) GLOBALHOST('SAP002') FORCEPROF(*NO)" manually.
Do you have any ideas?
Best regards
Henrik Hviid

Performance during Unicode Conversion

Hello,
currently we are planning to do a Unicode Conversion on a Linux/MaxDB System.
The DB has a size of approx. 350 GB. The system runs on Fujitsu-Siemens FlexFrame hardware.
One problem is that during a test conversion the export of the DB took more than 24 hours.
This seems too much regarding the DB size.
We know that filesystem and RAM and CPUs influence the export duration.
What possibilities do we have to tune the export with "software" tools?
- table splitting
For example: Our largest table has ~26GB datasize.
How do we split this table?
In 10 parts or in 20 or in 200?
If you could please post your experiences.
Regards, Michael

I don´t wanna discourage you but I´m not sure if splitting that single table will help alot.
The problem with this combination is the fact, that the MaxDB database reads data block-by-block, means, exeucting single I/Os for each block to read. Given that fact and the fact, that each I/O will be ran over an NFS (with the known latency) it´s unlikely that you will get much more speed out of this.
The problem is NOT the speed between the NAS and the database server, if you will look on the network traffic you will see, that there´s plenty left. The problem is the latency on the client side (the database server) when you put your files on NFS.
I can export a 250 GB database in under 3 hours (admittedly - without UC conversion) using a direct fibrechannel connection (so non-NFS) so the database itself is certainly not the problem, it´s the combination of the usage of NFS (no matter if v2 or v3) and the way the MaxDB database reads data.
I´ve been involved in a likewise project and with a NetApp specialist and some in-depth tuning we were able to gain 15 - 20 % speed but not more.
Markus

SAPInst Export Error during Unicode Conversion

Hello,
I started SAPInst, to export the source instance (for unicode conversion).
During the export preparation phase, I get the following error (in SAPInst)
ERROR
CJS-00030: Assertion failed: in component: NW_getDBInfo step: fillContextat this point the dbtype has to be != ind
ERROR
MUT-03025 Caught ESAPinstException in Modulecall:
ESAPinstException: error text undefined
ERROR
FCO-00011 The step fillContext with step key
|NW_Prepare_Export| ind| ind | ind | ind |0 |0 |NW_GetSidromProfiles |ind |ind |ind |ind |2 |0 |NW-getDBInfo |ind |ind |ind |4 |0 | fillContext was executed with status ERROR
Please help me how to rectify this error.
Thanks,
Haleem

Hello,
I recently experienced this problem, and it seems that when executing this step the <sid>adm account needs to be defined to use C shell. If its already set up to use C shell, check the <sid>adm logon scripts to make sure all the environment variables are being set correctly.
Regards,
Brad

Error during unicode conversion

Dear all,
we are facing one issue during unicode conversion. the code is as follows:
FIELD-SYMBOLS : <n> TYPE X,
                             <c> TYPE C.
DATA : a TYPE i.
DATA : x TYPE x.
MOVE <n> TO a.
a = a + 22.
MOVE a TO x.
ASSIGN x TO <c> CASTING TYPE c
and we are getting the following error:
ERROR : the length of "X" in bytes must be a multiple of the size of a Unicode character (regardless of the size of the unicode character
please guide on how this can be resolved in ECC.
Regards,
N.Jain

Hi,
here is some code to do it:
FIELD-SYMBOLS : <n> TYPE x,
                <c> TYPE c.
DATA : a TYPE i.
DATA : x TYPE x.
MOVE <n> TO a.
a = a + 22.
MOVE a TO x.
DATA:
buffer TYPE xstring,
conv TYPE REF TO cl_abap_conv_in_ce,
x_char.
buffer = x.
conv = cl_abap_conv_in_ce=>create(
       encoding = 'NON-UNICODE'
       input = buffer
CALL METHOD conv->read(
EXPORTING
    n    = 1
IMPORTING
    data = x_char
ASSIGN x_char TO <c>.
Regards
Walter Habich
Edited by: Walter Habich on Jun 10, 2008 4:09 PM

Error during Unicode Conversion - Import

Hi,
I am doing a Unicode conversion, done with the system export, while doing the
import during the Import ABAP phase system is throwing the error with R3load.
R3load -testconnect fails with following error.
emalonsbx002:wuuadm 18% R3load -testconnect
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
R3load: START OF LOG: 20071113095228
R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
R3load: version R7.00/V1.4 [UNICODE]
Compiled Oct 20 2007 06:20:06
R3load -testconnect
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1033
DbSl Trace: CONNECT failed with sql error '1033'
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1033
DbSl Trace: CONNECT failed with sql error '1033'
(DB) ERROR: db_connect rc = 256
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1033
DbSl Trace: CONNECT failed with sql error '1033'
DbSl Trace: OCI-call 'OCISessionBegin' failed with rc=1033
DbSl Trace: CONNECT failed with sql error '1033'
(DB) ERROR: DbSlErrorMsg rc = 99
R3load: job finished with 1 error(s)
R3load: END OF LOG: 20071113095230
Please let me know if anybody have any idea on this.
Thanks in advance.

Your database isn´t fully started yet (in shutdown or startup) - check your alert.log
Also see
Note 655240 - Composite SAP note: ORA-01033
Markus

Changes in source system dyring Unicode conversion

Hi,
I've upgraded our R/3 non-Unicode installation to ERP 6.0 non-Unicode using CU&UC guide. Now I plan to do the export & import phase to migrate the source system to Unicode.
My question is, does the export phase (where the Unicode conversion actually takes place) do any changes in the source system? It' is a production system, and when something goes wrong or the time exceeds the limit I have for the export, I need to stop the export, put it back to production and try another time. So I need to be sure that the export itself doesn't do any changes to the source system.
Thanks in advance
Tomas

Hi Tomas,
the export simply "copies" the source system (and converts the data to Unicode) - it does not change it.
Therefore you can still use it after the export is finished.
Best regards,
Nils Buerckel
SAP AG

Livecache changes during SCM Unicode conversion

Similar Messages

Maybe you are looking for