Hello all and Happy New Year!  Have you ever been in the position where a user has created a Payables invoice only to find out the items originated from a PO or PO shipment and would cause a duplicate transaction?  If so, this new feature is definitely what you are looking for!  

We have received several requests over the years asking for a way to warn or prohibit a user from creating a Payables invoice for items that were currently on a Purchase Order or shipping receipt that could potentially lead to a duplicate transaction.  With the new warning in Microsoft Dynamics GP 2015,  you will be prompted when entering a Payables invoice, if the invoice could be a potential match to an existing shipping receipt or Purchase Order line item.  What is great about this feature is the added ability to drill into a Purchasing Navigation list directly from the Payables transaction to view the potential match(s). This new feature is located under the Payables Setup.

This is a great example of what we do for you, the users, when you ask for features to make your day to day processes better.  I encourage you to give this new feature a try and see what you think!

Until next time - here's to 2015!

For more information regarding Microsoft Dynamics GP 2015:

What's New for Microsoft Dynamics GP 2015 Blog Series!

For comprehensive videos - Applications

Microsoft Dynamics GP 2015 New Features - Applications

 Microsoft Dynamics GP 2015 System Wide New Features 

To go straight to the Downloads:

Microsoft Dynamics GP 2015 Product Download Page  

Microsoft Dynamics GP 2015 System Requirements

Up to date information regarding Microsoft Dynamics GP 2015:

Microsoft Dynamics GP 2015 Upgrade Hot Topic

Are you ready for some exciting changes around payment terms for Microsoft Dynamics GP 2015?!?  For some time, we have heard from you in regards to the limitations with payment term offerings.  For example, if the payment term is a discount date term, in previous versions, it would go to the next month and then the due date goes to the following month.  This is another feature that you asked for and we hope you like the new capabilities. 

With Microsoft Dynamics GP 2015, you will have the ability to set the Due Date based on Months, Month/Day or Annual.  With this increased functionality, you will now have 8 different options for calculating the due date.  That is pretty awesome!  We have also added a new feature to help assist you in setting this option called the Calculate Action.  This new action will allow you to set up a Payment Term, then calculate to see the potential Due Date and Discount Date based on your setup of the Payment Terms.  We have taken out the guess work on how you want your Payment Terms to function!  Here is what the new window looks like:

We have also made similar changes to the Discount field to include new options to calculate based off EOM(end of month), Next Month, Months, Months/Day and Annual.  As you can see, this is a big change and we will address your current payment term settings when you upgrade to fit into these new options.  Below is an outline of how you could potentially have your payment terms today, and then what we will populate the Calculate Date From Field based on your current settings:

We are so excited to offer this increased functionality to make your day to day processing easier!  Please offer your feedback once you get Microsoft Dynamics GP 2015 loaded and let us know what you think. 

Until next time!

Deseree

For more information regarding Microsoft Dynamics GP 2015:

What's New for Microsoft Dynamics GP 2015 Blog Series!

For comprehensive videos - Applications

Microsoft Dynamics GP 2015 New Features - Applications

 Microsoft Dynamics GP 2015 System Wide New Features 

To go straight to the Downloads:

Microsoft Dynamics GP 2015 Product Download Page  

Microsoft Dynamics GP 2015 System Requirements

Up to date information regarding Microsoft Dynamics GP 2015:

Microsoft Dynamics GP 2015 Upgrade Hot Topic

WOW....I'm super excited about Microsoft Dynamics GP 2015 and the changes we have made around Human Resource and Payroll.

I have said this in the past, but all the changes you see are driven by you the customer and partner that use our product, THANK YOU.
As you review the list below you will know what I mean, it is great to see these enhancements.

Some of them are so small but it is the little items that make a difference and guaranteed it will make you stand up and clap!

The entire employee self-service is now built into Microsoft Dynamics GP 2015.
We had Timecards in GP 2013 R2 and now Microsoft Dynamics GP 2015 includes it all.

Employee Profile - allow your employees to change their employee information, add Emergency Contacts, Dependents and view their Position History.
Employee Paystubs - no more printing of checks or earnings statements, now your employees can view their pay check information online.
A nice addition here, we added pay period begin and end dates to the form and REMOVED social security number, all based on customer feedback.
Employee Benefits - allow your employees to view their benefit information that will pull from payroll and human resource tables in Microsoft Dynamics GP.
Benefit Open Enrollment process, Benefit Self Service, part of Advanced Human Resource  is also in Microsoft Dynamics GP 2015 (more to come next week)
Employee Direct Deposit - your employees can view/change and STOP their direct deposit information.
Also a change to the core product we added up and down arrow buttons to this window so it is easier to move the accounts around, no more re-entry...yes we heard YOU!
Employee W4 - your employee can change their federal tax information on this W4 form and submit it for approval and it has history tracking.
This is now all Microsoft Dynamics GP user date driven, so NO MORE yearly install of the W4 form...yeah, less work and less to remember at year end, your to-do list just got shorter!!
Employee Skills and Training - employees can see/edit their Education, Test, Skills and Training History information.
We know this is huge for our expiry dates and keeping on track of employee information.

Let's not forget Canadian Payroll!!  This module is now in WEB CLIENT, awesome.

Click HERE for my detailed documentation of all these features and look at what you are missing out on, let's get upgrading! (Microsoft Dynamics GP 2010 tax updates end October 2015)
Here is the cool VIDEO.

Terry Heley - Non ACA Expert, LOVES HRP and dedicated to helping all of you!

For more information regarding Microsoft Dynamics GP 2015:

What's New for Microsoft Dynamics GP 2015 Blog Series!

For comprehensive videos - Applications

Microsoft Dynamics GP 2015 New Features - Applications

Microsoft Dynamics GP 2015 System Wide New Features

To go straight to the Downloads:

Microsoft Dynamics GP 2015 Product Download Page

Microsoft Dynamics GP 2015 System Requirements

Up to date information regarding Microsoft Dynamics GP 2015:

Microsoft Dynamics GP 2015 Upgrade Hot Topic

In versions of Microsoft Dynamics GP greater than 10.0 SP4, there is a known issue with the 4-4-5 calendar in Fixed Assets (otherwise known as a Manufacturing or Retail calendar). This issue causes overstated depreciation in the year in which a 53 week year is necessary. Mathematically, the overstated amount will show as the expected depreciation amount times 13/12. For example
If the periodic depreciation should be $1000. The overstated amount will be:

$1000 * 13/12 = 1083.33

When this occurs, there are two workarounds to the issue depending on your version:

Workaround 1:

For versions Dynamics GP 10.0 and Dynamics GP 2010, support has developed a custom chunk file to resolve the issue. If you are on these versions, please contact Microsoft Dynamics GP Support for the file and instructions on use. This case will not be charged/decremented as this is related to a known issue.

Workaround 2:

