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

Similar Messages

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

LRAW data Conversion during Unicode Conversion

Hi,
We have upgraded our 46C MDMP system to Unicode system.
After conversion we found that some of the tables with field of LRAW type are having conversion issue.
In 46C system, Russian data which enetered in the MS Cyrillic (Code page 1504), is converted to code page 1500 after unicode conversion.
We have not found any entries for this table in vocabulary, reprocess log or in SUMG.
For example table STXL. This table contains Purchase order text for the material.
Report HRUU_CONVERT_IN_UNICODE does not shows LRAW data field for conversion.
Can you suggest how LRAW data can be converted from 1500 to 1504 code page.
Thanks and Regards
Rahul

Hi Rahul,
STXL is a language dependent INDX type table. Hence SPUMG will not scan this one with the default settings.
Please have a look at the description of INDX type table handling in the Unicode conversion Guide.
In the Unicode system, you can use UMG_ADJUST_STXL for the conversion.
However please be aware of the restrictions:
Once you have decided about the code page and converted the object, this cannot be reverted !
Therefore it is highly recommended to check the display mode first and in addition test it extensively on a sandbox system !
Best regards,
Nils Buerckel
SAP AG

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

Error with PS text after Unicode conversion

Hi, we are having problem after doing unicode conversion with special
character not displayed correctly in a Web interface. In SAP
(transaction CN04) everything is OK, but if the PS text is displayed
through a Web interface (BSP for instance) some characters are
displayed wrong. One of these characters is the apostrophe in French
language ('). Is there an available tool to perform a conversion of
existing PS text after performing unicode upgrade ?

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

MDMP unicode conversion - Vocabulary maintenace

Hello,
W have upgraded 4.5B MDMP system to ECC4 EHP4 and now we are in process of unicode conversion.
please advice on as specified below.
In SPUMG Scan process, we have completed the following scans:
a) Tables without language Info
b) Tables with Ambiguous language Info
c) Indx Analysis
For maintaining vocabulary we have implemented notes 756534 & 756535, 871541. and Tables with language are also scanned. While handling vocabulary the system has displays 539158 with duplicates and 189314 when duplicates are discarded, which doesnot assigened any languages. We have 9 acive languages.
As per Unicode conversion document i left out with only 2 more option a) HInt management b) Manual assignment
How to handle this? is this a normal situation or any correction can be done?
Thanks and Regards
Vinay

Hi Vinay,
This Thread belongs to the Unicode forum:
Internationalization and Unicode
In my opinion one of the best and most efficient possibility to reduce the number of words
is to make use of hints. Please follow the Unicode Conversion Guide and SAP note 1034188.
Application colleagues should be contacted in order to find proper hints.
Please also note that report umg_vocabulary_statistic or um4_vocabulary_statistic is the best tool to evaluate tables for hint processing.
And the rest of the vocab, which can not be assigned by the hints method or by the SAP notes you mentioned, need to be assigned by native speakers (manual effort !).
As you can see, SPUMG is NOT just a tool to be executed by Basis staff.
It needs in deed collaboration between Basis, Application and native speakers.
And it should be clear that the duration of the scans can be quite high - therefore a trial & error approach will take time (especially for large systems).
Best regards,
Nils Buerckel
SAP AG

SRM can not open attachment after unicode conversion

Hi,
Our system is SRM4.0, last week we do a unicode conversion project.
After we convert to unicode, some attachment in SC and PO can not be openned, these attachment file name include some chinese. If the attachment file name is all English, no problem to open it.
I think it is the cause by unicode conversion, do you have any idea what is the root of this problem?
Thanks.

Hi,
Please check in table :BBP_PDATT
If you have created a shopping cart with attachment. The attachment will be in the above table
Regards
G.Ganesh Kumar

Twin upgrade and Unicode conversion: UMG_TWIN_PROCESS_LOGS Could not adjust

Hello,
We have done Upgrade of 4.5B MDMP system to ECC6 EHP4 MDMP and currently Unicode conversion in progress.
We adopted TU&UC. Now we are importing twin spumg results of last run to our procution copy system.
During running UMG_TWIN_PROCESS_LOGs. we are facing some errors
INDX lines to be corrected:               4.417
INDX lines corrected      :               4.144
IN that Could not adjust:        SMODISRC, we are referring Note 991654 - UMG_TWIN_PROCESS_LOGS shows errors on SMODISRC.
please suggest for other error tables below
Could not adjust:        VARI 1160
Could not adjust:        MONI
Could not adjust:        BDLDATCOL 1160 DLR000000492TSK0020305440PV1     0000000000DIFF    BDL   000614a01822pr                        000000Field List          S1100
Please suggest what action can be taken
Regards
Vinay

