Data elements in multiple language

Hello SDNites,
I have some 300 data elements and all these data elements have to be maintained in 13 different languages. Can someone please suggest me the best way to do the same?
As per my approach, go to table DD04T, maintain the entries over there in different languages and explicitly attach this table in transport request. Suggest me is this the right approach?
Regards,
Abhi

Hi!
Try to look at this FM RPY_DATAELEMENT_UPDATE
Maybe you can quickly create a program that implement it and update all the texts you need.

Similar Messages

Reference data extraction in multiple languages

Hi all
I'd like to extract reference data from ECC system for say Material Groups with the descriptions in both English and German.
I added entries in the MDMGXC1 table to import the material group key and description into MDM lookup tables. Even though the German values exist in ECC its only the english ones which are imported.
This happens with all the reference tables. Is it because the language assigned to me in the ECC sys i EN, its by default picking up only that?
Thanks
SwarnaDeepika

Hi Swapna,
Check your repository definition in ECC using MDMGX transaction and "Define repositories". Please check and revert if you have german "DE" languages defined for your repository. You can define multiple languages seperated by Comma.
Please revert with your findings..
Best Regards,
SHiv

Data Conversion in Multiple languages environment

Hi,
I appreciate your help in throwing some light for the following question.
I need to do conversion of data from legacy system to Oracle Applications R12 environment.My problem is i need to load data in different languages.For example i need to load item information in US english as well as French.If i am right i think NLS_LANG variable need to be set before loading the data.I understand the data need to be loaded in to tl tables and language column in b table.But i am not sure of the sequece of steps need to be followed while doing the conversion.
Please help.
Thank you

The generic guide ares ML Docs 393861.1 (Globalization Guide for Oracle Applications Release 12) and 372952.1 (Customer Translations). Pl identify which modules you are loading data for.
HTH
Srini

How to print hard-coded data in multiple language in sapscript.

Hi All,
How to print hard-coded data in multiple language in sap-script, here the requirement is when printing the output
we can see the window heading, description which are mostly hard-coded here I want to print these in both language as fallows,
Goods to be delivered: = Morada de Entrega:
Total net value excl. tax = Valor Total (IVA não Incluído)
Description = Descrição
Item = linha
here I want to print in both languages like---- Goods to be delivered:/ Morada de Entrega:
and the above headings in English are hard-coded.
Kindly suggest me on this.
Thanks in advance.
Arun.

Hi Arun,
Use Standard text ade those text elements. Then use those in SAP script using different languages.
Regards,
Amitava

Address Data in Multiple Language

Hi Friends,
How can i mentain Address Data for Vendor/Customer in multiple language while Uploading through BAPI or if any other method to achieve the same.
Regards
Sonal

Hi Arun,
Use Standard text ade those text elements. Then use those in SAP script using different languages.
Regards,
Amitava

Multiple language data in the same table and indexes

We have 8.1.5 database with
NLS_LANGUAGE=ENGLISH and NLS_TERRITORY=UNITED KINGDOM set at the database level. We also set the NLS_LANG appropriately when we index the data. We also use the preference setting BASE_LETTER=YES when indexing.
Our tables contain book titles which is what we index using interMedia. Being an online book store, this table may contain titles in English (most of the titles are in English being UK) and some titles in French. Please note the French language has accents and diacritics. Normally in a French database with NLS parameters set correctly and BASE_LETTER=YES, if we search for a title with accent / diacritic it will return the record correctly and match the rows with or without the accents (e.g. searching for video will return both vidio (not the accent on e) and video). However, with the UK settings the accents are not ignored during indexing and it only returns the records that exactly match the search word (e.g. searching for video returns only video and searching for vidio returns only vidio (note the accents on e in the last two videos)).
Question: Is there any way to appropriately index multiple language specific titles in the same database? If yes, how? Is it possible at all? Suggestions, ideas are welcome.
null

Similar request; if there are several different languages used in a database, but a search word can be typed in by anyone and not necessarily in the default language, I still want to be able to pick up all the records (including text in blobs) in any language where my search word = the equivelant word in the other languages; eg. searching on "tree", the search would bring back a document that contained "l'arbre". I then want to set the default language, and allow the user to select a "search in these languages" option to expand the search from the default "tree" to all languages in the database.
I know about the multi_Lexer but does it extend functionality to this level?

Field label from data element (language dependent)

I have 2 development systems and am struggling to get different language from a standard sap data element.
On Dev system 1 the program is:
parameters: l_file1 like filename-fileintern.
In the selection texts of the program I select "Dictionary ref." and the text is automatically populated with the value "Logical File" i.e. it picks it up from the data element FILEINTERN of the parameter.
Now I log out and log back in in German and in this field I have "logische Datei" i.e. as expected this is the value in the data element of FILEINTERN.
When I logon in English and execute the program, the selection screen has "Logical File", and when I login in German and execute the program the selection screen has "logische Datei".
All well and good at this point and everything works as expected.
On Dev system 2 I have exactly the same program i.e. the same parameter, and same selection text settings.
However when I logon in English and execute the program I get "Logical File", but when I log on in German and execute it displays "L_FILE1" i.e. the name of the parameter and not the data element text value?
Any help greatly appreciated.

Hi Edgar and Sree,
Yes I have checked the data element in both systems and it is identical. In fact in the 2nd system when I log in in German and display the selection text it is correctly in German, only when I execute the program I don't get the value on the screen!
I realise I can simply uncheck this "dictionary ref." and translate the value myself but i want to understand why this doesn't work.... argh.

SQL server support or can store data in multiple languages? If so, how is it done

Hi All,
Can you please let me know If SQL server support or can store data in multiple languages? If so, how is it done..
Thanks,
Subbu
Thanks, Subbu

Yes, you have to use Unicode data types such as nchar and nvarchar to store the data. See https://technet.microsoft.com/en-us/library/ms191200(v=sql.105).aspx
Satish Kartan www.sqlfood.com

Changing locale settings of DB2 for storing data in multiple languages

hi friends,
i want to know how to store data in multiple languages in the same
DB2 database. i am developing a e-commerce application which stores
data of users around the globe. i know that i need to create a database
with characterset UTF-8. But how will i change the locale (language and territory) of the user session. (i am asking something corresponding to to Oracle's ALTER SESSION nls_language command). i want to insert data through JDBC.
please help me.
Binu Joseph

But how will i change the
locale (language and territory) of the user session.Store all keywords in a database, using the local name (e.g. us-en) as the primary key. Your servlet should determine the user's locale (ServletRequest.getLocales()) and use it as the primary key for an SQL select.
Now use the fields obtained from the DB to populate your HTML page.

Loading data in multiple languages using Import Manager

Hello Experts,
I have a description field associated with Main table, and need to load the data in multiple languages.. How to load the data in Multiple languages using Importmanager?
Thanks in advance..

Hi Kiran,
Please do the changes as mentioned in this threads:
Re: Multi Language Question
Multilingual field
Regards,
---Satish

Insert data in multiple languages

Hi,
How can I store data in multiple languages using SQL*plus.
What setting do I need to make.
NLS_CHARACTERSET
WE8ISO8859P1
mention the steps for the following.
Thanks
Jagriti
null

I recommend looking at the Globalization support FAQ at:
(http://technet.oracle.com/products/oracle8i/)

Master data in multiple languages

Hello All,
I have some masters data like vendor ,customer and gl master of 7 countries in multiple languages.
Now how to map or maintain all these masters in SAP so tht whenver user login using his regional language like chinese user or french user or spanish user he should be able to see all the data in the logon language only.
Pls let me knw how to proceed..
Regards,
Sunny

Hi,
U need to do transaltion from english to other languages in transaction code SE63..
Regards,
Nagaraj

Syndicating Master Data in Multiple Languages

What are the different approaches of syndicating multilingual data? We have a repository that contains data in 6 different languages. How do we syndicate all these languages?
a) One separate file per language?
b) One file with all values for all languages?
c) Other?
Thanks

