Alternation solution

[Former Member]

Hi Experts,

What is the alternative solution if the inventory transfer error can't be used anymore ? there is an error message this entry already exists. Our implementor said that they have logged a message to SAP support but until present no answer to us.

As a customer, I really dissappointed to this product. It seems that they can't do anything until present. Meanwhile we have searched the note that the similar errors happened and have had the solutions. Most of the solutions are to log a message or contact SAP support. We have sent the backup of corrupted db to our implementor so that they can upload it and have solution asap. We will not able to do it manually. We must work paperless and save a tree.

Where could I send my complain or sue this product ? Is this error not easy to resolve ?

The implementor's support helpdesk said that this issue's priority was set high, but no answer until present.

Be careful to use this product. It will ruin your life.

Andres

[former_member186095 · Accepted solution]

Hi,

I suggest to use good issue and good receipt. Just use one offset account for both document. So, it means that you must replace account code everytime you want to use the document to do an inventory movement.When the solution from SAP delivered, just lock the account code for use. Do not use the good issue or good receipt document numbering and series. Create new one. Lock it after the inventory transfer can be used again.

In addition to other's answer, I also suggest you to check OINM table (warehouse journal). I am afraid it is probably a corrupt data. Comparing the docentry of table OWTR and WTR1 too.

Rgds,

[senthil_m]

Hi,

I can give you the suggestion, But Do it in your Test Data base why because if you do it in a production DB, SAP will not support further and my personal opinion is that donu2019t practicing it in future. This is an ad-hoc solution.

Run the query in SQL query manager

1. Select * from OWTR

Count your Docentry, Note the Result

Run the Query

2. Select * from nnm1 where objectCode=u201967u2019

Please note your next number field result. That should be +1 of your Query 1 (Docentry) result. Say for example if the first query result is 99, next number field result should be 100.

Again run the below query

3. Select * from onnm where objectCode=u201967u2019

Note down your Auto Key Field Value. This also should be equal to the second query result (Next number field value).

If not equal, you have reset the document numbering ie, ONNM and NNM1.

Note the docentry of your inventory transfer table (OWTR). Then add 1 value from your result which you got from the First query. Ex: (Docentry :991=100).

Update this value (100) in these two tables onnm (AutoKey field) and nnm1(Nextnumber field) .

update onnm set autokey=u2019100u2019 where objectCode=u201967u2019

update nnm1 set nextnumber=u2019100u2019 where objectcode=u201967u2019

-

---

Senthil Maruthappan.

Team work Never Fails.

[Former Member]

Hi Andreas........

Try your transaction with new numbering series. But do it and get it confirm in test database. If it work then follow it.

Regards,

Rahul

[Former Member]

HI ANdres ,

We faced the similar issue with most of our client....until u get a response from sap u can try out the following..

Take a backup of your databse...then go to administration......utilities and use the option restore numbering file.....then logout from sap and login again.....hope it works....

*close the thread if the issue is resolved*