translation of cost element texts in all languages

1
SAP Note Statistic 13 | Printer-Friendly Version | PDF Version | Add to favorites | Subscribe | Quick link | 634887 - G/L account texts not copied into CO in other languages Version 6 Validity: 03.11.2011 - active Language Inglese Compare versions SSCR Download Content: Summary | Header Data | Validity | Correction Instructions | References Symptom FI G/L account texts are not copied for all languages to the cost element. Other Terms csku, skat, SAPLKMA4, OKB2, OKB3, KA01, KTEXT, LTEXT, short text, long text Reason and Prerequisites If you create a primary cost element via batch input (Transaction OKB3) or manually via KA01, the G/L account text is copied only in the logon language into CO. Other languages are not maintained in the cost element. This logic is not changeable. However, if you create a G/L account for which an entry exists in the automatic generation cost elements (Transaction OKB2), all texts are copied from FI into the cost element. Solution Execute the attached report. After entering the controlling area all missing texts are copied Statistic 13 | Printer-Friendly Version | PDF Version | Add to favorites | Subscribe | Quick link 634887 - G/L account texts not copied into CO in other languages https://websmp230.sap-ag.de/sap(bD1pdCZjPTAwMQ==)/bc/bsp/sno/ui... 1 of 1 02/10/2014 09:39

Upload: scontran

Post on 07-Dec-2015

250 views

Category:

Documents


3 download

DESCRIPTION

cost element translation

TRANSCRIPT

Page 1: Translation of Cost Element Texts in All Languages

SAP NoteStatistic13 | Printer-Friendly Version | PDF Version | Add to favorites | Subscribe | Quick link |

634887 - G/L account texts not copied into CO in other languages

Version 6 Validity: 03.11.2011 -active

Language Inglese Compare versions SSCR Download

Content: Summary | Header Data | Validity | Correction Instructions | References

Symptom

FI G/L account texts are not copied for all languages to the cost element.

Other Terms

csku, skat, SAPLKMA4, OKB2, OKB3, KA01, KTEXT, LTEXT, short text, long text

Reason and Prerequisites

If you create a primary cost element via batch input (Transaction OKB3) or manually via KA01,the G/L account text is copied only in the logon language into CO. Other languages are notmaintained in the cost element. This logic is not changeable.

However, if you create a G/L account for which an entry exists in the automatic generationcost elements (Transaction OKB2), all texts are copied from FI into the cost element.

Solution

Execute the attached report. After entering the controlling area all missing texts are copied

Statistic13 | Printer-Friendly Version | PDF Version | Add to favorites | Subscribe | Quick link

634887 - G/L account texts not copied into CO in other languages https://websmp230.sap-ag.de/sap(bD1pdCZjPTAwMQ==)/bc/bsp/sno/ui...

1 of 1 02/10/2014 09:39