Introduction
Translation process in SAP converts amount posted in Local Currency (also known as Company Code Currency) into Group Currency for the purpose of Group Reporting. Translation Sets contain the GL accounts on which posting can happen and therefore would be considered for currency translation.
This document reveals the process to create translation sets in SAP. Newly created sets must be assigned to the correct active Translation Methods.
Configuration
Configuration of Translations Sets & Methods involves the following steps:
- Creation of Translation Sets
- Creation of Translation Methods
- Adding Sets to Translation Methods
- Validating Assigned Sets to Translation Methods
Creation of Translation Sets
Enter Transaction code: GS01
- Enter Set ID (as per the request):A_OPACC_9988110_OPEN
- Enter Table e.g. XXREPO
- Select Set type: Basic Set
- Enter
- Enter Field name RACCT (Account Number)
- Enter a Description e.g. 9988110_OPENING RATE
- Enter Accounts to be included in the set (as per the request).
- Select Save
This process needs to be repeated until all the new sets have been created.
For example: Below mentioned 3 sets have been created-
- Set name: A_OPACC_9988110_OPEN
- Set name: A_OPACC_9988220_CLOSE
- Set name: A_OPACC_9988330_AVERAGE
Creation of Translation Method
- Enter Transaction code:- GCW4
- Translation method– AAA01 (for example)
- Name of Translation Method– Dummy Method 1 (for example)
- Enter Table Name – AAREPO (for example)
- Enter Usage Indicator *– 2 (for example)
*Usage Indicator: currency translation usage FI-GL/-LC - The entry indicates whether to use the currency translation method from the special ledger or from the consolidation system.
This is how below Translation Methods have been created:
- AAA01Dummy Translation Method for Operational GL A/C's)
- GGG01 (Dummy Translation Method for Group GL A/C's)
Adding Sets to Translation method
All sets must be added to either AAA01 or GGG01 Translation Methods, depending on whether GL account in sets is Operational GL account or group GL account.
Steps for Adding New Sets to Translation Methods
- Enter Transaction code: GCW4
- Double click on the Translation Method required e.g. AAA01
- Within the method find the most logical place to insert the set (take a note of the number)
- Select Create
- Ensure Translation entry radio button is selected
- Enter Insert after field the number that was noted above, the new set will be added after that entry.
- FS Item Set: Enter New Set Name (Set name) e.g.A_OPACC_9988110_OPEN
- Exchange rate indicator: enter From Template
- Translation Key: enter From Template
- Debit Item: enter From Template (Account got difference postings column)
- Credit Item: enter From Template (Account got difference postings column)
- Select Save
Based on the set names to be created, the following information is required before commencing the build:
- Translation Method
- Table
- Exchange Rate Indicator
- Translation Key
Translation Methods
The labeling of the new sets is based on whether the set includes Operational GL Accounts or Group GL Accounts. These sets are assigned to Translation Methods: AAA01 or GGG01 accordingly.
Table
Each set must be assigned to a table. This is because sets are table specific and the tables to be used are the summary or the totals tables when creating new sets.
- Operational Accounts: AAREPO (for example)
- Group Accounts: GGREPO (for example)
Exchange Rate Indicator
This is determined by the naming convention of the set.
- Opening
- Average
- Closing
Translation Key
This is determined by the naming convention of the set.
- Opening
- Average
- Closing
For example -
For creating FS item set: A_OPACC_9988110_OPEN (OPENING RATE)
For creating FS item set: A_OPACC_9988220_CLOSING (CLOSING RATE)
For creating FS item set: A_OPACC_9988330_ AVERAGE (AVERAGE RATE)
This process needs to be repeated for each newly created translation set
Once all the sets have been added to the translation method e.g. AAA01, the method needs to be validated.
Validating Sets Assigned to Translation Methods
Following steps needs to be followed for validating translation method to which new sets have been assigned.
- '-' in Check column (Blank): This means that the method has not yet been checked
- Select the check button now
- Once the check has been completed, the Check column will have one of the following statuses:
'E': The method was checked with errors
'X': The method was checked without errors
If the method has an ‘E’ in the column, then there are errors in that translation method. This could be due to overlapping accounts in assigned sets. The sets in question will be displayed in Validation Report and further investigation needs to be done to correct the errors.
Example of Validation Error Report for Translation Method AAA01 –
Following error has occurred due to presence of same GL account in both the sets at line number 100 & 120 in Translation Method AAA01.
To correct this error, change/ delete the GL account from any one of these two sets.
- Once the corrections have been made, the translation method needs to be validated again and the field will be populated with ‘X’ in the Check column.
- If the method has ‘X’ in the column, then this can be flagged as Active
Once all the sets have been assigned to the required methods and these methods are activated, the build is complete.
Testing
As a part of testing, following checks need to be made:
Check 1: Sets Created
- Transaction code SE16
- Table: SETLEAF
- Enter
- Select Multiple Selection button against Set ID field, Enter the New Sets created in the Single Values tab and Execute
Check 2: FS Item Sets Created
- Transaction code: SE16
- Table: T884
- Enter
- Select Multiple Selection button against FS item set 1 field, Enter the New Sets created (from the Template) in the Single Values tab and execute
Check 3: Journal Posting
- Transaction code: FB50
- Post a journal using Accounts that have been included in the newly created Translation Sets
Check 4: Executing the Translation Program
- Transaction code: SA38
- Run program: RGUUMR01 (FI-SL Currency Translation Program)
- Check if Period & Year have been updated
- Execute (preferably in Background)