Merge pull request #9696 from MicrosoftDocs/main

Auto Publish – main to live - 2025-09-11 10:00 UTC

Author: learn-build-service-prod[bot]

support/dynamics-365/supply-chain/procurement/source-document-lines-cannot-be-finalized.md

@@ -0,0 +1,41 @@
+---
+title: The Source Document Lines Cannot Be Finalized Until the Status Is Confirmed
+description: Provides a resolution for the Source document lines cannot be finalized error in Microsoft Dynamics 365.
+author: Sumit
+ms.date: 09/11/2025
+ms.search.form: PurchTable, PurchTablePart, PurchRFQTable
+audience: Application User
+ms.reviewer: kamaybac, shriramsiv
+ms.search.region: Global
+ms.author: sugaur
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.13
+ms.custom: sap:Purchase order procurement and sourcing\Issues with purchase order confirmation and packing slips
+---
+# "Source document lines cannot be finalized" error when confirming purchase order
+
+This article provides guidance to resolve an error that might occur when confirming a purchase order in Microsoft Dynamics 365.
+
+## Symptoms
+
+When you try to [confirm a purchase order](/dynamics365/supply-chain/procurement/purchase-order-approval-confirmation#confirming-purchase-orders), you might receive the following error message:
+
+> The source document lines cannot be finalized until the status is Confirmed.
+
+## Cause
+
+The issue occurs when the document accounting status in the related [purchase requisition](/dynamics365/supply-chain/procurement/purchase-requisitions-overview) isn't confirmed.
+
+## Resolution
+
+To resolve this issue, reset the purchase order accounting distributions by following these steps:
+
+1. Navigate to **Procurement and sourcing** > **Periodic tasks** > **Clean up** > **Purchase Order Distribution Reset**.
+2. Enter the **Purchase Order (PO) number** in the designated field.
+3. Select **OK** to proceed.
+4. The status of the purchase order updates to **Draft**.
+5. Submit the workflow and confirm the purchase order again.
+
+Triggering the purchase order distribution reset initiates a data check to ensure that the selected purchase order is in the correct state for the tool to run. After the reset, you should be able to finalize the source document lines.
+
+If you continue to experience issues after following these steps, verify that all required fields and configurations for the purchase order are complete. Additionally, ensure that any related workflows are properly configured and functioning as expected.

support/dynamics-365/supply-chain/toc.yml

@@ -158,6 +158,8 @@
       href: procurement/purchase-order-line-data-issues.md
     - name: Purchase orders don't reflect the language settings of the legal entity
       href: procurement/purchase-order-language-not-reflect-legal-entity-settings.md
+    - name: '"Source document lines cannot be finalized" error'
+      href: procurement/source-document-lines-cannot-be-finalized.md  
     - name: Transactions can be posted to a suspended ledger account
       href: procurement/canceled-receipts-posted.md
     - name: The delivery name isn't synced after changing a purchase order delivery address

support/power-platform/power-automate/desktop-flows/troubleshoot-errors-running-attended-or-unattended-desktop-flows.md

@@ -1,8 +1,8 @@
 ---
 title: Error code occurs when running an attended or unattended desktop flow
 description: Provides mitigation steps for the error codes that occur when running attended or unattended desktop flows.
-ms.reviewer: cefriant, kenseongtan, guco, johndund, alarnaud, ermathon
-ms.date: 07/14/2025
+ms.date: 09/11/2025
+ms.reviewer: cefriant, kenseongtan, guco, johndund, alarnaud, ermathon, iopanag
 ms.custom: sap:Desktop flows\Unattended flow runtime errors
 ---
 # Error code occurs when running an attended or unattended desktop flow
@@ -68,3 +68,4 @@ _Original KB number:_   4555406
 |LogonTypeNotGranted|400|Unattended|For more information, see [troubleshooting documentation for logon type not granted](logon-type-has-not-been-granted.md).|
 |UnallowedTenantForConnectWithSignIn|403|Attended|This error occurs when using a [connect with sign-in](/power-automate/desktop-flows/desktop-flow-connections#connect-with-sign-in-for-attended-runs) connection on an Active Directory (AD) domain-joined machine without adding your tenant to the allowlist. </br> For more information, see ["UnallowedTenantForConnectWithSignIn" error in a Power Automate desktop flow](troubleshoot-unallowed-tenant-for-connect-with-sign-in.md).|
 |MachineNotFound|404|Attended</br>Unattended|This error can occur when the machine is unregistered during a run or if the Dataverse organization has been migrated to a different region. Verify that:</br>- Your machine is still registered by [viewing its status](/power-automate/desktop-flows/manage-machines#view-list-of-machines) in the machine runtime application or the Power Automate portal.</br>- Your [desktop flow connection](/power-automate/desktop-flows/desktop-flow-connections) isn't broken in the Power Automate portal.</br>- [Scripting actions](/power-automate/desktop-flows/actions-reference/scripting) in your flow don't register your machine while the flow is running.|
+|NoSessionFoundForPasswordless|400|Attended|An opened session on the machine is required to run the desktop flow in attended mode. You can also use unattended mode instead of using a [Power Automate Process license](/power-platform/admin/power-automate-licensing/deep-dive-on-specific-license#power-automate-process-license).|