Ansicht
Dokumentation
09521 - EBCDIC/ASCII Codepage Conversion of R/3 4.6B
CPI1466 during Backup TXBHW - Original Tax Base Amount in Local CurrencyThis documentation is copyright by SAP AG.
EBCDIC/ASCII Codepage Conversion of R/3 4.6B
Hi Stan,we just finished the note 599700. I think, it will be viewable in the SAP
Service Marketplace by tomorrow.
So, I send you the complete note in the following already now:
Symptom
You want to do a codepage conversion from EBCDIC to ASCII on R/3 release
4.6B or BW 2.0B, in order to start the upgrade to R/3 Enterprise or BW
3.x subsequently, without having to perform the upgrade to the 4.6D
"conversion release" first. .
.
Additional key words
AS/400, iSeries, R/3, BW, 2.0B, 4.6B, CPCiSeries
Cause and prerequisites
You are running an R/3 SAP system with release 4.6B or a BW system with
release 2.0B on iSeries in EBCDIC. As R/3 Enterprise and BW 3.x are only
available in ASCII, you need to perform a codepage conversion before
doing the upgrade to these releases. The normal approach, would be to
upgrade to R/3 4.6C EBCDIC or BW 2.1C EBCDIC first, do the codepage
conversion and then finally perform the upgrade to R/3 Enterprise or BW
3.x.
In order to reduce the effort at the customer-site, we can offer the
direct codepage conversion to ASCII on these releases with a subsequent
upgrade to the higher releases.
This is only possible, because both SAP systems use the downward
compatible kernel 4.6D. Unfortunately, this approach will not be
possible for lower SAP releases, e.g. 3.1I, 4.0B or 4.5B, because no
ASCII Kernel is available on these releases.
Solution
BW 2.0B:
o Support Package 25 (or higher) must be installed for BW 2.0B
o OS/400 V5R1 or higher must be installed on the AS/400
o BW 2.0B (ASCII) may only be allowed for productive use during the
upgrade project to BW 3.x
o SAP will definitely not be supplying a BW 2.0B (ASCII)
installation
o SAP will not supply an upgrade from BW 2.0B (ASCII) to 2.1C
(ASCII/EBCDIC)
Seite 2
R/3 4.6B:
o The special transport from this note must be implemented into the
R/3 4.6B system first (not currently available, it will be
available soon. If you are interested, please open a SAPNet R/3
Frontend message under component BC-INS-AS4 and we will contact
you)
o OS/400 V5R1 or higher must be installed on the AS/400
o R/3 4.6B (ASCII) may only be allowed for productive use during
the upgrade project to R/3 Enterprise
o SAP will definitely not be supplying a R/3 4.6B (ASCII)
installation
o SAP will not supply an upgrade from R/3 4.6B (ASCII) to 4.6C
(ASCII/EBCDIC)
o The support of this conversion/upgrade project will cost 4 hours
remote consulting
As BW 2.0B is based on 4.6C basis components, no general problems are to
be expected. It is possible, therefore, to release this scenario without
special support from the AS/400 Porting Team. This is not the case with
R/3 4.6B. As the first AS/400 SAP system released for ASCII is 4.6C, we
can't guarantee that all ABAPs will run correctly under all
circumstances together with ASCII. In this case it is really necessary,
therefore, that the customer perform extensive tests of all the critical
core-business procedures on the converted test-system. Problems which
occur on the converted productive system, will only be corrected for
real system-down situations. Anything else will wait for the upgrade to
R/3 Enterprise. It is highly recommended, therefore, that the upgrade be
scheduled very soon - i.e.about one week - after the ASCII conversion.
This may seem a bit risky, but we didn't detect any problems when we did
this conversion and upgrade and running internal test tools in-house at
SAP. Nevertheless, since we don't have much customer experience at the
moment, the test is very necessary here.
Please open a message in the SAPNet R/3 Frontend under component
BC-INS-AS4, if you want to use one of the approaches described here.
Request immediate forwarding of your ticket to development support, so
that we can contact you on this issue and discuss the details.
Regards
Volker
-----Original Message-----
From: MCPARTLAND, Stan [mailto:stanley.mcpartlandZbently.com]
Sent: Mittwoch, 26. Februar 2003 17:08
To: Gueldenpfennig, Volker
Subject: RE: EBCDIC/ASCII Codepage Conversion of R/3 4.6B
Hi Volker,
Right now I am more interested in understanding the restrictions that will
be described in Note 599700. We're planning our upgrade strategy and
depending on the restrictions, this announcement could have significant
impact on our plans. We have been headed towards a 4.6C upgrade and are not
too concerned with the effort because of the similarities between 4.6B and
4.6C. We think of it more like a support package installation and test, but
now it may not be necessary depending on the timing of our hardware upgrade
for the database conversion. We may still go the 4.6C route, but I want to
fully understand all of our options.
Regards,
Stan
-----Original Message-----
From: Gueldenpfennig, Volker [mailto:volker.gueldenpfennigZsap.com]
Sent: Wednesday, 26 February, 2003 7:53 AM
To: 'DoNotReply@consolut.eu'
Cc: 'stanley.mcpartlandZbently.com'
Subject: RE: EBCDIC/ASCII Codepage Conversion of R/3 4.6B
Hi Stan,
if you are interested, you should open a ticket on BC-INS-AS4 and let me
know. Please open this when you want to start the project. I don't know when
I will finish the note.
This will be handled from Support with remote consulting anyway.
Regards
Volker
Durban Tours - Südafrika Safari
BAL Application Log Documentation BAL Application Log Documentation
This documentation is copyright by SAP AG.
Length: 6618 Date: 20240419 Time: 071847 sap01-206 ( 3 ms )