For Dynamics GP 2013 and Dynamics GP 2015 you can resolve the problem through the following steps. Note that it is recommended to take this action in a test company first per the following article:

KB 871973 How to set up a test company that has a copy of live company data by using SQL Server 7.0, SQL Server 2000, or SQL Server 2012
 
https://mbs.microsoft.com/knowledgebase/KBDisplay.aspx?scid=kb;EN-US;871973 

1. Go to Financial >> Setup >> Fixed Assets >> Calendar
a. Select your calendar
b. Select the 53 week year.
c. Mark the Short/Long Year option.
d. Leave the Depreciation Percentage at 100%, save your changes, and close the window.
 

2. In Dynamics GP click Transactions, point to Fixed Assets, click Select Assets, and then click New Group. Name the group, and then click OK.

3. Under Current Groups, click the newly created asset group, click to Mark, and then click OK.

4. Click Transactions, point to Fixed Assets, and then click Mass Change.

5. Select the newly created asset group ID, click the Book tab, select the book ID, select Reset Year, and then click Apply Changes.

6. In the following message, click OK:
“Are you sure you want to apply changes to group (New_Group_Name) “

7.  Close the window.

8. Review the depreciation results. If these come out as expected, repeat the above steps against the live company.

Cheers,

Ken Hubbard

Microsoft 

Hi everyone,

Yes, it's time to start planning for Year-End again!  I'd like to provide you with information to help ensure that your U.S. Payroll Year End Close (YEC) goes smoothly.

In Support, we are often asked "if it is okay to install the 2014 Year End Update even though 2014 payrolls are not completely processed?" The answer to that is YES YOU CAN!  Please review all documentation in detail so that you are well prepared for the year-end close, and knowledgeable about what has changed for this year.

What versions of Microsoft Dynamics GP will be supported with the 2014 Year End Update?

     • Microsoft Dynamics GP 2010   *This will be the LAST year that a Year End update is available.  Click HERE for more information on the lifecycle for Microsoft Dynamics GP 2010.

     • Microsoft Dynamics GP 2013 - (This does include Microsoft Dynamics GP 2013 R2)

     • Microsoft Dynamics GP 2015  - (YEC update to release January 15 ,2015) 

     • Note:  The Year-end/Tax Update is inclusive of all previous hot fixes, services packs and year-end downloads.

What are the target release dates?

• The 2014 Year End Update for Microsoft Dynamics GP 2010 and Microsoft Dynamics GP 2013 are now available for download. (Released on November 18, 2014.)

• The 2014 Year End Update for Microsoft Dynamics GP 2015 is targeted for January 15 release.

• The 2015 Round 1 Tax Update (tax table update only) for Microsoft Dynamics GP 2010 and Microsoft Dynamics GP 2013 will be available the week of December 19th, 2014.   This update will increase the FICA Social Security Limit to the new 2015 calendar year amount.  *NOTE: Therefore, do not install this tax update until the 2014 Year End Wage file is created and ALL pay runs for the 2014 year are completed!

• The 2015 Round 2 Tax Update will be available mid-January.

When should the Year End Close be performed?

The Payroll Year End Close should be processed after all pay runs have been completed in the current year, and before processing any pay runs in the New Year.

Are there any changes I should know about related to the Year End Update for Payroll?

• There are NO W2 form changes

• There are W3 form changes

• There are EFW2 (Electronic Filing) changes. *The file will error if these changes are not incorporated.

• 1099-R (Retirement) distribution code changes

• Affordable Care Act changes - available in Microsoft Dynamics GP 2013 and higher versions only

• Product Quality Fixes around Payroll Year-End

Where can I learn more about the Affordable Care Act (ACA) changes?

• Another blog will be released tomorrow (Nov 19) to further discuss the Affordable Care Act changes in Microsoft Dynamics GP and will include Frequently Asked Questions.

• For more information on the table/column changes due to the Affordable Care Act, click HERE.

• For more information on the Affordable Care Act, click HERE to read Terry's preliminary blog.

What does the Year End Close (YEC) process do?

The YEC process creates the 'Year End Wage' file with annual wage information used to generate W2s, W3s, 1099-R's, and the W2 Electronic file for the year being closed.

What steps should I take to close the year? (See KB Article 850663 for detailed instructions on each step listed below):

**First and foremost make a restorable backup of the company database so you can restore should you run into a problem.**

1.  Verify that you have installed the latest 2014 payroll tax updates. The 'Last Tax Update' should read 12/17/2013 or later in the Payroll Tax Setup Window (Microsoft Dynamics GP >> Tools >> Setup >> System >> Payroll Tax).   (Verifying that the Last Tax Update is dated greater than the Round 1 tax update for 2014 will ensure you have the correct FICA limit in place when you create the Year-End Wage file.)

2.  Complete all pay runs for the current year. 

3.  (Optional) Complete all month-end, period-end, or quarter-end procedures for the current year. 

4.  Make a backup of the original file.

5.  Install the Year-End Update. 

6.  Create the Year-End file. 

7.  Make a backup of the new file. 

8.  Verify W-2 and 1099-R statement information. 

9.  Print the W-2 statements and the W-3 Transmittal form. 

10. Print the 1099-R forms and the 1096 Transmittal form. 

11. (Optional:) Create the W-2 Electronic file. 

12. (Optional:) Archive inactive employee Human Resources information. 

13. Set up fiscal periods for 2015. 

14. (Optional:) Close fiscal periods for the payroll series for 2014. 

15. Install the payroll tax update for 2015. 

To recap, prior to processing a pay run in 2015 the following is:

Required:

• All 2014 pay runs completed.

• Year End Wage File created.

• Backup of company database made.

• Payroll Tax Update for 2015 (2015 Tax Update Round 1) installed.

Optional:

• Print W-2s.

• Create W-2 Electronic File.

Can we run a payroll in the new year prior to closing the 2014 year?

If you must process a payroll for the new year before the 2014 year-end closing procedures are completed, refer to the 'Alternative Payroll Year End Checklist' steps in KB 850663. 

Why may those using Microsoft Dynamics GP 2010 want to upgrade?

The functionality needed to track the Affordable Care Act changes for calendar year 2015 is included in the Year-End Update for Microsoft Dynamics GP 2013 and higher versions.  If assistance is needed for the install or upgrade, click HERE.

ASSISTANCE: Here are some links to use if you need assistance for Payroll Year End Close

• Refer the landing page for the 2014 Year-End Blog Series.

• Microsoft Dynamics GP Blog - https://community.dynamics.com/product/gp/gptechnical/b/dynamicsgp/default.aspx

• Microsoft Dynamics Community - https://community.dynamics.com/default.aspx

• Microsoft Dynamics Support - https://mbs2.microsoft.com/Support/newstart.aspx

   If you are creating a case with the Technical Support Team for assistance with Year End close for Payroll, please refer to the category selections below to ensure you are routed to the correct Support team for assistance:

     --Support Topic Selection:    Payroll

          --Sub-topic Selection:      Year End Procedures 

