BeyondERP.Newsletter
Menu

Setup step on the Purchase order vendor confirmation history page · Vendor collaboration

Check the confirmation history of a purchase order

Compare the versions of a purchase order and the vendor's answers to each.

Used by
Vendor contact (external)
Business process
Manage open purchases
Menu item
PurchVendorPortalVersionHistory
Main table
PurchaseOrderResponseHea
Data entity
None for this page's own settings
Setup steps
1 on this page
Show what matters for
SETUP GUIDEHow to set it up8 sections. Choose a role to highlight what matters to you.
Everyone

1What it is and why

What it isA list page of every purchase order and purchase order version sent to the vendor, together with the vendor's responses.
What you do hereUse this page to track the history of each purchase order, including all versions sent and all responses returned.
ExampleFor example, BEAT sends BEAT-000061 version 1, the vendor accepts it with a later receipt date, and BEAT sends version 2. The vendor opens the history, selects version 1 and View response to see what it suggested, then View sent order to compare it with version 2.
Purchase order vendor confirmation history page in Dynamics 365
The page in Dynamics 365. page title tab to open what to set or check
Functional consultant · Solution architect

2Where it fits

End user · Functional consultant

3How to do it

About the examples: Examples and screenshots in this guide use BEAT, a demo company in a Dynamics 365 test environment. Use your own company's codes and values instead of copying them.

Setup steps on this page

Check the confirmation history of a purchase order

Compare the versions of a purchase order and the vendor's answers to each.

Steps from Microsoft

  1. Go to Vendor collaboration > Purchase orders > Purchase order vendor confirmation history.
  2. Filter on the purchase order number to list every version sent.
  3. Select a version and View sent order to see what the customer sent.
  4. Select View response to see what was answered, by whom and when.

Source: Microsoft Learn

Fields on the page

FieldWhat it meansExample
Purchase orderThe purchase order number; each version sent is listed.Checked in Dynamics 365BEAT-000061
Vendor accountThe customer's vendor account the order was sent to.Checked in Dynamics 365BEAT-000001
ConfirmedShows whether the version is confirmed.Checked in Dynamics 365
Purchase journalThe purchase order journal of the version that was sent.Checked in Dynamics 365
Date time received / Date time answeredWhen the vendor received the version and when it answered.Checked in Dynamics 365
Responding personThe vendor contact who sent the response.Checked in Dynamics 365
View sent order / View responseActions that open the version sent to the vendor and the vendor's response to it.Checked in Dynamics 365

Common errors and fixes

MessageWhat to do
An order is listed as confirmed with no responseThe customer confirmed it without a vendor response (for example after an email). The vendor can no longer confirm or reject it. Microsoft Learn

Test checklist

  1. Send a purchase order for confirmation and have the vendor accept it with changes.
  2. Send a new version of the order.
  3. Open the confirmation history and check that both versions are listed with their received and answered times.
  4. Open View response on version 1 and check the suggested changes.

Source: Microsoft Learn

Functional consultant

4Setup decisions

Setup stepRecommended value and whyDecision, common mistake and test
Check the confirmation history of a purchase orderFilter on one purchase order, then compare View sent order and View response per versionEach version and each response is a separate line, so without a filter the history of several orders is mixed.Do you use change management for purchase orders?Reading the latest line as the current order: the version available to the customer's other processes is always the latest one, even if it hasn't been registered for the vendor yet.Test: Two versions in the history

Feature management and licence

Licence or add-inMicrosoft provides two external roles for vendor collaboration: Vendor admin (external), for contacts and user requests, and Vendor (external), for purchase orders, invoices, consignment inventory, RFQs and vendor information. External users created through a user request also get the SystemExternalUser role. On the live system, Vendor contact (external) can open this page.

Microsoft Learn

Solution architect

5Design impact

Shared or per companyThe history covers every version of each purchase order sent to the vendor account, from every customer legal entity where the contact has access. Microsoft Learn
Can it be undoneReversible: The page changes no data.
If you change it laterIf the customer confirms an order without a vendor response, the order shows in the history as confirmed with no responses and the vendor can no longer confirm or reject it. Microsoft Learn
Technical architect

6Technical

Menu itemPurchVendorPortalVersionHistory Checked in Dynamics 365
FormPurchVendorPortalResponsesHistoryList Checked in Dynamics 365
TablePurchaseOrderResponseHeaShown as “PURCHASE ORDER RESPONSE HEADER SUMMARY” in Record infoChecked in Dynamics 365
Data entitiesPurchaseOrderResponseHeaderEntityPurchase order response headers (the vendor's responses; the versions sent come from the customer's purchase order journals) Microsoft data model
Who can open itPrivilegesView vendor purchase orders VendVendorPurchOrderJournalViewDutiesMaintain process purchase orders VendVendorPurchOrderMaintain
1 security roleVendor contact (external) VendVendorContact
Checked in Dynamics 365
Roles to set it up and use itTo use itVendor contact (external) VendVendorContactGive people one of these roles. On this system, 1 role can open this page.Checked in Dynamics 365
Actions on the page(Action Pane without tabs): View received order, View sent order, View response, View responseChecked in Dynamics 365
Developer

7Developer

Open it by URLhttps://<your-environment>/?mi=PurchVendorPortalVersionHistory
Data migrationPurchaseOrderResponseHeaderEntity (Purchase order response headers): loaded for each company.Load order: The history builds up as orders are sent and answered; it is not usually migrated. Keep the old system's history for reference.Load first: purchase ordersChecked in Dynamics 365
Everyone

8Sources