cancel
Showing results for 
Search instead for 
Did you mean: 

Class type batch

Former Member
0 Kudos

Hi experts

If I create a material with class type batch and assign a class there is a short dump after saving and the class is not saved.

This problem exists only by class type batch. It doesn't matter if there is a characteristic description or not.

Can anybody help me?

Thanks

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

I think for such issues its better to sit with your ABAP person and debugg the transaction.

Regards,

Indranil

JL23
Active Contributor
0 Kudos

you have to read the first 5 pages of the short dump in ST22, it tells you more about the reason why it dumped and gives you recommendations what to do.

Former Member
0 Kudos

thanks

I've already read the dump. But it doesn't help me to find out the problem.

JL23
Active Contributor
0 Kudos

how can you expect us to help you if you dont tell what the dump says?

what is the name of the runtime error?

what does the section error analysis say?

Former Member
0 Kudos

The name of the runtime error is

SAPSQL_ARRAY_INSERT_DUPREC

The error analyses says

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in

procedure "PFLEGEN_ALL_TABS" "(FORM)", nor was it propagated by a RAISING

clause.

Since the caller of the procedure could not have anticipated that the

exception would occur, the current program is terminated.

The reason for the exception is:

If you use an ABAP/4 Open SQL array insert to insert a record in

the database and that record already exists with the same key,

this results in a termination.

(With an ABAP/4 Open SQL single record insert in the same error

situation, processing does not terminate, but SY-SUBRC is set to 4.)

JL23
Active Contributor
0 Kudos

SAPSQL_ARRAY_INSERT_DUPREC

means that there is already an entry with the same key in your database tables, hence you cannot add it.

Such error usually comes up if a number range was reset

so SAP determines the next number from this reset number range and for this number already a record exists.