Month: May 2014

The Inside Microsoft Dynamics GP blog started a series of Microsoft Dynamics GP 2013 R2 Feature of the day posts the other day. As they did with the Microsoft Dynamics GP 2013 Feature of the Day posts they are doing them as short posts containing a PowerPoint slide show. I am translating these from the PowerPoints into posts; you can find my series index here.

The fourteenth Feature of the Day covered is Document Attach – Scan. Document Attach was introduced in Dynamics GP 2013 and with every service pack has been further enhanced; Dynamics GP 2013 R2 is no exception with the introduction of a Scan feature.

The Scan feature allows you to attach a paper document directly into Microsoft Dynamics GP 2013 R2 using an attached scanner (previously you had to scan using external software which made attaching scanned documents a two-step process; scan the document to get a soft copy onto the computer and then go to the Document Attachment Management window of choice and attach it).

Now, just load the document into the scanner and choose the Scan button on the Document Attachment Management window of choice, and the document will be scanned and attached in one step.

The Inside Microsoft Dynamics GP blog started a series of Microsoft Dynamics GP 2013 R2 Feature of the day posts the other day. As they did with the Microsoft Dynamics GP 2013 Feature of the Day posts they are doing them as short posts containing a PowerPoint slide show. I am translating these from the PowerPoints into posts; you can find my series index here.

The thirteenth Feature of the Day covered is Default Sort Order for Checks.his feature gives users the option of defining a default sort order for printing checks in the Payables Management Setup (Purchasing » Setup » Payables):

Sort Options will be:

• Payment Number
• Name
• State-City
• Zip Code

This will remove the need to manually change the sort option at the time of printing checks. However, it would have been nice to also have the Vendor ID included in the options.

This feature is targeted at the following roles:

1. Accounting Manager
2. Accounts Payable
3. Bookkeeper

The Inside Microsoft Dynamics GP blog started a series of Microsoft Dynamics GP 2013 R2 Feature of the day posts the other day. As they did with the Microsoft Dynamics GP 2013 Feature of the Day posts they are doing them as short posts containing a PowerPoint slide show. I am translating these from the PowerPoints into posts; you can find my series index here.

The twelfth Feature of the Day covered is Requisition Management Integration Points . Purchase Requisitions has been written to integrate with several other areas of Dynamics GP such as Doc Attach, Encumbrance Management and SmartLists:

Continue reading “MDGP 2013 R2 Feature of the Day: Requisition Management Integration Points”

The Inside Microsoft Dynamics GP blog started a series of Microsoft Dynamics GP 2013 R2 Feature of the day posts the other day. As they did with the Microsoft Dynamics GP 2013 Feature of the Day posts they are doing them as short posts containing a PowerPoint slide show. I am translating these from the PowerPoints into posts; you can find my series index here.

The eleventh Feature of the Day covered is Reprint Outstanding Transaction in Bank Reconciliation. The Outstanding Transactions Report option has been added in the Bank Posting Journals report list (Financials » Reports » Posting Journals):

Continue reading “MDGP 2013 R2 Feature of the Day: Reprint Outstanding Transaction in Bank Reconciliation”

The Inside Microsoft Dynamics GP blog started a series of Microsoft Dynamics GP 2013 R2 Feature of the day posts the other day. As they did with the Microsoft Dynamics GP 2013 Feature of the Day posts they are doing them as short posts containing a PowerPoint slide show. I am translating these from the PowerPoints into posts; you can find my series index here.

The tenth Feature of the Day covered is Workflow Calendar.

In the new Workflow system for Microsoft Dynamics GP2013 R2, each step in a workflow can be given a time limit which calculates a due date/time by which the task must be completed. The Workflow Calendar allows users to define standard working hours for the company and holidays; this calendar can then be used in calculating the due date/time of a task so non-working days or time does not count against the time limit to complete the task.

For example, if a task with a time limit of 8 hours is assigned at 4:00 on Friday afternoon, and the company’s working hours are Monday to Friday, 8:00am to 5:00pm, then the due date/time for the task is set to 3:00pm the following Monday.

I’m liking the look of the new Workflow, although I do want to have a dig into the technical side of it. That said it does seem to have some good functionality with this calendarbeing useful (I’m assuming a little here) for reminders and reporting.

The Inside Microsoft Dynamics GP blog started a series of Microsoft Dynamics GP 2013 R2 Feature of the day posts the other day. As they did with the Microsoft Dynamics GP 2013 Feature of the Day posts they are doing them as short posts containing a PowerPoint slide show. I am translating these from the PowerPoints into posts; you can find my series index here.

The ninth Feature of the Day covered is Identity Management – Scalability Groups. The Identity Management Scale Groups provides flexible deployment options and improved efficiency for multitenant web client deployments. Using scale groups, you can logically group the web client session host servers that have a common configuration and host the same tenants. The web servers shared by all tenants will then be able to efficiently distribute tenant load across the session host servers configured for that tenant.

