Symptom
1. For which source and target releases is the Twin Upgrade & Unicode Conversion (TU&UC) supported?
2. Is the TU&UC supported for all code page configuration types?
The TU&UC is generally supported for:
The TU&UC is supported only as pilot project for:
The TU&UC is not applicable for Single Code Page systems.
3. How do I become a pilot customer?
Customers who want to become pilot customers (=SAP consulting involvement is mandatory) are requested to send an email to globalization@sap.com and to state explicitly that they would like to pilot the Twin Upgrade & Unicode Conversion. This email should also contain the source release, and the installation and customer number. They will be registered as pilot customers in SAP Note 959697.Documentation
Please note that there are several documents required for the entire procedure. The basic documentation is the "Twin Upgrade & Unicode Conversion Guide" which can be downloaded from the attachments of this SAP Note. You will find a list of all further documentation in this guide.
Additional Information
A) You are running an MDMP system (mixture of several code pages, see note 73606) and want to perform a combined Upgrade & Unicode Conversion with one of the following start releases:
SAP_BASIS < 46C
SAP_BASIS = 610
As the preparation tools for the Unicode conversion (for example transaction SPUMG) are not available in your source release you would be forced to run the preparations after the upgrade and before the database export of the source system. This procedure would take too long to be finished within a reasonable downtime window.
The Combined Upgrade and Unicode Conversion (CU&UC, SAP Note 928729) is not supported for your source release.
B) You are running a MDMP system (mixture of several code pages, see SAP Note 73606) on an arbitrary release and want to perform a Unicode conversion either integrated within an upgrade or separately. Running the SPUMG preparation steps in your production system produces some load on the system (several batch jobs) you would like to avoid.
For both cases the procedure "Twin Upgrade & Unicode Conversion" (TU&UC) is utilizable. As opposed to the standard Unicode conversion approach, the SPUMG preparations are not performed in the production system but in a copy of the production system. The results are reused afterwards during the production conversion.
You have questions about this approach.
Reason and PrerequisitesSAP_BASIS < 46C
SAP_BASIS = 610
As the preparation tools for the Unicode conversion (for example transaction SPUMG) are not available in your source release you would be forced to run the preparations after the upgrade and before the database export of the source system. This procedure would take too long to be finished within a reasonable downtime window.
The Combined Upgrade and Unicode Conversion (CU&UC, SAP Note 928729) is not supported for your source release.
B) You are running a MDMP system (mixture of several code pages, see SAP Note 73606) on an arbitrary release and want to perform a Unicode conversion either integrated within an upgrade or separately. Running the SPUMG preparation steps in your production system produces some load on the system (several batch jobs) you would like to avoid.
For both cases the procedure "Twin Upgrade & Unicode Conversion" (TU&UC) is utilizable. As opposed to the standard Unicode conversion approach, the SPUMG preparations are not performed in the production system but in a copy of the production system. The results are reused afterwards during the production conversion.
You have questions about this approach.
FAQs:
1. For which source and target releases is the Twin Upgrade & Unicode Conversion (TU&UC) supported?
2. Is the TU&UC supported for all code page configuration types?
3. What does 'pilot project status' mean to the customer?
Solution1. For which source and target releases is the Twin Upgrade & Unicode Conversion (TU&UC) supported?
2. Is the TU&UC supported for all code page configuration types?
3. What does 'pilot project status' mean to the customer?
1. For which source and target releases is the Twin Upgrade & Unicode Conversion (TU&UC) supported?
- Target Release:
The TU& UC is only supported for target releases which are Unicode enabled (see SAP Note 79991) and are running on at least SAP_BASIS 620.
The minimum support packages for the different Basis releases are:
SAP_BASIS 620: SP60
SAP_BASIS 640: SP18
SAP_BASIS 700: SP9
SAP_BASIS 710: tools are in the first shipment
The minimum support packages for the different Basis releases are:
SAP_BASIS 620: SP60
SAP_BASIS 640: SP18
SAP_BASIS 700: SP9
SAP_BASIS 710: tools are in the first shipment
- Source Release:
The TU&UC is supported for all source release.
2. Is the TU&UC supported for all code page configuration types?
The TU&UC is generally supported for:
- Pure MDMP configurations (no ambiguous blended code page is involved; see SAP Note 73606 for a list)
The TU&UC is supported only as pilot project for:
- SAP Ambiguous Blended Code Page configurations
- MDMP systems which include an ambiguous blended code page in the code page list
The TU&UC is not applicable for Single Code Page systems.
3. How do I become a pilot customer?
Customers who want to become pilot customers (=SAP consulting involvement is mandatory) are requested to send an email to globalization@sap.com and to state explicitly that they would like to pilot the Twin Upgrade & Unicode Conversion. This email should also contain the source release, and the installation and customer number. They will be registered as pilot customers in SAP Note 959697.
Please note that there are several documents required for the entire procedure. The basic documentation is the "Twin Upgrade & Unicode Conversion Guide" which can be downloaded from the attachments of this SAP Note. You will find a list of all further documentation in this guide.
Additional Information
General information about code page solutions in SAP systems are available in SAP Note 73606.
No comments:
Post a Comment