ADDITIONAL RESOURCES:

•Year-end closing procedures for the Payroll module in Microsoft Dynamics GP are found in KB 850663:  http://support.microsoft.com/kb/850663

•Be sure to check back to the Year-End Blog Schedule for current posted blogs and upcoming blog posts related to Year-End Closing for Dynamics GP.

•Here is a link to a comprehensive video presentation for "What's New in Year-End 2014" for Microsoft Dynamics GP.

•Check out the" What’s New for Year-End 2014” slide deck now available for download.

•Download the Year End Update document by clicking on US13YE.pdf on the Year-End update page. 

YEAR-END UPDATE LINKS:  Here are the 2013 Year-End Update pages which will provide you with documentation and installation instructions:

2014 U.S. Payroll Year End Update for Microsoft Dynamics GP 2013 Download Pages:

https://mbs.microsoft.com/partnersource/northamerica/deployment/downloads/tax-regulatory-updates/usgpye2013

https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/usgpye2013

2014 U.S. Payroll Year End Update for Microsoft Dynamics GP 2010 Download Pages:

https://mbs.microsoft.com/partnersource/northamerica/deployment/downloads/tax-regulatory-updates/usgpye2010

 https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/usgpye2010

TAX UPDATE LINKS:  Use these links to access the latest (and previous) Tax Updates:

Latest U.S. Payroll Tax Update for Microsoft Dynamics GP2013:

https://mbs.microsoft.com/partnersource/northamerica/deployment/downloads/tax-regulatory-updates/TUGP2013

https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/TUGP2013

Latest U.S. Payroll Tax Update for Microsoft Dynamics GP 2010:

https://mbs.microsoft.com/partnersource/northamerica/deployment/downloads/tax-regulatory-updates/TUGP2010

https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/TUGP2010

I hope you find this information helpful!  Please watch for more blogs and helpful information to come.   Have a great Year End!!!

Cheryl Waswick | Microsoft Dynamics GP  | Senior Support Engineer

Many of you have asked, is there a Benefit Self Service in Microsoft Dynamics GP 2015?  Well of course there is....and it is better than ever! 

Why I'm excited about Benefit Self Service in Microsoft Dynamics GP 2015 is we really took a look at what customers wanted / needed to change in the prior product and made those enhancements.
With the new Benefit Self Service product in Microsoft Dynamics GP 2015, Benefit Open Enrollment was just made EASIER and I know we all like that.

Here are a few of the items I would like to call out that were near and dear to customers as they went through open enrollment:

• Human Resource is not required; you can link directly to Payroll Benefit / Deduction codes.
• You can set validations that state you have to enroll in this plan prior to enrolling in the "higher" plan, like a prerequisite.  This happens a lot with Life Insurance.
• Easier integration to Microsoft Excel for reporting purposes.
• You can separate out your health enrollments easier, such as Dental, Health, Vision (key for ACA!!)
• An improved Benefit Enrollment period window so you can easily roll out enrollment to a large group of employees or single onboarding.
• Ability to attach multiple plan documents to a benefit, including Adobe Acrobat pdf's and Microsoft Word documents.
• User defined enrollment information
• You can now "return" the benefit enrollment back to an employee instead of having to delete it out, we now give you both options, awesome, who wants to re-key!
• More flexibility during the posting process for what benefits you want to post at a time, easier to administer.

I could go on and on, I think you get what I'm stepping in; this product is a force to be reckoned with and includes many enhancements based on customer feedback.

Take the time to check it out!

Click HERE for detailed documentation, VIDEO to follow soon!

Thanks

Terry Heley
Microsoft

Hello All,

In Microsoft Dynamics GP 2015, we have introduced a number of new workflow types. The new types, which reside in the core Dynamics GP modules, include the following:

• General Ledger Batch Approval
• Receivables Batch Approval
• Payables Batch Approval
• Vendor Approval

The first three types are Batch Approval types which require an approval before a batch can be posted. Some actions are allowed prior to approval. It is possible to create the batch, add transactions to the batch, and print the edit list for the batch prior to approval. In instances where a check would be printed in Payables, that printing is not allowed on a batch which has not yet been approved. It is not possible to post a batch that has not been approved, when the related workflow type has been enabled.

The Vendor Approval type, if enabled, will require that a new vendor be approved before any related transactions can be posted. Some transactions, such as vouchers and manual payments, can be entered and saved. However, computer check payments cannot be entered or saved.

Is it necessary to use these types? No, none of these four types are required. You can continue to process all of these batches, and enter new vendors, without using the workflow, if desired.

What else should we think about? If you are enabling a batch approval type, verify that the “Allow Transaction Posting” checkbox in the Posting Setup window, for the related Series and Origin, is unmarked. This will force all transactions to be saved in a batch and the batch to be approved prior to posting.

There are other workflows, in addition to these in the core Dynamics GP modules, added in Microsoft Dynamics GP 2015. They include the following workflow types:

• Employee Profile Approval
• (Human Resources) Employee Skills Approval
• Payroll Direct Deposit Approval
• Payroll W4 Approval
• (Project PTE) Expense Report Approval

These are in addition to the types which were previously introduced in Microsoft Dynamics GP 2013 R2:

• Purchase Order Approval
• Purchase Requisition Approval
• Payroll Timecard Approval
• (Project PTE) Timesheet Approval

 Thanks,

Tammy Torgerson

Microsoft

For more information regarding Microsoft Dynamics GP 2015:

What's New for Microsoft Dynamics GP 2015 Blog Series!

For comprehensive videos - Applications

Microsoft Dynamics GP 2015 New Features - Applications

 Microsoft Dynamics GP 2015 System Wide New Features 

To go straight to the Downloads:

Microsoft Dynamics GP 2015 Product Download Page  

Microsoft Dynamics GP 2015 System Requirements

Up to date information regarding Microsoft Dynamics GP 2015:

Microsoft Dynamics GP 2015 Upgrade Hot Topic

2015 is flying by, and the Microsoft Dynamics GP Round 2 Payroll Tax Update and January Hotfix is already here!!

I have included the most important information you’ll want to know regarding what’s changed and what’s been fixed by version below. Enjoy!:

Microsoft Dynamics GP 2010, 2013, and 2015:

After you install the Round 2 Tax Update and January Hotfix (code update on all workstations and the server), and the 2015 Round 2 Tax Table Update (tax tables only and installed once): The Payroll Tax Setup window (Microsoft Dynamics GP >> Tools >> Setup >> System >> Payroll Tax) should display the following dates:

Last Tax Update = 01/18/2015
Last Tax Code Update = 01/18/2015

US Payroll Tax: Arkansas and Rhode Island code updates.

Please Note: If you do not calculate payroll tax in Arkansas or Rhode Island, you can continue to process pay runs without installing the January Hotfix. However, as always we recommend you install the latest and greatest code.

