People Soft Enterprise One Euro Conversion Workbook

July 2001
Euro Conversion
and
Integrity Workbook
J.D. Edwards World Source Company
One Technology Way
Denver, CO 80237
Copyright © J.D. Edwards World Source Company, 2000, 2001
All Rights Reserved
J.D. Edwards is a registered trademark of J.D. Edwards & Company. The names of all other
products and services of J.D. Edwards used herein are trademarks or registered trademarks of
J.D. Edwards World Source Company.
All other product names used are trademarks or registered trademarks of their respective
owners.
The information in this guide is confidential and a proprietary trade secret of J.D. Edwards
World Source Company. It may not be copied, distributed, or disclosed without prior written
permission. This guide is subject to change without notice and does not represent a
commitment on the part of J.D. Edwards & Company and/or its subsidiaries. The software
described in this guide is furnished under a license agreement and may be used or copied only
in accordance with the terms of the agreement. J.D. Edwards World Source Company uses
automatic software disabling routines to monitor the license agreement. For more details about
these routines, please refer to the technical product documentation.
Table of Contents
About This Workbook ....................................................................................... 1

Pre-Conversion Tasks .................................................................................. 2
Conversion Tasks ......................................................................................... 2
Post-Conversion Tasks ................................................................................ 3
About the Euro Conversion .............................................................................. 4
Euro Exchange Rates................................................................................... 6
How Amounts Are Converted ................................................................... 6
Accounts Receivable and Accounts Payable...................................... 7
General Accounting............................................................................... 8
Procurement ........................................................................................... 8
Sales Order Management.................................................................... 10
Service Billing/Contract Billing ......................................................... 11
Ledgers Affected by the Euro Conversion............................................. 11
XA, YA, ZA Ledgers and Detailed Restatement Records ............ 12
Differences Between the Workbench and Post-Conversion Jobs ...... 12
The Euro Conversion and Non-JDE Records ...................................... 14
Coexistence and the Euro Conversion.................................................... 15
F0911 Amounts Before and After the Euro Conversion............................ 17
Domestic and Foreign Ledger Amounts................................................. 17
Domestic EMU Transaction.............................................................. 18
Foreign EMU Transaction (Before 1 January 1999) ...................... 18
Foreign EMU Transaction (As of 1 January 1999)......................... 19
Foreign Euro Transaction .................................................................. 20
Foreign Non-EMU Transaction........................................................ 21
Alternate Ledger Amounts........................................................................ 22
Domestic-Only Transaction............................................................... 23
Euro Foreign Transaction .................................................................. 24
Non-EMU Foreign Transaction........................................................ 25
Pre-Conversion Tasks 27
Planning a Euro Conversion Strategy ............................................................ 28
Establishing a Euro Conversion Project Team...................................... 28
Example: One Approach to the Euro Conversion ............................... 29
Setting Up a Euro Conversion Test Environment....................................... 31
Reviewing Sizing Impacts and System Resources ........................................ 33
Sizing Impacts ............................................................................................. 33
Sizing Impacts on the F0911 and F0902 Tables ............................. 34
Sizing Impacts on the F0086 Table................................................... 34
System Resources and Performance ........................................................ 35
Euro Conversion Software Requirements ..................................................... 37
Copying Tables to Your Conversion Environment..................................... 38
Copying the F0085 Table to Your Conversion Environment............. 39
Copying the F9843 Table to Your Conversion Environment............. 42
Creating Indices Before Running the Conversion........................................ 45
Completing System-Level Prerequisites......................................................... 46
Checklist: System-Level Prerequisites...................................................... 46
Currency Code Values for CRCD and CRCX Fields............................ 51
Completing Pre-Conversion Tasks ................................................................. 55
Checklist: Financials Pre-Conversion Tasks........................................... 56
Accounts Receivable............................................................................ 56
Accounts Payable................................................................................. 57
General Accounting............................................................................. 59
Reports .................................................................................................. 63
Localization........................................................................................... 63
Fixed Assets/Job Cost ........................................................................ 64
Checklist: Distribution Pre-Conversion Tasks....................................... 65
Checklist: Manufacturing Pre-Conversion Tasks................................... 66
Checklist: Final Post................................................................................... 68
Reviewing and Correcting Pre-Conversion Integrity Reports .................... 69
Coexistence and Accounts Receivable .................................................... 71
Checklist: Financials Pre-Conversion Integrity Reports ....................... 72
Localization........................................................................................... 78
Fixed Assets/Job Cost ........................................................................ 78
Change Management........................................................................... 79
Checklist: Distribution Pre-Conversion Integrity Reports ................... 79
Checklist: Logistics Pre-Conversion Integrity Reports ......................... 80
Checklist: Manufacturing Pre-Conversion Integrity Reports............... 80
Checklist: Batch Headers Pre-Conversion Integrity Reports............... 80
Checklist: Post Integrity Job (Repost) ..................................................... 81
Purging Outdated Data Tables........................................................................ 82
Checklist: General Purge Programs ......................................................... 84
Checklist: Financials Purge Programs...................................................... 84
Address Book ....................................................................................... 87
Checklist: Fixed Assets Purge Programs................................................. 88
Technical Considerations: Distribution Purge Programs ..................... 89
Checklist: Distribution Purge Programs.................................................. 90
Procurement ......................................................................................... 90
Sales Order Management.................................................................... 91
Electronic Commerce ......................................................................... 92
Checklist: Logistics Purge Program ......................................................... 95
Warehouse Management..................................................................... 96
Checklist: Manufacturing Purge Programs ............................................. 96
Work Orders......................................................................................... 96
Rerunning Pre-Conversion Integrity Reports ............................................... 98
Conversion Tasks 99
Environments and Euro Conversion Plans................................................. 100
Setting Up a Euro Conversion Plan ............................................................. 102
Verifying Statuses for UDC (H90/DS)................................................. 103
Setting Up Constants for a Conversion Plan........................................ 104
Euro Exchange Rates........................................................................ 107
Preventing Audit Records from Being Created ................................... 108
Updating the F9843 Table....................................................................... 112
Defining a Conversion Plan.................................................................... 115
Running the Euro Conversion Workbench ................................................ 119
Coexistence: Before Running the OneWorld Conversion ................. 120
During the Euro Conversion.................................................................. 122
Coexistence: After Running the OneWorld Conversion.................... 122
Verifying the Status of the Euro Conversion.............................................. 123
Reviewing the Euro Conversion Reports .................................................... 127
Table Conversion/Merge Driver Report .............................................. 127
Viewing the Conversion Log Records................................................... 128
Table Conversion Report ........................................................................ 129
Examples of Error Messages ........................................................... 129
Reviewing the Euro Conversion Audit Tables ........................................... 132
Exchange Rate Fields in the Conversion Audit Table ........................ 133
Rerunning a Euro Conversion Program ...................................................... 134
Rerunning a Conversion Program Before Updating the F0010 Table135
Rerunning a Conversion Program After Updating the F0010 Table 136
Deleting the Conversion Log for a Plan ...................................................... 138
Before Running Ordered and Additional Conversion Jobs...................... 141
Changing the Plan Exchange Rate Before Running a Job.................. 142
Preventing Audit Records from Being Created for a Job................... 144
Running Ordered Conversion Jobs .............................................................. 146
Checklist: Ordered Conversion Jobs ..................................................... 149
Configuration Management.............................................................. 150
Multicurrency Intercompany............................................................ 151
Distribution and Product Data Management ................................ 152
Company Currency Codes (Required)............................................ 153
Multicurrency Intercompany Post................................................... 154
Converting Multicurrency Intercompany Transactions...................... 154
Running Additional Conversion Jobs........................................................... 158
Checklist: Additional Conversion Jobs.................................................. 161
Sales Order Management.................................................................. 162
Procurement ....................................................................................... 165
Agreement Management................................................................... 167
Advanced Transportation Management......................................... 167
Equipment Management .................................................................. 168
Service Billing ..................................................................................... 169
Product Data Management .............................................................. 170
Stock Valuation .................................................................................. 170
Post-Conversion Tasks 172

Reviewing and Correcting Post-Conversion Integrity Reports ................ 173
Checklist: Financials Post-Conversion Integrity Reports ................... 175
Accounts Receivable.......................................................................... 175
Accounts Payable............................................................................... 178
General Accounting........................................................................... 179
Localization......................................................................................... 180
Fixed Assets/Job Cost ...................................................................... 180
Change Management......................................................................... 181
Checklist: Distribution Pre-Conversion Integrity Report................... 182
Checklist: Logistics Post-Conversion Integrity Reports ..................... 182
Checklist: Manufacturing Post-Conversion Integrity Report............. 183
Checklist: Batch Header Post-Conversion Integrity Report .............. 183
Checklist: Post Integrity Job (Repost) ................................................... 184
Reposting the Account Ledger...................................................................... 185
Completing Post-Conversion Tasks ............................................................. 187
Checklist: Financials Post-Conversion Tasks ....................................... 188
General Accounting........................................................................... 188
Accounts Receivable.......................................................................... 189
Accounts Payable............................................................................... 189
Localization......................................................................................... 190
Checklist: Distribution Post-Conversion Tasks ................................... 191
Checklist: Manufacturing Post-Conversion Tasks............................... 191
Converting the Production Environment.................................................... 193
Appendices 195
Conversion and Post-Conversion Tables .................................................... 196
Euro Conversion Workbench UBEs............................................................ 197
OneWorld Composite Keys........................................................................... 198
OneWorld Indices ........................................................................................... 199
Sample: Table Conversion/Merge Driver Report...................................... 200
Sample: Table Conversion Report ................................................................ 201
Sample: Euro Conversion Audit Report...................................................... 202
Sample: Company Currency Conversion Report........................................ 203
OneWorld Service/Contract Billing ............................................................. 204
Euro Conversion and Integrity Workbook
About This Workbook
Make sure you have the most current copy of the Euro Conversion and Integrity
Workbook before you begin preparing for the euro conversion. In addition,
remember to visit the Euro Base Currency Conversion site on the Knowledge
Garden (Worldwide Topics > Euro Base Currency Conversion) for any late-
breaking information since the publication of the workbook.
The Euro Conversion and Integrity Workbook describes the tasks that you must
complete before, during, and after you run the euro conversion. J.D. Edwards
recommends that you complete the tasks in this workbook twice. First, complete
them in your test, or conference room pilot (CRP), environment, correcting any
data issues in both your test and production environments. Later, when you are
satisfied with the results of the euro conversion in your test environment, complete
all the tasks again in your production environment and "go live."
The contents of this workbook apply to OneWorld releases B73.3.1, B3.3.2, and
Xe unless noted otherwise. This workbook includes the following types of tasks:
• Application. Tasks that apply to employees who are responsible for

overseeing the day-to-day activities for your J.D. Edwards applications.
• Technical. Tasks that apply to employees who are responsible for updates to
your computer systems.
Topics
The tasks in this workbook are divided into the following sections:
G Pre-Conversion Tasks
G Conversion Tasks
G Post-Conversion Tasks
OneWorld B73.3.1, B73.3.2, and Xe (07/01) About This Workbook

1
Pre-Conversion Tasks
The following table lists the pre-conversion tasks and identifies whether your
application personnel, technical personnel, or both should review and complete the
task.
Pre-Conversion Task Application Technical
Planning a euro conversion strategy x x
Setting up a euro conversion test environment x
Reviewing sizing impacts and system resources x
Euro conversion software prerequisites x
Copying tables to your conversion environment x
Creating indices before running the euro conversion x
Completing system-level prerequisites x x
Completing pre-conversion tasks x
Reviewing and correcting pre-conversion integrity x

reports
Purging outdated data tables x
Rerunning pre-conversion integrity reports x
Conversion Tasks
The following table lists the conversion tasks and identifies whether your
task.
Conversion Task Application Technical
Environments and euro conversion plans x x
Setting up a euro conversion plan x
Running the euro conversion workbench x x
Verifying the status of the euro conversion x x

2
Conversion Task Application Technical
Reviewing the euro conversion reports and audit tables x
Rerunning a euro conversion program x x
Deleting the conversion log for a plan x
Before running ordered and additional conversion jobs x
Running ordered conversion jobs x
Running additional conversion jobs x
Post-Conversion Tasks
The following table lists the post-conversion tasks and identifies whether your
task.
Post-Conversion Task Application Technical
Reviewing and correcting post-conversion integrity x

reports
Reposting the account ledger x
Completing post-conversion tasks x
Converting the production environment x

3
About the Euro Conversion
The euro conversion consists of programs that convert a company's base currency
to the euro. Specifically, the programs do the following:
• Convert all monetary amounts in all data tables from the base currency to
the euro, regardless of the batch status of the records in the tables.
For a complete list of the data tables converted, see Conversion and Post-
Conversion Tables.
• Ensure data integrity within a table, when necessary.
• Create an audit trail that shows the original amounts and converted amounts
for each converted table. (Audit trails are optional, based on user
preference.)
The euro conversion programs convert monetary amounts and currency codes
and, as a result, affect all J.D. Edwards data tables that contain currency codes,
monetary amounts, or both in the following systems:
• Financials
• Fixed Assets/Job Cost
• Change Management (OneWorld Xe only)
• Time Accounting
• Localization
• Distribution
• Logistics
• Manufacturing
• Load and Delivery Management/Agreement Management
The results of all conversion programs are final; there is no proof mode. As with
all J.D. Edwards conversions, you cannot add, change, or delete data while the
conversion programs are processing.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) About the Euro Conversion

4
To ensure the success of the euro conversion, it is important that you adhere to
the following guidelines:
• Test the conversion in a test or conference room pilot (CRP) environment

that contains a copy of your production data. See Setting Up a Euro Conversion
Test Environment.
• Correct any data issues that occur during your testing in both your test and
production environments.
• Update your production environment when you are satisfied with the results
of the conversion in your test environment and are ready to "go live."
For optimum results, plan to start and finish the euro conversion process without
interruption. First, complete all the pre-conversion tasks. Next, run the actual
conversion and verify its success. Then, complete the ordered and additional
conversion jobs. Finally, complete the post-conversion tasks and "go live." Now
you are ready to resume your daily business operations.
Note
Do not confuse the euro conversion with the euro enhancements. The euro
conversion converts a company's base (domestic) currency to the euro, whereas
the euro enhancements provide software functionality that allows you to process
transactions in the euro, regardless of whether you have converted your base
currency to the euro.
Topics
G Euro Exchange Rates
G How Amounts are Converted
G Ledgers Affected by the Euro Conversion
G Differences Between the Workbench and Post-Conversion Jobs
G The Euro Conversion and Non-JDE Records
G Coexistence and the Euro Conversion
See Also
G Euro Base Currency site on the Knowledge Garden for information about
the software required for the euro conversion. The path is Worldwide
Topics > Euro Base Currency Conversion > Software > Requirements.

5
Euro Exchange Rates
As of 1 January 1999, the euro exchange rate was irrevocably fixed to EMU
member currencies in 11 of the 12 participating EMU countries. Greece, the 12th
and latest country to join the EMU, had its currency irrevocably fixed to the euro
as of 1 January 2001.
International currencies are quoted as an exchange rate against the euro, and not
against the national EMU currencies. The official conversion rates are as follows:
1 euro equals
40.3399 Belgian francs

1.95583 German marks
166.386 Spanish pesetas
6.55957 French francs
0.787564 Irish pounds
1936.27 Italian lire
40.3399 Luxembourg francs
2.20371 Dutch guilders
13.7603 Austrian schillings
200.482 Portuguese escudos
5.94573 Finnish markka
340.750 Greek drachmas
How Amounts Are Converted
Depending on the table being converted, the euro conversion programs divide the
domestic or foreign amount by the conversion rate in the Currency Exchange
Rates table (F0015) to derive the new euro amount.
The euro conversion programs handle rounding the same way the application
programs handle rounding. For example, if the Accounts Receivable server uses
soft rounding for transactions, the conversion program uses soft rounding.
If an application program is not set up for rounding, the conversion program

performs the following mathematic rounding:
• Rounds down amounts less than 0.5

6
• Rounds up amounts greater than or equal to 0.5
Topics
G Account Receivable and Accounts Payable
G General Accounting
G Procurement
G Sales Order Management
G Service/Contract Billing
Accounts Receivable and Accounts Payable
The euro conversion converts amounts in the F03B11, F03112, F03B13, and
F03B14 tables (Accounts Receivable), F0411 and F0414 tables (Accounts Payable)
as follows:
• For a domestic-only transaction, the original domestic amount (your base

currency before the conversion) is used to derive the new domestic amount
in the euro. The original domestic amount becomes the foreign amount.
• For a foreign transaction between two EMU currencies that was entered
after 1 January 1999, the original domestic amount is used to derive the new
domestic amount in the euro. The original foreign transaction remains the
same.
• For a foreign transaction between two EMU currencies that was entered
before 1 January 1999, the domestic amount is used to derive the new
domestic amount in the euro. The original foreign amount remains the
same, but the rate on the transaction is changed to a calculated rate that is
derived by dividing the new euro amount by the foreign amount.
• For a foreign transaction in the euro, the foreign euro amount becomes the
new domestic amount. The original foreign euro transaction is removed.
• For a foreign transaction between an EMU and non-EMU currency, the
domestic amount is converted to the new euro amount. The original foreign
transaction remains the same.

7
Note
Amounts in the Accounts Payable Matching Document table (F0413) are not
converted; however, the currency mode on domestic payments is updated to
foreign.
General Accounting
For domestic-only transactions, the euro conversion creates CA records that did
not previously exist. Clients should be aware of potential sizing issues. See Reviewing
Sizing Impacts and System Resources.
For more information about how the euro conversion converts and updates
various types of transactions, see F0911 Amounts Before and After the Euro Conversion.
The euro conversion programs also convert the following amounts in the
Accounts Balances (F0902) and 52-Period Account Balances (F0902B) tables:
• Period amounts in the 01 - 14 or 01 - 52 fiscal period buckets

• Non-period amounts such as balance forwards and period year-end net
postings
Procurement
The euro conversion programs in Procurement, unlike those in Sales Order

Management, convert the unit cost and extended cost.
Unit costs (AMC3 and FEA), extended costs (ECST and FEC), and transaction
amounts (AEXP and FEC) are converted as follows:
• For a domestic order, the original domestic amount is used to derive the
new domestic amount. The original domestic amount becomes the foreign
amount.
• For a foreign order in the euro (that will become a domestic order), the
foreign amount becomes the new domestic amount. The original foreign
amount is removed.
• For a foreign order between two EMU currencies entered after 1 January
1999, the foreign amount is used to derive the new domestic amount in the
euro. The original foreign amount remains the same.
• For a foreign order between two EMU currencies entered before 1 January
1999, the original domestic amount is used to derive the new domestic
amount in the euro. The foreign amount remains the same, but the rate on
the order is changed to a calculated rate between the domestic and foreign

8
amounts. This also applies to a foreign order between an EMU and non-
EMU currency.
Note
Because tax fields are domestic only, the original domestic tax amount is converted
to the euro.
Once all unit cost, extended cost, and transaction amounts are converted to the
euro, the Procurement conversion programs recalculate the unit cost in purchasing
(PRRC) in the euro.
To recalculate PRRC in the euro, the conversion programs perform the following
calculations:
1. Add the extended price (AEXP) and amount on hold (ACHG) to derive the
transaction total (total order amount).
AEXP + ACHG = Transaction Total
2. Divide the transaction total by quantity to derive the transaction unit price.
Transaction Total / Quantity = Unit Cost in Transaction
3. Depending on the UOM conversion factor from transaction to primary,
multiply or divide the factor to derive the unit cost in primary.
Unit Cost in Transaction (x or /) factor = Unit Cost in Primary
4. Depending on the UOM conversion factor from primary to purchasing,
multiply or divide the factor to derive the unit cost in purchasing (PRRC).
Unit Cost in Primary (x or /) factor = Unit Cost in Purchasing (PRRC)
The following graphic is a visual representation of the calculations:

9
Example: Recalculating PRRC in the Euro

Remember that PRRC is recalculated after all other Procurement amounts have
been converted to the euro.
In this example, the following UOM conversion setup applies:
1 From = Quantity To Structure

UOM UOM Code
1 BX = 10.0000000 EA
1 CA = 5.0000000 BX
The following graphic is a visual representation of the calculations in this example:
To recalculate a unit cost amount in purchasing (PRRC), the conversion programs

perform the following calculations:
1. 25,565 + 0.00 (AEXP + ACHG) = 25,565 EUR (5 cases)

2. 25,565 / 5 (quantity) = 5,113 EUR (1 case)
3. 5,113 / 50 (factor) = 102.26 EUR (1 each)
4. 102.26 x 10 (factor) = 1022.60 EUR (1 box)
Sales Order Management
The euro conversion programs in Sales Order Management, unlike those in

Procurement, convert the unit price and use the converted unit price to re-
calculate the extended price. The conversion programs were specifically designed
to convert the unit price for the following reasons:
• To minimize rounding issues in the Sales Order Detail table (F4211). The
number of decimal positions stored for unit amounts, such as UPRC, is
determined by the data dictionary (typically 4 decimal places); whereas, the

10
number of decimal positions stored for extended amounts, such as AEXP,

is determined by the currency decimals (typically 0 to 3 decimal places).
Converting the unit price instead of the extended price helps minimize
rounding issues.
• To maintain consistency with Sales Order Management programs. When a
foreign order is created in Sales Order Entry, for example, the entry
program converts the domestic unit price to the foreign price and then
extends out the foreign price. The conversion programs in Sales Order
Management convert amounts in the same way.
• To avoid possible rounding issues in the Price Adjustment History table
(F4074). Price adjustments are applied to the unit price, with the net price
extended out to the extended price. If the conversion program recalculated
the unit price based on a converted extended price instead, the potential for
rounding issues would increase between the unit prices in the Sales Order
Detail (F4211) and Price Adjustment Ledger (F4074) tables.
Service Billing/Contract Billing
For information about how the euro conversion programs convert amounts in the
Service Billing and Contract Billing systems, see OneWorld Service/Contract Billing.
Multicurrency processing was enabled as of release B73.3 for Service Billing and
OneWorld Xe for Contract Billing.
Ledgers Affected by the Euro Conversion
The euro conversion programs convert amounts in all ledgers, except the
following:
• Foreign currency ledger (CA). The foreign transaction amount in the CA

ledger is not converted.
• Currency-specific ledgers (XA, YA, and ZA). If you try to convert a
currency-specific ledger, you will receive an error message. For error
messages that appear on the Table Conversion Report, see Examples of Error
Messages.
• Any ledgers that contain a currency code in the Special Handling field in
UDC table 09/LT and a currency code in the Denominated Currency Code
field in Ledger Type Master Setup (P0025). If you do not want to convert
amounts in a specific ledger, enter a currency code in both of the fields
described above. The euro conversion programs do not convert amounts in
currency-specific ledgers.

11
Budget Amounts
If you do not want to convert your budget amounts to the euro, create a
new ledger type (for example, BX), assign a currency code to the ledger, and
enter your budget amounts. The amounts will not be converted as long as
the ledger has a currency code assigned to it.
• Unit ledger (AU).

Although amounts in the AU ledger are not converted, currency codes are
converted. The following briefly explains this.
Even though unit records are not associated with currency codes, the system
stores a company currency code on the unit record. When you convert a
company to the euro, the conversion program converts the amount and
currency code in the AA ledger along with the currency code in the
corresponding AU ledger. It does this so that after converting a company,
both the AA and AU ledgers reflect the new company currency in the
Account Balances table (F0902).
XA, YA, ZA Ledgers and Detailed Restatement Records
Although the euro conversion programs do not convert amounts in the XA, YA,
and ZA ledgers, they update the following fields on the detailed restatement
records:
• Exchange rate field (GLCRR) with the calculated rate

• Historical exchange rate field (GLHCRR) with the calculated rate, only if it
contains an override rate
The euro conversion programs update the exchange rates because the XA, YA,
and ZA ledgers are based on the AA ledger, which is converted to the euro.
For information about how the euro conversion handles detailed currency
restatement records, see Alternate Ledger Amounts.
Differences Between the Workbench and Post-Conversion Jobs
The euro conversion workbench and the post-conversion (ordered and additional
conversion) jobs are similar in that they convert transaction amounts to the euro;
however, they are different in many other ways. The differences are described in
the following table:

12
Euro Conversion Workbench Post-Conversion Jobs
The Euro Planner/Workbench is The ordered conversion jobs are accessed from
accessed from the Setup and menu G97UE90 and the additional conversion
Conversion menu (G97UE9A). jobs are accessed from menu G97UE901.
Consists of jobs that the user loads into Consists of ordered and additional conversion
the workbench when setting up a plan. jobs that the user runs after successfully running
These jobs are launched when the user the Euro Conversion Workbench.
runs the Euro Conversion Workbench.
Converts amounts on records that have Converts amounts on records that do not have a
a company, business unit, or currency company, business unit, or currency code. The
code, which determines the base user must determine which records to convert
company currency on the record. using data selection.
User runs Euro Conversion User can run a post-conversion job multiple
Workbench one time for a plan. times for a plan, converting different data each
time as specified in the data selection.
For each conversion job in the For each ordered or additional conversion job,
workbench, converts all records in the converts certain records in the associated table
associated tables. based on the data selection you enter.
Retrieves conversion rate from the Depending on the ordered or additional

Currency Exchange Rates table conversion job, retrieves conversion rates from
(F0015). one of the following:
This rate is entered in the Exchange • Conversion Constants table (F0087). This
Rate field on the Set Daily Transactions rate is entered in the Exchange Rate field
Rate form (menu G11). It is set up on the Conversion Constants form (menu
once and never changed. G97UE9A) and can be changed to
coincide with the records being converted.
• Currency Exchange Rates table (F0015).

This rate is entered in the Exchange Rate
field on the Set Daily Transaction Rates
form (menu G11) and cannot be changed.
All post-conversion jobs, except Multi-Currency
Intercompany Conversion and Price Variable
Conversion, retrieve rates from the Conversion
Constants table. The Multi-Currency
Intercompany Conversion and Price Variable
Conversion jobs retrieve rates from the
Currency Exchange Rates table, based on the
companies being converted in the plan.

13
The Euro Conversion and Non-JDE Records
The euro conversion programs convert records that are created and maintained
using J.D. Edwards OneWorld software. They do not convert non-JDE records
entered through custom programs or third party software unless required fields
and tables are identical to those of J.D. Edwards software. The following example
illustrates this.
To avoid rounding issues, the R894301E and R8943121E conversion programs

calculate new unit costs by converting records based on unit of measure (UOM).
The following UOM fields must be populated for the conversion to run
successfully:
• Transaction (PDUOM) and purchase order (PDUOM3) - F4311

• Transaction (PRUOM0) and purchase order (PRUOM3) - F43121
These four UOM fields are required fields in J.D. Edwards software. If you have
non-JDE records, the R894301E and R8943121E conversion programs will not
convert them unless these four UOM fields are populated before you run the
conversion.
To help you research and determine which fields must be populated in non-JDE
records in order to run a specific conversion program, do the following:
• Enter a JDE record and compare that record to a non-JDE record. For
example, enter a sales order in the J.D. Edwards Sales Order Management
system and compare the fields that are populated on that record to the fields
that are populated on the non-JDE record. This should help you quickly
identify the required fields in a table so that you can populate those fields on
the non-JDE record and run the conversion program.
• Review the documentation that describes the fields that are required for
processing batches and electronic data interchange (EDI) transactions.
• For batch processing, see the Accounts Receivable, Accounts Payable,
General Accounting, and Sales Order Management Guides
• For EDI processing, see the Electronic Commerce Guide
These guides include information about which fields and tables must
contain data for a non-JDE record to get uploaded into your J.D. Edwards
tables. This information should help you identify the required fields in a
table so that you can populate those fields on the non-JDE record.

