If you configure the session mode to ANSI, then the compare on character based strings will be case sensitive.  Teradata is a none case sensitive database but the comparing of strings will take case into consideration when mode is ansi.  We don't use the CASESPECIFIC or NOT CASESPECIFIC keywords in our extraction and instead consider teradata as not case sensitive.

  We need to adjust the connections isCaseSensitive() return value to take into consideration the TMODE setting.  When you right click on the following example and choose the "edit table data" action, the extraction should find the object in ANSI and TERADATA modes.

CREATE MULTISET TABLE <database>zTesT2, NO FALLBACK, NO BEFORE JOURNAL, NO AFTER JOURNAL, CHECKSUM = DEFAULT, DEFAULT MERGEBLOCKRATIO (col2 VARCHAR(25) CHARACTER SET LATIN CASESPECIFIC) PRIMARY INDEX (col2)