Friday, January 30, 2009

Connecting remotely to Dynamics GP, Terminal Server, Citrix etc.

Ever have the need to work from home? Do you have multiple sites needing access to Dynamics? Ever travelling or on vacation (I hope not) and need access to you system just for a few minutes?
Connecting remotely to your accounting system is becoming a must have in the world today. Many employees work at home (I'm in Montana and our office is in San Diego) or travel and need access to their system. I will discuss a few technologies that make accessing your system remotely convenient and efficient. All of these products require a fairly speedy internet connection to get the performance you desire.

  1. Remote Desktop Connection (Terminal Server)- (Start>>programs>>accessories>>communication>>Remote Desktop Connection). This will connect you to a terminal server and if GP is installed you should have full access to your accounting system. Advantages: One install to maintain. Pretty decent performance. Usually easy to set up. Disadvantages: By default limited to number of users that can launch sessions
  2. Citrix- This is the perferred application solution for those hosting Dynamics GP. Advantages: Many users, multiple sites, great performance (if your Internet connection is sufficient). One installation (Typically) to maintain. Disadvantages: Need someone on staff to that knows how to implement Dynamics on Citrix. A few companies host Dynamics with Citrix if you don't want to do this yourself. See Rose ASP.
  3. Access to computer at work- These products will log you into your workstation and you can work as if you are sitting in your office. Log me in or PC Anywhere are examples of these type of tools. Advantages: You have access to your own workstation, typically a desktop computer. Disadvantages: You have to leave your workstation on all the time. Every workstation has a local install of GP making updates and upgrades more time consuming.
  4. Support tools - We use Go to Assist for our technical support team. There is also live meeting, Webex etc. Advantages: You can access any workstation (as long as firewall allows access). Disadvantages: Typically you need someone to accept request to launch application so unless you hire a temp to stay all night at the office, it's not to reasonable. There is some delay depending on Internet connection.
  5. Virtual Private Network (VPN) - You would set up a VPN that connects to the server then use your local workstation install of GP. Advantages: Can be anywhere and access data. Disadvantages: Typically performance suffers. Especially during reporting and processing transactions. Every workstation has a local install of GP making updates and upgrades more time consuming.

Certainly not an exhaustive discussion on this topic. I've been asked numerous times what the options for remote access are. I'm sure there's others. Anyone want to comment with more info I'd be happy to update this entry.

Resources and Websites

Labels: , ,

Format Issue with FRx Service Pack 10

Depending on how you format your FRx reports, you may want to skip FRx Service Pack 10. Consider these 3 questions:

1. Do you round your FRx reports to dollars?
2. Do you want to have the dollar sign ($) on only certain rows (such as the first and last row)?
3. Do you have reports with columns that have different formats (for example: amount columns and percent columns)?

If you answer is "Yes" to all three questions, you don't want to install FRx Service Pack 10. With SP10, FRx prints amounts with 2 decimals for rows that have "CS" in the print control field. You can add a format mask to the TOT or CAL rows that you want a dollar sign on, but that will mess up the columns that should have a different format, such as the % columns. You can, format the amount columns on the column layout but that would result in dollar signs being on every singe row.

Microsoft Tech Support has said that this issue might be fixed with FRx Service Pack 11. I sure hope so!

Thursday, January 29, 2009

Project Accounting - Deferred Revenue

The Project Accouting module in Dynamics GP can be used to accurately manage deferred revenue. Many of our clients use this function when their business involves a mix of project related activity and subscription based or contract based revenue.


To use Project Accounting for manageing deferred revenue there are a couple of rules:


  • Use a "Service" Fee Type

  • Use a "Time and Materials" Project Type

Project Accounting will allocate the fee amount evenly over the duration represented by the start date and end date of the project, or as identified in the Fee Entry screen.


This is an example of a Fee for which the revenue will be deferred over 12 months:




These three accounts will handle all accounting for the invoicing and revenue recognition of the fee:

Here's an example of the fee in a project:


To invoice the fee, you just use the standard invoicing process in Project Accounting. To recognize revenue you use the standard revenue recognition process. You can use Cycle Revenue Recognition or create the transaction manually by navigating to: Transactions >> Project >> Billing >> Revenue Recognition.

But what happens with a service fee that spans a period of time, is that revenue will be recognized for the fee amount, from the start date, up to the Cutoff date specified. This will then effectively defer the revenue associated with the fee, from the last time the revenue recognition process was run for the fee, and the current Cutoff date.

Here's an example of the Revenue Recognition Entry screen:


This is the detail of the results of the revenue recognition calculation:

In my example, the revenue was recognized from 4/12/2017, to 5/31/2017: (50-1) days / (365-1) days = 13.46% x $10,000 = $1,346.00.

Why one day is taken off the numerator and denominator is something known only to the developer.

Here are the examples from KB# 885070:

A service fee can be set up for any time period that you specify. The percent complete is based on the total number of days for the service fee. The Begin Date field and the End Date field are used to calculate the number of days for the service fee.

Then, the percent complete is multiplied by the fee amount to obtain the revenue recognition amount. Billing has no affect on the amount that is recognized. The following examples show how the revenue recognition amount is calculated:

Service fee example 1

Fee Amount: $10,000

Begin Date: 1/1/2007

End Date: 4/30/2007

Total Number of Days = 121 days (31 + 29 + 31 + 30)

If revenue recognition is run with a cutoff date of 2/15/2007, the percent complete is calculated as follows:

Percent Complete = ((31 + 15) - 1) / (121 - 1) = 0.375 = 37.50%

Amount Recognized = 37.50% * $10,000 = $3750

Service fee example 2

Fee Amount: $1000

Begin Date: 1/1/2006

End Date: 2/29/2007

Total Number of Days = 425 days (365 + 31 + 29)

If revenue recognition is run with a cutoff date of 2/15/2007, the percent complete is calculated as follows:

Percent Complete = ((365 + 31 + 15) - 1) / (425 - 1) = 0.9669811 = 96.70%

Amount Recognized = 96.70% * $1000 = $967


If you have a deferred revenue tracking issue related to project-type business activities, consider using Project Accounting to manage the whole process.

Labels: , ,

Wednesday, January 28, 2009

Contract Administration - Revenue Recognition

Contract Administration is included in the Dynamics GP, BRL - Advanced Management license. We have clients that are using it a lot to manage revenue recognition for parts of their businesses. The key functionality that makes it good for certain revenue recognition applications is that if you invoice your customers less than monthly, the module has a built-in deferred revenue recognition process that will create and post monthly revenue recognition entries.

It's relatively easy to use.


You create a new contract by navigating to: Transactions >> Contract Administration >> Contract Entry/Update.


In this example, I am invoicing annually.





Click on the "Contract Lines" button and this screen pops up. In this screen you can either select items from the item master file, or just key in an item. The pricing can be set up to default from a separate price book if you wish, or you can merely key in the amount you want to charge.



Click on the "Invoices" button and you get a list of all the invoices that are planned to be created according to the schedule you've set up. In this case there is only one, because this is a one year contract, invoiced on an annual basis. This screen will just show the amount to be invoiced for the selected line item in the schedule above.


In this screen you see the revenue recognition transactions; posted, and planned. The top window shows all the revenue recognition transactions that are scheduled to be posted. The bottom window shows the transactions that have been posted.



To invoice the contract, navigate to: Transactions >> Contract Administration >> Contract Billing.
To generate and post the revenue recognition transactions, navigate to: Transactions >> Contract Administration >> Revenue Recognition

One of the advantages of this module for revenue recognition is that the schedule of planned and posted revenue transaction are contained in SQL tables; as opposed to Project Accounting that calculates and creates the transactions as you request them. This makes reporting on future revenue easier.
Generally we recommend one or more of three modules in Dynamics GP to manage revenue recognition: Contract Administration, Project Accounting, and Revenue / Expense Deferral.

Each has its strong points. It depends on the business process you want to control, as to which module you choose.

Labels: , ,

Tuesday, January 27, 2009

Dynamics GP Fixed Assets - Start Using It

The Fixed Assets module has been a standard part of BRL licensing since its inception, and we still have many clients that don't even use it. This amazes me because when I was a Controller, the fixed-assets-in-a-spreadsheet thing drove me crazy. Invariably the spreadsheets would break, and they wouldn't total properly, or the calculations for depreciation expense wouldn't extend gracefully into a new year.


These are the benefits I generally see in using the Fixed Assets module:


  • Well integrated into the core financial modules; no duplicate entry required.

  • Decent reporting, in that it easily produces lists of assets for insurance listings, tax reporting, audit requests, etc.

  • All data is stored in SQL so it will be regularly backed up.

  • All calculations are done for you.

  • Great audit trail for depreciation and other asset related transactions.

  • There are transaction types for typical fixed asset events, and therefore creates a solid audit trail.

  • It's easy to make changes to individual depreciation attributes if needed, and the system will make appropriate transactions to reconcile changes.

The Fixed Assets module is easy to setup and use, and there's an easy import function built into the module.


The setup may take some planning time to make sure that the various transactions are coded to the proper accounts, and to ease data entry. But once you've planned it out, it's easy to implement.


The import function included in the module is easier and quicker than the Integration Manager approach, so use the Fixed Assets import utility.


You propbably already own the Fixed Assets module, so if you're not using, go ahead and set it up, import the data, and start using it. You'll be happy you made the effort.

Labels: , ,

Monday, January 26, 2009

MRP Example

This shows you how to set up a simple MRP run, so you can get the idea of how it works. I'll add a new item, and go through the setup necessary to have MRP pick it up and generate a PO.

1.) Add an item or select an existing one: Cards >> Inventory >> Item

