Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

SE63 smartform translation (need clear explanation) experts plz help

Former Member
0 Kudos

Hi folks,

I read several posts regarding the smartform translation using SE63. After translating the smartform, let us say, from English to Finnish some say if we log in Finnish language and go for print preview the form prints in Finnish langauge and some say we need to specify, in the <b>Output Transaction</b>, Finnish as the language in which the Output type should trigger.

Can someone please give me clear explanation and clarify my doubts. I really in need of your help guys.... please help me.

THanks

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi

The language of the print doesn't depend on the logon language but message language.

The message language is stored in the master data of the partner of the print.

So for example if you have a finnish customer and he has the finnish as message language when you create a sales order all messages are printed in finnish.

Max

9 REPLIES 9

Former Member
0 Kudos

Hi

The language of the print doesn't depend on the logon language but message language.

The message language is stored in the master data of the partner of the print.

So for example if you have a finnish customer and he has the finnish as message language when you create a sales order all messages are printed in finnish.

Max

0 Kudos

Hi Max,

Do you mean message language means NAST-SPRAS field?

My requirement is:

I am working on a Purchase Order smartform in log on language English. And let us say I will be using only English logon language. In PO smartform there are several hardcoded lables and texts which are in English. Now if the language of the Vendor to which this Purchase Order is to issued is Finnish, then the hardcoded lables and texts should be printed in Finnish langauge (I am in same logon language English).

Can you tell me how can proceed in this case.

Waiting............

0 Kudos

Hi

Yes I do.

You have to translate the smartform from english to finnish by SE63.

This trx translates only the texts of course, it's the same for the sapscripts.

Anyway the finnish has to be a language loaded on your system.

When the smartform is called the system display the texts in the language of the message if they aren't the'll be printed in the original language (so the english I suppose).

The original language is the language you have used to create the smartforms (so the language you use for logon).

Max

0 Kudos

Hi Max,

I dont know much about the output types and message types that is why its not very clear for me.

You said

<b>When the smartform is called the system display the texts in the language of the message if they aren't the'll be printed in the original language (so the english I suppose).</b>

Can you please explain this clearly. What do you mean by calling the smartform. Please help.

waiting..........

0 Kudos

Hi Max,

Can you please explain this.

How is the message language assigned to a vendor and when is the table NAST updated with those entries.

Please help. Waiting..................

0 Kudos

Hi

Every kind of logistic document (sales order, purchase order, bill, delivery,.....) can have several prints (messages).

Each message can be printed if the document has a certain status.

Each message is defined in customazing using message type by trx NACE.

When you define a message type you insert the form (sapscript or smartform) and driven program.

When a message is loaded on document, the language is picked up from the master data of vendor

(or customer).

Try to run the trx XK03 (or XD03), here you'll find the language of vendor (customer).

Now the problem is only some languages are loaded on the system, so you can create the prints

only using these languages, for these reason it usually defines a default language.

The default language is the original language used to create the print.

So if you try to print a document in a language not loaded on SAP, the system'll use the default

language.

but you're careful! The smartform checks if a language is loaded or not loaded on SAP, in this

last case an error'll occur.

Max

0 Kudos

Hi Max,

For example I am working with a custom message type ZNEU for Purchase Order form. ZNEU is defined in NACE.

And you said

<b>When a message is loaded on document, the language is picked up from the master data of vendor

(or customer).</b>

What do you mean by message loaded on document. Do you mean for example for document Purchase Order going to ME22 and assigning the message there.

According to your explanation, the message language should be always same as the language of the Vendor or Customer. Am I correct?

Please reply Waiting.............

0 Kudos

Hi

The messages are automatically load on documents, see the procedures and conditions type in NACE.

Here You can decide how and when the messages have to be loaded.

Anyway you can laod them manually:

- trx ME22N: Goto->Messages

- trx ME22 : Neader->Messages

Yes It should! But you can't assign all the language of the world, but only those loaded on the system, in the rest of case yuo should assign a default language.

Max

Former Member