1/22/2013

How to Publish Management Reporter Reports to SharePoint

Recently I was asked to integrate Management Reporter reports to SharePoint Foundation 2010. With Management Reporter 2012, it's quite simple to achieve.
 
All you have to do is to follow the steps below
 
1. Go to SharePoint site and create a document library.
 
2. Assign site permissions for the people who need to see the reports. Also provide Design and contribute permissions to the Management Reporter process service user.
 
3. Go to Management Reporter and choose the report from report definitions you'd want to publish to SharePoint.
 
4. Click Output and Distribution tab from the report definition.
 
 

5. Check Generate to multiple report library locations and add the SharePoint document library link in Related Report Link location as shown below.
 
 
6. If you want this report to be automatically publishing to SharePoint, You can setup a report schedule in Report scheduler.
 
7. You can see the reports in SharePoint like this.
 
 
 
8. When you click any report, it'll open like this where you can have the option of viewing it in Excel, Report viewer or XPS document. You can also set a default view so that next time it won't ask for a choice.
 

Deletion of company in Management Reporter


One might see this error when attempting to delete a company in Management Reporter Configuration console.

 

"This company is referenced by an existing report definition or reporting tree definition. Remove these associations before deleting the company"


For those who aren't aware as to how to delete or create a company in Management Reporter, It happens through configuration console which only Administrators can see that.  

The first step of troubleshooting is to go and see if any existing report definitions or reporting tree definitions linked to this company.Change those definitions to other companies so that those references to the company in question are removed, if any.
 
There might be occasions where the company cannot be deleted despite no visible references in the definitions.
 
To troubleshoot this, Go to Management Reporter service logs in the configuration console. This is the first level of troubleshooting for Management Reporter. Anything goes wrong, one must go and see what exactly the log is telling you. I got a log like this
 
System.Data.SqlClient.SqlException (0x80131904): The DELETE statement conflicted with the REFERENCE constraint "FK_ControlTreeDetail_ControlCompany". The conflict occurred in database "ManagementReporter", table "dbo.ControlTreeDetail", column 'CompanyID'.

System.Data.SqlClient.SqlException (0x80131904): The DELETE statement conflicted with the REFERENCE constraint "FK_ControlReport_ControlCompany". The conflict occurred in database "ManagementReporter", table "dbo.ControlReport", column 'CompanyID'. The statement has been terminated.

To resolve this, I went to Management Reporter database and took a backup of the same. Then, I ran the below statement to get the company ID
 
SELECT * FROM DBO.CONTROLCOMPANY
 
You can retrieve the company ID from ID column in the said table. The company database ID will be stored in the corresponding Code column.
 
I ran the following delete statements on two tables.
 
DELETE FROM DBO.CONTROLTREEDETAIL WHERE ID = '123' (Replace 123 with the ID retrieved from control company table)
 
DELETE FROM DBO.CONTROLREPORT WHERE ID = '123' (Replace 123 with the ID retrieved from control company table)
 
These statements above will delete all orphaned references in the report definitions and reporting tree definitions related tables for the company to be deleted.
 
After the above statements, we can go to configuration console and delete the company by just clicking 'Delete company'.

1/16/2013

Microsoft Dynamics GP 2013 VPC Download

Folks at Microsoft Dynamics are quick enough to provide us with the latest Microsoft Dynamics GP 2013 RTM V1 Hyper-V image for download on partner source.
 
The image is supposed to have the following.
  • Dynamics GP 2013 RTM Code with Web Client deployed
  • Management Reporter 2012 with Web Viewer deployed
  • Office 2013 with demo dashboards installed
Proceed to download this image from here.
 
 
More information from the original source.
 
Where's the Demo Image??? HERE! Today!
 

1/07/2013

Dynamics AX 2012 Purchase Requisitions

Procurement process in organizations is very critical such that right items are ordered at the right time. Often, companies end up with cost overruns partly due to bad purchasing planning or policies. It’s all about meeting the demand of materials or services within the stipulated time and minimal costs.  
One of the key success criteria set by the Purchasing departments when it comes to choosing the best ERP in the market revolves around efficient management of procurement cycle like Purchase Requisition workflow driven process, RFQ process, Catalog and non-catalog based purchases, vendor responses analysis.
 
The Finance department asks for creating commitments for those purchases to plan for their working capital needs. If the expenditure is incurred towards a project, the project information is also sought for. More importantly, a Finance Manager would always be interested in distributing the expense to multiple cost centers/departments than just to distribute it to one default account.
 
Organizations hate to come to terms when we inform them that you can’t create requisitions in multi-currency or you can’t link your projects to the requisitions or for that matter you can’t set the GL distributions to multiple accounts.
 
