SE63 — Translation
SE63 is used to translate SAP repository texts and custom development texts across maintained logon languages. It is most useful when multilingual custom developments, forms, data elements, messages or other repository objects require translation. For reliable SAP support, capture the exact system, client, user, time and object context first, then use the transaction's evidence before making configuration or data changes.
Verified practitioner reference for SE63 — Translation. It explains what the transaction does, when it is appropriate, which parameters and evidence matter, how to use it safely, common diagnostic traps, and how its role changes or remains relevant in S/4HANA.
Published 19 Sept 2026· 604 words
Diese Seite ist noch nicht auf Deutsch verfügbar.
Purpose
translate SAP repository texts and custom development texts across maintained logon languages. The transaction is most valuable when used as part of an evidence chain rather than as a shortcut. Start from the exact business or technical incident, preserve its user, time, system and object context, and distinguish display/analysis functions from actions that can alter system state.
When it is used
SE63 is typically used when multilingual custom developments, forms, data elements, messages or other repository objects require translation. Consultants also use it during project testing and post-change validation because a repeatable selection gives objective evidence. In production, keep the initial scope narrow and widen it only after confirming that the first result matches the reported incident.
How to use it in practice
- Identify the exact repository object and text type.
- Set source and target languages correctly.
- Translate in the designated translation system/client.
- Review text length and UI/form context.
- Transport or distribute translated objects according to the project's translation process.
Key data objects
These are the most useful anchors for work in SE63. Capture them in incident notes or test evidence so another consultant can reproduce the same result.
- object type — verify the exact value and its relationship to the affected execution or business object.
- source language — verify the exact value and its relationship to the affected execution or business object.
- target language — verify the exact value and its relationship to the affected execution or business object.
- object name — verify the exact value and its relationship to the affected execution or business object.
- translation status — verify the exact value and its relationship to the affected execution or business object.
How to prove it in the data
Build a reproducible before-and-after proof. Capture the exact selection or object, record the status, log or result that demonstrates the issue, then apply one controlled correction and repeat the same check. Correlate with neighboring SAP logs, documents or repository objects where needed. A successful retry with changed input is not the same as proving the original root cause.
ECC vs S/4HANA
SE63 remains the classic ABAP translation environment; S/4HANA Fiori applications may also involve UI5/i18n translation artifacts outside SE63. Availability of a classic transaction does not automatically make it the preferred implementation pattern for new work; distinguish support compatibility from clean-core and cloud-oriented design guidance.
Common pitfalls and how to diagnose them
- Translating generated texts that should come from master/customizing data. Validate the exact object, user, timestamp and release context before applying a fix.
- Ignoring text-length constraints in target languages. Validate the exact object, user, timestamp and release context before applying a fix.
- Maintaining translations directly in production. Validate the exact object, user, timestamp and release context before applying a fix.
Whose problem this is
Primary ownership is usually with the ABAP team. Bring in Basis, Security, functional or development specialists only when the evidence crosses those boundaries. A high-quality escalation includes the exact transaction, selection or object, timestamp, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/se63ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.