You cannot refer an input port for a Lookup SQL override.
When the session initializes, it creates the SQL query and caches it. When caching the query, there is no way to predict the data for the port when it reaches the Lookup.
In the Lookup Transformation, if any database column has to be compared with the Input port, then you will have to specify the column as conditions in the Condition tab. You should not include the Input port in the SQL override query in the Lookup transformation.
If you equate the Lookup port with an Input port in the SQL override, then the Invalid identifier error is displayed in the status bar.
What can we do to improve this information (2000 or fewer characters)