1. Base Currency Conversion Implementation Guide
  2. Conversion Test Environment Setup

Conversion Test Environment Setup

To help ensure the success of the base currency conversion, complete the preconversion, conversion, and postconversion tasks in a test environment before you complete them in the production environment.

JD Edwards EnterpriseOne provides these environments for conversion testing in the software:

  • Conference Room Pilot (CRPxxx, where xxx = release, such as CRP733).

  • Testing (TSTxxx, where xxx = release, such as TST733).

Verify that one of these environments is installed at the site and use it for the base currency conversion testing. By running and completing the conversion in one of these test environments, you can continue to run the daily operations in the production environment while preparing for the conversion in a test environment. Companies with multiple environments should test the conversion separately for each environment.

The test environment should contain a copy of the most current production data. Refresh the test environment from the production environment before you begin testing the base currency conversion.

Complete the preconversion, conversion, and postconversion tasks on data in the test environment. If you test only a portion of the data, the results are incomplete and do not apply to the actual conversion in the production environment. Remember that you must correct any data issues that you identify in the test environment in both the test and production environments.

Important: If you decide not to complete the preconversion, conversion, and postconversion tasks first in a test environment and instead complete them in the production environment, be aware that JD Edwards EnterpriseOne does not support or help ensure the success of the base currency conversion. The risks involved in converting the production environment without first preparing and testing the conversion in a test environment are consequential to the operation of the company. The potential risk for downtime, hastily made decisions, and incorrect converted data must be taken very seriously.