2.) Go to the Item Quantities Maintenance screen and assign it to a Site ID, make that Site ID the default site, and select a vendor for the Order Vendor ID.

3.) Go to the Item Purchasing Options Maintenance screen and select a Default Purchasing U of M.

4.) Go to the Item Vendors Maintenance screen and make sure there is a Vendor Item Number

5.) Go to Item Resource Planning. With the Site ID radio button selected, select the Site ID you defined as the default for the item. Check the "Calculate MRP for this item/site". And for Order Policy, select "Lot for Lot". Make sure the Replenishment Method is set to, "Buy".

Done with setup.


Add some demand for the item by creating a sales order for the new item.

Run the MRP: Transactions >> Manufacturing >> MRP >> MRP Regeneration

Click on "process".



Open the Purchase Request Resolution screen: Transactions >> Purchasing >> Request Resolution

Highlight the "Qty. Req." value for your item, and click on "Select Vendor".

Click on "Create".

Click on "OK".



A purchase order will be created and you'll see a report like this:


Go to Purchase Order Entry to see the new PO.

There are so many options and screens that can become a factor in how you use MRP, but this will give you a start.

Labels: , ,

Friday, January 23, 2009

Payables Scheduled Payments

The Scheduled Payments function in Payables Management, allows you to create an amortization schedule for an existing payables invoice, calculate interest expense, and then post to GP so that you can recognize a liability for a non-AP amount, and only show the current payment due in the AP aging.