Hi Vinay,
did you already check attachment of SAP note 765475 - "Unicode conversion Troubleshooting guide" ?
Excerpt:
...check if the entries in
<table name> still exist. In some cases those entries only exist in the
Twin System but no longer in the Production System. In such cases the
message is not an error message but only information.
Best regards,
Nils Buerckel
SAP AG

Unicode Conversion Preparations not finished

Hello,
we are upgrading our system to ERP 6.0 EHP 4 with unicode conversion.
During the "Preprocessing" phase I get the following error:
Error: The Unicode Conversion Preparations on the startrelease (transaction SPUMG)
have not been finished yet.
You cannot proceed with the upgrade unless the preparation has been finished.
I started the transaction SPUMG, but I don't know what to do there. What needs to be done to continue the upgrade process.
Thanks in advance
Andreas Kasper

SPUMG -
Unicode conversion preparation transaction. Provides several database scans for checking the consistency of the non-Unicode database and for preparing the database tables for the export and conversion. These scans must be executed manually.
SPUMG is used to prepare the database tables for the system conversion.
CHeck SAPnote # 928729, this has attached Unicode conversion guides.
Download as per your scenario and proceed ahead accordingly.
- Niraj

Expertise Advices on ASSM + Unicode Conversion

Hi,
I need some Expertise advice on Converting oracle Table Space to ASSM and Unicode.
Our company planning on upgrading ECC 5.0 to ECC 6.0 then we also want to do Unicode migration, but we need to know; what/when are the best practices to convert the oracle tablespace to ASSM?
I believe part of Unicode migrations we have to convert the Oracle tablespace to ASSM.
Option 1:
Is it better to convert all the tablespaces to ASSM before we do a Unicode migration? And then do the Unicode migrations?
Option 2:
Or is it better to do everything together at the same time Unicode Migrations and Tablespace conversation?
Is there are any benefits between those two options? Which one is really time saving? Option 1 or Option 2
Quick question on the side, how long would it take to convert 450 GB total data to ASSM?
Please advice on this!
Thanks in Advances
Kumar

