Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BF (Application Component) Basic Functions⤷
VS (Package) Application development R/3 sales master data 
Attribute
| Message class |  |
F2 | |
| Short Description |  |
Master Data Maintenance: Customer, Vendor | |
| Message Number |  |
771 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20131127 |
Message Text
Help Document
Diagnosis
Analyzing the address management tables resulted in table TSAV containing entries and being active.
This way you can enter and save international address versions in the master data transactions for customers, vendors, and banks.
System Response
All international address versions are converted to the new central address management in Release 4.5.
The previous table for address version keys was a non-client-specific Customizing table. As from Release 4.5, SAP delivers predefined version keys in a category E table (with customer namespace).
So that the assignment of the previous keys to the new keys is known for the data conversion in XPRA, you must maintain the corresponding entries in the TSAVX assignment table BEFORE the upgrade.
If you start preliminary conversion of the address data as stated in OSS note 97032, then you must maintain the assignment before starting the preliminary conversion.
If you do not maintain the assignment, you cannot convert any address versions.
Procedure
Maintain table TSAVX using transaction SE16: Table TSAVX, F8 = Execute, select entries in the list and choose Table entry -> Change.
There is then an authorization check for object S_TABU_DIS, activity "02" = Change.
Enter the appropriate new key for each "old key".
The following new keys have been predefined by SAP:
K Kanji
N Katakana
R Cyrillic
H Hangul (Korean)
I International
Additional keys may be defined by SAP in later releases.
You can display the old keys using transaction SADV. The texts for the keys in TSAV are saved in text table TSAVT.
If one of your keys is not contained in those predefined by SAP, assign one of the values 1,2,...9 (customer namespace) as the new key instead.
When you assign a key of the SAP namespace (A...Z) as new key, make sure that SAP delivers the key with the same meaning (see above).
Notes
The JOB_RSCNVADR phase of the upgrade preparations does not need to be repeated if the existing error message is issued.
The error message is issued irrespective of whether the recommended measures have already been carried out. It is simply intended to remind the user of the measures described.
Procedure for System Administration
History
| Last changed on/by | |
20131127 | SAP |
| SAP Release Created in |
