Unicode conversion for ERP

Morning!
In that famous OSS note about unicode conversion, the attached guides are labeled
as NW unicode conversion guides.
-- ERP can use the same guides?
-- how about the unicode conversion for other products such as SM, SCM, CRM, etc.?
Thank you!

Hi,
Answer to both the questions would be Yes. The conversion guides are as per the Netweaver base release for any of the applications (ERP, SCM, SRM, CRM etc).
Eg, If converting a CRM 2005 Non-Unicode to Unicode, the guide SCP700SP<xx> would be relevant, because the Netweaver 700 SP<xx> is the base release for CRM 2005. Similarly for all applications.
Regards,
Srikishan

Similar Messages

Combined upgrade and Unicode conversion for ECC5 MDMP system

Hello,
We are planning to do Upgrade and Unicode conversion of ECC5 MDMP system to ECC6 EHP4 Unicode. We are adopting Combined upgrade and Unicode conversion strategy to minimise the downtime.
In source version ECC5 we are in support pack level 6. Should we need to update the support pack to any target version to start with CU&UC or we can start with ECC5 with SP 6 itself.
Since we cant afford more downtime for support pack update also, is it ok to start with upgrade and unicode conversion with current version.
please advice.
Regards
Vinay

Hello Vinay,
please note that as a prerequisite the Basis SP should be accurate for an MDMP conversion.
There is no MUST to have the latest Basis SP, but without you could have severe issues in SPUMG.
On the application side, there are in most cases no hard requirements on the SP level.
Best regards,
Nils Buerckel
SAP AG

Unicode Conversion for SAP BI

Hi
We are upgrading out SAP BW 3.1 system to SAP NW 7.0. We are also planning to do a Unicode conversion of the upgraded system.
Please let me know the following:
1. What extra tests we need to do for Unicode Conversion
2. If you have done a Unicode conversion, please share the errors that you have got after the conversion, and the possible solutions.
Best Regards,
Rajib

hi,
Please refer
SAP Note Number: 928729 : Combined Upgrade & Unicode Conversion (CU&UC)
https://wiki.sdn.sap.com/wiki/display/unicode/ChallengesinBIUnicodeconversion
Below is the link for R/3... but still will give you some insight.
/people/tikkana.akurati/blog/2009/02/27/combined-upgrade-and-unicode-conversion-cuuc-cutover-project-plan-execution
This will also help you understand more about unicode...
/docs/DOC-8284#section5 [original link is broken]
Hope this helps
Regards
Raj

Unicode Conversion for Solution Manager

I would like to convert non-unicode for unicode my SM4.0. The SM4.0 was
upgraded with SR2 (3.2 -> 4.0 SR2).
What guides "Unicode Conversion" and "System Copy" I use?

I would upgrade to the latest stack and start conversion then. The latest SAP_BASIS has the most fixes for the programs needed to run.
Check
http://service.sap.com/unicode@sap
--> Unicode Conversion Guides
--> Single Code Page Conv. Guides
If you upgrade to SP 17 use
Single Code Page Conversion Guide NW 7.0 SP 14 et sqq.
Markus

Error in RFC call, after unicode conversion of ERP

Hi,
We have just converted our ERP system to unicode. And we are using xMII 11.5. When i am calling a RFC thro' the BLS, it throws me this error
[ERROR]: RFC Execution Error: An invalid XML character (Unicode: 0x0) was found in the element content of the document.
The same error for all the RFC's i call.
But when i execute the BAPI as such in se37, in ERP , its fine.
What could be the reason for this?

Hima ... try this
http://<server>/Lighthammer/JCOProxy?Mode=Reset

Support package requierement for unicode conversion

We are currently planning a unicode conversion for a SAP 4.7enterprise 1.1 extension version, running under Aix and Oracle, Basis/ABAP SP 35, HR SP20.
According to the conversion guide, we must implement at least Support Pachage 60 for Abap and Basis, no explicit requierement for HR SP level.
I believed that we must applied SAP procedure and exclusively HR Support Package Stack up to 27, which include SP 60 for Basis and Abap and HR 61.
Our HR guys argue there is no indication from SAP that the SUPPORT PACKAGE STACK policy is mandatory and that SAP will provide us with normal support if we run the unicode conversion with SP Basis/ABAP 60, in other word even if we do not respect the support package stack combinaison. Need help on this issue before starting the project

