GP 2010 Word Forms

The new Word Forms functionality in Dynamics GP 2010 is going to really be popular.  It allows you to modify the format of sales orders, quotes, invoices, and purchase orders in Microsoft Word.

The two things that I really like about it are:

• You can insert complicated graphics into your forms and they will look good.  That is just not possible with Report Writer.
• You can have as many different form templates as you wish so that you can assign a specific template to a specific customer or groups of customers.

I created a short video to demonstrate some of this new functionality.

Unsure About How Dates Are Calculated for MRP Planned Orders?

I find that many Great Plains manufacturing users do not use MRP effectively, or at all, because the release and due dates never seem to make sense. I realize that managing dates and then trusting the release and due dates from an MRP run can be a daunting task. That should not be a good excuse for not using a very powerful and effective tool.

Many users just use the default dates when creating documents that affect inventory and the manufacturing process because it is “too much work” to enter and manage the dates in Purchase Order Processing, Sales Order Processing and Manufacturing. I would argue that it costs users more in time and costs to not manage the dates up front and throughout the purchasing, sales and manufacturing.

How many times have you, as a user, had to track down a shortage, reallocate items to more urgent orders and correct errors? It is my belief as a former Controller and a current GP implementation consultant, that it cost you and your organization much more on the back end to deal with incorrect release and due dates than it does to enter and maintain meaningful dates in GP manufacturing. In fact, I feel so strongly about it, that I believe the savings would more than pay for an additional head or heads that may be required in your organization to maintain accurate dates.

When dates are used and managed effectively, issues that affect manufacturing and eventually shipping are identified quickly during an MRP run and MRP will even make suggestions on how to deal with the issues. MRP will include suggestions on moving orders in or out and cancelling orders that are oversupplied. Why should you study inventory levels via GP inquiries, reports and SmartLists when MRP will do it for you? Seems like a great time saver to me.

So where does MRP get the data to suggest release and due dates?

The due date is the date an order is due in house to meet the demand that created it. Due dates come from many sources including MO’s, MRP suggested MO’s, Sales Documents, Sales Forecasts, etc. The release dates suggested by MRP start with the due date of the document or MRP suggestion the item fulfills and works backwards, based on lead times and calendar down days.

MRP-Planned Manufacturing Orders

Let’s look at MRP-Planned manufacturing orders first. MRP looks at the lead times in the Item Resource Planning windows. The lead times can be entered here manually or generated from routers using the Calculate Mfg Lead Times utility. MRP will look to the item-site combination in Item Resource Planning. Since MRP suggests manufacturing orders for make item only, enter the lead times in days or fractions of days in either the Mfg Fixed Lead Time field or the Mfg Variable Lead Time field or both. MRP uses these fields differently as you might suspect.

• Mfg Fixed Lead Time – does just that, adds a fixed number of days to the MO when calculating the release date. The formula is Due Date – Mfg Fixed Lead Time. For example, if your forecast shows a suggested MO with a due date of 8/1/2010, the release date would be 5 days earlier or 7/27/2010 as long as 7/27/2010 is not a down day on your work center calendar.
• Mfg Variable Lead Time – is variable based on the quantity suggested. The formula is Mfg Variable Lead Time * quantity, rounded up to the next whole day. For example, if I have a Mfg Variable Lead Time = .01 and a quantity of 500, my lead time is 5 days.
• Total Manufacturing Lead Time for a make item is Mfg Fixed Lead Time + Mfg Variable Lead Time, rounded up to the next whole day. Mfg Fixed Lead Time & Mfg Variable Lead Time in Item Resource Planning.
• 
  
  

MRP-Planned Purchase Orders
If the item does not have a default site set in Item Quantities Maintenance, MRP will use the Purchasing Lead Time from the Item-Site combination in Item Resource Planning.

If the item has a default site set in Item Quantities Maintenance, MRP has two choices to select from.

• No Primary vendor selected for the default site – Purchasing Lead Time is from the specified default site in Item Resource Planning Maintenance window.
• Primary vendor has been selected for the default site – Purchasing Lead Time is selected from the item and vendor in the Item Vendors Maintenance window (Planning Lead Time).

I hope that this takes some of the mystery out of the MRP release dates and due dates.

Dynamics GP 2010 is on the Way

The next major release of GP will be Dynamics GP 2010.  Microsoft continues to design and deliver the product to be easier to use and to be a more effective business tool for getting things done and reporting results.

There are a number of functionality enhancements and richer connections with Microsoft Office and other Microsoft technologies.

We are presenting a sneak peek of the new version on March 24th.  Check out the details here.

This is an easy way to review the new release, so I expect you to be on-line with us on the 24th, 11:00 am – 12:00 pm PDT.

Go straight to the Click to Attend site here.

There will be a short discussion of CustomerSource immediately following, at 12:00pm.  Are you using CustomerSource?

Budget Import & Export

Dynamics GP has a very easy to use import and export function that allows you to create budgets in Excel and update budgets in GP, based on amounts you have in Excel.

All this functionality is available from the Budget Selection screen.  Navigate to:  Cards  >>  Financial  >>  Budgets

I created this short video to show this functionality in action.

One very important caveat:  Make sure that you validate the information in GP after importing or updating budget information from Excel.  There is no error reporting on the import function if the import does not properly import the data.

I usually create a quick FRx report for this purpose.  But you could also simply export the information from GP, to a new spreadsheet (make sure not to overwrite your original spreadsheet).

Simple Formula to Extract Specific Data from a List in Excel

I recently discovered the “SUMIFS” formula in Excel that I think you’ll like because it makes it easy to select specific data from a data list in Excel.  Excel Reports for GP is a great way to extract data from GP and report on it.  Because the resulting Excel spreadsheet includes a data connection to the GP database, you can format the spreadsheet and refresh the data as you wish.

Typically I have used the pivot chart, and graph functionality in Excel to create the reports I want.  But the “SUMIFS” formula allows me to have more control over the reported results and format.  This is how I generally use the formula:

Define range names for the data you want to report on.  In Excel: 

• Select the column with the data you wish to name
• Formulas  >>  Define Names

Enter the formula to select the data you want:

• Select the range that includes the data you want (e.g. Extended_Price)
• Select the range that includes the values you will select
• Select the specific value that corresponds to the data you want to display

The result:

See the formula in the formula bar on top.  In this case I used a relational reference to the criterion I used, B17.

Try it out.  It will give you a lot of control over the data you can select and how it is formatted.

Integration - All About Attitude

The possibility of an integration is rarely due to the technology. Most people would agree, but qualify possibility with a budget. With that said, even with great technology, skilled professionals, and adequate budget, integrations can still fail.

I think the reasons boil down to attitude and behavior:

1) Building from the bottom up: Avoid diving directly into topics such as field mapping and data exchange mechanics. Initial conversations should include high level topics like division of labor, project goals, expectations and business processes. High level decisions will alter the low level details.

