Description

'Invalid Column Name' error appears when trying to go back to the Run screen from the Mapper.

Cause

When the Identify Disabled Fields button is used within GUI Scripting, it creates a line that defaults to an SAP to Excel mapping type, but it does not include a column for the mapping in the Value field.

Applies to

Transaction 10.X

Solution

The Identify Disabled Fields button on the pop-up below, which appears after you select GUI Scripting, should be used only when you need to identify greyed out fields. Otherwise, ignore the pop-up and navigate to the screen as you normally would without clicking on the pop-up. When you need Transaction to identify a field that is not otherwise picked up, click the Identify Disabled Fields pop-up to turn it on. After the field has been identified, turn the Identify Disabled Fields button off so that you only capture what is needed.



In your mapping, a line will be automatically created that maps SAP to an Excel column, but it will not identify a column. If you want to bring that field into SAP, identify a column in the Value field. If it is only being used to identify the field during the script, you can disable the line that was automatically created.

If you do not see any mapped fields that are missing a column value in your mapping but you are still getting this error, please check your Filters to make sure that Hide Read from SAP Fields has not been selected. After this Filter has been disabled, please check the mapped columns again for any missing values and either add a column value or disable that line.