Problems found during the EXPORT to specified keyin table.

[Former Member]

Hi

I am getting this error in sending iDOC system( We have iDOC-XI-iDOC Scenario.) I tried to reregister the queues but still nothing is passing thru XI.

Thanks,

Manish

[Former Member · Accepted solution]

Hi Manish,

Could you specify exactly as to what error you are getting.

cheers,

Prashanth

[Former Member · Accepted solution]

Acutally I am getting this DUMP in ST22.

<i><b>ShrtText |

Problems found during the EXPORT to specified key in table.

-

---

-

---

What happened?

Error in ABAP application program.

The current ABAP program "CL_XMS_PERSIST================CP" had to be

terminated because one of the

statements could not be executed.

This is probably due to an error in the ABAP program.

-

---

-

---

What can you do?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

is especially useful if you want to keep a particular message.

-

---

-

---

Error analysis

The table " " does not contain any data records with the specified key.

The system called the internal SAP database interface because it

expected to find such a key.

-

---

-

---

How to correct the error

Probably the only way to eliminate the error is to correct the program.

-

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

"EXPORT_TABLE_UPDATE_CONFLICT" C

"CL_XMS_PERSIST================CP" or "CL_XMS_PERSIST================CM00W"

"INSERT_MSG_ALL"

If you cannot solve the problem yourself and you wish to send

an error message to SAP, include the following documents:

1. A printout of the problem description (short dump)

To obtain this, select in the current display "System->List->

Save->Local File (unconverted)".

2. A suitable printout of the system log

To obtain this, call the system log through transaction SM21.

Limit the time interval to 10 minutes before and 5 minutes

after the short dump. In the display, then select the function

"System->List->Save->Local File (unconverted)".

3. If the programs are your own programs or modified SAP programs,

supply the source code.

To do this, select the Editor function "Further Utilities->

Upload/Download->Download".

4. Details regarding the conditions under which the error occurred

or which actions and input led to the error.

-

---

-

---

Information on where terminated

The termination occurred in the ABAP program "CL_XMS_PERSIST================CP"

in "INSERT_MSG_ALL".

The main program was "SAPMSSY1 ".

The termination occurred in line 302 of the source code of the (Include)

program "CL_XMS_PERSIST================CM00W"

of the source code of program "CL_XMS_PERSIST================CM00W" (when

calling the editor 3020).

-

---

-

---

Source Code Extract

-

---

Line

SourceCde

-

---

272	IF lv_switch_mode = 2.
273	IF export_to_db_optimized = co_true.
274	CALL FUNCTION 'SXMB_EXPORT_TO_DB'
275	EXPORTING
276	iv_kind = 'P'
277	it_prop = lt_prop
278	iv_switch_mode = lv_switch_mode
279	iv_msgguid = clustkey-msgguid
280	iv_pid = clustkey-pid
281	iv_vers = clustkey-vers.
282	ELSE.
283	EXPORT lt_prop FROM lt_prop
284	TO DATABASE sxmsclup2(is) FROM wa_clup ID clustkey.
285	ENDIF.
286	ELSE.
287	IF export_to_db_optimized = co_true.
288	CALL FUNCTION 'SXMB_EXPORT_TO_DB'
289	EXPORTING
290	iv_kind = 'P'
291	it_prop = lt_prop
292	iv_switch_mode = lv_switch_mode
293	iv_msgguid = clustkey-msgguid
294	iv_pid = clustkey-pid
295	iv_vers = clustkey-vers.
296	ELSE.
297	EXPORT lt_prop FROM lt_prop
298	TO DATABASE sxmsclup(is) FROM wa_clup ID clustkey.
299	ENDIF.
300	ENDIF.
301
>>>>>	IF sy-subrc <> 0. "#EC *
303	m_syserr_raise 'PERSIST' 'MSGGUID_EXISTING'
304	clustkey-msgguid clustkey-pid
305	clustkey-vers ''.
306	lv_p1 = clustkey-msgguid.
307	lv_p2 = clustkey-pid.
308	lv_p3 = clustkey-vers.
309
310	RAISE EXCEPTION TYPE cx_xms_syserr_persist
311	EXPORTING id = cx_xms_syserr_persist=>co_id_msgvers_existing
312	p1 = lv_p1
313	p2 = lv_p2
314	p3 = lv_p3.
315
316	ENDIF.
317
318
319
320	table SXMSPRES (resources)
321	table SXMSPXRES (X-resources)

-

---

-

---

Internal notes

The termination occurred in the function "expOutDb" of the SAP

Basis System, specifically in line 3748 of the module

"//bas/640_REL/src/krn/runt/abexpo.c#8".

The internal operation just processed is "cmpr".

The internal session was started at 20060724051049.

Internal call code.........: " "

Key..................: " "

It is very likely that a constellation similar to the following applies:

Process 1: Process 2:

UPDATE x. ==> NOT_FOUND

UPDATE x. ==> NOT_FOUND

INSERT x. ==> ok

INSERT x. ==> DUPLICATE KEY

DELETE x. ==> ok

UPDATE x. ==> NOT FOUND

+ DUMP

-

---

-

---

Active Calls in SAP Kernel

-

---

Lines of C Stack in Kernel (Structure Differs on Each Platform)

-

---

[0] DoStack2 ( 0x105a4f7c0, 0x0, 0x2d1b000, 0x100000000, 0x1, 0x0 ), at 0x100471a60

[1] CTrcStack2 ( 0x105a4f7c0, 0x0, 0x100000000, 0x2d1ac00, 0x2, 0x102d1ada4 ), at 0x100471610

[2] __1cQrabax_CStackSave6F_v_ ( 0x10303b400, 0x303b400, 0x103874d10, 0x101fcfce8, 0x100000000, 0x

[3] ab_rabax ( 0x1, 0x2d1ac00, 0x0, 0x100000000, 0x3873800, 0x100000000 ), at 0x100a7fa04

[4] __1cIexpOutDb6FppCpLLInJEXPO_MODE__i_ ( 0x2, 0xe82, 0xffffffffffffffff, 0x101f97a90, 0x2, 0x38

[5] __1cTwrite_data_compress6FkpnICONNE_WR_C_i_ ( 0xffffffff7fffb038, 0x1070, 0x1000, 0x10095fa9c,

[6] __1cMab_connwrite6FIIpHIpFp0pIppnHAB_DATA_ppv_ipFppCpLLInJEXPO_MODE__i_i_ ( 0x0, 0x4, 0x10302a

[7] __1cLexpo_export6F_v_ ( 0x0, 0x960000, 0x95f800, 0x0, 0x103847980, 0x1 ), at 0x10095aa20

[8] __1cIab_jexpo6F_v_ ( 0x0, 0x5b52800, 0xd0, 0x100000000, 0x1, 0x0 ), at 0x100952df4

[9] __1cIab_extri6F_i_ ( 0x100000000, 0x5a37800, 0x2f0, 0x1, 0x0, 0x5e ), at 0x10068ccf8

-

---

</b></i>

[moorthy · Accepted solution]

HI,

I think the error is because of some parsing problems.

and the dump is from standard SAP Program.

Check the xml which calls Idoc adapter in XI ?

Check is this xml(mapped) is a valid xml ? check any special chars etc

Related SAP note -768415,916280 ( this is not help you directly )

Hope this helps,

Regards,

moorthy

[Former Member · Accepted solution]

Actually the issue was XID database got full , so XI stopped routing, now DBA has added some sapce to XI database and XI is routing messages

[Former Member]

Hi Manish,

Please take a look at this blog..

/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get

cheers,

Prashanth

P.S : Please mark all helpful answers