Announcements
Hello,
We are getting this error when trying to release a Issue Batch that was created by the Service Call Module, Generate Inventory Screen (SD30600). We are currently running 2011 FP1 SP2.
------------------------------------------------------------------------------------------
Processing: Batch: 155714
Fatal SQL Error: 515
Cannot insert the value NULL into column '%.*ls', table '%.*ls'; column does not allow nulls. %ls fails.
Processing: Batch: 155714
Error occurred in Batch 155714, InTran record 800773 while executing the following procedure: SCMINTran - Invoice(#7)
Processing: Batch: 155714
Error occurred in Batch 155714, InTran record 800773 while executing the following procedure: SCMINTran - ReleaseTran(#8)
Processing: Batch: 155714
Error occurred in Batch 155714 while executing the following procedure: SCMBatch - ReleaseBatch(#2)
Processing: Batch: 155714
System Message 838: not released - it has been put on hold.
-------------------------------------------------------------------------------------------
Has anyone experienced this error before and corrected it?
Thanks
*This post is locked for comments
Hello,
This is actually bug 16102, the KB tied to it is 3062706
It basically give the workaround posted by Lewis H (Thank you Lewis)
----------------------------------------
Alter the table that the error message indicates is causing the problem to allow null values for vendor_name.
NOTE: Run this one to fix the error when printing the Check Register.
ALTER TABLE AP03630MC_Wrk ALTER COLUMN Vendor_Name CHAR(30) NULL
NOTE: Run this one to fix the error when printing the Detail Remittance report.
ALTER TABLE AP03625_Wrk ALTER COLUMN Vendor_Name CHAR(30) NULL
Run this script to fix the error when you print the Check Register (03.630) report.
ALTER TABLE AP03630MC_Wrk ALTER COLUMN Vendor_Name CHAR(30) NULL
Run this script to fix the error when you print the Detailed Remittance Advice (03.625) report.
ALTER TABLE AP03625_Wrk ALTER COLUMN Vendor_Name CHAR(30) NULL
Dear Stuart,
I can't find a link or reference to the article , except for this thread...which doesn't help.
If you are in a supported version then I can suggest you create a case in MS support for SL so they can troubleshoot the batch
Best Regards,
Jana MacDonald
Have a client experiencing the same issue, but can find no reference in the KB to this article. Can anyone provide a good link?
KB 962984 has a bug that might be what you are seeing. If this doesn't help then a SQL Trace may point to what is happening.
André Arnaud de Cal... 291,359 Super User 2024 Season 2
Martin Dráb 230,370 Most Valuable Professional
nmaenpaa 101,156