Here is where solution like Microsoft Dynamics AX 2012 sets its foot stronger than its peers with its extensive functionality in procurement and sourcing to address these gaps.
Keeping this background in mind, let’s look at what Microsoft Dynamics AX2012 has in its store for the purchasing managers specific to Requisitions. AX 2012 can offer the best in class out of the box functionality through its procurement and sourcing module.
 
Some of the features are listed below through this module highlighted upon Purchase Requisitions. 
  • Purchase Requisition in Built workflow process
  • Requisitions can be submitted for approval by multiple users
  • Requisitions can be created through AX Client/Enterprise Portal/Employee self-services
  • Requisitions can be created by users to choose from existing procurement catalogs (internal catalogs). This is very helpful for some clients. Requisitions can be created for non-catalog items.
  • Multiple GL distributions can be attached to each Requisition line (Expense allocation becomes easier)
  • Budget control validation & Commitments through Encumbrances
  • Attach documents/images
  • Create Requisitions in Multi-currency
  • Attach Project Information to the Requisitions & Project Budget linking
  • Attach Fixed Assets information to the Requisitions
  • Create Purchasing Policies and thereby link them to Requisitions
  • Have the users fill up Questionnaires justifying their purchases
  • Create RFQ from Requisitions and Accept replies from RFQ to be copied over to Requisitions
  • Transfer requisitions to Purchase orders manually/ automatically/through demand consolidation
In order to address some of the business needs we discussed above like RFQ process, Multi-currency Requisitions, Project linking to requisitions, attaching Multiple GL distributions, Customers have to look at some third party products to address the gaps which are otherwise available as standard features in AX 2012.  Choosing Dynamics AX 2012 leaves tremendous advantage for Customers that they enjoy less implementation cost overruns and less maintenance costs.

Dynamics GP 2013 Licensing changes

Overview

A new licensing model called “Perpetual Licensing” came into effect replacing the BE & AM Licensing structure.

Under the new licensing, the Business Essentials (BE) & Advanced Management (AM) are replaced with Starter Pack and Extended Pack.

Under the new licensing, Users are classified as Full User and Limited User CALs

The Starter pack includes 3 Full Users

Few La Carte modules like Smart list Builder, HR & Payroll, and customization pack so on

Modules


Starter pack


      Financial Management
      Human Resource Management, including the Self-Service Suite
      Supply Chain Management
      Workspace Collaboration
      Configuration and Development
      Business Intelligence & Reporting

Extended Pack Modules
 
 
Business Intelligence & Reporting (Unlimited Forecaster)
 
Supply Chain Management (additional modules)
 
Manufacturing Solutions
 
Project Management
 
Customer Relationship Management (not Dynamics CRM)
 
 
 
Business Portal and Management Reporter

Unlimited business portal users under starter pack

Unlimited Management Reporter users under starter pack

Full Users Vs. Limited Users

The activities of the users drive these two user types. 
 
Full users have full read and write access in the system. 
Limited users have full read access but limited write access, for specific areas like time entry and expense management. 
Be it web client, desktop client, it doesn’t matter for these users licensing. It’s by activity types.

For Existing Customers

This new licensing will affect the existing customers licensing (Customers on BRL & MBL). These customers are classified under
License Migration Transition Upgrade (LMT) 
License Credit Transition Upgrade (LCT).
 
LMT is applicable for customers with GP2010 or prior who have purchased prior to 1st Oct 2012. LCT is applicable for customers purchased the software on or after 1st Oct 2012.

With the LMT Upgrade, MBL and BRL are mapped to the Perpetual Licensing model to ensure that customers receive at least their current functionality plus the number of users.

The LCT Upgrade is conducted through a license investment credit aligned with the Microsoft Dynamics Licensing Transition Policy.

Even after the transition, Customers can continue to use their old versions but they cannot add new modules to the old versions.

Example for LMT:

If a customer purchased 10 user licenses before Oct 1st 2012 under BE, they will get Starter pack plus 7 Full user licenses. If they purchased under AM, they will get starter pack, extended pack plus 7 full user licenses. In both cases, balance to be paid to Microsoft is 0.

Example for LCT:

If a customer purchased 10 user licenses on or after Oct 1st 2012 under BE, they will get Starter pack plus 7 Full user licenses. If they purchased under AM, they will get starter pack, extended pack plus 7 full user licenses. In both cases, they have to pay for the licensing difference.
 
Note: This post is compiled based on my personal understanding of the licensing structure and intended for informational purposes only. Please let me know if any corrections are required to the post.