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
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ ms.custom: sap:Cost management\Issues with inventory closing and recalculation
13
13
14
14
This article provides troubleshooting guidance for common errors that might occur during inventory close, recalculation, or reverse in Microsoft Dynamics 365 Supply Chain Management.
15
15
16
-
## Another closing or adjustment has not finished yet
16
+
## Another closing or adjustment is in progress
17
17
18
18
### Symptoms
19
19
@@ -31,7 +31,7 @@ This issue occurs when you attempt to execute a new closing or recalculation whi
31
31
32
32
Wait for the previous closing or voucher execution to complete, then you can execute a new closing or recalculation.
33
33
34
-
## Batch task failed: Cannot select a record in Current client sessions
34
+
## Cannot select a record in current client sessions
35
35
36
36
### Symptoms
37
37
@@ -65,7 +65,7 @@ Always execute the reversal of vouchers one at a time, and wait for each reversa
65
65
66
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
-
## Inventory closing cannot proceed because available physical on-hand inventory on item \<ItemName\> is currently negative
68
+
## Inventory closing cannot proceed
69
69
70
70
### Symptoms
71
71
@@ -102,7 +102,7 @@ Usually, the system flags this error while posting transactions for an item that
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.
104
104
105
-
## Close stock - processing level \<Level\> with a total of \<Total\> bundles
105
+
## Failure when closing stock
106
106
107
107
### Symptoms
108
108
@@ -177,7 +177,7 @@ Also, check the financial dimensions in the _Accounting Structure Setup_ for the
177
177
178
178
After verifying your configuration, resume the closing or recalculation operation.
179
179
180
-
## Only users in user group \<Group\>can post in module \<Module\> in the period containing the date\<Date\>
180
+
## User can't post in module for a given date
181
181
182
182
### Symptoms
183
183
@@ -195,7 +195,7 @@ An inventory closing or recalculation fails with the following error message:
195
195
196
196
1. After updating the access levels, resume the closing or recalculation operation.
197
197
198
-
## The entry for category \<Category\> on project \<Project\> cannot be posted/approved because it would cause the cost budget to be exceeded by \<Amount\>
198
+
## An entry can't be posted or approved because of the cost budget
199
199
200
200
### Symptoms
201
201
@@ -220,7 +220,7 @@ As a temporary workaround:
220
220
221
221
For a more permanent solution, update the project budget control cost to meet your business requirements.
222
222
223
-
## Transaction cannot be reopened as it has already been pre-closed
223
+
## A transaction cannot be reopened after being pre-closed
0 commit comments