I would suggest the following: Forget about ASSM - it will be enabled by default after your conversion, that's all I can say about ASSM in this context.
The Unicode migration itself is a really complex process, we had quite some issue to fight with. To see the whole story we were going through read that thread:
combined upgrade and unicode conversion
The topic is a bit different but I explain in-depth there, what problems we encountered, maybe this will helpful for you too.
You're right, the guides are pretty complex and the procedure and preparation is too so I would NOT do that as newbie (no offense). We had a consultant from SAP on-site while we were doing the preparation for the migration because of those many languages we had. The migration itself was then done by me after those four tests migrations I mentioned earlier.
If your system is a single codepage migration, it's not that difficult if you follow the guides provided (http://service.sap.com/unicode@sap) for your specific support package level. Just follow it step-by-step, read all the note (yes, I know, there are SO MANY).
My "best practice recommendations" are:
- use the VERY LATEST tools (kernel, R3load and dboraslib) for the export (VERY important!)
- if possible, install the latest Basis support package (SP 12 in your case) <b>before</b> you start the preparation (that is running the task of SPUMG)
- If you install the unicode instance, also use the latest tools there, latest kernel and latest R3load, you can patch the system while the database is created (there's enough time)
- if you have external systems connected, make sure, they are aware of the fact, that they are "talking" to Unicode systems after the migration (Fax-Servers, EDI and also all SAP systems such as BW, CRM, SCM or also SAP-KPRO-Servers or what else you have there)
- test, test, test, don't do the migration just theoretically
I can't provide a guide, they are highly individual depending on what modules are implemented, what external interfaces and connections to systems you have etc. etc. I could provide you with a "guide" but I'm VERY sure, there's something missing/too much and I won't be responsible for any errors/problems you will get. We did a full day of just evaluating the system, interfaces etc.
The only advise is - do a test migration, connect the system to everything you also have on production and test.
Markus

Unicode Conversion ERP6.0 EHP3

Hello
We have for Dev. purpose an ERP6.0 EHP3 SP2 Non-Unicode System, now we should make an Unicode conversion with this system. Does someone have an Idea for me which Conversion Guide I have to use for this ? NW70-14 ?? NW7016 ?? NW701 ?? there must be an NW703 or not ??
thanks,
Stefan

Hi Stefan,
the Unicode conversion guides depend on the Basis/NW support packages / EhPs of your system.
If you have e.g. NW 7.0 EhP 1, then you need the guide 701.
The application support packages / EhPs are not relevant for the UC conversion (since it can be used for ERP,CRM,SCM, ...).
Best regards,
Nils Buerckel
SAP AG
Edited by: Nils Buerckel on Aug 25, 2010 2:46 PM

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

Error while database export in package SAPDODS_33 (Unicode conversion)

Hello,
I am performing Unicode conversion on an upgraded BI 7.0 system. This is running on AIX/DB2.
When I take database export for conversion, one package fails (SAPDODS_33) with error "The file system is full". In fact, df -k doesn't show that any file system is full.
I am taking the export to the following location: /db2/BWS/sapdata/EXPORT_DIR
There are 3 system-managed temporary tablespaces: PSAPTEMP, PSATEMP16 & SYSTOOLSTMPSPACE which were residing in /db2/BWS/saptemp1/NODE0000. This was getting full during the export. Now these temp.tablespaces have been relocated to a new file system of size 15GB.
But still the package SAPDODS_33 doesn't get exported. Could you please let me know how to solve this issue?
Thanks a lot!
Sundar.
=====================================================================================
SAPDODS_33.log
(DB) INFO: connected to DB
(rscpsumg) Please look also into "SAPDODS_33012.xml".
(rscpMC) Warn: env I18N_NAMETAB_TIMESTAMPS = IGNORE
(rscpMC) Warn: UMGCONTAINER has 1 problems.
(rscpMC) Warn: Global fallback code page = 1160
(rscpMC) Warn: Common character set is not 7-bit-ASCII
(rscpMC) Warn: Collision resolution method is 'fine'
(rscpMC) Warn: R3trans code pages = Normal
(rscpMC) Warn: EXPORT TO ... code pages = Normal
(rscpMC) Warn: Source is 'MDMP'
(rscpMC) Warn: I18N_NAMETAB_NORM_ALLOW = 0
(rscpMC) Warn: I18N_NAMETAB_NORM_LOG   = 0
(rscpMC) Warn: I18N_NAMETAB_ALT_ALLOW = 0
(rscpMC) Warn: I18N_NAMETAB_ALT_LOG    = 0
(rscpMC) Warn: I18N_NAMETAB_OLD_ALLOW = 0
(rscpMC) Warn: I18N_NAMETAB_OLD_LOG    = 0
(GSI) INFO: dbname   = "BWS
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN
(GSI) INFO: sysname = "AIX"
(GSI) INFO: nodename = "itmlartdev01x"
(GSI) INFO: release = "3"
(GSI) INFO: version = "5"
(GSI) INFO: machine = "002417CA4C00"
(GSI) INFO: instno   = "0020169337"
(EXP) ERROR: DbSlExeRead failed
rc = 99, table "/BIC/B0000786000"
(SQL error -968)
error message returned by DbSl:
SQL0968C The file system is full. SQLSTATE=57011
(DB) INFO: disconnected from DB
/usr/sap/BWS/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/BWS/SYS/exe/run/R3load: END OF LOG: 20071211053119
p/sapinst/sapinst_instdir/NW04S/LM/COPY/DB6/EXP/CENTRAL/AS-ABAP/EXP #

Hi Sundar,
if the problem is due to a high temp space usage. The root cause is typically the
sort during export. If the table is large, the sort spills to temp.
You can avoid the sort by doing an unsorted export or tweak the DB2 optimizer to use the primary key to do the sort.
Before DB2 9, you can reduce the OVERHEAD tablespace parameter to zero. Return this value to its previous value after the successful export. This is a indirect hint to the optimizer that random IOs are cheap. This might not help.
With DB2 9, this should not happen, because the DB2_OPT_MAX_TEMP_SIZE=10240 registry variable is set under DB2_WORKLOAD=SAP which limits the temp space usage to 10GB if possible. You can reduce this parameter further if necessary. Another problem could be that the optimizer has chosen the wrong temp space. The optimizer choses the temp space with the largest amount of pages (not size).
Regards, Jens

Combined Upgrade and Unicode conversion of Sap 4.6C to ECC6.0

Hello all,
my project team intends to carry out a combined upgrade and unicode conversion of an SAP ERP 4.6C system with MDMP to ECC6.0 (no enhancement package). The system is running on Oracle 10.2.
In preparation for this upgrade, I have gone through the SAP notes 928729, 54801.
We need to get a rough estimate of the entire downtime so as to alert our end users. From the CU&UC documentation in 928729, I read up note 857081. However the program in this note cannot be used to estimate the downtime as my system is < SAP netweaver 6.20.
Is there any other SAP note or tool or program that I can use to estimate the downtime for the entire CU&UC? Thanks a lot!

Hi,
Combined upgrade depend upon number of factors like database size, resources on the server and optimization. In order to get idea of how much downtime, it will take, I would suggest you to do combined upgrade and unicode conversion on sandbox system which should be the replica of your production system. And try to optimize it. From there you can get approx. downtime required.
Also, please read combined upgrade and unicode conversion guides on http://service.sap.com/unicode@sap
Thanks
Sunny

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

SCM Unicode Conversion - Initialize LC or not??

Similar Messages

Maybe you are looking for