Skip to content

Commit 0731652

Browse files
committed
minor cleanup
1 parent 9da50c7 commit 0731652

1 file changed

Lines changed: 11 additions & 7 deletions

File tree

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

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -63,7 +63,7 @@ This issue occurs when you try to execute the reversal or cancellation of multip
6363

6464
Always execute the reversal of vouchers one at a time, and wait for each reversal to complete before proceeding to the next one.
6565

66-
This issue can also occur if a previous reversal execution doesn't complete successfully, the batch job ends with errors, and you try to execute a new reverse of the original voucher. This behavior 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.
66+
This issue can also occur if a previous reversal execution doesn't complete successfully, the batch job ends with errors, then you try to execute a new reverse of the original voucher. This behavior 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.
6767

6868
## Inventory closing cannot proceed because available physical on-hand inventory on item \<ItemName\> is currently negative
6969

@@ -79,7 +79,7 @@ You can view this error in the inventory closing logs. For more information on a
7979

8080
This error can occur because of data corruption in the posted inventory transactions. This error occurs when the on-hand physical or financial inventory becomes negative, which isn't allowed as per the item’s _Item Model Group_ configuration.
8181

82-
Usually, the system flags this error while posting transactions for an item that results in negative on-hand inventory, not during inventory closing or recalculation. But if you manually intervene, migrate data, or update the database directly, these checks are skipped and this error can occur during the stock closing process.
82+
Usually, the system flags this error while posting transactions for an item that results in negative on-hand inventory, not during inventory closing or recalculation. But if you manually intervene, migrate data, or update the database directly, these checks are skipped. In this scenario, the error can occur during the stock closing process.
8383

8484
### Solution
8585

@@ -97,7 +97,7 @@ Usually, the system flags this error while posting transactions for an item that
9797
1. Run the consistency check.
9898

9999
> [!NOTE]
100-
> If required, you can run the check as a batch process in the background.
100+
> If necessary, you can run the check as a batch process in the background.
101101
102102
1. Once the consistency check completes, you can view the final fix logs from the batch job logs or in the notification panel.
103103
1. After completing the consistency check, resume the closing or recalculation operation.
@@ -112,7 +112,11 @@ An inventory closing or recalculation fails with the following error message:
112112
113113
### Cause
114114

115-
This error usually occurs because of 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, and similar issues.
115+
This error usually occurs because of:
116+
117+
- Business data corruption due to manual database interventions.
118+
- Manual changes to the decimal precision in the customized version.
119+
- Incorrect exchange rate configurations while posting source documents and similar issues.
116120

117121
### Solution
118122

@@ -128,7 +132,7 @@ This error usually occurs because of business data corruption due to manual data
128132
1. Run the consistency check.
129133

130134
> [!NOTE]
131-
> If required, you can run the check as a batch process in the background.
135+
> If necessary, you can run the check as a batch process in the background.
132136
133137
1. Once the consistency check completes, you can view the final fix logs from the batch job logs or in the notification panel.
134138
1. After completing the consistency check, resume the closing or recalculation operation.
@@ -203,7 +207,7 @@ You can view this error in the inventory closing logs. For more information on a
203207

204208
### Cause
205209

206-
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.
210+
This issue can appear when inventory closing, recalculation, or reverse adjustments settle the project-enabled inventory transactions. Then those adjustments or settlements exceed the budget control price set for that specific project.
207211

208212
### Solution
209213

@@ -247,7 +251,7 @@ For each problematic transaction you identify, update the following field values
247251
After updating all problematic transactions, resume the closing or recalculation operation.
248252

249253
> [!IMPORTANT]
250-
> 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.
254+
> When making any direct database data modification, first make the change in a lower replica and confirm everything works correctly before proceeding to other replicas.
251255
252256
## Unable to edit a record in table
253257

0 commit comments

Comments
 (0)