This functionality was developed for the scenario in which your vendor has agreed to accept a schedule of partial payments as opposed to payment-in-full. Some of our clients are also using this to record basic loans and leases, which then allows them to have all the accounting for such arrangements in GP.

This is simple to do:

Navigate to: Transactions >> Purchasing >> Scheduled Payments

Select the posted payables invoice you want to create a schedule for.

Complete the specific attributes of the arrangement, e.g. Interest Rate, Number of Payments, Frequency of Payments, etc. The functionality allows you to solve for Number of Payments or Payment Amount, if you wish.

Click on Calculate. You can calculate and re-calculate until you get the schedule that matches your arrangement.

Click on Amortization to view the calculated schedule.


Here's the meaning behind the accounts:

Accounts Payable posting account:
Debited with the scheduled payment amount, including principal and interest, when an individual payment is posted using the Post Payables Scheduled Payments window.
Credited with the total schedule amount, not including interest, when the payment schedule is posted using the Payables Scheduled Payments Entry window.

Payables Offset posting account:
Debited with the total schedule amount, not including interest, when the payment schedule is posted using the Payables Scheduled Payments Entry window.
Credited with the scheduled payment amount, not including interest, when an individual payment is posted using the Post Payables Scheduled Payments window.

Interest Expense posting account:
Debited when you post a payment schedule.
Credited with the interest portion of the scheduled payment amount when an individual payment is posted using the Post Payables Scheduled Payments window.



Once you're satisfied that you have the schedule correct, click on Post. This will back out the AP amount on the GL and move it to the liability account you specified.

Done with the first step.


Now as time passes you will want to post payments from the schedule, to the open accounts payable.

To do that, navigate to: Tools >> Routines >> Purchasing >> Post Scheduled Payments

Just mark the payments you want to move to payables, and post.


If you haven't tried this functionality out yet, you should. There's a good chance that it can manage some of your current payment obligations, and you can retire some old spreadsheets.