2) The integration will do all the work: Integrations make work life easier by altering roles and responsibilities - not by removing them. Instead of entering data, we are now monitoring it. People will always be involved.

3) Lack of functional understanding: I have walked into situations where a client has an integration, with little to no knowledge of what it is actually doing...talk about dangerous! Documentation is one method for keeping knowledge in house and maintained. Another method involves training and practice: software reliance can be reduced and understanding can be increased by having people perform the processes manually.

4) This is how we have always done things: Any implementation project should be viewed as an opportunity to better a process...not re-invent it. When it is time for the company to adapt and grow, the integration should be prepared. Conversely, integrations built out of tradition lead to rigid processes and logic. What happens when business changes? You may have to re-implement the integration.

5) Oversimplification: There are plenty of simple integrations in which we just map a few fields and move some data, but this is not always the case. As a colleague of mine likes to say, "The devil is in the details." The devil is not very forgiving.

6) Haste: In most scenarios, time is on our side. Remember to take the integration through a sound SDLC, complete with client QA. It is a lot more expensive to clean up an integration than to just wait for it to be correct.

7) Fancier is better: Adding complex decision logic and transfer mechanisms (real time versus manual, etc...) may not actually make an integration better. There are actually legimate reasons to simplify an integration. Those reasons may include maintainability, stability, and flexibility.

People dictate the success of a project, and we should believe that technology and knowledge are never the limitations. The only limitation is human ingenuity, which is something we can control through our attitude and behavior.

"Respond intelligently even to unintelligent treatment." - Lao Tzu, Tao Te Ching

Great Plains Integration Requirements

Welcome to my first Rose Business Solutions blog post. For my first series of postings, I thought I would cover a topic near and dear to every developer working with Great Plains: Integration.

Software is now an integral part to operating a business, and many companies are tracking information in multiple systems, each with its own purpose. Much of this information has a dollar amount associated to it, which means it should probably end up in the ERP system.

There are many tools to choose from when implementing an integration; each has its own set of strengths and weaknesses. Ultimately, the solution choice is made based on the project budget, but what are some of the other factors that impact our choice of tool, and ultimately solution?

The answer: Requirements.

Over the course of implementing several integrations, I have compiled a list of requirement topics that are evaluated whenever an integration project arises:

1) Logistics: How exactly will the information get from point A to point B?
2) Security: Who has access to the integration? How sensitive is the information being transferred?
3) Tool Availability: Does a tool exist to help perform the integration, or are we starting from scratch?
4) Division of Labor: What are we responsible for? What is the client responsible for? What are third parties responsible for?
5) Automation: User driven, scheduled (how often) or real time?
6) Integration Points: What types of transactions are we integrating?
7) Integration Process: Where does the process begin? What happens with the data in GP before feedback? When does the process end?
8) GP Module Complexity: Are we integrating to the GL? Simple...Or are we integrating to Project Accounting? Not as simple...
9) Integration Volume: How much data will be transferred?
10) Field Mapping and Translation Logic: How many fields are mapped between systems? How difficult is the system translation?

Whew...I better stop before this gets too wordy. There are probably other factors to consider when deciding on an integration tool, but I think this list of ten is a good start. In my next few articles, I plan on drilling in on some of the tools and discussion some of the common mistakes. Until then, take care!

"Though we have heard of stupid haste in war, cleverness has never been seen associated with long delays." - Sun Tzu, The Art of War

Account Rollup Inquiry

The Account Rollup Inquiry screen allows you to summarize information from several accounts, and display information of several types, including: Actual, Budget, Prior Years, Other Currency, and Calculated.

Here is the summary level inquiry:

Here is the first drill down on the actual number that shows the accounts included in the rollup summary:

I created a short video to show this functionality.

Cash Flow Forecast

This is a screen in Dynamics GP that I suspect gets little use.  But it really can be quite useful because it gives you a time sequenced view of your payables and receivables, and allows you to drill down to see the detail records.

This is the basic screen:

If you click one of the days, it will bring up the Cash Flow Explorer that will allow you to see the details:

The set up is very easy, and allows you to create several “profiles” so you can take different views of the information in your system.

I created a short video to show this functionality.

Requisition Management

Requisition Management is an easy to deploy and easy to use system that allows you to automate parts of your purchase requisition process, and integrates directly to GP.  Requisition Management is included in the Advanced Management version of GP.  It does require the deployment of Business Portal.

The set up is fairly straight forward, requiring the following configurations:

• Company defaults
• Approval hierarchy and approval limits
• Business Portal role assignment to users

I created a short video to walk through part of this process.

Requisition Management is also fairly easy to use and integrates directly with GP, creating PO’s for approved requisitions.

The process is essentially this:

• Create a requisition, and submit for approval
• Approve the requisition, and submit to purchaser
• Final review and approval, and automatically create PO in GP

I created another short video to show this process in action.

There are generally two shortcomings I come across when determining a good fit for Requisition Management:

1. For any given requisition creator, there is only one available approval routing.  The system cannot be configured to automatically route a requisition to different approval paths depending on what is being requested, e.g. a laptop computer request would not be routed differently than a trade show attendance request.  This can be somewhat mitigated by allowing requisition creators to select who will approve their requests, but then this defeats a common control that organizations look for when considering a requisition system.
2. A requisition with multiple lines has to be approved, rejected, or deleted in total.  There is no ability to manage these processes on an individual line basis.

But with that said, if an organization is wishing to replace a manual requisition process, Requisition Management is a good first step.

Combining budgets in Dynamics GP 11.0

Following the superb example of Steve Chapman I decided to discuss some new features of Dynamics GP 2010 by video.

Click here if you would like a demo of how to combine budgets in GP 2010 beta version.

Make sure you veiw the video by the highest quality 720p (HD).

I'm taking requests. Let me know if there is anything you'd like a demo on and I'd be happy to publish it on youtube.com.

My favorite blog entries

After posting my last blog which was an update of an older post on  top technical support issues I cited that the article was a very popular blog but it wasn’t one of my favorites to write. After seeing Mariano’s Best blogs of 2009 I started thinking about my favorite blog entries over the past couple of years.

Below are a few of my favorites:

• Steve Chapman’s admission to how old he is
• New Roseling announcement with potential baby names
• What kind of training is most beneficial? I’m not sure if I followed up on this one or not. I guess I’ll do a future post on this
• How long…before applying new SP’s? Dedicated to Rebecca Bunas from our office who is an avid U2 fan
• Should you back up your database before posting payroll? I love horror stories from the trenches and this was a fun one. Here is another great “You should back up” blog
• To upgrade or not to upgrade – we were going to upgrade this client last month then they put it off for another month. Maybe by this time next year they will be ready for 10.0 and decide why not redo the whole upgrade plan for Dynamics 2010
• VAR versus Partner – I wax philosophical
• The Famous David Musgrave – True story
• Dynamics as a second language – probably my favorite one to write

I’ll hopefully add to this list as time goes on.

Dynamics GP Top Technical Support issues

