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

Similar Messages

4.7EEx1.10 to ECC6.0 upgrade and Unicode conversion

Hi Experts,
We are going to initiate the upgrade from next month onwards. Subsequently i have started preparing the plan and strategy for the same.
As our current setup is 4.7EEx110/Win 2003 R2-64 bit/Oracle 10.2.0.4.0 (Non unicode). And we have recently migrated on to this setup from WIn2k 32 bit. Also the current hardware is Unicode compatible.
With respect to strategy for achieving this Upgrade and Unicode conversion, i am planning as follows.
Step 1) Perform Unicode conversion on the current landscape (Both Export/import on the same servers)
Step 2) Setup Temporary landscape as part of Dual maintenance strategy and migrate data from the current systems to temporary systems using backup/restore method.
Step 3) Perform the SAP version upgrade on the current landscape and setup transport routes from temporary to current landscape in order to keep it in sync
Step 4) after successful upgrade, decommission the temporary landscape
Please provide your suggestions and valuable advices if there is anything wrong with my strategy and execution plan.
Regards,
Dheeraj

Hi,
Thanks. As i have already referred these notes as i am seeking advise with respect to my upgrade approach.
However i have planned to perform in the following manner.
1) Refresh Sandbox with Prod data and perform Upgrade to ECC6.0 EHP5 & subsequently Unicode conversion on the same server (Since both export & Import has to perform on the same hardware as we have recently migrated on this hardware which is Unicode compatible)
2) Setup temporary landscape for DEv & QAs and establish transport connection to Production system in order to move urgent changes
3) Keep a track of the changes which have transported during upgrade phase so that the same can be implemented in the upgraded systems i.e. Dev & QAS
4) After Sandbox Migration and signoff, we will perform Dev & QAS upgrade & unicode conversion on the same hardware (Note: Since these are running on VMware can we export the data from the upgraded system and import on to a new VM?)
5) Plan for production cutover and Upgrade the Prod system to ECC6.0 Ehp5 and then Unicode conversion. As i am planning to perform upgrade over the weekend and then Unicode conversion activity in the next weekend (Is it a right way?)
My Production setup: DB on one Physical host and CI on separate Virtual host
6) After the stabilization phase, we are planning for OS & DB upgrade as follows:
a) Windows upgrade from 2003 R2 to Windows 2008 R2
b) Oracle Upgrade from 10.2 to 11.2
If anyone thinks that there is anything wrong with my above approach and need changes then please revert.
I have one more doubt as I am going to upgrade 4.7EEx110 (WAS 620, Basis SP64) to ECC6.0 EHp5.As I presume that I can straight away upgrade from the current version to ECC6.0 Ehp5 without installing EHP. Kindly confirm
Thanks

BAPI Receives unreadable parameters after unicode conversion

Dear All,
I have a strange issue, which i am stuck with and need your help to solve this.
I have a BSP Application which resides in my BW Production system and it calls a custom BAPI in R/3 to fetch list of materials based on material-text search as one of the parameters. This used to work properly before our R/3 got upgraded to ECC 6.0 with unicode conversion.
Both BW and R/3 are unicode systems now. But, doing external debugging i found that the parameters that i am sending through BSP to this BAPI are ok on BW side but, when it reaches R/3 it is getting converted to some unreadable characters due to which the BAPI doesnot return correct results.
Please advice where does conversion is happening and how can this be solved. I need immediate help as I am helpless and its a production issue...
Thanks,
Chandan

Hi Chandan,
please make sure that in transaction SM59 on both sides (BW and ERP) the rfc connections are defined as Unicode.
Best regards,
Nils Buerckel
SAP AG

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

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

BI7 Upgrade - Data Classes and Unicode Conversion

It is mentioned that we need to Convert Data Classes of InfoCube, but I still dont quite understand. Do you know what exactly is this Data Classes mean?
NW2004s upgrade
Also, why do we need to perform Unicode Conversion during the 3.x to BI7 upgrade?
Please advice.

It is mentioned that we need to Convert Data Classes of InfoCube, but I still dont quite understand. Do you know what exactly is this Data Classes mean?
NW2004s upgrade
Also, why do we need to perform Unicode Conversion during the 3.x to BI7 upgrade?
Please advice.

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

