In Teradata this is completely different: it is about ordering the rows by the partitioning column(s) within the same storage. The seeking will avoid rows above and below the range desired based on this order. It has nothing to do with the Oracle 'partition pruning' mechanism, which will not scan the segments that are not needed.

You may re-read the Teradata documentation. It's not so bad iafter all... ;-)