14
Coexistence and the Euro Conversion
Clients with coexistence run both WorldSoftware and OneWorld applications

while accessing the same database. The exceptions to this are the applications for
Accounts Receivable (systems 03 and 03B) and, as of OneWorld Xe, Service
Billing (systems 48 and 48S). The A/R and Service Billing applications have
different databases and, therefore, do not coexist.
For the euro conversion, clients with coexistence must be at the following software
release levels:
• WorldSoftware release A7.3 CU9 (or above)

• OneWorld B73.3.1 (or above)
Clients with coexistence should carefully consider whether to run the conversion
programs in WorldSoftware, OneWorld, or a combination of both.
• For applications that are coexistent (share the same database), clients can
run the conversion programs in either WorldSoftware or OneWorld.
One of the advantages to running the conversion programs in
WorldSoftware is that the programs typically process more quickly, whereas
one of the advantages to running them in OneWorld is that the software for
the conversion programs takes less time to install.
• For applications that are not coexistent (Accounts Receivable and Service
Billing), clients must run the conversion programs over the database in
which the tables for that application reside.
Coexistence: Steps for Converting to the Euro

The following describes, at a high level, the steps involved when converting a
company base currency to the euro:
1. Complete all pre-conversion tasks for Accounts Receivable and Service

Billing in the application (WorldSoftware or OneWorld) implemented at your
site.
2. Complete all other pre-conversion tasks in either WorldSoftware or
OneWorld, or a combination of both.

15
3. Run the euro conversion in WorldSoftware or OneWorld, depending on

which database is appropriate for the tables you are converting.
Example
The following describes one approach to running the euro conversion in a
coexistent environment with OneWorld A/R:
• Run the conversion programs in WorldSoftware, converting data in
all tables that coexist.
• Back up the converted F0018 table before continuing. If the F03B11
conversion fails, you will need to restore this table.
• Run the A/R conversion programs in OneWorld, converting data in
the A/R tables that do not coexist.
4. Run all ordered conversion jobs, except Multi-Currency Intercompany Post,

in either WorldSoftware or OneWorld before running the Company Currency
Codes Conversion job. The Company Currency Codes job converts the
company currency code and updates the decimal places in the Company
Constants table (F0010).
Caution
You must run the Multi-Currency Intercompany Post after you run the
Company Currency Codes Conversion job. If you do not, the post will
create entries based on the old base currency instead of the new base
currency (euro).
5. Run all additional conversion jobs in either WorldSoftware or OneWorld.

6. Complete all post-conversion tasks for Accounts Receivable and Service
Billing in the application (WorldSoftware or OneWorld) implemented at your
site.
7. Complete all other post-conversion tasks in either WorldSoftware or
OneWorld, or a combination of both.

16
F0911 Amounts Before and After the Euro Conversion
This topic describes how the euro conversion converts and updates various types
of transactions in the Account Ledger table (F0911). It also includes examples of
transactions before and after the conversion.
Topics
G Domestic and Foreign Ledger Amounts
G Alternate Ledger Amounts
Domestic and Foreign Ledger Amounts
This topic describes how the euro conversion handles domestic (AA) and foreign
(CA) ledger amounts in the Account Ledger table (F0911).
To understand how the euro conversion converts and updates domestic and
foreign transactions in the F0911 table, review the examples of transactions before
and after the conversion. The examples are based on a Belgian franc company. To
convert the original domestic transactions to the euro, the divisor rate (Z) is used.
The exchange rate (BEF to EUR) is 40.3399 and is from the Currency Exchange
Rates table (F0015). The examples compare AA and CA ledger amounts in the
Account Ledger table (F0911) before and after the euro conversion.
After the euro conversion, the currency code in the CRCD field in the Account
Ledger table (F0911) does not change to the new base currency code. The CRCD
field retains the currency code of the original transaction. See Currency Code Values
for CRCD and CRCX Fields for more information.
Topics
G Domestic EMU Transaction
G Foreign EMU Transaction (before 1 January 1999)
G Foreign EMU Transaction (as of 1 January 1999)
G Foreign Euro Transaction
OneWorld B73.3.1, B73.3.2, and Xe (07/01) F0911 Amounts Before and After the Euro
Conversion 17
G Foreign Non-EMU Transaction
Domestic EMU Transaction
For a domestic-only transaction in an EMU currency, the conversion does the

following:
• Converts the original AA record to the euro, based on an EMU currency to

EUR rate in the F0015 table.
• Writes a CA record, which contains the original AA amount before the
conversion.
Example: Before and After the Euro Conversion

The following example shows a domestic-only transaction before and after the
conversion.
Ledger Before Conversion After Conversion
AA 1000 BEF 24.79 EUR

(1000 BEF/40.3399)
CA 1000 BEF
Note
For illustration purposes, this example shows currency codes before and after the
euro conversion. As you review the example, keep in mind that the conversion
does not change the actual currency code in the CRCD field, but instead retains
the currency code of the original transaction. For example, BEF does not change
to EUR in the CRCD field.
Foreign EMU Transaction (Before 1 January 1999)
For a foreign transaction in an EMU currency that was entered before 1 January
1999, the conversion does the following:

EUR rate in the F0015 table. (The original domestic amount is no longer
retained.)
Conversion 18
• Retains the original CA amount. However, because the euro fixed rate did
not exist before 1999 when the transaction was entered, the system changes
the rate on the record to a calculated rate instead of retaining the F0015 rate.

The following example shows a foreign EMU transaction before and after the
conversion. In this example, the transaction was entered before EMU exchange
rates were fixed to the euro. To derive the original domestic amount, the exchange
rate from the Currency Exchange Rates table was used. (2000 DEM x 20.6232 =
41246.40 BEF)
AA 41246.40 BEF 1022.47 EUR

(41246.40 BEF/40.3399)
CA 2000 DEM 2000 DEM

** Rate changes to 0.5112 (1022.47/2000)
** The conversion does not calculate a rate based on the F0015 table (which would
be 1/1.95583 = 0.5113). Instead, it calculates a rate of 0.5112, based on the EUR
(1022.47) and DEM (2000) amounts.
Note
Foreign EMU Transaction (As of 1 January 1999)
For a foreign transaction in an EMU currency that was entered after 1 January
1999, the conversion does the following:

retained.)
• Retains the original CA amount and exchange rate, since the transaction was
entered as of 1999 when the euro was effective.
Conversion 19

The following example shows a foreign EMU transaction before and after the
conversion. In this example, the transaction was entered after EMU exchange rates
were fixed to the euro. To derive the original domestic amount, triangulation was
used. (2000 DEM/1.95583 x 40.3399 = 41250.93 BEF)
AA 41250.93 BEF 1022.58 EUR

(41250.93 BEF/40.3399)
CA 2000 DEM 2000 DEM
Note
Foreign Euro Transaction
For a foreign transaction in the euro, the conversion does the following:
• Converts the original AA record to the euro, based on the EMU currency to
retained.)
• Deletes the original CA amount since the new AA amount is stated in the
euro.
Conversion 20

The following example shows a foreign euro transaction before and after the
conversion. To derive the original domestic amount, the exchange rate from the
Currency Exchange Rates table was used. (2000 EUR x 1.95583 = 3911.66 DEM)
AA 3911.66 DEM 2000 EUR

(3911.66 DEM/1.95583)
CA 2000 EUR Record deleted
Note
the currency code of the original transaction. For example, DEM does not change
Foreign Non-EMU Transaction
For a foreign transaction that is not in an EMU currency, the conversion does the
following:

retained.)
• Retains the original CA amount. However, the system changes the rate on
the record to a calculated rate instead of retaining the F0015 rate.
Conversion 21

The following example shows a foreign transaction that is not in an EMU currency
before and after the conversion. To derive the original domestic amount, the
exchange rate from the Currency Exchange Rates table was used. (200 USD x
34.2300 = 6846 BEF)
AA 6846 BEF 169.71 EUR

(6846 BEF/40.3399)
CA 200 USD 200 USD

Rate changes to 0.8486 (169.71/200)
Note
Alternate Ledger Amounts
This topic describes how the euro conversion handles alternate ledger (XA, YA,
and ZA) amounts in the Account Ledger table (F0911).
Conversion 22
The following illustration shows the alternate ledgers that are affected when
transactions are restated in another currency (detailed currency restatement):
To understand how the euro conversion converts and updates alternate currency
transactions in the F0911 table, review the examples of transactions before and
after the conversion. The examples are based on a French franc company. To
convert the original domestic transactions to the euro, the divisor rate (Z) is used.
The exchange rate (FRF to EUR) is 6.55957 and is from the Currency Exchange
Rates table (F0015). The examples show AA and CA ledger amounts in the
Account Ledger table (F0911), as well as the corresponding XA, YA, and ZA
amounts before and after the euro conversion.
After the euro conversion, the currency code in the CRCD field in the Account
Ledger table (F0911) does not change to the new base currency code. The CRCD
field retains the currency code of the original transaction. See Currency Code Values
for CRCD and CRCX Fields for more information.
Topics
G Domestic-Only Transaction
G Euro Foreign Transaction
G Non-EMU Foreign Transaction
Domestic-Only Transaction
For a domestic-only transaction in an EMU currency, the euro conversion does the
following:
Conversion 23
• Converts the original AA record to the euro.

• Writes a CA record, which contains the original AA record amount before
the conversion.
• Retains the original XA amount. However, the system changes the rate on
the record to a calculated rate between the converted AA amount and the
XA amount.
• Deletes the YA ledger record.
• Writes a ZA ledger record, which is based on the XA amount and calculated
rate.
Example: Before and After Conversion

The following example shows records before and after the conversion for a
domestic-only transaction.
AA 3000 FRF 457.35 EUR
CA No record 3000 FRF
XA 894.49 DEM 894.49 DEM

Rate changes to 0.5113 (457.35/894.49)
YA 3000 FRF Deletes record
ZA No record 457.35 EUR
Note
the currency code of the original transaction. For example, FRF does not change
Euro Foreign Transaction
For a foreign transaction in the euro, the conversion does the following:
Conversion 24
• Retains the original CA (euro) amount.

XA amount.
• Deletes the ZA ledger record.
• Writes a YA ledger record, which is based on the AA amount and calculated
rate.

foreign transaction in the euro.
AA 3,280 FRF 500.03 EUR
CA 500 EUR 500 EUR
XA 500 EUR 500 EUR

Rate changes to 1.00006 (500.03/500)
YA No record 500 EUR
ZA 500 EUR Deletes record
Note
the currency code of the original transaction. For example, FRF does not change
Non-EMU Foreign Transaction
For a foreign transaction that is not in the euro, the conversion does the following:
Conversion 25
• Retains the original CA amount. However, the system changes the rate on
CA amount.
XA amount.
• Retains the original ZA amount. However, the system changes the rate on
ZA amount. This rate is the same as the AA to XA rate.

foreign transaction that is not in the euro.
AA 4453.68 DEM 2277.13 EUR
CA 2000 USD 2000 USD

Rate changes to 1.138565 (2277.13/2000)
XA 14937 FRF 14937 FRF

Rate changes to 0.152449 (2277.13/14937)
YA No record No record
ZA 14937 FRF 14937 FRF

Rate changes to 0.152449 (2277.13/14937)
Note
the currency code of the original transaction. For example, DEM does not change
Conversion 26
Pre-Conversion Tasks
OneWorld B73.3.1, B73.3.2, and Xe (07/01)

27
Planning a Euro Conversion Strategy
Some companies have already converted their base currency to the euro, while
others are in the process of converting to the euro, and still others have not yet
begun. The deadline for all EMU countries except Greece is 31 December 2001.
In the weeks and months prior to converting to the euro, companies should begin
carefully planning their euro conversion strategy. Unlike other J.D. Edwards
conversions, the euro conversion requires a company-wide effort by application
and system administrators before, during, and after the conversion. Our research
indicates that, depending on the size of a company's database, it can take from
three to nine months to complete the euro conversion process.
Topics
G Establishing a Euro Conversion Project Team
G Example: One Approach to the Euro Conversion
Establishing a Euro Conversion Project Team
Many companies will establish a conversion project team consisting of a project

team leader, application administrators, system administrators, end users, IT
personnel, and so on. The project team defines the scope of the conversion and
creates a project plan that will ensure a successful conversion. The project team
should set up a method to track the progress of the project, making sure that issues
are handled in a timely manner and that the project stays on schedule and within
budget.
The conversion project team is responsible for running and testing the euro
conversion in a test environment before running it in the production environment.
First, the project team will complete the pre-conversion, conversion, and post-
conversion tasks in a test environment, correcting any data issues in both the test
and production environments. Later, when the team is satisfied with the results of
the conversion in the test environment, they will complete all of the tasks again in
the production environment and "go live."
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Planning a Euro Conversion Strategy

28
Prior to running the euro conversion, the project team should review and complete
the pre-conversion tasks documented in this workbook. The pre-conversion tasks
can take weeks, or even months, to complete. If you clean up your tables and
review and correct your integrity reports on a regular basis, you can expect to
spend less time completing the pre-conversion tasks.
After running the euro conversion, the project team should review and complete
the post-conversion tasks documented in this workbook.
The following is a list of some suggested project team tasks. Use this list to
generate discussion within your company and help you plan your euro conversion
strategy:
G Set up project objectives, scope, assumptions, resources, roles, and

responsibilities.
G Define the skills required by the project team and assign people to the team.
G List the milestones and target dates for the project.
G Plan a reporting method to keep management informed of progress.
G Schedule a kick-off meeting to discuss and finalize the project plan.
G Create an issues list. Include risks, questions, concerns, and so on, and
assign a project person to each issue.
Throughout the euro conversion, the project team should review and update the
project plan, track the progress of the conversion, and identify and resolve issues.
Example: One Approach to the Euro Conversion
There are many ways to approach converting your company's base currency to the
euro. Each company is unique and has its own internal business requirements.
Many manufacturing companies, for example, might choose to convert to the euro
during an off-peak season or holiday when disruptions are less notable, whereas
other companies might choose to convert at the beginning of a fiscal or calendar
year. You will want to discuss the euro conversion with your auditors and base
your decision on your business requirements and any legal requirements.
The following is an example of how you might approach converting to the euro at
the beginning of a calendar year. Use this example to generate discussion within
your company and help determine the conversion strategy that will work best.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Planning a Euro Conversion Strategy

29
A German company has decided to begin the new calendar year in the euro instead
of its base currency, the German mark (DEM). It will use the following approach
to convert to the euro as of 1 January 2001:
1. Complete entering year 2000 entries between 31 December 2000 and 9

January 2001 in the base currency (DEM).
2. Limit the number of year 2001 transactions entered during those 10 days.
3. On 10 January 2001, copy the production environment. This copy is the audit
trail for 2000 and prior years’ books.
If auditor adjustments are required for year 2000, enter them in both the
copy of the production environment (step 3) and the production
environment (step 4).
4. Convert the production environment to the euro as of 10 January 2001.
5. Enter transactions for year 2001 in the production environment, using 1
January 2001 as the start date for the transactions.

30
Setting Up a Euro Conversion Test Environment
To help ensure the success of your euro conversion, complete the pre-conversion,
conversion, and post-conversion tasks in a test environment before you complete
them in your production environment. J.D. Edwards provides the following
environments, which can be used for euro conversion testing:
• Conference Room Pilot (CRPxxx, where xxx = release, for example,

CRP733)
• Testing (TSTxxx, where xxx = release, for example TST733)
Verify that one of these environments is installed at your site and use it for your
euro testing. By running and completing the euro conversion in one of these test
environments, you can continue to run your daily operations in your production
environment while preparing for the euro conversion in a test environment.
Companies with multiple environments should test the euro conversion separately
for each environment.
Your test environment should contain a copy of the most current production data.
Make sure you refresh your test environment from your production environment
before you begin testing the euro conversion.
Complete the pre-conversion, conversion, and post-conversion tasks on all data in

your test environment. If you test only a portion of the data, your results will be
incomplete and will not apply to the actual conversion in your production
environment. Remember that you must correct any data issues identified in your
test environment in both your test and production environments.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Setting Up a Euro Conversion Test Environment
31
Caution
If you choose not to complete the pre-conversion, conversion, and post-
conversion tasks first in a test environment and instead complete them in your
production environment, be aware that J.D. Edwards will not support or help
ensure the success of your euro conversion. The risks involved in converting your
production environment without first preparing and testing the conversion in a test
environment are consequential to the operation of your company. The potential
risk for downtime, hastily made decisions, and incorrect converted data must be
taken very seriously.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Setting Up a Euro Conversion Test Environment
32
Reviewing Sizing Impacts and System Resources
Review the information about sizing impacts and system resources and use it as a
guideline to help you determine the size and disk space requirements needed for
your company's euro conversion. If you have concerns about sizing impacts and
system resources and performance, contact your hardware representative.
For additional information, see Hardware and Software Requirements in the OneWorld
Installation Guide or the OneWorld Upgrade Guide.
Topics
G Sizing Impacts
G System Resources and Performance
Sizing Impacts
To determine the sizing impacts that the euro conversion will have on your system,
it is important to understand how the euro conversion processes and converts
data. The euro conversion converts amounts on records in the base currency only.
In addition, it does the following:
• Creates a CA record for domestic-only transactions in the F0911 and F0902

tables. See Sizing Impacts on the F0911 and F0902 Tables.
• Optionally (based on user preference), creates records in the Audit Record
table (F0086) for the converted amounts. See Sizing Impacts on the F0086
Table.
Topics
G Sizing Impacts on the F0911 and F0902 Tables
G Sizing Impacts on the F0086 Table
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Reviewing Sizing Impacts and System Resources
33
Sizing Impacts on the F0911 and F0902 Tables
For companies with domestic-only transactions, the euro conversion has a sizing
impact on the F0911 and F0902 tables. Domestic-only transactions do not contain
a foreign amount and, therefore, do not have a corresponding CA record. If a CA
record does not exist in the F0911 and F0902 tables, the euro conversion creates
one based on the AA record. If your company has a large number of domestic-
only transactions, this will impact the size of your tables. For example, if your
company has domestic-only transactions, you can expect the number of records in
the F0911 to double after running the conversion and the records in the F0902
table to double after running the Repost.
Use the following formulas to calculate sizing impacts:
• Sizing impact on F0911 table = (number of domestic-only transaction

records x F0911 table size) + F0911 table size before conversion
• Sizing impact on F0902 table = (number of domestic-only balance records x
F0902 table size) + F0902 table size before conversion
The number of domestic-only records = total of AA total of records - CA records.
Sizing Impacts on the F0086 Table
Before running the euro conversion, you specify whether you want the conversion
to create an audit record in the Audit Record table (F0086) for a particular table
conversion. At a minimum, the conversion creates one record for each record
converted.
Caution
The ZJDE model plan that you copy and use as the basis for your plan was
specifically designed to create audit records for each table converted. Although
creating audit records is recommended, clients must be aware that doing so can
impact processing time greatly and requires additional disk space.
There are eight "to" and "from" amount fields in the F0086 table. If the amount
fields on a record exceed that number, the conversion creates additional audit
records. For example, the F0902 record has 22 amount fields. This means the euro
conversion creates three F0086 records for each F0902 record it converts.
34
The euro conversion creates multiple F0086 records for the following tables:
Financials Sales Order Procurement

Management
F03B11 - 2 records F4211 - 2 records F4311 - 3 records
F03B14 - 2 records F4211 - 2 records F4311 - 3 records
F0411 - 2 records F42199 - 6 records F43121 - 2 records
F47037 - 2 records F47042 - 3 records
F47097 - 3 records
F47102 - 3 records
Use the following formula to calculate sizing impacts:
Sizing impact on F0086 table = number of records to be converted for a

particular table x (F0086 table size x number of F0086 records written per
converted record)
System Resources and Performance
Based on the way in which the euro conversion processes and converts data, it is
important that you clean up your tables and, as much as possible, remove detailed
records before running the conversion. (Pay particular attention to the size of your
F0911 and F0902 tables.) By doing so, the conversion programs will use less disk
space, which will improve processing time.
35
When you run the conversion in your test environment, use the performance
monitor provided by your operating system vendor to get an idea of what to
expect for system resources and performance. The performance monitor allows
you to track CPU processing, amount of I/O, and memory consumption and
should help indicate what you can expect for system resources and performance
when you run the conversion in your production environment.
The following example shows the number of records in several tables before and
after the conversion. Use this as an example only, as actual results will vary.
Table Before After
F0911 43,656 50,342
F0311 1,247 same
F0411 889 same
F0902 19,985 21,308
F1301 46 same
F3102 12,162 same
F4201 818 same
F4211 2,004 same
F4111 14,302 same
F4229 182 same
F4812 36 same
Total 3,091,456 3,124,224
36
Euro Conversion Software Requirements
Before you begin the euro conversion process and the tasks described in this
workbook, your software must be updated to a specific OneWorld release and, if
applicable, an application software update (ASU) and electronic software updates
(ESUs).
For detailed and up-to-date information about the euro conversion software for
releases B73.3.1, B73.3.2, and Xe, visit the Euro Knowledge Garden site. The path
is Worldwide Topics > Euro Base Currency Conversion > Software >
Requirements.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Euro Conversion Software Requirements

37
Copying Tables to Your Conversion Environment
OneWorld B73.3.1 and B73.3.2

This task applies to OneWorld B73.3.1 and B73.3.2 clients only. It describes tables
that already exist in the conversion environment in OneWorld Xe and, therefore,
does not apply to Xe clients.
Clients who have installed B73.3.1EURO or B73.3.2EURO must copy two tables
from their deployment server to the environment in which they will run the euro
conversion. The tables are the Audit Record (F0085) and Table Conversion JDE
Scheduler (F9843).
The F0085 and F9843 tables must exist in your conversion environment before
you can proceed to the task Setting Up a Euro Conversion Plan. The tables contain
data records that are necessary to set up and run a euro conversion plan.
Remember that you must complete this tasks and all remaining tasks in this
workbook first in your test environment, correcting any data issues in both your
test and production environments. Later, when you are satisfied with the results of
the euro conversion in your test environment, complete all the tasks again in your
production environment and "go live."
Before You Begin

G Ensure that you have Microsoft Access 97 installed. The procedures for
copying tables to your conversion environment are not compatible with
Microsoft Access 2000.
Topics
G Copying the F0085 Table to Your Conversion Environment
G Copying the F9843 Table to Your Conversion Environment
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Copying Tables to Your Conversion Environment
38
Copying the F0085 Table to Your Conversion Environment
The following applies to OneWorld B73.3.1 and B73.3.2 only. For OneWorld Xe,
the F0085 table is already in the conversion environment.
The Audit Record table (F0085) contains the ZJDE plan, which is a list of all the
tables converted by the euro conversion. You will use the ZJDE plan as a model
for any conversion plans in which you do not want to create audit records.
► To copy the F0085 table to your conversion environment
1. Log into DEP733 on your deployment server.
2. Type OL in the Fast Path field to access Object Librarian.
3. On Work with Object Librarian, enter F0085 in the Name field and click
Find.
4. With the row highlighted, click Select.
39
5. On Table Design Aid, select the environment (Path Code) in which you will
run the euro conversion.
6. From the Form menu, choose Copy Table.
40
7. Verify that the Source - Data Source field contains one of the following
values:
• For B73.3.1, OneWorld Local

• For B73.3.2, OneWorld SU - B7332EURO
This is the environment where the F0085 table currently resides.
8. In the Destination - Data Source field, click the flashlight and select
Business Data - PROD from the list of values.
Business Data - PROD is the default data source for the object type tables.
If the default data source was changed after applying the ASU, you will need
to select the corresponding data source from the list of values.
9. Tab until your cursor is in the Password field.
10. Enter the password.
The default password is the same value as the Object Owner ID (previous
field). If the object owner changed the password after applying the ASU,
you will need to enter that password.
11. Click OK to copy the F0085 table to your conversion environment.
12. Upon completion, click OK in the Copy Successful window.
13. Click Cancel two times to return to Work with Object Librarian.
41
Copying the F9843 Table to Your Conversion Environment
The following applies to OneWorld B73.3.1 and B73.3.2 only. For OneWorld Xe,
the F9843 table is already in the conversion environment.
The Table Conversion JDE Scheduler table (F9843) contains the data records for
the conversion UBEs (type 8) that are necessary to run the euro conversion, as
well as other types of programs. When you copy the F9843 table to your
conversion environment, you cannot selectively copy the type 8 records. You must
copy the contents of the entire table. The additional (non-type 8) records will have
no impact on your euro conversion.
► To copy the F9843 table to your conversion environment
1. Log into DEP733 on your deployment server.
2. Type OL in the Fast Path field to access Object Librarian.
3. On Work with Object Librarian, enter F9843 in the Name field and click
Find.
4. With the row highlighted, click Select.
42
5. On Table Design Aid, select the environment (Path Code) in which you will
run the euro conversion.
6. From the Form menu, choose Copy Table.
7. Change the Source - Data Source field from System - B733 (default value) to
one of the following:
• For B73.3.1, OneWorld Local

• For B73.3.2, OneWorld SU - B7332EURO
8. In the Destination - Data Source field, click the flashlight and select System
- B733.
43
9. Tab until your cursor is in the Password field.
10. Enter the password.
The default password is the same value as the Object Owner ID (previous
field). If the object owner changed the password after applying the ASU,
you will need to enter that password.
11. Click OK to copy the F9843 table to your conversion environment.
12. Upon completion, click OK in the Copy Successful window.
13. Click Cancel two times, and then Close to exit Object Librarian.
44
Creating Indices Before Running the Conversion
When processing records, many of the euro conversion programs use data
selection and data sequencing that do not have existing indices. If conversion
programs cannot find indices, they try to build them. This takes an inordinate
amount of processing time and causes serious performance problems.
The euro conversion programs process millions of records, making performance a

critical issue. By creating indices before running the euro conversion, you can help
improve the time it takes to process records.
► To create indices before running the conversion
Determine whether indices have already been created for some of the tables you
are going to convert.
1. Create an index for each table that you are going to convert.
2. Update statistics to run the maintenance program that is required for your
database.
3. Run the euro conversion.
4. Delete the indices.
Your database determines whether you use the 'Where' or 'Order By' clause to
create an index. See OneWorld Indices for a list of know clauses and corresponding
tables and UBEs.
Caution
OneWorld guidelines recommend that a qualified database administrator be
present when the databases are configured and maintained for use with OneWorld.
The database administrator must understand how to maintain the OneWord
database, including indices.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Creating Indices Before Running the Conversion
45
Completing System-Level Prerequisites
This task consists of a checklist and description of the system-level prerequisites

that you must complete before you run the euro conversion. The checklist has two
check-off (√) columns - one for your test (TEST) environment and the other for
your production (PROD) environment.
Remember that you must complete the system-level prerequisites and all remaining
tasks first in your test environment, correcting any data issues in both your test and
production environments. Later, when you are satisfied with the results of the euro
conversion in your test environment, complete all of the tasks again in your
Checklist: System-Level Prerequisites
Prerequisite Description TEST PROD

√ √
Install the For a complete list of the releases, application software updates
appropriate euro (ASUs) and electronic software updates (ESUs) that are needed
releases, ASUs, to convert your company's base currency to the euro, visit the
and ESUs Euro Base Currency Conversion site on the Knowledge
Garden. The path is Worldwide Topics > Euro Base Currency
Conversion > Software > Requirements.
Correct any Ensure that you have corrected all Y2K data-related issues in
remaining Year all your J.D. Edwards tables and systems. See Year 2000 on the
2000 (Y2K) data Knowledge Garden. The path is Worldwide Topics > Year
issues 2000.
If data issues are not corrected before the conversion, they will
intensify as a result of the conversion and make the issues
more difficult to troubleshoot and correct.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Completing System-Level Prerequisites