Writers comments: This is an updated version of a post I did back in February 2009. This has continually been one of the most popular articles on our humble blog since I wrote it. I wouldn’t consider it one of  my favorite blogs but quite a few people seem to have found it useful.

****

I was asked what issues I deal with the most often. I'm sure there are many others but these are the first ones that come to mind along with the resolutions below.

Here's my Top support issues list in no particular order:

1. Batch stuck in posting, receiving, etc. status
2. Where do I find the table that holds a particular set of data?
3. My sub-module doesn’t tie to the GL
4. How do I set up a new fiscal year?
5. I can’t login to Dynamics – Unknown dictionary error
6. How do I import budgets?
7. Dynamics won’t let me post
8. I have a metrics error on my homepage
9. How do I move Dynamics to a new server?
10. After closing the GL I realized I have incorrectly listed a BS account as a P & L account, now there is not beginning balance. (or vice versa)
11. How do I adjust then print 1099’s?
12. When trying to access sales transaction entry I get the error "Your previous transaction-level posting session has not finished processing".
13. Inventory shows it is allocated when it’s not
14. I don’t have beginning balances in my balance sheet accounts for the new year
15. After applying a SP my reports will not print and GP crashes

Resolutions:

1. Doug Pitcher blog post - http://www.rosebizinc.com/gpblog/2009/01/stuck-batches-in-dynamics-gp.html. Dave Musgrave comment gives script that works well.
2. Blog post by MBS employee Dave Musgrave. http://blogs.msdn.com/developingfordynamicsgp/archive/2008/10/05/finding-table-and-field-information-in-microsoft-dynamics-gp.aspx
3. See Steve Chapman post-http://www.rosebizinc.com/gpblog/2008/02/reconcile-to-gl-easily.html
4. See Doug Pitcher blog Post- http://www.rosebizinc.com/gpblog/2009/07/setup-new-fiscal-year-in-dynamics-gp.html
5. Usually permissions error when network ID doesn’t have access to reports.dic file. Find path in Tools>>setup>>system>>edit launch file>>enter system password>>Highlight dynamics GP, look to see where Reports line is pointing to. Open a browser and try to path to this location. Need
6. Cards>>financial>>budgets. Use import wizard by choosing New>>using budget wizard for Excel.
7. Print edit list of batch (printer icon at top right hand corner of batch window). This will tell you why you can’t post
8. Tech doc: 918313. Install Office Web Components link, question and answer #21.
9. Doug Pitcher blog: http://www.rosebizinc.com/gpblog/2008/08/moving-sql-to-new-server.html
10. Tech doc #864913
11. Doug Pitcher blog: http://www.rosebizinc.com/gpblog/2010/01/1099-for-dynamics-gp.html or http://www.rosebizinc.com/gpblog/2009/01/dynamics-gp-1099-printing-for-90-and.html
12. Tech doc #852623. Run scripts to release captured user.
13. Run inventory reconcile at Tools>>utilities>>inventory>>reconcile. Everyone needs to be out of GP (well sop, pop, inv or any module that touches inventory)
14. You need to close out the year in GP. If you are not ready to do this and need a BS follow directions found here: http://www.rosebizinc.com/gpblog/2009/02/no-beginning-balances-in-frx-balance.html
15. Recreate the reports.dic file. See blog post - http://www.rosebizinc.com/gpblog/2010/02/recreating-reportsdic-in-dynamics-gp.html

I'd be interested in seeing your most common lists of frequently tackled issues in GP. Any issues come to your mind other than the ones above?

Recreating reports.dic in Dynamics GP

Can I come up for air yet? Talk about a busy month. January is always crazy but for some reason it seems this past month has been extra intense. Now that Year end closes are coming less frequent and 1099's, W-2's etc. should be about done maybe I'll be able to call in sick a time or two and head up to The Big.

One common issue I've seen rear it's ugly head is not being able to print reports after applying a SP or Year End update. GP will either crash before the report is done or will error out and not give you a report. Is it me or has SP's and Year End Updates continually gotten more difficult over the years? I don't even waste time with trying to update the Reports.dic file anymore. I go simply to recreating. Here is the process:

Method 1

1. Make a backup of reports.dic
2. Go to Microsoft Dynamics GP>>tools>>customize>>customization maintenance
3. Highlight all reports and choose export. Export this out to a package file
4. Have everyone get out of GP
5. Delete the reports.dic file
6. Log into GP again and go to GP>>tools>>customize>>customization maintenance
7. Choose import and select the package file created in step 3

Method 2

1. Make a backup of reports.dic
2. Delete reports.dic (or rename reports.dic path to reports2.dic in dynamics.set if you don’t want to kick everyone out of GP)
3. Log into GP and go to Microsoft Dynamics GP>>tools>>customize>>report writer
4. Choose Import on the right hand side of the reports menu
5. Browse out to the copy of the reports.dic file created in step 1
6. Insert each report (makes you do it one by one)
7. Choose import
8. If you created a reports2.dic file in step 2 rename the file back to reports.dic

Method 2 allows you to recreate without having everyone get out of GP. However, you most likely will have to get everyone out to rename the file back to reports.dic in step 8 of method 2.

Outsource your Manual Payables and Receivables Functions

This week I was given the opportunity to see the offering from Enliven Software that can help you streamline your payables and receivables functions using Dynamics GP.

Enliven Software has developed a SAAS offering that is very tightly integrated with GP.  They use Dexterity to add buttons in familiar GP screens that seamlessly extend GP functionality for common manual processes, to their hosted solution; adding well thought out and comprehensive automation.

For example:

• Provides automated workflow approvals for payables invoices
• Payables invoice capture from various delivery methods, including e-mail, fax
• Payables invoices can easily be scanned, indexed, and stored using OCR technology
• Send payments via ACH/EFT
• Provides an out sourced service to print, stuff, and mail payables checks
• Send sales invoices and statements via e-mail or fax, and automatically provides reminders to customers
• Accept payments electronically from a variety of payment types
• Provides a customer/vendor portal to improve communication

If you want to streamline your payables and receivables functions, automate current manual processes, and store documents electronically, this is a comprehensive solution.  To take a quick peek at this functionality you should check out the videos on these pages:

Accounts Payable

Accounts Receivable

Pay special attention to the integration with GP.  They’ve done a good job.

Multi-company SmartLists

Here’s a nice little option in SmartList Builder which I’m surprised few people know about.  SmartList Builder allows you to create SmartLists that can report information from multiple companies in one list.

We have several real estate companies and family office clients that have dozens of GP company databases from which they want to report on rather simple things, e.g. all bank accounts, all fixed assets.  SmartLists is perfect for this type of reporting.

To have a SmartList look at multiple companies, go to the “Options” button, check the “Multicompany SmartList” check box, and select the companies you want included.

Here’s an example of a multiple company bank account list:

The problem in this solution is to find a field in the data that identifies the company to which the results belong.  In my example, this is easy because the CM Checkbook Master table includes the Company ID field that can be linked to the Company Master table, to return the name of the company.

