Become a Dynamics 365 expert with Syvantis Learn
Provide additional details about the offer you're running.
This store requires javascript to be enabled for some features to work correctly.
There are some key differences to be aware of in the Purchase Order statuses and controls between Dynamics GP and Dynamics 365 for Operations.
Dynamics GP has one status for POs (there are 2 if Workflows are enabled, but this topic will not be discussed in this blog).
A PO in Received, Canceled, or Closed status can no longer be opened, since it can no longer be edited. They can only be found in Inquiry windows.
In Dynamics 365 for Operations there are 2 separate statuses for POs (workflow statuses are included in Approval status, but are not available if workflows are not enabled).
Security controls between Dynamics GP and Dynamics 365 for Operations are very similar. If a user has the appropriate security rights they can make changes to the PO. Likewise, users with appropriate security rights can receive and/or invoice the POs.
Note that security configuration, however, is different between the two systems. Dynamics GP takes an “add-on” approach: security starts with no permissions and you choose the tasks and roles to add. Dynamics 365 for Operations, on the other hand, allows you to also designate which tasks are not permitted to a role. When roles overlap, any restrictions inherited from one of the roles will apply and will not be overridden by any roles that grant that same task.
If workflows are enabled, POs cannot be received or invoiced, or changes cannot be saved, unless the appropriate users authorize the changes. Workflows will be covered more in-depth in a future blog.
In Dynamics GP you can easily view the number of times a PO has been changed and printed by referring to the version number, but you don’t have the ability to view the previous versions.
You can create a SmartList that shows the user who created a document, but this field isn’t available for all transaction types. Sometimes you can only see the last user to edit a document. Unfortunately, these lists aren’t pre-built.
If you are looking for more detailed audit trails, they are available, but limited and difficult to obtain. There is an audit report that will show which users edited documents and when the edits were made. However, the list will generate all changes made in GP for a designated period of time. This makes it quite difficult to locate the desired information, and even in companies with a smaller transaction volumes you will more than likely need to search through copious amounts of data to find the record you are looking for. The report also does not provide the document number but displays the record number, which is only found in the tables. Because of this, you will need to cross-reference these numbers to identify the document.
Audit trails in Dynamics 365 for Operations are much more user-friendly and obtainable. There are two different ways to inquire on transaction changes: viewing the transaction versions, or running audit trail reports.
You can view transaction versions for confirmation journals, receipt cancellations, receipt corrections, pro-forma invoices, etc. The list will show all versions and you can click on the version number to view the full document. There is also a feature that lets you compare the differences between the versions.
The audit reports are easily accessible, as they can be found in Inquiries and Reports, or oftentimes in the action pane of the transaction. The report displays the type of transaction, a description, who created the transaction, and when it was created. You can also click into any of these to drill down and view the transactions.
Overall, the same functionality is available in Dynamics GP and Dynamics 365 for Operations to allow companies to restrict and monitor their purchasing processes. Dynamics 365 for Operations is more user-friendly and provides more detail in the out-of-box version.