46

√ √
Install the Multi- Required for clients who have not installed system 11.
Currency system
(11)
Activate Required for clients who have not activated multicurrency.

multicurrency See the Multi-Currency Guide for detailed information about
how to activate multicurrency and run the multicurrency
update programs.
Update currency For new multicurrency clients only. Transactions with blank
code fields that currency codes are not converted during the euro
contain a blank conversion. To assign a currency code to transactions with
a blank currency code field, run the following programs:
• Load Domestic Currency Code - G/L to populate the

CRCD fields in the F0911 table
• Account Ledger Repost to populate the CRCX and

CRCD (monetary accounts only) fields in the F0902
table
See Currency Code Values for CRCD and CRCX Fields.
Compile a list of the The euro conversion programs and many of the pre-
J.D. Edwards conversion and post-conversion tasks apply to specific
systems that you use systems. Determine which J.D. Edwards systems you use.
This allows you to save time by running the euro
conversion programs and by completing pre-conversion
and post-conversion tasks, such as running integrities and
purging data, for your systems only.
For clients with coexistence, compile a list of both the
WorldSoftware and OneWorld systems you use.

47

√ √
Compile a list of Determine which companies you are going to convert to

companies that you the euro. You convert companies by environment. Within
plan to convert to an environment, you can convert individual companies one
the euro at a time, multiple companies with the same base currency
at the same time, or multiple companies with different base
currencies at the same time.
Multicurrency intercompany settlements: You do not
have to convert companies that are involved in
multicurrency intercompany transactions in the same plan
or at the same time. However, you must convert all
companies in all plans before you run the Multi-Currency
Intercompany Conversion and the Intercompany Post,
which make the necessary adjustments and keep the
multicurrency intercompany transactions in balance. See
Multicurrency Intercompany in Checklist: Ordered Conversion Jobs.
Determine the Consult with your Finance and Administration department

amount of historical to determine how many years of historical data to convert
data to convert to to the euro. This will depend on your company audit
the euro requirements, local government requirements, and any disk
space considerations. Some companies will convert one or
two years of historical data, while others will convert
opening balances only.
The European Union suggests converting no more than
two years of historical data to the euro. Clients who convert
their base currency to the euro as of 1 January 1999 might
choose not to convert two years of historical data, since the
amounts would be based on a currency and exchange rate
that did not officially exist. If you choose to convert
transactions dated prior to 1999, you must set up exchange
rates for the euro with an effective date prior to 1999. This
is described in Checklist: Financials Pre-Conversion Tasks.
Remember to archive any historical data that is needed for
fiscal audit reporting purposes.

48

√ √
Compile a list of The euro conversion programs convert records that are
custom programs created and maintained using J.D. Edwards OneWorld
and third party software. They do not convert non-JDE records entered
software used at through custom programs or third party software, unless
your site required fields and tables are identical to those of J.D.
Edwards software.
To convert non-JDE records using a specific J.D. Edwards
conversion program, clients must research and determine
which fields in their non-JDE records need to be populated.
For more information, see The Euro Conversion and Non-JDE
Records.
Identify which (Optional) Identify the currency amounts that the euro
currency amounts conversion will round to zero. This includes currency
will round to zero amounts of 1 Portuguese escudo (1/200.482 = 0.0049), less
after the euro than 10 Italian lire (9/1936.27 = 0.0046), and so on. To
conversion identify these amounts, create and run a query or UBE over
the tables in the J.D. Edwards systems that you use. See
Conversion and Post-Conversion Tables for a list of tables.
For example, if you use the Sales Order Management
system, create and run a query or UBE over the following:
• Cost Ledger (F4105) and Supplier/Catalog Price

(F41061) tables for cost records
• Base Price (F4106), Price Adjustment Detail (F4072),

and Price by Item (F4207) tables for price records
• Sales Order Detail (F4211) and Purchase Order Detail

(F4311) tables for transaction records
Amounts that round to zero appear as a warning on the
table conversion reports that are generated when you run
the euro conversion. By identifying these amounts before
the conversion, you can:
• Adjust amounts so that they do not round to zero.

(Alternatively, you can adjust zero amounts after the
conversion.)
• Quickly acknowledge warning messages on the table

conversion reports, saving valuable research time after
the conversion.
Summarize and See Purging Outdated Data Tables for more information.
purge outdated data
tables

49

√ √
Defragment tables (Optional) Prerequisite: Summarize and purge outdated data

and rebuild table tables. See Purging Outdated Data Tables for more
indices information.
After purging outdated data tables, defragment the affected
tables and rebuild the table indices. Contact your database
administrator for more information about this process.
Archive data tables Prerequisite: Summarize and purge outdated data tables. See
Purging Outdated Data Tables for more information.
Consult with your Finance and Administration department
to determine how many years of historical data to archive
for government legal requirements. Each EMU country has
specific requirements for fiscal reporting. Based on those
requirements, archive the following:
• All historical data that you do not want to convert or

purge
• Data tables that you do not need for comparison

purposes (before and after the euro conversion)
Be aware that you cannot restore archived data tables to
your production environment after the conversion. That is
because the conversion programs change your base
currency. You can, of course, restore archived tables to a
non-production environment.
Verify company On Company Names & Numbers (menu G09411), verify

currency the currency code of each company you are going to
convert. The currency code must be set to your current
base company currency (that is, the currency before the
conversion) for the conversion programs to run.
Compile a list of Compile a list of any special circumstances you want to

special monitor. Use the list to verify results after the conversion.
circumstances

50
Currency Code Values for CRCD and CRCX Fields
Before running the euro conversion, verify that the CRCD and CRCX currency
code fields contain accurate values. This ensures that when you convert your base
currency to the euro, you convert all amounts and that the amounts you convert
are assigned an accurate currency code. The euro conversion does not convert
amounts with a blank currency code.
Example: Currency Code Values for CRCD and CRCX Fields

Use the following example to verify that the currency code fields in your tables
contain accurate values.
This example is based on a Belgian franc company with the following:
Base Transactions Monetary Currency-Specific

Currency Account Ledgers (09/LT)
BEF DEM USD XA (Detail) = USD
FRF AC (Balance) = USD
ITL
Currency code values for CRCD, CRCX, or both are stored in the following tables:
• Company Constants (F0010)

• Account Master (F0901)
• Account Ledger (F0911)
• Account Balances (F0902)
These tables and associated currency code fields are described below.
Company Constants (F0010)

In this table, the currency code field is CCxxxx, where xxxx equals:
• CRCD = company currency

• CRCX = not applicable (field does not exist in table)

51
Company CRCD CRCX
Belgian BEF Not applicable
Account Master (F0901)

In this table, the currency code field is GMxxxx, where xxxx equals:
• CRCD = blank (if a nonmonetary account) and xxx (xxx = currency code
assigned to monetary account)
Accounts CRCD CRCX
Nonmonetary Blank Not applicable

Accounts
Monetary USD Not applicable

Accounts
Account Ledger (F0911)

In this table, the currency code field is GLxxxx, where xxxx equals:
• CRCD = transaction currency (AA and CA ledgers)

Transaction Ledger CRCD CRCX
BEF AA BEF Not applicable
DEM AA DEM Not applicable

CA DEM Not applicable
FRF AA FRF Not applicable

CA FRF Not applicable
ITL AA ITL Not applicable

CA ITL Not applicable

52
Account Balances (F0902)

In this table, the currency code field is GBxxxx, where xxxx equals:
Simple Method
• CRCD = blank
• CRCX = company currency (AA and CA ledgers)
BEF, DEM, FRF, or ITL AA Blank BEF
BEF, DEM, FRF, or ITL CA Blank BEF
BEF, DEM, FRF, or ITL BA Blank BEF
Alternate Ledgers (09/LT)
• CRCD = blank
• CRCX = currency specified for alternate ledger in UDC 09/LT (Special
Handling Code field)
BEF, DEM, FRF, or ITL AC Blank USD
BEF, DEM, FRF, or ITL XA Blank USD
Monetary Accounts
• CRCD = currency assigned to monetary account in F0901. (For release

B73.3.1 only, the transaction currency must be the same as the monetary
account currency except for JX entries, which are the base company
currency.)
• CRCX = company currency (AA ledger) and monetary account currency
(CA ledger).
BEF, DEM, FRF, or ITL AA USD BEF
BEF, DEM, FRF, or ITL CA USD USD
Balance by Currency

53
• CRCD = transaction currency

• CRCX = company currency (AA ledger) and transaction currency (CA
ledger)
BEF AA BEF BEF
DEM AA DEM BEF

CA DEM DEM
FRF AA FRF BEF

CA FRF FRF
ITL AA ITL BEF

CA ITL ITL

54
Completing Pre-Conversion Tasks
This task consists of a checklist and description of the pre-conversion tasks that
you must complete before you run the euro conversion. The checklist has two
check-off (√) columns - one for your test (TEST) environment and the other for
your production (PROD) environment.
The conversion programs convert records in all batches, regardless of their status.
This means that posted batches, as well as batches in error and unposted batches,
are converted. Before you run the euro conversion, make sure you process and
update all transactions and ensure that your data is as clean as possible.
Complete only those pre-conversion tasks that apply to the J.D. Edwards
programs and systems that you use. For example, if you do not use localization
programs, do not complete the pre-conversion tasks for Localization. Similarly, if
you do not use bank statement processing, do not complete the two pre-
conversion tasks for reconciliation listed under General Accounting.
Remember that you must complete the pre-conversion tasks and all remaining
tasks first in your test environment, correcting any data issues in both your test and
production environments. Later, when you are satisfied with the results of the euro
conversion in your test environment, complete all of the tasks again in your
Topics
G Checklist: Financials Pre-Conversion Tasks
G Checklist: Distribution Pre-Conversion Tasks
G Checklist: Manufacturing Pre-Conversion Tasks
G Checklist: Final Post
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Completing Pre-Conversion Tasks

55
Checklist: Financials Pre-Conversion Tasks
Accounts Receivable
Pre-Conversion Task Description TEST PROD

√ √
Determine whether to To reduce the processing time when converting your

run multiple versions of A/R records to the euro, you can run multiple versions
the A/R conversion of the A/R conversion programs from different
programs workstations.
For more information, visit the Euro Base Currency
Conversion site on the Knowledge Garden. The path is
Worldwide Topics > Euro Base Currency Conversion
> Global Support Services > OneWorld Knowledge
Documents > Application > Running Multiple
Versions of the A/R Conversion Programs.
Process all auto debit and Process all open batches of auto debits and A/R drafts
A/R draft transactions through to completion.
Process all batch invoices Upload all batch invoices to create records in the
Invoice Transactions Batch table (F03B11Z1), and then
process them to create transactions in the Customer
Ledger table (F03B11).
Complete all receipt Process all receipts through to completion.

processing
Convert customer Complete this task before or after the euro conversion.
currency codes and See Converting Customer Currencies and Amounts to the Euro
amounts (CRCD and in the Euro Implementation Guide.
CRCA)
The euro conversion workbench programs do not
convert the customer currency code (CRCD) or the
address book amount/currency (CRCA) in the
Customer Master table (F03B01).
Review a list of recurring The euro conversion workbench converts recurring

invoices invoices. Print a Recurring Invoice Report (R03B305),
accessed from menu G03B111, and review your open
recurring invoices. If you do not want to convert your
recurring invoices, delete them and, after the
conversion, enter new ones.

56

√ √
Close the fiscal period (Optional) The Update A/R from Address Book
for a company program (R03B802) updates amounts in the Customer
Master file (F03B01), based on the address book
amount/currency (CRCA).
The euro conversion programs do not convert these
amounts.
Calculate realized gains Complete this task before or after the conversion. The
and losses on non-EMU euro conversion programs do not affect the date and
currency transactions order in which you calculate gains and losses on non-
EMU currency transactions.
Note: EMU companies no longer calculate gains and
losses on transactions created between EMU
currencies. According to EU regulations, losses on
open invoices were to be realized at the end of 1998
and gains on open invoices were to be realized no later
than 31 December 1999.
Post all accounts Prerequisite: Post transactions from other systems,

receivable transactions to such as Sales Order Management, to the Accounts
the general ledger Receivable system before you post A/R transactions to
the general ledger. Run any update programs, such as
Sales Update.
Run all active batches through to completion and verify
the posting edit reports.
Accounts Payable

√ √
Process all A/P draft Process all open batches of A/P drafts through to
transactions completion.
Process all batch Upload all batch vouchers to create records in the
vouchers Voucher Transactions Batch table (F0411Z1), and then
process them to create transactions in the Accounts
Payable Ledger table (F0411).
Complete all payment Process all payments through to completion. Make sure
processing there are no active payment groups or workfiles. The
F04571, F04572, and F04573 tables should not contain
transactions.

57

√ √
Convert supplier master Complete this task before or after the euro conversion.
currency codes and See Converting Supplier Currencies and Amounts to the Euro
amounts (CRCD and in the Euro Implementation Guide.
CRCA)
The euro conversion workbench programs do not
convert the supplier currency code (CRCD) or the
address book amount/currency (CRCA) in the Supplier
Master table (F0401).
Review a list of recurring The euro conversion workbench converts recurring

vouchers vouchers. Print a Recurring Voucher Report (R04305),
accessed from menu G04111, and review your open
recurring vouchers. If you do not want to convert your
recurring vouchers, delete them and, after the
conversion, enter new ones.
Close the fiscal period (Optional) The Update YTD Voucher Amount
for a company program (R04820A) updates amounts in the Supplier
Master file (F0401), based on the address book
amount/currency (CRCA).
The euro conversion programs do not convert these
amounts.
Calculate realized gains Complete this task before or after the conversion. The
and losses on non-EMU euro conversion programs do not affect the date and
currency transactions order in which you calculate gains and losses on non-
EMU currency transactions.
Note: EMU companies no longer calculate gains and
losses on transactions created between EMU
currencies. According to EU regulations, losses on
open vouchers were to be realized at the end of 1998
and gains on open vouchers were to be realized no later
than 31 December 1999.
Post all accounts payable Prerequisite: Post transactions from other systems, such
transactions to the as Procurement, to the Accounts Payable system before
general ledger you post A/P transactions to the general ledger.
Run all active batches through to completion and verify
the posting edit reports.

58
General Accounting

√ √
Determine whether to run To reduce the processing time when converting your
multiple versions of the F0911 records to the euro, you can run multiple
F0911 conversion versions of the F0911 conversion program from
program different workstations.
For more information, visit the Euro Base Currency
Conversion site on the Knowledge Garden. The path
is Worldwide Topics > Euro Base Currency
Conversion > Global Support Services > OneWorld
Knowledge Documents > Application > Running
Multiple Versions of the F0911 Conversion Program.
Process all batch journal Upload all journal entry batch transactions to create
entries records in the Journal Entry Transactions Batch table
(F0911Z1), and then process them to create
transactions in the Account Ledger table (F0911).
Reconcile all bank Complete bank statement processing and

statements reconciliations for all companies that you are going to
convert to the euro.
Delete the Reconciliations The euro conversion does not convert records in the
Workfile (F0911R) Reconciliations Workfile (F0911R). Make sure you
delete the workfile before the conversion so that you
do not inadvertently try to reconcile unconverted
records after the conversion. (After the conversion,
you will regenerate the workfile so that the records are
based on the new euro amounts.)
Review a list of your The euro conversion does not convert model journal
model journal entries entry amounts in the Account Ledger table (F0911).
Review a list of your model journal entries and
determine whether you want to manually change them
after the conversion.
Run a query or UBE over the F0911 table for journal
entries with a posted code M (model). Review the list
and, after the conversion, revise the model journal
entries as needed.

59

√ √
Enter budget amounts in (Optional) Complete this task if you want the euro
your base currency for conversion programs to convert your BA ledger
the upcoming year amounts to the euro. The euro conversion programs
convert budget amounts in the BA ledger only.
The euro conversion programs do not convert
amounts in currency-specific ledgers. If you do not
want to convert your budget amounts, create a new
ledger type (for example, BX), assign a currency code
to the ledger, and enter your budget amounts. The
amounts will not be converted as long as the ledger has
a currency code assigned to it.
Run allocations (Optional) Complete allocations for the current period

or year, depending on when you run the euro
conversion.
Review a list of your The euro conversion does not convert amounts in the
allocations Cost Allocations/Flex Budgeting table (F0912). Review
a list of the recurring journal entries you have set up
for your allocations and determine whether you want
to manually change fixed amounts after the conversion.
Run a query or UBE over the F0912 table for journal
entries with a batch type D. Review the list and, after
the conversion, revise the recurring journal entries for
your allocations as needed.
Run the annual close Applies only to clients who run the euro conversion at
the end of a fiscal year.
J.D. Edwards recommends that you run your annual
close before you run the euro conversion. Advantages
to doing this include:
• The data you convert is likely to be "cleaner."

This is because most companies ensure that all
accounts are reconciled and balanced as part of
their regular year-end procedures. By running the
annual close before you run the conversion, you
should have less integrity issues to deal with after
the conversion.
• You can provide your auditors with year-end

reports in one currency instead of two currencies.

60

√ √
Complete fiscal date Applies only to clients who change a company's fiscal
pattern steps date pattern before running the euro conversion.
Make sure you complete all steps before you run the
conversion programs. The steps include running the
repost, annual close, and all integrity reports.
Retain records with a (Optional) If you want to retain records with a

company's domestic company's domestic currency amounts, restate your
amounts (if XA and AC domestic currency ledger to a currency-specific ledger
ledgers are not used) before you run the conversion. The amounts will not
be converted since amounts in currency-specific
ledgers, such as XA and AC, are not converted.
For example, a French company wants to be able to
view their original balances in the French franc after
the conversion. To do this, the company restates the
AA ledger to the AC ledger before the conversion. The
original domestic balances will reside in the AC ledger
and, after the conversion, the euro balances will reside
in the AA ledger.
J.D. Edwards recommends you run balance currency
restatement, instead of detailed restatement, to retain
your domestic currency amounts. If you run detailed
restatement, be aware that the size of your Account
Ledger table (F0911) will increase significantly. This
might create serious performance and disk space
problems during the euro conversion.

61

√ √
Set up currency To run the euro conversion programs, ensure that you
relationships for the euro have set up the following:
effective 1999 and later
• Currency code for the euro. See Setting Up a
Currency Code for the Euro in the Euro Implementation
Guide.
• EMU Member Setup table (00/EU). See Setting

Up EMU Member Currencies in the Euro
Implementation Guide.
• Conversion rates and relationships between

EMU currencies and the euro. See Setting Up No
Inverse Records and Setting Up Exchange Rate Records
in the Euro Implementation Guide.
You do not have to set up triangulation records to run
the euro conversion programs.
Note: On 1 January 2001, Greece joined the EMU.
Make sure you set up the conversion rate (1 EUR =
340.750 GRD) and add Greece to the EMU Member
Setup table.
Set up exchange rates for If your company plans to convert transactions dated
the euro prior to 1999 prior to 1999, you must set up exchange rates for
EMU currencies to the euro with an effective date
prior to 1999. For example, a German company that
wants to convert historical data for 1997 and 1998
must set up a DEM to EUR exchange rate of 1.95583
with an effective date of 01.01.97. The effective date
must include the G/L date of the oldest transaction.
Verify multicurrency If your business does not create multicurrency

intercompany transaction intercompany transactions, make sure the Allow Multi-
option in General Currency Intercompany Transaction option in General
Accounting Constants Accounting Constants is turned off. The conversion
takes longer to process if the constant is turned on.

62

√ √
Compile a list of batches Run the Batch to Detail and Out-of-Balance report
posted out of balance (R007031), accessed from menu G0922 and compile a
list of A/R, A/P, and G/L batches that were
intentionally posted out of balance. Use this list to
compare the results after the conversion.
The Batch to Detail and Out-of-Balance report shows
batches in which the Post Out of Balance and Include
Batch on Integrity flags are set to Y. To locate and
change the batches that are not included on integrity
reports (Include Batch on Integrity flag is set to N), see
Reviewing and Correcting Pre-Conversion Integrity Reports.
Post all journal entry Run all active batches through to completion and
transactions to the verify the posting edit reports.
general ledger
See Checklist: Final Post.
Run all financial reports Check with your auditors to find out which financial
reports are required.
Reports

√ √
Run Report Writer Run Report Writer reports for all companies that you
reports are going to convert to the euro. Use these reports to
compare pre-conversion amounts to post-conversion
results.
Localization

√ √
Post all transactions to Run all active batches through to completion and
the general ledger verify the posting edit reports.

63

√ √
Print the G/L For Italian clients only. Prerequisite: Post all
Registration Report transactions to the general ledger.
(R09404)
Print the G/L Registration Report (R09404), accessed
from menu G09315, to add registration numbers to
your journal entries. Review the registration numbers
and revise them, as necessary. The registration
numbers are an Italian legal requirement.
Print G/L legal reports For French clients who convert to the euro at fiscal
year-end.
For the closed fiscal year, run the following G/L legal
reports in final (update) mode: General Ledger, Trial
Balance, and General Journal. These reports are
accessed from menu G093151.
Determine whether If required, create Intrastat tax reports in your national

countries require Intrastat currency if it is the end of the calendar year and you
tax reports in a national are converting to the euro as of a new calendar year.
currency or the euro Remember to run Update Extra Tax file - Sales
(R0018I1) and Purchasing (R0018I2), accessed from
menu G00211, to update the Intrastat workfile
(F0018T).
After you convert to the euro, you can create Intrastat
tax reports in your national currency using the new as if
currency functionality in the processing options for the
Update Extra Tax file - Sales and Purchasing
programs. For more information, see Creating Intrastat
Reports in the Euro in the Euro Implementation Guide.
Fixed Assets/Job Cost

√ √
Run the annual close (Optional) Run the annual close. Make sure you also
run the depreciation schedule over your assets for the
year.
Post all transactions to Run all active batches through to completion and verify
the general ledger the posting edit reports.

64
Checklist: Distribution Pre-Conversion Tasks

√ √
Process all open and Complete this task to reduce the number of inbound
pending inbound and records in the EDI tables and help improve processing
outbound EDI time and performance during the euro conversion.
transactions
Process billing for Run end-of-day processing for Container Rental Billing
Container Management (R41186) and Container Deposit/Refund Billing
(R41187), accessed from menu G4118.
Identify orders that If you change the UOM conversion factor for items on
have items where the sales or purchase orders, you will get unexpected results
unit of measure (UOM) when you run the euro conversion. The results of the
conversion has changed conversion will be based on the new (changed) UOM
factor, not the original factor. The euro conversion does
not support UOM changes, as illustrated in the following
example:
A sales order for a stock item has a UOM conversion of
12 EA = 1 BX, a pricing UOM of BX, and a transaction
UOM of EA. The conversion factor for the item is 12 to
1. You later change the UOM conversion to 5 EA = 1
BX, which changes the conversion factor to 5 to 1. The
sales order is domestic only. Using this example, the
following occurs during the euro conversion:
• The original domestic order becomes a foreign

order with an EA to BX conversion factor of 5 to 1
and a foreign value of 12 to 1.
• For the new domestic order, the quantity is

converted based on the transaction UOM of EA.
The extended price is converted using the current
conversion factor of 5 to 1 (not the original factor
of 12 to 1) to derive the new domestic euro value.
As this example illustrates, the euro conversion does not
support UOM changes. If you want to convert orders
that have items where the UOM has changed, you will
need to identify the purchase or sales orders and change
the UOM conversion for an item back to its original
value before running the euro conversion.

65

√ √
Checklist: Manufacturing Pre-Conversion Tasks

√ √
Locate and revise items Run Costing Exceptions (R30801), accessed from menu
with missing values G3023, to generate a report that lists any values missing
for an item. This could include an item without a routing,
cost component, and so on. Revise any items that appear
on the report.
Compile a list of UDC If you have user defined code (UDC) fields that contain
fields that contain amounts, compile a list of the fields and tables in which
amounts they reside. After the conversion, you will have to
manually update the amounts in these fields.
Locate and correct price Run the Work in Process and Completions programs
variances (R31802), accessed from menu G3116.
• Work in Process locates any open work orders with

price variances
• Completions locates any completed work orders

with price variances
In final mode, these programs create journal entries for
work order transactions and update the Work Order
Variances table (F3102).
Locate and correct Prerequisites: Run the Work in Process and Completions
manufacturing variances programs in final mode (previous task).
Run Variances (R31804), accessed from menu G3116. In
final mode, this program creates journal entries for
manufacturing variances.
Caution: Run this program only one time over the same
set of transactions; otherwise, the program will create
duplicate journal entries.

66

√ √
Decide whether to The cost (CST1) and price (UPRC) fields for x-rule
convert x-rule records records in the Assembly Inclusion Rules table (F3293) can
in the F3293 table contain a monetary amount or factor (nonmonetary)
value. For records with a factor value, the price field is
multiplied by the result from the derived calculation in the
DERC field.
Determine whether most of your x-rule records contain a
monetary amount or factor value, and then use the
following guidelines to decide whether to convert the
F3293 table to the euro:
• If most of your x-rule records contain monetary

amounts, consider converting the F3293 table and
then manually changing any records with factor
values.
• If most of your x-rule records contain factor values,

consider not converting the F3293 table as it would
convert the factor values to the euro, which would
not be the desired result. In this case, all F3293
records must be converted manually.
To convert the F3293 table, you run a post-conversion
job called Assembly Inclusion Conversion, which is
described in Running Ordered Conversion Jobs.
Process all work orders Process all open work orders and complete all shop floor
activities.
The euro conversion converts history tables (F3112,
F31122, and F3102), but it does not convert open work
orders. If it did, a work order would have labor and
material costs in two different currencies after the
conversion. The labor costs would be in the new
currency (euro), whereas the material costs would remain
in the base (non-euro) currency. Because of this, it is
important to process all work orders to avoid
inconsistencies in the F3102 table.
Locate work orders Create and run a report or query over the Work Order
with a blank value in the Master table (F4801) to locate work orders with a Charge
Charge to BU field to BU equal to blank. To correct the work orders, enter a
value in the Charge to BU field on Work Order Entry
(R48201) for each work order.
The euro conversion programs do not convert work
orders with a blank value in the Charge to BU field.

67

√ √
Ensure that all currency OneWorld Xe only. Run Load Domestic Currency Code
code fields for Service - System 48S/52 (R11848S), accessed from the Multi-
Billing contain the Currency Advanced Operations menu (G1131).
domestic currency
Checklist: Final Post

√ √
Post the general ledger Prerequisite: Process and post transactions in all J.D.
Edwards systems.
Run Post General Journal (R09801), accessed from menu
G0911, to update the Account Ledger (F0911) and
Account Balances (F0902) tables. You must do this
before you complete the next task, Reviewing and Correcting
Pre-Conversion Integrity Reports.

68
Reviewing and Correcting Pre-Conversion Integrity

Reports
This task consists of a checklist and description of the pre-conversion integrity

reports that you must review and correct before you run the euro conversion. The
checklist has two check-off (√) columns - one for your test (TEST) environment
and the other for your production (PROD) environment.
To ensure the accuracy of the data that you are going to convert to the euro, you
must run the pre-conversion integrity reports, and then review and correct them.
Typically, clients who review and correct their integrity reports and clean up their
tables before the euro conversion have fewer errors to review and correct after the
conversion. Run the pre-conversion integrity reports in proof mode to review and
manually correct any errors. Optionally, you can run them in final (update) mode,
which does the following:
• Tests the integrity of data between tables with dependent relationships.