I found this query on CodeSnippets to find all the tables in the company database with the column name “CMPANYID”

SELECT table_name=sysobjects.name,
column_name=syscolumns.name,
datatype=systypes.name,
length=syscolumns.length
FROM sysobjects
JOIN syscolumns ON sysobjects.id = syscolumns.id
JOIN systypes ON syscolumns.xtype=systypes.xtype
WHERE syscolumns.name='CMPANYID'

These are the results:

CT00001
FA49900
CT00002
SOPS113B
RM50103
CT00003
SY00600
POPS0231
JCPS0040
POP10100
PRPF0113
UPR70501
DD40400
QAPS0032
QAPU0032
AAG00906
POPF0113
POPS0132
CO010000
ECPS0000
COSS0401
ECPU0000
ENC40000
ENC40100
RM30701
POP30100
mops0100
MOPS0200
CM00100
EC090000
WCPS0100
MRP0200
BMPF0114
BMPS0114
SVC40500
CAM10210
GTM41000
SY04800
MPPS0230
CAM10200
MPPU0130
WCPF0100
TLPS0100
TLPU0100
RVP0100
RVPS0132
CPO40001
CPO40002
WPPS0114
WPPU0114
PAVW10600
RTPS0130
RTPU0130
PAVW30600

If you have SmartList Builder and several GP company databases, you should try this out.

1099 for Dynamics GP

I've been really impressed with a lot of our clients this year. I usually don't start the 1099 rush until January 30th but I have been getting a lot of calls already about the 1099 process. I did a blog last year about 1099's found here. This is a good overview of the 1099 process.

A couple of comments about the 1099 process that I've come across this year are listed below.

1. I find it easiest to look at the yearly summary (still under Cards>>purchasing>>summary>>yearly tab>>change to calendar year view) and see how much was paid during the year versus the 1099 amount
2. To edit the 1099 amount it will have to be done in the 1099 detail window
3. If you only see zero's on your edit list you need to install SP2 or higher for 10.0
4. If you have a vendor listed as 1099 and it shouldn't be, delete the amounts in the 1099 window before changing the status to be "Not a 1099 Vendor". It will still show up on your 1099's otherwise
5. If you have a vendor listed as dividend and not the usuall miscellaneous you will have to zero out all dividend amounts and replace it in the miscellaneous window in the 1099 detail window
6. If you haven't listed the vendor as a 1099 vendor you will have to edit the amounts in the 1099 detail window as it doesn't go back and calculate for anything previous to the change
7. The minimum amount setting is under payables setup (Microsoft Dyanmics GP>>tools>>setup>>purchasing>>payables>>1099 setup). This used to be in the print 1099 window.
8. If you have a vendor that was paid $600, change the minimum in payables setup to be $599.99 or no 1099 will be printed for that vendor.
9. For 9.0 and before you edit 1099 details in the period view (cards>>purchasing>>summary>>period tab)
10. GP does not produce the 1096 summary form. Go figure.

Anyone else come across 1099 process issues not listed above?

Creating Custom Word Templates using the Letter Writing Assistant

You may have used the standard Letter Writing Assistant templates that come out-of-the-box with GP, that allow you to create Word documents from SmartList data.  There are actually some nice ones that I like to show when I demo GP.

But you can also modify the standard templates, and create your own.:

• To access the Letter Writing Assistant, navigate to:  Reports  >>  Letter Writing Assistant
• Select, “Customize the letters by adding…”
• Select the letter category that corresponds to the SmartList from which you want to pull data
• Select one of the four options available
• Select the document or action in the window:

• Word will then open, with a blank document or the existing document you identified
• Select the “Add-Ins” tab from the Word menu
• Move the cursor to the spot on the Word document, at which you want the added field to appear
• Select the field

• The selected field(s) will then be added to the Word document
• Save the Word document
• Cancel the Letter Writing Assistant

You’re now ready to use the Word template with SmartList.  The template will show up with the appropriate SmartList on the Word drop-down tab.

It’s easy to do.  Try it out.

I recorded a quick video that shows this in action.

Multiple Site MRP Calculations in Dynamics GP

Dynamics GP can easily be used to manage inventory demand and supply for multiple inventory locations. By using separate sales forecasts, the MRP functionality in GP can separately analyze forecasted demand, and suggest manufacturing orders and purchase orders to fulfill the demand.

This video shows this functionality in action.

Adjusting Standard Costs in Inventory Control

Generally our clients who use the standard cost method to value inventory, use the Manufacturing module; and standard costs are easily managed in that module.

However the Inventory Control module can be used to accurately maintain and track standard cost items using the FIFO Periodic and LIFO Periodic Valuation Methods.  Unfortunately the steps to adjust standard costs is a bit quirky.  There is not a dedicated function in GP that allows you to specifically identify the standard cost items that you want to adjust.

There is a function in the year-end close routine for Inventory Control (Tools  >>  Routines  >>  Inventory  >>  Year-End Close) that allows you to automatically adjust standard cost to the current cost for all FIFO Periodic and LIFO Periodic items.  This however does not allow you to select which items to update, what the new standard costs will be, and does not create a journal entry to revalue existing inventory in the GL; so really it’s useless.

The following is my preferred process:

1)  Run a Stock Status report before any changes are made to show the inventory values with existing standard costs.

2)  Change the standard cost for every item you want to change.

3)  Run a Stock Status report after all the changes are made to show the inventory values with the new standard costs.

4)  At this point you could enter a journal entry for the difference in inventory value as reported on the Stock Status reports, and you would be done.

But what I would do, is take the alternative step of adjusting the costs by using the Inventory Adjust Costs screen.  Navigate to this screen:  Tools  >>  Utilities  >>  Inventory  >>  Adjust Costs

Select the items and enter the new standard costs for all receipts, and Process:

This will update the receipt records and print the information you need to create adjusting GL entries. 

If you use the Purchase Receipts report for any of your reporting, you will want to do this step; otherwise the new standard costs will not be in the report.

Temporarily Disable a Product in GP

From time to time I want to disable some functionality in GP in order to make a demo more streamlined (e.g. disable Analytical Accounting) or to test some functionality without a specific product in the system. 

For example, I was recently testing the Inventory Control module to find out how it handles changes in standard costs.  I wanted to disable the Manufacturing module so I could get just the Inventory Control module functionality working in my system.

It’s easy to do.  To temporarily disable a product, navigate to:  Tools  >>  Customize  >>  Customization Status.  This brings up the Customization Status screen.

Select the product you wish to disable, and click the Disable button.  This will disable the associated functionality until you re-launch GP

If you want to disable the product for a longer period of use, check out KnowledgeBase article # 872087

Microsoft Dynamics GP - Year End Payroll Update

