Assumptions for these Integrations to Work


Customer Integration

Below are the assumptions for customer integrations:

  • Customers with type “Customer” in the Project Service Automation application (PSA) are only considered for integrations.
  • Project Service Automation application (PSA) customers synchronize to all Microsoft Dynamics 365 Finance and Operations legal entities, if there is no contracting unit on the Project Service Automation application (PSA) customer.
  • Customer group is defaulted via a parameter set on the Projects+ parameter.
  • Terms of payment between two systems has to match in oder to integrate the customer records.
  • Addresses validations for integration:
    • Country code to match – If blank, taken from the company address in case the zipcode also does not have the country code.
    • State code to match – If does not match then the integration record errors out.
    • Zip code – does not have to match, will be populated even if it does not exist.

Project Contract Integration

Below are the assumptions for Project contract integrations.

  • Customer is always of the type customer.
  • Only contracts mapped (via Contracting unit > Legal entity) brought into Ops Legal entity.

Project Integration

Below are the assumptions for project integrations.

  • Customer vs Internal project.
    • Projects linked to a Contract in Project Service Automation application (PSA) are customer projects.
    • Projects not linked to a Contract are internal projects.
  • Operations projects will be created 1:1 with Project Service Automation application (PSA) Contract lines.
    • The Operations Project type is derived from the Project Service Automation application (PSA) Contract line type.
  • Project groups are defaulted via a parameter per project type.
  • Projects must be activated manually by a Project accountant in Operations.
    • Sales prices.
    • Budgets.
    • Invoice settings.
    • Dimensions.
    • Expense category validation.
    • Modify Project group.


Resource Integration

Below are the assumptions for resource integrations.

  • Resource type of user in Project Service Automation application (PSA) will only be integrated.
  • Calendar periods must be composed before running the resource integration.
  • If calendar is not specified in the projects+ parameters, then the imported resources will be integrated as worker.

Work Breakdown Structure (WBS) Integration

Below are the assumptions for Work Breakdown Structure (WBS) integrations.

  • Hour categories are manually synchronized between systems.
  • If Hour category is not specified on the Work Breakdown Structure (WBS), can use a Default category parameter.
  • Work Breakdown Structure (WBS) is automatically published.
  • Edits to Work Breakdown Structure (WBS) will only be done in Project Service Automation application (PSA).

Timesheet Integration

Below are the assumptions for timesheets integrations.

  • Resource is mapped between systems via email address.
    • Resources are manually added to both systems.
  • Only approved timesheets from Project Service Automation application (PSA) will be brought into Operations.
  • Category is looked up from Work Breakdown Structure (WBS) activity.
  • If a timesheet exists in Draft status, time will be added.
    • If a timesheet doesn’t exist, or is in a non-Draft status, will add a new timesheet.
  • Timesheets are manually mass-submitted to workflow (posting), so admins can control the posting process.
    • Allows us to do daily integration of time for reporting, but manage the weekly late timesheet process.
  • Time adjustments are done through a Project Service Automation application (PSA) timesheet or operation adjustment.

Other Assumptions

Some of the other assumptions are as follows:

  • Frequency of integrations.
    • Customer, Project, Contracts: ~5 min – 1 hr.
    • Work Breakdown Structure (WBS), Timesheets – ~Daily.
  • Default reporting position is to report from Microsoft Dynamics 365 finance and operations.
  • Project Service Automation application (PSA) GUIDs (Record identifiers) are always synced to Microsoft Dynamics 365 finance and operations for traceability and to support Workspace “deep-linking”.
  • Contracting units mapped to Legal entities.
    • Contracting units are unique to one Microsoft Dynamics 365 finance and operations enivronment.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment