Merge pull request #9178 from MicrosoftDocs/main

Deland-Han · web-flow · commit 0693266f1a0d · 2025-06-24T10:34:29.000+08:00
Auto push to live 2025-06-24 02:34:22
diff --git a/support/dynamics-365/supply-chain/procurement/po-workflow-accounting-distribution.md b/support/dynamics-365/supply-chain/procurement/po-workflow-accounting-distribution.md
@@ -0,0 +1,54 @@
+---
+title: Accounting Distribution Validation Failed Error
+description: Solves an issue where you can't submit a purchase order for approval after it's updated.
+ms.reviewer: shubhamshr, ashuaggarwal
+ms.date: 06/24/2025
+ms.custom: sap:Purchase order procurement and sourcing\Issues with purchase orders
+---
+# Workflow approval fails with the "Accounting distribution validation failed" error
+
+This article addresses an issue where the workflow approval process for a purchase order fails due to unvalidated [accounting distributions](/dynamics365/finance/accounts-payable/accounting-distributions). The error occurs when the purchase order is modified and resubmitted without validating the accounting distributions, causing the workflow process to stop.
+
+## Symptoms
+
+After [setting a purchase order back to "Draft"](/dynamics365/supply-chain/procurement/purchase-order-approval-confirmation#changing-purchase-orders) and modifying the line items (for example, changing the unit price or the confirmed receipt date), when you submit the purchase order for approval, the workflow approval process fails with the following error:
+
+> Stopped (error): Accounting distribution validation failed. Please recall purchase order workflow and rectify accounting distributions. This action can only be completed after the line number 1 is fully distributed.
+
+### Steps to reproduce
+
+1. Create and approve a purchase order for a vendor with change management enabled.
+2. Confirm the purchase order.
+3. Request a change to revert the purchase order to "Draft" status.
+4. Modify the line items, for example, changing the unit price or the confirmed receipt date.
+5. Resubmit the purchase order for workflow approval without first saving the line items.
+6. Observe that the workflow approval fails with the error.
+
+## Cause
+
+When the **Auto calculate totals and accounting distributions** feature is enabled, the system automatically recalculates the purchase order totals and accounting distributions when a purchase order is submitted to the workflow. This recalculation is part of the workflow validation process, and any validation errors are displayed in the workflow history. For more information about the feature, see [Procurement and sourcing feature updates](/dynamics365/release-plan/2023wave2/finance-supply-chain/dynamics365-supply-chain-management/procurement-sourcing-feature-state-updates-10036#features-becoming-generally-available-with-the-10036-release).
+
+If accounting distribution errors occur, such as missing financial dimensions or invalid combinations, the system generates a warning or error and prevents the workflow submission until the issue is resolved.
+
+## Workaround
+
+To avoid workflow failures due to unvalidated accounting distributions, you can disable the auto calculation feature. This action ensures that errors in accounting distributions are identified and resolved before the workflow submission.
+
+1. Navigate to **Accounts Payable** > **Setup** > **Parameters**.
+2. Select the **General** tab.
+3. Locate the **Purchase Order Workflow** section.
+4. Disable the **Auto calculate totals and accounting distributions** parameter.
+5. Save your changes.
+
+By disabling this parameter, the system prevents you from submitting a purchase order to the workflow if there are accounting distribution errors. Instead, it displays a warning, requiring you to fix the distribution errors first. Once the errors are resolved, you can submit the purchase order to the workflow, and it will proceed without issues.
+
+## Additional considerations
+
+If disabling the **Auto calculate totals and accounting distributions** parameter is unacceptable to your organization, ensure that all accounting distribution errors are resolved before submitting the purchase order to the workflow.
+
+- Ensure that all required financial dimensions are correctly assigned to the accounting distributions.
+- After modifying the purchase order line items, make sure to manually save the changes.
+
+## More information
+
+[Approve and confirm purchase orders](/dynamics365/supply-chain/procurement/purchase-order-approval-confirmation)
diff --git a/support/dynamics-365/supply-chain/procurement/unable-to-cancel-po.md b/support/dynamics-365/supply-chain/procurement/unable-to-cancel-po.md
@@ -0,0 +1,58 @@
+---
+title: Unable to Cancel a Budget-Enabled Purchase Order in a Closed Period
+description: Describes a workaround for canceling or modifying a budget-controlled purchase order when the accounting period is closed in Microsoft Dynamics 365 Supply Chain Management.
+ms.reviewer: shubhamshr, ashuaggarwal
+ms.date: 06/24/2025
+ms.custom: sap:Purchase order procurement and sourcing\Issues with purchase orders
+---
+# Can't cancel a purchase order governed by budget within a closed period
+
+This article explains how to resolve issues when attempting to cancel or modify a purchase order (PO) [governed by budget](/dynamics365/supply-chain/procurement/tasks/create-purchase-order-governed-by-budget#perform-budget-checking) in Microsoft Dynamics 365 Supply Chain Management, specifically when the associated accounting period is closed or on hold.
+
+## Symptoms
+
+When you try to cancel or change a PO, you might receive one of the following error messages:
+
+- > Budget control is enabled. This purchase order cannot be cancelled as the accounting date period is either on-hold or closed. You can use the purchase order year-end close process to move the purchase order to the next fiscal year or open the ledger calendar associated with the accounting date.
+- > A change cannot be made to this purchase order as the accounting period is on hold or closed. You can use the purchase order year-end close process to update the order to the next fiscal year.
+
+## Cause
+
+This behavior is by design. The ability to cancel or modify a PO depends on the budget check status and the accounting period's status.
+
+For example, consider a fiscal year that runs from April 2023 to March 2024.
+  
+### Scenarios where you can cancel an open PO
+
+- A budget check isn't performed or failed.
+
+  If the PO hasn't undergone a budget check, or if the budget check has failed, you can cancel the PO.
+
+- A budget check is passed, and the closed period isn't the last period of the fiscal year.
+
+  If the PO has passed the budget check and the accounting date falls within a closed period that isn't the last period of the fiscal year, the system will use the next open or available period within the same fiscal year.
+
+  Example: If the accounting date of the PO is in December 2023, and the December 2023 period is closed while January, February, and March 2024 are open, you can still cancel the PO without reopening the December 2023 period.
+
+### Scenarios where you can't cancel an open PO
+
+- A budget check is passed and the accounting date falls in the last period of the fiscal year.
+
+  If the PO has passed the budget check and the accounting date is in the last period of the fiscal year (for example, March 2024) and that period is closed, you can't cancel the PO unless you reopen the closed period.
+
+## Workaround
+
+To cancel a PO in a closed period, you must reopen the closed or on-hold period. For example, if the blocking error message indicates that the March 2024 period is closed, follow these steps to reopen that period and then cancel the PO:
+
+1. Navigate to **General ledger** > **Ledger setup** > **Ledger calendars**.
+1. Find the ledger calendar for the fiscal year and accounting period of the PO.
+1. Change the status of the closed or on-hold period (for example, March 2024) to **Open**.
+1. Cancel the PO.
+1. After cancellation, return to the ledger calendar and set the period back to its original status (for example, closed or on hold).
+
+> [!NOTE]
+> We recommend that you perform this operation outside business hours to minimize the risk of other users creating records during the reopening period.
+
+## More information
+
+[Fiscal calendars, fiscal years, and periods](/dynamics365/finance/budgeting/fiscal-calendars-fiscal-years-periods)
diff --git a/support/dynamics-365/supply-chain/toc.yml b/support/dynamics-365/supply-chain/toc.yml
@@ -132,6 +132,8 @@
       href: procurement/vendor-rebate-not-cumulated.md
     - name: A product receipt voucher number is consumed even when not generating a voucher
       href: procurement/voucher-number-consumed.md
+    - name: Can't cancel a purchase order within a closed period
+      href: procurement/unable-to-cancel-po.md  
     - name: Can't delete a purchase order line after it's confirmed
       href: procurement/purchase-order-line-deletion-restriction.md  
     - name: Can't add a line to a purchase requisition after requesting a change
@@ -164,6 +166,8 @@
       href: procurement/post-setting-turned-off.md
     - name: Unit prices on purchase orders aren't calculated based on the unit conversion
       href: procurement/po-unit-prices-not-calculated.md
+    - name: Workflow approval fails with "Accounting distribution validation failed"
+      href: procurement/po-workflow-accounting-distribution.md
     - name: You can only complete a purchase order action for fully distributed line numbers
       href: procurement/action-requires-full-distribution.md
     - name: You can't add the Price unit field to the Purchase agreement page
diff --git a/support/power-platform/power-apps/manage-apps/wrap-issues.md b/support/power-platform/power-apps/manage-apps/wrap-issues.md
@@ -4,7 +4,7 @@ description: Provides solutions to common issues when using the wrap feature in
 ms.reviewer: sitaramp, koagarwa
 ms.author: arijitba
 author: arijitba
-ms.date: 06/17/2025
+ms.date: 06/24/2025
 ms.custom: has-azure-ad-ps-ref, azure-ad-ref-level-one-done, sap:App Management\Wrap an app
 ---
 # Troubleshoot wrap feature issues in Power Apps
@@ -87,17 +87,18 @@ If you can't sign in or see data in your wrapped app, try the following actions:
 
 You might encounter these error codes in the wrap wizard:
 
-| Error Code | Error Message |
+| Error code | Error message |
 |------------|-------------|
 | [1000118](#error-code-1000118) | Default subscription not found or missing access permissions. |
-| [1000119](#error-code-1000119) | Key vault doesn't exist or is missing access privileges. |
-| [1000120](#error-code-1000120) | No organization ID tags found on key vault. |
-| [1000121](#error-code-1000121) | Android keystore isn't valid. Missing tag and/or certificate. |
-| [1000122](#error-code-1000122) | iOS certificate isn't valid. |
-| [1000123](#error-code-1000123) | iOS profile isn't valid. |
-| [1000128](#error-code-1000128) | Missing access key used while accessing Azure Blob storage location. |
-| [1000130](#error-code-1000130) | Missing default value: The required environment variable for setting up Azure Key Vault in the wrap wizard isn't set. |
-| [1000131](#error-code-1000131) | Missing tags for the specified Azure Key Vault resourceID. |
+| [1000119](#error-code-1000119) | Key vault doesn't exist or is missing access privileges.|
+| [1000120](#error-code-1000120) | No organization ID tags found on key vault. Ensure that the tag {Bundle ID}.{organization-id} is present and uses the correct case sensitivity.|
+| [1000121](#error-code-1000121) | Android keystore isn't valid. Ensure that the tag {Bundle ID}.{keystore} is present and uses the correct case sensitivity.|
+| [1000122](#error-code-1000122) | iOS certificate isn't valid. Missing Tag and/or Secret. Ensure that the tag {Bundle ID}.{cert} is present and uses the correct case sensitivity.|
+| [1000123](#error-code-1000123) | iOS profile isn't valid. Ensure that the tag {Bundle ID}.{profile} is present and uses the correct case sensitivity.|
+| [1000128](#error-code-1000128) | Missing access key required to access the Azure Blob Storage location. Ensure that the tag {Bundle ID}.{accessKey} is present and uses the correct case sensitivity.|
+| [1000130](#error-code-1000130) | Missing default value: The required environment variable for setting up Azure Key Vault in the wrap wizard isn't set.|
+| [1000131](#error-code-1000131) | No tags or missing access permission for the specified Azure Key Vault. |
+| [1000132](#error-code-1000132) | Missing environment variable 'PA_Wrap_KV_ResourceID' for the targeted environment. |
 
 ### Error code 1000118
 
@@ -161,7 +162,7 @@ Error message: Key vault doesn't exist, or Key vault is missing access privilege
 
 ### Error code 1000120
 
-Error message: No organization ID tags found on key vault.
+Error message: No organization ID tags found on key vault. Ensure that the tag {Bundle ID}.{organization-id} is present and uses the correct case sensitivity.
 
 #### Resolution steps
 
@@ -179,7 +180,7 @@ Error message: No organization ID tags found on key vault.
 
 ### Error code 1000121
 
-Error message: Android keystore isn't valid. Missing Tag and/or Certificate.
+Error message: Android keystore isn't valid. Ensure that the tag {Bundle ID}.{keystore} is present and uses the correct case sensitivity.
 
 #### Resolution steps
 
@@ -198,7 +199,7 @@ Error message: Android keystore isn't valid. Missing Tag and/or Certificate.
 
 ### Error code 1000122
 
-Error message: iOS certificate isn't valid.
+Error message: iOS certificate isn't valid. Missing Tag and/or Secret. Ensure that the tag {Bundle ID}.{cert} is present and uses the correct case sensitivity.
 
 #### Resolution steps
 
@@ -217,7 +218,7 @@ Error message: iOS certificate isn't valid.
 
 ### Error code 1000123
 
-Error message: iOS profile isn't valid.
+Error message: iOS profile isn't valid. Ensure that the tag {Bundle ID}.{profile} is present and uses the correct case sensitivity.
 
 #### Resolution steps
 
@@ -232,7 +233,7 @@ Error message: iOS profile isn't valid.
 
 ### Error code 1000128
 
-Error message: Missing access key used while accessing Azure Blob storage location.
+Error message: Missing access key required to access the Azure Blob Storage location. Ensure that the tag {Bundle ID}.{accessKey} is present and uses the correct case sensitivity.
 
 #### Resolution steps
 
@@ -246,19 +247,61 @@ Error message: Missing default value: The required environment variable for sett
 
 #### Resolution steps
 
-- Add the resource ID for the Azure key vaults you intend to use with your wrap application.
-- Ensure that all required tags are present for the resource ID linked to the Bundle ID specified in the wrap wizard.
+1. Assign the resource ID of the Azure key vault you intend to use with your wrap application to the variable.
+
+2. Confirm that the specified resource ID includes all required tags associated with the Bundle ID defined in the wrap wizard.
 
 For more information, see [Step 2: Target platform](/power-apps/maker/common/wrap/wrap-how-to#step-2-target-platform).
 
 ### Error code 1000131
 
-Error message: Missing tags for the specified Azure Key Vault resourceID.
+Error message: No tags or missing access permission for the specified Azure Key Vault.
 
 #### Resolution steps
 
-- After setting up Azure key vaults, add all required tags.
-- Confirm that the resource ID associated with the Bundle ID specified in the wrap wizard includes every necessary tag.
+1. Assign the resource ID of the Azure key vault you intend to use with your wrap application to the variable.
+
+2. Confirm that the specified resource ID includes all required tags associated with the Bundle ID defined in the wrap wizard.
+
+3. Ensure you have permission to access your key vault:
+
+   1. As a Microsoft Entra ID (formerly Azure AD) admin, add the service principal for the AppID "4e1f8dc5-5a42-45ce-a096-700fa485ba20" by running the following commands in PowerShell:
+
+      ```powershell
+      Connect-AzureAD -TenantId <your tenant ID>
+      New-AzureADServicePrincipal -AppId 4e1f8dc5-5a42-45ce-a096-700fa485ba20 -DisplayName "Wrap KeyVault Access App"
+      ```
+
+   1. In the [Azure portal](https://portal.azure.com), under **Access Control (IAM)**, assign the **Reader** role to your service principal:
+
+      1. Go to **Access control (IAM)**, and then select **Add role assignment**.
+
+         :::image type="content" source="media/wrap-issues/add-role-assignment.png" alt-text="Screenshot that shows the Add role assignment option in the Access control (IAM) tab." lightbox="media/wrap-issues/add-role-assignment.png":::
+
+      1. Choose **Reader** under **Job function roles** and go to the **Members** tab.
+
+         :::image type="content" source="media/wrap-issues/add-members.png" alt-text="Screenshot that shows the Members tab on the top menu." lightbox="media/wrap-issues/add-members.png":::
+
+      1. Search for your app name.
+
+         :::image type="content" source="media/wrap-issues/select-members-to-add-role.png" alt-text="Screenshot that shows how to search for your app." lightbox="media/wrap-issues/select-members-to-add-role.png":::
+
+      1. Assign the **Reader** role.
+
+         :::image type="content" source="media/wrap-issues/assign-reader-role-to-wrap-keyvault-access-app.png" alt-text="Screenshot that shows how to assign a Reader role to your app." lightbox="media/wrap-issues/assign-reader-role-to-wrap-keyvault-access-app.png":::
+
+For more information, see [Step 2: Target platform](/power-apps/maker/common/wrap/wrap-how-to#step-2-target-platform).
+
+---
+### Error code 1000132
+
+Error message: Missing environment variable 'PA_Wrap_KV_ResourceID' for the targeted environment.
+
+#### Resolution steps
+
+1. Check whether the environment variable `PA_Wrap_KV_ResourceID` exists in the target environment. If it doesn't, create it.
+
+2. Ensure the name follows the correct naming convention without typos or formatting errors.
 
 For more information, see [Step 2: Target platform](/power-apps/maker/common/wrap/wrap-how-to#step-2-target-platform).
 