The time is at hand for review and consideration of the payroll year end process for Great Plains. This year (as in 2008) the year end update involves a service pack installation. In other words, this year end update will change the Microsoft Dynamics version number and more importantly, it must be installed on the server (where it will update tables and stored procedures), then it must be installed on each workstation running Great Plains so each workstation “synchronizes” with the same version as the server. Depending upon the size of the database(s) and the number of workstations, this can take a few minutes, or several hours.
I am not overly found of how Microsoft deals with the Year End Update, especially since the timing for installation is always difficult at year end (re: holidays, scheduling, vacations, parties, etc, etc). Keep in mind the basic timing required for completing the year end processes successfully.

1. Make sure all 2009 pay runs are complete. This means all payroll checks and direct deposits with a date on or before December 31, 2009 have been run. Many companies will set a date after which no payroll checks are allowed to be prepared. Another way of saying this is don’t fire anyone after the cut-off date so you don’t have to provide a final check. Also, don’t wait till the last minute to issue bonus or holiday checks. Anyone still remember those?
2. Install the Year End Update. Remember, this is a Service Pack and can take time. It will probably involve the IT Department or your friendly neighborhood Great Plains consultant (all of which have holidays, vacations, parties and such on their schedules). It is also a good idea to have your Accounting Department verify all is well after the Year End Update install (accountants don’t generally have holidays, vacations and parties as they like to work all the time and don’t have many friends).
3. Create the Year End Wage File. This is the file that your W2s are dependent on. If this file is not created successfully your W2s will not be available for distribution. Not having W2s ready for distribution to employees can get really, really ugly, not to mention how the IRS feels about missing distribution deadlines (I have heard stories about them coming to get first born children after a deadline is missed, but I am pretty sure they are just stories).
4. Setup fiscal periods for 2010. This is pretty easy and has probably been done already, in fact it can be accomplished at any time. If you have rent checks due on January 1st, you have found out you cannot enter the invoice for payment without the 2010 fiscal year in place.
5. Install the 2010 Payroll Tax Update. This is not the same as the Year End Update. The Year End Update is nasty, this one is easy (at least for now it is, maybe Microsoft will change that next year). Once you install the 2010 Payroll Tax Update, you can run your first pay run for 2010. One thing to keep in mind is that the “Calculate Checks” function is when the new 2010 tax tables are accessed. You must install the 2010 Payroll Tax Update before pushing the button for Calculate Checks. If you run a 2010 pay run before creating the year end file, you are screwed (unless you have a backup and then all you have to do is restore the backup, reinstall the last 2009 payroll tax updates, create the year end wage file, reinstall the 2010 payroll tax update and then re-run your 2010 pay run). You really, really don’t want to do this, so make sure someone that can at least walk and chew gum at the same time is keeping track of things.

If you read the Payroll year-end checklists from Microsoft (and I highly recommend that you do so) you will find that they have 17 steps compared to my 5. Some of their stuff is optional (such as closing the 2009 fiscal year or deleting inactive employees). Other items are just plain not possible like “Step 12 Prepare and submit W-2 information in the federal EFW2 format, if required.” No one submits this stuff until it is nearly due and it has been reviewed, scrubbed and reviewed again, that is unless you are not fearful of discussing non reconciling items with the IRS, but then again maybe you don’t much like your first born child.

If you haven’t guessed by now, the payroll year end close can be somewhat intimidating if this is your first time. There are several backups listed in Microsoft’s checklists. Don’t try to save time by not doing the backups. If you have backups, your “you know what” can be saved. Without backups, I am not sure. Your boss just may shoot you.

Simple Dashboards Using GL Summaries and Excel Reports for Dynamics GP

This video shows how to quickly create a dashboard that pulls information from the Dynamics GP general ledger and displays it as three separate graphs on one worksheet.

This is a good example of how to take a large amount of transactional data, summarize it, and present it in a graphical manner.

SmartList Export Solutions in Dynamics GP

If you’re using SmartLists on a regular basis to report on information in Dynamics GP, you’ll want to learn how to use the Export Solutions functionality within SmartLists to add charts, pivot tables, calculated fields, and additional formatting to your data.

Export Solutions allows you to run an Excel spreadsheet macro on the data that SmartLists exports to Excel.

These are the basic steps to set up the macro:

• Export a SmartList to Excel
• Start and name a new macro in Excel
• Perform the formatting you want in the Excel spreadsheet
• Stop the macro
• Delete any worksheets you may have added during formatting
• Delete the data that was initially exported to Excel
• Save the Excel spreadsheet as a template

These are the steps to attach the spreadsheet with macro to SmartLists:

• Navigate from SmartList:  SmartList  >>  Export Solutions
• Document: Select the Excel spreadsheet that contains the macro you wish to execute
• Works for Favorites: Select the SmartList(s) you want the Export Solution to be available with.

Once the Export Solution has been attached to the SmartList(s), you can use it when you wish.  Just make sure to select it from the menu drop down, and not “Quick Export”:

I’ve created a companion video to this on YouTube.

Technorati Tags: Export Solutions,Dynamics GP,SmartList

Make Use of the Source Document Field on Journal Entries

The Source Document field is a required field on a General Ledger journal entry but people rarely pay any attention to the field because it defaults to “GJ” for “General Journal”, which meets the basic criteria.  GJ is certainly acceptable for a General Ledger journal entry but you could expand on that code to make it more  meaningful and therefore provide another option for reporting transaction detail.  The Source Document field is a field you can place a print/search restriction on for standard GL reports, GL transaction inquiries, and smartlists.  Therefore, if you do a number of journal entries for the same purpose/event, you could assign them the same Source Document and then later do a search/print restriction on that specific Source Document code.  For example, if you have to do some post year-end close journal entries, you could create/assign a source document of “GJ-PCADJ” for “General Journal – Post Close Adjustment” to those journal entries.  Subsequently, you could easily run a smartlist of all the post closing adjustments by doing a search of Source Document = GJ-PCADJ.  You can create as many Source Document codes as you like.  I recommend that you start each new code with “GJ” in case you should want to run a report/smartlist on all journals that originated in the GL, you could easily pull all those that start with “GJ”.

 

To create a new Source Document code, you can type it into the Source Code field on the Transaction Entry window:

Dynamics GP will then prompt you to add it:

Enter the appropriate title and click the Save button:

 

Please note:  If you select/view an un-posted journal entry that has any Source Document other than GJ (for example, CMTRX, PMTRX, PMCHK, RMSLS, etc), do NOT change the source document.  These source document codes indicate that the journal entry originated from a subsidiary module and from which subsidiary module.  Also, when you are entering a General Ledger journal entry, do NOT use these pre-defined source documents, because that would make your journal entry misleading as to where it originated from.  If you are unsure which Source Documents are pre-defined and which ones are custom, you can view the pre-defined ones on the Audit Trails Setup window (Tools>Setup>Posting>Audit Trails).

The Confusing Name/Title of the Distribution Reference Field

