Note 1788995

PY-IN: Dual language handling in PA Infotypes

Scenario 1: Personal data (Infotype 02) in both English and Hindi:

Consider an example where a Company decides to maintain First Name and Last Name of employees in
both English and Hindi languages.
English is the default language and data is being maintained in that language. With the new solution, the users can
maintain the First Name and the Last Name in Hindi as well.

Follow below steps to customize table view V_T799IN_MLFM:

1) Identify the database table name (PA table) where Infotype 02 records are saved. For Infotype
02, it is PA0002.
2) Identify the standard fields in PA0002 table which stores First Name and Last Name.
First name VORNA
Last name NACHN

3) Add new customer specific fields (Z-fields) in the Customer Include (CI) of Infotype 02. In case of
Infotype 02, it is CI_P0002. Note that:
New z-fields in CI Include will correspond to the Standard fields
Data type of z-fields must be same as Standard field (here VORNA and NACHN)
New z-fields will store the First Name and Last Name in Hindi
You can use existing Standard Data Element (Component type) as well. Here we
created z-data element (ZPAD_VORNA) to have different Short Description

Page 1 of 10

Note 1788995

PY-IN: Dual language handling in PA Infotypes

In this case we create:

ZZVORNA_HI corresponds to VORNA
ZZNACHN_HI corresponds to NACHN

4) Perform the mapping in table view V_T799IN_MLFM as shown below:

The Original Database Table and Target Database Table must be same
The data type of the Original Database Field and Target Database Field must be same
Language will be HI, as you want to open saving of First Name and Last Name in Hindi
This customizing table is not used to store data, it is just used to perform mapping.

Page 2 of 10

Note 1788995

PY-IN: Dual language handling in PA Infotypes

The following explains how Infotype data maintenance works:

1. Login to the system in English and open Infotype 02.

2. Login into the system in Hindi and open Infotype 02 (via transaction code PA30). Note that
this is the first time you are viewing Infotype 02 with Hindi logon.

Both First name and Last name will appear in English, since it was maintained in English
language first. This time the data is being fetched from VORNA and NACHN. The fields
ZZVORNA_HI and ZZNACHN_HI still do not contain any data.
3.

To maintain data in Hindi language, overwrite the English names with Hindi names as
follows:
First name: Kishore ->
Last name: Kumar ->

Page 3 of 10

Note 1788995

PY-IN: Dual language handling in PA Infotypes

Note that your logon language is still Hindi in the system.

Now, when you save this record, the fields ZZVORNA_HI and ZZNACHN_HI will hold
First Name and Last Name in Hindi respectively. This is because you have mapped
these fields for Language HI in V_T799IN_MLFM.
4) Now for the above case, the First Name and Last Name is stored both in English and Hindi languages.
VORNA Kishore
NACHN Kumar
ZZVORNA_HI
ZZNACHN_HI

The personal details will look as follows with English and Hindi logon respectively.

The personal details on Employee Self Service (ESS) will look as follows with English and Hindi logon
respectively.

Page 4 of 10

Note 1788995

PY-IN: Dual language handling in PA Infotypes

Scenario 2: Addresses (Infotype 06) in English and Hindi:

Consider an example where a Company (referred below as you) chooses to maintain few fields (Care of,
Street, Address Line 2 and City) in Address Infotype of employees in English and Hindi.
English is the default language and data is being maintained in that language. With the new solution, the users can
maintain Care of, Street, Address Line 2, and City fields in Hindi as well.

Customer has to follow the below steps to achieve the above requirement:
1) Identify the database table (PA table) where Infotype 06 records are saved. For Infotype 06, it is
PA0006.
2) Identify Standard fields in PA0006 table which stores Care of, Street, Address Line 2 and City.
Care of (Contact Name) - NAME2
Street
- STRAS
Address Line 2
- LOCAT
City
- ORT01

3) Add new customer specific fields (Z-fields) in the Customer Include (CI) of Infotype 06. In this
case, it is CI_P0006. Note that:
New z-fields in CI Include will correspond to the Standard fields
Data type of z-fields must be same as Standard field (here NAME2, STRAS, LOCAT
and ORT01)
New (respective) z-fields will store the Care of, Street, Address Line 2, and City in
Hindi
Page 5 of 10

