Skip to Content
0
Former Member
Jul 30, 2010 at 02:10 AM

SAP Express Document Error: Posting cannot be done

78 Views

Hi Experts,

I have a problem on our QAS system, I have tried to post a lot of documents in transaction MIGO, in creating RFQ through ME41, in Posting Accounting Document in FB50. But all of them failed with the Express Document appearing at the end of the "Document Number Created" message.

Express Documents range from:

I. "MESSAGE_TYPE_X" when creating RFQ of One Time Vendors:

Short text of error message:

Database error changing table ADRC

Long text of error message:

Technical information about the message:

Message class....... "AM"

Number.............. 842

Variable 1.......... "ADRC"

Variable 2.......... " "

Variable 3.......... " "

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

Information on where terminated

Termination occurred in the ABAP program "SAPLSZA0" - in "ADDR_SAVE_INTERN".

The main program was "RSM13000 ".

In the source code you have the termination point in line 553

of the (Include) program "LSZA0U47".

The program "SAPLSZA0" was started in the update system.

II. SAPSQL_ARRAY_INSERT_DUPREC, Post Goods Receipt in MIGO

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 "INSERT_TABLES" "(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.)

III. SAPSQL_ARRAY_INSERT_DUPREC, Posting through FB50

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 "INSERT_TABLES" "(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.)

Please provide direct solution for the system problem. And please tell me also what are the usual causes of these problems (Configuration-wise or ABAP)