Hi,
Yes thats right , But if you see MATMAS structure , these two nodes <SPRAS_ISO> and <MAKTX> are situated under <E1MAKTM> segment. And this segment is repetable (You can set this property in "Destination Items" tab.
Now map the fields accordingly , you should be able to see a structure which will look like:
-<MATMAS05>
-<E1MARAM>
- <E1MAKTM SEGMENT="">
<MAKTX>English Description</MAKTX>
<SPRAS_ISO>EN</SPRAS_ISO>
</E1MAKTM>
- <E1MAKTM SEGMENT="">
<MAKTX>French Description</MAKTX>
<SPRAS_ISO>FR</SPRAS_ISO>
</E1MAKTM>
- <E1MAKTM SEGMENT="">
<MAKTX>Spanish Description</MAKTX>
<SPRAS_ISO>ES</SPRAS_ISO>
</E1MAKTM>
And it goes on.
Regards,
Amol.

Best practice in working with Adobe forms in multiple languages

We have to provide access to some Adobe Interactive Forms in both English and French, some of them from Web Dynpro application(s), some of them as callable objects from Guided Procedures.
1- We know for sure that we can have two copies of each form, one in English and one in French but that implies duplicating the FormCalc and Javascript code behind.
2- Another way if to modify in javascript all labels, captions using some javascript i.e. If lang = "E" then "My label" else "Mon étiquette" . It would work but it is not very efficient.
Is someone here has experience with this type of situation and would be willing to share his experience with me?
Thanks in advance,

Hi Benoit,
For Adobe Forms in multiple language you can use include text solution also . Within this solution you need to add a language parameter in your interface and then retrieve the include text in the language value ( not current language ) . Personnaly i used a lot this solution with Smartforms text .
Also i used dictionnary text for text linked with data dictionnary element . For this there is standard function module in SAP .
Anothers way is in the SFP editor you can translate your form as in SAPSCRIPT .
Hope this help you
Regard.
PS : if necessary i can send you a sample form with smartform/Dictionnary text solution.

Multiple currencies? Multiple languages?

hi,
Does SAP handle multiple currencies? Multiple languages? What is a currency factoring technique?
Thank you
Ashok kumar

HI,
Yes.
SAP handles Multiple Currencies and Languages
see the table TCURR, TCURC for different currencies
Currency Factoring Technique:
Currencies in Planning
In Profit Center Accounting, three currencies can be stored at once:
Transaction Currency
The transaction currency is the currency used for a specific transaction. You can choose a different currency from the list of valid currencies for each new transaction. The transaction currency is stored in the transaction data for Profit Center Accounting as the so-called "first currency".
Local Currency (Company Code Currency)
The controlling area currency is stored in Profit Center Accounting as the second currency.
Profit Center Local Currency
You need to set a special currency for Profit Center Accounting in Customizing for each controlling area. This currency is used in the standard reports, among other things. You can find more information about this currency in Customizing. The profit center currency is the third currency updated in the transaction data.
How Do I Plan Currencies in Profit Center Accounting?
You first plan a profit center in USD. Then you later plan the same profit center in DEM in a second planning session. This may be necessary if:
the planned costs for the profit center in a certain cost element consist of external invoices in the local currency and external invoices from abroad and
the external invoice from abroad was billed and paid abroad
The currencies which can be planned manually are defined in the Layout.
If the corresponding key figures are defined and ready for input in the planning layout, you can plan in any permissible transaction currency, the company code currency or the profit center currency. The planned amount is then immediately and automatically translated into the other currencies. Note, however, that the system can only translate into a transaction currency if you have explicitly specified a transaction currency.
If you want to want to plan data using different transaction currencies, you need to use a planning layout that contains the characteristic "Transaction currency".
Note that data can only be saved in the transaction currency if a transaction currency has been specified. Otherwise the data will only be saved in the other currencies without the transaction currency.
If you want to want to summarize data in the transaction currency, you need to use a planning layout that does not contain the characteristic "Transaction currency". You can then:
change the summarized values, in which case the changes are not updated in the transaction currency, and
add any combinations of objects that have not already been planned.
If you
enter one transaction currency, the system only displays the amounts planned in that currency. You can
change these amounts
plan in the currency specified
enter a number sign (#) to represent the value " " (no value), the system only displays those values that were planned without the transaction currency. You can
change these amounts
plan amounts without a transaction currency
specify more than one currency or all currencies (*), the system displays all the planned values. You can
change these amounts
can plan as yet unplanned combinations of your planning objects in any valid currency.
Planned currency amounts are translated using
the value date you entered in the planner profile for your area
a translation factor entered in the currency table for the exchange rate type entered in the planner profile
You will find further information about the currency table and currency translation in the documentation FI Configuration and Organization.
Transfer Pricing Using the Conditions Technique
The term "transfer pricing" is used to describe the calculation of prices for internal exchanges of goods between profit centers. Conditions are the individual steps carried out during price calculation. When a goods movement takes place between two plants, the price can depend on a number of factors, such as the material involved, the sender plant, the profit center, the partner profit center, and so on. The information on these variable factors is stored as master data in the form of condition records. There the transfer price can be defined as a fixed price or a percentage increase or reduction.
This section describes the steps necessary to define transfer prices. You define these transfer prices in Customizing. There you will also find a detailed description of how to proceed.
Define condition tables, which you use to store condition records for each condition type.
Here you define the price dependencies for transfer prices. You can make the transfer price found dependent upon a combination of fields. For example, if you want your transfer prices to be defined for a combination of material and partner profit center, you need to define a condition table that contains these key fields. The condition records then contain the individual prices for each combination of material and profit center. You maintain the condition records when you define the individual condition types.
Define access sequences that the system should use to search for valid condition records.
An access sequence is a search strategy that the system uses to find valid data for certain condition tables. Each access sequence consists of one or more steps, which the system processes in the order specified. The order determines where the system should look first for a valid condition record. You can specify an access sequence for any condition type for which you create condition records.
Define condition types for all the pricing elements (fixed amounts, markups and markdowns) that occur in your daily business operations.
In Profit Center Accounting, a condition type represents a component of a transfer price. You can define condition types for every type of fixed price, markup or markdown that occurs in your internal goods movements. If you define a percentage markup or markdown as a condition type, you also need to define another condition type to serve as the basis for this percentage. This can be a price stored in the material ledger. The relationship between these two condition types is then defined in the pricing procedure.
In some condition types you need to specify an access sequence. In this way you determine which fields the system should use to search for a valid condition record.
Define condition records that determine the amount or percentage to be applied for each set of values in the condition table (such as "fixed price of USD 100.00 for material 01, profit center ABC, and plant 0001").
You can maintain condition records directly from within the definition of the condition type. Or you can define them from the application menu by choosing Master data ® Transfer prices ® Conditions. It is also possible to copy existing condition records to create new ones. This is especially useful if you want to change the currency of the condition record. You can maintain condition records either in Customizing or in the application menu, under Master data ® Transfer prices.
Define a pricing procedure to group together condition types and determine how they relate to one another.
In addition to the selection and order of condition types, a pricing procedure determines
which subtotals should be calculated
what base value the system should use for calculating percentage markups or markdowns
what conditions must be met in order for a certain condition type to be calculated
The base value for markups and markdowns can be either a fixed price or a value from the material ledger. Using a routine supplied in the standard R/3 System, you can have the system read the legal, group, or profit center price from the material ledger and calculate the markup or markdown on this basis.
Define condition exclusions, which let you determine which condition type should be used in a given situation.
In transfer pricing for goods movements, it often happens that a number of different condition records are valid. Using condition exclusions, you can compare conditions with one another and use, for example, the most favorable price for the partner profit center.
For different condition exclusion methods are available:
· The most favorable condition in an exclusion group
· The most favorable condition record for a condition type
· The most favorable condition among different exclusion groups
· Exclusion of those conditions in an exclusion group when a condition type that belongs to another exclusion group appears
Define transfer price variants, which let you specify which pricing procedures are relevant for actual data and which for plan data.
To valuate different datasets, such as plan and actual data, using different conditions, you can define variants with an assignment to a specific pricing procedure. The system processes the specified procedures in order until it finds a valid transfer price.
In transfer pricing for goods movements, only actual data is valuated (variant 000). However, you can also create additional variants if you want to calculate plan prices on the basis of pricing data.
Define pricing reports, which determine the structure of lists of conditions.
A pricing report lets you analyze condition records according to certain criteria and define the structure of these lists. You can define pricing reports either in Customizing for Profit Center Accounting or in the application menu, under Master data ® Transfer prices ® Pricing reports.
Regards,
Padmam.

Data elements in multiple language

Similar Messages

Maybe you are looking for