Solution : https://service.sap.com/sap/support/notes/45548 (SAP Service marketplace login required)
Summary :
SAP provides mechanisms for managing the transport of language-dependent data, emphasized from version 3.0B onwards. By default, data for all installed languages is exported though imports cannot be restricted to specific languages without utilizing the "selectivelanguageimport" option. Configuration for selective language transport can be tailored using R3trans options "language" and "language_selection_mode" within the TPPARAM profile. Interesting behaviors between language vectors and object types, including ABAP programs and text translations, are outlined, offering flexibility depending on system needs and configurations. For specific table entries and their translations, adjustments in master language handling post-Release 6.10 are highlighted.
Key words :
file /usr/sap/trans/bin/tpparam, /usr/sap/trans/bin/tpparam, ~ftp/general/r3server/patches/rel40b/, ~ftp/general/r3server/patches/rel45b/, assignment table customizing development class -> master language, standard transport tools tp/r3trans, enter additional individual keys, language-dependent data handled, customizing development class, object-specific translation tools
Related Notes :
| 1558267 | langdeletions = auto |
| 1375438 | Globalization Collection Note |
| 1319517 | Unicode Collection Note |
| 1259939 | Text table design |
| 1074030 | R3trans: "Duplicate key" composite SAP note (as of Rel 6.10) |
| 596982 | Texts are deleted by Support Package |
| 432272 | Transporting language data using tp/R3trans |
| 408265 | Comma as a language ID for the R3TR TEXT object |
| 365539 | R3trans selects too many languages for LIMU CUAD |
| 302063 | Correspondence Language |
| 136649 | R3trans: Selective language import |
| 88656 | R3trans: Duplicate key composite SAP note (Release 4.0-4.6) |
| 80727 | Transporting non-LATIN-1 texts |
| 19466 | Downloading SAP kernel patches |