Wrong packing slip is printing

(0) Share

Report

Posted on by Community Member

We are running AX 2012 R3 CU8. When generating a packing slip for a customer, the wrong packing slip is generated. The entire packing slip is incorrect, not just part of it. It's an odd problem and has happened several times over the past 2 months.

Here's what we're seeing: The user reports the wrong packing slips are being generated. This continues until we reset the AOS. After that, the packing slips that were wrong still print wrong, but newly generated packing slips are OK.

We've determined it's related to the record ids already existing in the SalesPackingSlipHeaderTmp and SalesPackingSlipDetailsTmp tables for different packing slips. To get around this problem we have commented out the following code from the ProcessReport method in the SalesPackingSlipDP class. //localSalesPackingSlipHeaderTmp = SalesPackingSlipHeaderTmp::findJourRecId(recId); This causes it to skip reading the records from the 2 tables and generates a new packing slip each time.

Does anyone have any ideas why this happens? Can we delete both of the tables on a regular basis?
Any other ideas or suggestions?

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Community Member on at

Like (0)

Report
Copy link

Link copied!

* REPOST *

We are running AX 2012 R3 CU8. When generating a packing slip for a customer, the wrong packing slip is generated. The entire packing slip is incorrect, not just part of it. It's an odd problem and has happened several times over the past 2 months.

Here's what we're seeing: The user reports the wrong packing slips are being generated. This continues until we reset the AOS. After that, the packing slips that were wrong still print wrong, but newly generated packing slips are OK.

We've determined it's related to the record ids already existing in the SalesPackingSlipHeaderTmp and SalesPackingSlipDetailsTmp tables for different packing slips. To get around this problem we have commented out the following code from the ProcessReport method in the SalesPackingSlipDP class. //localSalesPackingSlipHeaderTmp = SalesPackingSlipHeaderTmp::findJourRecId(recId); This causes it to skip reading the records from the 2 tables and generates a new packing slip each time.

Does anyone have any ideas why this happens? Can we delete both of the tables on a regular basis?

Any other ideas or suggestions?

Was this reply helpful? Yes No
Lee Bailey 340 on at

Like (0)

Report
Copy link

Link copied!

We have the same issue on AX 2012 R3 CU8. I have searched a bit online and had not found any other reports of it until I found your post. I was starting to think it was being caused by some of our customizations, but now I'm not too sure. Do you have any\many customizations in this area? Our workaround was to write a job to remove the offending records, but it is happening more so I was thinking along the same lines as you and amending the DP class to force it to write a new entry every time as opposed to pulling from the "Temp" table. I notice you posted this back in November - have you continued just deleting the tables regularly without issue?

Was this reply helpful? Yes No
Brandon Wiese 17,788 on at

Like (0)

Report
Copy link

Link copied!

You can safely purge the SalesPackingSlipHeaderTmp and SalesPackingSlipDetailsTmp tables as needed, but better when the AOS is offline or the system is quiet (so as not to accidentally delete data that is actually being used at the moment of delete).

However, if you disable the code indicated, I suspect you will be unable to print Pro-forma packing slips, which may or may not matter to you.

Was this reply helpful? Yes No
Lee Bailey 340 on at

Like (0)

Report
Copy link

Link copied!

Thanks Brandon - you are correct. When I make that change the Pro Formas are blank. I will purge the tables frequently as that seems the safest option.

Was this reply helpful? Yes No