This should make it a lot easier to work in a cloud deployment of Dynamics GP.

The diagram below shows a GP multitenant web client deployment with two scale groups configured:

This feature is targeted at the following roles:

1. Administrator

The Inside Microsoft Dynamics GP blog started a series of Microsoft Dynamics GP 2013 R2 Feature of the day posts the other day. As they did with the Microsoft Dynamics GP 2013 Feature of the Day posts they are doing them as short posts containing a PowerPoint slide show. I am translating these from the PowerPoints into posts; you can find my series index here.

The eighth Feature of the Day covered is Default Fixed Asset ID From The Asset Class. Microsoft Dynamics GP 2013 saw the introduction of feature which allowed the Asset ID to be defaulted in the same way as the Voucher Number. GP 2013 R2 has seen this feature extended further to allow each Asset Class to have it’s own Asset ID range defaulting.

In Asset Class setup (Financials » Setup » Fixed Assets » Classes) a class can be set to have a Next Asset ID which has a prefix and ID unique to the class:

I can see this being very useful to a number of my clients using Fixed Assets where they have a number of different asset classes where having different prefixes for the different asset types would be very useful.

The Inside Microsoft Dynamics GP blog started a series of Microsoft Dynamics GP 2013 R2 Feature of the day posts the other day. As they did with the Microsoft Dynamics GP 2013 Feature of the Day posts they are doing them as short posts containing a PowerPoint slide show. I am translating these from the PowerPoints into posts; you can find my series index here.

The seventh Feature of the Day covered is Workflow User Delegation. The new workflow creates task assignments for users with a due date/time by which the task must be completed.

Users have the option to delegate task assignments to another user on a task-by-task basis, but also if a user will be out of the office for an extended period of time, the system also offers the option to set up automatic delegations to reassign the task.

In the Workflow User Delegation window delegation can be configured for all workflow types, or delegation can be configured on a per type basis:

Once delegation configuration is complete, if a task is assigned to the user while he or she has turned on the automatic delegations, the task is then automatically delegated to the assigned delegate.

The Inside Microsoft Dynamics GP blog started a series of Microsoft Dynamics GP 2013 R2 Feature of the day posts the other day. As they did with the Microsoft Dynamics GP 2013 Feature of the Day posts they are doing them as short posts containing a PowerPoint slide show. I am translating these from the PowerPoints into posts; you can find my series index here.

The sixth Feature of the Day covered is Workflow Types. The new Workflow system in Dynamics GP2013 R2 includes only four workflows, although Microsoft Dynamics GP 2015 coming later in this calendar year will include more.

The Microsoft Dynamics GP 2013 R2 Workflows:

1. Purchase Order Approval
2. Purchase Requisition Approval
3. Payroll Timecard Approval
4. Project Timesheet Approval

Others that are on the list for inclusion in Microsoft Dynamics GP 2015 are Project Expenses, Sales Order, and Batches although this list is subject to change.

These workflow types allow users to create workflow processes around each of the respective document types, requiring the workflow to be completed before defined document processes can be performed.

To show an example of workflow in GP 2013 R2, below is the Purchase Order Processing (Purchasing » Transactions » Purchase Order Processing) form:

As you can see there is a workflow notification bar below the ribbon which shows the workflow status, as well as a couple of buttons on the ribbon.

The Workflow button itself gives access to the Approve/Reject and Delegate actions:

The Inside Microsoft Dynamics GP blog started a series of Microsoft Dynamics GP 2013 R2 Feature of the day posts the other day. As they did with the Microsoft Dynamics GP 2013 Feature of the Day posts they are doing them as short posts containing a PowerPoint slide show. I am translating these from the PowerPoints into posts; you can find my series index here.

The fifth Feature of the Day covered is Workflow. Previously there was a Workflow module available with Microsoft Dynamics GP which sat on top of SharePoint; Microsoft Dynamics GP 2013 R2 sees the introduction of a new Workflow module which does not sit on top of SharePoint. Instead it is now a Microsoft Dynamics GP window which means it is easier to deploy, access and customise and allows users to design workflows, such as approval paths, for documents in Dynamics GP.

In Microsoft Dynamics GP 2013 R2, four types of workflow is available for use: Purchase Order Approval, Purchase Requisition Approval, Payroll Timecard Approval, and Project Timesheet Approval. Other workflow types will be introduced in future releases.

I have a number of clients who are looking for the functionality available within Workflow. While they could have used the SharePoint based Workflow module I have been recommending delaying until the rewrite was complete so I am really looking forward to this one being available. Especially as it removes the need for SharePoint and the problems which go along with integrating it with GP.