TABLE-SCAN fails with inactive index error 995

TABLE-SCAN on a table in a Type II Area fails with Error 995 if the index is inactive 
When the index that the compiler would have normally picked in the FOR EACH statement is inactive, TABLE-SCAN fails with error 995 when the table is in a Type II Area.

 

The TABLE-SCAN Option is used in FOR EACH statements
When the TABLE-SCAN keyword is used, only the record block instead of both record and index blocks should be used.
TABLE-SCAN should return rows without using an index in Type II Areas.
TABLE-SCAN should only use the default index when the table is in a Type I Area, as this feature is limited to Type II objects only

The AVM does an error check for inactive index before it checks for table-scan and type II area instead of ignoring the index check error when running TABLE-SCAN for records in a TYPE II area

Upgrade to OpenEdge 11.7.6.0, OpenEdge 12.3

The TABLE-SCAN keyword when used with a database table stored in a Type II area will no longer throw an error when the index is disabled.

Progress Articles: 

If the TABLE-SCAN option for a query is used, the next query which uses a normal index will get also the table-scan option.   
What is the benefit of using the TABLE-SCAN option?