some suggestions

Author: lucciz01

support/dynamics-365/supply-chain/procurement/purchase-requisitions-cannot-released.md

@@ -1,43 +1,53 @@
 ---
-title: Purchase requisitions cannot be released
-description: Purchase requisitions created before the current fiscal year cannot be released.
-author: Shubham
+title: Purchase Requisitions Can't Be Released
+description: Purchase requisitions created before the current fiscal year can't be released in Microsoft Dynamics 365 Finance and Dynamics 365 Supply Chain Management.
+author: Shubhs93
+ms.author: shubhamshr
 ms.reviewer: shubhamshr
 ms.search.form: PurchTable, PurchTablePart, PurchRFQTable
 audience: Application User
 ms.search.region: Global
 ms.custom: sap:Purchase order procurement and sourcing\Issues with purchase orders
-ms.date: 02/25/2025
+ms.date: 03/06/2025
 ---
-# Purchase requisitions created before the current fiscal year cannot be released
+# Purchase requisitions created before the current fiscal year can't be released
+
+This article provides workarounds for an issue where the purchase requisitions created before the current fiscal year can't be released in Dynamics 365 Finance and Dynamics 365 Supply Chain Management.
 
 ## Symptoms
-In Dynamics 365 Finance & Supply Chain Management (D365 F&SCM), Purchase Requisitions (PRs) that are submitted at the end of one fiscal year and approved in the new fiscal year encounter an issue when converting them into Purchase Orders (POs). The system throws the following error:
 
-"Purchase requisition line was pre-encumbered in a fiscal year that is different from the accounting date of the purchase order. Hence, purchase order cannot be created."
+When you try to convert a purchase requisition (PR) submitted at the end of one fiscal year and approved in the new fiscal year into a purchase order (PO) in Dynamics 365 Finance and Dynamics 365 Supply Chain Management, you might receive the following error message:
+
+> Purchase requisition line was pre-encumbered in a fiscal year that is different from the accounting date of the purchase order. Hence, purchase order cannot be created.
+
+## Cause 1 - Pre-encumbrance issue
 
-## Cause
-1. Pre-Encumbrance Issue
-When a purchase requisition is approved, it creates a pre-encumbrance in the system to reserve budget funds.
-If the requisition was submitted in the previous fiscal year, the pre-encumbrance is tied to that year’s budget.
-However, when attempting to convert the PR into a PO in the new fiscal year, the system detects a mismatch because the pre-encumbrance belongs to the old fiscal year, but the purchase order is being created in the new fiscal year.
+When a purchase requisition is [approved](/dynamics365/supply-chain/procurement/purchase-requisitions-overview#purchase-requisition-header-and-line-status-relationships), it creates [a pre-encumbrance to reserve budget funds](/dynamics365/supply-chain/procurement/purchase-requisitions-overview#consolidating-purchase-requisition-lines). If the requisition was submitted in the previous fiscal year, the pre-encumbrance is tied to that year's budget. The system detects a mismatch when converting the PR into a PO in the new fiscal year because the pre-encumbrance belongs to the old fiscal year, but the purchase order is being created in the new fiscal year.
 
-2. No PR Rollover Functionality
-D365 does not support purchase requisition rollovers across fiscal years.
-If a PR remains open at year-end, it cannot be carried over automatically into the new fiscal year.
-This restriction ensures that budgets and financial commitments remain aligned with fiscal year policies.
+## Cause 2 - No PR rollover functionality
+
+Dynamics 365 doesn't support purchase requisition rollovers across fiscal years. If a PR remains open at year-end, it can't be carried over automatically into the new fiscal year. This restriction ensures that budgets and financial commitments remain aligned with fiscal year policies.
 
 ## Workaround
-1. Cancel Open Requisitions at Year-End
-Before the fiscal year-end closing, identify all open purchase requisitions.
-Cancel any unapproved or pending PRs that have not yet been converted into purchase orders.
-Create new purchase requisitions in the new fiscal year, ensuring they align with the correct budget year.
-This avoids the issue altogether by ensuring that new requisitions are processed within the correct fiscal period.
 
-2. Convert PRs to POs Before Fiscal Year-End & Roll Over POs
-Instead of leaving PRs open, convert them into purchase orders before the fiscal year closes.
-If the PO needs to be received or invoiced in the new fiscal year, leverage the rollover functionality for purchase orders.
-This ensures that financial commitments are properly managed across fiscal years.
+The best practice is to either cancel open PRs at year-end or convert them into POs before the fiscal year closes. This ensures smooth procurement processing without encountering fiscal year mismatches. Since Dynamics 365 doesn't support PR rollovers, organizations should proactively manage requisitions as part of their year-end closing procedures.
+
+- Cancel open PRs at year-end
+
+   1. Identify all open PRs before the fiscal year-end closing.
+   1. Cancel any unapproved or pending PRs that haven't yet been converted into POs.
+   1. Create new purchase requisitions in the new fiscal year, ensuring they align with the correct budget year.
+
+  This avoids the issue by ensuring that new requisitions are processed within the correct fiscal period.
+
+- Convert PRs into POs before fiscal year-end and roll over POs
+
+   1. Convert open PRs into POs before the fiscal year closes.
+   1. If the PO needs to be received or invoiced in the new fiscal year, use the rollover functionality for POs.
+
+   This ensures that financial commitments are properly managed across fiscal years.
 
-The best practice is to either cancel open PRs at year-end or convert them into POs before the fiscal year closes. This ensures smooth procurement processing without encountering fiscal year mismatches. Since D365 does not support PR rollovers, organizations should proactively manage requisitions as part of their year-end closing procedures.
+## More information
 
+- [Select purchase orders and run the purchase order year-end process](/previous-versions/dynamicsax-2012/appuser-itpro/process-purchase-orders-at-year-end#select-purchase-orders-and-run-the-purchase-order-year-end-process)
+- [Purchase order year-end close](/dynamics365/finance/budgeting/purchase-order-year-end-process)

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

@@ -144,6 +144,8 @@
       href: procurement/object-reference-not-set.md
     - name: Imported purchase orders show incorrect line numbers
       href: procurement/line-number-increments.md
+    - name: Purchase requisitions created before the current fiscal year can't be released
+      href: procurement/purchase-requisitions-cannot-released.md
     - name: Purchase order line data discrepancies
       href: procurement/purchase-order-line-data-issues.md
     - name: Purchase orders don't reflect the language settings of the legal entity