1. Base Currency Conversion Implementation Guide
  2. Base Currency Conversion and Non-JD Edwards EnterpriseOne Records

Base Currency Conversion and Non-JD Edwards EnterpriseOne Records

The programs for the base currency conversion convert records that are created and maintained using JD Edwards EnterpriseOne software. They do not convert records that you entered through custom programs or third-party software unless required fields and tables are identical to those of the JD Edwards EnterpriseOne software. The example illustrates this concept.

To avoid rounding issues, the two Distribution conversion programs, Euro Conversion of F4301, F4311, and F4311T (R894301E) and Euro Conversion for F43121 (R8943121E), calculate new unit costs by converting records based on unit of measure (UOM).

For the conversion to run successfully, these UOM fields must be completed:

  • Transaction (PDUOM) and purchase order (PDUOM3) in the Purchase Order Detail File table (F4311).

  • Transaction (PRUOM0) and purchase order (PRUOM3) in the Purchase Order Receiver File table (F43121).

These four UOM fields are required fields in JD Edwards EnterpriseOne software. If you have non-JD Edwards EnterpriseOne records, the R894301E and R8943121E conversion programs do not convert them unless these four UOM fields are completed before you run the conversion.

To help you research and determine which fields must be completed in non-JD Edwards EnterpriseOne records to convert records successfully when you run a specific conversion program:

  • Enter a record in JD Edwards EnterpriseOne and compare that record to a non-JD Edwards EnterpriseOne record.

    For example, enter a sales order in JD Edwards EnterpriseOne Sales Order Management and compare the fields that are completed on that record with the fields that are completed on the non-JD Edwards EnterpriseOne record. This should help you quickly identify the required fields in a table so that you can complete those fields on the non-JD Edwards EnterpriseOne record.

  • Review the documentation that discusses the fields that are required for processing batches and electronic data interchange (EDI) transactions.

    This documentation includes information about which fields and tables must contain data in order for the system to upload a non-JD Edwards EnterpriseOne record into the tables. Use this information to help you identify the required fields in a table so that you can complete those fields on the non-JD Edwards EnterpriseOne record.

See also: