Application Development Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 
UweFetzer_se38
Active Contributor

Last week I've been at the DSAG ABAP Developments Days in Walldorf. At the usual visit of the tapas bar in the evening we had a discussion about the translation of development objects in ABAP in Eclipse (ABAP Development Tools ADT). SAP currently suggests, that we use the SE63 to translate the objects after we finished our developments.

At least my "development workflow" looks a bit different: every time I've created a translation relevant object, for example a new message or text element, I immediately translate this object (let it be from German to English or vice versa, depends on my current project).

Let’s play Design Thinking and give the Persona a name:

Hello, my name is Uwe and I’m an ABAP developer. On a daily basis I’m working with translation relevant objects. This is how I’m currently working

1. Text elements

I’m using the following format, because no comment for text-xxx is needed


WRITE:/ 'This is just a test'(001).

With <f2> on the text I’m creating the element.

Marking the element and going to the translation are just two clicks away

After entering the text, save and exit I’m finished.

2. Messages

MESSAGE i002(ytestmsg) WITH 'Another test'(002).

<F2> on “i002” and the message will be created.

Again: after entering the text I’m going directly to the translation

Translate the text save and exit. Finished

3. Data element labels

After entering the last Field label I’m going immediately to the translation

Translate all text save and exit. Finished

Or do you have another translation procedure? Do you have in-house rules?

In Eclipse we currently have this situation: after <f3> on a non-existing text element or message we get

(Object not found. Creation via navigation not supported)

To be honest: I had to google where to find the text elements. Here you are:

The result is, that we end in the SAP GUI. Would be nice if we’ll get an Eclipse tool for text element, but that’s not part of this blog post.

Now my dear developer college it’s up to us to help SAP to “translate” this workflow to the Eclipse world.

Suggestion 1

a new Eclipse view which is active for every translation relevant object

Suggestion 2

a new tab in the properties view

Looking forward to your opinion. (and I promise you: SAP is listening :wink: )

You can find me on Twitter and G+

26 Comments
Labels in this area