Every now and then, I find that a Dynamics GP user wants to show the Distribution Reference field on a smartlist or on a modified/custom report but they weren’t able to because they couldn’t find the field to add it.  For some strange reason, the title of this field is, “Description”.  So the next time you want a smartlist of GL account transactions with the Distribution Reference field displayed, add “Description” as a column.  And, you can change the column header to prevent any further confusion by typing in “Distribution Reference” in the display name area:

Removing Discontinued Items during Inventory Year-end in Dynamics GP

As a part of the Inventory year-end process in Dynamics GP, there is an optional feature to remove discontinued items.  Although this option may sound like a nice “house-cleaning” feature, proceed with caution!  Not only is the item removed from the Inventory Master file, all of the inventory historical transactions for that item will be gone too.

If this box is marked when the Inventory year-end process is performed, any item that meets the following criteria will be removed from the Inventory Item Master file:

1.  Item Type = Discontinued

2.  0 quantity on hand

3.  Not on any un-posted inventory, PO, or sales transaction

The reports and windows within the Inventory module will show as if the items removed never existed.  You will be able to see the items on the historical sales and purchase order transactions but you won’t be able to see them anywhere in the Inventory Module.  If you recently discontinued and item, you may still want to see the inventory activity for that item for a while.  In which case, you would NOT want to select this remove option.  A better/safer method would be to manually delete a discontinued item sometime well after you stopped selling/using it and you are sure you no longer need/want to view it in the Inventory module.  (When you are sure you’re ready, you would bring up the discontinued item on the Item Maintenance window and click the Delete button.)

I discuss this closing feature along with many other Dynamics GP year-end closing features in our “Prepare for Year-End Processing” class.  The class is a half day, information-packed class held numerous times in December.  Checkout the training schedule on our website at http://www.rosebizinc.com/training/classes.asp for exact dates and times.  Register soon, year-end will be here before you know it!

When to unmark the Account Entry Checkbox

A few versions ago, Microsoft added a little checkbox to the the Account Maintenance window in Dynamics GP called “Allow Account Entry”.  Even though this checkbox has been around for a while, I’ve found that many Dynamics GP users do not know what it is for and how to make use of it.  If this checkbox is marked, users can manually select/enter the account on any transaction in Dynamics GP.  If this checkbox is NOT marked, users CANNOT enter/select the account on any transaction throughout Dynamics GP; the account can only be used on a default basis.  Therefore, you can use this feature to prevent users from entering accounts that never should be manually updated.  By default, the checkbox is marked.  I recommend that the box be unmarked for Accounts Payable, Account Receivable, Accrued Purchases accounts and possibly inventory. 

If you’ve ever had the unfortunate experience of spending hours reconciling a General Ledger control account to the corresponding subsidiary and finding that the difference in the balances was due to transactions on which the control account was manually entered, you will welcome the opportunity to stop users from entering such transactions.  If there is an unusual circumstance in which the subsidiary is right and the GL is wrong, you can temporarily mark the checkbox, enter/post the correcting entry, then unmark the checkbox. 

 

Happy Reconciling!

Dynamics GP 10.0 Year end update

I see the year end update has been released for Dynamics 10.0.

Is it that time of year already?

Looks like SP 4 will be installed with the year end update if that hasn't been installed already. Probably be a good time to make sure you are up to date on SP's to speed up the year end update process.

Dynamics GP User Group Meeting

On October 28 we held a Dynamics GP User Group meeting at the Microsoft office in San Diego. And on November 10 we held a Dynamics GP User Group meeting at the Microsoft office in Irvine. I thought I'd share with you some of the highlights.

Dan Youngers, a Partner Technology Specialist at Microsoft, presented us with a brief look at GP 11; specifically a demo of the new Word forms functionality. Looks a lot better than Report Writer (not that there's anything wrong with Report Writer).

Dan also shared with us the GP Roadmap.


The consulting staff at Rose Business Solutions presented six sessions that covered various areas:

Tech Talk with Tom

Tom Celvi discussed several issues related to customization and integration development:

RBS uses a defined, two-phase development cycle

Add customization to fill Great Plains gaps when process changes are not appropriate or efficient

Customization and Integration Tools for Great Plains

• Modifier w/VBA - A GP Product Requiring a GP Instance
• eConnect - Microsoft’s Integration Engine
• Web Services - For web, distributed, and interoperable solutions
• Visual Studio GP Toolkit - For nearly any client functionality
• Dexterity Platform - The platform tool requiring specialized knowledge with superior access to resources

Analysis Cubes with Excel (Analysis Cubes Video)

 

SmartList Builder & Smartlist Tips & Tricks

Mike Feori covered these subjects:

SmartList
SmartList Options- Change Basic Defaults
SmartList Searches- Match All, Match One or More
SmartList Export Solutions- Adding Macros

SmartList Builder
Functionality – Joins, Calculations, Restrictions
SQL Views- Existing
SQL Views- Adding New Ones
Imports & Security – Necessary for Use of New Views

Attendees were particularly intersted in:

How to locate SmartList defaults to change/set default "Go To" screens and default record count (it doesn't always have to be 1,000). Navigate: Microsoft Dynamics GP >> Tools >> Setup >> System >> SmartList Options

How to use the “match 1 or more” feature in SmartList.

 

Distribution Series - Inventory, SOP, POP Tips & Tricks

Steve Johnston covered a lot in a short time:

Creating PO’s from Sales Orders
Printing Customer Items on SOP Documents
Back Orders - Document vs. Line Item
Purchase Order Approvals
Returns vs. Credit Memos
Inventory Valuation Methods
How Item Types affect inventory
In-Transit Transfers
Expensing purchases of inventory items
Do Account distributions matter?
Reconciling Inventory to the GL
Historical Inventory Trial Balance
Historical Stock Status Report
Smart Lists

The most discussed items were:

How to create PO's from Sales Orders

In-Transit Inventory functionality


Reconciling to the GL

Liane McIlraith walked through how to reconcile A/R and A/P to the General Ledger. Good stuff:

Use Historical Aged Trial Balance report with Print/Age as of date = period-end date and based on G/L post date to get the subsidiary balance.

Get the G/L balance of all A/P or A/R accounts on Summary Inquiry window or Summary Trial Balance Report. (If there are multiple accounts, use the report.)

Navigation:

To access Payables Historical Trial Balance report:
Reports>Purchasing>Trial Balance>Historical Aged Trial Balance

To access Receivables Historical Trial Balance report:
Reports>Sales>Trial Balance>Historical Aged Trial Balance

To access SmartList of G/L account transactions:
Microsoft Dynamics GP>Smartlist>Financial>Account Transactions


Finding Differences:

Check for un-posted transactions in the G/L.
Determine when the accounts were last in balance.
Use the Financial Reconcile tool (v10 only).
Search for the difference amount in SmartLists.
Search G/L SmartList for unusual transactions.
Compare SmartList of G/L account transactions to the Payables/Receivables Distribution Detail report (print the report to a tab delimited file).

These are the attendees feelings:

1) The Reconcile to GL tool in v10 – saves users lots of time because it compares GL distribution detail to the Payables distribution detail
2) Unmarking the “Allow Account Entry” box for the A/P, A/R, and Cash accounts helps prevent differences between the subsidiaries
3) Dynamics GP doesn’t allow you to post subsidiary transactions through GL without a batch