Exterprise 4.7 is Unicode-Compliant,meaning that you can have unicode in 4.7.
If that the case, you should convert to 4.7 Enterprise Ext 2.00 Unicode First.
later only upgrade to ECC 6.0 after 2 years, as you said.
My answer is yes, to your question.
You can download the installation kits at:
http://service.sap.com/swdc
anyway, it is recommended to have the latest SP in your system.
cheers,
Vincent

Unicode Conversion on E-Recruitment

Dear All,
We are in the preparation of doing Unicode conversion for E-Recruitment application on DB02. I was wondering if any of you done Unicode conversion for E-Recruitment system. I have seen lot of threads in the area realated to ERP or BI but not in E-Recruitment application. if you have done unicode conversion on E-Recruitment, can you share your experience?
thanks a lot.
Sunil

HI,
Thnks for the update.
It got solved.
Cheers,
Vamshi T

Error during Unicode Conversion at DDNTF table

Hello
We are doing a Unicode Conversion for our CRT systems. This system now
is a SAP CRM 7.0 SR1 ABAP.
We have performed preparatory steps (SPUMG, checks, updating R3load,
R3ldctl, R3szchk, dboralib, ...),
but when we start Import process we get an error in SAPSDIC package.
The error looks like:
*************************+
(RTF) ########## WARNING ###########
Without ORDER BY PRIMARY KEY the exported data may be unusable
for some databases
(EXP) INFO: table DDNTF will be exported with sorting
(RSCP) ERROR: 'DDNTF' in UMGCCTL: Guess has illegal value.
(RSCP) WARN: DDNTF: Missing in UMGSTAT,
ERROR in nametab conversion
conversion of nametab table 'DDNTF ':
rscpMCStartTab: rc = 128
(CNV) ERROR: data conversion failed. rc = 2
(DB) INFO: disconnected from DB
/usr/sap/CRT/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/CRT/SYS/exe/run/R3load: END OF LOG: 20091229193651
Any idea??
Thanks in advance
Regards

Yes I executed this Report using Menu Tool Bar.
The first execution gave me some errors regarding some tables existing at database level but not in DDIC. We ignored this errrors because those tables are not important.
But the last try, we decided solve this inconsistencies deleteting those tables at database level, repeting report RADUCNT (in this case no errors appeared) and repeting the export with the same error..
Now, we have seen in Tabscript STATUS of SPUMG there are some errors regarding DDNTF inconsistency found at table control. Reason 4. But this reason means that faillback codepage missing at table control for this table. But as far I know, I can't fill failbak field for this kind of table...
So know I'm reseting SPUMG, and reestarting again..
But I don't understand what is the problem
In a few minutes I will you inform about results
Meanwhile is anybody have any suggestion or idea... please let me know
Thanks!

Unicode conversion BI 7.0 SP15

Hello,
We are planning Unicode conversion for all our systems.
Due to large database size of BI, we want to reduce conversion time as much as possible.
Our PSA tables occupy around 1 terabyte of disk space.
I want to know what action possible to take to avoid conversion of PSA tables.
1. Delete PSA, covert to Unicode and then allocate again.
2. Reduce size to the minimum ( 1 week)
3. Any your suggestions
Thank you,
Mark

Hi Mark,
if the conversion takes too long (for example more than a weekend), then you could consider building a new BI Unicode system offline. You can load it either from the original sources or from the current BI system. Then on the go-live weekend, you switch over and load the remaining data.
However, you will need two big BI systems for a while.
Regards,
Marc
SAP NetWeaver RIG

Unicode Conversion necessary before 2004s upgrade??

Hello,
Can anyone tell me if it is necessary to do an Unicode Conversion first before upgrading a BW system to BW 2004s?
The Portal we are going to use is unicode enabled.
So this raises the question: "Do we need an Unicode Conversion first?".
Regards,
Jos

Hello,
It's not necessary to do a unicode conversion for NW 2004s BI. We still support non-unicode systems for NW 2004s BI. This link explains the pro's and con's of staying on non-unicode for SAP NetWeaver BI.
http://service.sap.com/~sapidb/011000358700006750052002E
Regards,
Bryan

Unicode conversion on 32 bit OS

Dear All,
I am planning to do unicode conversion for my non-unicode system.
Could you please let me know what are the steps to be taken to perform this activity?
Is the unicode conversion possible in 32 bit OS?
I would be obligued if anybody can give suggestions on this.
Thanks and Regards
Purna

Dear Purna,
depending on your system configuration (single code page or MDMP) you will need the attachments of the following SAP notes:
- Unicode Conversion without upgrade: See SAP Note 551344
- Single Code Page without Upgrade: See SAP Note 1051576
This is the technical step by step description how to do the conversion.
In addition I would recommend to have a look at the following SAP notes:
1322715 Unicode FAQs
1319517 Unicode Collection Note
The following link gives you an overview on the topic:
SAP Unicode Conversion Topics:
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000380759&_OBJECT=011000358700002020842008E
If you need more details, then please have a look at:
Unicode Workshop slides
http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000380759&_OBJECT=011000358700004426552004E
For the ABAP enabling, you will definitely need the following document:
Internationalization > Unicode > ABAP and Unicode Requirements > ABAP Programming in Unicode Systems: Requirements
You will find further info in:
http://service.sap.com/unicode
and
Internationalization > Unicode
Last but not least, there is also a Unicode book available:
http://www.sap-press.com/product.cfm?account=&product=H1984
Best regards,
Nils Buerckel
Solution Management
Globalization Services

Preparing for upgrade and Unicode conversion while on 4.6c

We're currently on 4.6c and preparing to upgrade to ERP 2005 and do a Unicode conversion. I'm trying to compile a list of coding techniques that can used in 4.6c that will minimize changes needed for Unicode. Does anyone have such a list?
Some things I've discovered reading about Unicode include:
1) Use GUI_UPLOAD and GUI_DOWNLOAD rather than WS_UPLOAD and WS_DOWNLOAD.
2) Structures or table headers that contain non-character data need to be identical when moving, comparing, selecting into, updating from, etc. This includes not moving structures/tables with non-character data to a character field or vice-versa.
3) Offsets can't cross non-character data.
4) Assign statement with offset must specify a length.
5) Open dataset must specify "FOR INPUT", "FOR OUTPUT", "FOR APPENDING", or "FOR UPDATE". It no longer defaults to FOR INPUT when omitted.
6) Many implicit conversions from char to numeric are no longer allowed. Use explicit conversion instead; such as the move statement.
I know there are others. Any help would be appreciated.
Regards,
Mark Perrey