• Locates the difference between the tables.
• Creates adjusting entries for batches that are out of balance. You can use the
data selection to exclude records in which you do not want to create
adjusting entries.
If there is a time lapse between when you run the pre-conversion integrity reports
and the euro conversion, run the integrity reports again to correct any errors that
might have occurred during that time.
Run integrity reports only for those systems that your company uses. After the
conversion, compare your pre-conversion integrity reports to the post-conversion
integrity reports to verify that the conversion results are accurate.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Reviewing and Correcting Pre-Conversion Integrity
Reports 69
Most integrity reports are accessed from the Euro Conversion menu (G97UE9).
An example of the B73.3.1EURO and B73.3.2EURO menu appears below.
Remember that you must run the pre-conversion integrity reports, and review and
correct them and complete all remaining tasks first in your test environment,
correcting any data issues in both your test and production environments. Later,
when you are satisfied with the results of the euro conversion in your test
environment, complete all of the tasks again in your production environment and
"go live."
Before You Begin

G Make sure all transactions for all systems have been posted and updated in
the Account Ledger (F0911) and Account Balances (F0902) tables.
G Before you run the pre-conversion integrity reports in proof mode for
Financials, make sure you change the flag on batches that do not appear on
integrity reports. If you do not do this, you will have no record or audit trail
of out-of-balance batches before the euro conversion.
To locate and change the flag on batches, do the following:
G Create and run a query or UBE over the Batch Control Records
table (F0011) for IBOI (Include Batch on Integrity) equal to N.
G On Work with Batches (R0011), select the batch. From the Row
menu, choose Revise. On Create/Revise Batch Header, choose
Overrides from the Form menu. On Batch Overrides, turn off the
Exclude Batch From Integrity Report option.
Reports 70
G A/R and A/P to G/L integrity reports. Before you run the F03B11 to
F0911 Integrity (R890911AI), F0411 to F0911 Integrity (R04711), and
F0414 to F0911 Integrity (R04712) reports in final mode, determine whether
you want to automatically create adjusting entries for batches that are out of
balance. If you do not want adjusting entries created, modify the data
selection to exclude the batches from appearing on the integrity reports.
Otherwise, adjusting entries will be created for out-of-balance batches.
G Before you run the F03B11 to B0911 Integrity report (R890911AI), make
sure that you set up AAI items ADR and AER for all companies you will
convert to the euro, as well as company 00000. If you do not, you will
receive an error message (AAI missing/invalid) when you run the report in
both proof and final modes.
Topics
G Coexistence and Accounts Receivable
G Checklist: Financials Pre-Conversion Integrity Reports
G Checklist: Distribution Pre-Conversion Integrity Reports
G Checklist: Logistics Pre-Conversion Integrity Reports
G Checklist: Manufacturing Pre-Conversion Integrity Reports
G Checklist: Batch Headers Pre-Conversion Integrity Reports
G Checklist: Post Integrity Job (Repost)
Coexistence and Accounts Receivable
With coexistence, clients run both WorldSoftware and OneWorld applications

while accessing the same database. One of the exceptions to this is the J.D.
Edwards Accounts Receivable applications. Because these applications have
different databases, they do not coexist which means that clients run the Accounts
Receivable applications in either WorldSoftware or OneWorld, but not both.
Clients with coexistence must make sure they run their A/R integrity reports over
the correct (active) database, using the Accounts Receivable application that is
implemented at their site. To determine which Accounts Receivable application is
implemented at your site, review the enhanced A/R constants for company 00000.
To access the enhanced A/R constants for company 00000, do the following:
1. From the Accounts Receivable Setup menu (G03B41), choose Accounts

Receivable Constants.
2. On System Setup, click Accounts Receivable Constants.
3. On Work with A/R Constants, click Find.
Reports 71
4. Choose company 00000 and click Select to access Accounts Receivable

Constants.
5. On Accounts Receivable Constants, choose Enhanced A/R from the Form
menu.
Checklist: Financials Pre-Conversion Integrity Reports
The following integrity reports are accessed from the Financials Integrities menu
(G97UE91).
Accounts Receivable
Report Name Description TEST PROD

(Program Number) √ √
F03B11 to F03B22 (Proof) Compares records in the A/R Ledger table

Integrity (R8903B22I) (F03B11) to the Fee Journal History table (F03B22) and
prints differences on a report.
(Final) Creates an adjusting amount in the F03B22 to
balance to the F03B11.
Reports 72

F03B11 to F03B40 Prerequisite: Previous integrity report (R8903B22I).

Integrity (R8903B40I)
(Proof) Compares records in the A/R Ledger table
(F03B11) to the Deduction Management table (F03B40)
and prints differences on a report.

(F03B11) to the A/R Check Detail table (F03B14) and

(Proof) Compares records in the A/R Check Detail table
(F03B14) to the Deduction Activity table (F03B41) and

(F03B14) to the Receipts Header table (F03B13) and
(Final) Creates an adjusting amount in the F03B13 table
to balance to the F03B14 table.

(Proof) Compares records in the Fee Journal History
table (F03B22) to the Fee History Detail table (F03B23)
and prints differences on a report.
(Final) Creates an adjusting amount in the F03B23 table
to balance to the F03B22 table.
Reports 73

F03B11 to F0911 Prerequisite: Previous integrity report (R8903B23I).

Integrity (R890911AI)
(F03B11) to the Account Ledger table (F0911) and
(Final) Creates an adjusting amount in the F0911 table
by document (G/L distribution) or by batch (automatic
offset) to balance to the F03B11 table. The adjusting
amount is directed to one of the following AAIs:
• ADR, if the offset method is by document. This

AAI item tracks differences between the F03B11
and F0911 distribution amounts.
• AER, if the offset method is by batch. This AAI

item tracks differences between the F03B11 and
F0911 automatic entry (AE) amounts.
Note: Make sure that you set up AAI items ADR and
AER for all companies that you will convert to the euro,
as well as company 00000. If you do not, you will receive
an error message (AAI missing/invalid) when you run
this report in both proof and final modes.
F03B14 to F0911 Prerequisite: Previous integrity report (R890911AI).

Integrity (R890911BI)
(Final) Creates an adjusting amount in the F0911 table to
balance to the F03B14 table.
F03B13 to F0911 Prerequisite: Previous integrity report (R890911BI).

Integrity (R890911CI)
(Proof) Compares records in the Receipts Header table
A/R to G/L by Offset OneWorld B73.3.1 only. Prerequisite: Previous integrity

Account (R03B7001A) report (R890911C1).
Summarizes open amounts in each G/L account
(F0311) and compares the total to the balance amount in
each offsetting A/R trade account (F0902).
Reports 74

A/R to Account OneWorld B73.3.2 and above. Prerequisite: R890911C1.

Balance by Account ID
(R03B707) If this report does not appear on your menu, visit the
Knowledge Garden for information about how to add it.
The path is Worldwide Topics > Euro Base Currency
Conversion > Global Support Services > OneWorld
Knowledge Documents > Technical > Menu
Corrections. Alternatively, you can run the report from
Batch Versions. From menu GH9011, choose Batch
Versions. In the Batch Application field, enter R03B707
and click Find. Choose the version and click Select to
run the report as usual.
This report replaces A/R to G/L by Offset Account
(R03B7001A). It summarizes open amounts in each
G/L account in the A/R Ledger table (F0311) and
compares the total to the balance amount in each
offsetting A/R trade account in the Account Balances
table (F0902).
For more information about the R03B707 report, visit
breaking news on the Knowledge Garden. The path is
Product > Knowledge > Knowledge Breaking News >
OneWorld > Financials > Accounts Receivable >
Reports.
Accounts Payable

F0411 to F0911 (Proof) Compares records in the A/P Ledger table

Integrity (R04711) (F0411) to the Account Ledger table (F0911) and prints
differences on a report.
(Final) Creates an adjusting amount in the F0911 table by
document (G/L distribution) or by batch (automatic
offset) to balance to the F0411 table. The adjusting
amount is directed to one of the following AAIs:
• ADP, if the offset method is by document. This

AAI item tracks differences between the F0411 and
F0911 distribution amounts.
• AEP, if the offset method is by batch. This AAI

item tracks differences between the F0411 and
F0911 automatic entry (AE) amounts.
Reports 75

F0414 to F0411 (Proof) Compares records in the A/P Matching

Integrity (R04713) Document Detail table (F0414) to the A/P Ledger table
(F0411) and prints differences on a report.
balance to the F0411 table.
F0414 to F0911 Prerequisites: Previous integrity reports (R04711 and

Integrity (R04712) R04713).
(Proof) Compares records in the A/P Matching
Document Detail table (F0414) to the Account Ledger
table (F0911) and prints differences on a report.
A/P to G/L Integrity Summarizes open amounts in each G/L account in the
by Offset Account A/P Ledger table (F0411) and compares the total to the
(R047001A) balance amount in each offsetting A/P trade account in
the Account Balances table (F0902).
General Accounting

Unposted General Prints a general journal of unposted transactions in the

Journal (R09301) Account Ledger table (F0911).
Accounts without (Proof) Locates account master records with an invalid

Business Units company number and without a business unit record.
(R097041)
(Final) Updates the Account Master table (F0901) with
the company number from the business unit master
record.
Account Balance (Proof) Locates account balance records with an invalid

without Account company number and without an account master record.
Master (R097031)
(Final) Updates the Account Balances table (F0902) with
the company number from the account master record.
Reports 76

Transactions without (Proof) Locates transaction records with an invalid

Account Master company number and without an account master record.
(R097021)
(Final) Updates the Account Ledger table (F0911) with
the company number from the account master record.
Companies in Balance Creates a report that shows the net balance for each
(R097001) company. If a company is in balance, the columns on
the report are blank.
Intercompany Accounts Locates imbalances between corresponding

in Balance (R097011) intercompany accounts and prints a report.
If you have multiple companies with different base
currencies, do not run this integrity report. This integrity
report does not accommodate different base currencies.
Account Balance to Locates imbalances between the Account Balances

Transactions (R09705) (F0902) and Account Ledger (F0911) tables by fiscal
period and prints a report.
If you have imbalances between these tables and you
turn monetary accounts on and off, contact your Global
Support Services consultant for a resolution plan for
monetary accounts.
Foreign Account This integrity report is accessed only from the Integrity
Balance Integrity Reports and Updates menu (G0922).
(R09707)
(Proof) Compares foreign ledger (CA) records to
domestic ledger (AA) records in the Account Balances
table (F0902) and prints a report that shows CA records
without a corresponding AA record.
(Final) Removes CA records in the F0902 table that do
not have a corresponding AA record.
Cash Basis Integrity OneWorld Xe only. This integrity report is accessed only
Test (R11C750) from the Cash Basis Accounting menu (G09314).
Identifies cash accounts that have different balances in
the AA and AZ ledgers after posting.
Repost Account Ledger See Checklist: Post Integrity Job (Repost).

(R099102)
Reports 77
Localization

F70404 to F0911 For Italian clients only. (Proof) Compares records in the
Integrity (R74701) Account Ledger table (F0911) to the G/L Registration
Balance table (F70404).
Integrity (R74703) A/P Ledger table (F0411) to the Withholding Tax Detail
table (F74411).

F0911 Transaction Prints Account Ledger (F0911) transactions for accounts

Report (R127012) within the AAI item FX range.
Unposted F0911 Compares unposted transactions in the Account Ledger

Transactions to F1202 table (F0911) to unposted transactions in the Asset
(R12301) Balances table (F1202) for accounts within the AAI item
FX range. Prints differences on a report.
F0911 to F1202 (Proof) Compares posted transactions (with batch rear end
Integrity (R12910) = *) in the Account Ledger table (F0911) to posted
transactions in the Asset Balances table (F1202).
balance to the F0911 table. This integrity report is the
Fixed Asset Repost.
Note: If you summarize your depreciation transactions,
do not run this integrity report. Clients who summarize
transactions have F1202 records without supporting
F0911 transactions and running this integrity report serves
no purpose. Once you summarize transactions, you cannot
go back and create detail for them.
F1202 to F0902 Compares posted transactions in the Asset Balances table

Integrity (R127011) (F1202) to posted transactions in the Account Balances
table (F0902) and prints differences on a report.
Reports 78

F5144/F5145 to (Proof) Compares records in the Account Balances table

F0902 (R51800) (F0902) to records in the Profit Recognition (F5144) and
Profit Recognition Account Balances (F5145) tables.
(Final) Creates adjusting amounts in the F5144 and F5145
tables to balance to the F0902 table.
Change Management

CO/PCO OneWorld Xe only. Compares final and quoted amounts

(F5315/F5314) for cost, revenue, and subcontract records in the Change
Integrity (R53701) Order Master table (F5315) to the attached planned
change orders in the Planned Change Order Master table
(F5314). Prints differences on a report.
CPC/CR OneWorld Xe only. Compares final and quoted amounts

(F5314/F5311) for cost, revenue, and subcontract records in the Planned
Integrity (R53702) Change Order Master table (F5314) to the attached
change requests in the Change Request Details table
Checklist: Distribution Pre-Conversion Integrity Reports
The following integrity report is accessed from the Distribution Integrities menu
(G97UE92).

Commitment Integrity (Proof) Compares records in the P.O. Detail Ledger table
Report (R40910) (F43199) to the Purchase Order Detail table (F4311) and
records in the F43199 table to the Account Balances table
(Final) OneWorld Xe only. Creates an adjusting amount in
the F43199 table if there is a difference between the
amounts in the F4311 and F43199 tables. Creates an
adjusting amount in the F0902 table if there is a difference
between the amounts in the F43199 and F0902 tables.
Reports 79
Checklist: Logistics Pre-Conversion Integrity Reports
The following integrity reports are accessed from the Logistics Integrities menu
(G97UE93).

Item Ledger/Account Compares records in the Account Ledger table (F0911) to

Integrity (R41543) the Item Ledger table (F4111) and prints differences on a
report.
Item Balance/Ledger Compares records in the Item Location table (F41021) to

report.
Checklist: Manufacturing Pre-Conversion Integrity Reports
The following integrity report is accessed from the Manufacturing Integrities menu
(G97UE94).

Cost Compares the sum of the frozen standard cost

Component/Ledger components to the unit cost in the Cost Ledger table
Integrity (R30543) (F4105) and prints a report that shows the variances.
Checklist: Batch Headers Pre-Conversion Integrity Reports
The following integrity reports are accessed from the Batch Header Integrities
menu (G97UE95).

Unposted Batches Prints all unposted batches sequentially by batch type and
(R007011) batch number.
Transactions to Batch Locates inconsistencies in the Batch Control table (F0011).

Headers (R007021) Locates F03B11, F0411, and F0911 transactions without a
batch header record. Locates unposted F03B11, F0411,
and F0911 transactions with a posted batch header record.
Reports 80

Company by Locates batches by company that were posted out-of-

Batch/Out of Balance balance and prints a report.
(R09706)
Batch to Detail/Out of Run this report after you run the pre-conversion integrity
Balance (R007031) reports for all other systems and before you repost the
account ledger.
Locates batches that were posted out-of-balance and prints
a detailed report. Compile a list of any batches that were
intentionally posted out-of-balance. Use this list to
compare the results after the conversion.
Checklist: Post Integrity Job (Repost)
The following program is accessed from the Post Integrity Jobs menu (G97UE99).

Repost Account Ledger Prerequisite: Run the pre-conversion integrity reports for
(R099102) all other systems.
Run the Repost Account Ledger program to:
• Identify accounts with different amounts in the

F0911 and F0902 tables (proof)
• Update the F0902 table with the posted amounts

from the F0911 table (final)
For more information, see Reposting the Account Ledger.
Reports 81
Purging Outdated Data Tables
This task consists of a checklist and description of the purge programs that you
can run before you run the euro conversion. The checklist has two check-off (√)
columns - one for your test (TEST) environment and the other for your
production (PROD) environment.
J.D. Edwards recommends that you summarize and purge any data that does not
need to be converted to the euro. This will help conserve valuable disk space and
system resources, as the conversion programs do not convert purged (P) tables.
However, before you purge any data, it is very important that you understand how
the J.D. Edwards purge programs work. This will help to ensure that when you
purge data, you get the results you expect.
Each purge program removes data in a table that meets certain criteria, regardless
of any interdependencies that might exist between that table and another table.
This means that when you purge data in a table, the results might impact another
table so that you no longer have data integrity between the two tables. For
example, if you purge data in a table in Sales Order Management, the results might
affect the data integrity between that table and a table in Accounts Receivable.
Because the purge programs are not based on any interdependencies between
tables, there is no purge process that dictates the order in which tables must be
purged.
Be sure to allow plenty of time to purge outdated data tables. Depending on the
number of transactions in a table, it can take hours or days to run a purge,
especially for tables as large as the Account Ledger (F0911).
As always, make sure that you do the following before running any purge
programs:
• Run integrity reports and correct any integrity issues. See Reviewing and
Correcting Pre-Conversion Integrity Reports.
• Back up your data.
Purge outdated data only for those systems that your company uses.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Purging Outdated Data Tables

82
Most purge programs are accessed from the Summarization and Purges menu
(G0023). An example of the B73.3.1EURO and B73.3.2EURO menu appears
below.
Remember to purge outdated data tables and complete all remaining tasks in this
the euro conversion in your test environment, complete all of the tasks again in
your production environment and "go live."
Before You Begin

G Run integrity reports for all J.D. Edwards systems that you use and correct
any integrity issues
G Back up your data
Topics
G Checklist: General Purge Programs
G Checklist: Financials Purge Programs
G Checklist: Fixed Assets Purge Programs
G Technical Considerations: Distribution Purge Programs
G Checklist: Distribution Purge Programs
G Checklist: Logistics Purge Programs
G Checklist: Manufacturing Purge Programs

83
Checklist: General Purge Programs
The first purge program listed below is accessed from the General Purges menu
(G00231). This program, along with the second program, can also be accessed
from application-specific menus, as indicated in the second column of the table.
Purge Program Description TEST PROD

Application-Specific Menu √ √
Purge Balance Auditor Table Purges workfiles built for financial reporting from
(P83001) the Balance Audit Workfile (F83UI001).
Advanced Report Setup menu (GH9141).
Tax File Purge OneWorld Xe only. Removes records from the

(R0018PURGE) Sales/Use/VAT Tax table (F0018) with a date
prior to the date you specify in the data selection.
Tax Processing & Reporting menu (G0021).
Checklist: Financials Purge Programs
The following purge programs are accessed from the Financials Purges menu
(G00232). They can also be accessed from application-specific menus, as indicated
in the second column of the table.
General Accounting

Summarize Creates a single balance forward record to replace

Transactions (R09811) numerous detailed transactions.
Summarize & Purge Data menu (G09317).
Purge Prior Year JEs Removes summarized journal entries for prior years
(R09911) from the Account Ledger table (F0911).
Purge Prior Year Removes account balance records with dates prior to the
Account Balance current fiscal year from the Account Balances table
(R09912) (F0902).

84

Purge Batch Journal Removes batch journal entries from the Journal Entry
Entries (R0911Z1P) Transactions Batch table (F0911Z1). This purge does
not affect journal entries in the F0911 table.
Batch Journal Entry Processing menu (G09311).
Accounts Receivable

Purge Electronics Removes processed electronic receipts from the

Receipt Input Electronic Receipts Input table (F03B13Z1).
(R03B0041A)
Caution: Ensure that you purge only receipts with an
auto-cash upload status of Y. Otherwise the purge
program will remove receipts that are stored in the
F03B13Z1 table for invoice and statement matching
purposes.
Automated Receipts Processing menu (G03B13).
Purge Batch Invoices Removes processed invoices from the following tables,
(R03B11Z1P) regardless of the batch they are in:
• Invoice Transactions Batch (F03B11Z1)
• Journal Entry Transactions Batch (F0911Z1)
• Journal Entry Transactions Batch Tag File

(F0911Z1T)
This purge removes only batch invoices; it does not
affect invoices in the F03B11 table.
Batch Invoice Processing menu (G03B311).
Purge/Repost A/R Removes records from the A/R Statistical History table
Statistical History (F03B16) and resets the ISTC field from 1 to 0 on the
(R03B163) corresponding invoices in the Customer Ledger table
(F03B11).
Use the data selection to designate which records to
remove; however, make sure you do not remove
records by company in the data selection.
A/R Advanced & Technical Operations menu
(G03B31).

85

Purge Removes delinquency notice and statement records

Statement/Notification from the A/R Notification History (F03B20) and A/R
(R03B5010) Notification History Detail (F03B21) tables.
To purge only delinquency notices, use the data
selection to specify notification type DL. To purge only
statement information, use the data selection to specify
notification type ST.
Statement Reminder Processing menu (G03B22).
Purge Invoice Removes paid and posted invoices without an open

Transactions (R03B800) amount from the Accounts Receivable Ledger table
(F03B11).
(G03B31).
Purge Receipt Removes posted receipts from the Receipts Header

Transactions (R03B801) (F03B13) and A/R Check Detail (F03B14) tables.
(G03B31).
Accounts Payable

Purge Closed A/P Removes paid transactions (open amount = zero) from
Records (R04800) the A/P Ledger (F0411), A/P Matching Document
(F0413), and A/P Matching Document Detail (F0414)
tables.
A/P Advanced & Technical Operations menu (G0431).
Purge Batch Vouchers Removes inbound processed vouchers from the

(R0411Z1P) Voucher Transactions Batch (F0411Z1) and Journal
Entry Transactions Batch (F0911Z1) tables, regardless
of the batch they are in. This purge does not affect
vouchers in the F0411 table.
Batch Voucher Processing menu (G04311).

86

Purge F0413 Removes outbound processed payments from the

Interoperability Table F0413 Interoperability (F0413Z1), F0414
(R0413Z1) Interoperability (F0414Z1), and F0911 Interoperability
(F0911Z4) tables, regardless of the batch they are in.
This purge does not affect payments in the F0413 or
F0414 table.
Automatic Payment Processing menu (G0413).
Purge A/P Payee Removes control records and associated audit trails
Control (R0450P) from the Payee Control table (F0450).
A/P Advanced & Technical Operations menu (G0431).
Purge Cost Analyzer Removes balance records from the Cost Analyzer
(R1602P) Balances table (F1602) and clears the posted code in the
Account Ledger table (F0911), which allows you to
repost the records in the euro after the conversion.
Cost Analyzer menu (G1612).
Address Book

Purge Address Book OneWorld B73.3.2 and above. Removes address book
(R01800P) records without associated transactions from the
following tables:
• Address Book Master (F0101)
• Who's Who (F0111)
• Address Book Generic Text (F0016)
• Contact Phone Numbers (F0115)
• Address by Date (F0116)
• Customer Master (F03B01)
• Supplier Master (F0401)
• Address Organizational Structure Master (F0150)

87

Purge Batch Address Removes processed addresses from the Address Book
Book (R0101Z1P) Batch Input table (F0101Z1), regardless of the batch
they are in.
A/B Advanced & Technical Operations menu (G0131).
Purge Completed Tasks For clients who use the J.D. Edwards Workflow
(R01131P) Management system. Removes message log records
from the Message Log table (F0113).
A/B Advanced & Technical Operations menu (G0131).
Checklist: Fixed Assets Purge Programs
The following purge programs are accessed from the Fixed Assets Purges menu

Purge Asset Master and Purges selected asset records or entire data tables,
Balances (R12912) based on the processing options. You can purge prior
year records in the Item Balances table (F1202), assets
that you disposed in a prior year, and so on.
Advanced Operations menu (G1231).
Purge Unedited Asset Purges selected asset records or entire data tables,
Master Transactions based on the processing options. You can purge prior
(R1201Z1P) year records in the Item Balances table (F1202), assets
that you disposed in a prior year, and so on.
Asset Interoperability menu (G1233).

88
Technical Considerations: Distribution Purge Programs
Caution for OneWorld B73.3, B73.3.1, and B73.3.2

The following information applies to clients who plan to purge data using the
Distribution purge programs prior to OneWorld Xe. (For OneWorld Xe, the
Distribution purge programs run as expected.)
For releases B73.3, B73.3.1, and B73.3.2, the following purge programs were
written using a tool called Table Conversion:
• Purge Purchase Order Detail (R4311P)

• Purge Purchase Order Receiver (R43121P)
• Purge Purchase Order Detail Ledger (R43199P)
• Purge Purchase Order Header (R4301P)
• Purge Purchase Order Text Lines (R43960)
• Purge Sales Order History (R42119P)
• Purge Sales Transactions (R42199P)
With Table Conversion, the purge programs do the opposite of what you would
expect them to do. That is, they retain records that match the data selection criteria
and delete records that do not match the data selection criteria.
The Distribution purge programs listed above were corrected in electronic

software updates (ESUs 4232204 and 4291896) for OneWorld release B73.3.2. The
corrected purge programs in these ESUs use a tool called Batch Delete, which
deletes records that match the data selection criteria and retain records that do not.
The ASU for B73.3.2 does not contain the corrected purge programs.
If you do not install the ESUs described, you must purge your data according to the
Table Conversion logic by entering your data selection in the opposite way as you
normally would. For example, to purge purchase order detail records for company
00100 only, you enter data selection for Company that is not equal to 00100.
The Distribution purge programs listed above must be run locally, not from a
server.

89
Checklist: Distribution Purge Programs
The following purge programs are accessed from the Distribution Purges menu
(G00234). Many of them can also be accessed from application-specific menus, as
indicated in the second column of the table.
Procurement

Purge Purchase Order Removes records with a next status of 999 (closed) from
Receiver (R43121P) the Purchase Order Receiver table (F43121).
Data File Purges menu (G43A311).
Purge Purchase Order Prerequisite: Purge Purchase Order Receiver (R43121P).

Detail (R4311P)
Removes records with a next status of 999 (closed) from
the Purchase Order Detail table (F4311).
Purge Purchase Order Prerequisite: Purge Purchase Order Detail (R4311P).

Header (R4301P)
Removes records from the Purchase Order Header table
(F4301) if there are no active detail lines.
Purge Purchase Order Prerequisite: Purge Purchase Order Header (R4301P).

Detail Ledger
(R43199P) Removes records with a next status of 999 (closed) from
the Purchase Detail Ledger table (F43199).
Purge POE Header OneWorld releases B73.3.1 and B73.3.2 only. Removes
Records (R4301Z1P) records from the Purchase Order Header Unedited
Transaction table (F4301Z1).
Purchasing Interoperability menu (G43A313).
Purge Receipt Routing Removes records from the Receipt Routing Unedited
(R43092Z1P) Transaction table (F43092Z1).
Purge for Receipts Removes records from the Receipts Unedited

(R43121Z1P) Transaction table (F43121Z1).

90

Purge Purchase Order Changes status of text lines to 999 (closed) on purchase
Text Lines (R43960) orders that have been closed.

Purge Sales Order Detail Deletes detail lines with a status of 999 from the Sales
to History (R42996) Order Detail table (F4211) and writes a history record
to the Sales Order History table (F42119).
Data File Purges menu (G42312).
Purge Sales Order Detail Available as of OneWorld Xe. Removes records from
(R4211P) the Sales Order Detail table (F4211).
Purge Sales Order Prerequisite: Purge Sales Order Detail to History