SSRS & Excel Refreshable Reports


Tom Celvi and I covered implementation and use of two strong reporting tools:

So what is SQL Server Reporting Services with Dynamics GP?

A free product that ships with Microsoft SQL Server to provide enterprise reporting capabilities on ANY SQL Server database(s)
SQL Server 2000, 2005, and 2008
GP10 SSRS product only compatible with SQL 2005 SP2 or later and SQL 2008

SSRS Includes the following components:
Report Manager (The user interface)
Website used to run, deploy, and manage reports
Report Server (The services)
Accesses the Microsoft reporting engine to generate reports

Provides necessary logic for administering and managing the report site

We showed some of the reports available. A complete list.

We also did a quick demo of how to use the Report Builder.

So what are refreshable Excel Reports?

Only available in GP version 10.0
Over 200 standard reports
Based on SmartList favorites
Report Builder included with SmartList builder
Creates and stores connection to GP database
Allows for easy publishing and sharing

We demoed the implementation process and how to create quick reports and dashboards.

I'm surprised at how many customers have not deployed the standard SSRS or Refreshable Excel Reports. It's really quite easy, and I know you'll like the results. So go ahead and try it.


Upgrades / Backups / SQL Traces and Sharepoint Performance

Doug White and Jason Young discussed issues related to managing Dynamics GP systems.



And finally, I know you're all dying to know how to make martinis with Dynamics GP.

Dynamics GP Payroll Tax Update Round 9

I recently helped a client load the Payroll Tax Round 9 Update – both the tax table update and the tax code update.  As indicated the Round 9 documentation, there are only a couple reasons why you would need to do the program update, one of which is if the Round 4 tax code update was not done.  The date of the last code update, as well as last tax table update, are shown on the Payroll Tax Update window.  If the Round 4 code update was loaded, the last code update date will be 2/26/2009.  If the Round 6 code update was loaded (necessary for Louisiana & Missouri employees), the last code update should be 6/22/2009.  When I first checked this client’s Payroll Tax Setup window, their last code update was a 2008 date so I determined they needed to load the code update as well as tax table update. 

A few odd/expected things came up during the process.  First, the program code file that you download from Partner/CustomerSource (KB971014-V10-ENU.msp) is titled “Canadian Payroll 2009 Tax Update for Microsoft Dynamics GP 10.0 (Round 4)” however, it is for US Payroll as well.  So keep that in mind (won’t say how much time I spent searching for the US Payroll version!)  Second, after I carefully performed each step to load the payroll code and tax update, only the Last Tax Table Update Date had changed, the Last Code Update Date had not changed.  I checked the Payroll Setup window and the Cobra field was there (which was a part of the code update).  I checked the version of Dynamics and HR and they both were up to v10 service pack 3 (which was also a part of the code update).  So everything looked like the code had been loaded, except the last code update field, strange!  I checked with Microsoft Tech Support and they agreed that the code had been successfully installed.  They said that they had seen this happen a few times in the past.  This client is on a 64bit system which might have something to do with it, Microsoft wasn’t really sure.  To update the Last Tax Code Update date to the correct date, Microsoft showed me that I had to manually change it in the Dex.ini file.  Once we did that, the Payroll Tax Setup window looked correct.  Of course, you should do this ONLY if you have confirmed the code did actually load.

Everything else with the update went fine.  The code was loaded on the client workstations without issue.  We didn’t even have to rebuild the reports dictionaries and this client had many modified reports in core GP and HR.  But I was ready with my backups, just in case!  As Doug Pitcher as noted many times, always take the safe route and make proper backups.

Payroll update for Dynamics GP

The past couple of days have been interesting regarding payroll updates. We have a couple of clients that run an extremely large amount of payroll transactions (I.E. One client paid around 30,000 employees last year). Typically when a tax update is released you:

• Have the client check for tax updates on their own
• Have them run the update automatically or manually
• Wait a second or two then go your merry way feeling happy you remembered to remind clients there was a tax update release

Well when you are dealing with such a large amount of transactions we felt it prudent to do some testing before giving the All OK sign. Here is the process we initiated:

1. Have all Dynamics users get out of the system
2. Backup Dynamics and company databases. Tax updates will effect the system/Dynamics tables so make sure that database is backed up
3. Enter payroll transactions in a batch. Make sure transactions cover a variety of situations (I.E. Multiple states, dependants, withholdings, deductions, benefits, etc.)
4. Build batch and run process through until you get calculation report. Save report, print it out, etc.
5. Remove batch from build
6. Install tax update. Can do automatically or manually. See MBS payroll site
7. Build batch again as in Step 2 and run until you get calculation report
8. Verify tax amounts have changed from Step 2
9. Verify tax amounts are correct. We did the below calculations to verify the numbers were as they should be. These numbers matched the calculation report in Step 6
10. We then had the client verify these numbers were correct as well
11. Remove build and delete transaction batch used in Step 2 and step 6
12. Signed off on payroll tax update

We started this process on one of the clients test server but after it took 4 hours to restore the backup and after opening Dynamics we still received several errors on the test system we decided the test server was really just there to waste electricity. We ended up doing this on the production server.

Disadvantage on testing on production server

• All users had to be out of the system for a couple of hours

Advantages

• The production server was much faster
• After the tax update was installed and tested we didn’t have to reapply tax update as we would have if we did this first on the test server.

So you probably think I’m a fairly big chicken when it comes to trusting MBS on SP’s and tax updates. It may have cost the client a few hours of testing and time but when payroll is involved I’d rather be called names than be totally naive.

WOW them with FRx Monthly & Year-end Forecast Report

One of my favorite FRx reports is a monthly and year-end forecast report that is a snap to create. Here’s a sample of the report:

 

 

The reason it is so easy to create is that the column layout has already been created and exists in the FRx sample company, Fabrikam Works. You can open the report in Fabrikam Works and then do a file>save as to save the column layout in your company’s spec set. The reason that you’ll wow the report recipients is because it provides actual and forecast information all on one page and because you’ll be able to create the report so quickly. Once you’ve saved the column layout to your company’s spec set, all you’ll have to do is change the Budget ID to the appropriate one for your company in each budget column (a simple copy/paste, paste, paste, etc. will do the trick). Then the report will generate properly each period, pulling actual amounts for the appropriate months and budget amounts for the other months, just with the click of the generate button!

Here are the detailed steps:

