Ansicht
Dokumentation

09496 - EBCDIC/ASCII Codepage Conversion of R/3 4. 6B

09496 - EBCDIC/ASCII Codepage Conversion of R/3 4. 6B

BAL Application Log Documentation   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

EBCDIC/ASCII Codepage Conversion of R/3 4. 6B

Hi Craig,

I took over the ticket.
I try to create the note today.

Here the old information for BW 2.0B. The restrictions will be the same for
4.6B. You won't need any special support pack level. You just have to import 1
transport request and/or have to adjust a bit manually before the conversion:

Good news from the BW porting team in Walldorf for BW 2.0b customers.

SAP provides from now on a CPC on BW 2.0b level and a BW 2.0b (ASCII) version
to reduce the number of steps for a BW upgrade to 3.0b. The fact that BW 2.0b
and BW 2.1c are based on the same 4.6d kernel technology enabled us to develop
this new feature.

Before that a customer using BW 2.0b (EBCDIC) had to execute the following
three steps for his upgrade project to the recent BW version 3.0b:

1.) Upgrade from BW 2.0b (EBCDIC) to BW2.1c (EBCDIC)
2.) Do the CPC from EBCDIC to ASCII on a BW 2.1c level
3.) Upgrade from BW 2.1c (ASCII) to BW 3.0b (ASCII)

With the new features the upgrade project can be reduced to a two step approach:

1.) CPC on BW 2.0b level
2.) Upgrade directly from 2.0b (ASCII) to 3.0B (ASCII)

SAP will allow the CPC on the BW 2.0b level and the BW 2.0b (ASCII) only on
customer request. Please create an OSS ticket with this request if you need it.
The component of the OSS ticket should be BC-INS-AS4.

Remarks:
-- BW 2.0b (ASCII) is allowed for productive use only during the upgrade
project to BW 3.0b.
-- There will definitely be no installation available for BW 2.0b (ASCII).
-- There will be no upgrade available for BW 2.0b (ASCII) to 2.1c
(ASCII/EBCDIC).
-- The existence of a new BW 2.0b (ASCII) version doesn't imply that SAP can or
will develop a new ASCII version for any other old release of an SAP product.
Only the fact that BW 2.0b and 2.1c are based on the same 4.6d kernel
technology enabled us to develop this new version.

Regards

Volker

-----Original Message-----
From: sapbasisguy <craig_welchZbradycorp.com>
[mailto:craig_welchZbradycorp.com]
Sent: Freitag, 28. Februar 2003 14:00
To: DoNotReply@consolut.eu
Subject: Re: EBCDIC/ASCII Codepage Conversion of R/3 4.6B


Hello Volker,

I opened ticket 19525. Can you please just give me a brief list of
limitations and exceptions? Support pack level, etc. We are in the
planning phase for a project at the moment. If we decide to go to
enterprise, this could affect our strategy.


Craig.

--- In DoNotReply@consolut.eu, "Gueldenpfennig, Volker"
<volker.gueldenpfennigZs...> wrote:
> 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
>
> -----Original Message-----
> From: MCPARTLAND, Stan [mailto:stanley.mcpartlandZb...]
> Sent: Mittwoch, 26. Februar 2003 16:36
> To: 'DoNotReply@consolut.eu'
> Subject: RE: EBCDIC/ASCII Codepage Conversion of R/3
4.6B
>
>
> Hi Christian,
>
> Great news! Please post another message when OSS Note 599700 is
available.
>
> Regards,
> Stan
> ----------------------------------------------
> Stanley A. McPartland
> Enterprise Application Architect
> Bently Nevada
> 1631 Bently Parkway S; Minden, NV 89423 USA
> Voice: +1 (775) 215-1139 DC: *201-1139
> Mobile: +1 (775) 230-1470
> Fax: +1 (775) 215-2894
> mailto:stanley.mcpartlandZb...
> http://www.bently.com
> ----------------------------------------------
>
>
> -----Original Message-----
> From: d001807 <christian.hoeltersZs...>
> [mailto:christian.hoeltersZs...]
> Sent: Wednesday, 26 February, 2003 4:27 AM
> To: DoNotReply@consolut.eu
> Subject: EBCDIC/ASCII Codepage Conversion of R/3 4.6B
>
>
>
> Hello,
>
> we initially provided the EBCDIC/ASCII codepage conversion for
> - R/3 4.6C
> - BW 2.1C
> - CRM 2.0C
> - EBP 2.0C
> - KW 5.2
> to the full extent.
>
> To reduce the number of steps necessary to upgrade BW systems for a
> significant number of customer installations from BW 2.0B to BW
3.0B,
> we extended the EBCDIC/ASCII codepage conversion support in 09/2002
to
> - BW 2.0B
> with some restrictions.
>
> To reduce the number of steps necessary to upgrade R/3 systems for
a
> significant number of customer installations from R/3 4.6B to R/3
> Enterprise, we extend the EBCDIC/ASCII codepage conversion support
> effective to today to
> - R/3 4.6B
> also with some restrictions.
>
> For the restrictions that apply in these two cases and for the
> process to follow up there please read SAP note 599700.
>
> Since enabling both, an EBCDIC version and an ASCII version of any
> SAP product on iSeries is technically restricted to SAP Technology
> 4.6, we will not be able to extend the EBCDIC/ASCII codepage
> conversion support any further.
>
>
> Viele Grüße / Kind Regards,
> Christian Hoelters
> Development Manager
> SAP Technology on IBM eServer iSeries
>
>
>
> Have a look to our homepage at: http://www.consolut.net
> DoNotReply@consolut.eu
>
> Your use of consolut is subject to
http://www.consolut.net



Have a look to our homepage at: http://www.consolut.net
DoNotReply@consolut.eu

Your use of consolut is subject to http://www.consolut.net


Durban Tours - Südafrika Safari

General Data in Customer Master   Addresses (Business Address Services)  
This documentation is copyright by SAP AG.

Length: 7682 Date: 20240328 Time: 164415     sap01-206 ( 4 ms )