Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Duplicate or overlapping KEY specifications now not allowed in READ

Former Member
0 Kudos
702

Hi ,

I am in an upgrade project. I am getting this error.

ASSIGN X_ISBN_INPUT(C_INDEX) TO <X_FS>.

CONCATENATE 'ISBN(' C_INDEX ')' INTO X_COMPONENT.

<b> READ TABLE ZZ_G_ITAB_ISBN WITH

KEY (X_COMPONENT) = <X_FS>.</b>

which says <b>Duplicate or overlapping KEY specifications now not allowed in READ</b>

Can anyone tell me what the solution is?

Helpful answers will be rewarded.

Thanks

kiran

1 REPLY 1

suresh_datti
Active Contributor
0 Kudos
200

pl take a look at OSS Note #367676 & do a find on 'DYN_KEY_DUPLICATE '.

this ia nextarct from the note:

"1. READ TABLE itab ... WITH KEY k1 = v1 ... kn = vn

The system now checks, during the syntax check, whether the key values can be converted into the component type. To date this only generated the warning TRMSG: READ 014 or the runtime error MOVE_NOT_SUPPORTED. This conversion check is also effective with the newer variant READ ... WITH TABLE KEY .... In addition, the system now generates a syntax error instead of a syntax warning with duplicate and overlapping key information. Previously, the last key information was used for dynamic information; now the runtime error DYN_KEY_DUPLICATE is deleted."

~Suresh