Click HERE to download detailed documentation regarding the Round 2 Tax Update and January Hotfix.

Microsoft Dynamics GP 2010 (version 11.00.2390)

Canadian Payroll: After the Year End Update for Microsoft Dynamics 2010 was installed, the ROE Generate window had missing buttons which made the window difficult to use. Resolved!

Microsoft Dynamics GP 2013 (version will be added upon release)

Canadian Payroll:T4 Box 86 not updating T4 xml correctly, thus rejected by CRA. Resolved!

Affordable Care Act:
As you all know, with the 2014 Year End Update we started to implement ACA tracking mechanisms to ensure you can report on ACA data at the end of 2015. With this new functionality of course, we’ve found a couple of issues. We wanted to make you aware of them and get them fixed right away!

• ACA codes were defaulting on ALL existing Health Insurance for lines 14 (Offer of Coverage) and 16 (Safe Harbor Codes), thus updating the BE020230 (HR Benefit Setup) table incorrectly. These codes ‘should’ default in as ‘None’. Resolved!
• The‘Reconcile Human Resources’ process results in ACA codes defaulting on ALL existing Health Insurance for lines 14 (Offer of Coverage) and 16 (Safe Harbor Codes), thus updating the BE020230 (HR Benefit Setup) table incorrectly. These codes ‘should’ default in as ‘None’. Resolved!
• Benefit information was over-written in the UPR00905 table causing incorrect data when more than one Health Insurance code is assigned to an employee. The UPR00905 table was originally designed to hold Affordable Care Act Codes assigned in the Health Insurance Enrollment window for ‘one’ Health Insurance Code per employee. As such, if one employee has multiple Health Insurance codes, the associated ACA codes would be overwritten. Thus we have decided to add a Benefit column to the UPR00905 to enable tracking of multiple Health Insurance Codes with ACA data per employee. Resolved!

• • Going forward, Microsoft Dynamics GP will read ‘covered’ (ACA code assigned) and ‘not covered’ (ACA code not assigned) for Self (the employee), based on the ACA code entered in the Health Insurance Enrollment window.  Previous to the January Hotfix, the employee was considered to be ‘covered’ all the time.
• Note: DON'T WORRY! These changes will not affect Affordable Care Act data you are currently tracking in your system.

Microsoft Dynamics GP 2015 (version will be added upon release)

US Payroll:

• Tax engine  was updated, so you can successfully install Payroll Tax Table Updates. Resolved!
• 2014 Year-End changes are included.

Canadian Payroll: 2014 Year-End and 2015 Tax Update changes are included. It’s very important for Canadian Payroll customer to install the January Hotfix for GP 2015, as it includes all Canadian Payroll tax changes.

PSTL (Professional Services Tools Library):PSTL will load and patch with the January Hotfix. Resolved!

eConnect:Changes with Microsoft Dynamics GP 2013 R2 caused some eConnect stored procedures to update incorrectly. Resolved!

Self Service/Payroll:

• Self-Service time cards do not allow Managers to see start and stop times when approving. Resolved!
• Employee Self-Service time card start and stop times do not work with over-night shift entry. Resolved!

Self Service/Project Accounting: Project Time and Expense encounters the following error while trying to approve a timesheet "Unposted Recognized Revenue : Please set up the Project/Customer/Contract". Resolved!

Affordable Care Act: All Affordable Care Act changes noted for GP 2013 are included in the January Hotfix.

TAX UPDATE LINKS:  Use these links to access the Round 2 Payroll (and previous) Tax Updates and January Hotfix:

Latest U.S. Payroll Tax Update and January Hotfix for Microsoft Dynamics GP 2010:

PartnerSource:
https://mbs.microsoft.com/partnersource/northamerica/deployment/downloads/tax-regulatory-updates/TUGP2010

CustomerSource:
https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/TUGP2010

Latest U.S. Payroll Tax Update for Microsoft Dynamics GP 2013 (January Hotfix available upon release):

PartnerSource:
https://mbs.microsoft.com/partnersource/northamerica/deployment/downloads/tax-regulatory-updates/TUGP2013

CustomerSource:
https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/TUGP2013

Latest U.S. Payroll Tax Update for Microsoft Dynamics GP 2015 (January Hotfix available upon release):

PartnerSource:
https://mbs.microsoft.com/partnersource/northamerica/deployment/downloads/tax-regulatory-updates/TUGP2015

CustomerSource:
https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/TUGP2015

I hope this information is helpful!

Andrea

Hello!

I wanted to provide some information on Service Based Architecture, which is a new feature in Microsoft Dynamics GP 2015.

Service Based Architecture is a method for accessing Dynamics GP functionality through a standards-based services model. The applications and services that leverage Service Based Architecture are created by Microsoft and its partners.

To boil this down, it means that we can utilize logic that is already created in a dictionary in a GP Client and expose that to an endpoint for Consumption.

Design

The introduction of the Web Client in Microsoft Dynamics GP 2013 paved the way for Service Based Architecture. It is deployed in the same installation as the Web Client and the same technologies (Certificates\Firewalls\Internet Information Services) need to be understood.

There are two main differences in the design between the Web Client and Service Based Architecture. The first is that unlike the Web Client which connects directly to the Dex Process, Service Based Architecture connects to the Dex Process via the GP Service and the Dex Service Controller.

The second is the nature of the connection. With the Web Client, it requires a stateful connection. Should the state be lost, Silverlight will produce Async errors. With Service Based Architecture, the connection is stateless.

What can we do with it?

With Service Based Architecture, you can perform the following actions:

• GET - Obtain a list of objects or details on a specific object.
• POST - This action is used for the creation of an object
• PATCH - When an update needs to be done, this HTTP Request Type is used.
• DELETE - This is used when an object needs to be deleted

Here is what is exposed to Service Based Architecture with Dynamics GP 2015 RTM:

• Administration
  • Countries
  • Currencies
  • Payment Terms
• Companies
• Financials
  
  • Checkbooks
  • Currency Accounts Setup
• Inventory
  
  • Classes
  • Item Currencies
  • Item Price Lists
  • Items
  • Item Sites
  • Item Vendors
  • Lot Categories
  • Price Groups
  • Price Levels
  • Sites
  • Transaction Headers
  • Transaction Lines
  • Transactions
  • Unit of Measure Headers
  • Unit of Measure Lines
  • Unit of Measures
• Modules
• Products
• Purchasing
  
  • Payables Transactions
  • Requisitions Transaction Headers
  • Requisitions Transaction Lines
  • Requisition Transactions
  • Vendor Addresses
  • Vendors
• Sales
  
  • Classes
  • Customer Addresses
  • Customers
  • Receivables Transactions

Not all of the above actions (GET | POST | PATCH | DELETE) are available for each of these objects.

Thanks,

Jason Lech | Escalation Engineer | Microsoft Dynamics GP

