Sales and marketingInquiries and reportsOrder posting
SalesPostingHistorylConfirmation
Used by
Credit management clerk, Credit management manager, Project assistant and 8 more roles
Business process
Enter sales orders
Menu item
SalesPostingHistorylConfirmation
Main table
SalesParmTable
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 is
An inquiry page that shows the update history of sales order confirmation posting: each sales order confirmation update job with its job status, date of creation and creator, the sales orders it covered and the quantities updated on each line.
What you do here
Use it to check whether a sales order confirmation update for an order was executed, ended in error or is still waiting, and to read the error text of a failed job. Every confirmation, picking list, packing slip and invoice update creates such history.
Example
For example, a BEAT clerk confirmed 25 orders in one batch run on 06.11.2026, but customer BEAT-000123 says no confirmation arrived for SO-001240. With Job status set to All, the job for SO-001240 shows an error; Error text gives the reason and the clerk confirms the order again.
The page in Dynamics 365. page title tab to open what to set or check
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 sales order confirmation jobs
Find out whether a confirmation was posted for an order and why a job failed.
Steps from Microsoft
Go to Sales and marketing > Inquiries and reports > Order posting > Sales order confirmation.
In Job status, choose the status you are looking for; choose All when you search for one order.
Find the job for the Sales order, read Date of creation and Created by, and check the Lines tab for the quantity in Update on each line.
For a job in error, select Error text, fix the cause on the order and post the sales order confirmation again; old executed and erroneous jobs are removed by Sales update history cleanup.
Whether the update was executed, ended in error or is still waiting.Microsoft Learn
Sales order
The sales order the update job covered.Checked in Dynamics 365
SO-001234
Date of creation
When the update job was created.Checked in Dynamics 365
Created by
The user who started the update.Checked in Dynamics 365
Update
On the Lines tab: the quantity the job updated on each order line.Checked in Dynamics 365
Common errors and fixes
Message
What to do
Posting of sales order confirmations gets slower over time.
Large amounts of old sales update history can cause performance and functional issues when confirmations, picking lists, packing slips and invoices are posted. Schedule Sales update history cleanup to run at least every three to six months. Microsoft Learn
Test checklist
Post a sales order confirmation for a test sales order.
Open Order posting > Sales order confirmation and set Job status to All.
Filter on the order number.
Check that one job is listed with your user and today's date, and that the Lines tab shows the updated quantity.
Set Job status to All and filter on the sales order number.The page opens with a status filter; a job that is executed or in error is hidden if the filter shows another status.
On the live system, Rental manager, Rental coordinator agent, Rental sales manager, Sales clerk and Retail service use this page; 11 roles can open it in total. No Feature management feature is needed to open it.
Checked in Dynamics 365
Solution architect
5Design impact
Shared or per company
Per company: each legal entity keeps its own sales update history. Microsoft data model
Can it be undone
Reversible: Running the inquiry or report changes no data.
If you change it later
Sales update history cleanup deletes executed, executed and erroneous, or all records older than a maximum age or a created-until date, so jobs disappear from this page after it runs. Waiting records are valid but not fully processed; keep them unless you are sure. Microsoft Learn
Technical architect
6Technical
Menu item
SalesPostingHistorylConfirmationChecked in Dynamics 365
Form
SalesPostingHistoryChecked in Dynamics 365
Table
SalesParmTableShown as “Sales order - update table” in Record infoKey field: SalesIdChecked in Dynamics 365
Who can open it
PrivilegesProcess sales order confirmation SalesFormLetter_ConfirmationProcessDutiesThis duty only include privileges that are accessible by the project manager and it does not contain the privileges related to sales order and purchase order ProjProjectItemTasksMaintainMaintain rental sales orders RentalSalesOrderMaintainMaintain sales order SalesOrderMaintain12 security rolesCredit management clerk CredManClerkCredit management manager CredManManagerMCRTestUserRoleProject assistant ProjProjectClerkProject manager ProjProjectManagerRental coordinator agent RentalCoordinatorAgentRental manager RentalManagerRental purchasing manager RentalPurchasingManagerRental sales manager RentalSalesManagerRetail service RetailServiceRevenue recognition manager RevRecManagerSales clerk TradeSalesClerkChecked in Dynamics 365
Roles to set it up and use it
To set it up or change itRental manager RentalManagerRental coordinator agent RentalCoordinatorAgentRental sales manager RentalSalesManagerSales clerk TradeSalesClerkRetail service RetailServiceGive people one of these roles. On this system, 11 roles can open this page.Checked in Dynamics 365
Actions on the page
Options: Personalize, Page options, ShareChecked in Dynamics 365
Load order: Sales order confirmation (order posting history) has no data entity in Data management. No standard entity is backed by its table (SalesParmTable). The history is created by posting in the new system, so there is nothing to migrate.Load first: Posted sales documentsChecked in Dynamics 365