When maintaining a condition table (Pricing, Output, Material Listing, Material Exclusion, Material Determination, Rebate Processing, Condition Index, Batch Determination, or Certificate Determination )
Some of the interface (GUI) is not translated or appears in German.
The interface for the condition tables is generated.
Typically, the regeneration of installation specific condition tables is carried out directly after a major upgrade. This means for example an upgrade from 2.1x to 2.2x. But, the language import is often carried out a few days later. Thus the regeneration program does not have access to the translation and cannot properly regenerate the GUI.
This does not occur often because the condition tables are usually created after the language import and the elements necessary for the language regeneration remain stable from release to release.
We have been working on making the regeneration process better.
Some of improvements for release 3.0 are:
- Reduction of the language dependent generation using new technology from the basis. The only remaining language dependent part is the selection texts for the selection reports.
- A 'real time' regeneration and not a batch regeneration directly after the upgrade. The regeneration is fully automatic and and occurs after even miniputs. This insures that the most current translation is used.
If there should be problems with condtion tables after a language upgrade, the installation specific condition tables (Tablerange 501 to 999) can be regenerated with the report RV12A001.
The language dependent components are reports and screens.
Additional key words
Transactions: VK11, VK12, VK13.
Program: SAPMV13*
Reports: RV13*
No comments:
Post a Comment