topic Problem in read statement in Application Development and Automation Discussions

Problem in read statement

Former Member — Fri, 13 Nov 2009 07:58:06 GMT

Hello Expert,

I am geting problem in read statement.

I am looping internal table Gt-ZSD0122t with vbeln and ponr and inside i am reading the one more internal table

GT_LIPS with GT_ZSD0122t-VBELN and GT_ZSD0122t-POSNR.

I have same value for vbeln and posnr in the 2 internal table than also sy-subrc i am getting 8.

So can u please tell me what is problem.

LOOP AT GT_ZSD0122T.

READ TABLE GT_LIPS INTO WA_LIPS WITH KEY VBELV = GT_ZSD0122T-VBELN

POSNV = GT_ZSD0122T-POSNR

BINARY SEARCH.

IF SY-SUBRC EQ 0.

MOVE WA_LIPS-VBELN TO GT_ZSD0122T-VBELN_D.

CLEAR:WA_LIPS-VBELN.

MODIFY GT_ZSD0122T.

ENDIF.

ENDLOOP.

what is the problem if sy-subrc equal to 8?

Re: Problem in read statement

Former Member — Fri, 13 Nov 2009 08:01:18 GMT

Hello,

Before the loop sort the internal table and check


sort gt_lips by vbelv posnv.   "add this

LOOP AT GT_ZSD0122T.
READ TABLE GT_LIPS INTO WA_LIPS WITH KEY VBELV = GT_ZSD0122T-VBELN
POSNV = GT_ZSD0122T-POSNR
BINARY SEARCH.
IF SY-SUBRC EQ 0.
MOVE WA_LIPS-VBELN TO GT_ZSD0122T-VBELN_D.
CLEAR:WA_LIPS-VBELN.
MODIFY GT_ZSD0122T.
ENDIF.
ENDLOOP.

Vikranth

Re: Problem in read statement

Former Member — Fri, 13 Nov 2009 08:03:42 GMT

Hi ,

First u sort the internal table GT_LIPS based on vbelv and posnv .

then u can perform the binary search. because for binary serch , u should sort the table based on key field (ie u r using in read statement)

Re: Problem in read statement

Former Member — Fri, 13 Nov 2009 08:43:42 GMT

Hi shridarudupi ,

Before using the BINARY SEARCH option in read statement you should sort the internal.

This is the primary requirement for using Binary Search.

Re: Problem in read statement

kesavadas_thekkillath — Fri, 13 Nov 2009 08:51:40 GMT

Always sort the internal table before using Binary search

SOR GT_ZSD0122T VBELV POSNV ASCENDING.

Re: Problem in read statement

Former Member — Sun, 15 Nov 2009 00:00:07 GMT

thanks...problem solved