Ledger Conversion (LCN)

This is the business unit to be used as the basis of the ledger conversion. The transactions posted to this business unit are used as the basis for the Ledger Conversion.

The source business unit includes these fields:

Value 1 Currency/Pivot

The Value 1, base currency set for the source business unit is displayed automatically. If this is the pivot currency it is indicated alongside.

Value 2 Pivot

If Value 2 is set as the pivot currency this is indicated. The value 2 currency can vary from one transaction to another, so a currency code is not displayed.

Value 3 Currency/Pivot

If a Value 3, second base or reporting, currency is defined for the source business unit it is displayed automatically. If this is the pivot currency, this is indicated alongside.

Memo Value

If the Memo Value is in use for the source business unit this is identified.

The business unit into which Ledger Conversion (LCN) generates and posts new transactions. This business unit must have been defined and static data must have been setup.

If a currency value is not being used for the target business unit, you are not able to enter the Source or Currency values. A currency value is not in use if the relevant Currency Post Rule is set to Undefined in Business Unit Setup (BUA).

• 1 to swap the Value 1 source values into the appropriate target value.
• 2 to swap the Value 2 source values into the appropriate target value.
• 3 to swap the Value 3 source values into the appropriate target value.
• M to swap the Memo source values into the equivalent target value.
• + to generate the values using the rates defined for the currency code specified. You can only generate Value 1 and Value 3 values.
• - to blank out the existing values in the target business unit.

You must enter one of the following codes to define the conversion requirements for each of the available Source values on the target business unit:

Ledger Conversion (LCN) uses the source and target business unit definitions to predict your requirements. For example, if EUR is defined as the Value 1 currency on the source business unit and as the Value 3 currency on the target business unit, the system assumes you want to swap Value 1 into Value 3 and sets the flag accordingly. You can override any of the system's default settings.

For each value 1/2/3/Memo value on the target business unit, the Source Value identifies the value on the source business unit ledger transactions to be swapped into, or used to generate, the equivalent target business unit ledger transactions.

Specify this information, clicking OK after each value entered:

Currency

The Value 1 and Value 3 currency codes are displayed from the target business unit setup.

If either of these currencies is different to the Value 1 and Value 3 currencies used in the source business unit, the system checks to ensure that currency conversion codes exist to convert from the source currencies to the target currencies, via the pivot. An error message appears if these codes have not been defined.

Value 1/2/3 Pivot

The pivot currency set for the business unit is indicated alongside the relevant currency. This is set using Business Unit Setup (BUA).

Validate Only

Set this option to validate the ledger conversion rules and produces a report of any errors. This option does not generate or post any transactions to the target business unit.

Journal Type

The journal type to be used for the transactions generated by Ledger Conversion. This journal type must be defined in both the source and target business units. Journal types are defined using Journal Types (JNT).

Balancing Option

Determines the level at which the generated journal transactions must balance. Three options are available:

• Period - the transactions generated for each accounting period must balance.
• Year - the transactions generated for each accounting year must balance.
• Total - the transactions must balance overall.

The option you choose here determines the number of balancing transactions that may be generated. For example, if you choose Period, a balancing transaction is generated for each accounting period that does not balance.

Posting Type

If provisional postings are optional for the target business unit, you can choose to post the transactions as provisional or permanent postings.

Include Tables to Process

Set this option to process the appropriate type of Financials data. The data files are processed in the order they appear on the window. If more than one budget file exists you can choose whether or not to convert these individually. However, if several archive files exist you must either convert them all, or not convert them at all, in the same run.

If the static data required to convert a particular type of data does not exist in the target business unit, you cannot select the data type. For example, if the currency code rates have not been defined.

If you are rerunning Ledger Conversion and you have successfully converted a data type, you can choose to reconvert the data type. For example, if you have already successfully converted the ledger transactions and now want to convert the budget transactions in a second run, you can select the Ledger File option again. In this case, a warning message is displayed.

%Complete

The percentage of source transactions that have been converted. This appears while the Ledger Conversion is processing to indicate its progress.

Error Count

The number of errors identified during the Ledger Conversion process. For example, if an account code, currency code or currency rate does not exist in the target business unit.

Click Process to begin the ledger conversion process.