Fix Depreciation Errors: Changing Fields in Microsoft Dynamics GP Fixed Assets

Table of Contents

Accurate depreciation is a cornerstone of sound financial reporting for any organization. It ensures that the cost of an asset is systematically allocated over its useful life, reflecting its consumption and reducing its book value. In Microsoft Dynamics GP, the Fixed Assets module is instrumental in managing this complex accounting process, providing robust tools for tracking, calculating, and reporting on an organization’s tangible assets. This module is vital for maintaining compliance, optimizing tax strategies, and gaining precise insights into asset utilization.

However, users may occasionally encounter an error that disrupts this critical functionality, specifically when attempting to modify certain fields within the Fixed Assets module. This article delves into the common “Recalc/Reset was unsuccessful. Return Code 99” error, providing a detailed understanding of its cause and a structured approach to its resolution, ensuring the integrity and accuracy of your fixed asset data in Microsoft Dynamics GP.

Understanding Depreciation in Microsoft Dynamics GP’s Fixed Assets Module¶

Depreciation is an accounting method used to allocate the cost of a tangible asset over its useful life. It serves to match the expense of the asset with the revenue it generates, providing a more accurate view of a company’s profitability and asset valuation over time. Microsoft Dynamics GP supports various depreciation methods, including straight-line, declining balance, and sum-of-the-years’ digits, allowing organizations to apply the most appropriate method for their assets and financial policies.

The Fixed Assets module in Dynamics GP is a comprehensive sub-ledger designed to automate asset management processes. It handles everything from asset acquisition and capitalization to depreciation calculation, disposals, and transfers. This module seamlessly integrates with the General Ledger, ensuring that depreciation expenses and asset values are accurately reflected in the financial statements. Proper setup and maintenance of the Fixed Assets module are crucial for reliable financial reporting and compliance.

Depreciation Sensitive Fields¶

Within the Fixed Assets module, certain fields are classified as “depreciation sensitive” because any changes to them directly impact the asset’s depreciation schedule. These fields include, but are not limited to, the original cost, salvage value, estimated useful life, depreciation method, depreciation start date, and depreciation basis. Modifying these parameters necessitates a recalculation of the asset’s depreciation, as the system must adjust future depreciation entries to reflect the new financial attributes.

When a change is made to one of these critical fields, the system attempts to perform an immediate recalculation to maintain data integrity. If this recalculation process encounters an underlying issue, it may fail, leading to an error message. Understanding which fields are sensitive helps users anticipate system behavior and potential issues during asset record adjustments.

Symptoms: Decoding “Recalc/Reset was unsuccessful. Return Code 99”¶

Users attempting to modify a depreciation sensitive field in the Asset Book window of Microsoft Dynamics GP’s Fixed Assets module may be met with an abrupt error message:

Recalc/Reset was unsuccessful. Return Code 99.

This error prevents the desired changes from being saved, effectively locking the asset record from further adjustments related to its depreciation. The immediate impact is the inability to correct or update asset information, which can have cascading effects on financial reporting, asset tracking, and audit readiness. The presence of this error signals a disruption in the system’s ability to process and re-synchronize depreciation data.

Beyond the direct prevention of updates, this error can lead to a state of inconsistency within the Fixed Assets module. If an asset’s information cannot be updated to reflect accurate parameters, its book value and depreciation expense may become incorrect over time. This discrepancy can result in inaccurate balance sheets and income statements, potentially impacting business decisions and external audits. Therefore, resolving this error promptly is paramount for maintaining the integrity of financial data.

Root Cause Analysis: The Desynchronized Quarters¶

The underlying cause of the “Recalc/Reset was unsuccessful. Return Code 99” error is often a desynchronization between the quarters defined within the Fixed Assets module and the fiscal periods set up for the company in Microsoft Dynamics GP. Dynamics GP uses fiscal periods to structure its financial data, including the calculation and posting of depreciation. The Fixed Assets module maintains its own internal calendar and quarter definitions, which must align perfectly with the company’s main fiscal periods to function correctly.

When these “quarters in Fixed Assets are out of sync,” it means that the internal calendar used by the Fixed Assets module does not correctly correspond to the actual fiscal periods (months, quarters, years) that the company operates under. This misalignment can occur due to several reasons, such as:

