Dynamics GP Error: Resolving 'USD Currency Does Not Exist' for Your Company

Table of Contents

Encountering errors while generating financial reports can be a significant hurdle, especially when dealing with critical business data. One common issue faced by users of Microsoft Dynamics GP and Management Reporter is the perplexing error message: “Currency USD does not exist for company xxxx. No values will be returned.” This error can halt report generation and leave users scrambling for a solution. Understanding the root cause and knowing how to resolve it efficiently is crucial for maintaining smooth financial operations. This article delves into the intricacies of this error, providing a comprehensive guide to diagnosing and fixing it, ensuring your financial reporting remains accurate and uninterrupted.

Symptoms¶

When attempting to generate a report within Management Reporter, you might be abruptly stopped by the following error message:

Currency USD does not exist for company xxxx. No values will be returned.

This message indicates that the system is unable to locate the USD currency for the specified company (represented by ‘xxxx’). Consequently, the report generation process fails, and no financial data is presented. This issue prevents users from accessing crucial financial insights and necessitates immediate attention to restore reporting functionality. The error typically arises during report generation, disrupting workflows and potentially delaying important business decisions that rely on timely financial information. It’s essential to address this error promptly to ensure the continued accuracy and availability of financial reporting within Dynamics GP.

Cause¶

The underlying cause of the “Currency USD does not exist” error stems from the differing ways currency configurations are interpreted between the Legacy provider and the Data Mart provider within Dynamics GP. These providers act as bridges connecting Dynamics GP data to Management Reporter, but they employ distinct methods for recognizing and processing currency information.

The Legacy provider identifies currencies based on the Currency ID assigned to them in Dynamics GP. For instance, in the default TWO company within Dynamics GP, currencies are often configured with IDs like Z-US$. This provider relies on this specific Currency ID to correctly identify and utilize the currency in financial reports. When Management Reporter is configured to use the Legacy provider, it expects to find currencies referenced by their Currency IDs as defined in Dynamics GP.

Conversely, the Data Mart provider recognizes currencies based on the ISO Code assigned to them. ISO codes are standardized three-letter currency codes, such as USD for United States Dollar. The Data Mart provider, designed for enhanced performance and data integration, utilizes these ISO codes for currency identification. If Management Reporter is set up with the Data Mart provider, it will search for currencies using their ISO codes.

The discrepancy arises when there’s a mismatch between the provider being used by Management Reporter and the currency configuration it expects. If, for example, you are using the Data Mart provider, but your currency settings in Dynamics GP are still using Legacy-style Currency IDs (like Z-US$ instead of USD ISO code), the Data Mart provider will fail to recognize “USD” as a valid currency for the company, leading to the error message. This difference in currency identification methods is the core reason behind the “Currency USD does not exist” error.

Feature	Legacy Provider	Data Mart Provider
Currency Recognition	Currency ID (e.g., Z-US$)	ISO Code (e.g., USD)
Performance	Generally slower for large datasets	Optimized for performance, faster for large datasets
Data Integration	More direct link to Dynamics GP database	Data is processed and stored in a separate data mart
Use Case	Suitable for smaller datasets, simpler reporting	Recommended for larger datasets, complex reporting

Resolution¶

To resolve the “Currency USD does not exist” error, you need to ensure consistency between the currency provider selected in Management Reporter and the currency configuration within your report definitions. The key lies in verifying and adjusting the Currency Display settings in your column definitions and the Company settings in your tree definitions.

Step 1: Check Currency Display in Column Definitions

1. Open Report Designer for Management Reporter.
2. Navigate to the Column Definitions.
3. Examine the FD (Financial Dimension) columns used in your report.
4. Locate the Currency Display cell for each FD column.
5. Crucially, if you are using the Data Mart provider, the Currency Display should be set to the ISO code, which is USD. If you see Currency IDs like Z-US$, this indicates a mismatch.

Step 2: Verify Company Settings in Tree Definitions

1. Open the Tree Definitions in Report Designer.
2. Check the Company column in your tree structure.
3. Identify the company codes. If the company codes are designated as Legacy companies (typically indicated by the inclusion of “-Curr” in the company code name, such as “TWO-Curr”), then the Currency Display in your column definitions should align with the Legacy provider’s currency identification method. In this case, you should use Currency IDs like Z-US$ in your column definitions.
4. Conversely, if the companies are set up to use the Data Mart provider (company codes without the “-Curr” suffix, like “TWO”), then the Currency Display in the column definitions must be set to use ISO codes like USD.

Step 3: Adjust Currency Display as Needed

Based on your provider configuration and the company settings in your tree definition, adjust the Currency Display in your column definitions accordingly.

• For Data Mart provider: Ensure Currency Display is set to USD (or the appropriate ISO code for other currencies).
• For Legacy provider: Ensure Currency Display is set to Z-US$ (or the corresponding Currency ID for other currencies).

Step 4: Script for Updating Currency Codes (Data Mart Migration)

If you are transitioning from the Legacy provider to the Data Mart provider, you might need to update your column definitions to reflect the change in currency code requirements. While the original article mentions a script, it does not provide it directly. A script to address this would typically involve querying the Management Reporter database to identify column definitions that are still using Legacy Currency IDs and updating them to ISO codes.

Conceptual Script Example (SQL - Adapt for your specific database and environment):

-- Replace 'YourDataMartDatabaseName' with your actual Data Mart database name
USE YourDataMartDatabaseName;

-- Identify column definitions using Legacy Currency IDs (e.g., Z-US$) in Currency Display
SELECT
    ColumnDefinitionID,
    ColumnDefinitionName,
    CurrencyDisplay
FROM
    ColumnDefinitionTable  -- Replace with the actual table name for column definitions
WHERE
    CurrencyDisplay = 'Z-US$'; -- Example: Check for Z-US$, adjust for other Legacy IDs

-- Example UPDATE statement (USE WITH CAUTION - BACKUP YOUR DATABASE FIRST)
-- Update Currency Display to ISO code (USD) for identified columns
UPDATE ColumnDefinitionTable -- Replace with the actual table name
SET CurrencyDisplay = 'USD'
WHERE CurrencyDisplay = 'Z-US$'; -- Match the Legacy ID identified in the SELECT query and update to ISO code

-- Review changes and test reports
SELECT
    ColumnDefinitionID,
    ColumnDefinitionName,
    CurrencyDisplay
FROM
    ColumnDefinitionTable
WHERE
    CurrencyDisplay = 'USD';

Important Notes Regarding the Script:

• Backup Your Database: Before running any SQL script that modifies data, always back up your Management Reporter database. This is crucial to prevent data loss in case of errors.
• Adapt the Script: The provided SQL script is a conceptual example. You will need to adapt it to your specific Management Reporter database schema, table names, and the exact Legacy Currency IDs you need to update. Consult your database documentation or a database administrator for assistance if needed.
• Testing: After running any script, thoroughly test your reports to ensure that the currency error is resolved and that your financial data is displayed correctly.

By carefully reviewing and adjusting your Currency Display settings in column definitions and ensuring they align with the provider type and company settings, you can effectively resolve the “Currency USD does not exist” error in Dynamics GP Management Reporter and restore accurate financial reporting. Remember to test your reports after making any changes to verify the issue is resolved.

Do you have any experiences with this error or other Dynamics GP currency issues? Share your thoughts and questions below!