Sales Orders not in the DB

[Former Member]

Hi,

A sales order is saved, and a sales order number is generated. And then when trying to view this using VA03, an error message is recevied stating "SD document is not in the database or has been archived"

And the SD document is not there in VBAK table as well.

Archiving has not been carried out.

What could be possible reasons for this?

Thank you in advance,

[brittacarols]

There are several possible reasons why a sales order may not be found in the database or the VBAK table, including:

1. Data entry error: It is possible that the sales order was not saved properly due to a data entry error or technical issue during the saving process.
2. System malfunction: A system malfunction or error could have prevented the sales order from being saved correctly, resulting in it not being in the database or VBAK table.
3. Authorization issue: The user attempting to view the sales order may not have the necessary authorization to access it, resulting in an error message being displayed.
4. Deletion: The sales order may have been accidentally or intentionally deleted from the database, resulting in it not being found when attempting to view it.
5. Archiving: Although you mentioned archiving has not been carried out, it is possible that the sales order was archived by mistake or by a background job, causing it to be removed from the database and not available for viewing.

To resolve the issue, you may need to investigate each of these possibilities and take appropriate action based on the root cause of the problem.

[Former Member]

Hi Kanishka,

i guess there might be some update terminate taking place when you are saving the sales order and naturally when you want to see it in VA03 it wont be available. As a check pl go to SM13 where you can see list of update terminations taken place.

Even if archiving has been set it wont applied as soon as the sales order is saved so that possibility can be ruled out.

A sales order once created will be part of VBAK table.

regards

sadhu kishore

[Former Member]

Thank you very much for all the infomation..

I will check on this further..

[Former Member]

solved

[msharpton49]

Hello,

Please share how you were able to solve this situation. We are facing a similar situation post upgrade.

Regards,

Matt Sharpton

[Former Member]

I suppose when you are saving the Sales Order, it is being saved & archieved in background.

It is recxommended to get it debugged with the help of the Abaper, as to where is the root cause of the problem.

Regards,

Rajesh Banka

[jignesh_mehta3]

Dear Friend,

There may be a case where the user might have deleted the Sales Order. Your Basis person can easily trace this.

Also sometimes the problem like this arise where the tables are not updated & number range is generated (skipped)... This can also be explored by your Basis person...

But most probably is seems that end-user might have deleted it by mistake...

Hope this helps

Reward if useful...

Thanks,

Jignesh Mehta

98700 10230

[Former Member]

hi

This problem is besically related to database update

You better to take help from the BASIS people they will be in a possition ,help you to find the which user deleted that order.

[Former Member]

Thank you for the feedback.

But this does not happen for all the sales orders, onlysme sales orders cannot be viwed through VA03.

[Former Member]

it might be giving some dump report with ur ID

check with basis team ppl they will provide you details

[Former Member]

Thanks for the feedback...

if the sales order is deleted, how can it be traced?

[Former Member]

hi

You might be knowing which is the last no you have created

Goto table and from there you will get the list of missing sales orders

But once the SO is deleted or archived we can not display them

If you know the order number you can have a try with tables CDPOS and CDHDR, but I am not sure whether this will be helpful.

Regards

Edited by: WISH on Jul 30, 2008 7:21 AM

[Former Member]

hi,

if this is happening with each n every order u r creating than ask help frm ur Basis people.... i think this might be the problem of database updation.

reg

Deepak