• Changes to Fiscal Periods: If fiscal year setup is modified (e.g., changes to start/end dates, number of periods) after Fixed Assets has been in use, the FA module’s internal calendar may not automatically update to reflect these changes.
• Data Migration Issues: During an initial setup or data migration, if the FA calendar was not built correctly or fully synchronized.
• Database Corruption: Rare instances of database inconsistencies can lead to quarter definitions becoming corrupt or misaligned.
• Manual Adjustments: Incorrect manual adjustments to system dates or calendar settings by advanced users.

Because the system relies on these synchronized quarters to accurately project and post depreciation, any discrepancy will cause the recalculation process to fail. The “Recalc/Reset” function cannot map the asset’s depreciation life to the incorrect or missing periods, hence the “Return Code 99” indicating a fundamental structural problem with the Fixed Assets calendar.

mermaid graph TD A[Change Depreciation Sensitive Field] --> B{System Attempts Recalculation}; B --> C{Fixed Assets Quarters Aligned with Fiscal Years?}; C -- No --> D["Recalc/Reset was unsuccessful. Return Code 99"]; C -- Yes --> E[Recalculation Successful]; D --> F[Need to Rebuild FA Quarters]; F --> G[Run Build Calendar Utility]; G --> H[Synchronize Quarters to Fiscal Years]; H --> I[Re-attempt Field Change]; I --> J{Error Resolved?}; J -- No --> K[Rebuild Entire FA Calendar]; J -- Yes --> L[Process Complete!];

Pre-Resolution Best Practices and Safeguards¶

Before attempting any resolution steps, especially those involving critical system utilities, it is imperative to implement robust safeguards to protect your data. These precautions minimize the risk of data loss and ensure a smooth recovery process if unforeseen issues arise.

The Importance of a Complete Database Backup¶

The foremost step before proceeding with any system-level changes is to create a complete and verifiable backup of your Microsoft Dynamics GP company database. This backup should include all relevant databases, such as the Dynamics system database and the specific company database where the issue is occurring. A recent backup serves as a critical recovery point, allowing you to restore your system to its previous state if any unexpected problems or data corruption occur during the resolution process. Without a current backup, any irreversible changes could lead to significant data loss and operational disruption.

Testing in a Copied Company Environment¶

Whenever possible, it is highly recommended to first test the resolution steps in a copied or test company that has been created from a recent backup of your live data. This practice provides a safe, isolated environment where you can freely experiment with the solution without impacting your production system or live financial records. Testing allows you to:

• Validate the solution: Confirm that the proposed steps effectively resolve the error.
• Identify potential side effects: Discover any unintended consequences before they affect your live data.
• Refine the process: Become familiar with the steps, ensuring confidence when applying them to the live environment.

This proactive approach significantly reduces risk and increases the likelihood of a successful resolution in your active company.

Step-by-Step Resolution: Rebuilding FA Quarters¶

The primary method for resolving the “Recalc/Reset was unsuccessful. Return Code 99” error involves rebuilding the Fixed Assets quarters. This process re-synchronizes the Fixed Assets internal calendar with your company’s defined fiscal periods.

1. Access the Build Calendar Utility:

   • Log into Microsoft Dynamics GP as a user with appropriate administrative permissions.
   • Navigate to the top menu bar, click on Microsoft Dynamics GP.
   • From the dropdown menu, point to Tools.
   • Then, point to Utilities.
   • Finally, point to Fixed Assets, and select Build Calendar.
   • This utility is specifically designed to manage the internal calendar structure that Fixed Assets relies upon for depreciation calculations.

2. Mark the Synchronize Quarters to Fiscal Years Checkbox:

   • In the Fixed Assets Build Calendar window that appears, locate and mark the checkbox labeled Synchronize Quarters to Fiscal Years.
   • This critical option instructs the system to re-evaluate and re-align the Fixed Assets quarters (which are typically defined as periods within fiscal years) to precisely match the fiscal year definitions that are configured in your company’s fiscal period setup. It ensures that the depreciation schedules recognize the correct start and end dates of each accounting period.

3. Initiate the Build Process:

   • After selecting the synchronization option, click the Build button.
   • The system will then process the request, rebuilding the Fixed Assets calendar structure based on the current fiscal year settings. This operation may take a few moments, depending on the volume of data and the complexity of your fiscal period setup. A progress bar or message may indicate that the process is underway.

4. Re-attempt the Change in Asset Book:

   • Once the build process is complete, close the Build Calendar window.
   • Navigate back to the Asset Book window where you initially encountered the error.
   • Attempt to make the depreciation sensitive field change that previously triggered the “Recalc/Reset was unsuccessful” error.
   • If the FA quarters were indeed out of sync, this action should now complete successfully, and the changes will be saved without the error message.

