Handling Customer Translations During the Upgrade

8/3/2019 Handling Customer Translations During the Upgrade

http://slidepdf.com/reader/full/handling-customer-translations-during-the-upgrade 1/7





16.11.2011 Page 3 of 7

SAP Note 485741 - Handling customer translations duringthe upgrade

populate this field, the system displays a dialog box for

creating a new transport request.

4. Execute the report RSLTMOD. After the report has run, the

transport objects, for which the translation of the standard

SAP system has been changed or enhanced, are placed in a

transport request.

5. Repeat the run for all relevant languages. Note that you

must create a new transport request for each language.

- Release 4.6x and higher

For these releases, you can use transaction SMLT_EX to create a

language package with your own translations. The use of

transaction SMLT_EX requires that the translated objects are

contained in a piece list or in a transport request.

Information about creating a language package is available inthe SAP Library under:

German: SAP-NetWeaver-Bibliothek -> Leitfaden für

Administratoren -> Technisches Betriebshandbuch für SAP

NetWeaver -> Administration von SAP NetWeaver Systemen -> AS

ABAP (Application Server für ABAP) -> Softwarelogistik ->

Sprachentransport.

English: SAP NetWeaver Library -> Administrator´s Guide ->

Technical Operations Manual for SAP NetWeaver -> Administration

of SAP NetWeaver Systems -> Administration of the SAP Web

Application Server (ABAP) -> Software Change Management ->

Language Transport.

- Release 6.20 and higher

As of Support Package 25 of Release 6.20, there is an option of

placing objects, which were translated using transaction SE63

or for which the translations were adjusted, in a transport

request. See Note 669505 for Release 6.20 as of Support Package

25 or Note 980626 for Release 700 and higher.

- Information about using the report RSLTMOD:

The report uses modification recording to find the changes to

translations. This means that it finds only the translated

objects that are contained in the modification log. Especially

the object set of the report RSLTMOD and the other tools may

not necessarily be identical as a result.

The report RSLTMOD is supported only for Release 45B and will

not be developed further.

-

2. Export in the source release

Release the transport requests that were created using transaction SE09.



16.11.2011 Page 4 of 7


Caution: In addition to the translation, the releasedtransport requests also contain language-independent parts.The import of these requests into the system with the targetrelease using the standard procedure ("tp import" or TMS) maycause considerable damage in the system.

3. Import in the target release (6.20 and higher)

- Import only the language parts of transport requests.

1. Start the report RSTLAN_IMPORT_SINGLE. It is contained in

the Support Package listed below for Release 6.20. You require

SPAM Version 6 or higher because functions from this area are

used.

2. In the "Transport Request" field, specify the transport

request that you want to import.

3. In the "Language" field, specify the language for which youwant to import language parts from the request.

Language-independent parts are not imported if youuse this import mode.

See Note 785847. This note provides additional information

about languages that are specified with lowercase letters, such

as Icelandic. To ensure that the import is processed correctly,

you must use a current R3trans version.

4. If the "Create Backup Request" field is selected, the report

first creates and exports a backup request after it is started.

If too many texts are overwritten after the import of the

specified request, you can import the backup request to restore

the previous language status.

5. Repeat the import for all of the saved transport requests.

- Import the language packages.

If you have created a language package with source release 4.6x

or higher, use transaction SMLT to import it.

- The import using the report RSTLAN_IMPORT_SINGLE is also used

for transports that were generated using Note 669505 or 980626.

Caution: Supplement to the correction instructions:

Before you implement the correction instructions for releases lower than

Release 46C, you must use transaction SE38, for example, to recreate the

report RSLTMOD.

Creation attributes:

Type: Executable program

Status: SAP Standard Production Program

Application: Basis (System)Package: SECE



16.11.2011 Page 5 of 7


After the implementation, you must create the following selection texts:

DARK Allow User Interaction

M_CORR Template Request/Task

P_CORR Target Request/Task

P_LANG Language

P_LOCK Lock Objects

and the following text symbols:

001 Include modified translations in language &1 in order

002 Error: message not found

003 OK

004 User termination

005 Error

006 No language selected

007 No objects found

Note for Release 4.5B: This release is no longer maintained. The second and

third set of correction instructions are not released for Release 4.5B as a

result. Solution:

In this case, implement the second and third set of correction instructions

manually.

Header Data

Release Status: Released for Customer

Released on: 11.05.2011 13:19:50

Master Language: German

Priority: Recommendations/additional info

Category: Upgrade information

Primary Component: BC-UPG Upgrade - general

Secondary Components:

BC-CTS-LAN Language Transport

Valid Releases

Software Component Release From

Release

To

Release

and

Subsequent

SAP_APPL 45 45B 45B

SAP_BASIS 46 46B 46D

SAP_BASIS 60 610 640 X

Support Packages



16.11.2011 Page 6 of 7


Support Packages Release Package Name

SAP_APPL 45B SAPKH45B53

SAP_BASIS 46B SAPKB46B41

SAP_BASIS 46B SAPKB46B56

SAP_BASIS 46C SAPKB46C33

SAP_BASIS 46C SAPKB46C48

SAP_BASIS 46D SAPKB46D26

SAP_BASIS 610 SAPKB61025





Related Notes

Number Short Text1375438 Globalization Collection Note

964731 Customer language 'Z1' in the upgrade

960783 Add. info.: Upgrade to SAP NW 7.0 Support Rel. 2 ABAP

905029 Add. info.: Upgrade to SAP NW 2004s Support Rel. 1 ABAP

826488 Enhancements to upgrade on SAP CRM 5.0 ABAP

826093 Add. info. on upgrading to SAP SCM 5.0 ABAP

826092 Add. info. on upgrading to SAP ERP Central Component 6.0

818322 Add. info.: Upgrade to SAP NW 2004s ABAP

788218 Add. info. on upgrading to SAP ERP Central Component 5.0 SR1

785847 Postlanguageimport does not import correctly

775047 Add. info. on upgrading to SAP Web AS 6.40 SR1

737696 Add. info on upgrade to SAP R/3 Enterprise 4.70 Ext. 2 SR1

689574 Add. info. on upgrading to SAP ERP Central Component 5.00

684406 Additional information on upgrading to SAP SCM 4.1

661640 Add. info. on upgrading to SAP Web AS 6.40

637683 Add info about upgrade to SAP R/3 Enterprise Core 4.70 Ext 2

587896 Add. info on upgrade to SAP R/3 Enterprise Core 4.70 SR1

484876 Additional information about upgrading to SAP Web AS 6.20

437096 Translations appear under <unknown> in SPDD

Attributes

Attribute Value

Transaction codes HIER

Transaction codes SE09

Transaction codes SE63

Transaction codes TRANSAKTIONEN

Correction Instructions



16.11.2011 Page 7 of 7


Correcti

on

Instruct

ions

Valid

from

Valid

to

Software

Component

Typ

e

*)

Reference

Correction

Last

Changed

454877 45B 45B SAP_APPL C Y4DK8A09IL 12.09.2002

07:30:57

454705 46B 620 SAP_BASIS C Y9CK027435 12.09.2002

07:46:16

637659 46B 640 SAP_BASIS C Y6BK049036 07.05.2004

07:24:44

*) C Correction, B Preprocessing, A Postprocessing, M Undefined Work

Documents

Handling Customer Translations During the Upgrade