writer updates

Author: haywoodsloan

support/dynamics-365/supply-chain/costing/inventory-closing-recalculation-reverse.md

@@ -17,7 +17,7 @@ This article provides troubleshooting guidance for common errors that might occu
 
 ### Symptoms
 
-An inventory closing, recalculation, or reverse fails with the following error:
+An inventory closing, recalculation, or reverse fails with the following error message:
 
 > Batch task failed: Cannot select a record in Current client sessions (SysClientSessions). Sessionld: 0, 0. The SQL database has issued an error.
 
@@ -27,31 +27,31 @@ This issue can occur due to SQL database unavailability, deadlocks, blockings, o
 
 ### Solution
 
-Most of the time, these type of issues are transient and never cause any data corruption. Retry the operation.
+Most of the time, these issues are transient and don't cause any data corruption. Retry the operation.
 
 ## Duplicate reverse is not allowed
 
 ### Symptoms
 
-An Inventory reverse fails with the following error:
+An inventory reverse fails with the following error message:
 
 > Another Inventory %1 reverse for voucher %2 is running. Duplicate reverse is not allowed
 
 ### Cause
 
-This issue occurs when you try to execute the reversal or cancellation of multiple closing or recalculation vouchers at the same time. Reversals must be carried out sequentially. This approach prevents any inventory and ledger data corruption due to concurrent updates of adjustments, settlements, or postings.
+This issue occurs when you try to execute the reversal or cancellation of multiple closing or recalculation vouchers at the same time. You must carry out reversals sequentially. This approach prevents any inventory and ledger data corruption due to concurrent updates of adjustments, settlements, or postings.
 
 ### Solution
 
 Always execute the reversal of one voucher at a time, and only after its completion, proceed with further reversals.
 
-This issue can occur if the previous reversal execution doesn't complete successfully, but the batch job ends with error, and the user tries to execute a new reverse of the original voucher. This issue can occur due to system issues, sudden crashes, system or SQL server unavailability, and so on. In such cases, contact Microsoft Support or your partner.
+This issue can occur if the previous reversal execution doesn't complete successfully, but the batch job ends with error, and you try to execute a new reverse of the original voucher. This issue can occur due to system issues, sudden crashes, system or SQL server unavailability, and so on. In such cases, contact Microsoft Support or your partner.
 
 ## Inventory closing cannot proceed because available physical on-hand inventory on item \<ItemName\> is currently negative
 
 ### Symptoms
 
-An inventory closing or recalculation fails with the following error:
+An inventory closing or recalculation fails with the following error message:
 
 > Inventory closing cannot proceed because available physical on-hand inventory on item \<Item\> is currently negative, which isn't allowed according to its item model group
 
@@ -66,11 +66,11 @@ Usually, the system flags this error while posting transactions for an item that
 ### Solution
 
 1. Review the inventory transactions for the item mentioned in the error message to identify the cause of this issue.
-   1. If necessary, based on your business requirements, you can enable the negative physical or financial inventory.
+   1. If necessary, based on your business requirements, enable the negative physical or financial inventory.
    1. Alternatively, you can post manual adjustments to balance out the inventory transactions that result in a negative inventory.
-1. Once you fix the transactions, execute a consistence check for that item:
+1. Once you fix the transactions, execute a consistency check for that item:
    1. Go to **System administration** > **Periodic tasks** > **Database** > **Consistency check**.
-   1. In the consistency check dialog set **Check/Fix** to **Fix error**.
+   1. In the consistency check dialog, set **Check/Fix** to **Fix error**.
    1. Set **Module** to **Inventory management**.
    1. Expand the **Item** tree and select the checkboxes for **Inventory transactions** and **On-hand**.
    1. Open the More menu (**...**) and select **Dialog**.
@@ -80,14 +80,14 @@ Usually, the system flags this error while posting transactions for an item that
    > [!NOTE]
    > If required, you can run the check as a batch process in the background.
 
