Order Transferred but Invoice Not Created

(0) Share

Report

Posted on by Jim Lines

Hello,
I've got a strange situation where an order was transferred to an invoice (according to the user) and there was no invoice created. Orders are created in CRM and pushed to GP through Scribe. The Order itself in GP looks fine. There are two line items both are for the same inventory item. The shipping process is typical - allocate/fulfill and transfer to invoice. The order is in history and when I drill down, I can see that each items shows the correct "previously invoiced" quantity. However, the invoice is no where to be found. I've queried by master number, checked inventory transactions, queried all relevant SOP tables (SOP10100, SOP10200, SOP30200, SOP30300) to no avail. We run Rockton Auditor on everything in SOP and I don't even show that the invoice was created. I also ran a reconcile and checklinks on the Work tables. Has anyone ever seen this? At this point, it's probably just as easy to enter an invoice, but this is pretty crazy in my opinion.

Thanks in advance!

JIM

*This post is locked for comments

All responses (7)

Answers (0)

Sort by

Mahmoud Saadi 32,738 on at

Like (0)

Report
Copy link

Link copied!

Hello Jim

I am always fascinated by the various weird cases occurring in your Dynamics GP environment. I am not here to propose an answer since it would not be an easy guess. I believe you need to get prepared from some SQL profiling activity. It will reveal the real truth beyond what's going on

Get a small order as your testing sample, and turn on the SQL profiler, make the trace limited by a specific user to get an efficient and effective result ... and then transfer the order into an invoice.

Keep us posted ;)
Heather Roggeveen 9,150 on at

Like (0)

Report
Copy link

Link copied!

Hi Jim

Can you see any GL postings associated with the missing invoice - i.e. if the GL side hasn't happened, reversing the "previously invoiced" quantity etc may be the best and then transfer the order to invoice again.

Cheers

Heather
Jim Lines 4 on at

Like (0)

Report
Copy link

Link copied!

Heather,

Thanks for your replay and sorry for the late response. I check everything on this one from start to finish. Nothing.... I tweaked my Auditor settings and should be able to find out what's going on if this happens again.

Thanks.

Jim
Jim Lines 4 on at

Like (0)

Report
Copy link

Link copied!

Mahmoud,

As always, thanks for your response and info. If I have a chance I'll try to recreate this and see if I can figure out what happened using the trace. In the meantime, other cases have come up and this has been pushed to the back burner.

Have a great day!

Jim
BrennerKlenzman 65 on at

Like (0)

Report
Copy link

Link copied!

Hi Jim-

Is the SOP Invoice Doc Type set up to allow Deletions? If so, my first suspect would be that the document was deleted and Auditor did not track that for some reason. SOP does not move the order to history until it creates the invoice, so it would be unlikely that it managed to move the order to history and yet NOT create the invoice. On top of that, it checks that the new document was created before it deletes the source document.

Regards,

Brenner ;-) (hi Jim!)
Jim Lines 4 on at

Like (0)

Report
Copy link

Link copied!

Hey Brenner (my old friend)!

I appreciate the explanation of the hand off from Order to Invoice as I was not fully aware of the process.

I checked the SOP setup and none of the docs types allow for deletion. Also, I did turn on for the appropriate actions it was not capturing at the time. At this point, I'm 99% sure it was user related and not worth investigating any further. But you can bet next time this won't be such a "mystery!" LOL.

Thanks to everyone for your input!

Jim
Suggested answer

Redbeard 12,931 on at

Like (0)

Report
Copy link

Link copied!

Jim,

I have run into similar problems before. From time to time, GP only gets part of a transaction done. This can manifest as having the same transaction, in whole or in part, in both the work and history tables. It can also manifest as the original transaction being removed from work tables and not being moved to the history table. I would like to take a look at your query language used for researching the tables.

I would suggest running independent queries on the header and line tables to ensure part of the transaction was not moved over, which is another behavior I've bumped into. You won't see line or header records in your query results if you use an inner join and records are missing from one of the tables. Once you are sure there are no remnants of the transaction (invoice/order) in either the work or history tables, then you can create the invoice manually as you suggested.