Header (R4201P) (R42996).
Removes records from the Sales Order Header table
(F4201) only if there are no open detail lines with a
matching order type and order number in the Sales
Order Detail table (F4211).
Purge Sales Order Text Changes status of text lines to 999 (closed) on sales
(R42960) orders with no open detail lines.
Purge Batch Receiver Deletes processed sales orders from the Batch
(R4001ZP) Receiver - Order Headings table (F4001Z). This
program selects only records with Y in the Processed
(Y/N) field.
Purge Sales Order History Removes records from the Sales Order History table
(R42119P) (F42119).

91

Purge Sales Transactions Removes records from the Sales Order Ledger table
Records (R42199P) (F42199).
Electronic Commerce

Purge EDI Purchase Removes inbound transactions from the Purchase Order
Order Inbound Header (F47011), Purchase Order Detail (F47012),
(R47018) Purchase Order Detail SDQ (F47013), Order Address
Information (F4706), Order Text Lines Header (F4714),
and Order Text Lines Detail (F4715) tables.
Customer Order menu (G47212).
Purge EDI Purchase Removes outbound transactions from the Purchase

Order Outbound Order Header (F47016), Purchase Order Additional
(R47019) Header (F470161), Purchase Order Detail (F47017),
Purchase Order Additional Detail (F470171), Order
Address Information (F4706), Order Text Lines Header
(F4714), and Order Text Lines Detail (F4715) tables.
Purchase Order menu (G47222).
Purge EDI P.O. Removes inbound transactions from the Purchase Order
Acknowledgement Acknowledgement Header (F47021) and Purchase Order
Inbound (R47028) Acknowledgement Detail (F47022) tables.
Purchase Order menu (G47222).
Purge EDI P.O. Removes outbound transactions from the Purchase

Acknowledgement Order Acknowledgement Header (F47026), Purchase
Outbound (R47029) Order Acknowledgement Detail (F47027), Order
Customer Order menu (G47212).
Purge EDI Shipping Removes outbound transactions from the Shipping

Notice Outbound Notice Header (F47036), Shipping Notice Detail
(R47039) (F47037), Order Address Information (F4706), Order
Text Lines Header (F4714), and Order Text Lines Detail
(F4715) tables.
Shipping Notice menu (G47215).

92

Purge EDI Voucher Removes inbound transactions from the Invoice Header
Inbound (R47041P) (F47041), Invoice Detail (F47042), and Invoice Summary
(F47044) tables.
Invoice - Summary menu (G47261).
Purge EDI Invoice Removes inbound transactions from the Invoice Header
Inbound (R47048) (F47041), Invoice Detail (F47042), and Invoice Summary
(F47044) tables.
Invoice with Receipt Match menu (G47227).
Purge EDI Invoice Removes outbound transactions from the Invoice from
Outbound (R47049) Sales Header (F47046), Invoice Additional Header
(F470461), Invoice from Sales Detail (F47047), Invoice
Additional Detail (F470471), Order Address Information
(F4706), Order Text Lines Header (F4714), and Order
Text Lines Detail (F4715) tables.
Sales Invoice menu (G47217).
Purge EDI Payment Removes outbound transactions from the Payment

Order Outbound Order Header (F47056), Payment Order Bank N & A
(R47059) (F470561), Payment Order Bank Vendor N & A
(F470562), Payment Order Payee N & A (F470563), and
Payment Order Remittance Advice (F47057) tables.
Payment Order with Remittance menu (G47266).
Purge EDI Planning Removes inbound transactions from the Planning

Schedule Inbound Schedule Header (F47061) and Planning Schedule Detail
(R47068) (F47062) tables.
Planning Schedule - Forecast menu (G47251).
Purge EDI Planning Removes outbound transactions from the Planning

Schedule Outbound Schedule Header (F47066) and Planning Schedule Detail
(R47069) (F47067) tables.
Planning Schedule-Forecast menu (G47251).
Purge EDI Receiving Removes inbound transactions from the Receiving

Advice Inbound Advice Header (F47071) and Receiving Advice Detail
(R47078) (F47072) tables in the Procurement and Sales Order
Management systems.
Receiving Advice-Purchasing menu (G47226).
Purge EDI Receiving Removes outbound transactions from the Receiving

Advice Outbound Advice Header (F47076), Receiving Advice Detail

93

(F4715) tables.
Receiving Advice-Purchasing menu (G47226).
Purge EDI Request for Removes inbound transactions from the Request for
Quote Inbound Quote Header (F47091), Request for Quote Detail
(R47098) (F47092), and Request for Quote Detail SDQ (F47093)
tables.
Request for Quote - Sales menu (G47211).
Purge EDI Request for Removes outbound transactions from the Response to
Quote Outbound RFQ Header (F47106), Response to RFQ Additional
(R47099) Header (F471061), Response to RFQ Detail (F47107),
Response to RFQ Additional Detail (F471071), Order
Request for Quote - Purchasing menu (G47221).
Purge EDI Response to Removes inbound transactions from the Response to

RFQ Inbound (R47108) RFQ Header (F47101), Response to RFQ Detail
(F47102), Order Text Lines Header (F4714), and Order
Text Lines Detail (F4715) tables.
Purge EDI Response to Removes outbound transactions from the Request for
RFQ Outbound Quote Header (F47096), Request for Quote Detail
(F4715) tables.
Request for Quote - Sales menu (G47211).
Purge EDI Product Removes inbound transactions from the Product

Activity Data Inbound Activity Data Header (F47121), Product Activity Data
(R47128A) Detail (F47122), and Product Activity Data SDQ
(F47123) tables.
Product Activity Data menu (G47241).
Purge EDI Product Removes outbound transactions from the Product

Activity Data Outbound Activity Data Header (F47126), Product Activity Data
(R47129A) Detail (F47127), and Product Activity Data SDQ
(F47128) tables.
Product Activity Data menu (G47241).

94

Purge EDI Purchase Removes inbound transactions from the Purchase Order
Order Change Inbound Change Header (F47131), Purchase Order Header
(R47138) Detail (F47132), Order Address Information (F4706),
Order Text Lines Header (F4714), and Order Text Lines
Detail (F4715) tables.
Customer Order Change menu (G47213).
Purge EDI Purchase Removes outbound transactions from the Purchase

Order Change Order Change Header (F47136) and Detail (F47137),
Outbound (R47139) Order Address Information (F4706), Order Text Lines
Header (F4714), and Order Text Lines Detail (F4715)
tables.
Purchase Order Change menu (G47223).
Purge EDI P.O. Change Removes inbound transactions from the Purchase Order
Acknowledgement Change Acknowledgement Header (F47141) and Detail
Inbound (R47148) (F47142) tables.
Purchase Order Change menu (G47223).
Purge EDI P.O. Change Removes outbound transactions from the Purchase
Acknowledgement Order Change Acknowledgement Header (F47146) and
Outbound (R47149) Detail (F47147), Order Address Information (F4706),
Order Text Lines Header (F4714), and Order Text Lines
Detail (F4715) tables
Customer Order Change menu (G47213).
Purge EDI Shipping Removes outbound transactions from the EDI Shipping
Scheduler Outbound Schedule Header (F47156) and Detail (F47157)
(R47156) Outbound tables.
Checklist: Logistics Purge Program
The following purge program is accessed from the Logistics Purges menu
(G00235). It can also be accessed from an application-specific menu, as indicated

95
Warehouse Management

Purge Inbound Removes inbound suggestion records from the

Suggestion Records Unedited Suggestion table (F4611Z1).
(R4611Z1P)
Warehouse Interoperability menu (G46313).
Checklist: Manufacturing Purge Programs
The following purge programs are accessed from the Manufacturing Purges menu
Work Orders

Purge Work Orders Removes work orders from the Work Order Master
(R4801P) table (F4801) and related information from the
following tables:
• Work Order Instructions (F4802)
• Work Order Parts List (F3111)
• Work Order Routing Instructions (F3112)
• Work Order Time Transactions (F31122)

Shop Floor Management Advanced menu (G3131).

Purge Closed Work Removes work orders and any associated record types
Orders (R48900) and approval records from the Work Order Master
(F4801), Work Order Instructions (F4802), and Work
Order Approval (F4828) tables.
Advanced & Technical Operations menu (G4831).
Purge Outbound Work Removes work orders from the Outbound Work Order
Orders (R4801Z1P) Header table (F4801Z1).

96
Shop Floor Management Interoperability menu

(G31311).

97
Rerunning Pre-Conversion Integrity Reports
After you purge outdated data tables, J.D. Edwards recommends that you rerun
your integrity reports to ensure that the records you purged were the ones you
intended to purge and that purging the records did not create any integrity issues.
If you do not rerun your integrity reports and correct any integrity issues, you will
have no proof that your tables were in balance before the euro conversion. And
after the conversion, you will not have current integrity reports to compare to the
post-integrity reports.
See Reviewing and Correcting Pre-Conversion Integrity Reports for a list of the pre-
conversion integrity reports to rerun. Rerun the integrity reports in proof mode
and, if necessary, research and correct any data issues.
Remember that you must rerun your pre-conversion integrity reports and complete
all remaining tasks in this workbook first in your test environment, correcting any
all of the tasks again in your production environment and "go live."
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Rerunning Pre-Conversion Integrity Reports

98
Conversion Tasks

99
Environments and Euro Conversion Plans
Before you begin the tasks for setting up and running the euro conversion, it is
important to understand what a conversion plan is and why you might choose to
set up more than one conversion plan in an environment.
A conversion plan contains a list of companies to convert to the euro. When you
run the euro conversion, you run it by plan and environment. The system converts
the data for a plan in the same environment that you run the conversion.
Some clients will set up a single conversion plan for all companies and base
currencies and run the euro conversion one time, as depicted in the graphic below.
Alternatively, clients with only a few companies to convert to the euro might set
up one conversion plan for each company.
Other clients will choose to set up multiple plans to convert multiple currencies, as
depicted in the graphic below.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Environments and Euro Conversion Plans
100
And still other clients will set up multiple plans and convert each currency in a
separate plan, as depicted in the graphic below. For these clients, it is easier to
manage the conversion and review the results for a single currency, instead of
multiple currencies, in a plan.
Clients who set up multiple plans must run the euro conversion one plan at a time
and upon successful completion, delete the conversion log before running the next
plan.
To set up a conversion plan, you enter conversion constant information and assign
companies to the plan on the Conversion Plan Revisions form (P0087). When you
run the euro conversion, the system retrieves the conversion rate for each
company in the plan from the Currency Exchange Rate table (F0015).
You do not have to convert companies that are involved in multicurrency

intercompany transactions in the same conversion plan or at the same time.
However, you must convert all companies in all plans before you run the Multi-
Currency Intercompany Conversion and the Intercompany Post, which make the
necessary adjustments and keep the multicurrency intercompany transactions in
balance. See Converting Multicurrency Intercompany Transactions.
As you prepare to convert your company currencies to the euro, ask yourself the
following questions:
• How many companies do I need to convert?

• How many different base currencies do I need to convert?
• In which environments are the companies I need to convert?
Based on your answers to these questions and any special considerations at your
site, such as schedules and resources, carefully evaluate how you want to convert
your company base currencies to the euro and set up your conversion plans
accordingly.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Environments and Euro Conversion Plans
101
Setting Up a Euro Conversion Plan
This task describes the setup tasks that you must complete before running the euro
conversion. To complete the setup tasks, you use the first three programs on the
Pre-Conversion Setup menu (G97UE9A).
Remember that you must set up your euro conversion plan and complete all
remaining tasks in this workbook first in your test environment, correcting any
all the tasks again in your production environment and "go live."
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Setting Up a Euro Conversion Plan

102
Topics
G Verifying Statuses for UDC (H90/DS)
G Setting Up Constants for a Conversion Plan
G Preventing Audit Records from Being Created
G Updating the F9843 Table
G Defining a Conversion Plan
Verifying Statuses for UDC (H90/DS)
The following User Defined Code table (H90/DS) lists the various statuses that a
program can have throughout a OneWorld installation or conversion. The statuses
that apply specifically to the euro conversion programs are 10, 45, 50, 60, and 70.
► To verify statuses for UDC (H90/DS)
From the General Accounting System Setup menu (G0941), choose User Defined
Codes.
1. On Work with User Defined Codes, do the following and click Find:
• Enter H90 in the Product Code field

• Enter DS in the User Defined Codes field
2. Verify that statuses 10, 45, 50, 60, and 70 exist. (The euro conversion
programs do not use some statuses in the table.)

103
3. If a status is missing, do the following:
• Click Add.
• On User Defined Codes, enter the status on a blank line.
• Click OK.
• Click Find to refresh the UDC table and verify that the status was
added.
Setting Up Constants for a Conversion Plan
When you set up constants for a conversion plan, you assign companies and
currency information to the plan. The euro conversion uses the constants for a
plan to determine which company base currencies to convert, which currency to
convert to, and the effective date to use to retrieve conversion rates from the
Currency Exchange Rates table (F0015). When you set up the constants, you also
enter a plan exchange rate. The plan exchange rate is used only by the ordered and
additional conversion jobs.
Before You Begin

G Ensure that you have set up currency relationships for the euro, as described
in Completing Pre-Conversion Tasks.
G The following applies to coexistent clients who run conversion programs in
World first and then run the remaining conversion programs in OneWorld.
After you successfully complete the World conversion programs, you must
delete the Conversion Audit table (F0086) in your data library (DTALIB). If
you do not delete the F0086 table, which contains World converted records,
before you set up constants for a conversion plan in OneWorld, the P0087
program in OneWorld will not create another F0086 table since is already
exists. Therefore, the conversion programs in OneWorld will not write
records to the F0086 table.
► To set up constants for a conversion plan
From the Euro Conversion menu (G97UE9), choose Setup and Conversion. On
the Setup and Conversion menu (G97UE9A), choose Conversion Constants.
1. On Work with Conversion Plans, click Add.

104
2. On Conversion Plan Revisions, type a name for the conversion plan in the
Plan Name field using the following guidelines.
• Give the plan a meaningful name to help you (and others) identify it
throughout the conversion process.
• Use alphanumeric characters. Do not use special characters, except
underscore (_), in the plan name.
• Name your plan something other than ZJDE. (ZJDE is reserved by
J.D. Edwards software as a model plan.)
3. In the Effective Date field, type the date you want the euro conversion
workbench to use to retrieve the conversion rate from the Currency
Exchange Rates table (F0015). The system uses this date to retrieve the rate,
regardless of the transaction date.
If there is not a matching date in the F0015 table, the euro conversion
workbench searches backwards and uses the exchange rate associated with
the most recent prior date. For example, if a currency relationship has a
conversion rate and effective date of 99/01/01 and you enter 99/06/30 in
this field, the workbench uses the exchange rate for 99/01/01.
4. In the To Currency Code field, type the code of the currency that you are
converting your base currency to, for example, EUR for euro.
5. In the Exchange Rate field, type a default exchange rate to be used by the
ordered and additional conversion jobs. See Euro Exchange Rates.
All ordered and additional conversion jobs, except the Multi-Currency

Intercompany Conversion and Price Variable Conversion jobs, use the
exchange rate in this field along with the currency conversion method in the
following field to convert records without a currency code, company, or

105
business unit. The Multi-Currency Intercompany Conversion and Price

Variable Conversion Jobs use the conversion rate in the Currency Exchange
Rates table (F0015), based on the companies being converted.
6. In the Currency Conversion Method field, enter Z (divisor). This method is
used by the ordered and additional conversion jobs when converting records
to the euro.
7. In the Begin Company field, do one of the following:
• To convert one company, enter the number of the specific

company.
• To convert a range of companies, enter the first number in the
range.
• To convert several companies that are not in a range, enter each
company number.
The company in the Begin and End Company fields must exist in the
Company Constants table (F0010).
8. In the End Company field, do one of the following and click OK:
• To convert one company, leave this field blank. The system

automatically fills the End Company field with the Begin Company
value you entered.
• To convert a range of companies, enter the last number in the range
of companies.
• To convert several companies that are not in a range, leave this field
blank. The system automatically fills the End Company field with
the Begin Company value you entered.
The following example shows the constants for a conversion plan with
several companies that are not in a range.

106
Euro Exchange Rates
As of 1 January 1999, the euro exchange rate was irrevocably fixed to EMU
member currencies in 11 of the 12 participating EMU countries. Greece, the 12th
and latest country to join the EMU, had its currency irrevocably fixed to the euro
as of 1 January 2001.
International currencies are quoted as an exchange rate against the euro, and not
against the national EMU currencies. The official conversion rates are as follows:
1 euro equals
40.3399 Belgian francs

1.95583 German marks
166.386 Spanish pesetas
6.55957 French francs
0.787564 Irish pounds
1936.27 Italian lire
40.3399 Luxembourg francs
2.20371 Dutch guilders
13.7603 Austrian schillings
200.482 Portuguese escudos
5.94573 Finnish markka
340.750 Greek drachmas

107
Preventing Audit Records from Being Created
Audit records show transaction amounts before and after the euro conversion and
the conversion rate used to calculate the new euro amount. All euro conversion
programs automatically create audit records for each table and write the records to
the Conversion Audit table (F0086), although the conversion programs do not
require that you create audit records.
• If you want audit records created for all tables in a plan, skip this task
(Preventing Audit Records from Being Created).
If there is no record for a plan in the Audit Record table (F0085), the
conversion programs automatically create audit records.
• If you do not want audit records created for all tables, you must complete
this task (Preventing Audit Records from Being Created) and create a record for the
plan.
If there is a record for a plan in the Audit Record table (F0085), the
conversion programs search the table and determine whether to create or
prevent audit records from being created. You can create audit records for
some tables, while preventing audit records from being created for others.
Caution
Creating audit records during the euro conversion can require a substantial amount
of disk space. For more information, see Sizing Impacts on the F0086 Table.
Be prudent in deciding whether you need to create an audit trail for a table. Check
with your auditors to find out which audit trails are required by your company and
the EMU member nation in which you conduct business.
To produce a report, you can create and run a query or UBE over the F0086 table.
To do this, you will need the composite key for each table converted. See Composite
Keys. If you choose to run a UBE, create the report based on the F0086 Audit
Report Model that can be accessed from the Setup and Conversion menu
(G97UE9A). See Sample: Euro Conversion Audit Report for a sample report that is
based on the model.
► To prevent audit records from being created
J.D. Edwards provides a model plan (ZJDE) that contains a list of tables converted
by the euro conversion workbench and post-conversion jobs. Copy the tables from
the model plan into your conversion plan, and then change the flag for each table
in which you do not want audit records created. (Remember, the default value is to
create an audit record for a table.)

108
the Setup and Conversion menu (G97UE9A), choose Audit Record Maintenance.
1. On Work with Audit Definitions, choose ZJDE (model plan) from the list
of plans.

109
2. Click Select to view the tables for model plan ZJDE on Audit Definition
Revisions.
3. If an error message appears, locate any tables that are highlighted and delete
them.
4. The following tables are missing in the ZJDE plan. Add the tables that apply
to the release and systems at your site.
• OneWorld B73.3.1: F43008 and F4915

• OneWorld B73.3.2: F43008, F4915, F41181, F3908, F3910, F39061,
F390619, F39062, F39063, F390639, F39064, F390649, F39120W,
and F39121W
• OneWorld Xe: F43008, F4915, F41181, F74800, F3908, F3910,
F39061, F390619, F39062, F39063, F390639, F39064, F390649,
F39120W, and F39121W
5. Verify that the F0018 table exists in the ZJDE plan and add it, if necessary.
6. Click OK, and then Cancel.
7. On Work with Audit Definitions, choose the model plan ZJDE and click
Copy.

110
8. On Audit Definition Revisions, enter your plan name.
9. Change the Audit Record Flag to 1 for any tables that do not require an
audit record or are not used at your site. The Audit Record Flag controls
whether the creation of an audit record is suppressed during the conversion.
Valid values are:
• 0 (or Blank) = no (default), do not suppress the creation of an audit

record. That is, create an audit record. Audit records are written to
the Conversion Audit table (F0086).
• 1 = yes, suppress the creation of an audit record. That is, do not
create an audit record.
F03B11 and F0411 Tables
The F03B11 and F0411 tables write tax records to the F0018. If you prevent
audit records from being created for the F03B11 or F0411 table, remember
to do the same for the F0018 table.

111
10. Click OK, and then Cancel.
11. On Work with Audit Definitions, verify that your new plan appears and
click Close.
12. To remove a plan that was entered in error, read the following caution and
continue to step 12, if appropriate:
Caution
The Delete option on this form does not check the status of a plan before
removing it. Make sure that the plan you want to delete has never been run.
13. Highlight the plan on Work with Audit Definitions and click Delete. Then
click OK in the Confirm Delete window.
Updating the F9843 Table
The Table Conversion - JDE Scheduler table (F9843), which contains the euro
conversion programs, is not completely accurate in OneWorld Xe. To update the
F9843 table, you must remove and add some conversion programs.
The system loads records from the F9843 table into the euro workbench when you
define a conversion plan. For this reason, make sure that the contents of the F9843
table are accurate before you define any conversion plans.

112
► To update the F9843 table
For a list of the euro conversion programs and the order in which they run, see
Euro Conversion Workbench UBEs.
From the Advanced Operations menu (GH9611), choose Table Conversion

Scheduler.
1. On Work with Table Conversion Scheduler, enter 8 (for euro conversion

records) in the Conversion Type field and click Find.
2. (OneWorld Xe only). To remove the following conversion programs from

the workbench, choose the program and click Delete:
• R891206EB
• R891301EB
• R8930008E
• R9838011E
3. The conversion programs listed in the following tables are missing from the
workbench. To add the programs that apply to the release and systems at
your site, click Add, enter the values in the table, and click OK. Then
continue to step 4.
OneWorld B73.3.1
Conv Table From and Conv Dep Conversion Version One

Type Name To Release Seq Seq Program World
Only
8 F4915 *CURRENT 217 0 R894915E XJDE0001 Y
OneWorld B73.3.2

Only

113

Only
8 F39120W *CURRENT 227 0 R8939120WE XJDE0001 Y
One World Xe

Only

114

Only
4. Click Cancel to return to Work with Table Conversion Scheduler.
5. Verify the results before proceeding to the next task, Defining a Conversion
Plan.
Defining a Conversion Plan
When you define a conversion plan, you enter a description and status, and the
system loads the euro conversion programs into the plan. To define a conversion
plan, J.D. Edwards created a new front-end application called the Euro
Conversion Planner/Workbench (P9840E). This application interfaces with the
existing Installation Planner (P9840) and Control Table Workbench (P98413)
applications and does the following:
• Provides an exit to the Conversion Planner form, which contains the euro
conversion programs for a plan. This form is described in the steps for this
task.
• Provides an exit to the Conversion Workbench form, which you use to run
the euro conversion programs. This form is described in Running the Euro
Conversion Workbench.

115
► To define a conversion plan
Locate the list of J.D. Edwards systems that you use. This list was compiled before
the conversion and is described in Completing System-Level Prerequisites. You will refer
to this list in step 8 below.
the Pre-Conversion Setup menu (G97UE9A), choose Euro Conversion
Planner/Workbench.
1. On Work with Euro Conversion Plans, click Add.
2. On Maintain Euro Conversion Plans, type the plan name for the
conversion. This is the same plan name you entered in the task Setting Up
Constants for a Conversion Plan.
Do not leave this field blank. If you do, the system will enter a default plan
name (ZJDE), which will appear when you return to the Work with Euro
Conversion Plans form.
3. Type a meaningful description in the Description field, especially if you set
up more than one euro conversion plan. This is a 30-character field.
4. Enter 10 (In Planning) in the Plan Status field. This field identifies the stage
of a plan; 10 is the first stage.

116
5. Click OK and the system does the following:
• Creates a plan master in the Installation Plan Master table (F9840).

• Creates an environment record in the Environment Plan Detail table
(F98403).
• Loads all type 8 programs from the Table Conversion JDE
Scheduler table (F9843) to the Table Conversion Scheduler table
(F98405). This loads all euro conversion programs into your plan.
6. To review the euro conversion programs in your plan, choose your plan on
Work with Euro Conversion Plans.
7. Choose Conversion Planner from the Row menu.

117
On the Euro Conversion Planner, note the following:

• The New Environment and Previous Environment fields contain
the same name. This is because you run the conversion and convert
your data in the same environment.
• The Conversion Sequence field begins at 101 for the first conversion
program and is numbered sequentially through the last conversion
program.
• The Dependency Sequence field is set to 0 (zero) for all conversion
programs except the following:
• R8951911E, which is set to 119. (Note that 119 is the
conversion sequence for R890911E.) R8951911E is
dependent on the successful completion of R890911E, that
is, R890911E must run before R8951911E.
For a list that shows the sequence in which the conversion programs run,
see Euro Conversion Workbench UBEs.
8. Refer to the list of J.D. Edwards systems that you use, as described in
Checklist: System-Level Prerequisites. Based on the list, determine which systems
you do not use and continue with the next step.
9. To improve processing time, remove any conversion programs that do not

apply to your plan. On Euro Conversion Planner, choose the row that
corresponds to the program and click Delete.
10. If you inadvertently deleted programs in the previous step, choose Auto
Load from the Form menu. This reloads all type 8 (euro conversion)
programs into your plan and resets the plan status to 10 (In Planning).
11. If you add a conversion program, click Save.
12. Press Cancel when you are satisfied with the contents of your plan.
13. On Work with Euro Conversion Plans, click Close.
14. See Running the Euro Conversion Workbench for the next task.

118
Running the Euro Conversion Workbench
After you complete the setup requirements described in Setting Up a Euro Conversion
Plan, you can proceed with this task.
When you run the euro conversion workbench, you run it by conversion plan and
the system converts the records for the companies defined in that plan. Some
clients will set up only one conversion plan, whereas others will set up multiple
plans. (See Environments and Euro Conversion Plans for more information.) Clients
with multiple plans must run the euro conversion workbench one plan at a time
and upon successful completion, delete the conversion log before running the next
plan.
Remember that you must run the euro conversion workbench and complete all
satisfied with the results of the euro conversion in your test environment, you will
complete all of the tasks again in your production environment and "go live."
Before You Begin

G To review the conversion programs for a specific conversion plan, print the
grid as follows:
On Work with Euro Conversion Plans, choose a conversion plan and then
choose Conversion Workbench from the Row menu. On Euro Conversion
Workbench, choose Grid -> Print from the Preferences menu.
Alternatively, you can export the data to a spreadsheet and print the
spreadsheet.
G Print a copy of the list that shows the sequence in which the euro
conversion programs must run in Euro Conversion Workbench UBEs. You will
need to refer to this list throughout the euro conversion.
G To reduce processing time, consider running multiple versions of the A/R
conversion and F0911 conversion programs. For more information, visit the
Euro Base Currency Conversion site on the Knowledge Garden. The path is
Worldwide Topics > Euro Base Currency Conversion > Global Support
Services > OneWorld Knowledge Documents > Application.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Running the Euro Conversion Workbench
119
G Make sure you back up all data before running the euro conversion
workbench.
G Make sure you are signed on to a client workstation with a full install.
Although you submit the euro conversion and review the results from a
workstation, you should process the conversion on the enterprise server for
performance purposes.
G Make sure you are signed on to the environment that contains the
companies you want to convert to the euro. Ensure that no one else is
signed on to the environment.
Coexistence: Before Running the OneWorld Conversion
The following applies to clients with coexistence who successfully ran and
completed most of the euro conversion in WorldSoftware and now need to run
the remaining conversion programs over their Accounts Receivable tables in
OneWorld.
If you successfully ran and completed the euro conversion using the E9 scheduler
(WorldSoftware) and plan to convert your OneWorld A/R tables using the
workbench (OneWorld), make sure you back up the converted F0018 table
(World) before you run the euro conversion for OneWorld A/R.
The euro conversion programs for the F03B11 table as well as the F0411 and
F0911 tables convert the F0018 table. If your F03B11 conversion fails, you will
need to restore the F0018 table (which you converted in World) and the F03B11
table before you rerun the A/R conversion in OneWorld.
► To run the euro conversion workbench
On the Setup and Conversion menu (G97UE9A), choose Euro Conversion

