User getting error while running an inquiry on Microsoft Dynamics GP

Asked By 0 points N/A Posted on -
qa-featured

One of our users receives an error message in Microsoft Dynamics GP while trying to do “receivables transaction inquiry”.

Details:
This happens only for this one user and in this one company; when I tried logging in using different user accounts, I found no errors.   So when this user goes to run a "receivables transaction inquiry by customer" and enters the customer digit and then tabs out to see the, results they receive this error:

[Microsoft][SQL Native Client][SQL Server]Cannot insert the value NULL into column 'ORTRXAMT',table 'tempdb.dbo.##1760642', column does not allow nulls. INSERT fails.

So now I need a solution to get rid of this typical problem. 

Thanks.

SHARE
Best Answer by farooqiq
Answered By 0 points N/A #95540

User getting error while running an inquiry on Microsoft Dynamics GP

qa-featured

Hi friend,

Microsoft Dynamics GP is a common getup from Microsoft Corporation. This is a license based product. It creates some problem in a few company or occasion because of license registry or out of date occasion.

In this case first thing that you can do is to update your Microsoft Dynamics GP. There is 4.0 version is available on http://support.microsoft.com or http://www.microsoft.com/en-us/download/default.aspx Major problem would be SQL server. This is little difficult to find possible wrong in SQL database. Though, you can try to reconfigure database properties as like name and location in server.

Other thing is you can’t insert null value in the properties of any integer category of database field. If you want to put null value then you must set that’s field’s property of data type as “VARCAR”.

Best Answer
Best Answer
Answered By 0 points N/A #95542

User getting error while running an inquiry on Microsoft Dynamics GP

qa-featured

HI,

It was tough to figure out a solution, but with extensive R&D I was able to fine a working fix for this problem.

So here it is,

Quite couple of ways to get around, and a lot of things to check while fixing:

First of All,

Run Grant.SQL script, delete the user, and recreate it.

Try to recreate the user with a new name, not with the same name by adding a 1 with the previously deleted user name.

If this doesn't work, check out the second solution.

Second:

Alright, for this to work, stick to the directions close and true. Follow them word by word and the problem will be resolved.

Run the following script:

a.   SELECT * from MC40500 where SERIES = 3  and USERID = 'user1'
        SELECT * from MC40500 where SERIES = 3  and USERID = 'user2'

  • SERIES = 3 (SALES)

b. 'VIEWTYPE' values:

 FUNCTIONAL = 3
 ORIGINATING = 4
 REPORTING = 5

c. Considering that client is not a registered MC, the user login should not be referencing  'VIEWTYPE'  = 4 or 5.

d.  change the 'VIEWTYPE' to 3 for the login in question.

Update these to RM20101, RM30101 and RM10301 tables as Work, Open and History might get included by the user.

HTH

Login/Register to Answer

Related Questions