Similar functionality is also available in the Receivables Management module.

Labels: ,

Thursday, January 22, 2009

Manufacturing Order Entry in Dynamics GP

Here's a simple example of creating a manufacturing order in GP. This will give you an idea of how the process works.

You will need two things in order to create a manufacturing order transaction:
1.) Bill of Material (See my example of simple BOM) For this example make the BOM a "Backflush" BOM
2.) Routing

Let's make the routing first. Create a simple one that has one sequence. Navigate to: Cards >> Manufacturing >> Routings >> Routing Entry.

Look up your finished good item number.

Create a Routing Name.

When the Routing Header Creation screen comes up, check, "Primary Routing" and save.

Enter "100" for the sequence number.

Select a work center. If you don't have any, they're simple to create.

Save, and you're done.






Create a Manufacturing Order Transaction.

Navigate to: Transactions >> Manufacturing >> Manufacturing Orders >> Entry

Look up your finished good item.

Create a default Scheduling Preference if you don't have one.

Enter an Ending Quantity amount.

Assuming a "Forward Infinite" Scheduling Method, enter a "Start Date".

Click on "Schedule MO" button.

Click on "Build Picklist" button.

You are done entering the manufacturing order transaction.



To proceed, change the "MO Status" field to, "Released", and save.

Create a Manufacturing Order Receipt transaction to add the finished good item and relieve the component items from inventory.

Navigate to: Transactions >> Manufacturing >> Manufacturing Orders >> Entry

Look up your manufacturing order, and enter the quantity of the finished good created.

The Quick MO offers an alternative to the Manufacturing Order, but I like this best, and don't feel it's much more complicated than the Quick MO.

Try this out in the Fabrikam sample company, and you'll see that basically, it's fairly straight forward.
There are significantly more options and functionality, but this will help you get over the initial feeling of being overwhelmed.

Labels: , , , ,

Wednesday, January 21, 2009

Microsoft Convergence past and present

