topic Re: Insert same primary key to custom table not dump in Application Development and Automation Discussions

Insert same primary key to custom table not dump

former_member660488 — Thu, 07 Apr 2022 09:39:31 GMT

Hi experts,

As I am trying to insert same primary key to a custom table ,there is no dump and the data is normally saved to the custom table,not dump.Why is this happening?

INSERT zhx_ficot015i FROM TABLE gt_tb_di.

The same data exists in gt_tb_di and zhx_ficot015i ,but sy-subrc return 0.

codes:

DATA:gw_ficot015i TYPE zhx_ficot015i,
gt_ficot015i TYPE TABLE OF zhx_ficot015i.

gw_ficot015i-mandt = '500'.
gw_ficot015i-od_type = '02'.
gw_ficot015i-receno = 'F510320220420004'.
gw_ficot015i-itemno = '000001'.
APPEND gw_ficot015i TO gt_ficot015i.

INSERT zhx_ficot015i FROM TABLE gt_ficot015i ACCEPTING DUPLICATE KEYS.
IF SY-SUBRC = 0.

ENDIF.
BREAK-POINT.

Re: Insert same primary key to custom table not dump

Sandra_Rossi — Thu, 07 Apr 2022 14:55:37 GMT

Please look at ABAP Documentation. The consequence of INSERT ... FROM TABLE ... with data which would lead to duplicate keys in the table is:

if you also indicate ACCEPTING DUPLICATE KEYS, you will get SY-SUBRC = 4.
otherwise you get CX_SY_OPEN_SQL_DB. If you don't catch this exception, there will be a short dump.

Re: Insert same primary key to custom table not dump

Sandra_Rossi — Thu, 07 Apr 2022 14:56:21 GMT

If it's another case, check SAP notes or contact SAP support.

Re: Insert same primary key to custom table not dump

Jeansy — Thu, 07 Apr 2022 16:52:25 GMT

For a detail analysis I would change the INSERT ... FROM TABLE to a single INSERT in a LOOP-statement. Just to find out which record is responsible for the dump.

But sandra.rossi is right, you should indeed consider to catch the related exception if you want to stay by this variant using INSERT ... FROM TABLE.

It would be also an option to change it to MODIFY ... FROM TABLE, then there is no issue anymore in case of an existing record in the table with the same key (as it will be just updated in this case).

Kind regards
Jens

Re: Insert same primary key to custom table not dump

former_member660488 — Fri, 08 Apr 2022 01:39:44 GMT

same primary key insert from wa or table not dump.Only this table will show this situation.

indicate ACCEPTING DUPLICATE KEYS , SY-SUBRC still return 0.

Re: Insert same primary key to custom table not dump

keremkoseoglu — Fri, 08 Apr 2022 05:09:42 GMT

If the previous record came from somewhere else (like an integration); it might be the case that one of the columns contains an additional special character which can't be displayed by SAPGUI. Characters like TAB, CR, LF, etc are typical examples.

If that's the case, the system rightly thinks that the old value (containing the rogue character) is different from your clean value.

You might want to inspect the table contents through an external non-SAP tool and see if it shows such a rogue character. Checking string length is also an approach.

Re: Insert same primary key to custom table not dump

jmodaal — Fri, 08 Apr 2022 06:45:05 GMT

Hello,

strange. When showing the database object (in SE11 > Utilities > Database Object > Display), is the primary index ZHX...~0 shown as "Unique" (like usually)?

Re: Insert same primary key to custom table not dump

former_member660488 — Fri, 08 Apr 2022 06:54:40 GMT

Codes：search by primary key have 12 records now.

It should not be the cause of abnormal characters.

SELECT * INTO TABLE @DATA(gt_ficot015i) FROM zhx_ficot015i
WHERE od_type = '02' AND receno = 'F510320220420004'

AND itemno = '000001'.

Re: Insert same primary key to custom table not dump

former_member660488 — Fri, 08 Apr 2022 07:01:52 GMT

Is the index the cause of this problem?

I'm not sure about the indexes

Re: Insert same primary key to custom table not dump

former_member660488 — Fri, 08 Apr 2022 07:08:37 GMT

After checking, I found this problem.

Is it caused by this? What should I do? This table already has a lot of data

Re: Insert same primary key to custom table not dump

jmodaal — Fri, 08 Apr 2022 07:20:02 GMT

Hello,

so it seems the missing primary index causes the problem, that you were able to insert multiple rows with same primary key fields. Don't know how this could happen (except deleting it on database level). With the database utility (Utilities > Database Object > Database Utility) you can try to fix this by choosing "Persist data" and clicking "Activate and adjust database". In front of this duplicates of the primary key fields should be deleted, otherwise I guess the database utility will fail. And I would think about extracting / back up the data in front of this (by using a transport request or R3trans or a self-developed ABAP).

Re: Insert same primary key to custom table not dump

former_member660488 — Fri, 08 Apr 2022 07:36:44 GMT

I have delete the duplicates records,then tried clicking "Activate and adjust database" ,Promting success.

but the primary index strill missing.

Re: Insert same primary key to custom table not dump

jmodaal — Fri, 08 Apr 2022 07:55:56 GMT

Hello,

even after activating the table again in SE11?

Then you could try to make one of the primary key fields longer, activate it (my expectation would be that the primary index will be created again) and after it shorten the primary key field again to its original length and activate again.

Re: Insert same primary key to custom table not dump

former_member660488 — Fri, 08 Apr 2022 08:34:27 GMT

I try change a primary key longer and add a primary key then clicking "Activate and adjust database",

cannot activate

Re: Insert same primary key to custom table not dump

jmodaal — Fri, 08 Apr 2022 09:04:04 GMT

Encouple the primary key fields from any value tables by using data elements CHAR2, CHAR16, CHAR6 and try it again. Then change it back to the currently used data elements and activate again.

Re: Insert same primary key to custom table not dump

former_member660488 — Fri, 08 Apr 2022 09:25:42 GMT

I just checked the z table, Actually the duplicates records cannot delete by se16n or abap code

Re: Insert same primary key to custom table not dump

former_member660488 — Fri, 08 Apr 2022 09:34:40 GMT

I have been confirmed that there is no duplicate data. The length of the primary key has been adjusted to cahr16, but it cannot be activated

Re: Insert same primary key to custom table not dump

jmodaal — Fri, 08 Apr 2022 09:56:24 GMT

Hello,

column "Data element" still shows your own data elements. Did you try to change this to CHAR16 to get rid off the search help?

Re: Insert same primary key to custom table not dump

former_member660488 — Fri, 08 Apr 2022 10:25:29 GMT

Additional error fields that exist and I added a field bukrs as the primary key. Now I can't cancel it

Re: Insert same primary key to custom table not dump

jmodaal — Fri, 08 Apr 2022 11:16:13 GMT

I have the impression that the action is meanwhile somewhat... chaotic. Still using the data elements bound to search helps? My idea was to replace these data elements by simple CHAR... data elements for getting rid of most dependencies to finally enable the activation of the database table with a valid, unique primary key.