Transaction XK01 - Creating an International Address Version for a Vendor
Studio 11, Transaction 10.x
Sometimes, Master Data requires the maintenance of addresses in different languages due to the linking of the record to multiple countries (via Company Codes for example). The default options for creating a vendor through Transaction are Non-Batch Input Mode and Without SAP Controls. This method does create an International Version of the address for the vendor in question, but does not allow for repetitive behaviour within the XK01 transaction for it to be recorded and re-used as a mass tool for creation.
The solution is to use Batch Input Mode as this opens up the option to select the language key of the International Version of the address that needs to be created.
1. Open up Winshuttle Transaction and create a new transaction XK01.
2. Select Batch Input Mode.
3. Populate the required fields (Account Group 0001 is the only mandatory field in this example as only the Address screen is the requirement) and tick the Use Central Address Management checkbox located below the Reference fields (this is the key field!).
4. Populate the required fields in the Address screen – Name, Search Term, and Country are the only mandatory fields required for creating a vendor with minimal data.
5. Click the Check Address icon to validate the Address User-added image. This is a crucial step in the recording, because it creates the necessary gap to close the recording if an International Version of the address is not required for the particular vendor. In this example, the full name of the country key will appear next to the Country field.
6. Click on the International Version icon User-added image to open up the popup box Choose International Version. Populate the Address Version field with the desired language key (this configuration is maintained externally, and a list of possible entries and whether they are active or not can be viewed in the table V_TSADV).
7. Click on the green tick to continue on to the next screen. Populate the necessary fields (in this example, the direct Cyrillic translations of the English Name and Search Term were used and the Country was not changed).
As the recording is now complete, it is now possible to create the mapping within Transaction to create the script. However, it is important to note that the screen for each language key can be different and thus creating loops is not as simple for vendors that require various International Versions within the same script (unless the recording and consequently the mapping mirror this behaviour for all keys and screens).
For example, Kanji and Katakana are Japanese languages and therefore share the same screen, but a recording like the above with Cyrillic will give an error if used to input any of these Japanese language keys. The error message from SAP will be that of a missing screen, and these can be further explored through the screen names when mapping in Transaction, or viewing the technical field information via F1 in ECC.