Microsoft Dynamics Blog

Welcome to Armanino’s Microsoft Dynamics Blog, where you’ll find information on topics across Microsoft Dynamics 365 ERP and CRM, Dynamics GP, Power BI, PowerApps, Flow and more. Use these tips, tricks and insights to get the most out of your applications! Want these articles delivered straight to your inbox? Subscribe to our newsletter below.

Thursday, November 29, 2018

Dynamics 365 PSA vs Projects Module: Maybe You Don’t Have to Decide

Posted by Michelle Monnin

Dynamics 365 PSA vs Projects Module: Maybe You Don’t Have to Decide

Last year, I wrote a blog comparing Project Service Automation (a newer offering in the Customer Engagement suite) to the Projects module in Dynamics 365 Finance & Operations.  Since then, Microsoft has worked to integrate the two similar offerings.

Below is the vision Microsoft shares of how they see these two areas interacting:

Dynamics 365 PSA vs Projects

The integration between Project Service Automation (PSA) and Projects  is built on the new Common Data Service 2.0 (CDS) which is based on the xRM platform.  It’s a direct connect and utilizes the Power Query tool in PowerApps. It also requires PSA version 9.0 or higher.  What Microsoft is delivering as of July 2019 is in two general areas:  Templates and a PSA Integration Parameters form which included defaults and functionality locking.  Each area is covered in more detail below:

Templates

These are really PowerApps that are predefined by Microsoft to move data from PSA to Projects.  The mapping is done for you although you can edit it as needed by your organization.  They utilize the Power Query tools within the PowerApps and prefilter data such as excluding the import of regular sales orders and importing only projects contracts. The Power Query allows the PSA Organizational Unit field to be filtered so that the projects are imported to a specific Finance & Operations legal entity.

Templates currently available in Finance & Operations 7.3 or 8.x are:

  • Project contracts and projects which brings in the following:
    1. Project Contracts
    2. Projects
    3. Project contract lines
    4. Project contract line milestones
  • Project tasks (to record activities)
  • Project expense categories
  • Hour estimates (to come into project forecasts)
  • Expense estimates (to come into project forecasts)
  • Actuals (Time entry and expense entry)

Actuals come into a new source document that looks like a journal called Dynamics 365 for Project Service Automation integration journal.  It is periodically brought into a staging table. This new journal is just used for integration purposes and entries cannot be manually created in it.  You can edit the accounting data or delete bad data.

Integration Parameter Form

If you look at the graphic at the beginning of this blog, Microsoft has a vision of how the data should flow from PSA to Projects, but they respect that each company may have different requirements.  The parameter locking allows you to say which fields are locked down and not updatable in Finance & Operations.  For example, you could lock down Project Contract, Project Quote, the Work Breakdown Structure (WBS) or even the Project itself and have that data created and edited only in PSA.  What is brilliant about the locking is it only applies to projects originating in PSA.  Kim showed another project that existed only in Finance & Operations where those fields were not locked down.  Also, on the PSA Integration Parameters form is where you specify default values for fields that do not exist in PSA such as Project Type, Time Category and Fee Category.  It also is a place to map PSA Project Time and Material and Fixed-Price to the related Project Group as well as PSA Billing Type to Line Property.

A few issues worth noting:

  • PSA does not support internal projects such as R&D projects. All projects in PSA are currently tied to a project contract and are billed either as Time & Material Projects or as Fixed Price projects.
  • If your billable PSA project has a combination of Time & Material and Fixed Price in Finance & Operations, they must be set up as two separate projects.
  • Future templates include the WBS, Billing, Bookable Resources, as well as Expenses from Finance & Operations to PSA. Those are not available today unless you create them yourself.
  • PSA doesn’t support sub-projects.
  • Purchasing can only occur in Finance & Operations. This may change in the future.

Here’s a link to the presentation from the Business Application Summit:  https://www.microsoft.com/en-us/businessapplicationssummit/video/BAS2018-2071

Here’s the link to the What’s New coming in the Fall Release specific to the Integration with Dynamics 365 for Field Service – Inventory and Projects https://docs.microsoft.com/en-us/business-applications-release-notes/October18/dynamics365-finance-operations/integration-field-service-inventory-projects

 

 

As Manager of Armanino’s Enterprise Solution Consulting practice, Michelle is responsible for coordinating the presales activities across Armanino’s Microsoft engagements. Her background includes extensive experience across a wide range of business applications with emphasis on Enterprise Resource Planning (ERP), Customer Relationship Management (CRM) and supply chain advanced planning applications within the manufacturing and distribution industry. Prior to joining Armanino, Michelle worked at ERP companies such as SAP, PeopleSoft, JDEdwards and Symix (now called Syteline).

COMMENTS

comments powered by Disqus
« |