Solution : https://service.sap.com/sap/support/notes/626408 (SAP Service marketplace login required)
Summary :
Following an SAP system upgrade (R/3, APO, CRM, etc.), issues may arise with using or displaying background variants, often due to extended program interfaces incorporating new functions. This incompatibility stems from variant data stored in a pooled table, which may not align with updated program structures. SAP addresses this via a Variant-Restore tool within the ASU toolbox (Note 623723), preserving variant data in transparent tables during upgrades, thus maintaining usability post-upgrade. Caution is advised against running this tool during ERP 2004 upgrades if sourced from release 4.5B or higher. Customization through transaction SE16 and table VARID ensures specific adaptations are included.
Key words :
r3tr tabu tasuvcatr3tr tabu tasuvsvdr3tr tabu tasuvsvodouble-click, productive run yellow traffic light, previously stored variant data rasuvsho, 'save variant values transparent' button, active green traffic light, application-specific upgrade guides [note 623723], variant-restore tool programs rasuvcat, create downward-compatible programs, schedule manager monitor view, button 'create variant catalog'
Related Notes :
| 775047 | Add. info. on upgrading to SAP Web AS 6.40 SR1 |
| 758375 | ASU: VARID-AEDAT not filled after restore |
| 737696 | Add. info on upgrade to SAP R/3 Enterprise 4.70 Ext. 2 SR1 |
| 733519 | Settlement: No list output for reports RKO7xxxx |
| 689192 | WEC Release 1: General Fixes # 66 |
| 684406 | Additional information on upgrading to SAP SCM 4.1 |
| 661640 | Add. info. on upgrading to SAP Web AS 6.40 |
| 623723 | Upgrade: Application-specific problems |
| 587896 | Add. info on upgrade to SAP R/3 Enterprise Core 4.70 SR1 |
| 484876 | Additional information about upgrading to SAP Web AS 6.20 |
| 390665 | Additional information: Upgrade to 4.6C SR 2 (DB2/400) |
| 326783 | Additional Info: Upgrade to 4.6C SR1 (DB2/400) |
| 202169 | Additional Info: Upgrade to 4.6C - DB2/400 |