Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Rudy Salcedo]

?We have received this error during our nightly invoicing batch job 2 nights in a row on 2 different sales orders, causing the invoicing job to error-out and stop dead in its tracks.

When our Credit manager invoiced the SOs manually the next day, there were no issues and both SOs invoiced successfully.

Does anyone know why this error comes up, how to prevent it, and why manually invoicing the problematic SOs works but invoicing via batch job does not?

——————————
Rudy Salcedo
Senior Programmer/Analyst
LaForce, Inc
Green Bay WI
——————————

[vishal Dhawgaye]

Hi Rudy,

This is common issue with processes executing in batch jobs. Is this batch invoicing orders asynchronously? this occurs when multiple threads trying to update the same record. You can try ‘retry’ mechanism in catch. It will retry the same operation in case update conflict occurs.

——————————
vishal Dhawgaye
Hitachi Solutions America, Ltd.
——————————
——————————————-

[Joe MacPherson]

All…

We ran into an issue on 10.0.4 with batch processing of invoices across multiple threads which resulted in excessive charges to Credit Card transactions.  If you are affecting consumer Credit Card transactions in the Invoicing process, you need to validate that the error has impacted the consumer credit card with excess charges…

——————————
Joe MacPherson
Coldwater Creek
Hingham MA
——————————
——————————————-

[Mark Schurmann]

Awhile back we encountered a similar issue after an upgrade.  We use an AvaTax connector for the sales tax calculation.  During invoicing two calls to AvaTax are made, 1 to calculate and return the tax and 2 to commit the transaction and record the invoice number in AvaTax.  The invoice number is generated by D365 from a number sequence and is the last step in the invoice process.  The combination of multi-treading and multiple calls to AvaTax was causing the AvaTax to lose track of the invoice number which resulted in the commit of the invoice in AvaTax to fail due to a duplicate invoice number.  

I doubt this is quite your scenario, but if you have addons they might be the cause.

——————————
Mark Schurmann
Accounting Systems Manager
Automobile Protection Corp
Norcross GA
——————————
——————————————-

[Jessica Murphy]

Is there something wrong with the 10.0.4 update?  When we went to Update 28, all of our batch schedules had to be redone.  Our invoicing one we could not resolve in house, so we had to go to our Partner.  We still get an error, but it invoices.

——————————
Jessica Murphy
Master Planner
Goodwill Industries of Central Indiana
Indianapolis IN
——————————
——————————————-

[Rudy Salcedo]

Thanks everyone for the info/advice.  We ended up recreating the batch job for nightly invoicing 3 nights ago, and ?since then invoicing has run successfully without encountering the error that crashed the original invoicing batch job for over a week.

We’re not sure what happened to the original invoicing batch job to cause it to abend with the error since nobody changed anything.  And we don’t understand why creating an exact new version of the batch job runs successfully without getting the same error.  But if this happens again, the first thing we’re going to do is recreate the batch job again.

——————————
Rudy Salcedo
Senior Programmer/Analyst
LaForce, Inc
Green Bay WI
——————————
——————————————-

[Mark Schurmann]

I can second this.  On occasion, we’ve had batch jobs inexplicably fail and recreating the batch has resolved the issue.

——————————
Mark Schurmann
Accounting Systems Manager
Automobile Protection Corp
Norcross GA
——————————
——————————————-