Hai Mark
Check the following F.M Replacents
Upgrade Error Details     Suggestions
Function Module "DOCUMENT_REGISTRY_PROGRAM"not found in the target system     Suggest to replace this FM with the function module CV120_GET_APPL_FROM_REGISTRY.
Function Module "RP_HIRE+FIRE"not found in the target system     Suggest to replace this FM with the function module RP_HIRE_FIRE .
Function Module "ME_READ_HEADER_SINGLE" not found in the target system     Suggest to replace this FM with the function module ME_EKKO_SINGLE_READ.
Function Module "ME_READ_ITEM_SINGLE" not found in the target system     Suggest to replace this FM with the function module ME_EKPO_SINGLE_READ.
Function Module "RZL_ALERT_CONTROL" not found in the target system     Function Module "RZL_ALERT_CONTROL" is not available in the Enterprise Version. Suggest to use the function module "TH_SEND_ADM_MESS" to acheive the same functionality of "RZL_ALERT_CONTROL".
Function Module "MM_SELECT_ADDRESS" not found in the target system     Suggest to replace this FM with the function module MM_SELECT_PARTNER.
Function Module "MM_READ_ADDRESS" not found in the target system     Suggest to replace this FM with the function module MM_PARTNERS_FOR_MESSAGING
Function Module "ME_VALUES_T161" not found in the target system     Suggest to replace this FM with the function module HELP_VALUES_BSART.
Function Module "ME_VALUES_T024W" not found in the target system     . Suggest to replace this FM with the function module HELP_VALUES_WERKS.
Function Module "SD_PACKING_REFRESH" not found in the target system     Suggest to replace this FM with the function module HU_PACKING_REFRESH.
Function Module "SD_PACKING_RENAME" not found in the target system      Suggest to replace this FM with the function module V51P_PACKING_RENAME.
Function Module "RV_EXPORT_CONTROL_UPDATE" not found in the target system     Suggest to replace this FM with the function module RV_EXPORT_CONTROL_UPD_PREPARE.
Function Module "RV_INVOICE_COPY" not found in the target system     Suggest to replace this FM with the function module RV_SALES_DOCUMENT_COPY.
Function Module "SD_SCHEDULE_AGREEMENT_PACKING" not found in the target system     Suggest to replace this FM with the function module HU_PACKING_SALES_PROPOSAL.
Function Module "SERIAL_RENUM_WV" not found in the target system     Suggest to replace this FM with the function module IWOL_WV_SWITCH_NUMBER.
Function Module "CUD0_DISPLAY_CONFIGURATION" not found in the target system     Suggest to replace this FM with the function module VC_I_DISPLAY_CONFIGURATION.
Function Module "SD_PACKING_CREATE" not found in the target system     Suggest to replace this FM with the function module V51F_PACKING_CREATE.
Function Module "FI_ARCHIVE_CHECK_DOC" not found in the target system     Function Module FI_ARCHIVE_CHECK_DOC is not available in the Enterprise Version. Suggest to replace this FM with the function module FI_DOCUMENT_ARCH_CHECK_DOCS.
Function Module "OPEN_FI_CHECK" not found in the target system     Function Module OPEN_FI_CHECK is not available in the Enterprise Version. Suggest to replace this FM with the function module OPEN_FI_PERFORM_******_E.
Function Module "SD_PACKING_UPDATE"not found in the target system     Function Module SD_PACKING_UPDATE is not available in the Enterprise Version. Suggest to replace this FM with the function module HU_PACKING_UPDATE.
Function Module "F4_MACO" is being used in the program     Function Module "F4_MACO" is not available in the Enterprise Version. Since the Matchcode objects are not used in the Enterprise Version, Suggest to replace this FM with Search help's Value Request function module F4_SEARCH_HELP.
Function Module "SWZ_AI_RELEASE_S" is used in the program     Suggest to use the function module "SWZ_AI_RELEASE" instead of "SWZ_AI_RELEASE_S".
Function Module "SWW_WI_ORGTASK_READ" is used in the program      Suggest to replace this FM with the function module RH_WI_ORGTASK_READ.
Function Module "RH_READ_EXCEL_PATH" is being used in the program     Suggest to replace this FM with "RH_CHECK_EXCEL_SUPPORT".
Function Module "RZL_ALERT_CONTROL" is used in the program     Function Module "RZL_ALERT_CONTROL" is not available in the Enterprise Version. Suggest to use the function module "TH_SEND_ADM_MESS" to acheive the same functionality of "RZL_ALERT_CONTROL".
Function Module "CONVERT_TO_OTHER_CURRENCY" is used in the program     Suggest to ruse the function module "CONVERT_TO_LOCAL_CURRENCY" for currency conversion.
Function Module "LOAN_TABLECONTROL_SCROLLING" is not available in the Enterprise Version.      Suggest to replace this FM with the function module SCROLLING_IN_TABLE.
CALL FUNCTION 'DOWNLOAD' used in program is obsolete in target system.     "DOWNLOAD function module is obsolete and result in errors on Unicode systems or on systems that may potentially be Unicode enabled.
Suggest to use the unicode enabled methods
FILE_SAVE_DIALOG and GUI_DOWNLOAD
from class CL_GUI_FRONTEND_SERVICES.
Note:
However, to support existing applications, a compatibility mode was added to the function module(enhanced with Support Package) that will forward calls to DOWNLOAD to the new GUI_DOWNLOAD functions."
CALL FUNCTION 'HELP_VALUES_GET_NO_DD_NAME' used in program is obsolete in target system.     "HELP_VALUES_GET_NO_DD_NAME function module is obsolete and result in errors on Unicode systems or on systems that may potentially be Unicode enabled.
Suggest to use the function module F4IF_INT_TABLE_VALUE_REQUEST in the target system."
CALL FUNCTION 'POPUP_TO_CONFIRM_LOSS_OF_DATA' used in program is obsolete in target system.     "POPUP_TO_CONFIRM_LOSS_OF_DATA is obsolete in the target system.
Suggest to use function module POPUP_TO_CONFIRM."
CALL FUNCTION 'POPUP_TO_CONFIRM_STEP' used in program is obsolete in target system.     "POPUP_TO_CONFIRM_STEP is obsolete in the target system.
Suggest to use function module POPUP_TO_CONFIRM."
CALL FUNCTION 'WS_DOWNLOAD' used in program is obsolete in target system.     "WS_DOWNLOAD function module is obsolete and result in errors on Unicode systems or on systems that may potentially be Unicode enabled.
Suggest to use the unicode enabled GUI_DOWNLOAD function module.
Note:
However, to support existing applications, a compatibility mode was added to the function module(enhanced with Support Package) that will forward calls to WS_DOWNLOAD to the new GUI_DOWNLOAD function."
CALL FUNCTION 'WS_FILENAME_GET' used in program is obsolete in target system.     "WS_FILENAME_GET function module is obsolete, and results in errors on Unicode systems.
Suggest to use FILE_OPEN_DIALOG und FILE_SAVE_DIALOG Unicode-enabled methods of the cl_gui_frontend_services class.
Note:
New applications should restart on these methods instead of the function module. The function module is extended by a Support Package so that it diverts calls to the methods without the application having to be changed."
CALL FUNCTION 'WS_UPLOAD' used in program is obsolete in target system.     "WS_UPLOAD function module is obsolete and result in errors on Unicode systems or on systems that may potentially be Unicode enabled.
Suggest to use the unicode enabled GUI_UPLOAD function module.
Note:
However, to support existing applications, a compatibility mode was added to the function module(enhanced with Support Package) that will forward calls to WS_UPLOAD to the new GUI_UPLOAD function."
Function parameters EBENE, GRUPP, DATE_LOW, DATE_HIGH, BANKK. BUKRS, S_BUKRS, S_DISPW in function module CASH_FORECAST_TR_SELECT_ITEM is missing in the target system.     "Function Module CASH_FORECAST_TR_SELECT_ITEM is no longer used, instead it has been split based on the functionalities.
Suggest to use function module
1) CASH_FORECAST_PR_SELECT_ITEM for Payment Arrangements.
2) For TR, WP, DA use function module CASH_FORECAST_TR_ITEM_2.
The IMPORT and TABLES parameters of the above 2 function modules are almost same as CASH_FORECAST_TR_SELECT_ITEM.
The IMPORT parameter BUKRS is not available in the above 2 function modules. Hence suggest to change the coding accordingly."
Import parameter BUKRS in function CASH_FORECAST_LO_SELECT_ITEM is missing in the target system.     "Import parameter BUKRS in function CASH_FORECAST_LO_SELECT_ITEM is not available in the target system.
Also the coding in Function Module based on the parameter BUKRS has been removed, instead the TABLES parameter S_BUKRS and S_GSBER has been used.
Suggest to check the coding in the program accordingly.
Import parameter BUKRS in function CASH_FORECAST_RE_SELECT_ITEM is missing in the target system.     "Import parameter BUKRS in function CASH_FORECAST_RE_SELECT_ITEM is not available in the target system.
Also the coding in Function Module based on the parameter BUKRS has been removed, instead the TABLES parameter S_BUKRS and S_GSBER(new parameter) has been used.
Suggest to check the coding in the program accordingly.
Function Module HELP_VALUES_GET_WITH_MACO is obsolete in target system     Suggest to use F4IF_FIELD_VALUE_REQUEST
Function Module G_OBJECT_GET is obsolete in target system.     Suggest to Use G_INTERVAL_GET_NEXT
Function Module READ_COSTCENTER is obsolete in target system     Suggest to Use K_COSTCENTER_SELECT_SINGLE
Function Module K_BUSINESS_PROCESS_READ_MULTI is obsolete or not available in target system     Suggest to Use K_PROCESSES_SELECT_TAB
G_SET_AVAILABLE     Suggest to Use G_SET_GET_INFO
Function Module G_SET_DOUBLE_CHECK is obsolete or not available in target system     "DO NOT CALL THIS FUNCTION MODULE
FROM 4.0A VERSION ,THIS PROBLEM WILL NOT OCCUR"
Function Module HELP_VALUES_GET is obsolete or not available in target system     Suggest to Use F4IF_FIELD_VALUE_REQUEST
G_SELECT_SET     Suggest to Use G_SET_SELECT
Function Module G_SET_AVAILABLE is obsolete or not available in target system     Suggest to Use G_SET_GET_INFO
Function Module NAMETAB_GET is obsolete or not available in target system     Suggest to Use DDIF_FIELDINFO_GET
Function Module DD_GET_DD03P is obsolete or not available in target system     Suggest to Use DDIF_FIELDINFO_GET / DDIF_TABL_GET
CALL FUNCTION 'POPUP_TO_CONFIRM_WITH_MESSAGE' used in program is obsolete in target system.     Suggest to use function module POPUP_TO_CONFIRM.
CALL FUNCTION 'POPUP_TO_DECIDE' used in program is obsolete in target system.     Suggest to use function module POPUP_TO_CONFIRM.
Function Module HELP_VALUES_GET_WITH_TABLE is obsolete or not available in target system     Suggest to Use F4TOOL_F4FUNCTION_BRIDGE
Function Module CLPB_EXPORT is obsolete or not available in target system     "Suggest to Use Suggest to use the unicode enabled methods
CLIPBOARD_EXPORT from class CL_GUI_FRONTEND_SERVICES."
Function Module SAP_TO_ISO_MEASURE_UNIT_CODE is obsolete or not available in target system     Suggest to Use UNIT_OF_MEASURE_SAP_TO_ISO
Regards
Sreeni

