== Why is this an issue?

Internal tables can quickly become a source of performance problems if not accessed correctly, ``++SORTED++`` and ``++HASHED++`` tables should always be accessed with the appropriate key or partial key.


=== Noncompliant code example

[source,abap]
----
READ TABLE it INTO work_area INDEX 1.
----


=== Compliant solution

[source,abap]
----
READ TABLE it INTO work_area WITH KEY color = 'RED'.
----

ifdef::env-github,rspecator-view[]

'''
== Implementation Specification
(visible only on this page)

=== Message

Access table XXX using "WITH TABLE KEY"


endif::env-github,rspecator-view[]
