Error during KEPM in COPA

[Former Member]

Dear Experts,

I was trying to do a sales data copy in KEPM and the following error message appeared.

Runtime Errors MESSAGE_TYPE_X

Date and Time 11.02.2011 14:48:57

-

---

-

---

Short text

The current application triggered a termination with a short dump.

-

---

-

---

What happened?

The current application program detected a situation which really

should not occur. Therefore, a termination with a short dump was

triggered on purpose by the key word MESSAGE (type X).

-

---

-

---

What can you do?

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system

administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also

keep them for a long time.

-

---

-

---

Error analysis

Short text of error message:

RFC_ERROR 3 RFC error when sending logon data.

Long text of error message:

Technical information about the message:

Message class....... "KE"

Number.............. 628

Variable 1.......... "RFC_ERROR"

Variable 2.......... 3

Variable 3.......... "RFC error when sending logon data."

Variable 4.......... " "

-

---

-

---

How to correct the error

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

-

If the error occures in a non-modified SAP program, you may be able to

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the following

keywords:

"MESSAGE_TYPE_X" " "

"RK2A1014_POST" or "RKEVRK2A_POST_COMMIT__FIX"

"INSERT_CE4_FLUSH_BUFFERS"

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File

(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

-

---

Does anyone know what went wrong?

Regards,

Abraham

[waman_shirwaicar]

Hi,

The above reported error can normally be avoided by the following notes:

421653 Termination with error message KE628, RFC_ERROR

19030 SAPSQL_ARRAY_INSERT_DUPREC in table CE4xxxx

Please check the current number level of tables CE4XXXX (XXXX = your operating concern) and CE4XXXX_ACCT according

to note 19030 and compare to the number range status of object COPA_OBJ in transaction SNRO.

Please follow the steps outlined in the note.

This has helped in some cases as this is used to avoid inconsistencies in the number ranges for the CE4 tables.

When you turn on the buffering for COPA_OBJ in transaction SNRO the dump should hopefully no longer occur.

The default value is 100 numbers in the buffer.

If this does not help then please increase the number of waiting dialog work processes (profile parameter rdisp/rfc_min_wait_dia_wp) from current value 1 (that is the system default value) to new value 15.

Furthermore you should also increase the buffer of number range object COPA_OBJ from current value '100' to '500' (using transaction SNRO) but only in case that changing the value for rdisp/rfc_min_wait_dia_wp hasn't solved the problem so far.

regards

Waman

[Former Member]

Thanks Waman for replying.

I did what you suggested.

First, I added this line "rdisp/rfc_min_wait_dia_wp = 15" in the Instance Profile (it wasn't there earlier).

It didn't work, then I increased the COPA_OBJ number range object value to 500 from 100, but still the same it didn't work.

What else could I try?

regards,

Abraham