-1. Once the consistence check completes, you can view the final fix logs from the batch job logs or in the notification panel.
+1. Once the consistency check completes, you can view the final fix logs from the batch job logs or in the notification panel.
 1. After completing the consistency check, resume the closing or recalculation operation.
 
 ## Close stock - processing level \<Level\> with a total of \<Total\> bundles
 
 ### Symptoms
 
-An inventory closing or recalculation fails with the following error:
+An inventory closing or recalculation fails with the following error message:
 
 > Close stock - processing level \<Level\> with a total of \<Total\> bundles
 
@@ -97,10 +97,10 @@ This error usually occurs because of business data corruption due to manual data
 
 ### Solution
 
-1. Identify the item and inventory transactions causing this error
+1. Identify the item and inventory transactions causing this error.
 1. Execute a consistency check for that item for on-hand and inventory transactions.
    1. Go to **System administration** > **Periodic tasks** > **Database** > **Consistency check**.
-   1. In the consistency check dialog set **Check/Fix** to ?????. <!-- (need to confirm with SME) -->
+      1. In the consistency check dialog, set **Check/Fix** to ?????. <!-- (need to confirm with SME) -->
    1. Set **Module** to **Inventory management**.
    1. Expand the **Item** tree and select the checkboxes for **Inventory transactions** and **On-hand**.
    1. Open the More menu (**...**) and select **Dialog**.
@@ -110,7 +110,7 @@ This error usually occurs because of business data corruption due to manual data
    > [!NOTE]
    > If required, you can run the check as a batch process in the background.
 
-1. Once the consistence check completes, you can view the final fix logs from the batch job logs or in the notification panel.
+1. Once the consistency check completes, you can view the final fix logs from the batch job logs or in the notification panel.
 1. After completing the consistency check, resume the closing or recalculation operation.
 
 ## Fiscal period is not open
@@ -134,7 +134,7 @@ Verify the ledger calendar period status:
 
 ### Symptoms
 
-An inventory closing or recalculation fails with the following error:
+An inventory closing or recalculation fails with the following error message:
 
 > Account number for transaction type \<Type\> does not exist
 
@@ -156,13 +156,13 @@ After verifying your setup, resume the closing or recalculation operation.
 
 ### Symptoms
 
-An inventory closing or recalculation fails with the following error:
+An inventory closing or recalculation fails with the following error message:
 
 > Only users in user group \<Group\> can post in module \<Module\> in the period containing the date \<Date\>
 
 ### Solution
 
-1. Go to **General Ledger** > **Calendars** > **Ledger calendars**
+1. Go to **General Ledger** > **Calendars** > **Ledger calendars**.
 1. Select the required ledger period, then check the access level for specific modules and legal entities.
 
    > [!NOTE]
@@ -174,15 +174,15 @@ An inventory closing or recalculation fails with the following error:
 
 ### Symptoms
 
