diff --git a/support/dynamics-365/supply-chain/costing/another-closing-or-adjustment-has-not-finished.md b/support/dynamics-365/supply-chain/costing/another-closing-or-adjustment-has-not-finished.md
new file mode 100644
index 00000000000..b02ef0f0686
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/another-closing-or-adjustment-has-not-finished.md
@@ -0,0 +1,25 @@
+---
+title: Another closing or adjustment has not finished yet
+description: Error during inventory closing or recalculation -- Another closing or adjustment has not finished yet
+author: Soumyamoy Das
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\Another closing or adjustment has not finished yet
+---
+
+# Another closing or adjustment has not finished yet
+
+## Symptoms
+
+Inventory closing or recalculation errors out with "Another closing or adjustment has not finished yet" and a new closing or recalculation voucher is not created in the Closing and Adjustment form.
+
+## Resolution
+
+This justifies that some other closing or recalculation voucher execution might be in progress when you are trying to execute another closing or recalculation. Please wait for the previous closing voucher to complete execution and post that, you can execute another fresh closing or recalculation. 
diff --git a/support/dynamics-365/supply-chain/costing/batch-error-generic.md b/support/dynamics-365/supply-chain/costing/batch-error-generic.md
new file mode 100644
index 00000000000..881e589ad79
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/batch-error-generic.md
@@ -0,0 +1,25 @@
+---
+title: Batch task failed: Cannot select a record in Current client sessions (SysClientSessions). Sessionld: 0, 0. The SQL database has issued an error.
+description: Error during inventory closing, recalculation or reverse -- Batch task failed: Cannot select a record in Current client sessions (SysClientSessions). Sessionld: 0, 0. The SQL database has issued an error.
+author: Soumyamoy Das
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\Batch task failed: Cannot select a record in Current client sessions (SysClientSessions). Sessionld: 0, 0. The SQL database has issued an error.
+---
+
+# Batch task failed: Cannot select a record in Current client sessions (SysClientSessions). Sessionld: 0, 0. The SQL database has issued an error.
+
+## Symptoms
+
+Inventory closing, recalculation or reverse errors out with "Batch task failed: Cannot select a record in Current client sessions (SysClientSessions). Sessionld: 0, 0. The SQL database has issued an error.".
+
+## Resolution
+
+This issue can occur due to SQL database unavailability, deadlocks, blockings or any other generic SQL limitation/error. Most of the time, these issues are transient and never cause any data corruption. Please retry the operation again. If the issue persists, please reach out to Microsoft Support or your Partner. 
diff --git a/support/dynamics-365/supply-chain/costing/closed-inventory-transactions-adjusted.md b/support/dynamics-365/supply-chain/costing/closed-inventory-transactions-adjusted.md
new file mode 100644
index 00000000000..8f9d9dac890
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/closed-inventory-transactions-adjusted.md
@@ -0,0 +1,27 @@
+---
+title: Already closed inventory transactions being reopened and adjusted again
+description: Already closed inventory transactions being reopened and adjusted again
+author: soumyamoydas
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\Already closed inventory transactions being reopened and adjusted again
+---
+
+# Already closed inventory transactions being reopened and adjusted again
+
+## Symptoms
+
+It is observed that already closed inventory transactions being reopened and settles/adjusted again in the subsequent closings or recalculations.
+
+## Resolution
+
+This behavior is by design and might be observed for items using Weighted Average (Date) as the valuation model.  
+
+As per the design of carrying out settlements/adjustments through inventory closing/recalculation, a summarized transaction is created each for all issues and receipts separately, and these summarized transactions settle/adjust issues to receipts. Now, post-closing, if any manual adjustment is posted to any inventory transaction which was involved in any of the previous summarized transactions, and a fresh closing/recalculation is executed, then correspondingly all the inventory transactions which made up the summarized transaction contributing to the settlement/adjustment process, would be reopened and re-settled/re-adjusted.  
diff --git a/support/dynamics-365/supply-chain/costing/difference-in-tb-and-inventory-value.md b/support/dynamics-365/supply-chain/costing/difference-in-tb-and-inventory-value.md
new file mode 100644
index 00000000000..eef72239c4d
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/difference-in-tb-and-inventory-value.md
@@ -0,0 +1,34 @@
+---
+title: Ledger Trial Balance differs from Inventory Value post execution of inventory closing, recalculation or reverse
+description: Ledger Trial Balance differs from Inventory Value post execution of inventory closing, recalculation or reverse
+author: Soumyamoy Das
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\Ledger Trial Balance differs from Inventory Value post execution of inventory closing, recalculation or reverse
+---
+
+# Ledger Trial Balance differs from Inventory Value post execution of inventory closing, recalculation or reverse
+
+## Symptoms
+
+Upon checking the inventory value and trial balance reports, it is observed that trial balance for the corresponding main accounts differs from the inventory value.
+
+## Resolution
+
+Normally this issue is resolved after rebuilding the Trial Balance for the corresponding Main Accounts from General Ledger -> Inquiries and reports -> Trial Balance.
+
+Verify whether inventory closing, recalculation or reverse execution has been completed successfully and whether voucher postings are present. Cross check the status of batch job with the voucher execution status. Check the logs in the Closing and Adjustment form for the correponding voucher. Once verified, rebuild the trial balance for the specific account where you are observing the differences. 
+
+If the issue persists, this means there is inconsistency between the general ledger and inventory postings. Try generating potential conflicts report to trace the items resulting in conflicts.  
+
+Next, inventory value report can be generated for those specific items to trace the inconsistent inventory transactions. Consistency check shall be executed for those items for on-hand and inventory transactions to check whether it resolves the data inconsistencies. Consistency check can be executed from System administration -> Periodic tasks -> Database -> Check/Fix error -> Inventory management -> Item -> Enable checkbox for Inventory transactions and On-hand, then filter the exact item from the dialog. If the consistency check fix makes any changes to the inventory postings, execute inventory closing again and rebuild the trial balances to check whether the balance matches now.  
+
+In case none of these help, please reach out to Microsoft support or your partner. 
+
diff --git a/support/dynamics-365/supply-chain/costing/duplicate-reverse-is-not-allowed.md b/support/dynamics-365/supply-chain/costing/duplicate-reverse-is-not-allowed.md
new file mode 100644
index 00000000000..aac5f10516f
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/duplicate-reverse-is-not-allowed.md
@@ -0,0 +1,27 @@
+---
+title: Duplicate reverse is not allowed
+description: Duplicate reverse is not allowed while trying to reverse a closing or recalculation voucher
+author: Soumyamoy Das
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing, InventoryReveresal, InventoryRecalculation, DuplicateReverse
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\Duplicate reverse is not allowed
+---
+
+# Duplicate reverse is not allowed
+
+## Symptoms
+
+Inventory reverse fails with the following error as "Another Inventory %1 reverse for voucher %2 is running. Duplicate reverse is not allowed.". 
+
+## Resolution
+
+This issue mainly occurs when user tries to execute the reversal/cancellation of multiple closing/recalculation vouchers at the same time. As shared in the best practices for Inventory Reverse, always execute the reversal of one voucher at a time, and only after its completion, proceed with further reversals i.e. reversals should be carried out sequentially. This is a check used to prevent multiple reversals and thereby avoid any inventory & ledger data corruption due to concurrent updates of adjustments/settlements/postings. 
+
+This issue can rarely occur if the previous reversal execution has not completed successfully, but the batch job has ended with error, and user tries to execute a fresh reverse of the original voucher. This can be due to system issues, sudden crashes, system or SQL server unavailability, etc. In such cases, you can reach out to Microsoft Support or your Partner. 
diff --git a/support/dynamics-365/supply-chain/costing/error-negative-oh-hand.md b/support/dynamics-365/supply-chain/costing/error-negative-oh-hand.md
new file mode 100644
index 00000000000..8793248a136
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/error-negative-oh-hand.md
@@ -0,0 +1,27 @@
+---
+title: Inventory closing cannot proceed because available physical on-hand inventory on item is currently negative, which is not allowed according to its item model group
+description: Error during inventory closing or recalculation -- Inventory closing cannot proceed because available physical on-hand inventory on item is currently negative, which is not allowed according to its item model group
+author: Soumyamoy Das
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\Inventory closing cannot proceed because available physical on-hand inventory on item is currently negative, which is not allowed according to its item model group
+---
+
+# Inventory closing cannot proceed because available physical on-hand inventory on item XXX is currently negative, which is not allowed according to its item model group
+
+## Symptoms
+
+Inventory closing or recalculation errors out with "Inventory closing cannot proceed because available physical on-hand inventory on item abc is currently negative, which is not allowed according to its item model group". The error can be viewed from the closing logs.
+
+## Resolution
+
+This can happen because of data corruption in the posted inventory transactions, when the on-hand physical/financial inventory becomes negative which is otherwise not allowed as per the item’s Item Model Group configuration. Ideally this error should be flagged while posting transactions for an item which results in negative on-hand, and not during inventory closing/recalculation process. But if any manual intervention or data migration or direct database updates are done, these checks are skipped and hence the error is thrown during the stock closing process. In those cases, this error is thrown during the stock closing process.  
+
+As the error already mentions the specific item, please go through the inventory transactions for that item and try to figure out the actual issue. If required, enable the negative physical/financial inventory, but final call should be taken as per your business requirements. Else manual adjustments can also be posted to balance out the inventory transactions resulting in negative inventory. Once these transactions are fixed, execute consistency check fix for that item from System administration -> Periodic tasks -> Database -> Fix error -> Inventory management -> Item -> Enable checkbox for Inventory transactions and On-hand, then filter the exact item from the dialog. If required, this process can be executed as a batch process in the background. The final fix logs can be viewed from the batch job logs. Upon completion of this process, resume the closing/recalculation operation.
diff --git a/support/dynamics-365/supply-chain/costing/error-processing -level-total-bundles.md b/support/dynamics-365/supply-chain/costing/error-processing -level-total-bundles.md
new file mode 100644
index 00000000000..71febaa4caf
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/error-processing -level-total-bundles.md	
@@ -0,0 +1,25 @@
+---
+title: Close stock - processing level x with a total of y bundles
+description: Error during inventory closing or recalculation -- Close stock - processing level x with a total of y bundles
+author: Soumyamoy Das
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\Close stock - processing level x with a total of y bundles
+---
+
+# Close stock - processing level x with a total of y bundles
+
+## Symptoms
+
+Inventory closing or recalculation errors out with "Close stock - processing level x with a total of y bundles".
+
+## Resolution
+
+This is a generic error thrown mostly in cases on business data corruption due to manual database interventions, manual changes in the decimal precision in the customized version, incorrect exchange rate configurations while posting source documents, etc. Try to trace the exact item, inventory transactions for which would be responsible for this error. Then execute the consistency check for that item for on-hand and inventory transactions (from System administration -> Periodic tasks -> Database -> Check/Fix error -> Inventory management -> Item -> Enable checkbox for Inventory transactions and On-hand, then filter the exact item from the dialog), to verify whether there are data inconsistencies which can be corrected autonomously. If the issue persists, please reach out to Microsoft Support or your Partner. 
diff --git a/support/dynamics-365/supply-chain/costing/fiscal-period-is-not-open.md b/support/dynamics-365/supply-chain/costing/fiscal-period-is-not-open.md
new file mode 100644
index 00000000000..8e994694530
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/fiscal-period-is-not-open.md
@@ -0,0 +1,25 @@
+---
+title: Fiscal period is not open
+description: Encountering error fiscal period is not open during inventory closing, recalculation or reverse or during journal postings
+author: Soumyamoy Das
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing, JournalPosting, InventoryReverse, InventoryRecalculation
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\Fiscal period is not open
+---
+
+# Fiscal period is not open
+
+## Symptoms
+
+Inventory closing, recalculation or reverse or journal postings (like inventory journal, production orders, purchase orders, sales orders, etc.) errors out with the following message as "Fiscal period for XXX is not open". 
+
+## Resolution
+
+Please verify the ledger calendar period status from General Ledger -> Calendars -> Ledger calendars -> Select the required ledger period and then verify the period status for specific legal entities. Ideally, the period status should be “Open” to allow the posting of any adjustments. 
diff --git a/support/dynamics-365/supply-chain/costing/inventory-transactions-posted-at-different-cost-price.md b/support/dynamics-365/supply-chain/costing/inventory-transactions-posted-at-different-cost-price.md
new file mode 100644
index 00000000000..b7ee2588439
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/inventory-transactions-posted-at-different-cost-price.md
@@ -0,0 +1,33 @@
+---
+title: Inventory transactions posted at a different cost price
+description: Inventory transactions posted at a different cost price
+author: Soumyamoy Das
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\Inventory transactions posted at a different cost price
+---
+
+# Inventory transactions posted at a different cost price
+
+## Symptoms
+
+It is observed that some inventory transactions posted at a different cost price than the one mentioned during posting
+
+## Resolution
+
+Please note that issue transactions are always posted at the running average cost, and the receipt transactions are posted at the cost specified during posting the document line, or the latest activated cost price. 
+
+The system estimates this running average cost price for an item by using the following formula: 
+
+Estimated price = (Physical amount + Financial amount) ÷ (Physical quantity + Financial quantity) 
+
+If the “Include physical value” option isn't selected for an item in its Item Model Group, the system uses 0 (zero) for both the physical amount and the physical quantity. 
+
+For more understanding, [this](https://learn.microsoft.com/en-us/dynamics365/supply-chain/cost-management/running-average-cost-price) can be referred.
diff --git a/support/dynamics-365/supply-chain/costing/ledger-access-level-error.md b/support/dynamics-365/supply-chain/costing/ledger-access-level-error.md
new file mode 100644
index 00000000000..a6f2553a134
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/ledger-access-level-error.md
@@ -0,0 +1,25 @@
+---
+title: Only users in user group x can post in module y in the period containing the date z
+description: Error during inventory closing or recalculation -- Only users in user group x can post in module y in the period containing the date z
+author: Soumyamoy Das
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\Only users in user group x can post in module y in the period containing the date z
+---
+
+# Only users in user group x can post in module y in the period containing the date z
+
+## Symptoms
+
+Inventory closing or recalculation errors out with "Only users in user group x can post in module y in the period containing the date z".
+
+## Resolution
+
+Please verify the ledger calendar period access level from General Ledger -> Calendars -> Ledger calendars -> Select the required ledger period and then verify the access level for specific modules and legal entities. Default access level for all the modules is “<All>”. 
diff --git a/support/dynamics-365/supply-chain/costing/posting-profile-setup.md b/support/dynamics-365/supply-chain/costing/posting-profile-setup.md
new file mode 100644
index 00000000000..4e366cb0477
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/posting-profile-setup.md
@@ -0,0 +1,26 @@
+---
+title: Account number for transaction type does not exist
+description: Error during inventory closing or recalculation -- Account number for transaction type does not exist
+author: Soumyamoy Das
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\Account number for transaction type does not exist
+---
+
+# Account number for transaction type does not exist
+
+## Symptoms
+
+Inventory closing or recalculation errors out with "Account number for transaction type XXX does not exist".
+
+## Resolution
+
+Verify whether Main Account is correctly setup for the specified transaction type under proper head in Inventory Management -> Setup -> Posting -> Posting. Also, verify the financial dimensions' in the Accounting Structure Setup for the corresponding Main Accounts from General Ledger -> Ledger setup -> Ledger. 
+Once all the setup are verified, try resuming calculation for the corresponding voucher.
diff --git a/support/dynamics-365/supply-chain/costing/project-budget-exceed.md b/support/dynamics-365/supply-chain/costing/project-budget-exceed.md
new file mode 100644
index 00000000000..eec3f722b75
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/project-budget-exceed.md
@@ -0,0 +1,29 @@
+---
+title: The entry for category x on project y cannot be posted/approved because it would cause the cost budget to be exceeded by z
+description: Inventory closing/recalculation/reverse errors out with -- The entry for category x on project y cannot be posted/approved because it would cause the cost budget to be exceeded by z
+author: Soumyamoy Das
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\The entry for category x on project y cannot be posted/approved because it would cause the cost budget to be exceeded by z
+---
+
+# The entry for category x on project y cannot be posted/approved because it would cause the cost budget to be exceeded by z
+
+## Symptoms
+
+Inventory closing, recalculation, or reverse fails with "The entry for category x on project y cannot be posted/approved because it would cause the cost budget to be exceeded by z" error during the ledger posting stage. The error can be traced from the Logs in Closing and Adjustment form, after selecting the specific voucher.
+
+## Resolution
+
+This issue can appear when inventory closing, recalculation or reverse adjusts/settles the project enabled inventory transactions, and such adjustments/settlements exceed the budget control price set for that specific project. As a temporary mitigation, please navigate to Project management and accounting -> Setup -> Project management and accounting parameters -> Cost control -> Budget control -> Disable “Use budget control” 
+
+Once disabled, resume the inventory closing/recalculation/reverse voucher, and once the operation completes, enable the parameter back. 
+
+For permanent mitigation, please try updating the project budget control cost as per the business requirement. 
diff --git a/support/dynamics-365/supply-chain/costing/transaction-cannot-be-reopened-as-it-has-already-been-pre-closed.md b/support/dynamics-365/supply-chain/costing/transaction-cannot-be-reopened-as-it-has-already-been-pre-closed.md
new file mode 100644
index 00000000000..f31b0f5044a
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/transaction-cannot-be-reopened-as-it-has-already-been-pre-closed.md
@@ -0,0 +1,31 @@
+---
+title: Transaction cannot be reopened as it has already been pre-closed
+description: Error during inventory closing or recalculation -- Transaction cannot be reopened as it has already been pre-closed
+author: Soumyamoy Das
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\Transaction cannot be reopened as it has already been pre-closed
+---
+
+# Transaction cannot be reopened as it has already been pre-closed
+
+## Symptoms
+
+Inventory closing or recalculation errors out with "Transaction XXX cannot be reopened as it has already been pre-closed".
+
+## Resolution
+
+This issue can rarely occur if there are any data corruptions in the inventory transactions/adjustments, when pre-closing has posted settlements to financial transactions and closed them, instead of the non-financial transactions. Pre-closing is executed implicitly in the inventory closing/recalculation process for the non-financial transfers against which we have any markings. This issue might have most likely occurred in that process. 
+
+This can be traced directly from the database in InventTrans table. The records agianst which we have some values posted in QtySettled and CostAmountSettled fields but again ValueOpen is false and NonFinancialTransferInventClosing has got some record id of a closing/recalculation voucher. 
+
+One of the mitigations is to explicitly reset the ValueOpen, NonFinancialTransferInventClosing and DateClosed in those records in InventTrans and retry the closing process again. In case of any direct database data modifications, please carry out first in any lower replica and check whether everything is correct as per the business and calculation procedures.
+
+In case of any further assisstance, please reach out to Microsoft Support or your Partner to fix this issue. 
diff --git a/support/dynamics-365/supply-chain/costing/unable-to-edit-a-record-in-table.md b/support/dynamics-365/supply-chain/costing/unable-to-edit-a-record-in-table.md
new file mode 100644
index 00000000000..8166e623275
--- /dev/null
+++ b/support/dynamics-365/supply-chain/costing/unable-to-edit-a-record-in-table.md
@@ -0,0 +1,29 @@
+---
+title: Unable to edit a record in table
+description: SQL error while updating/inserting data in a table related to the inventory closing or journal posting procedures
+author: Soumyamoy Das
+ms.date: 11/26/2025
+ms.topic: troubleshooting
+ms.search.form: InventClosing, SQLError, JournalPosting
+audience: Application User
+ms.reviewer: kamaybac
+ms.search.region: Global
+ms.author: soumyamoydas
+ms.search.validFrom: 2021-05-31
+ms.dyn365.ops.version: 10.0.43
+ms.custom: sap:Cost management\Unable to edit a record in table
+---
+
+# Unable to edit a record in table
+
+## Symptoms
+
+Inventory closing, recalculation or reverse errors out with the following message as "Unable to edit a record in InventSettlement table". The same can be traced with multiple other processes like inventory journal, sales order, production or purchase order postings, or with different other tables like InventTrans, AssetTrans, ProdTable, etc. 
+
+## Resolution
+
+This message signifies that some SQL issues have prevented further execution, due to which any process or batch job failed. Normally these issues can be deadlocks as multiple other processes are also executing at the same time, or SQL Server Availability issues due to increased traffic, or due to insufficient and inappropriate indexing resulting to query timeouts for long running queries. Generally, these SQL issues are mostly transient and shall be done away with retries. 
+
+Sometimes, it is observed that customizations also result in deadlocks and blockings due to inappropriate transaction scope and error handling. Please try to trace the error message from the batch job (or related processes), call stack, SQL statement, verify whether any customizations are poresent, check the indexes and index fragmentations. 
+
+In case the issue persists after retrying, please feel free to contact Microsoft Support or your Partner.