cancel
Showing results for 
Search instead for 
Did you mean: 

Outbound delivery does not exist in table

Former Member
0 Kudos

Dear experts, please your help...

The enquiry of the stock overview for a material code in

a plant shows 497 BTO of existences in unrestricted use condition.

But if I try to make a stock transport order, the system indicates 17

BTO of existences.

This gives the impression that the outbound delivery was

deleted. But I can see it in MD04 transaction.

Searching for the document through VL03N transaction code, the

outbound delivery does not exist. And for sure, in the table LIKP.

Please your hints or comments, i will really appreciate it.

Thanks in advice.

Felipe

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Felipe,

Try checking out this Wiki entry: http://wiki.scn.sap.com/wiki/display/ERPMan/Inconsistencies+for+planning+elements+and+display+proble...

The section 'Deleted or Already Completed Sales Order / Delivery' looks relevant.

- Jeff

Former Member
0 Kudos

thank you very much Jeff!

that report has solved the problem.

all the best.

felipe

Answers (2)

Answers (2)

RobynCouch
Contributor
0 Kudos

Hi Felipe

I'm not 100% certain what help you are asking for.  I have a couple of suggestions though.

It sounds like you are running an availability check which is giving an available quantity of 17.  You can use transaction CO09 to look at what documents have reserved the other stock.  There are also buttons in the ME21N transaction that will take you to this information.

After a delivery document has been deleted you will not see any evidence of it's existence in the LIKP and LIPS tables.  The only evidence I have ever been able to find sits in the change history tables which are CDHDR and CDPOS.  I can't remember the object id at this time but I'll look it up and let you know.

Regards

Robyn

Prasoon
Active Contributor
0 Kudos

Hi,

   If the delivery is deleted and still showing in MD04, refer the KBA: 1888035 - Trouble shooting for incorrect entries in transaction code MD04 which offers few reports to correct the issue.

Regards,

AKPT