Problem Note 70970: Incorrect results can be generated with the Lookup Transformation when a column in a source table is renamed
Incorrect results for Lookup transformations can be generated when columns with the same name exist in both source and dimension tables.
The problem can occur when values for columns with the same name are needed in the fact table that is generated by the transformation. You must rename the column in either the source or dimension table to output both values to the fact table. Incorrect results can be generated when you rename the column in the source table. The new column that is written to the fact table contains the value from the dimension table.
A workaround is to rename the column in the dimension table.
This issue has separate hot fixes for different releases of SAS® 9.4.
SAS® 9.4M8 and SAS® 9.4M9
In SAS® 9.4M7, a hot fix was provided to correct the problem by modifying the source code generated to rename the columns in the source and target tables. This change caused errors in some jobs in SAS 9.4M8 and SAS 9.4M9. The errors include:
ERROR: Following columns were not found in the contributing tables: <list of column names>.
or
ERROR: Type mismatch for key variable <variable_name> at line <line_number> column <column_number>.
Other reported issues include:
- missing column names in the KEEP statement in the SAS DATA Step code used to perform lookups
- RENAME statements that list columns that do not exist in the table
- incorrect results
- calculated columns that result in missing values
- code that is generated in SAS® Data Integration Studio differs from code that has been deployed previously
Click the Hot Fix tab in this note to access the relevant hot fix for your release.
Operating System and Release Information
| SAS System | SAS Data Integration Studio | Microsoft® Windows® for x64 | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows 8 Enterprise 32-bit | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows 8 Enterprise x64 | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows 8 Pro 32-bit | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows 8 Pro x64 | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows 8.1 Enterprise 32-bit | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows 8.1 Enterprise x64 | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows 8.1 Pro 32-bit | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows 8.1 Pro x64 | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows 10 | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows 11 | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2008 | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2008 R2 | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2008 for x64 | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2012 Datacenter | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2012 R2 Datacenter | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2012 R2 Std | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2012 Std | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2016 | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2019 | 4.905 | | 9.4 TS1M7 | |
| Microsoft Windows Server 2022 | 4.905 | | 9.4 TS1M7 | |
| Windows 7 Enterprise 32 bit | 4.905 | | 9.4 TS1M7 | |
| Windows 7 Enterprise x64 | 4.905 | | 9.4 TS1M7 | |
| Windows 7 Home Premium 32 bit | 4.905 | | 9.4 TS1M7 | |
| Windows 7 Home Premium x64 | 4.905 | | 9.4 TS1M7 | |
| Windows 7 Professional 32 bit | 4.905 | | 9.4 TS1M7 | |
| Windows 7 Professional x64 | 4.905 | | 9.4 TS1M7 | |
| Windows 7 Ultimate 32 bit | 4.905 | | 9.4 TS1M7 | |
| Windows 7 Ultimate x64 | 4.905 | | 9.4 TS1M7 | |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | high |
| Date Modified: | 2025-11-05 14:48:17 |
| Date Created: | 2024-09-19 13:39:56 |