For more information regarding Microsoft Dynamics GP 2015:

What's New for Microsoft Dynamics GP 2015 Blog Series!

For comprehensive videos - Applications

Microsoft Dynamics GP 2015 New Features - Applications

 Microsoft Dynamics GP 2015 System Wide New Features 

To go straight to the Downloads:

Microsoft Dynamics GP 2015 Product Download Page  

Microsoft Dynamics GP 2015 System Requirements

Up to date information regarding Microsoft Dynamics GP 2015:

Microsoft Dynamics GP 2015 Upgrade Hot Topic

Hello!

Identity Management for the Web Client was introduced in Dynamics GP 2013 R2. This feature allowed us to map our Windows credentials to our Dynamics GP user to allow for a more streamlined login. Here is the blog that discussed this feature when it was released.

https://community.dynamics.com/gp/b/dynamicsgp/archive/2014/06/03/identity-management-for-the-web-client.aspx

With Microsoft Dynamics GP 2015, Identity Management has been extended to include authentication with Organizational Accounts, which are accounts set up in Windows Azure Active Directory.

The biggest benefit comes from the ability to log into Dynamics GP using the same identity when logging into other cloud applications, like CRM Online an Office 365. This prevents being challenged for another set of credentials when utilizing the Web Client and accessing those cloud applications.

The implementation of Identity Management with Organizational Accounts does require knowledge of Windows Azure. In addition to a Windows Azure Active Directory Domain needing to be created with users setup, the global administrator of the domain will need to create an application that will be used to authenticate to Windows Azure Active Directory.

The Web Client installation has included two new windows to address authentication with Organizational Accounts. Dynamics Utilities also has a new option on the Additional Tasks window to handle Organizational Accounts.

The last thing to remember is that when mapping your GP User to an Organizational Account, it has to be done from the Web Client. You are not able to map a GP User to an Organizational Account from the Desktop Client.

Thanks,

Jason Lech | Escalation Engineer | Microsoft Dynamics GP

For more information regarding Microsoft Dynamics GP 2015:

What's New for Microsoft Dynamics GP 2015 Blog Series!

For comprehensive videos - Applications

Microsoft Dynamics GP 2015 New Features - Applications

 Microsoft Dynamics GP 2015 System Wide New Features 

To go straight to the Downloads:

Microsoft Dynamics GP 2015 Product Download Page  

Microsoft Dynamics GP 2015 System Requirements

Up to date information regarding Microsoft Dynamics GP 2015:

Microsoft Dynamics GP 2015 Upgrade Hot Topic

With the announcement of the discontinuation of BP, a new solution has been made available within GP 2015 to allow users to track Employee expenses.  This allows users to enter Project Accounting Employee Expenses, and they will flow through the Workflow 2.0 approval workflows that the users create.

There is also a new Project Time and Expense section that can be added to the Home page. This allows users to quickly see the active Timesheets and Expenses they have entered. Users can also enter or approve Timesheets and Expenses, and they can see a list of recent documents.

Give this new feature a try today!

For more information regarding Microsoft Dynamics GP 2015:

What's New for Microsoft Dynamics GP 2015 Blog Series!

For comprehensive videos - Applications

Microsoft Dynamics GP 2015 New Features - Applications

 Microsoft Dynamics GP 2015 System Wide New Features 

To go straight to the Downloads:

Microsoft Dynamics GP 2015 Product Download Page  

Microsoft Dynamics GP 2015 System Requirements

Up to date information regarding Microsoft Dynamics GP 2015:

Microsoft Dynamics GP 2015 Upgrade Hot Topic

Hello!

Recently we have seen a number of cases coming in that are failing on the following table in the company database: APR_BSSBEN02.  This table is failing to insert the records from the HRPBEN02 table because it needs to create the dependents from beneficiaries. 

If you are currently in the failed state and have created a DexSQL.log, you may see the following statement in the log file:

Cannot insert the value NULL into column 'SEQNUMBR', table 'Databasename.dbo.APR_BSSBEN02'; column does not allow nulls. INSERT fails.

Please run the following script PRIOR to kicking off the Upgrade if you haven't already done so to resolve the issue before you encounter it:
(As always, ensure that you have a valid working backup of the DYNAMICS database and all Company databases before proceeding.)

https://mbs.microsoft.com/Files/customer/GP/Downloads/Updates/CreateDependentsFromBeneficiaries.sql

 
Otherwise, if the database is already in the failed state, you can go through the following steps:

1. Do not restore the company databases.  All troubleshooting can take place at the time of failure.
2. Make sure you have a valid working backup of the Dynamics database and all Company databases before proceeding.
3. Run the following script against all of your company databases.
   

   https://mbs.microsoft.com/Files/customer/GP/Downloads/Updates/CreateDependentsFromBeneficiaries.sql

4. Run the following script against the System Database:
   Delete DU000030 WHERE (Status <> 0 or errornum <> 0) and Status <>15  
5. Launch Microsoft Dynamics GP 2015 Utilities to continue the upgrade from the failed state.

This issue is tentatively set to be fixed in the March Hotfix.

Thanks!
Lance

Sure, Convergence 2015 offers plenty of “wow factor” activities, with keynote speeches from visionary leaders, a surge of stadium-sized rock with OneRepublic, fabulous food, and late night parties in a city famous for its night life. But when it comes right down to it, one of the main reasons for attending Convergence is the support you receive for the products you already use.   I have been privileged to attend Convergence every year since 2003, and can’t wait for the excitement to begin again.

Here are some tips to think about as you prepare for Convergence or why YOU should attend:

1. Bring Your Questions: Write down the issues or ideas you have for improving your processes and find answers at the Experience Center!  

2. Ask Your Coworkers: Not everyone in the company can make it to Convergence, so ask your team mates for their questions and issues.  

3. Prepare for Remote Access: Sometimes the only way to explain a situation is to show us using your own system. At the Experience Center, we can stream into your system with you, so you can show us exactly what’s going on, and we can work with you to come up with a solution.  

4. Talk to Other Customers: Creating relationships with other customers is an important part of Convergence, and will help you long after you return to the office.  

5. Build Your Schedule: Don’t just sit and work in your hotel room! Block time for as many concurrent sessions, keynotes, expo visits, Experience Center sessions, and meetings with customers and partners as you can possibly fit in, and make sure you plan to use the evening events to meet people and have a great time!

6. Find Out What’s New: New features and enhancements can make a huge difference to your business, and Convergence is the best way for you to truly see, hear, and understand the value of these enhancements.  

I feel the experience of Convergence is really amazing.   There are many customers that never get this opportunity. Come feel the love, make connections, and talk to other customers who really understand the system. The relationships you make can last a lifetime, and they’ll help you long after you return to the office.

Click HERE for more information.

Convergence begins in... 10 days, 18 hours, 5 minutes, 8 seconds, see you in Atlanta!