SAP R/3 4.6 C to ECC 6.0 Upgrade using CU &UC method- Unicode conversion

Basis Gurus
   I am working on upgrade from R/3 4.6C to ECC 6.0.
ECC 6.0 upgrade completed( still in non Unicode). Now I am in the process of Unicode conversion.
I have used following methods for the upgrade.
1. Combined Upgrade & Unicode conversion(CU & UC)
2. Resource minimized( as I am doing it in Sandbox).
As I understand I need to perform the DB export and Import now for the unicode conversion.
According to the Upgrade document, First I need to run Export using R3load in ECC6.0(Non unicode)
and then install Unicode system and import the same data file.
My understanding was, when I choose, Resource minimized, I need to run Export and import
in the same system.
Can you please help me , whether I need another Unicode system for import ??
Graham

Hi,
Dont get confused with upg strategy and unicode conversion.
In general Upgrade strategy (either downtime-minimized/resource minimized)
In unicode conversion you have export/import(exp/imp) of data concept
In CU&UC approach you have to do in a streach to complete migrate from old release to new realease ECC 6.00.
Using database independent (sapinst only) or Using database dependent (migration monitor or Distribution monitor)
It can be done in 2 ways.
If you dont have addtional server for unicode conversion
       1)you can either do exp on same hardware and take bakup and do import using the exp dump.
       2)Do exp on one server and prepare your target empty database on another server and complete imp of data.
Hope this is clear.
Regards,
Vamshi.

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

Unicode conversion in situ

Hi SCN,
I'm looking at the possibility of running a Combined Upgrade & Unicode Conversion (CUUC) in-situ; i.e. without a migration to new hardware.
However in all my years of SAP Basis projects any Unicode conversion I've seen has involved a migration to new hardware (which makes good sense as the process is the same as an OSDB migration with R3load/MigMon).
What I want to know is - has anyone ever run one in-place. I.e. keeping the same server and running the CUUC entirely inplace?
This seems logically problematic as you need a target system to import to.
I can imagine a process along these lines though...:
1. Take SAP layer offline
2. Run full backup of system
3. Export system
4. Drop database* (to make clean ready for new import)
5. Run SPUMG/SUMG/SAPINST to setup Unicode database ready to receive import...
6. ....and continue to run import into that database
7. Complete Unicode conversion process
However the big issue here for me is
(a) *dropping the live production system is far from attractive.... I'm presuming everyone would do as I've always seen and combine this with a migration to new improved hardware, so that a backout to the old system is simple
(b) I'm not sure at what point with the SAP tools (SPUMG/SUMG/SAPINST) this process would become convoluted with it all being in-situ on the same box. I.e. I'm not sure if it's something the SAP tools are really designed to cater for.
Any input/discussion on these points would be very welcome.
Regards, doonan_79

FYI Community. Feeling after reading and research is to use a temorary server to import unicode converted system data into; then swing disks back to the original host. Making all required hostname updates during the process.
Allowing for parallel export/import, but going back to the original configured host to complete the process.

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.

Some character display incorrect after unicode conversion

Dear Experts,
Currently we upgrade our SAP system from 4.6B NU to ECC6.0 UN.
in 4.6B system we had implemented Simple Chinese and French language package to the system. after upgrade to ECC6.0 no-unicode system. we perform a MDMP unicode conversion.currently system running with ECC6.0 unicode interface with language 1EFD. SUMG releated tasks had been finished. Chinese and French language checked OK in ECC6 UN system.
Our issue is. in the past time. some Spanish local end user typing some spanish character in some master date field when they login in 4.6B GUI choice english as login language.these kind of spanish characters could not display correct in current unicode environment.
could you please given us some suggestion for how to fix this issue.
I also sent this message in the Netweaver administrator forums with below links.
Spanish display incorrect after unicode conversion

Hello,
I doubt that the data shown by you in the link was caused by Spanish users logged on in EN.
I think this was rather caused by utf-8 data uploaded into the Non-Unicode system.
In this case, you need to repair the according texts manually, I do not know any automatic repair.
Best regards,
Nils Buerckel
SAP AG

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

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

Expertise Advices on ASSM + Unicode Conversion

Similar Messages

Maybe you are looking for