Planner/Workbench.
1. On Work with Euro Conversion Plans, click Find.
2. Choose the plan in which to run the euro conversion.
3. From the Row menu, choose Conversion Workbench.
120
The New Status field on this form always has a default value of 60, which
should not be changed. This default value reflects the detail status that each
conversion program should have upon successful completion.
4. For the mode, choose Synch.
Each conversion program runs to completion before another one is

launched, regardless of whether you have a single job queue or multiple job
queues. The system creates one or multiple Table Conversion/Merge Driver
reports (R98405), based on the following:
• If you convert all tables and run the conversion from a server and
synchronously, the system creates a separate report for each
conversion program, indicating whether it completed normally.
• If you convert selected tables and run the conversion synchronously,
the system creates a separate report for each conversion program.
Caution
When you complete the next step, the system immediately begins the euro
conversion. Make sure you have selected the correct plan and that you are
ready to proceed with the actual conversion before continuing to the next
step.
5. From the Form menu, choose Convert All.
J.D. Edwards recommends that you convert all tables when you run the
euro conversion workbench for a plan; however, you can convert selected
tables by choosing Convert Selected from the Form menu or the menu bar.
6. See Verifying the Status of the Euro Conversion for the next task.
121
During the Euro Conversion
The following describes some things you can expect while the euro conversion is
processing:
• An hourglass icon appears on the Euro Conversion Workbench form and

remains there while the conversion jobs are processing.
• Upon completion of each conversion job, an online report that shows
exceptions (errors) appears. If there are no exceptions, the online report
displays header report information only and is blank.
• You cannot perform any functions on the Euro Conversion Workbench
form.
• You cannot run any other application jobs.
• You can track the progress of the conversion jobs by doing one of the
following:
• View the Table Conversion/Merge Log. To access this program, use
the fast path and enter P984052, or go to the System Installation
Tools menu (GH961) and select the program.
• Work with Submitted Reports. To access this tool, use the fast path
and enter P986116, or go to the System Administration Tools menu
(GH9011) and select the program.
Coexistence: After Running the OneWorld Conversion
The following applies to clients with coexistence who successfully ran and
completed most of the euro conversion in OneWorld and now need to run the
remaining conversion programs in WorldSoftware.
After you successfully complete the OneWorld conversion programs, you must
delete the Conversion Audit table (F0086) in your data library (DTALIB). The
F0086 table is created when you enter the conversion constants for a plan (P0087).
Later, when you run the conversion programs, converted records are then written
to the table.
If you do not delete the F0086 table, which contains OneWorld converted records,
before you enter conversion constants for a plan in World, the P0087 program in
World will not create another F0086 table since is already exists. Therefore, the
conversion programs in World will not write records to the F0086 table.
122
Verifying the Status of the Euro Conversion
After you run the OneWorld euro conversion workbench for a plan, you must
verify its status. Each conversion program within a plan must have a status of 60
(Installed) for the euro conversion to have completed successfully. When all
conversion programs within a plan have a status of 60, the euro conversion is
complete.
The following User Defined Code table (H90/DS) lists the various statuses that a
program can have throughout a OneWorld installation or conversion. The statuses
that apply to the euro conversion programs are 10, 45, 50, 60, and 70.
Remember that you must verify the status of the euro conversion and complete all
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Verifying the Status of the Euro Conversion
123
► To verify the status of the euro conversion
From the Setup and Conversion menu (G97UE9A), choose Euro Conversion
Planner/Workbench.
1. On Work with Euro Conversion Plans, click Find to view a list of plan
names.
2. Choose the conversion plan that you ran and choose Conversion
Workbench from the Row menu.
3. On Euro Conversion Workbench, review the Detail Status field in the grid
area. This field shows the status of each conversion program.
4. Scroll down (several times) to review the status of each program in the plan.
5. Depending on the status of the programs, proceed to step 6 under one of

the following headings:
• All programs have a status of 60 (Installed)

• One or more programs has a status of 50 (Failed)
124
All Programs Have a Status of 60
If all programs in the plan have a status of 60 (Installed), complete the

following steps:
6. On Euro Conversion Workbench, click the Next button in the tool bar.
(This button is activated only if all conversion programs have a status of 60.)
The system displays the Congratulations! form.
7. Click Finish to complete the euro conversion. This updates the plan status
to 60 (Installed) on the Work with Euro Conversion Plans form.
8. Verify the plan status on Work with Euro Conversion Plans and click Close.
9. See Reviewing the Euro Conversion Reports and Reviewing the Euro Conversion Audit
Tables for the next tasks.
125
Note
After reviewing the euro conversion reports and audit tables, clients with
multiple conversion plans must delete the conversion log for a plan before
running another plan. See Deleting the Conversion Log for a Plan.
One or More Programs Has a Status of 50
If one or more programs in the plan have a status of 50 (Failed), complete

the following steps:
6. Determine what caused the conversion to fail and correct the errors. See
Reviewing the Euro Conversion Reports and Reviewing the Euro Conversion Audit Tables
for more information.
7. After correcting the errors identified in the previous step, restore the
necessary tables and rerun the euro conversion program. See Rerunning a Euro
Conversion Program.
126
Reviewing the Euro Conversion Reports
After you verify the status of the euro conversion, you must review the euro
conversion reports generated by the conversion. It is very important that you
review these reports before continuing with the euro conversion. If a conversion
program completed with errors, you must review the reports, correct the errors,
and rerun the conversion program.
When you run the euro conversion workbench, the system generates the following:
• Table Conversion/Merge Driver report (R98405). A one-line summary

report that indicates whether a conversion program completed normally.
For a sample report, see Sample: Table Conversion/Merge Driver Report.
• View Log. An online view of each conversion program by object (table)
name, indicating whether the conversion finished normally.
• Table conversion report. This detailed report shows the record and error if
any errors occurred during a conversion. The conversion program number
appears in the upper left corner of this report. For a sample report
(R8974412E), see Sample: Table Conversion Report.
Topics
G Table Conversion/Merge Driver Report (R98405)
G Viewing the Conversion Log Records
G Table Conversion Report
Table Conversion/Merge Driver Report
The Table Conversion/Merge Driver report (R98405) lists each conversion

program that ran and its status. To access the report, choose Submitted Reports
from the System Administration Tools menu (GH9011).
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Reviewing the Euro Conversion Reports
127
A conversion program on this report will have one of the following statuses:
• Completed Normally
• Completed with Errors
The system creates one or multiple Table Conversion/Merge Driver (R98405)
reports, based on the following:
• If you convert all tables and run the conversion from a server and
synchronously, the system creates a separate report for each conversion
program, indicating whether it completed normally.
• If you convert selected tables and run the conversion synchronously, the
system creates a separate report for each conversion program.
See Sample: Table Conversion/Merge Driver Report for a sample report (R98405).
Viewing the Conversion Log Records
The system creates conversion log records and stores them in the Table
Conversion History Log (F984052). You can view the conversion status of the log
records by plan name, by object (table) name, and so on. Records in this log will
have one of the following statuses:
• 2 Conversion Finished Normally

• 3 Conversion Finished Abnormally
The system creates one log record for each conversion program in a plan, along
with the date and time of the conversion. If a conversion program finishes
abnormally, another log is created when you rerun the conversion program. This
means that you could potentially have more than one log for a conversion
program.
► To view the conversion log records
Workbench/Planner.
1. On Work with Euro Conversion Plans, click Find to see a list of conversion
plans.
2. Choose a plan and choose Conversion Workbench from the Row menu.
3. On Euro Conversion Workbench, choose View Log from the Form menu.
128
4. On Table Conversion/Merge Log, verify that the plan appears in the Plan
Name field in the QBE line and click Find.
Table Conversion Report
To review detailed information about a conversion program that completed with

errors, use the table conversion report. To access the report, choose Submitted
Reports from the System Administration Tools menu (GH9011).
This report lists warnings and errors that occurred during the table conversion.
Make sure that you review the warnings and research and correct any errors that
appear on the report. See Sample: Table Conversion Report for a report (R8974412E)
that shows the results of converted F74412 records.
Typically, clients who correct their integrity reports and clean up their tables before
the conversion have fewer messages to review and correct on the table conversion
reports.
If you need assistance in determining the cause of a message or how to correct an

error, contact the appropriate application or technical support services
representative.
Examples of Error Messages
Some messages on the table conversion report can be readily explained and may
not need to be researched, such as, messages associated with records that
originated from an external source.
Other messages, such as minor rounding exceptions, begin with the word
WARNING and are informational messages that may not need to be corrected.
129
The message WARNING - Amounts Round to Zero prints on the table conversion
report when the conversion rounds a converted amount for a record to zero. For
example, if the conversion rounds the converted amount of 1 Portuguese escudo
to zero or the converted amount of 9 Italian lira to zero, it prints a warning
message on the report. Another message, which is similar in wording but different
in meaning is WARNING - Amounts Converted to Zero. This prints on the report
when the conversion calculates the new euro amount and the result is zero.
Still other messages will need to be researched and, if necessary, corrected. Review
the following for examples of messages that might appear on the table conversion
report. You must correct the errors associated with these messages before you
rerun the conversion.
Error Message Cause and Solution
From currency same The original base company currency is the same as the "convert
as to currency to" currency. This error message appears if the base currency of
the company you are trying to convert is the same as the
currency you are converting to.
Review the conversion plan and determine the base currency of
each company. Verify the currency that you are converting to.
The currencies cannot be the same. Correct your plan
accordingly.
Currency exchange The exchange rate between the original base company currency
rate not found and the "convert to" currency does not exist in the Currency
Exchange Rates file (F0015). This error message appears if you
have not set up a currency relationship and conversion rate
between the base currency of your company and the euro.
Set up the currency relationship and exchange rate on the Set
Daily Transaction Rates screen. See Setting Up Euro Currency
Relationships in the Euro Implementation Guide.
A currency code has This error message appears if you try to convert a currency-
been defined for the specific ledger such as XA, YA, or ZA. (The euro conversion
ledger type in UDC does not convert currency-specific ledgers.)
09/LT and F0025
If you want to convert a particular currency-specific ledger,
remove the currency code for the ledger type in the following:
• Special Handling Code field in the UDC table for 09/LT
• Denominated Currency Code field in the Ledger Type

Master Setup (P0025)
130
Error Message Cause and Solution
Amount must balance The debit side and credit side of an entry do not balance to zero.
to zero
This error message might appear if an adjusting entry (AE)
document was posted, but the corresponding invoice or voucher
was not posted, or if the document is for budget entries, which
do not have to balance.
Research the documents that do not balance and determine
whether you need to take any action, for example, post
transactions.
131
Reviewing the Euro Conversion Audit Tables
After you verify the status of the euro conversion, you must review the euro
conversion audit records generated by the conversion. It is very important that you
review your audit records before continuing with the euro conversion.
For internal purposes, make sure your MIS or IT department writes and prints the
necessary reports for your company auditors. For external purposes, make sure
that any legal audit reports contain the information required by your local or
national governments.
Audit records show transaction amounts before and after the euro conversion and
the exchange rate used to calculate the new euro amount. All euro conversion
programs automatically create audit records for each table and write the records to
the Conversion Audit table (F0086), unless you prevent them from being created.
(See Preventing Audit Records from Being Created for more information.)
The records in the audit table contain the original currency amount, exchange rate,
and new euro amount. This table is the only audit trail for the euro conversion
programs. Examine your audit table carefully.
You can review the F0086 table using the Universal Table Browser. To do this,
sort the contents of the audit table by plan name and converted table, or other
criteria, using the query-by-example (QBE) line.
You can run a query or UBE over the F0086 table. To do this, you will need the
composite key for each file converted. See OneWorld Composite Keys. If you choose
to run a UBE, create the report based on the F0086 Audit Report Mode, which is
accessed from the Setup and Conversion menu (G97UE9A). See Sample: Euro
Conversion Audit Report for a sample report based on the model.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Reviewing the Euro Conversion Audit Tables
132
Exchange Rate Fields in the Conversion Audit Table
The three exchange rate fields that appear in the Conversion Audit table (F0086)
are described below:
Exchange Rate Field Description
AUCRR Currency This is the exchange rate used to convert the domestic amount to the
Conversion Exchange new base currency. This rate is retrieved from the Currency
Rate Exchange Rates table (F0015).
AUCRRB Currency This is the exchange rate on the original transaction before the
Exchange Rate - Before conversion. This rate was either retrieved from the F0015 table or
entered manually as an override (spot) rate during data entry. If the
original transaction was domestic only, this field is blank.
AUCERA Currency This is the exchange rate on the original transaction after the
Exchange Rate - After conversion.
If the original transaction was domestic only, this is the rate used to
convert the domestic amount to the new euro amount. This rate is
retrieved from the F0015 table and is the same as the AUCRR field.
If the original transaction was foreign and the transaction currency is
not the same as the new base company currency (that is, the
transaction currency is not the euro), this is a calculated rate between
the converted domestic amount and the foreign amount. To derive
the calculated rate, the foreign amount is divided by the converted
domestic amount.
If the original transaction was foreign and the transaction currency is
the same as the new base company currency (that is, the transaction
currency and new base company currency are both the euro), this
field is blank. The transaction is now domestic only.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Reviewing the Euro Conversion Audit Tables
133
Rerunning a Euro Conversion Program
You might need to rerun a euro conversion program under the following
circumstances:
• During the conversion - If a conversion program fails when you run the
euro conversion workbench.
• After the conversion - If you need to rerun an ordered or additional
conversion job (over the same set of data).
• After the conversion - If you discover data problems when you review the
post-conversion integrity reports.
Before you rerun a euro conversion program, determine where you are in the euro
conversion process and whether you have run the Company Currency Codes
Conversion (R890010E) job. The Company Currency Codes Conversion is an
ordered conversion job that changes the base currency code for companies in a
plan to the euro (EUR) in the Company Constants table (F0010).
Before You Begin

G Restore the table associated with the conversion program that you need to
rerun, if necessary. For information about restoring a backup file, see
Backing Up OneWorld Tables on Servers in the OneWorld Server and Workstation
Administration Guide.
Depending on where the conversion program failed during processing, you
might have to restore tables before rerunning the program. If the conversion
program failed because there was no data selected, you should not have to
restore any tables.
G Make sure that everyone is signed off. No one should be entering or
modifying data, running integrity reports, reposting, and so on for the
companies in which you need to rerun a conversion program.
Topics
G Rerunning a Conversion Program Before Updating the F0010 Table
G Rerunning a Conversion Program After Updating the F0010 Table
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Rerunning a Euro Conversion Program

134
Rerunning a Conversion Program Before Updating the F0010 Table
The steps in this task apply to clients who rerun a conversion program before
running Company Currency Codes Conversion (R890010E), an ordered
conversion job that updates the F0010 table.
If a euro conversion program fails when you run the euro conversion workbench,
you must review the euro conversion reports, correct the errors, and rerun the
conversion program.
► To rerun a conversion program before updating the F0010 table
Do not reset the status of the failed conversion program on the Euro Conversion
Workbench form; leave it as is.
Planner/Workbench.
plans.
2. Choose the plan that contains the conversion program that failed.
4. To selectively rerun one or more failed conversions, do one of the

following:
• To convert one table, choose the row that corresponds to the table
and choose Convert Selected from the Row menu.

135
• To convert several tables, press Ctrl (Control) and choose the rows
that correspond to the tables. Then choose Convert Selected from
the Row menu.
Caution
Do not choose Convert All from the Row menu to rerun one or more failed
conversions. Although the workbench reruns only those programs with a
status of less than 60 (Installed), the processing time required is prohibitive.
Rerunning a Conversion Program After Updating the F0010 Table
The steps in this task apply to clients who rerun a conversion program after
running Company Currency Codes Conversion (R890010E), an ordered
conversion job that updates the F0010 table.
If you need to rerun an additional conversion job over the same data or if data
problems appear on a post-conversion integrity report, you must follow the steps
in this task. Make sure you research and correct the data problems before you
rerun the euro conversion program.
► To rerun a conversion program after updating the F0010 table
Caution
If you do not complete steps 1 - 4 be aware that a euro conversion program might
zero out amounts in a table for all companies in a plan as you would be converting
from EUR to EUR.
From the Organization & Account Setup menu (G09411), choose Company
Names & Numbers.
1. On Work with Companies, click Find to view all companies.
2. Choose the company associated with the plan and click Select.
3. On Company Setup, click the Currency tab and change the currency code
back to the base currency code before the euro conversion.
For example, for a French franc company, change the currency code from
EUR back to FRF.
4. Repeat step 3 for each company in the plan.

136
To rerun a conversion program, complete the remaining steps:

5. From the Setup and Conversion menu (G97UE9A), choose Euro
Conversion Planner/Workbench.
plans.
7. Choose the plan that contains the conversion program that you need to
rerun.
9. To selectively rerun one or more conversions, do one of the following:
• To convert one table, choose the row that corresponds to the table
and then choose Convert Selected from the Row menu.
• To convert several tables, press Ctrl (Control) and choose the rows
that correspond to the tables. Then choose Convert Selected from
the Row menu.
Caution
Do not choose Convert All from the Row menu to rerun one or more failed
conversions. Although the workbench reruns only those programs with a
status of less than 60 (Installed), the processing time required is prohibitive.
10. When you are satisfied with the results, run the Company Currency Codes
Conversion job again to return the company currency codes back to EUR.

137
Deleting the Conversion Log for a Plan
Deleting the conversion log for a plan clears out the log and all associated log
records in the Table Conversion History Log table (F984052) so that you can run
another plan in the same environment or rerun the same plan without getting
warning messages. This task applies to the following:
• Clients who have multiple plans to convert in the same environment. After
you run the euro conversion workbench for a plan and verify that it
completed successfully, you must delete the conversion log for the plan
before running the workbench for another plan.
• Clients who decide to "start over" and run the conversion again for the
same plan. If you have an excessive number of programs that failed during
the conversion and you decide to run the workbench again, you must first
delete the conversion log for the plan.
If you do not delete the conversion log and you run the euro conversion again,
whether over another plan or the same plan, you will receive the following warning
message for each conversion program in the plan.
This warning message will appear each time the Euro Conversion Workbench or
the Euro Conversion Planner form loads conversion records.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Deleting the Conversion Log for a Plan
138
► To delete the conversion log for a plan
Planner/Workbench.
plans.
2. Choose the conversion plan that completed successfully. (The plan status
must be 60.)
4. On Euro Conversion Workbench, choose View Log from the Form menu.
5. On Table Conversion/Merge Log, verify that the plan appears in the Plan
Name field in the QBE line and click Find.
139
The system displays the conversion log records for the plan, which are
stored in the Table Conversion History Log (F984052). These are not the
same records that appear on the Euro Conversion Workbench form.
6. To select all conversion log records, choose the first record in the grid.
7. Press Shift, scroll to the bottom, and choose the last record.
8. Click Delete.
9. On Confirm Delete, click OK to proceed.
10. Verify that no records appear in the log and click Close three times to exit
and return to the menu.
11. To run another conversion plan in the same environment, see Running the
Euro Conversion Workbench.
140
Before Running Ordered and Additional Conversion Jobs
Before you run an ordered or additional conversion job, you must decide which
records you want the job to convert to the euro and what exchange rate to use.
Based on that decision, you will enter a plan name in the processing option and
specify certain criteria in the data selection for the job. Additionally, you must
decide whether you want to create audit records for the table converted by the
ordered or additional conversion job.
To change the plan exchange rate and prevent audit records from being created,
you use the first two programs on the Pre-Conversion Setup menu (G97UE9A).
Remember that you must complete these tasks and all remaining tasks in this
the euro conversion in your test environment, complete all of the tasks again in
your production environment and "go live."
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Before Running Ordered and Additional Conversion
Jobs 141
Topics
G Changing the Plan Exchange Rate Before Running a Job
G Preventing Audit Records from Being Created for a Job
Changing the Plan Exchange Rate Before Running a Job
Each time you run an ordered or additional conversion job, you must enter a plan
name in the processing option. These jobs use the plan name to determine the
following:
• The currency to convert the records to.

• The conversion rate to use when converting the records. (This applies to all
ordered and additional conversion jobs except the Multi-Currency
Intercompany Conversion and the Price Variable Conversion jobs, which
use the exchange rate in the F0015 table.)
Depending on the ordered or additional conversion job you run and the records
you want to convert, you might run a job multiple times for a plan and change the
plan exchange rate each time. The following example illustrates this.
The Price by Item Conversion is an additional conversion job that converts two
amounts in the Price by Item table. At your company, certain price rules
correspond to certain currencies, which means that you set up standard price
adjustments by currency. To convert records for the different currencies, you will
run the Price by Item Conversion for a plan multiple times, entering the plan name
in the processing option once and changing the exchange rate for the plan each
time you run the job to coincide with the currency on the records you convert.
Note
Clients who set up their conversion plans by currency can change the plan name in
the processing option each time they run an ordered or additional conversion job,
instead of manually changing the exchange rate on a plan.
► To change the plan exchange rate before running a job
From the Setup and Conversion menu (G9UE9A), choose Conversion Constants.
1. On Work with Conversion Plans, click Find to see a list of conversion plans.
Jobs 142
The rate in the Exchange Rate field is used by all the ordered and additional
conversion jobs, except Multi-Currency Intercompany Conversion and Price
Variable Conversion, to convert amounts to the euro. The Multi-Currency
Intercompany Conversion and Price Variable Conversion jobs use the
exchange rate in the F0015 table, based on the companies being converted.
2. To change the exchange rate for a specific conversion job, choose the plan
and click Select.
3. On Conversion Plan Revisions, change the amount in the Exchange Rate

field and click OK.
4. On Work with Conversion Plans, verify the exchange rate and click Close.
Jobs 143
Preventing Audit Records from Being Created for a Job
All ordered and additional conversion jobs automatically create audit records for a
table and write the records to the Conversion Audit table (F0086). If you want
audit records created for all tables converted by the ordered and additional
conversion jobs for a plan, skip this task. If you do not want audit records created,
you must complete the steps in this task.
See Conversion and Post-Conversion Tables for a list of tables converted by the ordered
and additional conversion jobs.
Caution
Depending on the size of the tables to be converted, creating audit records can
require a substantial amount of disk space. For more information, see Sizing Impacts
on the F0086 Table.
► To prevent audit records from being created for a job
From the Setup and Conversion menu (G97UE9A), choose Audit Record
Maintenance.
1. Depending on whether the plan you want to use appears on the Audit
Record Maintenance form, proceed to step 2 or step 3.
2. If the plan appears, choose the plan and click Select. On Audit Definition
Revisions, change the Audit Record Flag field to 1 for each table that you do
not want audit records created for and click OK.
Jobs 144
3. If the plan does not appear, click Add and complete the remaining steps.
4. On Audit Definition Revisions, enter the table that corresponds to each

ordered and additional conversion job that you plan to run in the File Name
field.
5. Enter one of the following values in the Audit Record field for each table
and click OK:
• 1 - do not create an audit record

• 0 - create an audit record
Jobs 145
Running Ordered Conversion Jobs
This task consists of a checklist that has two check-off (√) columns - one for your
test (TEST) environment and the other for your production (PROD) environment.
Remember that you must run the ordered conversion jobs and complete all
After you run the euro conversion workbench and verify that the conversion has
successfully completed, you run the ordered conversion jobs. The ordered
conversion jobs are designed to run separately from the workbench conversion
jobs so that you can control:
• What exchange rate to use (based on a plan name), using the processing
option
• Which records to convert, using the data selection
For example, the euro conversion workbench does not convert amounts on
records without a currency code, company, or business unit. To convert those
amounts, you must run several ordered conversion jobs. Alternatively, you could
manually modify the records instead.
Each time you run an ordered conversion job, you specify a plan name in the
processing option. The system uses the exchange rate assigned to that plan to
convert amounts for all ordered conversion jobs, except the Multi-Currency
Intercompany Conversion and the Price Variable Conversion jobs, which use the
exchange rate in the F0015 table.
Each ordered conversion job is dependent on the successful completion of one or

more other ordered conversion jobs, so it is important that you run the jobs in the
sequence that they appear on the menu. You are required to run only the ordered
conversion jobs that apply to the J.D. Edwards systems you use. All clients must
run the Company Currency Codes Conversion job.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Running Ordered Conversion Jobs

146
The ordered conversion jobs are for the following:
• Configuration Management
• Multi-Currency Intercompany
• Distribution and Product Data Management
• Company Currency Codes (required)
• Multi-Currency Intercompany Post
Remember that you must run the ordered conversion jobs and complete all
remaining tasks first in your test environment, correcting any data issues in both
your test and production environments. Later, when you are satisfied with the
results of the euro conversion in your test environment, you will complete all of
the tasks again in your production environment and "go live."
Before You Begin

G Ensure that the exchange rate assigned to the plan is correct. If necessary,
change it on the Conversion Constants form (P0087). See Changing the Plan
Exchange Rate Before Running a Job for more information.
G For OneWorld releases B73.3.1, B73.3.2, and Xe, the following items on the
Ordered Conversion Jobs menu (G97UE901) are incorrect and should be
corrected.
G The version (XJDE0001) for the Company Currency Codes
Conversion job (R890010E) is corrupted and should be replaced.
G The Euro Currency Conversion job (R8930008E) should not appear
on this menu.
G The Integrity Reports job (R8909801EB) that appears on this menu
should be titled Multi-Currency Intercompany Post.
Visit the Euro Knowledge Garden site for more information. The path is
Services > OneWorld Knowledge Documents > Technical > Menu
Corrections.

147
► To run ordered conversion jobs
An example of the B73.3.1EURO and B73.3.2EURO menu appears below. Three

items on this menu are incorrect. See Before You Begin for more information.
Caution
Do not run an ordered conversion job more than one time over the same data.
Ordered conversion jobs convert amounts every time you run them, regardless of
whether the amounts have already been converted.
From the Euro Conversion menu (G97UE9), choose Ordered Conversion Jobs.
1. On Ordered Conversion Jobs, choose an ordered conversion job.
You must run the ordered conversion jobs in the order they appear on the
menu. For detailed information about the ordered conversion jobs, see
Checklist: Ordered Conversion Jobs.
2. On Work with Batch Versions, highlight the version.

148
3. From the Row menu, choose Processing Options.
All ordered conversion jobs, except the Multi-Currency Intercompany

Conversion and Price Variable Conversion jobs, use the exchange rate on
the plan you enter in this processing option. The Multi-Currency
Intercompany Conversion and Price Variable Conversion jobs use the
exchange rate in the F0015 table, based on the companies being converted.
4. Enter the plan name to use for the ordered conversion job and click OK.
5. On Work with Batch Versions, choose the version again and click Select to
access Version Prompting.
6. Enter the data selection and submit the job to batch, as usual.
Company Currency Codes Conversion

For the Company Currency Codes Conversion job, enter data selection for
one plan name only. Do not enter any other data selection. The plan name
must match the plan name you entered in the processing option.
Checklist: Ordered Conversion Jobs
The following conversion jobs are accessed from the Ordered Conversion Jobs
menu (G97UE90).

149
Configuration Management
Ordered Conversion Description TEST PROD