Terry Heley
Microsoft

We've had a couple of questions on how it works when both the Purchase Requisition Approval and Purchase Approval workflow types, for Workflow 2.0, are setup and activated for the same company database, in Microsoft Dynamics GP 2013 R2 and Dynamics GP 2015.

What happens is that when we have both activated in the same company, when we create a requisition and submit it for approval, it goes through the workflow approval process until it has completed all steps and approvals, then in the Purchase Requisition Entry window, we can pull up the requisition, click on Actions > Purchase, and convert it into a purchase order, where it gets a PO number.

However, since we also have the Purchase Order Approval workflow activated, and because we are in essence creating a new purchase order, even though it is from the requisition that has already gone through the approval process, the new purchase order is given a Workflow_Status of 4, meaning it is 'Pending Approval' and if we bring it up in the Purchase Order Entry window, it shows as 'Pending Approval', because it is forced into the Purchase Order Approval workflow steps and process as well. Only once it has completed all of the approval steps in the Purchase Order Approval workflow, does it become a completed purchase order available for use within the Dynamics GP application.

If we only have the Purchase Requisition Approval workflow activated in a company database, the completed PO would receive a Workflow_Status value of 9, meaning the PO Approval workflow is not activated, thus it is not pending any approval.

This is all by design in Microsoft Dynamics GP and is how the system works if both Purchase Requisition Approval and Purchase Approval workflow types are being used in the same company database. The questions we've seen mostly is why the completed requisition, once converted into a purchase order, must go through the approval process again/shows as 'Pending Approval'.

I hope this helps explain this part of the Workflow 2.0 functionality in Microsoft Dynamics GP 2013 R2 and Dynamics GP 2015.

Spring has Sprung in Fargo, ND EARLY this year that is what we are excited about and no flood on the horizon.

Well...yes, I guess we have more to be excited about...what a GREAT Convergence 2015 it was this year.  It was nice to meet many friends and the excitement as we unveil the GP 2015 R2 features, many customers will be upgrading!

OK...let's get back to reality and what I really want to talk about.  What changes are in the March Hotfix.

Microsoft Dynamics GP 2013 (version 12.00.1894)

Affordable Care Act (ACA)– YOU CAN PRINT THE FORMS....WITH LINES!!!!!
Click HERE for detailed documentation changes on ACA.
Dynamics Online Services Changes to cash receipt functionality with credit card payments.

Payroll Self Service Timecard sequence issues when deleting and adding pay codes while entering time.

Distribution Sales order processing to Purchase order processing link may cause duplicate serial numbers on the sales order.

Microsoft Dynamics GP 2015 (version  RELEASING SOON   )

Benefit Self Service There are a variety of fixes for Benefit Self Service, if you plan to setup open enrollment, it would be encouraged to install this hotfix.

Advanced Human Resource dependent window missing ACA field.

Affordable Care Act (ACA) – YOU CAN PRINT THE FORMS....WITH LINES!!!!!
Click HERE for detailed documentation changes on ACA.

Deduction in Arrears
When deduction in arrears is marked, a deduction may be taken from a Business Expense pay type when it is not based on this pay code.
Templates do not advance dates when there is no deduction in arrears to post for mandatory arrears.

Dynamics Online Services Changes to cash receipt functionality with credit card payments.

Web Client
Navigation List display may go to a blank state.
Server side error after applying January Hotfix when you switch companies.

Project Time and Expense
Transactions were not posting to Payables Management.
Incorrect PABillnoteidx values for timesheets entered in the Project Time and Expense entry window.

Payroll Self Service Timecard sequence issues when deleting and adding pay codes while entering time.

Dexterity - 
This issue could cause concern in multiple areas, to name a few, Integration Manager, VBA, Analytical Accounting, etc. the typical error is: Run-time error '70'; Permission deniedPermission denied.
Arabic characters displayed incorrectly.
Distribution
Sales order processing to Purchase order processing link may cause duplicate serial numbers on the sales order.

Download links:

Microsoft Dynamics GP 2013  Customersource                Partnersource
Microsoft Dynamics GP 2015  Customersource                Partnersource

Enjoy!

Terry Heley
Microsoft

Her Magesty's Revenue and Customs (HMRC) has outlined changes to the VAT invoice that offers a Prompt Payment Discount (PPD) to take effect on April 1st, 2015.   This change will affect any VAT (Value Added Tax) registered business that offers their debtors (or customers) a prompt payment discount.  (For example, a business may offer a discount of 2% of the full price if payment is made within 10 days of the date of the invoice.)  This article explains how Microsoft Dynamics GP will handle these changes to the UK VAT law on Prompt Payment Discounts and the action items for you. 

To read more information about this regulatory change for Prompt Payment Discounts and to view an example of a suggested invoice, please refer to the HMRC website for further details.  

Q1.  How does Microsoft Dynamics GP handle this change?

• If the payment is received at the discounted amount before the PPD offer has expired, the transaction and distributions are correct in Microsoft Dynamics GP, and no additional steps are needed. (Refer the EXAMPLE section below for 'Payment Scenario 1'.)

• However, if the payment is received for the full amount after the PPD offer date has expired, then additional steps would be needed, as the payment will have an 'unapplied' amount left on it in the amount of the discount.  (Refer the EXAMPLE section below for 'Payment Scenario 2'.)

• There are no changes to the invoice form in Microsoft Dynamics GP.   You will be responsible for modifying the invoice form as noted in the HMRC website as desired.  (For guidelines on when a support case becomes a consulting engagement for any report modification, please refer to KB 850201.)

Q2.  If the full amount was received after the PPD offer date expired, what does the user need to do?

The HRMC suggests two options:

Option 1:  You may enter a credit note for the amount of the discount to evidence the reduction in consideration.

Option 2: Or alternatively, you can edit the invoice form to show both the original and discounted amounts and add a statement that the customer can only recover as input tax the VAT paid to the Supplier.  Refer to the HMRC website for the exact wording.  If you follow this option, the user must also: 

a.  Enter a debit memo in Microsoft Dynamics GP for the 'unapplied' amount (ie. discount amount), and apply it to the unapplied amount on the cash receipt.

b. The user should install and run the 'VAT Tax Routine' to update the tax tables with the correct amounts, so the correct amounts are reported on the VAT return.  

Q3.  What does the 'VAT Tax Routine' do?

The VAT Tax Routine will:

• Print a report for all Debtors to show all payments that have an unapplied amount left on them. 

• Update the tax tables with the correct original full amounts so the invoice amount and tax amounts are correct, and can be accurately reported on the VAT return. 

Q4. Where can I download the hot fix for the  'VAT Tax Routine'?

• If using Microsoft Dynamics GP 2010 SP4 or higher, click HERE for the hot fix.

• If using Microsoft Dynamics GP 2013 R2 or higher, click HERE for the hot fix.

• If using Microsoft Dynamics GP 2015 RTM or higher, click HERE for the hot fix.

*IMPORTANT NOTES:
• You must be running GP2010 SP4 (version 11.00.2248 or higher), GP2013 version (12.00.1745 or higher), and GP2015 (version 14.00.524 or higher) to apply these hot fixes. 
• Each zip file includes a VatDaybk.cnk, Procs.sql and Readme.txt file.  Please follow the Readme.txt instructions carefully.
• Also remember that this hot fix could get overwritten if you install a patch release over it that does not yet include this hot fix.
• After you install the hot fix to create the VAT Tax Routine, it can be found under Microsoft Dynamics GP | Tools | Routines | Company | VAT Tax Routine.

Q5. Do I need to run the VAT Tax routine if I use VAT 100 instead of VAT Daybook?

You will want to run the VAT Tax routine if you have customers that pay a full amount after the PPD offer date has expired, whether you are using VAT 100 or VAT Daybook, the steps will be the same.  Both modules pull from the same tax tables.

-----------------------------------------------------------------------------

EXAMPLE:  Here is an example of both payment scenarios:

Scenario:  

• The 'Calculate Terms Discount Before Taxes' option is marked in the Company setup options.
• The debtor will receive a 2% discount if paid within 10 days (on the Sale/Purchase and Tax).
• The debtor has one tax detail for 20%.
• A sales invoice is entered for £1000.  VAT tax is £200 (20% tax) and PPD offered is £20 (2% discount).

Example:

Sales invoice dated April 5, 2015 would have these distributions:

SALES                           (1000)
TAX                                (196)     --20% tax on the £1000 minus 2% PPD offer (£200 - £4)
AVAIL         20                             --2% PPD offer available on the £1000 sale.RECV       1176
RECV       1176

Payment Scenario 1:  Payment made April 10, 2015 (within 10 day discount date)* would have these distributions:

CASH      1176
TAKEN        20                             --records discount taken
AVAIL                              (20)      --clears out Discount Available account
RECV                           (1176)

*If the payment is made within the discount period, the transaction and distributions are correct.  No further adjustment is needed.

Payment Scenario 2:  Payment made April 28, 2015 (made after discount date)** would have these distributions:

CASH       1200
AVAIL                           (20)
RECV                         (1180)       --Offsets £1176 debit, so difference of £4 in remains in Receivables account

**If the payment is made after the discount date, the payment has £4 left unapplied.  An adjustment is needed to fully apply the payment and clear the receivable.  To do this:

1. Key a debit memo: 

a.  Enter £4 in the Tax field.
b.  In the Tax Entry window, enter the VAT tax detail.
c.  Leave the sales amount field blank.
d. Apply to the £4 left unapplied from original cash receipt.

2.  Post.

The default distributions are:
TAXES                  (4)
RECV       4                       --clears out the Receivables account for the difference above

Most debtors usually take the PPD discount, so hopefully the debtors you need to key debit memos for will be low in number.  

-----------------------------------------------------------------------------------------

I hope this information will be helpful to you.  Please refer to the HMRC website for any additional guidance.

Thank you!

Cheryl Waswick | Sr. Technical Support Engineer | Microsoft Dynamics GP

Hi Everyone,

Since many new customers are activating Human Resources (HR) at this time, I have been seeing a common question arise for Health Insurance codes especially this question, so I wanted to share it with you:

Q:  When I run the HR Reconcile utility for 'Update Benefit Setup' and "Update Benefit Enrollment', I have noticed that Inactive benefit/deduction codes on the Payroll side are getting created on the HR side as well, but they are marked as Active on the HR side still (and should also be inactive).   In GP I can only mark the code inactive in the HR Enrollment window (ie. one employee at a time).   The 'main' setup for the code does not have an Inactive field that I can roll down.  Therefore, how can I do a mass update to get this code inactive on the HR side?

A:  The reconcile utility will create all codes (even inactive codes), however, since the all the Status codes available on the HR side don't all exist on the Payroll side, the utility does not set this field for you and this is currently the design.   The user should be verifying all the fields are correct.  As mentioned above, you can inactivate the code on the HR side one employee at a time but GP does not have a 'mass' update feature to do this.   Therefore, to do this in mass, you would have to do this in SQL Server Management Studio.  Run the below script against the company database for the respective benefit/deduction code and it will set this code to be inactive for all employees

enrolled in the respective code on the HR side:

Keep in mind that the HR side has more fields than the Payroll side, but it is the Payroll side that is used in a checkrun, so the code will not be used in the checkrun anyway if the Payroll side is inactive.

*Before running any update script, it is always recommended to make a current backup copy of the company database first!

Scenario 1: DEDUCTIONS ONLY: The first script below will 'find' where the status code on the deduction on the HR side does not match the status code on the same code in the Payroll Deduction Master table, so you can view what codes do not match.  Then run the second script to 'update' the status on the HR side and the End Date, to match the status and End Date as stored on the Payroll side. Run these scripts against the company database to affect deduction codes only:

DEDUCTIONS:
---------------------------------------
Select a.EMPLOYID, a.deducton as 'Deduction', b.inactive as 'HR_Active',
a.inactive as 'Payroll_Active', a.DEDENDDT as 'DED End date'
from UPR00500 a
join BE010130 b
on a.EMPLOYID = b.EMPID_I
and a.DEDUCTON = b.BENEFIT
where a.INACTIVE <> b. inactive
---------------------------------------
update a set a.inactive = b.inactive, a.BNFENDDT = b.DEDENDDT
from BE010130 a
join UPR00500 b
on b.EMPLOYID = a.EMPID_I
and b.DEDUCTON = a.BENEFIT
where b.INACTIVE <> a.INACTIVE
-------------------------------

IMPORTANT NOTE: The benefit and deduction codes may have the same code ID, and are stored in two different tables on the Payroll side (UPR00500 and UPR00600), however, they are stored together as one record in only one table on the HR side (BE010130). So take note what script you ran last as it will overwrite the status and End Date on the record in HR, and will apply to both the benefit and deduction on the HR side. So if you have any instances where the deduction is inactive, but the benefit is active (or visa versa), you will need to pay attention to what script you ran last. It is recommended for these situations to view the code in the front-end and activate back the one needed in the front-end.

Scenario 2: BENEFITS ONLY:  The first script below will 'find' where the status code on the benefit on the HR side does not match the status code on the same code in the Payroll Benefit Master table, so you can view what codes do not match. Then run the second script to 'update' the status on the HR side and the End Date, to match the status and End Date as stored on the Payroll side. Run these scripts against the company database to affect benefit codes only:

