Tips & Tricks Dynamics GP

FRx Showing Splash Screen and stops without showing error.

2017-09-14T21:43:00.001-07:00

Problem :

Last night my FRx users emailed me about FRx strange behavior. Showing splash screen and stops without showing any error.

Solution :

I search a lot on internet but I could not find any suitable or reliable answer to solve this error. I delete all .G32 files but problem does not solved, so I delete all .lck and .idb files but no solution.
When I replaced the Frxsys32.mdb file with old my recent backed up file then runs without any problem.

Please always take backup of sysdata10 folder every week/monthly.

Thanks

Arif

Set up a test company that has a copy of live company data for Microsoft Dynamics GP by using Microsoft SQL Server

2017-08-10T12:13:00.000-07:00

To test certain issues, a troubleshooting technique may be to copy the Live Company database to a Test Company database.

This article describes how to set up a test company that has a copy of live company data by using Microsoft SQL Server.
MORE INFORMATION

Notes

If you use Record Level Notes - in your existing live company and plan to use them in the test company, you must run the NoteFix utility. For more information, contact the Microsoft Business Solutions System Technical Support team by telephone at (888) 477-7877.
If you are using Human Resources for Microsoft Dynamics GP, the Attendance Setup information appears to have not been copied over. To open this window, click Tools, point to Setup, point to Human Resources, point to Attendance, and then click Setup. This table (TAST0130) is copied over, but it contains a field that still references the Live Company database. To correct this issue, you can simply re-enter the data in the Attendance Setup window in the new Test company database to contain the same information as before and Save it. Or, you may choose to update the COMPANYCODE_I field in the TAST0130 table to change the company code reference to Test database instead (which can be found in the INTERID column value for the Test company in the Dynamics..SY01500 table).
If you are using Fixed Assets for Microsoft Dynamics GP, the Fixed Assets Company Setup information will not be brought over to the Test Company. To correct this issue, open the Fixed Assets Company Setup window in the Live Company and note the settings. Open the Fixed Assets Company Setup window in the Test Company and enter the same settings as the Live Company. To open the window, use the following:
- Microsoft Dynamics GP 10.0 or a later version:
  Click Microsoft Dynamics GP, point to Tools, point to Setup, point to System, point to Fixed Assets, and then click Company.
If you are using Audit Trails for Microsoft Dynamics GP, you must delete the audit triggers from the test company using SQL and not from the front-end. Audit Trails is just triggers that are copied over and still point to the same live audit database. However, do not delete, stop or remove the audit in the Audit Trail Maintenance window in the test company, or this will clear out the history in the audit table and/or remove the trigger on the live company. Refer to steps outlined in the KB article below to remove the audit trail triggers from the test company:

2847491 How to stop Audit Trail triggers in the test company from updating the live audit database using Audit Trails in Microsoft Dynamics GP
If you are using Analytical Accounting (AA), you must first activate AA in the Test company, before the live company database (that has AA active) can be restored to the Test
company. After the restore is completed, you must then click on the link below to obtain a script to run against the Test company database that will update the next available values stored in the AAG00102 table (to prevent Duplicate Key errors when keying new transactions).

https://mbs2.microsoft.com/fileexchange/?fileID=a80eb2b7-dbcf-4d5f-a7a2-f64306f65721

• If you are using Management Reporter 2012, you must stop the Management Reporter services which can be done using either of the following options:

1. In the Management Reporter 2012 Configuration Console, on the first page, you’ll see both the Management Reporter 2012 Application Service and Management Reporter 2012 Process Service. Click Stop under these two services to stop them.

2. Click on Start, click on Control Panel, click on Administrative Tools, then click to open Services. In the Services window, highlight the Management Reporter 2012 Application Service and click on the link to Stopthis service. Also, highlight the Management Reporter 2012 Process Service and click the link to Stop this service as well.

Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

To set up the test company, follow these steps:

In Utilities, create a new company database that you can use as the test company. Make sure that you give the database a unique DB/company ID and company name that will designate the database as a test company. For example, you could use a DB/company ID of "TEST" and a company name of "TEST COMPANY."

Note Note the path where the database's .mdf and .ldf files are being created. You will need this information for a step later in this article.
Log in to the test company. To do this, use the following step.
- Microsoft Dynamics GP 10.0 or later:
  Click Microsoft Dynamics GP, click Tools, click Setup, click System, and then click User Access. .
In the User Access area, select the user to whom you want to grant access to the test company database. Then, click to select the check box next to the test company name to grant access to the test company database. Repeat this step for all users to whom you want to grant access to the test company database. To do this, use the following step..
- Microsoft Dynamics GP 10.0 and Microsoft Dynamics 2010: Click Microsoft Dynamics GP, click Tools, click Setup, click System, and then click User Access. .
Make a backup of the live company database. To do this, use one of the following methods, as appropriate for your situation.

Method 1

If you are using SQL Server Enterprise Manager, follow these steps:
1. Click Start, and then click
  Programs.
2. Point to Microsoft SQL Server, and then click Enterprise Manager.
3. Expand Microsoft SQL Servers, expand
  SQL Server Group, and then expand the instance of SQL Server.
4. Expand Databases, right-click the live company database, click All Tasks, and then click
  Backup Database.
5. In the SQL Server Backup window, click
  Add in the Destination section.
