You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/dynamics-365/supply-chain/costing/inventory-closing-recalculation-reverse.md
+11-7Lines changed: 11 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ This issue occurs when you try to execute the reversal or cancellation of multip
63
63
64
64
Always execute the reversal of vouchers one at a time, and wait for each reversal to complete before proceeding to the next one.
65
65
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.
67
67
68
68
## Inventory closing cannot proceed because available physical on-hand inventory on item \<ItemName\> is currently negative
69
69
@@ -79,7 +79,7 @@ You can view this error in the inventory closing logs. For more information on a
79
79
80
80
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.
81
81
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.
83
83
84
84
### Solution
85
85
@@ -97,7 +97,7 @@ Usually, the system flags this error while posting transactions for an item that
97
97
1. Run the consistency check.
98
98
99
99
> [!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.
101
101
102
102
1. Once the consistency check completes, you can view the final fix logs from the batch job logs or in the notification panel.
103
103
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:
112
112
113
113
### Cause
114
114
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.
116
120
117
121
### Solution
118
122
@@ -128,7 +132,7 @@ This error usually occurs because of business data corruption due to manual data
128
132
1. Run the consistency check.
129
133
130
134
> [!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.
132
136
133
137
1. Once the consistency check completes, you can view the final fix logs from the batch job logs or in the notification panel.
134
138
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
203
207
204
208
### Cause
205
209
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.
207
211
208
212
### Solution
209
213
@@ -247,7 +251,7 @@ For each problematic transaction you identify, update the following field values
247
251
After updating all problematic transactions, resume the closing or recalculation operation.
248
252
249
253
> [!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.
0 commit comments