-An inventory closing, recalculation, or reverse fails during the ledger posting stage with the following error message:
+An inventory closing, recalculation, or reverse operation fails during the ledger posting stage with the following error message:
 
 > The entry for category \<Category\> on project \<Project\> cannot be posted/approved because it would cause the cost budget to be exceeded by \<Amount\>
 
 You can view this error in the inventory closing logs. For more information on accessing closing logs, see [Inventory close](/dynamics365/supply-chain/cost-management/inventory-close#the-inventory-close-log).
 
 ### Cause
 
-This issue can appear when inventory closing, recalculation, or reverse adjustments settles the project-enabled inventory transactions, and those adjustments or settlements exceed the budget control price set for that specific project.
+This issue can appear when inventory closing, recalculation, or reverse adjustments settle the project-enabled inventory transactions, and those adjustments or settlements exceed the budget control price set for that specific project.
 
 ### Solution
 
@@ -191,7 +191,7 @@ As a temporary workaround:
 1. Go to **Project management and accounting** > **Setup** > **Project management and accounting parameters** > **Cost control**.
 1. Set **Budget control** to **Disabled**. <!-- Need to ask SME where "Use budget control" applies to -->
 1. Resume the inventory closing, recalculation, or reverse voucher.
-1. After the inventory operation completes, set **Budget control** back to **Enabled** <!-- Need to confirm this value with the SME -->
+1. After the inventory operation completes, set **Budget control** back to **Enabled**. <!-- Need to confirm this value with the SME -->
 
 For a more permanent solution, update the project budget control cost to meet your business requirements.
 
@@ -207,23 +207,26 @@ An inventory closing or recalculation fails with the following error message:
 
 This issue can occur if data corruptions exist in the inventory transactions or adjustments. The error happens when pre-closing incorrectly posts settlements to and closes financial transactions. Pre-closing should only affect non-financial transactions.
 
-The inventory closing and recalculation processes implicitly execute pre-closing for the non-financial transfers against which it has any markings. This issue most likely occurred in that process.
+The inventory closing and recalculation processes implicitly execute pre-closing for the non-financial transfers against which they have any markings. This issue most likely occurred in that process.
 
 ### Solution
 
-You can identify which transactions are causing this issue from the `InventTrans` table in the database. Look for records that meet the following criteria:
+You can identify which transactions cause this issue from the `InventTrans` table in the database. Look for records that meet the following criteria:
 
 - A value is specified for the `QtySettled` or `CostAmountSettled` fields
 - The `ValueOpen` field is set to `false`
 - The `NonFinancialTransferInventClosing` field is set to the record ID of a closing or recalculation voucher.
 
-For each problematic transaction you identify, reset the `ValueOpen`, `NonFinancialTransferInventClosing`, `DateClosed` fields. After updating all problematic transactions, resume the closing or recalculation operation.
+For each problematic transaction you identify, reset the following fields: <!-- What does resetting them entail -->
+
+- `ValueOpen`
+- `NonFinancialTransferInventClosing`
+- `DateClosed`
 
-1. Reset the `ValueOpen`, `NonFinancialTransferInventClosing`, `DateClosed` fields
-1. After updating all problematic transactions, resume the closing or recalculation operation.
+After updating all problematic transactions, resume the closing or recalculation operation.
 
 > [!IMPORTANT]
-> When making any direct database data modification, you should first make the change in a lower replica then confirm everything is work correctly before proceeding to other replicas.
+> When making any direct database data modification, first make the change in a lower replica then confirm everything works correctly before proceeding to other replicas.
 
 ## Unable to edit a record in table
 
@@ -235,14 +238,14 @@ An inventory closing, recalculation, or reverse fails with the following error m
 
 ### Cause
 
-This issue occurs when a SQL error prevents further execution and cause a process or batch job to fail. Typically, these SQL errors are deadlocks that occur when multiple processes execute at the same time. Other possible causes include SQL Server availability issues due to increased traffic, or insufficient and inappropriate indexing that results in query timeouts for long running queries.
+This issue occurs when a SQL error prevents further execution and causes a process or batch job to fail. Typically, these SQL errors are deadlocks that occur when multiple processes execute at the same time. Other possible causes include SQL Server availability issues due to increased traffic, or insufficient and inappropriate indexing that results in query timeouts for long running queries.
 
 ### Solution
 
 Usually, these SQL issues are transient and go away with retries.
 
-Sometimes, customizations also result in deadlocks and blocking issues due to inappropriate transaction scopes and error handling. Tace the error message from the batch job or related processes, call stack, and SQL statement. Verify if any customizations are present. If customizations are present, check the indexes and index fragmentation. <!-- The indexes and index fragmentation of what? The customizations? The tables the customizations are applied to? -->
+Sometimes, customizations also result in deadlocks and blocking issues due to inappropriate transaction scopes and error handling. Trace the error message from the batch job or related processes, call stack, and SQL statement. Verify if any customizations are present. If customizations are present, check the indexes and index fragmentation. <!-- The indexes and index fragmentation of what? The customizations? The tables the customizations are applied to? -->
 
 ## Additional support
 
-If the guidance in this article does not resolve your issue, contact Microsoft Support or your partner for further assistance.
+If the guidance in this article doesn't resolve your issue, contact Microsoft Support or your partner for further assistance.