How to go for Unicode conversion?

Hi All,
Presently i'm upgrading my SAP 4.7 system (6.2 WAS) in to ERP 2004 (6.40 WAS), which is an non-unicode upgrade.
Now should i first complete Unicode conversion or apply the latest SP stack.
Also please tell me how this Support pack will affect me in Unicode conversion?
Order of this steps will be really helpful for smooth flow of work
Thanks in Advance

If you have already completed your upgrade, the best practice would be to install the SP stack first in order to have the latest updates available for the unicode migration tools. Then proceed with the unicode migration. There are slight differences in the process between support packages where you may have to create a migration program manually in an older support package and the very same migration program is included in the later support package. SAP publishes separate unicode migration guides, based on the support package level, due to these updates.

SAPDODS package splitting for Unicode conversion

I have experience doing a unicode conversion of an ERP system with numerours splits including SAPAPPL plackages, but this time I am looking for info on how to split/tune the SAPDODS package. I have started the test conversion of our SCM system today which is only 400GB and everything was completed within an hour or so, but the SAPDODS package took 7 hours to export and 3 hours to import. Can you tell me if there is any way to tune it?

Exterprise 4.7 is Unicode-Compliant,meaning that you can have unicode in 4.7.
If that the case, you should convert to 4.7 Enterprise Ext 2.00 Unicode First.
later only upgrade to ECC 6.0 after 2 years, as you said.
My answer is yes, to your question.
You can download the installation kits at:
http://service.sap.com/swdc
anyway, it is recommended to have the latest SP in your system.
cheers,
Vincent

How to estimate the time needed for unicode conversion

Experts:
I am going to perform an upgrade from 46C (non-unicode) to ECC6/EHP4.
In the action plan , it's hard to estimate the time needed for unicode conversion.
We do not have a sandbox to benchmark that time.
Could you please help share your experience here?
Thanks!!

Hi,
usually it is very hard to estimate a proper time.
There are some hints to get a rough feeling (SAP note 857081 and [SMP link|http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000380759&_OBJECT=011000358700001279022010E] ).
However please note that SAP highly recommends to do a Sandbox conversion - otherwise there is a high risk that the PRD conversion will take (much) longer than expected.
Best regards,
Nils Buerckel

Unicode conversion for ERP

Similar Messages

Maybe you are looking for