Monday, June 17, 2013

Adjust the cost for a posted Sales, Purchasing or inventory transactions in MS Dynamics GP

If you facing a problem in your inventory costing you can apply the following scenario  but only if your valuation methods are (FIFO Perpetual, LIFO Perpetual and Average) 

Go to MS Dynamics GP>>Tools>>Utilities>>Inventory>>Adjusts Costs

Then enter the item ID and the "posted" transaction date as well and change the item cost and the system will create GL transaction for the variance cost.

Dynamics GP 2010 Utilities error "The Microsoft SQL Server database compatibility level for your Microsoft Dynamics GP databases is not supported. Change the compatibility level to SQL Server 2005 or later, refer to KB article 2399690"


Cause:
The database compatibility level of one or more Microsoft Dynamics GP databases is not set to SQL Server 2005 (90) or SQL Server 2008 (100). This is a new requirement starting with Microsoft Dynamics GP 2010 Service Pack 1.

Solution:
Change the database compatibility level of all Microsoft Dynamics GP databases to SQL Server 2005 (90) if running Microsoft SQL Server 2005 or to SQL Server 2008 (100) if running SQL Server 2008.

IMPORTANT NOTE: If an integrating application or customization requires the database compatibility to be something other than SQL Server 2005 (90) or SQL Server 2008 (100), change the database compatibility temporarily for the Service Pack 1 installation and then change it back to the required setting. Please be aware that this process will have to be performed for every hotfix and service pack installation following Service Pack 1 if the compatibility level is set back to a version older than SQL Server 2005 (90).

Perform the following steps:

1. At the Microsoft SQL Server, click Start, click All Programs, click Microsoft SQL Server 2005 or Microsoft SQL Server 2008, and then click SQL Server Management Studio.

2. Login to your Microsoft SQL Server as the sa user.

3. In the Object Explorer area, expand Databases.

4. Right-click the DYNAMICS database and then click Properties.

5. In the Select a page area, click Options.

6. Click to select the drop down list next to Compatibility level and then select SQL Server 2005 (90) if running Microsoft SQL Server 2005 or select SQL Server 2008 (100) if running Microsoft SQL Server 2008.

7. Click OK.

8. Repeat Steps 4-7 for each Microsoft Dynamics GP company database.

9. Start Microsoft Dynamics GP 2010 Utilities to continue the service pack installation.

Wednesday, April 10, 2013

How to delete a company in MS Dynamics GP

You have to delete the company in GP first then from the database from SQL.

Steps: 
1. MS Dynamics GP Menu>>Tools>>Utilities>>System>>Delete Company.
2. Enter the system password if necessary.
3. Open the lookup then select the company that you want to delete.

by this you just deleted the company from GP only

4. Open the SQL management studio.
5. Open the databases.
6. Right click on the database you want to remove and click delete.

Tuesday, April 9, 2013

MS Dynamics GP:- This batch is being posted by another user

You get this message even though nobody is logged in to the database so that it's impossible for the batch to be being posted by somebody else. What to do?
  1.  Back up the DYNAMICS and company databases.
  2. Change the batch status so that it no longer thinks it's being posted.
USE TWO
GO

UPDATE SY00500 set BTCHSTTUS = 0 WHERE BACHNUMB = 'Batch ID'

Monday, March 18, 2013

Windows 2008 Server R2 Enterprice: Joining my existing domain

I attempted to join my existing domain with this server being a member server, and received a message:

An attempt to resolve the DNS name of a DC in the domain being joined has failed. Please verify that this client is configured to reach a DNS server that can resolve DNS names in the target domain.

I actually know how to fix this, I think... when configuring IP addresses, I didn't put the local address of my domain controller in as one of the DNS possibilities. Once this change was made...it worked.