Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Today we are going to talk about an error message that can be misleading and send us down the wrong path when troubleshooting. The error message I am referring to happens when you open the Transaction by Vendor or Transaction by Document is below.
“Cannot insert the value NULL into column ‘DOCTYABR’ table tempdb.dbo.##0135356, column does not allow nulls. INSERT fails”
“The stored procedure pmBuildTrxINquiryByDateRange returned the following results. DBMSL 515, Microsoft Dynamics GP:0”
The error above is misleading because it references a DOCTYABR column that does not exist. It is telling us there is an issue with the DOCTYPE column in the PM00400 table.
When I see this case, it is due to a DOCTYPE being 0 or blank which is not valid. Our Doc Types are:
It can also mean that the DCSTATUS is blank or 0. Our valid DCSTATUS variables are:
To help identify these issues, we can use the select statements below.
Select * from PM00400 where DCSTATUS = ''
Select * from PM00400 where DCSTATUS = '0'
Select * from PM00400 where DOCTYPE = ''
Select * from PM00400 where DOCTYPE = '0'
Once you locate the bad records in the PM00400, you can review the results of the transaction tables to determine if there is any damage and make corrections as needed.
If the only thing that is damaged is the PM00400 record, the correction to this issue is:
I recommend testing this in a test company with a copy of live data to ensure that you receive the results you are looking for:
KB 871973 How to set up a test company that has a copy of live company data by using SQL Server 7.0, SQL Server 2000, or SQL Server 2005
This usually clears up the error.
I hope this helps and saves you a call to support.
Microsoft Support Engineer | Brandon Jarrett
Business Applications communities