BENEFITS:
---------------------------------------
Select a.EMPLOYID, a.BENEFIT as 'Paycode', b.inactive as 'HR_inactive',
a.inactive as 'Payroll_inactive', a.BNFENDDT as 'BEN End date'
from UPR00600 a
join BE010130 b
on a.EMPLOYID = b.EMPID_I
and a. BENEFIT = b.BENEFIT
where a.INACTIVE <> b. inactive
---------------------------------------
update a set a.inactive = b.inactive, a.BNFENDDT = b.BNFENDDT
from BE010130 a
join UPR00600 b
on b.EMPLOYID = a.EMPID_I
and b.BENEFIT = a.BENEFIT
where b.INACTIVE <> a.INACTIVE
---------------------------------------

IMPORTANT NOTE: The benefit and deduction codes may have the same code ID, and are stored in two different tables on the Payroll side (UPR00500 and UPR00600), however, they are stored together as one record in only one table on the HR side (BE010130). So take note what script you ran last above as it will overwrite the status and End Date on the record in HR, and will apply to both the benefit and deduction on the HR side. So if you have any instances where the benefit is inactive, but the deduction is active (or visa versa), you will need to pay attention to what script you ran last. It is recommended for these situations to view the code in the front-end and activate back the one needed in the front-end.

Scenario 3: ALL: Use this script if you know a code (benefit and deduction) is inactive on the Payroll side for 'all' employees, and you just want to update the status for all the employees enrolled in it on the HR side too: (The first script will find all records for that code, whether a benefit or deduction, where it is not inactive on the HR side, and the second script will update the status for that code to be inactive for all employees enrolled in it on the HR side.)

Select * from BE010130 where BENEFITSTATUS_I <> '2' and BENEFIT = 'xxx'
---------------------------------------------------------------
update BE010130 set BENEFITSTATUS_I = '2' where BENEFIT = 'xxx'

--update the xxx placeholder for the benefit or deduction code that you would like to mark as inactive on the HR side. Note that this script just sets the INACTIVE status and does not update the Benefit/Deduction End Date on the HR side. Also refer to the note above in Scenario 2.

Benefit Status values mean:
1=active
2=inactive
3=waived

ADDITIONAL:

Note that if you are enabling HR for the Affordable Care Act, be sure to install the March Hot Fix that has just released.  (It includes the January Hot Fix in it.)  But you can read about the changes that were included in both for the Affordable Care Act using the blog links below:

MARCH HOT FIX:
https://community.dynamics.com/gp/b/dynamicsgp/archive/2015/05/08/the-march-hotfix-has-released-what-is-all-the-excitement-about.aspx

JANUARY HOT FIX:
https://community.dynamics.com/gp/b/dynamicsgp/archive/2015/01/23/draft-microsoft-dynamics-gp-2015-round-2-payroll-tax-update-what-you-need-to-know.aspx

I hope this information is helpful to you. 

Thanks,

Cheryl Waswick  | Sr. Technical Support Engineer | Microsoft Dynamics GP

--------------------------------------------------------------------------------------

Hello everyone!

You may be familiar with this one, as it has been going on for some time now. When you open up a Navigation List, click to preview a record in the list, the Preview Pane will show HTML code instead of the properly formatted data you would expect to see. The only known "workaround" we had was to rename the Dynamics.EXE.config file. This would cause any DLL-dependent features (Workflow 2.0, Document Attach, etc.) to stop working, so we don't recommend doing this anymore.

We could not recreate this issue accurately enough internally to get a good fix in place, and the fix kept getting pushed back due to testing difficulties. However, this IS currently slated for a GP 2015 "R2" release, as we have been able to reproduce and resolve internally.

If you have an add-in installed to GP, which is indicated by the presence of a DLL in the "Addins" folder, then this issue will not occur anymore.

Dan Peltier

GP Systems Support Engineer

Hello -

It has been identified that in some scenarios after an upgrade to Microsoft Dynamics GP 2015, the following error is encountered within Microsoft Dynamics GP:

We have seen the above referenced error occur in the following modules:  GL, Payables, Payroll and Project.  This issue appears to be stemming from missing data in the WF100001 table.  The results of the WF10001 table in the company database, should look like this:

When users are encountering the error referenced above, we see the following results in the WF10001 table:

The WfTypeHistBusObjKey is not getting populated for all of the Workflow types which is causing an error in the substring.  At this point in time, this issue only seems to appear on databases that have been upgraded.  This does not appear to happen on a brand new installation in which the databases themselves (System and Companies) are created brand new on Microsoft Dynamics GP 2015. 

Development has been made aware of this issue and it will be addressed in a future release.  In the meantime, the workaround is pretty simple.  You will need to update the WfTypeHistBusObjKey for the appropriate Workflow_Type_Name that is missing data.

Here are examples of scripts that you may need to run depending on what Workflow_Type_Names have data missing:

update WF100001
set WfTypeHistBusObjKey = 'SY30500~BACHNUMB~BCHSOURC~CREATDDT~TIME1'
where Workflow_Type_Name = 'General Ledger Batch Approval'

update WF100001
set WfTypeHistBusObjKey = 'PM00200~VENDORID'
where Workflow_Type_Name = 'Vendor Approval'

update WF100001
set WfTypeHistBusObjKey = 'PTE30500~PTE_Empl_Expense_Doc_No'
where Workflow_Type_Name = 'Expense Report Approval'

update WF100001
set WfTypeHistBusObjKey = 'PM30100~BACHNUMB~BCHSOURC~CREATDDT~TIME1'
where Workflow_Type_Name = 'Payables Batch Approval'

update WF100001
set WfTypeBusObjKey = 'SY00500~BACHNUMB~BCHSOURC~CREATDDT~TIME1'
where Workflow_Type_Name = 'Receivables Batch Approval'

update WF100001
set WfTypeHistBusObjKey = 'HR30100~EMPLOYID~CREATDDT~CREATETIME'
where Workflow_Type_Name = ‘Employee Skills Approval’

update WF100001
set WfTypeHistBusObjKey = 'DD20100~EMPLOYID'
where Workflow_Type_Name = 'Payroll Direct Deposit Approval'

update WF100001
set WfTypeHistBusObjKey = 'UPR30600~EMPLOYID~CREATDDT~CREATETIME'
where Workflow_Type_Name = 'Employee Profile Approval'

update WF100001
set WfTypeHistBusObjKey = 'UPR30604~EMPLOYID~SEQNUMBR'
where Workflow_Type_Name = 'Payroll W4 Approval'

Thank you!
Sarah

Hello!

We have ran into a couple cases where a Purchase Requisition went through the approval process. After that the users were looking to convert it to a Purchase Order by following these steps Actions>>Purchase (see Image 1) on the Purchase Requisition Entry Window. Unfortunately the Purchase option was missing. We found that the SOP module was not checked in the Registry (see Image 2) in both cases. If the SOP module is not checked, you will not be able to see the Purchase option on the Purchase Requisition Entry Window.

IMAGE 1

IMAGE 2

Please be sure to check this setting if you happen to be missing the Purchase option in the Purchase Requisition Entry Window.

Thanks,

Ross