My first experience with Microsoft Convergence was in Florida in 2002 (maybe it was 2001, can't remember exactly. Must be getting old.) I do remember being somewhat awestruck with the show Microsoft put on for it's customers. The expo was top notch, concurrent sessions were educational, and the key note speakers were enlightening. I worked for a .com company at the time and Microsoft choose us for the Pinnacle award for Excellence in Customer Care. Nice honor to be recognized for.

One of the most vivid memories I have was just before the key note speech from Bill Gates. The doors opened and I saw accounting professionals of all ages, shapes and sizes running as fast as they could to the get the best seat possible. Kind of a funny sight really but remember thinking how exciting it was to listen to someone so successful in person. Mr. Gates gave his insights on the industry and gave a road map on how Microsoft was going to help each company using Dynamics.

From that first experience I have attended Convergence in San Diego, Dallas, Florida (again last year), and will be attending in New Orleans this year. Every year Microsoft out does themselves. Just look at the sessions available this year.

The concurrent sessions are a big part of the event but I particularly like interacting with MBS folks directly. Geeky as it may sound I find it great fun to go "Yell" at MBS folks on things that I wanted fixed, corrected, or included in the next versions of GP. I also take all our customers to the tech support area and give demos of modules they are looking for. This is a good time for customers to get "Free" training or tech support.

If someone is looking for a particular module or fix to a business process the Expo is the place for customers. Every year we are able to solve business process pain by finding the best 3rd party products. Last year we looked at several tax solutions offered by 3rd party companies. Ended up moving off of one 3rd party product (implemented by another VAR) to another saving a significant amount of money on a monthly basis on the way with all the functionality the customer needed. Point is, the customer was able to analyze each product in person along with meeting the people that were going to support them going forward.

There's still time to register.

My own take is if you have GP you should be going to Convergence. It's a sacrifice to go but the returns are tremendous in education, training, and GP utilization.

It's also a lot of fun.

Labels:

Simple Manufacturing BOM in Dynamics GP

The manufacturing BOM is a sophisticated bill of material application, and can be a bit intimidating to use, at first. But here are the steps to create a simple, functional BOM, to give you the feeling of the system; assuming you have your items all set up:

First we want to set up the finished good item so that it is identified as a "Make" or a "Make or Buy" item.

Navigate to: Cards >> Inventory >> Item >> Item Engineering Data, and select "Make" for the "BOM should treat as" value.


Navigate to the Bill of Materials Entry screen: Cards >> Manufacturing >> Bill of Materials

Enter your finished good item.

Click on the Green + to add components. This will activate the component entry area of the screen.

Look up the component you want to add.
Enter the quantity.
Click on the "Add" button to add an additional component item.
When you're done adding components, click on the "Tree View" button to return to the finished good portion of the screen.
Not too bad.
For clients that have the Advanced Management BRL license, I almost always recommend that they use the manufacturing BOM, instead of the other BOM in the Inventory Control module. It takes a bit longer to learn, but has much more functionality to accomodate future needs.

Labels: ,

Friday, January 16, 2009

Dynamics GP 1099 printing for 9.0 and 10.0

Significant improvements/changes have been made to Great Plains 1099 printing process for version 10.0 versus previous releases of Dynamics (basically any version before 10.0). I've had several calls over the past week about printing 1099's so I thought I'd shed some light on the subject here.

First off there is a new setup window in Payables for 1099's. On the purchasing homepage look under setup and choose payables (tools>>setup>>purchasing>>payables). See screen shot below (click on picture to see better detail). You can now set the minimum 1099 amount in the 1099 setup window for each tax type and box number desired. (In 9.0 you would choose the minimum amount right on the print 1099 screen.)



Another change is the 1099 box added to the vendor options window. (cards>>purchasing>>vendor>>options). When you change the tax type to be a 1099 type you now can identify where the 1099 box will default to for the vendor. Nice little addition.



One of the biggest changes to this process is previous to 10.0 you could not split the 1099 amount between any needed boxes. You basically had to print out seperate 1099's for each box needed per vendor, updating the 1099 amount previous to each printing (or use a type writer, ha). In 10.0 you have the 1099 detail window as shown below. This window is a new place you can update the 1099 amounts as well and is found on the purchasing homepage under cards (instead of going to Cards>>purchasing>>summary>>period, in 9.0).



The 1099 detail window could also be used to correct the 1099 amount in 10.0. (Note that you need to choose the monthly view instead of yearly view to update any numbers.) In 10.0 you can still go in the old way which is Cards>>purchasing>>summary>>period (for homepage non users) but the 1099 detail window looks like that may be where I do this from now on. However, in 9.0 I usually tell people to see what the yearly number is (Cards>>purchasing>>summary>>yearly) and then update one of the periods with the amount desired so not sure how easy this will be in 10.0 with this new window. (Anyone have any thoughts on this???) Alternately you can go through each period and put the appropriate amount...but that's a pain and the 1099's will just use a summary total anyways.

You still print the 1099 edit list on the print 1099 window by choosing the printer icon in the upper right hand corner of the screen. The print 1099 window looks a little different as the payables setup area is where you change the 1099 minimum amounts now.


There is really no changes made to the 1099 form this year other than some 1099-R Distribution code changes. Not significant. So no year end update is really required. Still recommend being on the most recent SP but as I said, not really critical. One note on SP's, if you are not on SP 2 or beyond for 10.0 your edit list will print all zero's. So either update your SP version or print the 1099's to screen and browse numbers that way. May have 50 pages with 2 vendors on a page but at least you can see numbers etc.

I always get asked about forms and alignment. You can purchase forms from a store like Office Depot.

If the 1099 doesn't align correctly (sometimes off depending on the printer etc.), use these guidelines to make adjustments in the Print Dialog Box (tech doc #870140):

Horizontal: If you enter a positive number, the information on the paper will move to the right. If you enter a negative number, it will move to the left.

Vertical: If you enter a positive number, the information on the paper will move down. If you enter a negative number, it will move up.

Very rarely do I see you having to adjust the actual report writer report but have had to do it on occasion.

Last bit of advice. January 30th is fast approaching and the heat is usually on to get these done. Don't wait until January 29th to do your 1099's. It's a simple process but Murphy's Law definitely applies here.

Good Luck.

Labels: ,

Tuesday, January 13, 2009

Stuck batches in Dynamics GP

Stuck batches are one of the most common issues in GP. This is caused by a number of issues including:
  • Power fluctuations

  • Data corruption (batch posted but not deleted from SY00500)

  • Transaction errors in batch but Batch Recovery window will not process

  • 3rd party product issues

  • Workstation disconnecting from the server (network connectivity issue or loosing remote connection via citrix or Terminal Server)
The SQL scripts to fix this is found in tech doc #850289. Here they are if you don't have access to PartnerSource. Make sure you kick everyone out of GP and backup up your databases.
DELETE DYNAMICS..ACTIVITY
DELETE DYNAMICS..SY00800
DELETE DYNAMICS..SY00801
DELETE TEMPDB..DEX_LOCK
DELETE TEMPDB..DEX_SESSION
Then use this script to update the status of the batch:
UPDATE SY00500 SET MKDTOPST=0, BCHSTTUS=0 where BACHNUMB='XXX'

Mariano Gomez reminds us of MBS Automated Solutions on his blog. One of the automated solutions in the system series is a batch stuck in posting routine that does this for you manually.

I rarely use any of the above if I have access to SQL. It is a pain to kick people off of the system in the middle of the day so will use enterprise manager/management studio to do this as follows:
  1. Open Enterprise Manager/Management Studio

  2. Choose + sign next to databases

  3. Choose + sign next to database (Dynamics or company database)

  4. Highlight tables and a list of tables should show up on the review pane

  5. Find Table and right click, Choose open table

  6. Delete rows (SY00800, SY00801, or Dex_LCK) or update fields manually by putting your cursor in the field you want to update (MKDTOPST and BCHSTTUS fields in SY00500 table). See screen shot below.



This is somewhat dangerous if you are careless or are unfamiliar with SQL. Still should have a backup when working on the database.

Wednesday, January 7, 2009

2008 Payroll year end close update Dynamics 10.0

Bear with me a moment while I grumble and I'll get to YEC for 10.0.

Great Plains isn't what it used to be. That's both good and bad I suppose.

It is good that all workstations should be on the same SP version to be able to log into a company. This saves many significant issues popping up as most are well aware. Workstations used to always be out of sync and a lot of the time the resolution would be "Apply this patch like all the rest of the workstations. etc."

However it is frustrating when you only need to apply the year end update for payroll. In times past you could put the cnk file only on the payroll persons workstation and they'd be good to go. It's a major effort now to apply any service pack. It almost feels like people are being pushed into a Citrix/Hosted or Terminal Server model. There are major advantages of only having to apply SP's once at a central location. I know you can have the SP automatically apply the next time a user logs into the system but that is mostly just a huge pain none the less.

Ok, 10.0 year end update. Here are a few things I've come across while going through the year end update. Most are pretty user specific but here they are none the less.


  1. All people must be out of the system. Sounds like a no brainer but we spent several mins troubleshooting why the system tables wouldn't update then found some people had snuck into the system. (Hopefully Mike's head doesn't hurt too bad from hitting it repeatedly on the desk in front of him.)

  2. To install the update make sure the installation of GP is at least the first recommended release of 10.0. Had one client on 10.0.465 which is a beta release of 10.0. Who knows how they got that one installed. Kept getting this erorr when trying to apply the update. Applied 10.0 Feature pack 1 which includes SP3 (1.5 gb download so don't do this with a 56k modem), applied the update and they were good to go.
  3. You can run the update from a client workstation. Don't need to be at the server. Kind of counter intuitive but it works. After corrupting GP on the server during resolution of #1 we got the update to go on a client workstation. (Thanks to Jamie Nelson on this one).
  4. Plan for several minutes per database. I've timed several updates and it seems like it runs around the 20 min range per database. This is true when the databases are pre SP3. Not sure if it's quicker if SP3 is already applied. (Anyone know this?)
  5. You must run the year end wage file before applying 2009 tax tables. Duh.
  6. You can't run a 2009 payroll before running the year end wage file. Duh again. ha.
  7. User gets kicked out of GP when running payroll reports after applying update. Recreated reports.dic as it was corrupted in the process. So....make sure you backup reports.dic, forms.dic, dynamics and company databases etc. The process looks like it actually exports then imports the reports as part of the update so that could easily cause issues.

Here's a few other Year end update comments from Christina Phillips on her blog.

Victoria Yudin still has a great post on Year end close resources.

Labels: , ,

Tuesday, January 6, 2009

MOSS vs. WSS

WSS comes with Windows Server. So why would you want to pay extra for MOSS?

For me these are three good reasons:
  • Enterprise Content Management Capabilities (previously available only in Microsoft Content Management Server) Office SharePoint Server 2007 builds on these capabilities to deliver enhanced authoring, business document processing, Web content management and publishing, records management, policy management, and support for multilingual publishing. This is for Enterprise Content Management as well as Web content management.
  • Enterprise Search of both structured (ERP) and unstructured (Office produces) data, utilizing a very powerful Business Data Catalog feature. The search component has been significantly enhanced in this release. The new features provide a consistent and familiar search experience, increased relevance of search results, and new functionalities along with improved scalability, manageability, and extensibility. The Business Data Catalog is now available for GP and CRM
  • Excel Services in MOSS go beyond simply displaying Excel spreadsheets, you can actually stream parts of a spreadsheet, showing or hiding various parts. This is an easy way to create and deliver reports. Can be linked to Analysis Cubes in GP.

Additionally these are other reasons our clients have chosen MOSS:
  • Slide libraries – a much needed and unique way to share and reuse slides
  • Single Sign On (SSO) is only available in MOSS.
  • Records Management which enables organizations to comply with Sarbanes-Oxley Act of 1992 and HIPPA requirements.

Additional information at Microsoft.

Labels: , ,

Monday, January 5, 2009

Version pages for Dynamics GP 9.0 and 10.0

Ever wonder what version number in Great Plains corresponds to which service pack or hotfix?

I memorized many of these as it's a pain figuring this out via partner/customer source. It also makes me sound really smart when someone calls and says I have GP 9.0.358 and I could say, "Oh that's KB957740 US Year End update and includes SP 4." Certainly not a great pick up line but think of how popular I am in forums such as Convergence.

Well, MBS has outdated my version talent skills by linking a spreadsheet that contains which version relates to each release on the main service pack page for 9.0 and 10.0.

Here are the previous service pack releases in excel spreadsheet format for 9.0 and 10.0 . This is a link on the current release notes section.

I suppose this blog is mostly for me so I will now be able to forget previous version numbers but still look them up quickly. Leaving room in my brain for more important things but still making me look incredibly smart and hip.

Labels: ,

Tiptoeing into Visual Studio 2005 for SSRS

I wanted to create a report for a client that showed unapproved timesheets in PDK that could be published in SQL Reporting Services. I did not use the Report Builder because there was not an existing object for the data I wanted. So I decided to try out Microsoft Visual Studio 2005. I'm not a developer, so I proceeded with a bit of trepidation.

Guess what. I found it pretty easy to get started. This is what I did:
1.) Open Visual Studio >> New Project >> Business Intelligence Project >> Report Server Project
2.) Right-click on your new project name >> Add >> New Item >> Report Wizard

