Hi chiman can you explain more background leading up to this i.e. was the order pushed in via the Sage 300 Web API and this error only occurs for orders inserted this way?  Does this occur for orders entered through Order Entry manually?  Did you try entering a shipment manually as the error suggests?  It could just be an incorrectly filled out field, have you tried entering an order manually using the same parameters.  Try to share as much background as you can.  Cheers...Tim

It happens only with orders imported via Sage API, manually entered orders working fine. When entering shipment manually on a shipment screen receiving similar error.

It happens only with orders imported via Sage API, manually entered orders working fine. When entering shipment manually on a shipment screen receiving similar error.

Hi chiman this is a great discovery - that the error only works with API inserted orders.  This will help solve it.  What you want to do now is push an order in via the API but don't post it, then manually enter an order with identical details, but don't post it.  Now either export both orders to Excel via File -> Export or select both orders in database tables OEORDH and OEORDD and compare what's different between the two.  Its also good that manually entered orders work because it means there is nothing wrong with your system overall.  Once you identify what the API insert is doing wrong, fix it or get the developer to fix it.  Good luck!

Thanks for the tips. We found that mapping was an issue, inserted tax group as a tax authority.

That's brilliant chiman  I was really hoping you would be able to spot it.  Unfortunately as you've discovered sometimes the error messages are not helpful.  Ideally the error you received should have been "Invalid Tax Authority" instead of "Errors found during generation"  again fantastic work diagnosing and solving the issue