Error message when closing ledger period ( PU 34 , 10.0.10)
-
Error message when closing ledger period ( PU 34 , 10.0.10)
Posted by vy.ngo@gigamon.com on April 20, 2020 at 5:35 pm-
Hello All,
We just updated our D365 F&O to PU 34 (10.0.10) last weekend. Today, we try to change the Period status from Open to Onhold for month closing and we get this error below. We have never faced with this issue before since we are using standard cost method. I’m not sure why D365 asks for inventory closing.
Does any one get the same issue? How can we by pass the inventory closing process to close the period without any error ?Thanks in advance.
–error message —
You are about to change the status of ledger period Period 3 to On hold. No execution of Inventory close with a date 3/31/2020 matching period end has been registered.
Please execute an inventory close as of 3/31/2020 matching the period end before changing the status. The valuation of inventories, cost of goods sold and variances may not be correct in Subledger or general ledger until this has been executed. Reported from legal entity XXX.——————————
Vy Ngo——————————
-
Vy,
Do you have access to the Financial period close workspace?
Add this to the end of your URL: &mi=LedgerPeriodCloseProjectWorkspace
Do you have any tasks here that pertain to inventory close?
——————————
Ian Gorman, PMP, MCSE
Senior Consultant
——————————
——————————————- -
Hi Vy,
We are at the same version as you (V10.0.10) in our Test environment and we do not have the same issue but we have no tasks that pertain to Inventory as per Ian’s suggestions.
Thanks
——————————
Chantal Golding
PSP Investments
Montreal QC
——————————
——————————————- -
Hi Chantal,Ā
This validation happens when you have the inventory transaction in this period. Maybe your TEST environment doesn’t have inventory transaction in the period that you tested. I had several discussions with Microsoft team as I raised the ticket to them and they were able to reproduce the issue. However, they explained to me that it’s as-design so we will have to run the closing inventory even nothing will be posted to GL due to standard cost method. Below is the latest email from MS team that I just received this morning
—————We have internally discussed and finally concluded this behavior is now as by-design.Ā The correct period end process should be as below:
- Close Inventory for the period. This prevent postings that affect the Inventory (PO, SO etc.)
- On-hand adjustments (NRV)
- Set General ledger period to On-hold. This prevent all postings to occur in period
- Prepare external/Internal reporting. User validate the data Reconciliation Inventory to GL ect.
- In case adjustments needs to be done in GL the ledger period is changed back to Open
- Report results external/Internal
Ā
- The previous steps are suggested to avoid new variances to occur as it could happen that Standard cost is not 100% used. Plus, even for Standard cost, inventory close has always been “‘required/suggested”. The inventory closing process inserts a period balance into a table which is used in Reporting and Revaluation.
- There could be performance concerns if you are not running inventory closing now and then try to do it some day later after running business for quite a while.
Ā
Please let me know if this assessment is correct or if there is anything further I can help you with related to this support incident.
——————————
Vy Ngo
Sr Manager ERP Systems
Gigamon Inc.
Santa Clara CA
——————————
——————————————- -
Hi Ian.
No, we did not setup the financial period close process. We did close March period successfully before updating to PU 34. After updating to PU 34, accounting team opened the period and booked another adjustment and then they cannot update the period back to onhold.I created the ticket with MS team and they explained to me that it’s now as by-design. That means you will have to perform the inventory closing process . It’s an extra step even there is nothing posted to GL as we are using standard cost. Below is the email from MS team
—————————————-We have internally discussed and finally concluded this behavior is now as by-design.Ā The correct period end process should be as below:
- Close Inventory for the period. This prevent postings that affect the Inventory (PO, SO etc.)
- On-hand adjustments (NRV)
- Set General ledger period to On-hold. This prevent all postings to occur in period
- Prepare external/Internal reporting. User validate the data Reconciliation Inventory to GL ect.
- In case adjustments needs to be done in GL the ledger period is changed back to Open
- Report results external/Internal
Ā
- The previous steps are suggested to avoid new variances to occur as it could happen that Standard cost is not 100% used. Plus, even for Standard cost, inventory close has always been “‘required/suggested”. The inventory closing process inserts a period balance into a table which is used in Reporting and Revaluation.
- There could be performance concerns if you are not running inventory closing now and then try to do it some day later after running business for quite a while.
——————————
Vy Ngo
Sr Manager ERP Systems
Gigamon Inc.
Santa Clara CA
——————————
——————————————- -
I saw some quality update towards fiscal closing, might want to check in LCS for PU34
——————————
Best Regards
Rahul Mohta
Partner – Real Dynamics
——————————
——————————————-
vy.ngo@gigamon.com replied 5 years, 5 months ago 1 Member · 0 Replies -
-
0 Replies
Sorry, there were no replies found.
The discussion ‘Error message when closing ledger period ( PU 34 , 10.0.10)’ is closed to new replies.