Job √ √
Assembly Inclusion To convert the price and cost amount fields in the
Conversion Assembly Inclusion Rules table (F3293), you must run the
(R893293EB) Assembly Inclusion Conversion job or change the fields
manually on the x-rule record. If most of your price and
cost fields contain factor values (which use a derived
calculation) and not monetary amounts, you might want to
manually change the factor values instead of running this
program. Or, if you run this program, make sure you
manually change the converted factor amount on your x-
rule records back to their original value afterwards.
The Assembly Inclusion Conversion job converts amounts
as follows:
• If rules are established by business unit and the

branch/plant on a record corresponds to a company
designated in a conversion plan, the job converts
amounts using the exchange rate stored in the
Currency Exchange Rates table (F0015).
• If rules are not established by business unit, the

branch/plant on a record is blank and the job
converts amounts using the plan exchange rate
assigned to a conversion plan, which is stored in the
Conversion Constants table (F0087).
Use the data selection to specify which records to convert.
The Assembly Inclusion Conversion job converts records
with a blank branch/plant every time it is run. If you run
this job more than one time, make sure you exclude blank
branch/plants in the data selection (Business Unit NE *
BLANK); otherwise, amounts without a branch/plant will
be converted again.

150

Job √ √
Rules Table Detail To convert the price amount field in the Rules Table Detail
Conversion table (F3283), you must run the Rules Table Detail
(R893283EB) Conversion job or change the field manually on a record.
The Rules Table Detail Conversion job converts amounts
as follows:
• If rules are established by business unit and the

branch/plant on a record corresponds to a company
designated in a conversion plan, the job converts
amounts using the exchange rate stored in the
Currency Exchange Rates table (F0015).
• If rules are not established by business unit, the

branch/plant on a record is blank and the job
converts amounts using the exchange rate assigned
to a conversion plan, which is stored in the
Conversion Constants table (F0087).
Use the data selection to specify which records to convert.
The Rules Table Detail Conversion job automatically
converts records with a blank branch/plant every time it is
run. If you run this job more than one time, make sure you
exclude blank branch/plants in the data selection (Business
Unit NE * BLANK); otherwise, amounts without a
branch/plant will be converted again.
Multicurrency Intercompany

Job √ √
Multi-Currency To convert multicurrency intercompany transactions that

Intercompany are automatically generated by the system, you must run
Conversion the Multi-Currency Intercompany Conversion job one
(R890911EB) time only and for all plans. For detailed information, see
Converting Multicurrency Intercompany Transactions.
Unlike the other ordered conversion jobs, the Multi-
Currency Intercompany Conversion job can convert
multiple currencies at the same time because the job
retrieves conversion rates from the Currency Exchange
Rates table (F0015), based on the companies you are
converting.

151
Distribution and Product Data Management

Job √ √
Item Cost Components To convert item cost component add-on records, you
Add-Ons must run the Item Cost Components Add-Ons
(R8930026EB) conversion job. This job converts the simulated factor,
rate amount, or both. It also converts the net added-
simulated cost. The simulated values are stored in the
Item Cost Component Add-Ons table (F30026).
Unlike the other ordered conversion jobs, this job has
processing options that you use to designate:
• Whether to convert the simulated factor, rate

amount, or both
• Which plan name to use to retrieve the exchange

rate
The Item Cost Components Add-Ons conversion job
does not convert frozen values. See Completing Post-
Conversion Tasks for information about running the
Simulated Rollup and Frozen Update programs.

152
Company Currency Codes (Required)
Coexistence: Clients with coexistence must run all ordered conversion jobs in
either World or OneWorld (not both) before running this job.
Ordered Conversion TEST PROD

Description
Job √ √
Company Currency Prerequisites: Complete all other ordered conversion jobs,

Codes Conversion except Multi-Currency Intercompany Post (if applicable).
(R890010E) Make sure you have deleted the corrupted version of this
job and added a new one. For more information, visit the
Euro Base Currency Conversion site on the Knowledge
Garden. The path is Worldwide Topics > Euro Base
Currency Conversion > Global Support Services >
OneWorld Knowledge Documents > Technical > Menu
Corrections.
The Company Currency Codes Conversion job is required
for each plan. This job changes the base currency to the
euro in the Company Constants table (F0010) for all
companies in a conversion plan. To determine the new
base currency, this job uses the currency code in the To
Currency Code field on the Conversion Plan Revisions
form (P0087).
Enter the plan name in the processing option only; do not
enter any data selection. See Sample: Company Currency
Conversion Report for a sample report.
Note: Instead of running this conversion job, you can
manually change the base currency of a company to the
euro on the Company Names & Numbers form (P0010),
menu G09411. (The Company Currency Codes
Conversion job does this automatically.)

153
Multicurrency Intercompany Post

Job √ √
Multi-Currency Prerequisites: Multi-Currency Intercompany Conversion

Intercompany Post (run one time only for all plans) and Company Currency
(R8909801EB) Codes Conversion (run one time for each plan).
The Multi-Currency Intercompany Post (R8909801EB) is
the same as the G/L Post program (R09801) except that it
does not update the Account Balances table (F0902),
which saves valuable processing time. To determine the
exchange rate, the R8909801EB uses the historical date
(HDGJ), if applicable, or the G/L date (DGJ). The
R8909801EB marks all entries as posted even though they
are not actually posted so that when you run the Repost
later in the conversion process the entries are selected and
updated to the F0902 table. For detailed information, see
Converting Multicurrency Intercompany Transactions.
Note: The R8909801EB does not convert a transaction if
the account or business unit was changed from a blank to
a non-blank posting edit code after the original transaction
was posted. This applies only to posting edit codes that
were originally blank and have since changed to a non-
blank value such as I (inactive), M (machine-generated), or
N (non-posting). See step 11 in the procedures for
Converting Multicurrency Intercompany Tranasctions for more
information.
Converting Multicurrency Intercompany Transactions
The euro conversion does not convert multicurrency intercompany transactions

that are automatically generated by the system. To convert these transactions, you
run the Multi-Currency Intercompany Conversion program one time only after
you have converted all companies and all plans. The Multi-Currency Intercompany
Conversion program converts amounts in the Account Ledger table (F0911) for all
intercompany transactions in which the base currency of the company associated
with the transaction is being converted to the euro.

154
To convert multicurrency intercompany transactions, the Multi-Currency

Intercompany Conversion program (R890911EB) first locates all AA transactions
with 1 in the GLALT1 field (the value 1 indicates that a multicurrency
intercompany transaction was automatically generated). It then does the following:
• Converts all transaction amounts on a journal entry if the company on the

first line (which is the company base currency) is the company you are
converting.
• Deletes the corresponding AE (offset) and AM (adjusting) entries for
companies you are not converting.
Note
The R890911E conversion program, which runs during the euro conversion,
deletes corresponding AE and AM entries for all companies converted. The
R890911EB conversion program, which runs after the euro conversion and
is described in this document, deletes corresponding AE and AM entries
only for those companies not converted. (The AE and AM entries are
recreated later during the post.) Review the following example for further
clarification.
If the first line of a journal entry is for a FRF company and the second line
is for a USD company, the following applies:
• R890911E deletes the corresponding AE and AM entries for the
FRF company (which is being converted).
• R890911EB deletes the corresponding AE and AM entries for the
USD company (which is not being converted).
• Clears the posted code and the GLALT1 field on the original transactions
and resets the batch to an approved (unposted) status so that you can post
them again.
• Prints a report that lists the batches that were reset to an approved
(unposted) status.
The R890911E euro conversion program, which runs in the workbench, converts
multicurrency intercompany transactions that are entered manually; however, you
will still need to review and, if necessary, correct them. This is described in step 4
of the procedures for this task.
Run the Multi-Currency Intercompany Conversion program one time only, after
converting all companies and all plans. This program, along with the Multi-
Currency Intercompany Post, makes the necessary adjustments to keep your
multicurrency intercompany transactions in balance.

155
Caution for Clients with Multiple Plans

Run the Multi-Currency Intercompany Conversion program one time only for all
plans. If you run this conversion program more than one time, it will convert all
records on a transaction each time, which will result in inaccurate amounts.
► To convert multicurrency intercompany transactions
Clients who have the Allow Multi-Currency Intercompany JE option on General

Accounting Constants set to Y must complete this task.
1. Verify that all companies and all plans have been converted successfully.
2. From the Ordered Conversion Jobs menu (G97UE90), choose Multi-

Currency Intercompany Conversion. Do not run this job more than one
time.
3. From the Ordered Conversion Jobs menu (G97UE90), run the Company
Currency Codes Conversion one time for each plan.
This job updates the base currency code in the Company Constants table
(F0010) for all companies in a plan.
4. Review your intercompany accounts for any manual multicurrency
transactions. The euro conversion converts these transactions; however, you
must verify them and correct the amounts as needed.
5. From the Organization & Account Setup menu (G09411), choose Company
Names & Numbers. Reset the fiscal period and year (for A/R, A/P, and
G/L) so that you can post to prior years.
6. Use the report generated by the Multi-Currency Intercompany Conversion

(step 2) to identify the different batch types that need to be posted.
7. From the Ordered Conversion Jobs menu (G97UE90), choose Multi-

Currency Intercompany Post.
8. Designate the batch type in the processing option and run the Multi-
Currency Intercompany Post separately for each batch type you identified in
step 6.
• The Multi-Currency Intercompany Post (R8909801EB) is a version

of the G/L Post program (R09801) that creates all F0911 entries,
including AE offset and AM adjusting entries, based on the new
base currency in the F0010 table.

156
• Unlike the G/L Post, the Multi-Currency Intercompany Post does

not post to the Account Balances table (F0902). Instead, it marks the
entries as posted so that when you run the Repost later in the euro
conversion process, the entries are selected and posted to the F0902
table. For more information, see Reposting to the Account Ledger.
9. Review the report created by the Multi-Currency Intercompany Post. If the
report shows batches that did not post, determine the cause and proceed to
step 10 or step 11 accordingly.
10. Batch is out of balance. Slight rounding differences occur when the Multi-
Currency Intercompany Conversion converts transactions such as invoices
and vouchers that do not have an associated F0911 transaction to balance
to. The rounding differences, which are typically less than a cent, cause a
batch to be out of balance and, as a result, the batch will not post. For out-
of-balance batches, do one of the following:
• To correct an out-of-balance batch, inquire on the batch and revise

the amount of the entry for each document that is out of balance.
Approve the batch and rerun the Multi-Currency Intercompany
Post.
• To correct an out-of-balance batch, create a one-sided adjustment at
the document level or at the batch level. For each batch, remember
to set the option on the Batch Header Revisions form that allows
you to post out-of-balance. Approve the batch and rerun the Multi-
Currency Intercompany Post.
• To post out-of-balance batches, set the option on the Batch Header
Revisions form that allows you to post out-of-balance batches for
each batch. Approve the batch and rerun the Multi-Currency
Intercompany Post. After you rerun the post, create a final
adjustment to balance all batches or, if applicable, run an integrity
report that creates the final adjustment. Remember to set the post
out of balance option for each batch and post your final
adjustments.
11. Posting edit code on an account or business unit changed after the original
transaction was posted. If you changed the original posting edit code on an
account or business unit from a blank to a non-blank value after you posted
the original transaction, the Multi-Currency Intercompany Post will not post
the batch. Change the posting edit code back to blank on the account or
business unit. Approve the batch and rerun the Multi-Currency
Intercompany Post. After you rerun the post, change the posting edit code
back to the previous value.
12. From the Organization & Account Setup menu (G09411), choose Company
Names & Numbers. Reset the fiscal period and year back to its original
value.

157
Running Additional Conversion Jobs
This task includes a checklist that has two check-off (√) columns - one for your
test (TEST) environment and the other for your production (PROD) environment.
After you run and successfully complete the euro conversion workbench and the
ordered conversion jobs, you run the additional conversion jobs. The additional
conversion jobs are designed to run separately from the workbench conversion
jobs so that you can control:
• What exchange rate to use (based on a plan name), using the processing
option
• Which records to convert, using the data selection
For example, the euro conversion workbench does not convert amounts on
records if certain fields are not in a table or if certain values on a record are invalid
or blank. To convert these amounts, you must run several additional conversion
jobs. If records do not include a company or business unit, the associated amounts
are assumed to be in the domestic currency of the company.
Each time you run an additional conversion job, you specify a plan name in the
processing option. The additional conversion job uses the exchange rate assigned
to that plan to convert amounts to the euro.
Run only the additional conversion jobs that apply to the J.D. Edwards systems
you use. The additional conversion jobs are for the following systems:
• Sales Order Management

• Procurement
• Agreement Management
• Advanced Transportation Management
• Equipment Management
• Service Billing
• Product Data Management
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Running Additional Conversion Jobs

158
• Stock Valuation
Remember that you must run the additional conversion jobs and complete all
remaining tasks first in your test environment, correcting any data issues in both
your test and production environments. Later, when you are satisfied with the
results of the euro conversion in your test environment, you will complete all of
the tasks again in your production environment and "go live."
Before You Begin

G Make sure you successfully ran and completed the Company Currency
Codes Conversion job (R890010E), which updates the company currency
codes for a plan to EUR. You can verify currency code values on Company
Names & Numbers (menu G09411).
G Ensure that the exchange rate assigned to the plan is correct. If necessary,
change it on the Conversion Plan Revisions form (P0087). See Changing the
Plan Exchange Rate Before Running a Job for more information.
G For OneWorld releases B73.3.2 and Xe, the additional conversion jobs for
Stock Valuation do not appear on the Additional Ordered Conversion Jobs
menu (G97UE901).
Visit the Euro Knowledge Garden site for more information. The path is
Services > OneWorld Knowledge Documents > Technical > Menu
Corrections.

159
► To run additional conversion jobs
Caution
Do not run an additional conversion job more than one time over the same data.
The additional conversion jobs convert amounts every time you run them,
regardless of whether the amounts have already been converted.
From the Euro Conversion menu (G97UE9), choose Additional Conversion Jobs.
1. On Additional Conversion Jobs, choose an additional conversion job.
For detailed information about the additional conversion jobs, see Checklist:
Additional Conversion Jobs.
2. On Work with Batch Versions, choose the version.
3. From the Row menu, choose Processing Options.

160
Work Center and Advanced Transportation Conversion Jobs

The Work Center Conversion job has an additional processing option,
which is required. For more information, see Product Data Management in
Checklist: Additional Conversion Jobs.
All Advanced Transportation Management conversion jobs have an
additional processing option that allows you to either convert the records or
bypass converting them.
To convert amounts, the job uses the exchange rate associated with the plan
you enter in this processing option
4. Enter the plan name to use for the additional conversion job and click OK.
5. On Work with Batch Versions, choose the version again and click Select to
access Version Prompting.
6. Enter the data selection and submit the conversion job to batch, as usual.
Checklist: Additional Conversion Jobs
The following jobs are accessed from the Additional Conversion Jobs menu
(G97UE901).

161
Additional Description TEST PROD

Conversion Job √ √
Commission For clients who use the commission functionality. This job
Constants converts the Fixed Cost and Minimum Gross Margin amounts
Conversion in the Commission Constants table (F42004). A currency code
(R8942004EB) is not stored in this table.
If all commission records are set up in one currency, enter the
plan name that corresponds to that currency in the processing
option, specify all records in the data selection, and run this
job one time only. If commission records are set up in
multiple currencies, determine which commission records
represent a given currency in order to convert the records. For
example, certain commissions might correspond to certain
currencies. Then, do one of the following:
• Enter the plan name that corresponds to a particular

currency (processing option), specify the records to
convert, for example, address book numbers (data
selection), and run this job separately for each currency.
• Modify selected records manually.
Price by Item For clients who use the standard price adjustment
Conversion functionality. This job converts the Override List Price and
(R894207EB) Related Price amounts in the Price by Item table (F4207). The
currency code is not populated in this table.
If all standard price adjustments are set up in one currency,
enter the plan name that corresponds to that currency in the
processing option, specify all records in the data selection, and
run this job one time only. If standard price adjustments are
set up in multiple currencies, determine the price adjustments
that represent a given currency. For example, certain price
rules might correspond to certain currencies. Then, do one of
the following:

convert (data selection), and run this job separately for
each currency.

162

Batch Receiver For clients who have unprocessed batch records. This job
Header/Detail converts amounts on unprocessed orders without a business
Conversion unit, as follows:
(R894001ZEB)
• Converts the Order Total and Total Cost amounts in
the Batch Receiver Header table (F4001Z)
• Converts the Unit Price, Unit Cost, Extended Price,

Extended Cost, and Unit List Price amounts in the
Batch Receiver Detail table (F4011Z)
If all unprocessed orders have domestic amounts set up in one
currency, enter the plan name that corresponds to that
currency in the processing option, specify all records in the
data selection, and run this job one time only. If unprocessed
orders are set up in multiple currencies, determine which
orders represent a given currency. Then, do one of the
following:

each currency.

163

EDI Purchase For clients who have unprocessed inbound EDI transactions
Order for purchase orders. This job converts amounts on
Header/Detail unprocessed orders without a business unit, as follows:
Conversion
(R8947011EB) • Converts the Order Total and Total Cost amounts in
the EDI Purchase Order Header table (F47011)

Extended Cost, and Unit List Price amounts in the EDI
Purchase Order Detail table (F47012)
orders represent a given currency. Then, do one of the
following:

each currency.

164

EDI Request for For clients who use the EDI Request for Quote Inbound or
Quote Conversion the EDI Request for Quote Edit/Create functionality. This
(R8947091EB) job converts amounts on unprocessed orders without a
business unit, as follows:
• Converts the Order Total and Total Cost amounts in

the EDI Request for Quote Header table (F47091)

Extended Cost, and Unit List Price amounts in the EDI
Request for Quote Detail table (F47092)
particular currency in the processing option, specify all records
in the data selection, and run this job one time only. If
unprocessed orders are set up in multiple currencies,
determine which orders represent a given currency. Then, do
one of the following:

each currency.
Price Variable For Advanced Pricing clients who use the Price Variable Table
Conversion functionality. This job converts the Unit Price amount in the
(R894075EB) Price Variable table (F4075). This table, unlike the tables for
other additional conversion jobs, contains a currency code.
This job retrieves exchange rates from the Currency Exchange
Rate table (F0015), which means that you can convert multiple
currencies at the same time. It also updates the currency code
in the table with the new euro currency code.
Specify the records to convert by currency code or price
variable in the data selection and run this job.
Procurement
The additional conversion jobs for Procurement have two versions:
• Version 1 (XJDE0001) runs during the euro conversion workbench and

converts records with a branch/plant and company. Do not run this version
again.

165
• Version 2 (XJDE0002) is the additional conversion job that you must run to
convert records without a branch/plant or company. Alternatively, you can
create a new version and run it to convert these records.

Tolerance Rules Do not run if your tolerance rules are based only on
Conversion percentages. This job converts amounts on records without a
(R894322E) company. It converts the Unit Price Tolerance and Extended
Tolerance amounts in the Tolerance Rules table (F4322).
records represent a given currency. Then, do one of the
following:

each currency.
Item Cost This job converts amounts on records without a branch/plant.

Components It converts the Cost Add-On Amount, Freight Add-On Rate,
Conversion and Volume Add-On Rate amounts in the Item Cost
(R8941291E) Components table (F41291).
records represent a given currency. Then, do one of the
following:
• Enter the plan name for a particular currency

(processing option), specify the records to convert (data
selection), and run this job separately for each currency.

166
Agreement Management
The following additional conversion job converts the currency code for records in
the Distribution Contract Quantities table (F38011). This job does not run during
the euro conversion workbench because most clients do not want to convert the
currency code on all agreement records. For example, a Belgian company has
agreements that are due to a company in BEF and it also has agreements that are
due to a supplier in BEF. The company has converted its base currency to the
euro; however, the supplier has not. In this example, the Belgian company would
run the additional conversion job and use data selection to select records with Due
To equal to C (company). The job would convert the currency code to BEF on all
agreements due to the company only, and not on any suppliers (or customers).
The advantage to running the additional conversion job is that it automatically

updates records associated with the F38011 record in five other Agreement
Management tables. Alternatively, you can manually modify agreement records.

Distribution This job converts the currency code field in the Distribution
Contract Quantities Contract Quantities table (F38011) on records with a business
Conversion unit. (The business unit is used to retrieve the correct
(R8938011E) exchange rate when calculating amounts on the associated
records.) If there are no errors, the conversion job updates
currency codes, amounts, or both for all associated records in
the following tables:
• Product Source Destination Master (F38012)
• Contract Quantities Schedule (F38013)
• Contract Formulas and Factors (F38014)
• Distribution Contracts Transaction Ledger (F38111)
• Distribution Contracts Committed Quantities (F38112)
Advanced Transportation Management

Routing Entries This job converts freight rates on domestic-only transactions

Conversion in the Routing Entries table (F4950). It converts the Freight
(R894950EB) Rate and Currency Code From fields based on the route
number.

167

Rate Detail This job converts freight rates on domestic-only transactions

Conversion in the Detail Rate table (F4972). It converts the Freight Rate
(R894972EB) and Currency Code From fields based on the unique key ID
internal.
Spot Quote Detail This job converts freight rates on domestic-only transactions
Conversion in the Spot Quote Detail table (F49721). It converts the
(R8949721EB) Freight Rate and Currency Code From fields based on the
rate name, shipment number, routing step number, cost
center, load number, and delivery number.
Rate Structure This job converts monetary lookup values on domestic-only

Definition transactions in the Rate Structure Definition table (F4973). It
Conversion converts the Lookup From Value and Lookup To Value
(R894973EB) fields for records with a lookup type of B, C, F, or S only.
Rate Parameters This job converts amounts on domestic-only transactions in

Conversion the Rate Parameters table (F4977) for the following fields:
(R894977EB) Base Charge, Minimum Charge, Maximum Charge, Minimum
Package Charge, and Oversize Package Charge.
Customer Freight This job converts amounts on domestic-only transactions in

Conversion the Preference Profile Customer Freight table (F40332) for
(R8949332EB) the following fields: Extended Price From and Extended
Price Through.
Equipment Management

License Fee File This job converts records without a branch/plant and
Conversion company. It converts the License Fee amount field in the
(R891206EB) License Master table (F1206).
Rental Rates This job converts records without a branch/plant and

Conversion company. It converts the Replacement Cost and Rate
(R891301EB) Component (01-10) amounts in the Equipment Rental Rate
table (F1301).

168
Service Billing

Invoice Summary This job converts and rebuilds the Invoice Summary
File Conversion Workfile (F4822) in the new domestic currency (euro), based
(R894822EB) on the converted Service Billing History Workfile (F4812H).
Rebuild Invoice OneWorld Xe only. This job rebuilds the Invoice Summary
Summary Access Access table (F48520) in the new domestic currency, based
Table on the Service Billing History workfile (F4812H).
(R8948520EB)
Use the data selection to select the same companies that you
converted during the euro conversion.
Restate Contracts OneWorld Xe only. This job restates amounts in the

(R895202EB) Contract Billing Master (F5201), Owner Pay Item Detail
(F5202), and Pay Item Mark-Up Cross Reference Accounts
(F5213) tables in the new domestic currency.
If you choose to create new contracts instead of restating
amounts, close out your existing contracts and enter new
ones with the negotiated amount in your new domestic
currency.

169
Product Data Management

Work Center Depending on how your manufacturing constants are set up

Conversion for a branch/plant, this job converts overhead costs in the
(R8930008E) Work Center Rates table (F30008) as follows:
• For branch/plants in which overhead costs are set up as

percentages, the rate fields for Direct Labor, Setup
Labor, and Machine Run fields are converted. The
overhead fields remain percentages and are not
converted.
• For branch/plants in which overhead costs are set up as

rates, the aforementioned rate fields as well as the
overhead fields (Labor Variable O/H, Labor Fixed
O/H, Machine Variable O/H, and Machine Fixed O/H)
are converted.
Unlike other additional conversion jobs, this job has an
additional processing option that is required and is used to
specify the branch in which you want to convert overhead
costs. You control whether you convert some or all work
centers within a branch. To specify which work centers
(Business Units) within a branch you want to convert, use the
data selection. There are two versions for this job (XJDE0001
and ZJDE0001). You can run either one, as the versions are
the same.
Stock Valuation
The following conversion jobs convert dual currency records only. Do not run
these conversion jobs if:
• You do not process dual currency records

• You do not want to convert your dual currency records
If you want to convert dual currency records to a currency that is different from
what the domestic records were converted to, you must set up a new conversion
plan. For example, before the conversion a French company had dual currency
records in German marks. The company now wants to see their dual currency
records in Canadian dollars. To convert these records using the Stock Valuation
additional conversion jobs, the company must first set up a conversion plan with a
EUR to CAD exchange rate. See Setting Up a Euro Conversion Plan for more
information and detailed procedures.

170

Valuation Period This job converts dual currency records in the F39061 table
Dual Currency for the following amount fields: Amount Opening Cost
Conversion (OPAM), Amount Period Purchases (PEPA), Amount Period
(R8939061EB) Outgoing (POAM), Amount Closing (CLAM), Amount Cost
of Goods Sold (CGAM), Amount COGS Adjustment
(CGAD), Amount Inventory Adjustment (IVAD), and
Amount LIFO Adjustment Cost (LICS).
Historical Valuation This job converts dual currency records in the F390619 table
Period Dual for the following amount fields: Amount Opening Cost
Currency (OPAM), Amount Period Purchases (PEPA), Amount Period
Conversion Outgoing (POAM), Amount Closing (CLAM), Amount Cost
(R8939619EB) of Goods Sold (CGAM), Amount COGS Adjustment
(CGAD), Amount Inventory Adjustment (IVAD), and
Amount LIFO Adjustment Cost (LICS).
Valuation Layers This job converts dual currency records in the F39062 table
Dual Currency for the following amount fields: Unit cost Purchasing
Conversion (AMC3), Amount Current (CRAM), and Amount Last
(R8939062EB) Allocation (ALAM).
Period Additional This job converts dual currency records in the F39063 table
Quantity Dual for the following amount fields: Amount Opening Cost
Currency (OPAM), Amount Period Incoming (PIAM), Amount Period
Conversion Outgoing (POAM), Amount Closing (CLAM), and Amount
(R8939063EB) Period Adjustment (ADAM).
Historical This job converts dual currency records in the F390639 table
Additional Quantity for the following amount fields: Amount Opening Cost
Dual Currency (OPAM), Amount Period Incoming (PIAM), Amount Period
Conversion Outgoing (POAM), Amount Closing (CLAM), and Amount
(R8939639EB) Period Adjustment (ADAM).
Valuation This job converts dual currency records in the F39064 table
Document for the Amount Current SV (CRRA) field.
Summary Dual
Currency
Conversion
(R8939064EB)
Historical Valuation This job converts dual currency records in the F390649 table
Document for the Amount Current SV (CRRA) field.
Summary Dual
Currency
Conversion
(R8939649EB)

171
Post-Conversion Tasks

172
Reviewing and Correcting Post-Conversion Integrity

Reports
This task includes a checklist and description of the post-conversion integrity

reports that you must review and correct after you run the ordered and additional
conversion jobs. The checklist has two check-off (√) columns - one for your test
(TEST) environment and the other for your production (PROD) environment.
Most of the integrity issues that appear on the post-conversion integrity reports are
minor rounding differences that occur when converting from your base currency
to the euro. Make sure you compare your post-conversion integrity reports to the
pre-conversion integrity reports to ensure that the conversion results are accurate.
Run the post-conversion integrity reports in proof mode first and then run them in
final (update) mode. Final mode was created especially for the euro conversion to
update any minor rounding differences that occur during the actual conversion.
Final mode does the following:
• Tests the integrity of data between tables with dependent relationships.