1. Launch FRx and switch the Default Company to “Fabrikam Works”
2. Open the catalog ID “IS_Dynamic_GL”
3. Open the Column ID for that report, “Dynamic_GL” (you could skip step #2 and go directly to this column layout, if you prefer). This is what the column layout looks like:

As you can see, there are 2 columns for each period, one for actual and one for budget. The key factor here is the Print Control line. Notice that the Actual columns have “P<=B” which means, print this column if the period of this column is less than or equal to the Base period. The Budget columns have “P>B” meaning, print this column if the period of this column is greater than the base period. Since these settings are mutually exclusive, only one column will print for each period. For example, if the report is run for the Base Period 4, then the Actual amount will print for Period 1 to Period 4 columns and the Budget amount will print for Period 5 to Period 12 columns (pretty nice!)

Where it gets really fancy is in the column header section. Look back at the report sample up above. Notice that the Actual and Budget headers stretch over the appropriate columns. FRx does this automatically for you. No matter what period you run the report for, FRx figures it out! Take a look at the details for each header. The Actual header looks as follows:

By telling FRx to Spread the header from B to BASE, it will always stretch over only the actual columns!

 

The Budget header looks as follows:

By telling FRx to Spread the header from BASE+1 to Y, it will always stretch over only the budget columns! And, Font Style = Column Shade makes the distinction even better.

Anyway, close the Header Options window and move on to step 4.

1. Click File>Save as. This window will open:

The key here is to click on the drop-down button for Specification set and select your company’s spec set. (Normally your company’s spec set will be “Default”. If you have more choices than FRxDemo and Default, and you’re not sure which one to pick, cancel out and go to Company>Information. Click on your company on the left and view the spec set displayed on the right. Do NOT do anything else on this window! Click Cancel and go back to the column layout.) You can then change the name and/or description of the column layout if you want and click OK. You will then get this message:

It did what you asked it to do so, just click OK and move on to step 5.

1. Close the column layout
2. Close the report catalog
3. Switch the Default Company back to your company
4. Open the column layout you saved in step #4 and change the Budget ID in each budget column to the appropriate Budget ID for your company
5. Create a report catalog (or modify an existing one, if you prefer) with your desired row format, the new column layout, and your desired reporting tree (if applicable)
6. Wow your boss and others with this informative report!

Electronic Document Delivery in Business Portal 4.0 with Dynamics GP

This video shows an example of how to use the Electronic Document Delivery function in Business Portal. This is an easy way to send large amounts of documents to your customers electronically.

SSRS Reports Available in Dynamics GP 10.0

This is a list of SQL Server Reporting Services reports that are available for Dynamics GP 10.0. You should also check out the KnowledgeBase article #954242

SSRS reports:

Field Service

Contract Information
SVC RTV Hard Copy

Financial

Additions Report
Bank Transaction History Report
Checkbook Register
Fixed Asset Depreciation Detail
Fixed Assets Depreciation Ledger
Fixed Assets to General Ledger Reconciliation Report
Journal Entry Report
Period Projection Report
Retirements Report
Source Cross Reference
Trial Balance Detail
Trial Balance Summary
Undeposited Receipts

Human Resources

Employee Attendance Detail
Employee Attendance Summary
Enrollment by Benefit
Enrollment by Employee

Inventory

Purchase Advice Report
Purchase Receipts
Sales Summary
Stock Status

Manufacturing

BOM Detail Report
Item Standard Cost Changes Report
Job Detail
Manufacturing BOM Report Standard Costs
MO PO Links Report Sort By Vendor
Picking Report – Item Number
Picking Report Multibin – Item Number
Traveler Graphics Reports

Payroll

Check History
Check Registry
Department Wage and Hour Report
Earnings Summary
Employee Pay History
Employee Wage and Hour
Payroll Summary
State Wage Report
Vacation Sick Time List

Project

Detail Trial Balance
Monthly Employee Utilization
PA PBW Fee
PA PBW T and M
Pre-Billing Worksheet CPFP
Pre-Billing Worksheet T and M
Project Cost Breakdown
Projects in Progress

Purchasing

Aged Trial Balance – by Document Date
Aged Trial Balance Details Subreport – by Document Date
Back-ordered Items Received
Cash Requirements
Expected Shipments
Historical Aged Trial Balance
Purchase Order History
Purchase Order Status
Received Not Invoiced
Receivings Trx History
Transaction Detail
Vendor Summary

Sales

Accounts Due
Aged Trial Balance – Detail
Historical Aged Trial Balance
Receivables Sales Analysis
Sales Distribution History
Sales Document Status
Sales Transaction History
Sales Transaction History Payment Details Subreport
Sales Transaction History Tax Details Subreport
SOP Document Analysis
SOP Document Analysis by Customer
SOP Inventory Sales Report

Once you've got these loaded, take a look at my quick video about using the Report Builder function in SSRS.

Payroll update for Dynamics GP round 9

Round 9 payroll update was released for Dynamics GP today. This affects only California so if it's above 60 degrees and you are living close to the Sharks or Kings and west of the Coyotes chances are you will need to do this. (Sorry, Canadian's mostly use temperature and hockey town's for figuring out geographic locations. For example, I live 5 hours south of the Calgary Flames, 8 hours from the stinky Oilers, not far enough from the Canadiens. I digress.)

It's just a tax table update so no code is installed (assuming you have already applied round 4 where the code was changed.) Back up the Dynamics database then on the server or any workstation, log onto Microsoft Dynamics GP with the System Administrator user, and open the Payroll Tax Update window. (Microsoft Dynamics GP menu>> Maintenance>> U.S. Payroll Updates>> Check for Tax Updates) and you're good to go.

If you are still on Great Plains 8.0, shame on you. But you can probably just download this file and run it on your sql backend. Save you some time from updating this all manually. The file is the TX.cab file and can be ran instead of doing the automatic payroll update. Make sure you back up the Dynamics database before so executing.

Important, Please read
Another side note for payroll. I received word today that MBS is starting their GP 12 planning as they think they've done about all they can with GP 11. (Hope that's a good thing.) I was asked for any wish lists items for HR and Payroll. If you have anything you would like added to Dynamics payroll and HR, NOW is the time to voice your opinion. If you don't have a MBS super secret contact to get you in on the planning leave a comment here and I'll be sure to voice your opinion. (I'm talking to you Chris.)

Collections Management

The Collections Management module in GP includes features that assist you in managing and collecting your accounts receivable. The module is included in the Advanced Management BRL license. And though many organizations own the license to use this module, I rarely see it implemented.

There are five features that I think really make it useful for controlling your outstanding accounts:

1.) Most of the information that you would want access to in order to review a specific client's account is accessible from one screen; the Collections Main screen

2.) You can create various queries to select customer accounts that allow you to focus your attention on the accounts that need the most attention

3.) You can create notes that document activities and conversations regarding specific customer accounts.

4.) You can easily re-print selected invoices, print a current account statement, select an appropriate cover letter, and distribute to the customer via fax or e-mail.

5.) You can print a standard aging report that includes the notes relevant to each customer's account.

If you haven't implemented Collections Management yet, you should take a look at it. I recorded a short video to show you my favorite features.

Have You Used Any of These?

I've used several of these machines in the past; how about you?

David Musgrave suggested the following two additions; the Amiga, and the Sinclair ZX80: