Application Development and Automation 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: 
Read only

Read statement with repeated key field

Former Member
0 Likes
410

Hi Experts ,

We are in the process of UCCHECK in an upgrade program and come across an issue with read statement using repeated key fields which is not allowed in a unicode compatable environment.

READ TABLE it_vbpa WITH KEY

vbeln = l_vbeln

parvw = '0'

parvw = 'ZN'.

I checked this in 4.6c environment and observed that the Read statement uses the last key value for reading and doesnt consider other values even if the last value is not present in the table .

I want to know if I can use only that last value for read statement ? If so, what was the use of the repeated key fields in a read statement?

Thanks and Regards

Sanu

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
369

Hi,

Your main aim in a upgrade would be to successfully replicate the 4.6x functionalities in the ECC 6 version with the unicode checks. So it would be a safe option to only consider the last key condition. I dont have access to a 4.6C environment. May be it was a mistake corrected by SAP in the new version.

Vikranth

Hi Experts ,

We are in the process of UCCHECK in an upgrade program and come across an issue with read statement using repeated key fields which is not allowed in a unicode compatable environment.

READ TABLE it_vbpa WITH KEY

vbeln = l_vbeln

parvw = '0'

parvw = 'ZN'.

I checked this in 4.6c environment and observed that the Read statement uses the last key value for reading and doesnt consider other values even if the last value is not present in the table .

I want to know if I can use only that last value for read statement ? If so, what was the use of the repeated key fields in a read statement?

Thanks and Regards

Sanu

1 REPLY 1
Read only

Former Member
0 Likes
370

Hi,

Your main aim in a upgrade would be to successfully replicate the 4.6x functionalities in the ECC 6 version with the unicode checks. So it would be a safe option to only consider the last key condition. I dont have access to a 4.6C environment. May be it was a mistake corrected by SAP in the new version.

Vikranth