Needed Help: SAP User cannot Post in any of the transactions

Question

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)

Answer 1

Hi Experts,
I already investigated this in the system and this issue still occurs I already changed the current number in transaction code OMBT, still error occurs in Posting any Account Documents. When I change the current number manually, then post a document in MIGO, the document number will be displayed in the status bar. But once you tried any function/push any button, an express document will be displayed with the error DUPREC.
I checked in OMBT the current number range and it's incrementing to 10 example if last current doc number is 5000000510, the new current doc number will be 5000000520.
Do we have any confoguration that will correct this increment on the number range interval for Accounting Documents? Curerntly only Accounting Documents cannot post, other than these documents like Sales Order, PO, PR, etc. they can be created.
There are no changes in the user exits affecting the transaction as it was running smoothly last month.
Please help. Thanks a lot!