topic Re: UNIQUE KEY addition difference in Application Development and Automation Discussions

UNIQUE KEY addition difference

minchevm — Wed, 27 Jun 2018 17:15:37 GMT

Hello SAP comunity,

I have 2 SAP systems - one version 702, one 750.

Both are interpreting the statement bellow differently. 702 is creating the unique key for SORTED and HASHED tables correctly but not 750 (you could check that in the debugger).

I am receiving short-dump because of this. Any idea how I may resolve the problem in 750?

DATA: lt_test LIKE HASHED TABLE OF t000 WITH UNIQUE KEY mtext.

2018-06-27-20-14-23-display-table-key-for-lt-test.jpg

Re: UNIQUE KEY addition difference

AlexFrank — Wed, 27 Jun 2018 21:00:07 GMT

Hello,

You probably want to use TYPE instead of LIKE since you're referencing a dictionary object. In ABAP OO, you'll get an error if you use LIKE like this.

I doubt that the short dump is related to the "Table index not up-to-date" warning. If you input data into your lt_test variable, the warning should vanish. Can you add the short dump to your question?

Re: UNIQUE KEY addition difference

minchevm — Thu, 28 Jun 2018 07:21:45 GMT

The problem is resolved now. Thank you for the efforts.

Re: UNIQUE KEY addition difference

minchevm — Wed, 13 Mar 2019 12:31:58 GMT

Reference for those that needed the answer - it as a dynamic internal table created from MDG API. The static definition and the dynamic definition via the API differed so I simply had to create it via one of the API methods.