Advanced Troubleshooting: Re-creating the Entire FA Calendar¶

If the “Recalc/Reset was unsuccessful. Return Code 99” error persists after attempting to rebuild and synchronize the FA Quarters, it suggests a deeper underlying issue with the Fixed Assets calendar’s integrity. In such cases, a more comprehensive approach involving the re-creation of the entire Fixed Assets calendar might be necessary. This process is more drastic and essentially involves resetting the entire calendar structure within the Fixed Assets module.

While the original KB article provides specific guidance, the general concept for rebuilding the entire FA calendar typically involves:

1. Deleting the Existing Fixed Assets Calendar: This step involves removing all current calendar definitions within the Fixed Assets module. This is usually done through a specific maintenance utility or by carefully following system-provided instructions to clear out the existing calendar data. It’s crucial to understand that this does not delete your asset data, but rather the structural framework used for depreciation periods.

2. Re-creating the Calendar from Scratch: After deletion, the calendar must be re-initialized. This involves re-running the Build Calendar utility, often without the “Synchronize Quarters” option initially, to create a blank calendar, and then potentially running it again with the synchronization option to populate it correctly based on your company’s fiscal periods. This ensures that a fresh, uncorrupted calendar structure is established.

This advanced step should only be undertaken after confirming that the simpler quarter synchronization method has failed. It requires a thorough understanding of your company’s fiscal period setup in Dynamics GP, as the new calendar will derive its structure from these definitions. Always ensure you have a robust backup before proceeding with such a significant change to prevent data loss.

Post-Resolution Verification and Maintenance¶

After implementing the resolution steps, it is essential to perform thorough verification and consider preventive measures to maintain the health of your Fixed Assets module.

Reviewing Quarter Setup for Missing Periods¶

Even after rebuilding the calendar, it is a good practice to manually review the quarter setup for the entire life of relevant assets. This involves checking the fiscal period definitions in Microsoft Dynamics GP (Microsoft Dynamics GP > Tools > Setup > Company > Fiscal Periods) and then cross-referencing them with the Fixed Assets calendar details if accessible. Ensure there are no missing periods or inconsistencies across different fiscal years, especially if your fiscal year definitions have changed over time. This proactive check helps confirm that the system can properly project depreciation for all past and future periods an asset will exist.

Data Integrity Check and Preventive Measures¶

Beyond checking the calendar, consider running other Fixed Assets utilities that check for data integrity. Microsoft Dynamics GP often provides reconciliation tools within modules that can identify and correct minor discrepancies. Regular maintenance and understanding the dependencies within the Fixed Assets module can prevent future issues:

• Understand Fiscal Year Changes: Be particularly cautious when defining or modifying fiscal years. Any changes should prompt a review of the Fixed Assets calendar.
• Consistent Setup: Ensure that fiscal period settings are consistent across all companies and modules if you have a multi-company setup.
• User Training: Train users who manage Fixed Assets on best practices for data entry and field modifications, emphasizing the importance of accurate initial setup.
• Scheduled Maintenance: Periodically run maintenance utilities within Dynamics GP to ensure database health and module consistency.

By adhering to these practices, you can minimize the recurrence of “Recalc/Reset” errors and maintain a highly accurate and efficient Fixed Assets system within Microsoft Dynamics GP.

Conclusion¶

The “Recalc/Reset was unsuccessful. Return Code 99” error in Microsoft Dynamics GP Fixed Assets can be a frustrating hurdle, but it is typically a solvable issue rooted in calendar synchronization. By understanding that this error signals a misalignment of internal Fixed Assets quarters with your company’s fiscal periods, you can systematically address the problem. The most common resolution involves utilizing the “Build Calendar” utility to synchronize these quarters.

In cases where the initial synchronization is insufficient, a more comprehensive rebuild of the entire Fixed Assets calendar may be necessary. Regardless of the chosen path, the critical importance of performing complete database backups and testing solutions in a copied company environment cannot be overstated. These safeguards are indispensable for protecting your valuable financial data and ensuring a smooth resolution process. By diligently following these steps and maintaining a proactive approach to system health, you can ensure the accuracy and integrity of your depreciation calculations and asset management within Microsoft Dynamics GP, contributing to robust financial reporting and operational efficiency.

Have you encountered this specific error in your Microsoft Dynamics GP environment? What steps did you find most effective in resolving it? Share your experiences and insights in the comments below! Your contributions can help others navigating similar challenges.