We have come across some scenarios where it was not possible to complete purchase invoicing, for example:
It may happen that if AOS gets stopped suddenly or the client loses connection with the AOS, some records stay in specific tables that causes these kind of situations. In other cases we or Partners could not find repro steps to get those scenarios.
I found a list of the SQL tables where the 'pending' record may exist. If the record is found in any of the following tables, the recommendation is to remove it when you have no users accessing AOS (and take normal precautions first of backing up the data). Also test the procedures in a test/development environment before applying it to a live enviroment. Then, check to see if you are able to properly invoice update the PO.
PurchParmTablePurchParmLinePurchParmSubTablePurchParmSubLinePurchParmUpdateVendInvoiceInfoTableVendInvoiceInfoLineVendInvoiceInfoSubTableVendInvoiceInfoSubLine
Of course, you can also delete these records going through Forms, these are the ones I used (ensure no users besides you are working in the application):1. Firstly checking PurchParm tables when looking History forms (Account Payable/ Inquiries/ History/ Purchase orders), and delete those records where the status is "Waiting". 2. The next step is to check VendInvoiceInfo tables where you found the wrong records, You can access those records in the list page: Accounts payable module > Places > Pending Purchase Order Invoices. Here you can delete it as well. Note: pending invoice of your case will be in this list page.
Hope it's helpful
Kind regards
Marialecia Guada
Dynamics AX SCM Technical Lead
Marialecia ,
Any idea why the updates to the listed tables were not part of a transaction (ttsBegin) so the updates to them could be rolled back?
Bijan Gofranian,
AKA KK
Hi! The point is that the application understands that you want to keep that "pending invoice" to process it later. In other cases, Partners nor we have found repro steps to generate the issue.
Hi Marialecia.
I found myself in this situation several times and since we have active Budget Control, I have also cleaned BudgetSource.
Trying to delete the VendInvoiceInfoTable, with budget control active, we received an sql stored procedure error in budget validation (it happens also in the particular invoice will be posted on MainAccount that are not subject to budget limit).
Hi,
I'm from the AX Product Group. We are looking into the root cause of this issue right now to find a permanent resolution.
/Tariq Bell
Hi Marialecia,
You've just saved my dat, thanks!
Maud