cancel
Showing results for 
Search instead for 
Did you mean: 

deposit error message

Former Member
0 Kudos

An error occurred when we adding a check in DEPOSIT in SAP-B1.

"This entry already exist in the following tables 'Deposit' (ODPS) (ODBC -2035) [Message 131-183]u201D

any suggestions on the resolution of this

thanks.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi........

What is your B1 Version and PL?

This type of error generally comes if DocEntry is beings repeated. So you must restore Numbering Series.

Try this too....

Go to Help in Menu Bar> Support Desk> Restore--> Restore Numbering File........

Run this and then try........

Hope this would solve your issue............................

Regards,

Rahul

Former Member
0 Kudos

Hi

afternoon the version is sap b1 2007a (8.00.181) sp:00 pl:47

what would be the effect of this on the numbering series of the other documents lets say ar invoice and others as well?

the only document numbering series with problem is the deposit module wherein the serie number which was posted is still being used by the system as the next number series for another deposit to be made.

thanks in advance.

Former Member
0 Kudos

Hi.....

If you have doubt then do this.

Take a Back up restore it as Demo and Retore No. series as i suggetsed.

If it works proper then deploy it in Live DB.......

Regards,

Rahul

Former Member
0 Kudos

hi

thank you for the assistance.

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

What is your B1 version and PL?

This is usually caused by a bug. First make sure nobody else try to add the same check.

Thank,

Gordon

Former Member
0 Kudos

Hi

its sap b1 2007a (8.00.181) sp:00 pl:47

we have posted a journal entry for deposit number 11354 and this is reflected as reference entry for the journalize transaction when we go to journal entry sub-module

when we make another deposit at the deposit module it still shows that the next number should be 11354 when this number has already been used and in fact posted.

any additional work around this error message

thanks in advance