• Locates the difference between the tables.
• Creates adjusting entries for batches that are out of balance and corrects any
integrity issues caused by the conversion. (You can use the data selection to
exclude records in which you do not want to create adjusting entries.)
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Reviewing and Correcting Post-Conversion Integrity
Reports 173
Most integrity reports are accessed from the Euro Conversion menu (G97UE9).
An example of the B7331EURO and B7332EURO menu appears below.
Run integrity reports only for those systems that your company uses.
Remember that you must run and review the post-conversion integrity reports and
correct any data issues and complete all remaining tasks first in your test
environment, correcting any data issues in both your test and production
environments. Later, when you are satisfied with the results of the euro conversion
in your test environment, complete all of the tasks again in your production
environment and "go live."
Before You Begin

G Make sure you successfully completed the Company Currency Codes
Conversion job(R890010E), which updates the company currency codes for
a plan to EUR. You can verify currency code values on Company Names &
Numbers (menu G09411).
G Make sure you successfully completed all other post-conversion jobs. See
Checklist: Ordered Conversion Jobs and Checklist: Additional Conversion Jobs.
G A/R and A/P to G/L integrity reports. Before you run the F03B11 to
F0911 Integrity (R890911AI), F0411 to F0911 Integrity (R04711), and
F0414 to F0911 Integrity (R04712) reports in final mode, determine whether
you want to automatically create adjusting entries for batches that are out of
balance. If you do not want adjusting entries created, modify the data
selection to exclude the batches from appearing on the integrity reports.
Otherwise, adjusting entries will be created for out-of-balance batches.
Reports 174
Topics
G Checklist: Financials Post-Conversion Integrity Reports
G Checklist: Distribution Post-Conversion Integrity Reports
G Checklist: Logistics Post-Conversion Integrity Reports
G Checklist: Manufacturing Post-Conversion Integrity Reports
G Checklist: Batch Headers Post-Conversion Integrity Reports
G Checklist: Post Integrity Job
Checklist: Financials Post-Conversion Integrity Reports
The following integrity reports are accessed from the Financials Integrities menu
(G97UE91).
Accounts Receivable

F03B11 to F03B22 (Proof) Compares records in the A/R Ledger table (F03B11)
Integrity (R8903B22I) to the Fee Journal History table (F03B22) and prints
(Final) Creates an adjusting amount in the F03B22 table to

(Proof) Compares records in the A/R Ledger table (F03B11)
to the Deduction Management table (F03B40) and prints

to the A/R Check Detail table (F03B14) and prints
Reports 175


(F03B14) to the Deduction Activity table (F03B41) and

(F03B14) to the Receipts Header table (F03B13) and prints

(Proof) Compares records in the Fee Journal History table
(F03B22) to the Fee History Detail table (F03B23) and
F03B11 to F0911 Prerequisite: Previous integrity report (R8903B23I).

Integrity (R890911AI)
to the Account Ledger table (F0911) and prints differences
on a report.
document (G/L distribution) or by batch (automatic offset)
to balance to the F03B11 table. The adjusting amount is
directed to one of the following AAIs:
• ADR, if the offset method is by document. This AAI

item tracks differences between the F03B11 and
F0911 distribution amounts.
• AER, if the offset method is by batch. This AAI item

tracks differences between the F03B11 and F0911
automatic entry (AE) amounts
Reports 176

F03B14 to F0911 Prerequisite: Previous integrity report (R890911AI).

Integrity (R890911BI)
(F03B14) to the Account Ledger table (F0911) and prints
differences on a report. In proof mode, this report is
equivalent to A/R to G/L Receipts by Batch (R03B702).
F03B13 to F0911 Prerequisite: Previous integrity report (R890911BI).

Integrity (R890911CI)
(Proof) Compares records in the Receipts Header table
(F03B13) to the Account Ledger table (F0911) and prints
A/R to G/L by OneWorld B73.3.1 only. Prerequisite: Previous integrity

Offset Account report (R890911C1).
(R03B7001A)
Summarizes open amounts in each G/L account (F0311)
and compares the total to the balance amount in each
offsetting A/R trade account (F0902).
A/R to Account OneWorld B73.3.2 and above. Prerequisite: R890911C1.

Balance by Account
ID (R03B707) If this report does not appear on your menu and you want
to add it, visit the Euro Base Currency Conversion site on
the Knowledge Garden. The path is World Wide Topics >
Euro Base Currency Conversion > Global Support Services
> OneWorld Knowledge Documents > Technical > Menu
Corrections.
Alternatively, you can run the report from Batch Versions.
From menu GH9011, choose Batch Versions. In the Batch
Application field, enter R03B707 and click Find. Choose the
version and click Select to run the report as usual.
This report replaces A/R to G/L by Offset Account
(R03B7001A). It summarizes open amounts in each G/L
account in the A/R Ledger table (F0311) and compares the
total to the balance amount in each offsetting A/R trade
account in the Account Balances table (F0902).
For more information about the R03B707 report, visit
breaking news on the Knowledge Garden site. The path is
Product > Knowledge > Knowledge Breaking News >
OneWorld > Financials > Accounts Receivable > Reports.
Reports 177
Accounts Payable

F0411 to F0911 (Proof) Compares records in the A/P Ledger table (F0411)
Integrity (R04711) to the Account Ledger table (F0911) and prints differences
on a report.
document (G/L distribution) or by batch (automatic offset)
to balance to the F0411 table. The adjusting amount is
directed to one of the following AAIs:
• ADP, if the offset method is by document. This AAI

item tracks differences between the F0411 and F0911
distribution amounts.
• AEP, if the offset method is by batch. This AAI item

tracks differences between the F0411 and F0911
automatic entry (AE) amounts.
F0414 to F0411 (Proof) Compares records in the A/P Matching Document

Integrity (R04713) Detail table (F0414) to the A/P Ledger table (F0411) and
F0414 to F0911 Prerequisites: Previous integrity reports (R04711 and

Integrity (R04712) R04713).
(Proof) Compares records in the A/P Matching Document
Detail table (F0414) to the Account Ledger table (F0911)
and prints differences on a report. In proof mode, this
report is equivalent to A/P Payments to G/L by Batch
(R04702A).
A/P to G/L Integrity Summarizes open amounts in each G/L account (F0411)
by Offset Account and compares the total to the balance amount in each
(R047001A) offsetting A/P trade account (F0902).
Reports 178
General Accounting

Unposted General Prints a general journal of unposted transactions in the

Journal (R09301) Account Ledger table (F0911).
Accounts without (Proof) Locates account master records with an invalid

Business Units company number and without a business unit record.
(R097041)
(Final) Updates the F0901 table with the company number
from the business unit master record.
Account Balance (Proof) Locates account balance records with an invalid

without Account company number and without an account master record.
Master (R097031)
(Final) Updates the Account Balances table (F0902) with the
company number from the account master record.
Transactions without (Proof) Locates transaction records with an invalid company

Account Master number and without an account master record.
(R097021)
(Final) Updates the Account Ledger table (F0911) with the
company number from the account master record.
Companies in Creates a report that shows the net balance for each
Balance (R097001) company. If a company is in balance, the columns on the
report are blank.
Intercompany Locates imbalances between corresponding intercompany

Accounts in Balance accounts and prints a report.
(R097011)
If you have multiple companies with different base
currencies, do not run this integrity report. This integrity
report does not accommodate different base currencies.
Account Balance to Locates imbalances between the Account Balances table

Transactions (F0902) and Account Ledger table (F0911) by fiscal period
(R09705) and prints a report.
If you have imbalances between these tables and you turn
monetary accounts on and off, contact your Global Support
Services consultant for a resolution plan for monetary
accounts.
Reports 179

Foreign Account This integrity report is accessed only from the Integrity
Balance Integrity Reports and Updates menu (G0922).
(R09707)
(Proof) Compares foreign ledger (CA) records to domestic
ledger (AA) records in the Account Balances table (F0902)
and prints a report that shows CA records without a
corresponding AA record.
(Final) Removes CA records in the F0902 table that do not
have a corresponding AA record.
Cash Basis Integrity OneWorld Xe only. This integrity report is accessed only
Test (R11C750) from the Cash Basis Accounting menu (G09314).
Identifies cash accounts that have different balances in the
AA and AZ ledgers after posting.
Localization

Integrity (R74701) Account Ledger table (F0911) to the G/L Registration
Balance table (F70404).
Integrity (R74703) A/P Ledger table (F0411) to the Withholding Tax Detail
table (F74411).

F0911 Transaction Prints Account Ledger (F0911) transactions for accounts

Report (R127012) within the AAI item FX range.
Reports 180

Unposted F0911 Compares unposted Account Ledger (F0911) transactions to

Transactions to unposted Asset Balances (F1202) transactions for accounts
F1202 (R12301) within the AAI item FX range. Prints differences on a
report.
F0911 to F1202 (Proof) Compares posted transactions (with batch rear end
Integrity (R12910) = *) in the Account Ledger table (F0911) to posted
transactions in the Asset Balances table (F1202).
balance to the F0911 able. This integrity report is the Fixed
Asset Repost.
Note: If you summarize your depreciation transactions, do
not run this integrity report. Clients who summarize
transactions have F1202 records without supporting F0911
transactions and running this integrity report serves no
purpose. Once you summarize transactions, you cannot go
back and create detail for them.
F1202 to F0902 Compares posted Asset Balance (F1202) transactions to

Integrity (R127011) posted Account Balance (F0902) transactions and prints
F5144/F5145 to (Proof) Compares records in the Account Balances table

F0902 (R51800) (F0902) to records in the Profit Recognition (F5144) and
Profit Recognition Account Balance (F5145) tables.
(Final) Creates adjusting amounts in the F5144 and F5145
tables to balance to the F0902 table.
Change Management

CO/PCO OneWorld Xe only. Compares final and quoted amounts

(F5315/F5314) for cost, revenue, and subcontract records in the Change
Integrity (R53701) Order Master table (F5315) to the attached planned
change orders in the Planned Change Order Master table
CPC/CR OneWorld Xe only. Compares final and quoted amounts

(F5314/F5311) for cost, revenue, and subcontract records in the Planned
Integrity (R53702) Change Order Master table (F5314) to the attached
change requests in the Change Request Details table
Reports 181
Checklist: Distribution Pre-Conversion Integrity Report
The following integrity report is accessed from the Distribution Integrities menu
(G97UE92).

Commitment Integrity (Proof) Compares records in the P.O. Detail Ledger table
Report (R40910) (F43199) to the Purchase Order Detail table (F4311) and
records in the F43199 table to the Account Balances table
(Final) OneWorld Xe only. Creates an adjusting amount
in the F43199 table if there is a difference between the
amounts in the F4311 and F43199 tables. Creates an
adjusting amount in the F0902 table if there is a
difference between the amounts in the F43199 and F0902
tables.
Checklist: Logistics Post-Conversion Integrity Reports
The following integrity reports are accessed from the Logistics Integrities menu
(G97UE93).

Item Ledger/Account Compares records in the Account Ledger table (F0911) to

Integrity (R41543) the Item Ledger able (F4111) and prints differences on a
report.
Item Balance/Ledger Compares records in the Item Location table (F41021) to

report.
Reports 182
Checklist: Manufacturing Post-Conversion Integrity Report
The following integrity report is accessed from the Manufacturing Integrities menu
(G97UE94).

Cost Compares the sum of the frozen standard cost

Component/Ledger components to the unit cost in the Cost Ledger table
Integrity (R30543) (F4105) and prints a report that shows the variances.
Checklist: Batch Header Post-Conversion Integrity Report
The following integrity report is accessed from the Batch Header Integrities menu
(G97UE95). There are four batch header reports on the menu - run only the
following one.

Batch to Detail/Out of Run this report after you run the post-conversion
Balance (R007031) integrity reports for all other systems and before you
repost the account ledger.
Locates batches that were posted out of balance and
prints a report. Use this report to compare to the list of
out-of-balance batches that you compiled before the
conversion.
Reports 183
Checklist: Post Integrity Job (Repost)
The following integrity report is accessed from the Post Integrity Jobs menu
(G97UE99).

Repost Account Ledger Prerequisite: Run the post-conversion integrity reports

(R099102) for all other systems.
Run the Repost Account Ledger program to:
• Identify accounts with different amounts in the

F0911 and F0902 tables (proof)
• Update the F0902 table with the posted amounts

from the F0911 table (final)
For more information, see Reposting the Account Ledger.
Reports 184
Reposting the Account Ledger
After you review and correct your post-conversion integrity reports, you must
repost the account ledger for all companies, regardless of whether you converted
their base currency to the euro. This is necessary to ensure that the Account
Balances (F0902) and Account Ledger (F0911) tables for all companies are in
balance after the euro conversion. Reposting the account ledger allows you to
identify and correct any differences, thereby maintaining the integrity between your
F0911 and F0902 tables.
Some euro conversion programs create minor rounding differences between the
transaction amounts and balance amounts converted. The Repost Account Ledger
program does the following:
• Identifies all accounts that should be adjusted due to minor rounding

differences between transaction amounts in the F0911 and balance amounts
in the F0902 tables (proof). Most company auditors will want to have an
audit record of the rounding differences that are identified.
• Updates the F0902 table so that it balances with the F0911 table (final). The
repost "plugs" numbers in the F0902 table, based on the detailed
transactions in the F0911 table.
Reposting the account ledger updates or creates new F0902 records for all existing
F0911 records and, therefore, can take a long time to process. Typically, reposting
updates the F0902 records; however, if the CRCD and CRCX fields on records are
not populated or an account has a post edit code, reposting actually creates new
F0902 records.
The Repost Account Ledger program is located on the Post Integrity Jobs menu
(G97UE99).
Remember that you must repost your account ledger and complete all remaining
tasks in this workbook first in your test environment, correcting any data issues in
both your test and production environments. Later, when you are satisfied with the
results of the euro conversion in your test environment, complete all the tasks
again in your production environment and "go live."
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Reposting the Account Ledger

185
Before You Begin

G Review and correct all post-conversion integrity reports. See Reviewing and
Correcting Post-Conversion Integrity Reports.
G For clients who run the euro conversion at the end of their fiscal year, J.D.
Edwards recommends that you run the Annual Close program for all
companies before reposting the account ledger. Depending on the records
that were purged before the conversion, the repost might produce
unexpected results unless you run the annual close before the repost.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Reposting the Account Ledger

186
Completing Post-Conversion Tasks
This task consists of a checklist and description of the post-conversion tasks that
you must complete before or after you review and correct your post-conversion
integrity reports and repost the account ledger. The checklist has two check-off (√)
columns - one for your test (TEST) environment and the other for your
production (PROD) environment.
Most of the pre-conversion tasks rebuild or update workfiles. Complete only those
post-conversion tasks that apply to the J.D. Edwards programs and systems that
you use. For example, if you do not use localization programs, do not complete the
post-conversion tasks for Localization. Similarly, if you do not use bank statement
processing, do not complete the post-conversion task for reconciliation listed
under General Accounting.
Remember that you must complete the post-conversion tasks first in your test
environment, correcting any data issues in both your test and production
environments. Later, when you are satisfied with the results of the euro conversion
in your test environment, complete all of the tasks in this workbook again in your
Topics
G Checklist: Financials Post-Conversion Tasks
G Checklist: Distribution Post-Conversion Tasks
G Checklist: Manufacturing Post-Conversion Tasks
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Completing Post-Conversion Tasks

187
Checklist: Financials Post-Conversion Tasks
General Accounting
Post-Conversion Description TEST PROD

Task √ √
Change the currency On Company Names & Numbers, menu G09411, change
code for company the currency code for the default company 00000 to EUR.
00000 The euro conversion does not do this; you must do it
manually.
Refresh the Run Refresh Reconciliation File (R09130), menu G0921.

reconciliation file
Rebuilds domestic amounts in the Account Ledger
Reconciliation workfile (F0911R) with euro amounts.
Review and revise your The euro conversion does not convert model journal
model journal entries entries. Locate the list of model journal entries that you
printed before the conversion, or create a new list by
running a query or UBE over the F0911 table for journal
entries with a posted code M (model). Revise model
journal entries as needed.
Review and revise your The euro conversion does not convert amounts in the
allocations Cost Allocations/Flex Budgeting table (F0912). Locate the
list of recurring journal entries that you printed before the
conversion, or create a new list by running a query or UBE
over the F0912 table for journal entries with a batch type
D. Revise recurring journal entries as needed.
Run the annual close Run the annual close program for all prior years that have
for prior years been closed and contain converted records. The annual
close program creates an adjusting amount to correct prior
year-end and beginning balance postings. Use the report
produced by this program to verify the prior year-end and
balance forward amounts with the amounts from the
repost.
Delete indices Delete any indices that you created prior to running the
euro conversion. For more information, see Creating Indices
Before Running the Euro Conversion.

188
Accounts Receivable

Task √ √
Rebuild workfile Run Credit Analysis Refresh (R03B525), menu G03B15.

Rebuilds domestic amounts in the A/R Cash Management
workfile (F03B15) with euro amounts.
Print the Recurring Print the Recurring Invoice Report (R03B305), menu
Invoice Report G03B111.
Review and revise your recurring invoices. Review the
converted recurring invoices and verify the new amounts.
If you want to revise an amount, you must delete the
recurring invoice and enter a new one.
Accounts Payable

Task √ √
Rebuild workfiles Run Date File Generation (R04901), menu G0421.

Rebuilds domestic amounts in the following workfiles
with euro amounts:
• As of A/P Ledger (F0411A)
• As of A/P Matching Document (F0413A)
• As of A/P Matching Document Detail (F0414A)
Print the Recurring Print the Recurring Voucher Report (R04305), menu
Voucher Report G0411.
Review and revise your recurring vouchers. Review the
converted recurring vouchers and verify the new
amounts. If you want to revise an amount, you must
delete the recurring voucher and enter a new one.

189
Localization

Task √ √
Run a query over the For clients with F0018 (Sales/Use/VAT) records. Run a
F0018 tax table query over the F0018 tax table for records that are not in
the A/R, A/P, and G/L ledger tables. The euro
conversion converts F0018 tax amounts that are stored in
the F03B11, F0411, and F0911 ledger tables only.
If you enter tax amounts directly in the F0018 table
(using the Tax File Revisions program), you must convert
those tax amounts manually.
Rebuild sales tax Run Update Extra Tax File - Sales (R0018I1), menu
workfile G00211.
Rebuilds domestic amounts in the Intrastat workfile
(F0018T) with euro amounts.
Rebuild purchasing Run Update Extra Tax File - Purchasing (R0018I2),

workfile menu G00211.
Rebuilds domestic amounts in the Intrastat workfile
(F0018T) with euro amounts.
Rebuild French Legal For French and Italian clients only. Run G/L by
Report workfile Category Code (R70470), menu G093151 or menu
G093152.
Rebuilds domestic amounts in the French Legal Report
workfile (T740911) with euro amounts.
Rebuild A/P Ledger For French clients only. Run the Ledger Report -
workfile Localized (R7404014), menu G093151.
Rebuilds domestic amounts in the Accounts Payable
Ledger workfile (T74411) with euro amounts.
Rebuild ETAFI For French clients only. Run ETAFI Interface

Interface table (R7409FI), menu G093151.
Rebuilds domestic amounts in the ETAFI Interface table
(F7409FI) with euro amounts.

190
Checklist: Distribution Post-Conversion Tasks

Task √ √
Rebuild workfile Run Item Ledger As Of Generation (R41542), menu

G4122.
Rebuilds the Item Ledger As Of workfile (F41112), based
on transactions in the Cardex table (F4111).
Run the container Run the container extraction and billing processes for
extraction and billing Container Management, menu G4118.
processes
OneWorld B73.3.1 only. Run end-of-day processing for
Container Extraction (R41189) and Container Billing
(R41180).
OneWorld B73.3.2 and above. Run end-of-day processing
for Container Extraction (R41189), Rental Billing
(R41186), and Deposit/Refund Billing (R41187). As of
release B73.3.2, R41186 and R41187 replaced R41180.
euro conversion. For more information, see Creating
Indices Before Running the Euro Conversion.
Checklist: Manufacturing Post-Conversion Tasks

Task √ √
Update PM Projectoins Run PM Projections Update (R13411), menu G1322.

table
Updates domestic amounts in the PM Projections table
(F13411) with euro amounts.
Update Work Order Run Update Work Order Actual Amounts (R13800),
Master table menu G1331.
Updates actual domestic amounts in the Work Order
Master table (F4801) with euro amounts.
Run Simulate Rollup Run Simulate Rollup (R30812), menu G3014.

Creates euro costs using converted rates and purchased
costs.
Run Frozen Update Prerequisite: Simulate Rollup. Run Frozen Update

(P30835) G3014

191

Task √ √
(P30835), menu G3014.
Revalues inventory in euro amounts.
Run Create Summary Run Create Summary Forecast (R34640), menu G3421.
Forecast
Creates the summary forecast for future sales amounts in
euro amounts.
Manually update Refer to the list you compiled before the conversion.
amounts in UDC fields Update the amounts in the user defined code fields
(if applicable) manually.
euro conversion. For more information, see Creating
Indices Before Running the Euro Conversion.

192
Converting the Production Environment
Make sure you have successfully completed the pre-conversion, conversion, and
post-conversion tasks in this workbook in your test environment. By testing the
euro conversion in your test environment and correcting data issues in both your
test and production environments, you help ensure the success of the actual
conversion in your production environment.
Once you are satisfied with the conversion results in your test environment, you
are ready to convert your production environment. To convert your production
environment, start at the beginning of this workbook and complete all the pre-
conversion, conversion, and post-conversion tasks again - this time in your
production environment. The effort required to complete the tasks in your
production environment should be considerably less since you have already
identified data issues in your test environment and corrected them in both your
test and production environments.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Converting the Production Environment

193

194
Appendices
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Appendices

195
Conversion and Post-Conversion Tables
Conversion and Post-Conversion Tables contains a list of tables converted during the
OneWorld Euro Conversion (workbench UBEs) and Post-Conversion (ordered
and additional conversion jobs).
This document is available in the published edition of the OneWorld Euro Conversion
and Integrity Workbook and on the euro Knowledge Garden site (the path is World
Wide Topics > Euro Base Currency Conversion > Global Support Services >
OneWorld Knowledge Documents > Technical > Conversion and Post-
Conversion Tables). It is not available in PDF format.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Conversion and Post-Conversion Tables

196
Euro Conversion Workbench UBEs
Euro Conversion Workbench UBEs contains the UBEs for OneWorld B73.3.2 and the
sequence in which they run during the euro conversion. The list is a "dump" of the
F98405 table, imported into a spreadsheet.
OneWorld Knowledge Documents > Technical > Euro Conversion Workbench
UBEs). It is not available in PDF format.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Euro Conversion Workbench UBEs

197
OneWorld Composite Keys
OneWorld Composite Keys contains a list of the composite keys for tables converted
during the euro conversion.
OneWorld Knowledge Documents > Technical > Composite Keys). It is not
available in PDF format.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) OneWorld Composite Keys

198
OneWorld Indices
The OneWorld Indices contains a list of known clauses for creating indices.
OneWorld Knowledge Documents > Technical > Indices). It is not available in
PDF format.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) OneWorld Indices

199
Sample: Table Conversion/Merge Driver Report
A sample Table Conversion/Merge Driver Report (for R89405) is available in the

published edition of the OneWorld Euro Conversion and Integrity Workbook. It is not
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Sample: Table Conversion/Merge Driver Report
200
Sample: Table Conversion Report
A sample Table Conversion Report (for the F74412 table) is available in the
published edition of the OneWorld Euro Conversion and Integrity Workbook. It is not
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Sample: Table Conversion Report

201
Sample: Euro Conversion Audit Report
A sample audit log report is available in the published edition of the OneWorld Euro
Conversion and Integrity Workbook. It is not available in PDF format.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Sample: Euro Conversion Audit Report
202
Sample: Company Currency Conversion Report
A sample company currency conversion report is available in the published edition

of the OneWorld Euro Conversion and Integrity Workbook. It is not available in PDF
format.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) Sample: Company Currency Conversion Report
203
OneWorld Service/Contract Billing
OneWorld Service/Contract Billing
OneWorld Service/Contract Billing includes information for clients who have enabled
multicurrency billing in the OneWorld Service Billing and Contract Billing systems.
OneWorld Knowledge Documents > Application > Service/Contract Billing). It is
not available in PDF format.
OneWorld B73.3.1, B73.3.2, and Xe (07/01) OneWorld Service/Contract Billing

204

People Soft Enterprise One Euro Conversion Workbook

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

People Soft Enterprise One Euro Conversion Workbook

Uploaded by

Copyright:

Available Formats

July 2001

One Technology Way

Copyright © J.D. Edwards World Source Company, 2000, 2001

All Rights Reserved

About This Workbook ....................................................................................... 1

Post-Conversion Tasks 172

About This Workbook

• Application. Tasks that apply to employees who are responsible for

OneWorld B73.3.1, B73.3.2, and Xe (07/01) About This Workbook

Pre-Conversion Task Application Technical

Planning a euro conversion strategy x x

Setting up a euro conversion test environment x

Reviewing sizing impacts and system resources x

Euro conversion software prerequisites x

Copying tables to your conversion environment x

Creating indices before running the euro conversion x

Completing system-level prerequisites x x

Completing pre-conversion tasks x

Reviewing and correcting pre-conversion integrity x

Purging outdated data tables x

Rerunning pre-conversion integrity reports x

Conversion Task Application Technical

Environments and euro conversion plans x x

Setting up a euro conversion plan x

Running the euro conversion workbench x x

Verifying the status of the euro conversion x x

OneWorld B73.3.1, B73.3.2, and Xe (07/01) About This Workbook

Conversion Task Application Technical

Reviewing the euro conversion reports and audit tables x

Rerunning a euro conversion program x x

Deleting the conversion log for a plan x

Before running ordered and additional conversion jobs x

Running ordered conversion jobs x

Running additional conversion jobs x

Post-Conversion Task Application Technical

Reviewing and correcting post-conversion integrity x

Reposting the account ledger x

Completing post-conversion tasks x

Converting the production environment x

OneWorld B73.3.1, B73.3.2, and Xe (07/01) About This Workbook

About the Euro Conversion

OneWorld B73.3.1, B73.3.2, and Xe (07/01) About the Euro Conversion

• Test the conversion in a test or conference room pilot (CRP) environment

OneWorld B73.3.1, B73.3.2, and Xe (07/01) About the Euro Conversion

Euro Exchange Rates

40.3399 Belgian francs

How Amounts Are Converted

If an application program is not set up for rounding, the conversion program

• Rounds down amounts less than 0.5

OneWorld B73.3.1, B73.3.2, and Xe (07/01) About the Euro Conversion

• Rounds up amounts greater than or equal to 0.5

Accounts Receivable and Accounts Payable

• For a domestic-only transaction, the original domestic amount (your base

OneWorld B73.3.1, B73.3.2, and Xe (07/01) About the Euro Conversion

• Period amounts in the 01 - 14 or 01 - 52 fiscal period buckets

The euro conversion programs in Procurement, unlike those in Sales Order

OneWorld B73.3.1, B73.3.2, and Xe (07/01) About the Euro Conversion

OneWorld B73.3.1, B73.3.2, and Xe (07/01) About the Euro Conversion

Example: Recalculating PRRC in the Euro

In this example, the following UOM conversion setup applies:

1 From = Quantity To Structure

The following graphic is a visual representation of the calculations in this example:

To recalculate a unit cost amount in purchasing (PRRC), the conversion programs

1. 25,565 + 0.00 (AEXP + ACHG) = 25,565 EUR (5 cases)

G Foreign Non-EMU Transaction