6. In the Select Backup Destination window, click the ellipsis button next to the File name field.
7. In the Backup Device Location window, expand the folders, and then select the location for the backup file.
8. Type a name for the backup file. For example, type
  Live.bak.
9. Click OK repeatedly until you return to the SQL Server Backup window.
10. Click OK to start the backup.
11. When the backup has completed successfully, click
  OK.
Method 2

If you are using SQL Server Management Studio, follow these steps:
1. Click Start, and then click
  Programs.
2. Point to Microsoft SQL Server, and then click SQL Server Management Studio. The Connect to Server window opens.
3. In the Server name box, type the name of the instance of SQL Server.
4. In the Authentication list, click
  SQL Authentication.
5. In the User name box, type
  sa.
6. In the Password box, type the password for the sa user, and then click Connect.
7. In the Object Explorer section, expand Databases.
8. Right-click the live company database, point to
  Tasks, and then click Backup.
9. In the Destination area, click
  Remove, and then click Add.
10. In the Destination on disk area, click the ellipsis button.
11. Find the location where you want to create the backup file, type a name for the backup file, such as LIVE.bak, and then click OK.
12. Click OK repeatedly until you return to the Backup Database window.
13. Click OK to start the backup.
Restore the live company backup file that you created in step 4 into the test company database. To do this, use one of the following methods, as appropriate for your situation.

Method 1

If you are using SQL Server Enterprise Manager, follow these steps:
1. In Enterprise Manager, right-click the test company database, click All Tasks, and then click Restore Database.
2. In the Restore as database field on the General tab, verify that the test company database is selected.
3. In the Restore section, click to select the From device check box.
4. In the Parameters section, click
  Select Devices, and then click Add in the Choose Restore Devices window.
5. In the Choose Restore Destination window, click the ellipsis button next to the File name field.
6. In the Backup Device Location window, expand the folders, locate and then click the live company backup file that you created in step 4.
7. Click OK repeatedly until you return to the Restore Database window.
8. Click the Options tab.
9. Click to select the Force restore over existing database check box.
10. Verify that a valid path appears in the Move to physical file name field, and then verify that the .mdf and .ldf file names are for the test company database that you created in step 1.
  
  Note The logical file name reflects the name of the live database. Do not change the logical file name.
11. Click OK to start restoring the live company database into the test company database.
12. When the restore has completed successfully, click
  OK.
Method 2

If you are using SQL Server Management Studio, follow these steps:
1. Click Start, and then click
  Programs.
2. Point to Microsoft SQL Server, and then click SQL Server Management Studio. The Connect to Server window opens.
3. In the Server name box, type the name of the instance of SQL Server.
4. In the Authentication list, click
  SQL Authentication.
5. In the User name box, type
  sa.
6. In the Password box, type the password for the sa user, and then click Connect.
7. In the Object Explorer section, expand Databases.
8. Right-click the test company database, point to
  Tasks, point to Restore, and then click Database.
9. In the Source for Restore area, click
  From Device, and then click the ellipsis button.
10. In the Backup Location area, click
  Add.
11. Find the location where saved the backup file, select
  LIVE.bak file, and then click OK.
12. Click OK. You return to the Restore Database window.
13. In the Select the Backup Sets to Restore section, click the backup file that you want to restore.
14. In the Select a Page area, click
  Options.
15. In the Restore Database Files as area, you will need to change the location of these two files from the Live database to the test database's .mdf and .ldf files. By default, these will be selected on the Live database's .mdf and .ldf files.
  
  Note The logical file name reflects the name of the live database. Do not change the logical file name.
16. To change these locations, click on the Ellipse (…) next to the file location field.
17. Navigate to the path that you noted in step 1, where the test database was created.
18. Highlight the respective .mdf file, and then click
  OK.
19. Repeat steps p through r, select the .ldf file, and then click OK.
20. Click to select the Overwrite existing database check box.
21. Click OK to return to the Restore Database window
If you are using Microsoft Dynamics GP 10.0 or later, follow these steps to copy the security permissions from the live company to the test company:
1. Log on to Microsoft Dynamics GP as the sa user.
2. Click Microsoft Dynamics GP, point to
  Tools, point to Setup, point to
  System, and then click User Access.
3. Select an appropriate user, and then make sure that the check box for the new test company is selected to indicate that access is granted.
  
  Note If you receive an error message when you click to select a company, delete the user from the Users folder under the new test database in SQL Server Management Studio or in Enterprise Manager.
4. Click Microsoft Dynamics GP, point to
  Tools, point to Setup, point to
  System, and then click User Security.
5. In the Security Task Setup window, select the user who you want to have access to the test company.
6. In the Company list, click the live company.
7. Click Copy, click to select the check box that is next to the test company, and then click OK.
  
  The user’s permissions in the live company are copied to the test company.

After the live company database has been restored over the top of the test company database, the test company contains references that have the same COMPANYID and INTERID information that the live company has. To correctly reflect the information for the test company, run the following script below against the test company in Query Analyzer or in SQL Server Management Studio. This script updates the COMPANYID and INTERID in the test database with the information that is listed in the system database SY01500 table for this test company.

if exists (select 1 from INFORMATION_SCHEMA.COLUMNS where TABLE_NAME = 'SY00100') begin
  declare @Statement varchar(850)
  select @Statement = 'declare @cStatement varchar(255)
declare G_cursor CURSOR for
select case when UPPER(a.COLUMN_NAME) in (''COMPANYID'',''CMPANYID'')
  then ''update ''+a.TABLE_NAME+'' set ''+a.COLUMN_NAME+'' = ''+ cast(b.CMPANYID as char(3)) 
  else ''update ''+a.TABLE_NAME+'' set ''+a.COLUMN_NAME+'' = ''''''+ db_name()+'''''''' end
from INFORMATION_SCHEMA.COLUMNS a, '+rtrim(DBNAME)+'.dbo.SY01500 b
  where UPPER(a.COLUMN_NAME) in (''COMPANYID'',''CMPANYID'',''INTERID'',''DB_NAME'',''DBNAME'')
    and b.INTERID = db_name() and COLUMN_DEFAULT is not null
 and rtrim(a.TABLE_NAME)+''-''+rtrim(a.COLUMN_NAME) <> ''SY00100-DBNAME''
  order by a.TABLE_NAME
set nocount on
OPEN G_cursor
FETCH NEXT FROM G_cursor INTO @cStatement
WHILE (@@FETCH_STATUS <> -1)
begin
  exec (@cStatement)
  FETCH NEXT FROM G_cursor INTO @cStatement
end
close G_cursor
DEALLOCATE G_cursor
set nocount off'
  from SY00100
  exec (@Statement)