Then the Report Wizard takes over, and you basically define your data source and design the report. You can run the report from within Visual Studio.

I created this sample report quickly. You don't need to be a developer to get started with this tool, and I think you will find it fairly easy to get stared.

More and more we are recommending SSRS to our clients for their reporting needs. You should check it out.

Labels: , ,

Simple SSRS Reports Using Report Builder

SQL Reporting Services is functionality that's included with Microsoft SQL Server. There are many reports that are delivered out-of-the-box with GP that can be deployed to your SSRS site. But there is also an easy to use reporting tool that allows you to create custom reports.

Report Builder is accessed through the SSRS site. It allows you to use existing objects from which to report; and the objects are pretty standard. When you create a new report you have the option of creating a table style, matrix style, or chart report. You can easily drag and drop fields on to the report, and format the report to look the way your wish.

Once you have your report you can utilize the functionality in SSRS to schedule and deliver the reports. The report export options include: XML, CSV, PDF, Excel, and others.

If you have not yet tried creating a report in SSRS, you should. It's easy to get started, and I'm sure you'll like the results. Here is a report I created in five minutes. Think what you could do in 20.



Labels: , ,

Simple Dashboard in Business Portal

Below is a simple dashboard I created as a sample for a client of ours. This is deployed on a MOSS site, so I got to use Excel Services as well as standard Business Portal functionality.

I used Excel Services to show a simple MTD and YTD summary sales analysis. This spreadsheet is pulling data from the standard analysis cubes in GP, so the data will be refreshed on a scheduled basis.

Right below it is a Business Portal query that shows current open orders in GP. This data will be refreshed as order status changes in GP.

This is simple stuff, but gives users the information they're looking for, in one place. It would be easy to add additional webparts to this page; whether they would be standard Business Portal pieces or Excel Services, etc.


Here is an example of an Excel Services webpart on our internal MOSS site. I'll be capturing data from Google Analytics and manually entering it to the Excel spreadsheet, as well as providing a link to the Google Analytics report itself. This is a more manual data capture example, but it easily and effectively reports out.



Labels: , , ,