Note 1788995

PY-IN: Dual language handling in PA Infotypes

In this case we create:

ZZNAME2_HI corresponds to NAME2
ZZSTRAS_HI corresponds to STRAS
ZZLOCAT_HI corresponds to LOCAL
ZZORT01_HI corresponds to ORT01

4) Perform the mapping in table view V_T799IN_MLFM as shown below:

The Original Database Table and Target Database Table must be same
The data type of the Original Database Field and Target Database Field must be same
Language will be HI, as you want to open the saving of fields Care of, Street, Address
Line 2, and City in Hindi
This customizing table is not used to store data, it is just used to perform mapping.

Page 6 of 10

Note 1788995

PY-IN: Dual language handling in PA Infotypes

The following explains how Infotype data maintenance works:

1. Login to the system in English and open Infotype 06 (via transaction code PA30).

2. Login to the system in Hindi and open Infotype 06. Note that this is the first time you are
viewing it with Hindi logon.
The data in fields Care of, Address line 2, Street, and City will come in English, since
it was maintained in English language first. This time the data is being fetched from
NAME2, STRAS, LOCAL, and ORT01. The fields ZZNAME2_HI, ZZSTRAS_HI,
ZZLOCAT_HI, and ZZORT01_HI still do not contain any data.

Page 7 of 10

Note 1788995

PY-IN: Dual language handling in PA Infotypes

3. To maintain data in Hindi language, overwrite the English text with Hindi as shown below:

Note that your logon language is still Hindi in the system.

Now, when you save this record, the fields ZZNAME2_HI, ZZSTRAS_HI, ZZLOCAT_HI,
and ZZORT01_HI will hold Care of, Address line 2, Street, and City in Hindi respectively.
This is because you have mapped these fields for Language HI in V_T799IN_MLFM.
4. Now for the above case, the Care of, Address line 2, Street, and City are stored both in English and
Hindi languages.
NAME2 Rajesh Kumar
STRAS 2nd Cross, 2nd Main
LOCAT Whitefield
ORT01 Bangalore
ZZNAME2_HI
ZZSTRAS_HI 2

,2

ZZLOCAT_HI
ZZORT01_HI

Page 8 of 10

Note 1788995

PY-IN: Dual language handling in PA Infotypes

The address will look as follows with English and Hindi logon respectively.

The address on Employee Self Service (ESS) will look as follows with English and Hindi logon respectively.

Page 9 of 10

Note 1788995

PY-IN: Dual language handling in PA Infotypes

How to use the solution:

1) Decide the Infotype and its fields that you want in dual languages.
2) Find the standard database table (PA table) and its fields, which stores the corresponding data
(of fields identified in point 1).
3) Create customer specific fields (Z-fields) in the Customer Include (CI) structure for the selected
Infotype.
4) Make sure the data type of Standard fields in PA table and that of Z-fields in CI structure are
same.
5) Map the Infotype fields required in dual languages in the table view V_T799IN_MLFM.
6) Specify language as HI if you want to maintain the fields (identified in point 1) in second
language Hindi.

Note the below mentioned points:

1) The solution is not about translation of text from one language to another.
2) It is assumed that default/primary language in your system is English. Hence, any
customizing with Language as EN should not be maintained in V_T799IN_MLFM.
3) Both the Original and the Target Database table should be same in the table view
V_T799IN_MLFM.
4) You do not have to perform any other customization or activation after maintaining customizing
in table view V_T799IN_MLFM.
5) The IMG path for maintaining V_T799IN_MLFM is:
Payroll-> Payroll: India-> Dual Language Handling-> Maintain Dual Language Mapping Fields

6) Data type of Custom Z-fields in CI Structure should be same as the Standard fields in PA table.
7) There are no time constraints for mapping fields in the customizing. Changing the fields settings
after enabling dual languages may lead to inconsistencies.
8) Creating/Editing/Copying/Deleting any data record in any Infotypes in PA30 will have the same
behavior irrespective of logon language.
9) You can save text in Hindi by logging on to the system in English. This behavior remains as-is.
10) One Target Database Field should be mapped to one Standard field only.

Page 10 of 10