end
else begin
  declare @cStatement varchar(255)
  declare G_cursor CURSOR for
  select case when UPPER(a.COLUMN_NAME) in ('COMPANYID','CMPANYID')
    then 'update '+a.TABLE_NAME+' set '+a.COLUMN_NAME+' = '+ cast(b.CMPANYID as char(3)) 
    else 'update '+a.TABLE_NAME+' set '+a.COLUMN_NAME+' = '''+ db_name()+'''' end
  from INFORMATION_SCHEMA.COLUMNS a, DYNAMICS.dbo.SY01500 b
    where UPPER(a.COLUMN_NAME) in ('COMPANYID','CMPANYID','INTERID','DB_NAME','DBNAME')
      and b.INTERID = db_name() and COLUMN_DEFAULT is not null
    order by a.TABLE_NAME
  set nocount on
  OPEN G_cursor
  FETCH NEXT FROM G_cursor INTO @cStatement
  WHILE (@@FETCH_STATUS <> -1)
  begin
    exec (@cStatement)
    FETCH NEXT FROM G_cursor INTO @cStatement
  end
  close G_cursor
  DEALLOCATE G_cursor
  set nocount off
end

Note If this script fails with a duplicate key error, you must manually change the INTERID and COMPANYID columns in the table on which you are receiving the primary key error in the test company.

For example: A primary key constraint error on "PKRVLPD033." To properly perform a search for the table, the prefix, PK, refers to Primary Key and is not part of the table name. In this example, the table that you want to verify is "RVLPD033" for that database.

Note If you are using Human Resources, you must also change the COMPANYCODE_I value in the TAST0130 table. See the NOTES section at the top of this article for more information.

Verify that the database owner of the test database is DYNSA. To do this, run the following script against the test company in Query Analyzer or in SQL Server Management Studio:
```
 
sp_changedbowner 'DYNSA'
```
If you use the drilldown functionality in the SQL Server Reporting Services or Excel integrated reports you need to do the following to update your server links so the drilldowns work after the database change:
- Ensure that everyone has logged out of Microsoft Dynamics GP and close all instances of SQL Server Management Studio
- On a machine where Dynamics GP is installed click on Start, then point to All Programs. Click on Microsoft Dynamics, then GP 2010 and click on Database Maintenance
- When the utility opens select or enter the SQL Server instance where the Dynamics GP databases are stored. If you are logged in as a domain account with rights to this SQL Server instance you can select that option. Otherwise select SQL Authentication and enter a n appropriate user name and password. Then click Next >>
- Select Mark All to choose each of the Dynamics GP databases and click Next >>
- Select the Microsoft Dynamics GP product, then click Next >>
- Select 'Functions and Stored Procedures' and 'Views', then click Next >>
- Review the confirmation window, then click Next >> to begin the process.
The test company should now have a copy of the live company data and be ready for use.

Target Date Fiscal Year may not be greater than current fiscal year for selected Book

2015-11-03T22:24:00.001-08:00

Solution:

Financial > Utilities > Book

Select the Depreciation Book and select the current fiscal year, which is open now.

If you have closed June 2015 and now working in July 2015 and trying to post the depreciation then the above error will be shown. Just go to Book in financial of Assets and select Dep. Book and change it to 2016 ( which is the current Fiscal Year)

Purchase Order Processing setup information is missing or damaged

2012-02-08T04:43:00.001-08:00

When you try to open a purchase order entry window in Microsoft Dynamics GP, you receive the following error message:

Solution

Microsoft Dynamics GP 2010 and 10.0

On the Microsoft Dynamics GP menu, point to Tools, point to Setup, point to System, point toSecurity, and then click Alternate/Modified Forms and Reports.

In the ID box, type the user ID.

In the Product list, click Project Accounting.

In the Type list, click Windows.

Expand the Purchasing folder.

Expand the Purchase Order Processing Setup folder.

Click Project Accounting.

Click Save.

On the Microsoft Dynamics GP menu, point to Tools, point to Setup, point to Purchasing, and then click Purchase Order Processing.

Click Project.

Make the appropriate selections.

Click OK.

Scheduling, Scheduling, Scheduling Payments in Dynamics GP | Dynamics GP Insights

2011-12-28T07:04:00.000-08:00

Scheduling, Scheduling, Scheduling Payments in Dynamics GP | Dynamics GP Insights

Scheduled payments are not used extensively in Microsoft Dynamics GP, but they can be quite helpful if you need to record scheduled invoices to post over time. If you want to pay off an invoice in installments, in payables management, or if you have negotiated with a customer to allow them to pay a large bill over time, scheduled payments can be helpful. They are available in both the receivables and payables management modules and work similarly in both. We’ll look at this feature in Payables Management.

DynamicAccounting.net: Weekly Dynamic: Receivables Scheduled Payments

2011-12-28T07:02:00.000-08:00

DynamicAccounting.net: Weekly Dynamic: Receivables Scheduled Payments

Microsoft Certification Tutorial

2011-11-30T07:33:00.001-08:00

Microsoft Certification Tutorial
by
Snack Owner

Microsoft Certification Tutorial

2011-11-30T07:31:00.001-08:00

Microsoft Certification Tutorial
by
Snack Owner

WAQAS BUTT - Microsoft Dynamics ERP'S Blog: Dynamics GP – Multicurrency Exchange Rate Updating...

2011-11-02T05:45:00.000-07:00

WAQAS BUTT - Microsoft Dynamics ERP'S Blog: Dynamics GP – Multicurrency Exchange Rate Updating...: Dynamics GP – Multicurrency Exchange Rate Updating Tool

We came across so many requests from our customers asking for a utility which ...

WAQAS BUTT - Microsoft Dynamics ERP'S Blog: Using SQL Server Reporting Services(SSRS) with Mic...

2011-11-02T05:42:00.000-07:00

WAQAS BUTT - Microsoft Dynamics ERP'S Blog: Using SQL Server Reporting Services(SSRS) with Mic...: In Dynamics GP we have a ...

I was #1 Rank in MVA from Pakistan

2011-09-22T05:57:00.000-07:00

With the experience of IT, data and information security from small startup to complex and challenging projects. I have been involved in the exciting Information Security, Identity & Access, and Systems Integration technologies.

#1 Rank in MVA from Pakistan

You cannot unapply a payment when you transfer the payment to the history tables in Receivables Management in Microsoft Dynamics GP

2011-07-29T06:52:00.001-07:00

Problem :

When you transfer a payment to the history tables in Receivables Management in Microsoft Dynamics GP or in Microsoft Business Solutions - Great Plains, you cannot un apply the payment.

To work around this problem, use one of the following methods.

Method 1: Remove the payment and the applied documents from the history tables

1. Use the Remove Receivables Transaction History window to remove the payment and applied documents. To do this, use one of the following methods:

o In Microsoft Dynamics GP 10.0, point to Tools on the Microsoft Dynamics GP menu, point to Tools, point to Sales, and then click Remove Transaction History.

o In Microsoft Dynamics GP 9.0 and in Microsoft Business Solutions - Great Plains 8.0, point to Utilities on the Tools menu, point to Sales, and then click Remove Transaction History.

2. Reenter the payment and the applied documents in the Receivables Transaction Entry window and in the Cash Receipts Entry window. To open the Receivables Transaction Entry window, point to Sales on the Transactions menu, and then click Transaction Entry. To open the Cash Receipts Entry window, point to Sales on the Transactions menu, and then click Cash Receipts.

Note If you do not want the transactions to update General Ledger, delete the batch that is created in General Ledger. Or, post reversing transactions.

3. Method 2: Use the Transaction Un apply tool

4. If you are using Microsoft SQL Server, a tool that is called Transaction Un apply may be available for Receivables Management. This tool enables you to unapply documents in the history tables. It automatically moves the records back to the open tables. Then, you can reapply the records as needed. For more information about this tool, contact Microsoft Dynamics Support at MBSProfessionalServices@microsoft.com (mailto:MBSProfessionalServices@microsoft.com) , or visit the following Microsoft Web site:

5. http://www.microsoft.com/dynamics/support/default.mspx (http://www.microsoft.com/dynamics/support/default.mspx)

Article ID: 853678

Year Does Not Exist message during Multicurrency Revaluation

2011-07-25T04:23:00.000-07:00

Question:
When I go into the Revaluation window and choose Current Year, I receive the message Year does not exist. If I choose Other Year and enter a period, I receive the message, Period does not exist. I have verified or done the following:

1. Renamed my fiscal period setup files and re-setup all of my fiscal period.

2. Verified that the user date falls within a valid fiscal period.

What else can I do to resolve this issue?

Answer:

Go into Audit Trail Codes Setup (Setup - Posting - Audit Trail Codes). In the Financial series, verify that you have an audit trail code for Revaluation. If you do not have an audit trail code for Revaluation, clear data on the Audit Trail Codes file to recreate the audit trail codes with Multicurrency audit trail codes. Before you clear data on this file, print out the Audit Trail Codes report (Reports - Company - Setup - Audit Trail Codes), then after you have cleared data, reenter the Audit Trail Codes based on this report.
Article ID: 864052

Microsoft Dynamics CRM and Office 365 – Powered Productivity - Executive Insight - Community Home - Microsoft Dynamics Community

2011-07-25T04:20:00.000-07:00

Microsoft Dynamics CRM and Office 365 – Powered Productivity - Executive Insight - Community Home - Microsoft Dynamics Community

If you look closely at any successful company you will find productivity is the engine fueling growth. When business leaders think about improving the effectiveness of their people, they look to remove barriers that constrain knowledge sharing and empower confident decision making. In order to do this, organizations need technology solutions that are cost-effective, and deliver the latest innovations. ......

Customers Choose Microsoft Dynamics When Investing in Business Applications - Executive Insight - Community Home - Microsoft Dynamics Community

2011-07-25T04:16:00.000-07:00

Customers Choose Microsoft Dynamics When Investing in Business Applications - Executive Insight - Community Home - Microsoft Dynamics Community

How to restore a full backup of the Company database or the Dynamics database in Microsoft Dynamics GP

2011-06-21T03:58:00.001-07:00

To restore a full backup of the Company database or the DYNAMICS database, follow the appropriate steps.

Using Microsoft SQL Server 2000

1.	Click Start , point to All Programs , point to Microsoft SQL Server , and then click Enterprise Manager.
2.	In the navigation pane, expand Microsoft SQL Servers, expand SQL Server Group, expand (local) (Windows NT), and then expand Database.
3.	Right-click the database that you want to restore, click All Tasks, and then click Restore Database.
4.	In the Restore as database box, select the database that you want to restore.
5.	In the Restore area, click From device.
6.	In the Parameters area, click Select Devices to open the Choose Restore Devices dialog box, and then click Add.
7.	Click the File name field lookup (…) button, and then select the backup file of the database that you want to restore.
8.	Click OK three times.
9.	In the Restore Database dialog box, click the Options tab.
10.	Click to select the Restore over existing database check box.
11.	In the Move to physical file name field, type the path where you want to restore the database's .mdf file and .ldf file.
12.	Click OK to start the database restore process.
13.	On the Tools menu, click SQL Query Analyzer.
14.	Run the following command against the Dynamics database and against all company databases. sp_changedbowner 'DYNSA'

Using Microsoft SQL Server 2005 or Microsoft SQL Server 2008

1.	Click Start , point to All Programs , point to Microsoft SQL Server 2005 or Microsoft SQL Server 2008 , and then click SQL Server Management Studio
2.	In the navigation pane, expand Databases.
3.	Right-click the database that you want to restore, click Tasks, click Restore, and then click Database.
4.	In the To database box, click the database that you want to restore.
5.	Click From device, and then click the From device lookup (…) button to open the Specify Backup dialog box.
6.	Click Add, and then click the backup file of the database that you want to restore.
7.	Click OK two times.
8.	Click to select the check box in the Restore column of the database that you want to restore.
9.	In the Select a page pane, click Options.
10.	Click to select the Overwrite the existing database check box.
11.	In the Restore as field, type the path where you want to restore the database's .mdf file and .ldf file or you can leave the default path.
12.	Click OK to start the database restore.
13.	In SQL Server Management Studio, run the following command against the DYNAMICS database and against all company databases. sp_changedbowner 'DYNSA'

Using Navigation List Builder in GP 2010

2011-06-08T07:55:00.000-07:00

If you have SmartList Builder and GP 2010, you have access to a new feature called Navigation List Builder. This tool enables you to create your own lists that appear on the Navigation Pane.
What are navigation lists, and why would you want to create your own? Let’s look at an example of a navigation list that’s a standard option with GP for viewing sales documents.
Click the Sales button on the Navigation Pane.
Click “Sales Order Transactions” in the Shortcut Bar.

You can filter this list and save your filter as a favorite. For example, you can filter the list to display only invoices and exclude historic invoices.

The only problem you may have is that the system can be slow to display your data.

Using Navigation List Builder, you can create a list that automatically displays just the data you want and the columns you want.

Go to Microsoft Dynamics GP menu >> Tools >> SmartList Builder >> Navigation List Builder.

Enter List ID, List Name and Navigation Pane options as shown below.

Add the table you want by clicking the + sign. In this case, select “Sales Transaction Work.”

For the Display column, mark the columns you would like the user to be able to view.

For the Preview column, mark the columns that you want to display in the bottom of the window.

Click the Restrictions button to add a restriction to display only invoices.

Click the OK button to save the restriction.

Other options in Navigation List Builder include:

· Preview – Change the order and display of columns

· Action – Add functionality, such as the ability to drill down to another window

· Calculation – Add calculated fields, such as a margin amount

· Options – Display images for different values so that users can identify records visually

Click Save to save your new list.

Click the Sales button in the Navigation Pane.

Scroll down to see the new list.

Click the list you created.

The completed list you created is displayed.

Use the Filter button to restrict the information in the list, and use the other features of lists to hide the columns you do not want to see.

Another great feature of Navigation List Builder is the ability to create lists based on data outside of GP. For example, if you have another system, such as a custom accounts receivable module, you can display data from it inside GP.

Reference Site :

http://www.bkdtechnologies.com/Newsletters/MS/Updates/2010/2010-11Updates-1.htm

Top 10 Reasons You Should Upgrade to Dynamics GP 2010

2011-06-08T07:50:00.000-07:00

If you are current on your annual maintenance and have not yet upgraded to Dynamics GP 2010, it’s time to think about taking advantage of your maintenance benefits. While every company is unique and may have specific reasons for not upgrading, you may want to consider getting current. By staying current, upgrading to future versions will be simpler.

Why would you want to upgrade to GP 2010? There are several improvements and new features in GP 2010, even for those companies using GP 10. Here are 10 reasons you may want to consider upgrading to GP 2010, including:

1. Deliver faster access to personalized insight – You no longer have to give users full access to GP for them to get information from the system. With role centers, you can give users personalized dashboards and KPIs with drill-back capabilities. You also can view GP data on a variety of devices and applications.

2. Get more out of Excel integration – Imagine being able to open an Excel file and have up-to-date information from GP with charts and pivot tables automatically updated. GP 2010 delivers 220 refreshable Excel reports. You can use SmartList Builder to create new Excel refreshable reports.

3. More options for analyzing information – Besides the Excel refreshable reports, you now have 90 SQL Server Reporting Services reports. Of course, new reports can be created with SQL Server Business Intelligence Development Studio.

4. Better Microsoft Outlook & Word integration – Using new Word templates, you can automatically send invoices, purchase orders and other documents as PDF documents in Outlook.

5. Enhanced personalized experience – Users can tailor dashboards and action panes with the lists they need to find information. You also can use the new Navigation List Builder to create custom lists.

6. Create “mini-applications” using Extender – Without a single line of code, you can use Extender to create your own applications within GP to capture and share information with GP.

7. Make unified communications a part of doing business – Instantly communicate with business partners using Microsoft Office Communicator.

8. Connect to other business applications – Using more than 350 Web services, you can connect GP to other business applications to keep GP and the connected applications up to date.

9. Use current Microsoft technology innovations – You can use GP 2010 on 64-bit environments and implement workflows using Windows SharePoint Services.

10. Management Reporter – Take advantage of the new 64-bit environments with Management Reporter for enhanced financial reporting.

Error message when you log into a company in Microsoft FRx: "Invalid Path Specified for Work Drive"

2011-06-07T03:05:00.000-07:00

By default, the work drive path is set to the temp directory for the current user (as defined by the TEMP environment variable), but it can be changed for each user. If the user's TEMP environment variable contains an invalid path, or if the path specified was removed, this error will occur.

The Optional Work Drive is a directory used by FRx while building GL index files or reports.

Once the index or report has been built, FRx moves the file to its proper location.

The path may be changed by using either of the following methods:
From within the FRx Designer: On the Admin menu,click Processing Options.Click thearrow in the Optional Work Drive box.Browse to the desired path. Click OK. Close Designer, and then open it again - the error should no longer occur.

From the FRX.INI file: Click the Start button, then click Run. Type frx.ini, and then click OK - the file should open in Notepad. Locate the [Network] section. Change the value on the WorkDrive line to a valid path. Save and close the file.
Launch FRx Designer - the error should no longer occur.

Note: On Terminal Services/Citrix servers, a new temp directory is created for each user session, and the user's TEMP environment variable is set accordingly. When the user logs out, the temp directory is deleted, and a new temp directory is created each time a user logs in. Each time the WorkDrive path is changed, FRx stores the path in the FRX.INI file. Because the temp directory will change on each login, this error may occur every time a user launches FRx in a new session.
To get around this, a shared directory should be created for all users. The following steps may be used to set this up:
Create a new directory on the Terminal Services/Citrix server - an example of this might be D:\\FRxTemp.Open a command prompt. From the prompt, type change user /install to enter install mode. Using Windows Explorer, browse to the Windows directory. Locate the FRX.INI file and open it in Notepad. Change the value on the WorkDrive line (located under the [Network] section) to the directory created in step 1. Save and close the FRX.INI file. Switch back to the command prompt window, and then type change user /execute to change back to user execute mode. When users re-connect to the Terminal Services/Citrix server, the WorkDrive path in each user's FRX.INI file should be changed to the new drive. If specific users still receive the error, simply change the WorkDrive path in the FRX.INI file for the user or users having the problem.

http://support.microsoft.com/kb/965528

Regards,

Muhammad Arif Hussain

To project depreciation for assets in one or more books:

2011-05-23T08:36:00.001-07:00

1. Open the Depreciation Projection window.

(Microsoft Dynamics GP menu Routines >> Fixed Assets >> Projection)

2. To project depreciation for an asset group, unmark Project all assets and select

an asset group ID. Otherwise, leave Project all assets marked to project depreciation for all assets.

3. Enter the date to project depreciation through in the Depreciation Projection Target date field.

4. Select a book and choose Insert to move the book to the Selected Books list.

5. Choose Projection and close the window.

6. You can print projection reports or view the information in the Projection

Inquiry window

Regards,

Muhammad Arif Hussain

GP System Administrator

How to hold the posting batches of Purchases / Sales in Financial Module

2011-05-13T04:36:00.000-07:00

Go Tools>Setup>Posting>Posting -

The main difference between these options is that when you Post To General Ledger, you have an extra opportunity to verify Batch transactions before they affect the General Ledger. When you Post Through General Ledger, you save time by not having to complete the additional verification step.

Post to General Ledger

If you choose to Post to General Ledger, batches posted in all other modules will update the module in which the transaction originated, and then create a batch of General Ledger transactions. Then you must post those batches within General Ledger as well, to update the posting accounts for the transactions.

There is one exception to bear in mind – Bank Transactions – all Bank transactions are single transactions – there are no batches in Banking. However, if you have Bank Transactions set to Post To, a batch is automatically created by GP for each individual transaction. The Batch ID will begin with ‘CMTRX’.

Post through General Ledger Files

You can choose to have General Ledger accounts updated automatically when you post from another module to General Ledger. If you mark the Post through General Ledger Files option, batches posted in other modules automatically update the module in which the transactions originated and the appropriate posting accounts in General Ledger.
Note: Single transactions (not in a Batch) Post To General Ledger and not Through General Ledger, even if the Posting Setting is 'Post Through'. A Batch ID is created using the prefix of the Source Document Code for the transaction posted, i.e. 'IVTFR' for an inventory transfer transaction.
Also, at least one of the two Posting Settings must be checked or no General Ledger batch will be created.

How to reset the Stuck 'Printing' status of Batch Job

2011-05-05T04:31:00.000-07:00

I searched a lot on google.com about to solve this problem, but I could not get best solution for this issue.

I tried by myself to open the SQL Server database of that company in which the batch was stuck.

Find SY00500 table and find that batch record which was stuck and not showing in Batch recovery Window in GP and set its BCHSTTUS field from 5 to 0. ( 5= being printing, 0= available )

After this action now we can post and print the Batch smoothly.

Arif

Cell : +923328244088

The benefits of classes in Dynamics GP

2011-05-02T02:54:00.001-07:00

A consultant had a case come through that was a great reminder of the benefits of classes in Dynamics GP. So, we thought it would be a great tip for you if you are not currently using Classes. In all modules except Fixed Assets, classes are completely optional. However, there are some very practical reasons to use classes, which include:

Provide defaults for new records
Roll down changes to records
Group records for reporting and other processes

An Example: Let’s use Inventory!

When you set up an item from scratch (using Cards>>Inventory>>Item), the maintain history checkboxes are not marked by default (in Cards>>Inventory>>Item>>Options). If the track history box is not checked, the inventory history will NOT be tracked for that selected item. Yes. You heard that right. No inventory history, which will then interfere with the printing of historical reports like the historical stock status.

So…how does a class help this? Simple, if you set up your item classes and mark the check boxes to track history, then when an item is placed in the classes, those settings can default. No more having to remember every time you create an item.

Now, a similar issue can occur if new item classes are set up and the maintain history check boxes are not marked for the new class. How can we ensure that these options are marked by default on new classes? It’s as easy as marking the “default” check box on a class.

The “default” check box is often misunderstood. It does NOT mean the selected class is the default class for new items. What it DOES mean is that the selected class is the default template for any future classes that are created. So, pick a basic class with the correct settings, and make it your default. Then when you set up a new class, it will assume the settings of the default class and then you can make modifications based on the requirements of the new class.

Dynamics GP Year End Procedure

2011-04-06T08:40:00.000-07:00

Year End Closing for Dynamics GP Module must be done in following order

A) Inventory

B) Receivable

C) Payables

D) Fixed Assets

E) GL Year End

GL Year End Close should be done after you have completed you Year End Closing for all above Module in above order.

Let see go Module wise Year End Close procedure and its affects.

A) Inventory

GOTO-->Tools-->Routines-->Inventory-->Year End Close

Inventory Year End Close affects

i) Transfers all summarized current-Year Quantity, Cost and Sales Amounts to last-year for the Items for which you have been keeping summarized sales history

ii) Updates each item’s beginning Quantity from the Quantity on hand at each site

iii) Zeros the Quantity sold field in the Item Quantities maintenance (Cards-->Inventory-->Quantities/sites) for each site

iv) Give you the Option to: Remove Discontinued Items, remove sold Receipts, Remove Sold Lot Attributes, and update Item’s Standard cost.

Key Points to remember while/before running Inventory Year End Updates

i) Enter and post all PO Processing , Invoicing/sales Order Processing and Inventory Transaction for the current year

ii) Follow KB872713- Describes how to close the year and how to prepare your inventory records for the new fiscal year in Inventory Control in Microsoft Dynamics GP.

iii) Restorable Backups of Production and as well as Dynamics Database

iv) Reconciles SOP and POP and IV Module .. Reconcile SOP,POP and Then Inventory.

Knowledge Base Reference

i) KB872713 Describes how to close the year and how to prepare your inventory records for the new fiscal year in Inventory Control in Microsoft Dynamics GP.

ii) KB855316 Inventory Accidentally Closed Twice

iii) KB872182 Inventory Year End Close Does Not Remove Discontinued Items.

B) Accounts Receivables
GOTO-->Tools-->Routines-->Sales-->Year End Close

Affects of Receivable Management Year End Close

i) Calendar year End Close clears the Calendar Year to Date Finance charges and moves them to the last year Calendar field in Customer Finance Charge summary(Cards-->sales-->Summary-->Finance Charges)

ii) The Fiscal year End close transfer all amounts other than the Calendar YTD Finance charge amount to the Last Year Column in Customer Summary using the Amounts since Last closed view(Cards-->Sales-->Summary)

Key Points to remember

i) Post all transactions for current year

ii) Keep Restorable backup

iii) Follow KB857444- Describes how to perform the year-end closing routine in Receivables Management. Contains preparation steps and troubleshooting information for the year-end closing routine.

iv) Receivable management is not completely date sensitive there are some date sensitive features. It would still be the best option to close the year on time

v) KB851140- Explains the effects of performing the year-end closing procedure in Receivables Management after December 31.

C) Payable Management Year End Close

Goto-->Tools-->Routines-->Purchasing-->Year End

Calendar year End Close Routine should be run at the End of the Calendar year prior to posting transactions in the New Year

The Fiscal Year End close Routine should be run at the end of the fiscal year Prior to posting transactions in the New year

What does not Payable Management Year End Close does

i) The Fiscal year End Close Process transfers all other amounts from the Year to Date column to the Last Year Column in the Amounts since Last Close view.

ii) The Calendar year End Close process transfers the 1099 Amount from the Year to Date Column to the Last Year Column in the Amounts Since Last Close view in the Vendor yearly Summary window (Cards-->Purchasing -->Summary-->Yearly button)

Key Point to Remember

i) Post all transactions for the current year

ii) Make sure transaction for the new year are saved not posted

iii) Make a backup

iv) Follow the KB 875169 -Describes how to perform the year-end closing routine in Payables Management in Microsoft Dynamics GP. This article also lists preparation steps and troubleshooting information for the year-end closing routine.

v) Payable Management is not fully date sensitive , so it sill still recommended that you process your Year End closing routine at the Actual Year End

D) Fixed Assets Year End CloseGOTO-->Tools-->Routines-->Fixed Assets-->Year End

When should the Fixed Assets Year End close to be done?

i) The Fixed Assets Year End close should be run after you close Payable management but before you close General Ledger

ii) You can close each book separately, but you must close all books before you can do any processing in Fixed Assets for the New Year.

What does the Year End Close Process do?

1) In the Asset General information Window (Card-->Fixed Assets--> General)

     a) YTD Maintenance amount is removed

     b) The Quantity is copied to the Begin Quantity field

2) In the Asset book window (Cards-->Fixed Assets-->Book)

    a) The YTD Depreciation Amount is removed

    b) Cost basis is copied to Begin year Cost

    c) Life to Date Depreciation is copied to Begin Reserve

    d) Salvage is copied to Begin salvage

    e) Increase the Current fiscal year by on Year for Each book that is being closed.

Key Points to Remember

1) Print all the reports that you need for the year that you are closing

2) Backup of Production Database

3) KB865653- Describes the year-end closing routine in Fixed Asset Management in Microsoft Dynamics GP. Also lists preparation steps and troubleshooting information.

4) You must take depreciation to the last day of the year that you are closing before you close the year

E) GL Year EndGOTO-->Tools-->Routines-->Financial-->Year End Closing

What does the year End close process do?

1) The Year End close process close all P & L Account out to Retained Earnings, Leaving the P&L Ac with Zero Balance at the beginning of the New year

2) All Balance Sheet Accounts are updated with the Beginning Balance in the New year which will be the same as the Ending balance from the Year you are closing

3) The Retained Earning Account is updated with Amount from All P&L accounts if you close to one Retained Earning Account or with the Amount from P&L Account in that division if you close to divisional Retained Earning Account. The Retained Earning Accounts are the Only Balance sheet Accounts that should have different beginning balance than the Ending Balance from the year that you closing

4) The year End close routine moves all open year transactions from the GL20000 to the GL30000 table

5) The Fiscal Period Table is updated to Mark the year that you are closing as Historical.

Key Points

1) Restorable Backup of Dynamics as well as Production Database.

2) Follow KB888003- Describes the recommended year-end closing procedures for General Ledger in Microsoft Dynamics GP.

3) Make sure you have enough space on SQL Server to allow GL20000 table double in Size.

4) Perform Year End at Server.

5) Have all user out of Dynamics GP when you perform Year End operation.

6) The Year Close Routine does appear to hang at 50% but is still running be patience.

Important KB to follow

1) KB871679 Describes how to set up an adjusting period to record adjustments that are posted to the general ledger after the year-end close process has been performed.

2) KB850615 This article describes how the divisional retained earnings accounts work in General Ledger in Microsoft Dynamics GP.

3) KB864913- Describes how to correct accounts that were set up to use the wrong posting type after the General Ledger year-end closing process is complete in Microsoft Dynamics GP.

4) KB850741- Discusses that you receive a "Retained Earnings account not found" error message when you try to perform the year-end closing process in General Ledger in Microsoft Dynamics GP. Provides steps to troubleshoot the problem.

5) KB857582- Discusses that the balances for all unit accounts roll forward after the General Ledger fiscal year has been closed in Microsoft Dynamics GP. Describes how to delete the beginning balances for the unit accounts.

Compacting a Microsoft FRx Database

2011-04-05T04:39:00.001-07:00

On the Company menu, click Specification Sets. The Specification Sets dialog box appears.
Note the location and file name for the Specification Set. Make a copy or backup of that file. Click Close.
On the Admin menu, click Organization. The Organization Information dialog box appears.
Click the SysData button. The SysData Directory dialog box appears.
Note the location of the SysData folder and click OK.
Browse out to the SysData folder and then make a copy or backup of the FrxSys32.mdb file.Verify that all other Microsoft FRx users have closed Microsoft FRx.
On the File menu, click Compact FRx Database. Select either Current Spec Set Database, FRx System Database or FRx Queue Database.
When prompted to Compact Now, click Yes.