Add 51 Sa

Scala 5.
1
Addendum
Part 3 – System Administration
1
 Copyright 1999 - 2001 Scala ECE (Overseas) Ltd. All Rights Reserved. No Reproduction Without
Permission.
This material is the sole property of Scala ECE (Overseas) Ltd., and is under the protection of the
Berne Convention and other applicable local laws. Any duplication, reproduction, copying or usage of
this material or the software programs and other protected material described herein without the
expressed written permission of Scala ECE (Overseas) Ltd. is illegal and any person or company in
violation will be prosecuted for damages.
All other trademarks are registered to their respective owners.
This edition describes version 5.1.
Publication number: EN-2003-C-0301 2

CONTENTS
Contents
Preface __________________________________________________________________________6
System Utilities ____________________________________________________________________7
Feature Activation_______________________________________________________________7
RTF Option ___________________________________________________________________7
RTF Spool File Options _______________________________________________________7
Changing System Date ___________________________________________________________8
Creating New Data Files __________________________________________________________8
Rebuilding Files ________________________________________________________________9
Rebuilding Stock_______________________________________________________________11
Utility Description __________________________________________________________11
Algorithm Specification ______________________________________________________13
Cost Options _______________________________________________________________13
Limitations ________________________________________________________________14
Supplement________________________________________________________________14
Copying Automatic Accounting Schedule ___________________________________________18
EMU Data Conversion __________________________________________________________20
EMU Conversion Wizard _____________________________________________________20
Description of Conversion Utilities _____________________________________________22
Deleting Old Data after EMU Conversion ___________________________________________40
Information on EMU Conversion in Company File ____________________________________41
Basis for VAT calculation _______________________________________________________41
Note on ScaComp and ScaUser ___________________________________________________41
Creating Companies with Own Menus _____________________________________________41
User File Security ______________________________________________________________42
Special Prefix to Be Used for Scala Commands ______________________________________43
Scala Backup/Restore Procedure __________________________________________________44
Scala SQL_________________________________________________________________44
Currency System ______________________________________________________________45
Currency Types ____________________________________________________________45
Activating Currency System___________________________________________________46
EMU Coefficients___________________________________________________________47
Currency Definition _________________________________________________________48
Central Currency Register ____________________________________________________49
Printing Currency System_____________________________________________________51
Entering Currency Rates______________________________________________________52
Enquiring Currency Rates ____________________________________________________54
Rounding Parameters ________________________________________________________54
Currency Calculator _________________________________________________________57
Currency Calculator ____________________________________________________________57
Rounding Tolerance for Invoice Closing ____________________________________________58
Three Decimals Option in VAT Rate _______________________________________________58
Additional Multilingual Support __________________________________________________58
Menu Customisation for Currency System options ____________________________________59
Currency System Converter (Scala 5.0 to Scala 5.1) ___________________________________59
Restricted Usage of Quotation Marks with Text Variables and Commas in Input-Output Files __60
Compulsory VAT Code 00 ______________________________________________________60
Language Dependent Tax Name __________________________________________________60
Tax Rounding and Calculation Options for Customers and Suppliers ______________________60
3
CONTENTS
Integration of Third Party Products into Scala ________________________________________61

Emeritor Integration _________________________________________________________61
Transferring Scala Data to Other Applications _______________________________________62
Changes in Scala Menu Default Settings ____________________________________________64
DDF ____________________________________________________________________________65
General ______________________________________________________________________65
Additions to Extended DDF Format_____________________________________________65
Year Date Format __________________________________________________________67
DDF Codes for Replacement Items _____________________________________________69
General Ledger ________________________________________________________________70
Coding Slip _______________________________________________________________70
Example of DDF File for Periodic Transaction Remeasurement Report ________________70
Sales Ledger __________________________________________________________________70
DDF Code for Invoice Currency Balance in Statement by Date _______________________70
DDF Codes for Location Information (US/Canada) ________________________________71
Purchase Ledger _______________________________________________________________71
Statement by Supplier _______________________________________________________71
Sales Order ___________________________________________________________________71
Common DDF Codes in Sales Order Documents __________________________________71
DDF Code for Gross Amount _________________________________________________77
New DDF Codes in Sales Order Documents ______________________________________77
New DDF Codes in Sales Order Documents ______________________________________78
DDF Code for Other Tax Amount in Sales Order and Direct Invoicing Document Lines ___78
DDF Codes for Price for Internal Customer ______________________________________78
DDF Code for Historical Invoice Prefix _________________________________________79
New DDF Codes for Invoice/Credit Note/History Invoice ___________________________79
Cash Discount and VAT DDF Codes (Invoice Credit Note/History Invoice) _____________83
DDF Codes for Allocation Quantity in Delivery Proposal____________________________85
Order Consolidation ________________________________________________________85
Correct Example for Delivery Note/History Delivery Note __________________________86
DDF Codes for Customer Stock Code (Invoice/Credit Note/History Invoice, Tax Invoice,
Quotation, Order Confirmation, Delivery Note/History Delivery Note, Delivery Proposal,
Product Label) _____________________________________________________________87
Unavailable DDF Codes in Delivery Note/History Delivery Note _____________________87
Unavailable DDF Codes in Product Label _______________________________________87
Unavailable DDF Codes in Summarised Export Document __________________________87
Changes in DDF Codes for Transport Documents _________________________________87
Purchase Order ________________________________________________________________88
Purchase Order, Order Confirmation Reminder, Delivery Reminder: ___________________88
DDF Codes from Stock Control ________________________________________________88
New DDF Unit Codes _______________________________________________________88
New DDF Code for Customer Order Number (for Direct Orders)______________________88
DDF Code for Undelivered Quantity ____________________________________________88
DDF Codes for Stock Items’ Text Lines and Extra Descriptions_______________________88
DDF Codes for Body 3 Section in Goods Received Note ____________________________89
New DDF Code for Goods Received Note Number ________________________________90
Direct Invoicing _______________________________________________________________90
DDF Code for Tax Name in Invoice/Credit Note __________________________________90
DDF Code for Other Tax Amount in Invoice Line _________________________________90
Project Management ____________________________________________________________91
FloatEnd Lines with Asterisks in Invoice, Credit Note, and Invoice Proposal ____________91
Printing Serial Number and Extra Text in Invoice _________________________________91
Service Management____________________________________________________________91
DDF Code for Document Flag, Proforma Invoice _________________________________91
Correct DDF Codes for Price per Unit in Quotation and Order Confirmation ____________91
DDF Changes for Quotation and Order Confirmation ______________________________92
4
CONTENTS
DDF Changes for Picking Lists ________________________________________________92

MPC ________________________________________________________________________93
Printing Extra Stock Items ____________________________________________________93
Configuration ______________________________________________________________93
Payroll _______________________________________________________________________98
Payslip DDF Codes Enhancement ______________________________________________98
System Utilities ________________________________________________________________98
DDF File for VAT Report ____________________________________________________98
Country Specific Documents _____________________________________________________99
DDF Code for Delivery State Code in US/Canada Purchase Order, Order Confirmation, and
Delivery Reminder _________________________________________________________99
DDF Codes for United Kingdom Cheque ________________________________________99
New DDF Codes and Files for Finnish Transport Documents _______________________104
For Russia: Payment Method R1 (Domestic Payments to CitiBank) and Payment Method R2
(Foreign Payments to CitiBank) _______________________________________________107
Country Specific Utilities _________________________________________________________113
US/Canada __________________________________________________________________113
State and ZIP Codes for International Locations __________________________________113
ZIP Code Length for Companies with No Taxware Installed ________________________113
ZIP Code Length Extension for Companies with Taxware Installed __________________113
Hungary_____________________________________________________________________113
Purchase VAT Reports _____________________________________________________113
UK, Belgium _________________________________________________________________115
Calculating VAT __________________________________________________________115
Germany ____________________________________________________________________116
German Payment Method in Sales Ledger and Purchase Ledger Modules ______________116
Israel _______________________________________________________________________116
Extended Tax Support ______________________________________________________116
Working with Scala ______________________________________________________________121
Scala Automation Manager _____________________________________________________121
Organising Projects ________________________________________________________121
Using Macros _____________________________________________________________123
Scala e-Repository _________________________________________________________124
Deleting Customised Button from Scala Toolbar ____________________________________124
Scala Menu External Links _____________________________________________________124
Troubleshooting _________________________________________________________________126
Troubleshooting Blocking Sessions when Generating Long Reports _____________________126
Troubleshooting Scala Backup on MS SQL 2000 ____________________________________127
Country Specific ______________________________________________________________127
Sorting with Japanese Regional Settings ________________________________________127
List of New Features and Corrected Bugs ____________________________________________128
5
PREFACE
Preface
This addendum includes descriptions of Scala 5.1 features and corrected bugs that were not included in
Scala mainstream manuals for:
• System Utilities
• DDF
• Country Specific Utilities
• Working with Scala
The respective service pack and bug log numbers are given in brackets alongside headings.
All screen shots and reports are included for visualisation purposes only and contain dummy data.
6
SYSTEM UTILITIES
System Utilities
Feature Activation
Search path:
Miscellaneous – Features Activation Set–up
Use this routine to enable/disable Scala features.
Only features developed in a special way and activated/deactivated by this routine are affected.
With the features activation routine, you can:
• Edit features activated for the current company (Edit Feature Set-up)
space enable/disable features
Enter save settings and exit
Esc exit
• Copy features settings from other company/country (Copy Feature Set-up from…)
• Merge features settings from other company/country (Merge Feature Set-up from…)
• Update default features settings per country from external file supplied with the Scala system
(Import default features per country)
The country features external file can be amended with Scala upgrades.
RTF Option (SP01)

Setup Changes
The setup for DDFs in RTF formats is as outlined below. For more information about the setup, refer to
the Scala System Utilities User’s Guide. For information on installing DDFs in RTF format, refer to the
Scala Installation and Operation Instruction.
• Set the System Utilities – Documents/Installation – Printer Connections, Spool Method field to
6 (to save a DDF directly in RTF format) or to 7 (to save a DDF in RTF format and be able to
open it in Microsoft Word).
Microsoft Word must have been installed to open the DDF in RTF format.
The fonts used to construct the DDF-files must be available in Microsoft Word.
This is relevant for the following modules: General Ledger, Sales Ledger, Purchase Ledger, Stock
Control, Sales Order, Purchase Control, Direct Invoicing, Project Management, Service Management,
Payroll, Promissory Notes, Market Database.
RTF Spool File Options (#30032)

For system administrators only!
Search path:
Scala Menu Bar – Tools – Customise – Miscellaneous tab – RTF viewer group box
When printing Scala documents using RTF-files, the following is available:
1. If the Use windows default check box is selected:
When printing, the document is loaded to Microsoft Word where the user can edit and print it.
2. If the Use windows default check box is cleared:
7
SYSTEM UTILITIES
Scala documents printing routine is determined by the file specified in the File name list. This file
could be a script-file, written according to business requirements, or any RTF viewer (executable
file).
An example of a script-file (PrintRTF.js) written on the Windows batch command language
(Windows Script Host) is shown below. If specified in the File name list, this file creates the
Microsoft Word instance, opens and prints a document, closes Microsoft Word, and leaves or
deletes a RTF spool file depending of the user choice in the respective dialog box.
An example of an RTF viewer executable file is WordView.exe.
PrintRTF.js
// Some constants defenition
var vbOKOnly = 0;
var vbOKCancel = 1;
var vbYesNo = 4;
var vbQuestion = 32;
var vbInformation = 64;
var vbCancel = 2;
var vbYes = 6;
// Shell creation to be able to interact with the user

var WSHShell = WScript.CreateObject("WScript.Shell");
// Check if we have exactly 1 parameter

if (WScript.Arguments.length!=1)
{
WSHShell.Popup("Invalid number of parameters!",0,"Printout Script",0);

WScript.Quit();
// Create Word object

var objWord = WScript.CreateObject("Word.Application");
// Minimize window
objWord.WindowState=2;
// Open document
var objDoc = objWord.Documents.Open(WScript.Arguments(0), false,false,false ,"","", false,"","",0);
// Print document
objDoc.Printout();
// Wait for printout finishing

while (objWord.BackgroundPrintingStatus==1) {};
// Close Word
objDoc.Close(false,0,0);
objWord.Quit();
var intButton
// Ask user for file deletion
intButton = WSHShell.Popup("Would you like to delete the file "+WScript.Arguments(0)+"?",0,"Printout Script",vbQuestion + vbYesNo);
// Delete if needed
if (intButton == vbYes)
{
WSHShell.Run ("command.com /c del "+WScript.Arguments(0), 2, true);
}
//Quit from script

WScript.Quit();
Changing System Date (#30603)

Search Path:
Miscellaneous – Change System Date
Warning!
Be aware that the changed system date applies only to the current session.
It is recommended to change the system date while logging on to Scala (System Date field).
Creating New Data Files

Search Path:
Create/Check Files – Create New Data Files
2. Only Year Dependent Files
y Create year-dependent data files only.
Warning!
(#23533)
The Copy Parameter Files option (next field) will be
unavailable.
8
SYSTEM UTILITIES
n Create all data files for selected modules.

3. Copy Parameter Files
y Copy module’s parameter files from another company and/or another
financial year.
To copy the Chart of Accounts, use the Chart of Accounts copying routine
(General Ledger – Miscellaneous – Special Utilities – Copy Chart of
Accounts). For more information, see the Scala General Ledger User’s
Guide.
To copy the Automatic Accounting Schedules, use the Copy Automatic
Accounting Schedule routine. See the respective section in the Software
Reference – File Checks – Special Data File Function chapter for details.
n No copying of parameters is required.
If you copy parameter files, in the next two fields, enter the company and/or financial year to copy
from and specify whether the previously set up parameters are to be overwritten or not:
4. From Company Code
5. From Financial Year
(SP11) (#31794)
6. Retain existing parameters?
y Parameters will be copied only to the newly created files.
n Parameters will be copied to all files; the previously set up parameters will be
overwritten.
After the above parameters have been selected, the program displays a menu of installed Scala
modules.
The following options are available:
+
space Select/deselect the highlighted module.
- Deselect all modules.
* Create all non-existing files for each module.
Enter To continue
Esc To return to selection criteria.
If only one particular module has been selected, you can specify the module’s files to be created. For
selecting files use the same method as for selecting modules.
In case if only one module and only one module file have been selected, Scala will check that the file is
not already on disk. If the file exists, confirm the new (empty) file creating. For security reasons, the
old file will be saved with the extension .old. If a file with an extension of .old already exists, confirm
its deletion.
Warning!
Be careful when you create a file that already exists. After the new file is created, all the
information in the old file will be deleted.
If more than one module file has been selected, Scala will automatically check files on disk and
create only non-existing ones.
Rebuilding Files
Search Path:
Create/Check Files – Rebuild Data & Index Files
Only the system manager (SYS) can use this routine.
There are two reasons for rebuilding:
9
SYSTEM UTILITIES
• The most common reason is that there has been an interruption in operations, e.g. a power failure.
Usually, your data files remained intact but the indexes (i.e. file keys such as customer code for the
customer file) became invalid.
Run the rebuild routine to recreate valid indexes.
The rebuilding routine never damages indexes.
Warning!
There is no 100% guarantee that the rebuilding routine will restore all data. The only way to
guarantee this is to restore from backup.
• The second reason is that you want to reduce the size of files (for Btrieve database) as Scala files
increase in size as you enter data but there is no other routine for reducing the files size.
Run the rebuild routine to purge all deleted items from the file.
The rebuilding routine differs for Btrieve and SQL databases.
(#19236)
For Btrieve database, the rebuilding routine checks data files of the company you are currently
working with, purges all invalid and deleted items and recreates indexes. The system saves old files
with the extension .old. This provides a full backup security, even in case of a power failure during
rebuilding.
Check disk space to avoid “disk full” problems before rebuilding. If there is a lack of disk space,
use Delete Data Files menu option to delete all files with the extension .old.
Warning!
Never rerun the rebuilding routine if it has been already run unsuccessfully, without first taking a
backup of the .old files created while first rebuilding. Otherwise, the second run will remove the
newly created .old files, which are the only backup of the files on disk.
(SP02)
For SQL database, the rebuilding routine checks indexes for data files of the company you are
currently working with after the Scala database index structure; if some indexes are missing, they will
be recreated.
For SQL database, no old files will be created.
In addition to the file validity checks (i.e., all Scala routines can read and write from/to the file), an
extended check is possible for some Scala files. For example, you can check that the balance in the
customer file agrees with the customer invoices in the Sales Ledger. These checking routines are
available under the Special Data File Functions menu option.
The company file and the user file cannot be rebuilt with the rebuilding routine. To rebuild these
files, use the ScaComp and ScaUser programs. See the Special Programs chapter for details.
To run the rebuilding routine, follow the steps described below:
1. Financial Year
Enter the year for the year dependent files to be rebuilt.
The field is available for Btrieve database only.
Only certain files are year dependent.
2. Year Dependent Files Only
y Only year dependent files for the financial year, specified in the previous
field, will be rebuilt.
n All files will be rebuilt.
The field is available for Btrieve database only.
3. Select the module for rebuilding files.
↑
↓ To move between modules.
+
space To select/deselect modules.
10
SYSTEM UTILITIES
* To select all modules.

– To cancel all previous selections.
Esc To return to the previous screen.
Enter To continue.
2. Confirm starting the rebuilding routine.
For Btrieve database, after you have chosen a particular module, the list of module’s files will display.
If you know which files need rebuilding, select them the same way as for the module. If a file with the
extension .old remains from previous rebuilding, you will be prompted to confirm the old file deletion
before rebuilding start. If you have selected all module’s files to be rebuilt, old files will be
automatically deleted.
Rebuilding Stock
Search Path:
Create/Check Files – Special Data File Functions – Rebuild Stock
Utility Description
Reasons for Having the Utility
The first reason for having the Stock Rebuild Utility is that the old versions of Scala did not support the
stock in the consolidating currency. After conversion of data to Scala 5.x, the fields with costs in
consolidating currency must be populated with correct values.
The other reason is that the balance of stock item in a warehouse differs from the balance calculated by
stock transactions in the old versions of Scala.
And the third reason is the necessity to rectify some errors in stock data. See the list of such errors in
Supplement below.
Data Affected
The Stock Rebuild utility affects the following files:
1. Statistics and balance in Stock Item File (SC01)
2. Balances in Stock Location file (SC03)
3. Stock Transactions file (SC07)
4. Batch file (SC33)
5. Batch Costs file (SC34)
The utility affects quantity and both accounting (local) and consolidating currencies (LCU and CCU):
Statistics and Balance in Stock Item File

For selected stock items, the Utility deletes data from the following fields:
Field No. Description of the Field
SC01042 Stock Balance (All Wh) [SCUNIT]
SC01046 Stock Tacking Diff (All Wh) [SCUNIT]
SC01048 Latest Stock Taking Date (Std Whouse)
SC01049 Latest Delivery Date from supplier
SC01050 Latest Delivery Date to Customer
SC01052 Average Cost Price
[LCU/PPMULT*SCUNIT]
SC01054 Qty Received from supplier [SCUNIT]
SC01077 Profit Period [LCU]
SC01078 Profit YTD [LCU]
SC01081 Sales Period [LCU]
SC01082 Sales YTD [LCU]
11
SYSTEM UTILITIES
SC01085 Qty Period [SCUNIT]

SC01086 Qty YTD [SCUNIT]
These fields are updated when stock transactions are processed. If stock items are out of selection
range, the listed fields remain unchanged.
Statistics and Balance in Stock Location File

For selected stock items, the Utility deletes data from the following fields:

SC03003 Stock Balance
SC03007 Stock Tacking Difference
SC03009 Latest Stock Taking Date
SC03014 Lowest Purchase Price
SC03017 Stock Taking Difference Value
SC03029 FIFO Value [LCU/PPMULT*SCUNIT]
SC03054 Latest Delivery Date from supplier
SC03055 Latest Delivery Date to Customer
SC03057 Average Cost Price [LCU/PPMULT*SCUNIT]
SC03064 Average Cost Price [CCU/PPMULT*SCUNIT]
SC03067 Lowest Purchase Price [CCU/PPMULT*SCUNIT]
SC03099 Turnover File.
These fields are updated when stock transactions are processed. If stock items are out of selection
range, the listed fields remain unchanged.
Batch File
Before to start, the Batch file is renamed to SC3Vcc00.DAT file, then the new SC33cc00.DAT file is
created. After completion of rebuild, the batch file is updated with extended batch information for the
selected stock items. The following are the fields to be updated:

SC33006 Allocated Qty
SC33007 Ordered Qty
SC33008 Lock Status
SC33011 Search Field
SC33014 Date Manufactured
SC33015 Date Best Before
SC33016 Date Ship Before
SC33017 Batch Source
SC33022 Supplier Batch ID
SC33024 User Defined field 1
SC33025 User Defined Field 2
12
SYSTEM UTILITIES

For unselected stock items, the complete record is copied from the old batch file to a newly created
one.
Batch Costs File

The Batch Cost file is completely rebuilt for selected stock items.
Algorithm Specification
The original stock transactions file is renamed to the SC07ccVK file, and a new stock transactions file
is created. For selected stock items, stock transactions are read from the old file (SC07ccVK) and are
written to the new SC07cc00 file once the transformation in keeping with the rule of Scala algorithms
has been done. Unselected stock items are copied without transformation.
The same is done for batch file SC33CC00.
If the received results run counter to the expected ones, the original transactions file can be
restored from the SC07ccVK file to the SC07cc00 file and the batch file SC33cc00 can be restored
from the SC33ccVK file.
Backup of master files SC01, SC03 and the SC34 file is not done automatically. Thus, it is
recommended to make a reserved copy of data before rebuilding.
During rebuild the following takes place:
1. Batch numbers are kept as in the original file, except negative batches. If stock transactions were
created in RV6, RV7 or AM versions with more than 5 FIFO batches, some batches are hidden in
stock transactions and the balances of such batches are erroneous. The utility retrieves such
batches, providing the tracibility of them.
2. Transactions of type 07 are ignored and recreated automatically.
3. Transactions of type 10 are ignored and recreated automatically after transactions of type 03 if the
balance is negative.
4. Transactions of type 06 are renamed to type 03, then, if necessary, transactions of type 10 are
created. It depends on the value of the currently calculated balance for the batch if the batch is
given in the transaction or depends on total balance if the batch is not given.
5. Compressed transactions (batch number “************”) remain of type 01, but are considered as
receipt transactions. They affect oncost of goods.
6. Transactions of type 01 with positive quantity are treated as returns of goods. Returns of goods can
be done by either the historical cost or currently calculated cost in accord with the given valuation
model. The way of usage is asked by the utility.
Cost Options
Scala asks how to process cost for the consolidating currency and how to process cost of goods return.
Costs for Consolidating Currency

Calculation of costs in consolidating currency is defined by the value of the "Cost of Purchase in CC
from Transaction File ?" switch. If the switch is set to yes, the value of the cost is taken from the
transaction record. If the switch is set to no, the cost in consolidating currency is calculated for
13
SYSTEM UTILITIES
transactions of type 00, 03, 06 with the exchange rate on the date of transaction. For transactions of
type 01, 02, 04, 07, CCU cost is taken from the stock location file or the batch file.
The transaction of type 08 can be calculated automatically for the local currency or can be created
during adjustment of proper costs (Average price, FIFO values, Standard costs, depending on the stock
valuation model) separately for LCU and CCU. By this reason the values for transactions of type 08 are
taken from the transaction file. If cost in CCU is zero, it will retain the zero value.
The transactions of type 03 with cost type 08 for consolidating currency are always taken from the
stock transaction file. The respective values are generated in the purchase control and should not be
changed during rebuild.
Costs of Transactions for Goods Return

Transactions of type 01 with positive quantity are treated as returns of goods. Returns of goods can be
done either by historical or by currently calculated cost in keeping with the given valuation model.
If historical cost of return is selected, the cost of return is taken from the stock transaction file and the
average cost is recalculated.
If the currently calculated cost of return is selected, the currently calculated cost is written to the stock
transaction file. The cost is retained.
Limitations
When the Stock Rebuild utility cannot help.
• The valuation model of standard costs is used.
The reason: the last calculated standard costs are applied to the whole history of stock transactions.
(SP11) (#31937)
The Standard Cost stock valuation model may produce incorrect results when
rebuilding stock.
• The valuation model was changed.
The reason: the last valuation model is used.
(SP11) (#31938)
The Rebuilding Stock utility uses the latest stock valuation model set in the stock
parameters.
• The forward cover was used for purchase orders and consolidating currency cost should be
calculated by cost in local currency with the exchange rate for delivery rate.
What to do if the cost of goods in a warehouse is changed after rebuild

It is recommended to run the End of Period report (reports type 1 and 2) before rebuilding the stock and
afterwards.
The End of Period report contains subtotals by accounting code after total by warehouse.
Accounting code defines debit and credit accounts for the receipt and issue transactions (see automatic
accounting schedule).
If you run these reports before rebuilding and afterwards, you will easily be able to calculate the
difference by accounts connected to stock. These differences can be put to the accounts in the General
Ledger.
Supplement
List of Problems that CAN be Fixed by the Utility
Old versions of Scala contained bugs that resulted in data misrepresentation.
1. FIFO value is not recalculated when goods are returned to stock with the changed cost
14
SYSTEM UTILITIES
Example:
This bug can be reproduced manually in three steps:
Use the stock item with "Extended batch information" = Yes;
Make receipt of the stock item with price A1 and batch B1;
Make partial issue of the B1 batch of the stock item;
Create a credit sales order (type 8). When entering, change the cost of stock item to A2, then select
batch number B1 for returning goods;
At this moment Scala does not recalculate FIFO value or average cost.
If this is the only batch and you withdraw the item completely, you will receive zero quantity with
non-zero cost of stock (in the stock transaction list).
2. When issuing goods, Scala generates unexpected issue transactions (not always)
Example:
”Decimals in Own Currency”: 2 in the company file;
”Number of Decimals, Quantities”: 3 in SC Units parameters.
Enter some receive transactions to the new item with different batches; for example, enter the
quantities with 1 amount in price in the following sequence:
Date Quantity
981014 0.0921
981028 0.11
981028 0.25 1
981028 0.11
981026 0.2681
981102 0.5821
981124 0.0091
981123 0.0611
981119 0.0481
981118 0.0531
981112 0.0661
981110 0.0761
981230 20.001
Enter the issue transactions with the quantities: 1.51, 0.053, 0.066, 0.076, 18.295 .
Print the Stock Tr. List (SC/Transaction/Stock Tr. List). You can see that the entered quantities are
split by Scala, and the fifth quantity (18.295) is split into two parts: 6.776 + 18.295 instead of
18.295.
It happens when you make the complete issue of stock item with big quantity of batches. These
batches should have balance with fractional quantities. Scala (internally) splits your issue to
separate batches in several steps. On every step, Scala subtracts the rest to be issued and finally
calculates not zero value, but something like 6.12345678901234567890E-21. Because the length
of the quantity is greater than 20 characters, the right part of the string ("E-21") is truncated when
the value is being written to the database.
3. When average cost becomes negative, Scala uses an absolute value for the issue of batches
15
SYSTEM UTILITIES
Example:
Average price valuation model is set up.
Receive 10 units by 1$ (order 1), 10 units by 100$(order 2);
Issue 10 units with cost 50.5$;
Receive 6 units for order 2 with price 100$;
Average cost is now 23.75$. The balance is 4 units. Amount is 95$;
Issue 4 units. Scala writes off these units with 23.75$ instead of 23.75 $;
Now balance is 0, amount is 190.
4. Wrong calculation of FIFO value if balance of a batch was increased not via the stock receipt
transaction, and if costs were added to this batch
Example:
Valuation model is FIFO.
The list of transactions is given below;
Stock item has extended batch information = yes;
Receive one batch;
Stock taking transaction is done to the same batch;
Additional costs are entered to the same batch;
All items from the batch are issued;
The result is zero balance with non-zero amount.
TEST * * STOCK TRANSACTION LIST * * 09/15/99 18:20:55 Page 1

FOR PERIOD 00/00/00 -- 99/99/99
01 - Main Moscow
Currency Code : RUB
COMPANY 01 FIN.YEAR 99===============================================================================================/Scala/SC0061/5
STOCK CODE---------- DESCRIPTION-------------- PURCHASES/SALES-------------------------- BALANCE---------------------------------
DATE-- WAREH. TT CT BATCH------- ORDER----- REF.-I AMOUNT QTY PRICE/EA QTY AMOUNT PRICE/EA
====================================================================================================================================
VE
091599 01 00 000000010807 200.00 2 100.00 2 200.00 100.0000
091599 01 02 000000010807 100.00 1 100.00 3 300.00 100.0000
091599 01 03 02 000000010807 300.00 300.00 3 600.00 200.0000
091599 01 01 000000010807 750.00- 3- 250.00 0 150.00- 0.0000
------------- ------------ ------------
SUB TOTAL 0 150.00- 0.0000
STOCK VALUE: 200.0000
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
TOTAL FOR WAREHOUSE 0.0000 150.00- 0.0000
1. The same result is if return of goods is done (through sales order or stock) to the same batch
instead of the stock taking inventory.
2. The same result is if you work in Scala versions prior to versions 4.x or 5.x. and have the
following transactions:
Receive batch to the first warehouse;
Move the first part of the batch to the second warehouse;
Move the second part of the same batch to the second warehouse;
Add costs for the batch in the second warehouse;
Convert to Scala 5.0;
Run the Stock Rebuild utility.
List of Problems that CANNOT be Fixed by the Utility

1. Wrong processing of small prices in currency (the bug is fixed, but old stock records are
retained in the system)
16
SYSTEM UTILITIES
The exchange rate on the date of stock transaction is used instead of the forward cover rate, which
is set up in purchase order line.
Example:
Create purchase order with the following parameters:
Quantity = 500000
Price = 0.04$ per 100 inits (0.0004$ per unit)
Forward cover = Y
Rate for the forward cover = 10Rub /$
Set up the rate for the delivery date = 27Rub /$.
Make delivery for the order
Check stock transaction costs
The result is:
In Rub cost = 0.004 Rub (transfer price 1), total cost = 2000 Rub
In $ cost = 0.000148148148 (transfer price 2), total cost = 77.57$ (instead of 200$)
2. Wrong processing when a zero balance of stock and stock batch exists with a negative
quantity
In the old versions of Scala the following was processed erroneously:
Create Purchase order of 10 units of item A1;
Receive 10 units of Item A1 batch 1 with cost C1;
Issue 3 units of stock item A1 from a warehouse;
Delete the order line from the purchase order;
Scala recorded 3 units for the batch 1. (Batch 1 had a 12 digits number without special number like
******xxxxxx, where xxxxxx is a number);
Receive 3 units of item A1 to the batch 2 with cost C2;
Scala did not reverse batch 1;
Balance was 0 quantity and cost C2-C1.
WORKAROUND
Set up the parameter batch control for the stock item A1 to yes;
Create stock taking transactions for every batch individually putting balance to 0 quantity;
Return the parameter batch control for the stock item A1 to its original value.
Known Problems
Wrong Processing of Negative Batch Created when Balance is Positive
Example:
Receive one batch of stock item (10 items);
Change the batch status from 0 to 1 (lock the batch for any issue);
Issue, say, 3 items. Scala creates a negative batch without touching the locked batch;
Change the batch status from 1 to 0 (unlock the batch for issue);
Issue 7 items;
You will have 2 batches in stock: 3 items for the real batch and 3 items for the negative batch;
17
SYSTEM UTILITIES
Run the Stock Rebuild utility. Scala will not create the negative batch and will issue the real batch;
Finally we will have 0 balance.
Real and negative batches can have their own costs. It is unimportant from regarding the balance, but if
transactions belong to the different reporting periods, it may become important.
(SP11) (#27865)
If you ever had negative balance and the respective batch is blocked, the system may
produce incorrect results when rebuilding stock.
Copying Automatic Accounting Schedule (SP02)

Search Path:
Create/Check Files – Special Data File Functions – Copy Automatic Accounting Schedule
Use the routine: To copy the Automatic Accounting Schedule of the

selected module, company and financial year to the
same module of the current company and current
financial year.
Normal reasons for Setting up the Automatic Accounting Schedule after
use: the Automatic Accounting Schedule of the other
company and/or other financial year.
What the routine does: Copies links of the Automatic Accounting Schedule
positions with the account numbers from the source
company and selected financial year to the current
company and current financial year.
General remarks: If the respective module of the current company from
which the Automatic Accounting Schedule is copied
is integrated with the General Ledger, the routine will
check the compatibility of the accounts being copied
with the company’s Chart of Accounts; the non-
existing and statistical accounts will be reported but
still can be copied.
1. Select the module to copy the Automatic Accounting Schedule from.

2. Source Company
Enter the code of the company to copy the Automatic Accounting Schedule from.
? (company codes)
3. Source Year
Enter the financial year to copy the Automatic Accounting Schedule from.
Warning!
The Automatic Accounting Schedule for the selected company and financial year must exist.
The report on the Automatic Accounting Schedule of the current company, financial year and selected
module will be printed.
An example of the printout is as follows:
Scala 5.1................ COPY AUTOMATIC ACCOUNTING SCHEDULE 99-01-10 16:16:06 Page 1
COMPANY 01 FIN.YEAR 98=========================================================================/Scala/SY0145/5
NO-- TEXT----------------------------- ACC.NO------ * NO-- TEXT----------------------------- ACC.NO------ *
==============================================================================================================
1. Stock Received (00) 000010 S 2. Accr. Received (00) 000011 N
3. Accr. Costs (00) 000012 N 4. Stock Issued (00)
5. Accr. Issued (00) 6. Stock Tak. Diff. (00)
7. Purchase Diff. (00) 8. Purchase Costs (00)
9. Revaluation (00) 10. Stock Received (01)
11. Accr. Received (01) 12. Accr. Costs (01)
13. Stock Issued (01) 14. Accr. Issued (01)
15. Stock Tak. Diff. (01) 16. Purchase Diff. (01)
17. Purchase Costs (01) 18. Revaluation (01)
19. Stock Received (02) 20. Accr. Received (02)
21. Accr. Costs (02) 22. Stock Issued (02)
18
SYSTEM UTILITIES

19
SYSTEM UTILITIES

369. Revaluation (40) 370. Intermediate Acc.
--------------------------------------------------------------------------------------------------------------
2 LINK(S) TO NON-EXISTENT ACCOUNT (MARKED 'N')
1 LINK(S) TO STATISTICAL ACCOUNT (MARKED 'S')
* * * * * * * * * * * * E N D O F R E P O R T * * * * * * * * * * * *
If the current company’s module you copy the Automatic Accounting Schedule for is integrated with
the General Ledger, the accounts will be verified according to the current company’s Chart of
Accounts. The non-existing and statistical accounts will be marked by letters N and S respectively. If
so, you can copy the whole Automatic Accounting Schedule or only “valid records”, i.e., non-statistical
accounts existing in the current Chart of Accounts (All records and Valid records in the displayed
dialog box respectively).
If the module is not integrated with the General Ledger, no verification will be performed, but you can
copy such Automatic Accounting Schedule anyway (All records).
4. Confirm copying.
EMU Data Conversion

Overview
The Economic and Monetary Union means that the Euro will replace the local currencies of the
participating countries. Those currencies will cease to exist in the year 2002. Companies based in
participating countries therefore have to switch their accounting records from local currency to the
Euro at some stage over the next three years. This involves conversion of the company’s data base. All
current year transactions and account balances will need to be converted. Standing data such as price
lists will have to be re stated in Euro. Fixed Assets may have to be converted to Euro. At least some
historic data will have to be converted.
It should be noted that conversion of the database is not a prerequisite for switching to the Euro for
trading, banking and reporting. In a multi-currency system, such as Scala, these functions can be
performed in Euro (or any other currency) regardless of the company’s base currency.
The EMU Conversion Wizard is a utility in Scala 5.1 that helps to manage the conversion of the
company’s database from local currency to Euro. The utility uses the ‘big bang’ approach to
conversion to Euro, i.e., it should be run only once and converts all data at the same time. From the
point at which it is run, the company’s database will be based in Euro. Euro will then become the base
currency of the company. However, data that is in a currency other than the company’s base currency
will not be converted.
The Wizard has the capability to convert current, future and historic data, either automatically or in
manual mode, which gives the user the flexibility to decide which data will be converted. Control of
rounding differences that will occur is an integral part of the utility.
EMU Conversion Wizard

Search Path:
System Utilities – Create/Check Files – EMU Conversion Wizard
The EMU Conversion Wizard is a set of utilities, accessible only to the System Manager, to convert all
the existing data from a source currency into Euro or any other target currency. The Wizard can be run
in two modes:
• Auto mode – where automatic conversion of all data occurs without user’s intervention, but
for setting up the required parameters.
• Manual mode – which is a step-by-step manual process, enabling the user to choose the
routines (modules and individual files in some routines) for conversion. By default, the EMU
Conversion Wizard will run in the manual mode.
20
SYSTEM UTILITIES
Before running the EMU Conversion Wizard, make sure to run the Rebuild Data and Index Files
option from System Utilities. All data files and indexes will be rebuilt for the selected modules and
files. All journals in all modules (General Ledger daybook journal, invoices journal in Sales Ledger,
etc.) must be updated before the wizard is run. The Wizard will not run if there are any unposted
journals.
The EMU converter will convert the data for the company that we log into, for the financial year that
we are logged into. For example, if we log into Scala in financial year 98, the data from the beginning
of the financial year 98 will be converted. By financial year, we mean the year as defined in the
General Ledger parameters, which may not be the calendar year. The data that is converted includes
both current year and year independent data, such as credit limits.
Normally we would log into the current financial year, but we can log into and run the converter for
future years provided they have been set up in the company file. The earliest year that the converter
will allow us to convert is the current financial year – that is the one that today’s system date falls into.
We cannot convert earlier years.
It is necessary to print and clear all journals before running the EMU Conversion Wizard. Future
year refers to any of the years (subsequent to the current year) defined in the company files. Prior
to running the database conversion, users should consider purging the database of all superseded
material and reconciling all control accounts with the underlying detail.
Automatic Mode
In automatic mode, all the conversion steps are selected and run by the system automatically by
selecting the Auto Run option from the EMU Conversion Wizard Menu.
Before selecting the Auto Run option, the user must first enter the EMU Conversion Set-up Utility
menu and run the utilities there. These include selecting the target currency which the data will be
converted to, and stating the levels of tolerance that are acceptable for the various types of rounding
differences that will occur during conversion. For a detailed guide to the steps that must be completed
here, refer to the EMU Conversion Set-up Utility section below.
The user can interrupt the conversion by pressing the S key. In such cases, changes to the file currently
under conversion are rolled back. The user can then resume conversion from that stage onwards in
either automatic or manual mode. All utilities that are successfully executed will appear grey and will
be disabled for further selection.
After completing the EMU Conversion Set-up Utility, return to the EMU Conversion Wizard Menu
and select Auto Run. The subsequent screen gives the conversion steps performed by the EMU
Conversion Wizard. Each menu item is invoked and conversion performed. The step being executed is
highlighted while those that have been performed or are yet to be executed are greyed out.
During conversion, if the rounding difference exceeds the rounding tolerances, the message Tolerance
Overshoot appears. If other errors occur, an error message will be displayed. The program will
continue to the end of the file being converted to identify any other overshoots or errors. These errors
are registered in the wizard log file. The program then automatically rolls back to the beginning of the
current utility. The program can be restarted in either auto or manual mode after the tolerance level has
been changed or the error corrected.
All converted amounts are stored in .dat files, while the source amounts are available in .mon files.
(tables in SQL database).
Rounding gains and losses constitute the Audit Trail Report that is available in detailed or deviated
form. A deviated report shows only errors or tolerance overshoot, while a detailed report shows the
results of successful conversion too. The appropriate report may be chosen by setting the switch to
Detailed or Deviated in the EMU Set-up. The report can be printed using the Audit Trail Report
option from the Wizard menu.
21
SYSTEM UTILITIES
The user has the option to rollback changes at the end of automatic conversion, if necessary by
selecting the Roll back option from the Wizard menu. This has the effect of cancelling everything from
the start of conversion and restoring all data in the source currency.
The progress of conversion is indicated on the screen.
After running the EMU Conversion Wizard, it is recommended that the standard utilities are run –
Rebuild Stock, Recalculate Standard Prices Stock and Recalculate Standard Price MPC to
maintain consistency with other modules.
Manual Mode
If the user opts to run the EMU Conversion Wizard in the manual mode, he must select each utility to
be run from the Wizard menu. The menu is the same as the one displayed in the automatic mode. The
user has to select the conversion utilities one after another as required. Before selecting any other
options from the menu, the user must select the EMU Conversion Set-up Utility and perform the
procedures described below. Afterwards, the utilities may be run in almost any order- certain utilities
cannot be run until others have been completed, but these will be greyed out in the menu until the
appropriate time. As in the case of automatic conversion, rounding gains and losses constitute the audit
trail that are available in the Audit Trail Report.
Select the conversion utilities (menu items), one after another.

If, at any point during conversion, the rounding difference exceeds the specified rounding tolerances or
any other error occurs, an error message is displayed on the screen. The user is required to
acknowledge this by pressing enter. The program continues to the end of the file to identify other
similar errors or overshoots. It then rolls back to the beginning of the utility. The tolerance level must
be increased or the errors corrected. That utility can then be restarted. The parameters for the EMU
Conversion Wizard need not be set up again.
At any stage during the conversion, the user can change from the manual to auto mode or vice versa. If
we change from Manual to Auto, the system will perform the remaining utilities automatically and
there is no need to select those manually.
The user can interrupt the conversion by pressing the S key. In such cases, changes to the file currently
under conversion are rolled back. The user can then resume conversion from that stage onwards in
either automatic or manual mode. All utilities that are successfully executed will appear grey and will
be disabled for further selection.
All converted amounts are stored in .dat files, while the source amounts are available in .mon files
(tables in SQL database).
Rounding gains and losses constitute the Audit Trail Report that is available in detailed or deviated
form. A detailed or deviated Audit Trail Report is generated depending on whether the switch is set to
Detailed or Deviated in the EMU Setup. The report can be printed using the Audit Trail Report
option from the Wizard menu.
The user can roll back the entire conversion by selecting the Roll back option from the menu. If he
chooses to roll back conversion entirely and start afresh, he has to reset all conversion parameters. The
user may also make a selective roll back where only the files that the user selects are rolled back. Roll
back should not be performed for the year after sign off for the year.
After running the EMU Conversion Wizard, it is recommended that the standard utilities are run –
Recreate Stock Balance, Recalculate Standard Price Stock and Recalculate Standard Price MPC
to maintain consistency with other modules.
Description of Conversion Utilities

Conversion is carried out for the year and company logged into. The user can log into the current or
any of the future years defined in the company files. The user can log into the past years, but cannot
run the EMU Conversion Wizard on the past years’ data; i.e., data in year dependent data files from
previous years.
22
SYSTEM UTILITIES
The conversion utilities that are available within the EMU Conversion Wizard are:
• EMU conversion set-up utility.
• EMU conversion of monetary fields.
• Conversion of transactions.
• Update Chart of Accounts.
• Recreate balance GL.
• Rebalance accounts.
• Convert fixed assets module.
• Convert purchase invoices/payments - this only converts the local currency equivalent of the
invoices to the target currency. The invoices themselves remain in their original currency.
• Convert sales invoices/payments - as with purchase invoices, only the local currency equivalent is
converted.
• Convert sales orders.
• Convert purchase orders.
• Convert payroll.
• Sign off conversion for a year.
• Auto Run - this allows all the utilities to be run by this system in sequence, rather than selecting
each module separately.
• Audit Trail Report.
• Rollback.
• Sign off for the company.
EMU Conversion Set-up Utility

This utility has to be run to set up the files and parameters in order to execute the EMU Conversion
Wizard. The following options are available:
Creating EMU Conversion Account Correspondence Table

The EMU Conversion Account Correspondence Table shows the Chart of Accounts before and after
conversion (the source and target charts of accounts) including all Special Function Code links. It also
shows where the transactions from the source Chart of Accounts will be posted to in the target, and in
which currencies. This is required because the settings of certain accounts, especially as regards
currency related Special Function Codes/ codes will need to be changed as a result of the change in
base currency.
When we run the utility Create EMU Conversion Account Correspondence Table, the system will
create a table showing identical source and target charts of accounts, with identical Special Function
Code links. If we wish to adjust the table- for example to add new Special Function Code links to the
23
SYSTEM UTILITIES
target Chart of Accounts, we can do this by selecting the option Adjust EMU Conversion Account
Correspondence Table from the EMU Conversion Set-up Utility.
In order to see the EMU Conversion Account Correspondence Table, we need to print it by selecting
the option Print EMU Conversion Account Correspondence Table.
Adjusting EMU Conversion Account Correspondence Table

Before converting, we need to plan what changes will take place in the Chart of Accounts as a result of
changing the base currency. In particular, bank accounts denominated in the source currency will
become “foreign currency” accounts as they are no longer denominated in the company’s base
currency. We will therefore need to add statistical accounts to the chart of account for these and add
Special Function Code (sub- ledger) links. The same will apply to receivable and payable accounts.
The Adjust EMU Conversion Account Correspondence Table enables us to add new Special
Function Code links to our target Chart of Accounts. We can also remove or change old Special
Function Code codes, for example, we might want to change Special Function Code links for the new
base currency as it is no longer a “foreign” currency. When we select the option, the following screen
will be displayed:
1. Enter the Account Code for which the target Special Function Code needs to be changed.
2. Enter the Special Function Code be linked to the translated account.
Valid target Special Function Codes are:
Source Special Function codes Valid Target Special Function codes

00 00, 03, 04, 09
01 00, 03
02 00, 04
03 00, 01, 03
04 00, 02, 04
09 00, 09
10 00, 10
The target Chart of Accounts should not have any other Special Function Codes except valid codes
at the moment of EMU conversion.
3. Enter the statistical account to be linked by the Special Function Code. If the Special Function
Code is changed to type 03, 04 or 09 of the account, a statistical transaction line with amount in
source currency code is added during transaction conversion and balancing utility.
? (statistical accounts)
Please note that any new statistical accounts required must first of all be added to the Chart of
Accounts in the General Ledger.
24
SYSTEM UTILITIES
The Chart of Accounts will be updated to reflect these changes when the Update Chart of Accounts
utility is run from the EMU Conversion Wizard. This will occur after conversion of transactions.
Entering EMU Conversion Automatic Accounting Schedule

During the conversion process, there will be rounding differences, both on the transaction level and at
account level. The EMU Conversion Wizard includes a mini automatic account schedule, which
specifies to which accounts these differences will be booked. This automatic account schedule must be
completed before conversion can be started.
There are 6 following items in the automatic accounting schedule:

1 Account Level Round off Gain.
2 Account Level Round off Loss.
3 Transaction Level Round off Gain.
4 Transaction Level Round off Loss.
5 Opening Balance Round off Gain.
6 Opening Balance Round off Loss.
To complete the schedule, enter item 1 in the first field, and in the second field enter the account
number to which account level round off profits should be posted. Repeat this process for the other five
items. Accounts for items 5 and 6 should be of balance type.
Printing EMU Conversion Account Correspondence Table

Run this routine to print the account correspondence table defined in the preceding steps. The account
correspondence table would look like this.
Company EMU Conversion of Chart of Accounts 31-12-99 16:34:20 Page 1
COMPANY 11 FIN.YEAR 99=========================================================================/Scala/GL0077/5
ACC DIMENSIONS BPZ F ACC DIMENSIONS BPZ F
==============================================================================================================
010000 B 00 Assets 1 ->010000 B 00 Assets 1
100000 B 00 Petty Cash ->100000 B 00 Petty Cash
101000 B 00 Petty Cash (USD) ->101000 B 00 Petty Cash (USD)
150000 B 00 NLG Bank Account ->150000 B 00 NLG Bank Account
* * * * * * * * * * * * E N D O F R E P O R T * * * * * * * * * * * *
Entering/Adjusting Conversion Parameters

This routine is used to set up the conversion parameters for the EMU Conversion Wizard. The
parameters must be entered before conversion can proceed. The screen is as follows:
1. Source Currency
The source currency of the company is displayed.
2. Enter the target currency into which the data is to be converted. The target currency can be Euro
or local currency. The default target currency is Euro. In case the source and target currencies are
the same, the Rate 1 field is enabled.
F4 (currencies)
25
SYSTEM UTILITIES
3. Book-Entry Date
Enter the date against which the rounding differences will be booked to balance the accounts.
For current year conversion, the date should fall within any of the book entry periods defined in
the Company file. If we have transactions already booked into future years, then we should log
into those years and run the conversion process here too. In this case, it is recommended that the
first date of the year is chosen as the Book-Entry Date as this is the closest date to the conversion
date.
(#30935)
After EMU conversion parameters are set, this field will be disabled.
To be able to convert next years, run the Roll Back routine before each next year EMU
conversion and set the BE date as required; otherwise, all rounding conversion transactions
will be booked to the first converted year.
4. Conversion Rate Date
Enter the date as on which the conversion rate will be used and applied to data during conversion.
This field is enabled only when a floating exchange rate has been selected. The value entered
cannot be greater than the current date.
5. Rate/Coefficient
Fixed exchange rate will be displayed here and cannot be changed.
6. Enter the Rounding Tolerance for Transaction. After each line is converted, the transaction may
not balance due to rounding differences. If this occurs, the system will add a balancing line to the
transaction booked to the transaction level rounding gains/loss accounts specified in the automatic
accounting schedule.
The tolerance level that we enter here is the limit for the rounding difference for each individual
transaction. If the rounding difference on any transaction exceeds this amount, the conversion
process will be continued to the end, but then rolled back. The tolerance level will have to be
raised before running the transaction conversion again. The tolerance level is specified as a
monetary amount in terms of the target currency.
7. Enter the Rounding Tolerance for Account. After we have converted all the transactions, the
balance on each account is calculated by adding up the value of the converted transactions. The old
account balance in the source company is then converted to the target currency. There may be
differences between the two.
This difference is the Account level rounding difference, and a transaction will be created to adjust
for this difference. Here we specify the tolerance level for each individual account. If the rounding
difference for any account exceeds this tolerance, the conversion will be halted. The level is
specified as monetary amount in terms of the target currency.
8. Enter the Transaction Series from A to Z, except Q and R which are reserved if any. The
transaction series is used to number the transactions that will add the rounding differences to the
transaction file during account balancing. If no series is specified, the default series will be A.
9. Audit Trail Report
Audit Trail Reports are generated during restatement of monetary fields, transactions and accounts.
Enter 0 or 1 in this field. Entering 0 will generate a detailed report, while 1 will generate a
condensed (or deviation) report. The default value for this field is 1.
0 Detailed report
1 Deviated (or condensed) report
Once the EMU Conversion Wizard is run with Deviated Report option, a detailed report
cannot be generated unless the conversion is rolled back and the EMU Conversion Wizard run
again with the Detailed Report option.
The detailed report could result in data occupying a large amount of disk space and affect the
performance of Scala.
10. Source Currency FA
This utility is designed for companies, which keep fixed asset values in a currency other than the
Scala base currency. When we convert the information in depreciation plan and tax fields only
values recorded in the currency that we select here will be converted.
If we have fixed asset values in more than one currency and we wish to convert all of these to the
target currency, we have to rerun the conversion for each different currency.
26
SYSTEM UTILITIES
By default, currency 00 is selected that means that only fixed asset values in the base currency will
be converted to the target currency.
11. Convert Plan FA / Convert Tax FA
Here we are given the choice as to whether or not we wish to convert the information stored in the
depreciation plan and depreciation tax fields of fixed assets. All monetary information in these
fields will be converted to the target currency, provided that the information is initially in the
currency specified in the source currency field described above.
The system asks to confirm that we wish to convert plan and tax. If we wish to convert, we have to
enter Yes! The fixed asset conversion takes place when we run the Convert Fixed Asset Module
utility.The Insurance Value replacement cost and revaluation depreciation fields in the fixed asset
file are converted separately during the EMU Conversion of Monetary Fields. These fields will
all be converted from base currency to the target currency. In future versions of the EMU
Conversion Wizard, it will also be possible to decide whether or not we wish to convert the
information stored in the Insured Value field and the Revaluation Fixed Assets screen, and we will
be able to select alternative currencies. In the current version of the Wizard this additional
functionality has not been implemented.
Printing Conversion Parameters
Run this routine to print the conversion parameters defined in Enter/Adjust Conversion Parameters.
TEST COMPANY EMU CONVERSION SET UP 20/01/99 10:58:20 Page 1
COMPANY 01 FIN.YEAR 98=========================================================================/Scala/GL0077/5
PARAMETERS SWITCHES
==============================================================================================================
Source Currency : 00 FIM
Target Currency : 05 EUR
Conversion Rate Date : 02/09/99

Book Entry Date : 01/10/98
Rate / Coefficient : 5,945730
Tolerance for Transaction : 0.10

Tolerance for Account : 1.00
Transaction Series : Z
Audit Trail Report : 0 Detailed
Source Currency Code FA : 00 FIM

Convert Plan FA : Yes
Convert Plan FA : Yes
* * * * * * * * * * * * E N D O F R E P O R T * * * * * * * * * * * *
Enter/Adjust Convert Payroll Setup

This utility is for selecting which of the user-defined tables in the payroll module we wish to convert.
The tables are listed, and we select those, which we want to convert.
EMU Conversion of Monetary Fields

This utility converts monetary fields in each module to the target currency specified by the user in the
EMU Conversion Set-up Utility.
27
SYSTEM UTILITIES
The utility is invoked automatically in the automatic mode for all modules and files therein; if you wish
to use the manual mode, clicking on it. For each module the individual files for conversion are selected
by clicking on them or pressing the plus (+) key with the cursor on the item. To select all modules and
files, press an asterisk (*). To undo all selections, press the minus (-) key.
The routine uses the conversion factor retrieved from the currency table as on the Conversion Rate
Date and Target Currency and restates all monetary fields for the files within each module. The
corresponding module wise .mon files retain the monetary fields and amounts in the source currency.
The progress of conversion is indicated on the screen.
The converted amounts are stored in .dat files, while the source amounts are available in .mon files./
SQL tables.
The following data is not converted by this utility:
• Statistical accounts.
• Fixed Asset values and depreciation – these are converted by the Convert Fixed Assets Module
routine.
• Transactions - these are converted by the Conversion of Transaction utility.
• Account balances - refer to the section on Rebalance Accounts.
• Tables for currency conversion for periodic consolidation - these must be converted manually.
After conversion be aware of possible rounding differences causing a difference between the converted
value of stock balances in the stock control and the converted balance on the stock account in the
General Ledger. The following is an illustration:
Balances
before Balance after
conversion Conversion factor conversion
No of units in stock 100 100
Unit price 500 1.92573 259.64
Total stock balance
per stock control 50,000 25964.00
Balance in General
Ledger 50,000 1.92573 25964.18
Difference 0 0.18
In these cases it is necessary to calculate the total of such differences by printing stock balance reports
from stock control, comparing these to the balances on the General Ledger and posting the difference
to an appropriate rounding account.
Similarly, in MPC, where we have Bill of materials set up for items incorporating many elements, the
sum of the converted elements may not equal the converted total standard cost:
Balances before Conversion Balance after

conversion factor conversion
Labour cost 100 3 33.33
28
SYSTEM UTILITIES
Materials 100 3 33.33

Overhead allocation 100 3 33.33
Calculated standard
cost 300 99.99
Standard cost in stock 3
control 300 100
It will therefore be necessary to recalculate the old cost of the completed article and then to revalue
stock to the extent that it is accounted for at standard costs.
An Audit Trail Report is generated during conversion. The detailed Audit Trail Report gives details of
each field. Please refer to the section Audit Trail Report for a sample report.
A detailed report could result in data occupying a large amount of disk space and affect the
The user has the option to select Roll back from the menu, roll back all changes and restore all files to
the before conversion state. A fresh conversion process can be initiated if required.
(#31257)Simulation transactions should be re-entered manually after conversion.
Conversion of Transactions
This utility converts General Ledger transactions in the base currency to the target currency specified in
the conversion parameters. In cases where the converted transactions do not balance due to rounding
differences, the system will add a balancing line to the transaction, which is booked to the rounding
accounts specified in the Automatic Accounting Schedule.
The conversion is invoked automatically in the automatic mode for all modules and files therein. In the
manual mode the utility is invoked by clicking on it.
The system retrieves each transaction from the General Ledger transaction file and restates the
transaction amounts on B (Balance) & P (Profit & Loss) accounts by applying the conversion factor
taken from the currency table as of the conversion date rate. Each amount is converted by applying the
standard rounding rules. Where the transaction no longer balances in the target currency, a rounding
transaction line is added. This amount is compared with the transaction tolerance and if it exceeds that
tolerance, the appropriate warning appears.
If the rounding difference is within the tolerance margins, the rounding differences are booked to debit
and credit accounts as a new transaction line. The transaction gain and loss accounts are specified in
the EMU Conversion Automatic Account Schedule in the EMU setup. For transactions where the
rounding differences exceed tolerance margin, the user is warned of the error condition and the
transactions are logged in the wizard log file. The progress of conversion is indicated on the screen.
For bank accounts, accounts receivable and payable account in the original base currency. There may
be new special function codes and statistical accounts setup in the EMU Conversion Account
Correspondence Table above to account for the fact that the base currency becomes a foreign
currency after conversion. The conversion process for these accounts is as follows:
1. Each transaction line is written to the new statistical account setup.
2. The transaction is also converted and posted to the original nominal account in the new base
currency.
For example, a company is accounting in DEM. It decides to convert its database to Euro. The
company has a balance sheet account 1000 in its Chart of Accounts, which represents bank balances in
DEM. Before conversion there is no statistical account linked to this as DEM is the base currency of
the company accounting.
After conversion, when the company’s base currency becomes Euro, DEM will be a “foreign”
currency. It will be necessary re-create a new statistical account, 910000, called statistical account
Bank DEM. During setting up the EMU Conversion Account Correspondence Table we will add the
special function code 9 to the account 10000, and link the account to a statistical account.
29
SYSTEM UTILITIES
When we run conversion, all transactions in account 10000, which were in DEM, will be posted
directly to the new statistical account 910000, in DEM. At the same time, they will also be converted to
Euro and written back to the account 10000.
The converted amounts are stored in .dat files, while the source amounts are available in .mon files/
SQL Tables.
Amounts in statistical accounts are not converted and the amounts are retained as they are.
Transaction types that are considered for conversion and balancing are given below:
0 Transaction in General Ledger (Directly entered)
1 Reversal Transaction in GL
2 Accrued Transaction (Periodic Allocation) in GL
3 Customer Invoice (Transaction from SL)
4 Customer Payment (Transaction from SL)
5 Supplier Invoice (Transaction from PL)
6 Supplier Payment (Transaction from PL)
7 Depreciation Transaction (Fixed Assets in GL)
8 Automatic Accrual Allocation (Periodic AA:51-99)
9 Transaction from Project Management
A Transaction from Payroll
B Transaction from Stock Journal
C Transaction from Promissory Notes
I Closing period Transaction
K Fixed Assets Revaluation
L Cash Book Transaction
/ Opening Balances
S Transaction from source company (consolidation)
For the following transaction types, the transactions are created from the converted transactions. No
further transaction balancing is performed:
\ Reporting Level Transaction Opening balances
a Reporting Level Transaction (Cost Centre, Product or Project are of Reporting
Level)
c Reporting Level Transaction Budget 1
d Reporting Level Transaction Budget 2
e Reporting Level Transaction Budget 3
f Reporting Level Transaction Budget 4
g Reporting Level Transaction Budget 5
h Reporting Level Transaction Budget Previous Year
j Reporting Level Closing period Transaction
The following transaction types are converted from source transactions, but no balancing of
transactions is performed:
U Transaction Budget 1
V Transaction Budget 2
W Transaction Budget 3
X Transaction Budget 4
Y Transaction Budget 5
Z Transaction Previous Year Comparatives
If an account, which no longer exists in the Chart of Accounts, was posted to for a transaction, on
conversion, the transaction will be posted to the error account 999999. The audit trail report will show
the transaction number with a ##. At this stage it is necessary to perform the following steps:
1. Roll back the Conversion of transactions.
2. Go to the General Ledger - Standard Reports menu and print the transactions affected.
3. From the transaction list, it will be possible to ascertain the account numbers that are missing.
30
SYSTEM UTILITIES
4. Enter the missing accounts back into the Chart of Accounts.

5. Re-run the Conversion of transactions.
If these steps are not performed, there will be a tolerance overshoot when the rebalance accounts
function is run (see below), because the balance in account 999999 after conversion will be compared
to the zero balance from before conversion, and the amount will exceed the tolerance level (unless very
large tolerance levels have been selected.)
During the conversion, sub-account (dimensional) information attached to the transactions is not
changed. For example, if we have a transaction posted to a cost centre, the conversion program will not
change this information, even if that cost centre is not defined in the dimension file.
Where automatic allocations have been set up in the source company, no automatic allocation
transactions are created as a result of the currency conversion; any such transactions will already have
been created in the source currency and will therefore also be converted. The transaction “flag” for the
initial entry transactions, which records whether or not the allocation of those entries will be performed
will appear in the converted transactions.
An Audit Trail Report is generated during conversion. The deviated Audit Trail Report contains the
transaction values exceeding the tolerance margin. The detailed Audit Trail Report gives details of each
transaction line. Sample. Reports are provided in the section Audit Trail Report below.
A detailed report could result in data occupying a large amount of disk space and affect the
The user has the option to select Roll back from the menu, roll back all changes and restore all files to
the before conversion state. A fresh conversion process can be initiated if required.
Update Chart of Accounts

This utility updates the Chart of Accounts with the new account correspondence table after successful
conversion and balancing of transactions.
The Chart of Accounts is updated with the new Special Function Code, target currency code and target
statistical account defined in the account correspondence table set up by the user in the EMU
Conversion Set-up Utility.
The reason for this utility is that during transaction conversion, the program must use the original Chart
of Accounts setup.
This is a standard Scala feature. The utility creates account balances in the General Ledger by summing
up all converted transactions in the following way:
Source Account Target Account
1. Transacti
1. Transacti ons Euro
Transaction conversion
ons DEM
Recreate Balance GL
1. Account
balance
Euro
1. = sum of
transactio
Recreate Balance GL
This system utility recalculates account balances in the target currency.
31
SYSTEM UTILITIES
Rebalance Accounts
This utility takes the General Ledger account balances from the source currency and converts those
balances to the target currency:
32
SYSTEM UTILITIES
Source Account Target Account
1. Transacti 1. Transacti
ons DEM ons Euro
Conversion of transactions
1. Account 1. Account 1. Account

balance balance balance
DEM Euro Euro
Compare
1. = Sum of 1. = 1. = sum of
balances
transactio Account transactio
Re-balance
Accounts
Transaction in
Euro
The account balances calculated in this way are compared to the balances calculated in the Recreate
Balance GL utility described above. The difference is the account rounding difference.
The rounding difference is compared to the tolerance level set up in the EMU Conversion parameters
to identify any overshoots. If it exceeds this, the utility will continue to the end in order to create a
complete report of all other tolerance overshoots but then will roll back to the beginning. The tolerance
overshoot will appear on the reports, and it will be necessary to increase the Rounding Tolerance for
Account in the EMU conversion parameters or otherwise adjust the cause of the problem, before
rerunning the utility.
If there is no overshoot, rounding differences are posted to the transaction level round off gain/loss
accounts specified in the Automatic Accounting Schedule in the EMU Conversion Set-up Utilities.
The rounding transactions are posted to the daybook journal, which can be reviewed before update. The
items in the journal cannot be amended, and the General Ledger must be updated before further activity
can occur.
(#31490)
To enable printing of rounding transactions, set the General Ledger Automatic Ledger
Backup parameter to “no”.
1. Print Report?
y The report is printed.
n The report is not printed. The user can save the report to the file on disk.
2. Reprint Required?
y The report is reprinted.
n The report is not reprinted.
3. Update General Ledger?
y The General Ledger is updated with the data.
n The General Ledger is not updated. The converted data remains in the
journal file.
As a consequence, the subsequent utilities cannot be selected for execution.
The General Ledger must be updated before the Wizard continues.
4. The daybook journal will now be cleared?
y The journal is cleared and update is confirmed.
n The journal is not cleared.
33
SYSTEM UTILITIES
As a consequence, the General Ledger is not updated. The General Ledger must be updated before
the Wizard can continue further.
The converted amounts are stored in .dat files, while the source amounts are available in .mon files.
(SQL tables).
An Audit Trail Report is generated during conversion. The deviated Audit Trail Report contains the
account totals exceeding the tolerance margin. The detailed Audit Trail Report gives details of each
transaction line. Sample reports are given in the section below, Audit Trail Report.
A detailed report data may occupy a large amount of disk space and slow down the performance
of Scala.
The user can opt to select Rollback from the menu, roll back all changes and restore all files to the
state before conversion. A fresh conversion process can be initiated, if required.
Convert Fixed Assets Module

The EMU Conversion Wizard automatically converts Cost, Replacement Value, Insured Value &
Replacement Depreciation when the EMU Conversion of Monetary Fields is run. The user has the
option whether to convert the fields in the plan & tax depreciation screens. If the user wishes to convert
these fields, he must select the Convert Fixed Assets Module utility.
The system supports several sets of plan & tax depreciation calculations by currency. The user needs to
select which currency depreciation sets to convert.
This utility also supports conversion of currency depreciation data when the database itself is not
changed, e.g., memo DEM depreciation in books maintained in Russia in RUR. The converted fields
are:
• Purchase Cost
• Depreciation amount (year)
• Depreciation basis
• Accumulated Depreciation
• Depreciation during the year
• Scrap Value
• Extra Depreciation
• Sales value
Selection of source and target currencies for the conversion is made in the EMU Conversion Set-up
Utilities, in the Parameters menu. Only depreciation sets in the source currency specified here will be
converted. If we have depreciation sets in more than one currency, we must rerun this utility, selecting
the new source currency each time.
Convert Purchase Invoices

Invoices in the company’s base currency prior to conversion will become foreign currency invoices
once that base currency changes. Scala always records the currency amount of an invoice and the local
currency equivalent at the date the invoice was booked (or at the latest revaluation date). For invoices
in base currency, these amounts are identical.
On conversion of purchase invoices the recorded currency amounts will not change. Thus, the invoice
is still recorded in its original currency, irrespective of what that currency is. However, the local
currency equivalent will change from the original base currency to the target currency for all invoices.
The same conversion applies to payments of invoices. The utility also converts supplier data; thus,
monetary data in local currency will be converted. The default currency for the supplier will not
change.
Convert Sales Invoices

This utility works in the same way for sales invoices, payments and customer data as the Convert
Purchase Invoices utility described above.
34
SYSTEM UTILITIES
Convert Sales Orders

Sales orders are also held in two currencies, the order currency and the base currency. This utility
converts only the base currency amount. There is separate functionality in the Sales Order module that
allows to change the order currency.
Convert Purchase Orders

This utility performs the same function on Purchase Orders as the Convert Sales Orders utility
performs on Sales Orders.
Sign off Conversion for a Year

Use the Sign Off Conversion for a Year utility to prevent further revision of data files.
Run this menu option to sign off conversion for the login year. This utility is run after all other utilities
are executed.
In the automatic mode, the user is prompted whether this utility should be run or not. The utility is
executed if confirmed by the user. In the manual mode, the user has to select this utility by clicking on
it.
After sign off of conversion for a year, it is no longer possible to roll back any files, i.e., year
dependent or year independent files of the current year.
If any transactions are already entered for a future year, you will have to log into that year and run the
conversion to convert these transactions. After conversion, it will be possible to roll back only year
dependent files prior to sign off of that year. We can never roll back the conversion of year-
independent files, except in the current year, prior to sign off of that year.
Year Sign Off Data Files Rollback

Current Year Future Year
Selected (ON) Year dependent files Not possible Possible
Year independent files Possible –
Selected (OFF) Year dependent files Possible Possible
Year independent files Possible –
As a minimum, we must sign off for the current year before we start to enter any further activity. Such
activity must be in the new currency.
Auto Run
Select this menu item to run the EMU Conversion Wizard in the automatic mode after setting the
environment using EMU Conversion Set-up Utility.
Audit Trail Report

Run this routine to view/print and delete the Audit Trail Reports. Audit Trail Reports are generated for
conversion of monetary fields, transactions and account balancing. Two types of Audit Trail Reports
are created – detailed and deviated depending on the switch set in the Conversion Parameters in the
EMU Conversion Set-up Utility. This menu item should be always selected manually.
35
SYSTEM UTILITIES
The Audit Trail Report will contain header information. The header will show the company name, the
year for which the conversion is carried out, source and target currencies, exchange rate (sell/buy rate)
as applicable on the conversion rate date, and the conversion’s book-entry date. The report will also
contain the details about the records converted, including those that exceed tolerance levels. Records
exceeding tolerance levels are marked with an asterisk (*).
Printing Monetary Restatement Report

Select this option to view/print the detail or deviation reports of monetary fields. Select the modules for
which to view/print the report(s) or press the plus (+) key with the cursor on the item. Press an asterisk
(*) to select all modules. To undo all selections, press the minus (-) key.
For the module(s), select the files for which to view the reports. Press an asterisk (*) to select all files
within a module or press the plus (+) key with the cursor on the item. To undo all selections, press the
minus (-) key.
The detailed report will contain details of all fields restated. The deviation report will contain details of
only those fields that have exceeded the tolerance margin. All records exceeding the tolerance levels
are marked with an asterisk (*). The following is a sample detailed Monetary Restatement Report:
Test Euro * * CONVERSION AUDIT TRAIL * * 06/04/00 13:35:13 Page 1
CONVERSION DATE 04/04/00 FIM TO EUR BOOK ENTRY DATE 01/01/01
CONVERSION RATE 5,94573 TOLERANCE LIMIT 0,10 EUR
COMPANY TE FIN.YEAR 00=============================================================================/Scala/SY0505/5
FILE---- FLD NAME------------------------------------ -------SOURCE AMOUNT ----CONVERTED AMOUNT --ROUNDING
==================================================================================================================
PR32TE00 7 AMOUNTLCU 0,00 0,00 0,00
SC01TE00 4 PRICELOCCURR 7.100,00 1.194,12 0,01
SC01TE00 5 NEWPRICELCU 0,00 0,00 0,00
SC01TE00 52 AVERCOSTPRI1 4.358,84 733,10 0,01
SC01TE00 53 STDCOSTPRIC1 0,00 0,00 0,00
SC01TE00 77 PROFITLCUPER 453.000,00 76.189,13 0,00
SC01TE00 78 PROFITLCUYTD 453.000,00 76.189,13 0,00
SC01TE00 79 PROYTDPREVYR 0,00 0,00 0,00
SC01TE00 80 PROFYTDPRYR1 0,00 0,00 0,00
SC01TE00 81 SALESLCUPER 453.000,00 76.189,13 0,00
SC01TE00 82 SALESLCUYTD 453.000,00 76.189,13 0,00
SC01TE00 83 SALYTDPREVYR 0,00 0,00 0,00
SC01TE00 84 SALEYTDPRYR1 0,00 0,00 0,00
SC01TE00 106 LANDEDCOST 6.039,48 1.015,78 0,01-
SC01TE00 108 PRFLCUNXTPER 0,00 0,00 0,00
SC01TE00 109 PRFLCUNETYTD 0,00 0,00 0,00
36
SYSTEM UTILITIES
SC01TE00 110 SALLCUNXTPER 0,00 0,00 0,00
SC01TE00 111 SALLCUNXTYTD 0,00 0,00 0,00
SC01TE00 146 STANDREPCOST 0,00 0,00 0,00
SC03TE00 14 LOWESPURCHPR 2.240,00 376,75 0,01-
SC03TE00 29 FIFOVALUE1 8.587,48 1.444,31 0,00
SC03TE00 57 AVGCOSTPRICE 8.587,48 1.444,31 0,00
SC03TE00 58 STDCOSTPRICE 0,00 0,00 0,00
SC03TE00 59 LANDEDCOST 8.759,48 1.473,24 0,00
SC03TE00 63 UNALLOCCOSTS 0,00 0,00 0,00
SC03TE00 76 ABC_COST1 0,00 0,00 0,00
SC03TE00 78 DIRECTCOST 0,00 0,00 0,00
SC03TE00 79 PREVSTDCOST 0,00 0,00 0,00
SC03TE00 80 NXTYRSTDCOST 0,00 0,00 0,00
SC03TE00 81 SIMUSTDCOST 0,00 0,00 0,00
SC07TE00 5 TRANSFPRICE1 100.993,33 16.985,86 0,00
SC07TE00 10 SELLINGPRICE 613,94 103,26 0,00
SC33TE00 23 BATCHCOSTUNIT 12.079,45 2.031,61 0,01
SC33TE00 34 BATCOSTUNIT2 12.324,25 2.072,78 0,01
SC34TE00 4 COSTLCU 11.834,65 1.990,44 0,00
SC37TE00 4 PRICELOCCURR 0,00 0,00 0,00
SC38TE00 4 PRICELOCCURR 0,00 0,00 0,00
SC42TE00 9 LATSTOCKTAK 0,00 0,00 0,00
SC42TE00 10 SELLINGPRICE 0,00 0,00 0,00
------------------------------------------------------------------------------------------------------------------
Note : ** indicates overshoot of tolerance limit.
* * * * * * * * * * * * E N D O F R E P O R T * * * * * * * * * * * *
Printing Transaction Restatement Report

Select this option to view/print the detail or deviation reports of transaction restatement. The detailed
report will contain details of all converted transactions, transaction text and account string. All records
exceeding the tolerance levels are marked with *. The following is a sample detail Transaction
Restatement Report:
The deviation report will contain details of only those transactions that exceeded the transaction
tolerance.
TRANNO BE DATE-- ROUNDING\ACCOUNT DIMENSION--------------------
==================================================================================================================
400003 030400 0,01
400006 040400 0,01-
555001 030400 0,01
------------------------------------------------------------------------------------------------------------------
Note : ## indicates accounts not maintained.
* * * * * * * * * * * * E N D O F R E P O R T * * * * * * * * * * * *
Printing Account Balance Report

Select this option to view/print the detail or deviation reports of account balances. The detailed report
will contain details of all converted account balances, amount before and after restatement, transaction
text and account string. All records exceeding the tolerance levels are marked with an asterisk (*). The
deviation report will contain details of only those records that exceeded the account tolerance.
The following is a sample of detail Accounting Balance Report:
ACCOUNT DIMENSION STRING------------- ------OLD MON AMOUNT ----------DAT AMOUNT CONVERTED MON AMOUNT --ROUNDING
==================================================================================================================
01800 540.246,68 90.862,96 90.862,97 0,01-
01900 14.036,20- 2.360,73- 2.360,72- 0,01-
02200 107.549,21- 18.088,47- 18.088,48- 0,01
37
SYSTEM UTILITIES
02222 345,03- 57,95- 58,03- 0,08
03022 0,18 0,05- 0,03 0,08-
04050 12.159,15 2.045,01 2.045,02 0,01-
06000 10 17.000,00 2.859,20 2.859,19 0,01
------------------------------------------------------------------------------------------------------------------
* * * * * * * * * * * * E N D O F R E P O R T * * * * * * * * * * * *
Deleting Log Files

Select this item to delete the log file and disable any Audit Trail Reports.
Remember to archive this data for possible use at a later time; e.g., for auditors review.
Roll Back
This utility is used to roll back any changes made during conversion. The user can roll back the entire
conversion and start afresh, in which case he has to reset all conversion parameters. The user may also
make a selective rollback where only the files that the user selects are rolled back.
The utility cannot be used for a particular year after sign off for a year. Before sign off, it is possible to
roll back changes to both year dependent and year independent files if we are logged into the current
year. If we are logged into a future year, after converting the database of the current year, we can only
roll back year dependent files of that year.
Sign off for Company

This utility is the final step of the conversion process. It makes the target currency the base currency
(currency 00) in the currency table. The source currency takes the position vacated by the target
currency; thus, if the target currency was 03 prior to conversion, the old source currency will become
03.
Regarding currency history the following rules apply:
• For currency types 1, 2 or 3, when the database is changed to Euro, the historical exchange rates
will still be applied correctly after the conversion. There will be no change to the historical rates as
part of the conversion since these rates were already shown against Euro.
• For currency type 0, when the database change is to Euro, the historical exchange rates will be
recalculated by the conversion factor used during conversion of the database. Thus, we will have a
converted currency history.
• For currency type 0, where the database is being changed by a factor (for example, after the
introduction of the new rouble in Russia, where the old rouble was divided by 1,000 to get the new
rouble), the historical exchange rates will be re calculated by that factor. This will also happen to
rates against Euro, even if the Euro is set up as a type 3 currency, and the base currency is type 0
or 1. This modification is not available in early releases of the EMU Converter Wizard, but will
be added as a service pack.
Pre conversion checklist

Planning Considerations
• Has a timetable been prepared for the conversion project?
• Do you have any contingency or emergency plan to protect the business during the conversion?
• Have you identified which parts of the business are likely to be affected?
• Have you considered interfaces with other systems - such as EPOS systems? Will these be
converted at the same time?
• Have resources been identified and allocated – both internal resources and external consultants?
What will be the reporting structure of the teams, and who will be the project leader?
38
SYSTEM UTILITIES
• Which approach to conversion will be used? A once only ‘Big Bang’ approach, or a more phased
approach?
• The retention of data is governed by local legislation; given that all the accounting records are to
be restated to Euro, what are the policies for retaining some or all of your historical data for
comparison purpose? Normal practice as regards retention of old records will be to keep them
unconverted, i.e. in the currency in which the activity was recorded. This is even specifically laid
down in the Dutch requirements. The conversion of past data is required to support comparison and
drill down in the later periods, when the Euro is the base currency.
• What results are expected from the system after conversion, and what tests should be applied as
evidence that the conversion was sound? Who should define these? Who should check these?
• What permanent records should be retained, 1) as evidence of the conversion, 2) for subsequent
review by internal audit, the external auditors, etc?
• What are the authority levels of those persons responsible for approving the conversion and what
level of tolerances will your external auditors accept?
• What approach is being taken to converting the fixed assets register to the Euro?
• Are all persons involved in the project, or who will be affected by it aware of their part?
• Has a timetable been established for closing the accounting records prior to conversion?
Pre conversion action list

• Have all subsidiary records been reconciled with their control accounts etc. prior to the database
conversion?
• Have data files been purged of old data that is no longer needed?
Open Sales Order file should be purged of all old orders, which are not likely to be fulfilled.
Historical Sales Order to be reviewed and purged of redundant records.
Open Purchase Order file should be purged of all old orders, which are not likely to be fulfilled.
Completed Purchase Order records to be reviewed and purged of redundant records.
Obsolete Stock Items to be identified and purged if required.
Purge the Customer file of old and redundant customers.
Purge the Sales Ledger of irrecoverable rounding and balancing differences no longer collectable.
Redouble the efforts on customer statement reconciliation.
Purge the Supplier file for old and redundant suppliers.
Purge the Purchase Ledger of irrecoverable rounding and balancing differences.
Double the efforts on supplier statement reconciliation.
Reconciliation of all bank accounts to bank statements.
Review of employee advances including reimbursement where necessary.
• Print Trial Balance and other key financial reports after making all adjustments and file.
• User to create unique account numbers for rounding arising from the conversion. It may be
necessary to cumulate individual totals for debits and credits.
• Chart of accounts to be reviewed and new statistical accounts and Special Function Code links
designed to account for the change of base currency.
• System Manager/User to ensure all journals are posted prior to starting the conversion.
• System Manager to rebuild all data files immediately prior to running the conversion programs.
• General ledger balances should be compared to the underlying transactions. Where there are
differences, these should be investigated before running the “Recreate Balance” routine in system
39
SYSTEM UTILITIES
utilities to find out whether the difference relates to errors in the transactions themselves, or to the
balances.
• System Manager to run ‘Recreate Balances’ in system utilities prior to running the conversion
programs:
Recreate GL references
Validate General Ledger Balances
Check Sales Ledger
Check Purchase Ledger
Check Stock item file
• System manger to make backup of system prior to conversion process.
• Reconcile all control accounts with underlying detail including:
Accounts receivable
Accounts payable
Fixed Assets
Inventories
Work in progress
Post conversion action list

• Run the following utilities from the system utilities:
Recreate stock balance
Recalculate standard Prices Stock
Recalculate Standard Price MPC
Deleting Old Data after EMU Conversion (SP01)

Search Path:
Create/Check Files – Delete Before EMU records
Use this routine to delete .mon files created while EMU conversion procedure. For information on
EMU conversion procedure, see the respective section.
Warning!
After deletion files cannot be recovered.
The .mon files are located in \dat\xx directory, where xx is the module abbreviation. Once .mon
files are deleted, roll back is not possible.
• The financial year for which the records will be deleted is displayed.
• Year Dependent Files Only?
y to delete only year-dependent files
n to delete both year-dependent and year-independent files
• The modules and files to select for deletion are displayed:
↑
↓
To move between modules.
+
space To select/deselect modules.
* To select all modules.
– To cancel all previous selections.
Esc To return to the previous screen.
40
SYSTEM UTILITIES
Enter To continue.
After you have selected a module, depending on the Year Dependent Files Only? switch settings,
all module’s .mon files or only year-dependent .mon files are displayed in a menu. Use the same
method as for modules to choose the files to delete.
• Confirm deletion.
Information on EMU Conversion in Company File (SP01)

Search path:
Access Rights/Menus – Company Files
Alongside each financial year the information on EMU conversion for this year have or have not been
done (“Yes” or “No” respectively) is displayed. “Yes” is displayed if the Sign Off Conversion for a
Year utility from the EMU Conversion Wizard has been executed (System Utilities/Office Automation –
Create/Check Files – EMU Conversion Wizard). If, in addition, the Sign Off Conversion for Company
utility has been executed, the message about EMU conversion have been done is displayed below
company defined financial years. For more information on EMU Conversion Wizard, see the respective
section.
Basis for VAT calculation (SP03)

Search path:
Access Rights/Menus – Company Files
• Basis for VAT calculation
y VAT calculation will be based on line amount
n VAT calculation will be based on item price.
The appropriate rounding rules, specified in Miscellaneous – Currency File – Rounding
Parameters, will be applied in both cases but the rounding succession will be different. The
rounding succession applied may produce different calculation results.
Note on ScaComp and ScaUser (#29332)

Before using ScaComp and ScaUser, all data files must have been created.
Creating Companies with Own Menus (#31828)

Search path:
Scala Menu Bar – Tools – ScaComp
• Own Menus
y Company own (customised) menu will be used.
For new companies or for Company 01when new installations, to work
properly with menu type 2, before first logging on to the company, do
the following:
• in ScaUser, for the system manager SYS of the new created
company (Company XX), set menu type 1:
in the Menu Type field, enter 1
• log on to Company XX as SYS and create all data files required
• import the standard menu
• log off Scala
• in ScaUser, for the Company XX’s system manager SYS,
set menu type 2: in the Menu Type field, enter 2
41
SYSTEM UTILITIES
• customise the menu to match the company’s own working practice

n Company 01 menu will be used.
User File Security (SP09) (#28461)

ScaUser
Search path:
Scala Menu Bar – Tools – ScaUser
When starting the ScaUser utility, enter the logon information:
• Company
? (companies)
• User
? (users)
• Password
After logging on, select the user file option you are allowed to run depending on your logon access
rights as described below:
Options Enter/Change Delete Rebuild Create Select
Users Users User File New User File Company
Company/
User Access rights:
01/SYS is entitled is entitled to is entitled to is entitled to is entitled to
enter/change delete all rebuild all create all select another
data of all users of all companies’ companies’ company and
users and all companies; user files new user files continue
companies; no no passwords working with
passwords are are required user files
required
XX/SYS is entitled to is entitled to is entitled to is entitled to N/A
enter/change delete all rebuild the create the
data of all users of company XX’s company XX’s
users of company XX; user file new user file
company XX; no passwords
no passwords are required
are required
XX/YY is entitled to is entitled to N/A N/A N/A
enter/change delete the
data of the logged user
logged user (User YY)
(User YY) and other
and of other users of
users of company XX
company XX if their
if their passwords
passwords are are known
known
Company XX/User YY is unable to modify the Hours Period, Year, Previous year, Logged in
(Y/N), Entry Block (Y/N), Menu Type and Menu Number fields as well as to increase his/her own
access level and other users’ level above his/her own to any Scala module.
42
SYSTEM UTILITIES
If the User File for Scala company XX (SY13XX00.dat) is corrupted, the Rebuild User File option
creates a new file with one record for company XX’s system manager SYS and password scala.
Special Prefix to Be Used for Scala Commands

(SP12)(#23806)
Search path:
Scala Menu Bar – Tools – ScaUser
or
Access Rights/Menu – Users & Users Groups – Enter/Change User
• Command Prefix
Specify the one-character command prefix that will allow to distinguish the same Scala letter
commands (for example: n, p, v, co, da, t2, tx, job, and so on) and Scala item codes (such as stock
items, customers, suppliers, and so on) if you plan to define such item codes in your Scala system.
With the command prefix specified, use it as a prefix in any Scala command in the following
modules:
Stock Control
Sales Order
Purchase Order
Project Management
MPC
Promissory Notes
Prefix @ is recommended.
Warning!
Do not use for command prefix the following characters used in other Scala commands:
! (exclamation point)
% (percent)
= (equal sign)
> (greater than)
? (question mark)
_ (underscore)
* (asterisk)
~ (tilde)
# (number sign)
& (ampersand)
Example.
If the character @ is specified as the command prefix, in sales/purchase order lines entering
routines, stock item code field:
for the copy order command – type @CO or select the respective command from the command list;
for the stock item CO – type CO or select the respective stock item from query
If no command prefix is specified, the conflicting values, entered in Scala data fields, will be
treated as Scala commands.
Password Troubleshooting (#29933)

Warning!
The password of the system manager SYS of the company 01 cannot be restored if forgotten.
If a user has forgotten his/her password, he/she should do the following:
• for ordinary users, contact the system manager SYS of his/her company or the system manager
SYS of Company 01
43
SYSTEM UTILITIES
• for system managers SYS of a company other than 01, contact the system manager SYS of
Company 01
User File
Search path:
System Utilities – Access Rights/Menus – Users & User Groups
This routine is similar to the ScaUser utility described above with the following differences:
• The Rebuild User File, Create New User File, and Select Company options are unavailable.
• The current user cannot delete himself/herself.
Scala Backup/Restore Procedure (SP11)

Search Path:
Document/Installation – Backup Local Hard Disk
Scala SQL
For Scala SQL backup/restore procedures, the internal MS SQL bcp bulk copy utility is used.
bcp is accommodated to insert large numbers of new rows into MS SQL tables and allows keep files in
desirable format in MS Windows file system. Security is achieved by operational system permission
settings on the backup directory (disk:\Scala\Backup by default). After backup, for each table
[table_name], two flat files are produced:
• [table_name].fmt with format specification
• [table_name].dsa with data.
The .fmt file is a tab-delimited text file with a specific structure as follows:
Field Description
Version Version number of bcp.
Number of fields Number of fields in the data file.
This number must be the same for all rows.
Host file field order Position of each field within the data file. The first field in the row is 1, and
so on.
Host file data type Data type stored in the particular field of the data file. With ASCII data files,
use SQLCHAR
44
SYSTEM UTILITIES
use SQLCHAR.
Prefix length Number of length prefix characters for the field. Legal prefix lengths are 0, 1,
2, and 4. To avoid specifying the length prefix, set it to 0. A length prefix
must be specified if the field contains null data values.
Host file data length Maximum length, in bytes, of the data type stored in the particular field of the
data file.
Terminator Delimiter to separate the fields in a data file. Common terminators are
comma (,), tab (\t), and end of line (\r\n).
Server column order Order that columns appear in the SQL Server table. For example, if the fourth
field in the data file maps to the sixth column in a SQL Server table, then for
the fourth field the server column order is 6.
To omit a column in the table from receiving any data in the data file, set the
server column order value to 0.
Server column name Name of the column taken from the SQL Server table. It is not necessary to
use the actual name of the field. The only condition is that the field in the
format file not be blank.
Scala always produce backup in the format described above. As result file with data is tab-delimited
text file which can be read by any tool (MS Word, MS Excel, MS Access, any browser, and so on); any
person with granted access can change or analyse this file.
Moreover, with the file format correctly described in the .fmt file, Scala users can restore data from
different accounting systems and tools.
Currency System (SP01)

The currency system is common for all Scala modules. You can work with up to 30 different currencies
within each Scala company and choose whether to use the Company 01’s currency or the own
company’s currency (Own Currency File field in the company file).
Scala as a multi-currency transaction-based system meets all requirements of the European Council
regarding Euro introduction within the European Monetary Union (EMU) countries. For more
information on Euro and EMU, see the Scala EMU User’s Guide.
Currency Types
The Scala currency system comprises 4 currency types, which are the following:
Currency Type 0
Currency type 0 is for currencies whose exchange rates:
• Have the floating rates quoted against the accounting currency.
• Do not require any triangulation.
According to EMU legislation, triangulation (i.e., conversion of one currency to another by
first converting one currency to the Euro and then using the resulting figure as a basis for
converting to the target currency) is required when converting between two EMU-
participating currencies. For more information, see the Scala EMU User’s Guide.
Example: USDDEM, where DEM is the accounting currency.
Currency Type 1
Currency type 1 is for currencies whose exchange rates:
• Have the floating rates quoted against the Euro (not against the accounting currency as for
currency type 0).
45
SYSTEM UTILITIES
This currency type is similar to type 0, except that conversions to the accounting currency are
‘triangulated’ via the Euro.
Where the accounting currency is the Euro itself, currency type 1 amounts will be converted
directly to the accounting currency.
Example: USDEURDEM, where DEM is the accounting currency.
It is up to the user’s discretion to decide whether a currency should be treated as type 0 or type 1. In
situations where the practice or regulations are require to quote rates against the Euro, the non-
participating currencies should be treated as type 1, with the currency-to-Euro rates entered in the
currency table. See the Currency Definition section in this chapter for details.
Currency Type 2
Currency type 2 is for currencies whose exchange rates are:
• Fixed against the Euro, i.e. the currencies of the eleven EMU-participating states.
Currency of type 2 supports triangulation of the EMU-currencies using fixed exchange rates, i.e.,
conversion to the accounting currency will be by triangulation via the Euro.
Where the accounting currency is the Euro itself, currency type 2 amounts will be converted
directly to the accounting currency.
Conversions between EMU-currencies must be triangulated via the Euro, using the fixed
exchange rates; cross or inverse rates must not be used.
Conversion between the EMU and floating currencies must be performed using the fixed
“EMU-currency – Euro” rate and “Euro –floating currency” rate.
Example: FRFEURDEM, where DEM is the accounting currency.
Setting up a currency as type 2 will also block access to the exchange rate entering (see the Entering
Currency Rates section), preventing inadvertent changes or tampering. Setting procedures for these
fixed rates are entered in a separate routine supporting a heightened level of security. See the EMU
Coefficients section in this chapter.
Currency Type 3
Currency type 3 is:
• Dedicated solely to the Euro.
• Acts as a marker for the system to recognise the currency through which triangulation is done.
The Euro must be set up only as currency type 3 and you can define only one currency of type 3 in
your currency system.
Whether the rate of the Euro to the accounting currency is a fixed or a floating rate will depend on the
currency type of the accounting currency. Where the Euro, marked as type 3, is the accounting
currency, amounts in currencies of types 1 and 2 will be converted directly to the Euro.
Warning!
Assigning each currency with the proper currency type is crucial for proper performance.
Activating Currency System

To activate the Scala currency system and proceed with the Scala currency operations, complete the
following:
1. For new Scala installation, create all currency system files. See the File Operations – Create New
Data Files section in this chapter for creating data files details.
2. If your currency system comprises the currencies of types 1-3, enter these currencies’ EMU
coefficients, i.e. exchange rates against the Euro (see the EMU coefficients section).
3. Enter the currencies to be used within each Scala company (see the Currency Definition section).
46
SYSTEM UTILITIES
4. If you need the centralised currency table to link definitions of the same currency in different Scala
companies with each other, use the Central Currency Register. In this case, the definition of the
currency in each company will refer to the one Central Currency Register currency code.
For new Scala installation, the Central Currency Register can be defined at the first stage of
activating the currency system. The procedure is similar to adjusting Central Currency
Register; see the Adjusting Central Currency Register section for details.
Example:
US Dollar (USD) can be assigned to the currency code 01 in the company 1, to the currency code
10 in the company 2, to the currency code 23 in the company 3 and so on, but be linked to the one
particular currency code in the Central Currency Register.
To activate the Central Currency Register, first set up the Central Currency Register (see the
Setting up Central Currency Register section) and thereafter create it (see the Creating Central
Currency Register section).
The Central Currency Register can be switched on and off at every stage of work.
To support a heightened level of security, only the system manager (SYS) of Company 01 can
carry out the routines related to the Central Currency Register and EMU coefficients.
After the above has been completed, enter/adjust currency exchange rates for a specific date in Scala
companies as often as required for the currency types allowing the exchange rate adjustments (see the
Entering Currency Rates section).
Moreover, with the currency system options, you can:
• Print the currency system (see the Printing Currency System section);
• Enquire currency rates (see the Enquiring Currency Rates section);
• Set up rounding parameters (see the Rounding Parameters section);
• Check out currency conversion calculations (see the Currency Calculator section).
See the sections below for details.
EMU Coefficients
Search Path:
Miscellaneous – Currency File – Enter/Change EMU coefficients
Use this option to register or edit, if required, the fixed exchange rates against the Euro of the EMU-
participating countries’ currencies (currencies of type 1-3).
If your currency system does not comprise currencies of type 1-3, this option can be skipped.
Only the system manager (SYS) of Company 01 can carry out EMU coefficients handling.
For each EMU-currency specify the following:
1. EMU Currency Code
The code of a new EMU currency or of an existing one whose information you want to adjust.
F4 (currencies)
2. EMU Currency Name
The name for the EMU-currency.
3. Date of Changes
The start date when the fixed exchange rate takes effect.
F4 (rate history)
4. Precision
The number of decimals for the EMU rate to be used.
According to EMU legislation, the EMU-currency rates must be calculated with 6 significant
figures. Six significant figures do not mean six decimal places; e.g., one Euro is 1936.27
Italian Lira (only 2 decimal places). For more information, see the Scala EMU User’s Guide.
47
SYSTEM UTILITIES
5. EMU Coefficient
The rate against the Euro (with 6 significant figures).
The EMU rates are defined as “an amount in the other (foreign) currency equivalent to one Euro”,
i.e., the expression “EMU rate German Mark (DEM) = 1.95583” means that one Euro equals to
1.95583 DEM (1.95583 DEM for 1 Euro).
This definition is a reverse one of the “classical” exchange rate definition.
Once the EMU-currency has been defined, you can adjust its attributes and enter the exchange rates for
the particular dates if required; the EMU-currency cannot be deleted unless you delete the Scala
currency files.
Currency Definition
Search Path:
Miscellaneous – Currency File – Add/Change Currency Definition
Use this option to define the currencies to be used for each Scala company.
1. Rate From
Specify a date for the entered currency system to be applied.
? (currency definition dates history)
The first currency (00) is the company’s accounting currency.

2. Currency Code
Enter the Central Currency Register’s currency code (central currency code) for the currency
system to be applied.
F4 (central currency codes)
The field is available if the Central Currency Register is active. See the Central Currency
Register section for details.
3. Name
Enter a three-character currency abbreviation.
It is recommended to use the international currency codes.
4. Type
Specify currency type (0-3); see the Currency Types section above for details.
Warning!
The Euro (currency of type 3) must be defined before any currency of type 1 or 2 can be
entered.
48
SYSTEM UTILITIES
5. Currency Type Description, EMU Currency Code and EMU Name

If the Central Currency Register is active, the information will be automatically displayed in the
TYPE-DESCR, EMU and EMU_NAME columns. Otherwise, for currency 2, enter EMU-currency
link in the EMU field; for the Euro (currency type 3), the link 00 will be displayed automatically.
? (EMU-currencies)
Warning!
If you change the EMU-currency link and there are transactions made using the old link, the
unpredictable results can be expected.
6. Currency description
Enter the currency description. If the Central Currency Register is active, the currency description
specified in the Central Currency Register is displayed by default and can be adjusted.
Central Currency Register

Use the Central Currency Register if you need the centralised currency definitions of the same currency
to be used in different Scala companies.
If you do not need the centralised currency definitions, this option can be skipped.
To activate the Central Currency Register, set up and create it (see Setting up Central Currency
Register and Creating Central Currency Register sections respectively). After the Central Currency
Register is active, you can adjust and cancel it (see Adjusting Central Currency Register and
Cancelling Central Currency Register sections respectively).
Only the system manager (SYS) of Company 01 is to carry out the Central Currency Register
routines.
The Central Currency Register is neither company nor year dependent.
Setting Up Central Currency Register

Search path:
Miscellaneous – Currency File – Adjust Central Currency Register
The described below assumes that the Central Currency Register is not created.
Use this option to set up the Central Currency Register, i.e., to link the currencies already defined for
the Scala companies with one centralised currency code in the Central Currency Register.
The Central Currency Register set-up procedure is as follows:
1. The preliminary Central Currency Register comprising all Scala companies’ currency definitions is
created.
49
SYSTEM UTILITIES
2. For each company the system scans throughout all defined currencies and links them to the created
preliminary Central Currency Register’s currency code (central currency code); you can change the
central currency code link for each currency if required. Before the next company is scanned, you
should confirm or cancel the current company’s central currency codes links.
Creating Central Currency Register

Search path:
Miscellaneous – Currency File – Create Central Currency Register
Use this option to create the Central Currency Register after the currencies have been specified for the
Scala companies.
After the creating procedure has been run, the report will be printed.
Comp01 CENTRAL CURRENCY REGISTER FOR COMPANY 01 98-12-30 11:43:46 Page 0
COMPANY 01 FIN.YEAR 98=========================================================================/Scala/SY1201/5
NO NAME CCC NAME ERR
==============================================================================================================
00 GBP - 005 GBP

01 USD - 002 USD
02 RUB - 006 RUB
03 Eur - 007 Eur
Comp01 CENTRAL CURRENCY REGISTER FOR COMPANY F1 98-12-30 11:43:47 Page 1

COMPANY F1 FIN.YEAR 98===============================================================================/Scala/SY1201/5
==============================================================================================================
00 FIM - 004 FIM

01 USD - 002 USD
02 DM - 003 DM
03 EUR - 001 EUR
04 RUB - 006 RUB
Comp01 CENTRAL CURRENCY REGISTER FOR COMPANY FF 98-12-30 11:43:47 Page 2

COMPANY FF FIN.YEAR 98=========================================================================/Scala/SY1201/5
==============================================================================================================
00 FRF - 000 FRF

01 EUR - 001 EUR
02 USD - 002 USD
03 DM - 003 DM
Comp01 CENTRAL CURRENCY REGISTER FOR COMPANY FI 98-12-30 11:43:47 Page 3

COMPANY FI FIN.YEAR 98=========================================================================/Scala/SY1201/5
==============================================================================================================
00 FIM - 004 FIM

01 USD - 002 USD
14 FIM - 008 FIM
29 EUR - 001 EUR
30 DM - 003 DM
* * * * * * * * * * * * E N D O F R E P O R T * * * * * * * * * * * *
If in the currency system there are currencies not linked to the Central Currency Register code, the
Central Currency Register will not be created. The undefined currency will be marked with an
exclamation mark (!) in the ERR column of the report, and the error message will be displayed. To
50
SYSTEM UTILITIES
complete creating of the Central Currency Register, return to the Adjusting Central Currency Register
option to set up the valid currency links and run the Central Currency Register creating routine once
again.
After the Central Currency Register is created, it becomes active and can be adjusted (see the Adjusting
Central Currency Register option) and/or cancelled (see the Cancelling Central Currency Register
option).
The Create Central Currency Register and Adjust Central Currency Register menu options will
be changed to the Switch Off Currency Register and Enter/Adjust Central Currency Register
menu options respectively.
Adjusting Central Currency Register

Search path:
Miscellaneous – Currency File – Enter/Adjust Central Currency Register
The described below assumes that the Central Currency Register is active.
Use this option to adjust the Central Currency Register’s currency names and descriptions.
1. Currency Code
Enter the Central Currency Register’s currency code (central currency code) for the currency to be
adjusted.
2. Currency Name
Enter a three-character currency abbreviation.
It is recommended to use the international currency codes.
3. Description
Enter the currency description.
Cancelling Central Currency Register

Search path:
Miscellaneous – Currency File – Switch Off Central Currency Register
The described below assumes that the Central Currency Register is active.
Use this option to cancel the Central Currency Register (press Enter twice to confirm cancelling).
Printing Currency System

Use this option to print the defined currency system.
The printout includes the following sections: the company defined currencies with rounding
parameters, all Central Currency Register’s currencies (if the Central Currency Register was created),
currency exchange rate history and EMU coefficients history with the respective parameters.
51
SYSTEM UTILITIES

Comp01 * * PRINT CURRENCY SYSTEM * * 98-12-30 11:46:37 Page 1
CURRENCY DICTIONARY FILE CONTENTS
COMPANY 01 FIN.YEAR 98===========================================================================/Scala/SY12/5
NO NAME CTR PRICE ITEM VAT LINE LINE VAT TOTAL TOTAL VAT Description
==============================================================================================================
00 GBP 005 0.0 0.0 0.0 0.0 0.0 0.0 British Pounds
01 USD 002 0.0 0.0 0.0 0.0 0.0 0.0 US Dollars
02 RUB 006 0.0 0.0 0.0 0.0 0.0 0.0 Russian Rubles
03 Eur 007 0.0 0.0 0.0 0.0 0.0 0.0 Euro

CENTRAL CURRENCY REGISTER CONTENTS
NO NAME Description In use
==============================================================================================================
000 FRF FRF No
001 EUR EUR No
002 USD USD Yes
003 DM DM No
004 FIM FIM No
005 GBP GBP Yes
006 RUB RUB Yes
007 Eur Eur Yes
008 FIM FIM No

CURRENCY HISTORY FILE CONTENTS
NO CTR EMU Start End Rate Sell Rate Buy Dec Unit Opr Type Type Description
==============================================================================================================
- GBP -----------------------------------------------------------------------------------------------
00 005 980801 999999 1 1 2 1 Floating EMU curr
- USD -----------------------------------------------------------------------------------------------
01 002 980801 999999 1.5 1.6 2 1 / 0
- RUB -----------------------------------------------------------------------------------------------
02 006 980801 999999 10 11 2 1 / 0
- Eur -----------------------------------------------------------------------------------------------
03 007 00 980801 999999 2 2.2 2 3 Euro
-----------------------------------------------------------------------------------------------------
Selection
Period :000000-999999
Currency code :00-30

EMU CURRENCY HISTORY FILE CONTENTS
NO NAME Start End Coefficient Prec.
==============================================================================================================
00 EUR 000000 999999 1.00000 5
--------------------------------------------------------------------------------
01 FRF 980101 999999 6.63186 5
--------------------------------------------------------------------------------
02 DEM 980101 999999 1.97738 5
* * * * * * * * * * * * E N D O F R E P O R T * * * * * * * * * * * *
Entering Currency Rates

Search path:
Miscellaneous – Currency File – Enter Currency Rates
Use this option to enter/adjust currency exchange rates for a specified date.
1. Rates From
Enter the date from which the rate will apply.
? (exchange rate dates history)
The date must be later than the currency definition date, otherwise, the currency will be
considered as a currency of type 0.
The currencies defined for the company are displayed. See the Currency Definition section for details
on currencies for the company.
52
SYSTEM UTILITIES
2. Currency Name and Currency Type are displayed in the Name and Typ columns respectively as
defined in the company currency definitions and cannot be adjusted.
The first currency (00) is the company’s accounting currency.
To define a new currency, enter a caret (^) in the Name column; you will proceed with the
company currency definition routine as described in the Currency Definition section.
For currency type 0, you can specify the following:
3. Decimals
Enter the number of decimals to round off the currency calculation results.
The setting will apply to the calculated amounts, not to the currency rates.
Entered number of decimals will apply for new documents from the date specified in the Rates
From field or, if there are currency rates entered for the latest dates, between the date
specified in the Rates From field and the closest later date.
4. Units
5. Operator
In the Unit column, enter the coefficient to be used as a multiplier or devisor (depending on the
next field setting) for exchange rates calculations.
In the O column, enter:
* if the coefficient from the Unit column must to be multiplied by
the rate
/ if the coefficient from the Unit column must to be divided by
the rate
Example:
Let us assume that your accounting currency is Swedish Kronor (SEK), and German Mark (DEM)
is noted as:
100 DEM = 470 SEK.
Therefore:
No Name Units Operator Rate
00 SEK 1 1
…
10 DEM 100 / 470
The advantage of entering rates in this way is that you have no problem with decimals.
6. Selling Rate
7. Buying Rate
Enter the selling and buying rates based on the Units and Operator (“Unit” and “O”) column
settings.
The selling rate is the rate used when selling currency; in Scala it is the bank’s buying rate. The
selling rate will be used within the General Ledger, Sales Ledger, Sales Order, Direct Invoicing,
Project Management and Service Order modules.
The buying rate is the rate used when purchasing currency; in Scala it is the bank’s selling rate.
The buying rate is used within the General Ledger, Purchase Ledger and Purchase Control
modules.
For the currency of type 1, the selling and buying rates are the rates against the Euro.
For the currencies of type 1 and 2, the effective rate against the accounting currency,
calculated via triangulation, is displayed at the bottom of the screen.
53
SYSTEM UTILITIES
For currency type 1, you can specify the following:

3. Decimals
4. Selling Rate
5. Buying Rate
For currency type 2, you can specify only:
3. Decimals
For currency type 3 (the Euro),
• if the accounting currency is of type 0, you can specify:
3. Units
4. Operator
5. Selling Rate
6. Buying Rate
• if the accounting currency is of type 1, you can specify:
3. Selling Rate
4. Buying Rate
• if the accounting currency is of type 2 or 3, the Euro information is not available.
When you have entered all required rates, press Enter or PgDn to finish.
Warning!
To apply the settings, the report must be printed.
Comp01 * * CURRENCY FILE * * 99-03-24 10:00:16 Page 1
ROUNDING PARAMETERS 99-03-24
ROUNDING PARAMETERS
NO NAME PRICE ITEM VAT LINE LINE VAT TOTAL TOTAL VAT TOLERANCE
==============================================================================================================
00 GBP 0 0 0.00 0.00 1.00 0.00 910.00
01 USD 0.0000 0.00 0.00 0.00 1.00 0.00 910.00
02 RUB 0.0000 0.00 0.00 0.00 1000.00 0.00 910.00
03 Eur 0.0000 0.00 0.00 0.00 0.00 0.00 910.00
04 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
05 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
06 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
07 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
08 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
09 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
10 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
11 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
12 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
13 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
14 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
15 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
16 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
17 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
18 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
19 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
20 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
21 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
22 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
23 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
24 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
25 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
26 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
27 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
28 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
29 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
30 --- 0.0000 0.00 0.00 0.00 0.00 0.00 0.00
* * * * * * * * * * * * E N D O F R E P O R T * * * * * * * * * * * *
Enquiring Currency Rates

Search path:
Miscellaneous – Currency File – Enquire Currency Rates
Use this option to enquire currency exchange rates for a specified date. To this end, enter the date in the
Date From field; the information as for entering currency rates is displayed, but cannot be adjusted.
See the Entering Currency Rates section for fields descriptions.
? (exchange rate dates history)
Rounding Parameters
Search path:
Miscellaneous – Currency File – Rounding Parameters
Use this option to set each currency’s rounding parameters for:
54
SYSTEM UTILITIES
• individual prices and VAT

• line level – for item and VAT
• total level unit and total VAT
For each parameter, you can specify a signed 7-digit value to which the relevant amounts will be
rounded. If a positive value is specified, the amounts will be rounded according to mathematical rules,
if a negative value is specified, the amounts will be truncated. You can also specify a zero value; if so,
no rounding will be applied; i.e., the relevant amounts will be kept intact for further calculations and
printed rounded up as specified for the respective currency in the currency rates entering routine (DEC
column).
Example:
Rounding Amount Result
Parameter to be rounded Amount
0,0001 0,12345 0,1235

–0,0001 0,12345 0,1234
…
100 123456,78 123500
–100 123456,78 123400
The following is the description of the rounding parameters:

• PRICE
The rounding value for the item price excluding VAT. That is normally printed with the DDF code
<40> or <41>. The default number of decimals for this rounding value for the accounting currency
is taken from the Stock Control parameters if the Stock Control module is installed; otherwise, it
defaults to currency decimals.
• ITEM VAT
The rounding value for the item VAT amount applied to a single item. This amount added to the
base price can be printed with the DDF codes <42> or <43> and also with the DDF code <83>.
The number of decimals follows the same rules as for the first parameter above.
• LINE
The rounding value for the line total applies to the base price multiplied by quantity. Normally is
printed with the DDF codes <44> or <45>.
55
SYSTEM UTILITIES
• LINE VAT
The rounding value for the line VAT amount at the invoice line level. This amount added to the
line total (DDF code <44> or <45>) can be printed with the DDF codes <46> or <47> and also
with the DDF code <68>.
• TOTAL
The rounding value for the invoice total excluding VAT.
• TOTAL VAT
The rounding value for the total VAT amount on the invoice.
The above parameters’ settings will lead to the following rounding of invoice figures:
1. The base price is calculated by subtracting any line discount from the original price and/or VAT (if
prices include VAT as specified by the Stock Control parameter).
2. The VAT amount per item is calculated by applying the VAT percentage to the base price.
3. The base price is rounded with the rounding parameter 1 (Price).
4. The item VAT is rounded with the rounding parameter 2 (Item VAT).
5. Price including VAT is calculated by adding up the two values from steps 3 and 4.
6. The line total is calculated by multiplying the value from step 3 by quantity.
7. The line VAT is calculated by multiplying the value from step 4 by quantity.
8. The line total is rounded with the rounding parameter 3 (Line).
9. The line VAT is rounded with the rounding parameter 4 (Line VAT).
10. The line total including VAT is calculated by adding up the two values from step 8 and 9.
11. Invoice total is calculated by adding up all the values from step 8.
12. Total VAT on invoice is calculated by adding up all the values from step 9.
13. Invoice total is rounded with the rounding parameter 5 (Total).
14. Total VAT on invoice is rounded with the rounding parameter 6 (Total VAT).
By adjusting and combining all rounding parameters in a flexible manner, you can achieve different
rounding results depending on various statutory or business requirements.
Warning!
To apply the settings, the report must be printed.
Comp01 * * CURRENCY FILE * * 98-12-30 12:02:08 Page 1
ROUNDING PARAMETERS 98-12-30
ROUNDING PARAMETERS
NO NAME PRICE ITEM VAT LINE LINE VAT TOTAL TOTAL VAT
==============================================================================================
00 GBP 0 0 0.00 0.00 1.00 0.00
01 USD 0.0000 0.00 0.00 0.00 1.00 0.00
02 RUB 0.0000 0.00 0.00 0.00 1000.00 0.00
03 Eur 0.0000 0.00 0.00 0.00 0.00 0.00
04 --- 0.0000 0.00 0.00 0.00 0.00 0.00
05 --- 0.0000 0.00 0.00 0.00 0.00 0.00
06 --- 0.0000 0.00 0.00 0.00 0.00 0.00
07 --- 0.0000 0.00 0.00 0.00 0.00 0.00
08 --- 0.0000 0.00 0.00 0.00 0.00 0.00
09 --- 0.0000 0.00 0.00 0.00 0.00 0.00
10 --- 0.0000 0.00 0.00 0.00 0.00 0.00
11 --- 0.0000 0.00 0.00 0.00 0.00 0.00
12 --- 0.0000 0.00 0.00 0.00 0.00 0.00
13 --- 0.0000 0.00 0.00 0.00 0.00 0.00
14 --- 0.0000 0.00 0.00 0.00 0.00 0.00
15 --- 0.0000 0.00 0.00 0.00 0.00 0.00
16 --- 0.0000 0.00 0.00 0.00 0.00 0.00
17 --- 0.0000 0.00 0.00 0.00 0.00 0.00
18 --- 0.0000 0.00 0.00 0.00 0.00 0.00
19 --- 0.0000 0.00 0.00 0.00 0.00 0.00
20 --- 0.0000 0.00 0.00 0.00 0.00 0.00
21 --- 0.0000 0.00 0.00 0.00 0.00 0.00
22 --- 0.0000 0.00 0.00 0.00 0.00 0.00
23 --- 0.0000 0.00 0.00 0.00 0.00 0.00
24 --- 0.0000 0.00 0.00 0.00 0.00 0.00
25 --- 0.0000 0.00 0.00 0.00 0.00 0.00
26 --- 0.0000 0.00 0.00 0.00 0.00 0.00
27 --- 0.0000 0.00 0.00 0.00 0.00 0.00
28 --- 0.0000 0.00 0.00 0.00 0.00 0.00
29 --- 0.0000 0.00 0.00 0.00 0.00 0.00
30 --- 0.0000 0.00 0.00 0.00 0.00 0.00
* * * * * * * * * * * * E N D O F R E P O R T * * * * * * * * * * * *
56
SYSTEM UTILITIES
Currency Calculator
Search path:
Miscellaneous – Currency File – Set-up Verification
Use this option to check out currency conversion calculations for a specified date, i.e., to covert the
amount in the source currency to the target currency.
1. Date
Enter the date for the currency conversion calculation.
2. Local Currency Type
The type of the accounting currency is displayed.
The field is not user-adjustable.
3. Source Currency
Enter the code of the currency to convert the amount from.
F4 (currencies)
4. Amount
Enter the amount in the accounting currency for conversion.
5. Target Currency
Enter the code of the currency to convert the amount to.
F4 (currencies)
6. Amount
The amount in the target currency is displayed after the calculation has been run.
7. User Defined Rate
y Enter the rate of the target currency against the source currency.
n You proceed with the currency conversion calculation.
The field is available if the source and target currency types allow the exchange rate
adjustments and either source or target currency is of type 0. For more information on
currency types, see the Currency Types section in this chapter.
After the above parameters have been set up, the calculation result screen pops up.
The target currency amount will be rounded as specified for the currency in the currency rates
entering routine (DEC column).
Currency Calculator (SP04)

Search path:
Miscellaneous – Currency File – Currency Calculator
Use this option along with the currency verification (Set-up verification) for onscreen outlook all
conversion details (including triangulation).
1. Date
Enter or select from the dropdown list box the date for the currency conversion calculation.
2. Source Currency
Select the currency to convert the amount from.
3. Target Currency
Select the currency to convert the amount to.
4. Local Currency Type
The type of the accounting currency is displayed.
57
SYSTEM UTILITIES
5. Amount
Enter the amount in the accounting currency for conversion.
6. Click on the Calculate button to perform currency conversion.
The visual calculation-result screen with conversion details pops up.
The target currency amount will be rounded as specified for the currency in the currency rates
entering routine (DEC column).
If in the active Central Currency Register the currencies are coded according to the standard
currency abbreviations, the respective country flags are displayed alongside currency codes.
Rounding Tolerance for Invoice Closing (SP03)

Search path:
Miscellaneous – Currency File – Rounding Parameters
Use this routine to set up the rounding tolerance for closing foreign-currency invoices in the Sales
Order and Direct Invoicing modules when the payment currency is neither accounting currency nor
invoice currency.
The round off tolerance margin should be set for each currency in absolute value. When invoice
payment is entered and the underpaid or overpaid amount by absolute value is less then the tolerance or
equal to it, the system adjusts the last payment amount in invoice currency (positively or negatively) to
the exact invoice amount without creating an accounting transaction.
Example:
Invoice of 5537633 ITL has been paid as 2859.95 EUR. Invoice closing gives
2859.95*1936.27=553635 ITL. Thus the invoice is 2 ITL overpaid. The amount of 2 ITL will be
ignored and invoice will be closed in the invoice currency.
Three Decimals Option in VAT Rate (SP10) (#28688)

Search path:
Miscellaneous –Features Activation Setup – Edit Feature Setup
The number of decimals in VAT rates is controlled by the USA-07 decimals in VAT rate switch. If
the switch is on, all VAT rates have 3 decimals; otherwise, all VAT rates will have 2 decimals.
Additional Multilingual Support (SP08)

Search path:
Miscellaneous – Language Code Setup
Use this routine to set up 3-letter abbreviations for languages used in Scala.
• Language Code
• Language
The language codes (0-9) with the respective descriptions from Scala .lan files are displayed and
are not user-adjustable.
• Language Abbreviation
Enter the language abbreviation for this language code.
The settings are company-dependent.
These settings are used as follows:
Descriptions in Scala code files (except for payment methods, payment terms and delivery terms) are
being entered and displayed on screen in a language of a current user; the other language descriptions
are stored separately.
58
SYSTEM UTILITIES
For Scala sales side modules, the DDF-files to be sent to customers are printed in the language that
code is set in the customer file (Currency/VAT option, Language Code field). For other Scala modules,
the DDF-files are printed in the language of a current user.
If the description in customer’s language is not entered, the description in the last entered
language will be used.
Menu Customisation for Currency System options

(SP04)
Search path:
Access Rights/Menus – Adjust Menus & Menu Passwords – Change Menu Type 2
Some Currency System options can be used via stand-alone menu items. To this end, in the menu
structure adjusting routine enter sy12 in the PGM/MENU field and set the Alt field as follows:
Currency System option Alt field’s content
Enter Currency Rates 1

Enquiry Currency Rates 2
Rounding Parameters 3
Add/Change Currency Definition 4
Print Currency system 5
Set-up verification 6
Enter/Change EMU coefficients 7
The option is available for the

system manager (SYS) of
Company 01 only.
Enter/Adjust Central Currency Register 8
The option is available for the

system manager (SYS) of
Company 01 only.
Currency Calculator 10
For more information on menu structure adjusting, see the Software Reference chapter.
Currency System Converter (Scala 5.0 to Scala 5.1)

(SP01)
Search path:
Currency System Converter
The utility must have been run from the Company 01 menu only.
Use this utility to convert the currency files when you update your Scala system from the version 5.0 to
5.1.
To run the utility properly, the Scala 5.0 currency files (Currency File and Currency History) and Scala
5.1 currency files (Central Currency Dictionary, EMU Currency History, Currency Dictionary and
Currency History) must exist in the subdirectory DAT/SY of the Scala root directory. If the user’s
company uses the currency system other then of the Scala Company 01 (Own Currency File field in the
59
SYSTEM UTILITIES
Company File), the Scala 5.1 Currency Dictionary and Currency History files must exist for each
company the utility is being run for. The details about how to create new data files see in the Scala
System Utilities User’s Guide (Software Reference – File Checks – Create New Data Files chapter).
Once the currency conversion is done, the summary report can be printed.
Restricted Usage of Quotation Marks with Text

Variables and Commas in Input-Output Files (#29744)
Beware that usage of double quotation marks within other double quotation marks when defining text
variables (e.g. “bonus “xx” “) results in loss of data. To avoid data loss, you may use single quotation
marks within double quotation marks (e.g. “bonus ‘xx’ “). Beware also that in the user-adjustable
input-output files (such as PA040000.fld) the use of commas within commentary text results in system
crash.
Compulsory VAT Code 00 (#30601)

Search path:
Miscellaneous – VAT Codes
VAT code 00 is compulsory for the system to work properly and always must be set up.
Language Dependent Tax Name (SP13)

Search path:
Miscellaneous – TAX Codes
• Language
Enter the code of the language to enter the tax.
• Tax Code
• TAX Name
Enter the name of the tax code.
Tax Rounding and Calculation Options for Customers

and Suppliers (SP13)
Search path:
Miscellaneous – Features Activation set–up – Edit Feature set-up
With the JAP-02 TAX rounding and calculation feature activated, the following tax rounding and tax
calculation methods are available:
Tax rounding methods:
0 rounding according to the rounding parameters specified in the Scala currency file
1 rounding up to the number of decimals specified for the currency
2 rounding down to the number of decimals specified for the currency
3 normal rounding to the number of decimals specified for the currency
(if a digit is less than 5 – rounding down; otherwise – rounding up)
Tax calculation methods:

0 rounding the sales order tax amount by each order line
1 rounding the sales order tax amount by order total
Tax rounding method can be specified for each customer and supplier in the customer and supplier files
(Sales Ledger – Customer File – Enter/Adjust Customer, Currency/Tax option, Tax Rounding Method
60
SYSTEM UTILITIES
field and Purchase Ledger – Supplier File – Enter Supplier, Codes option, Tax Rounding Method field
respectively)
Tax calculation method can be specified for each customer in the customer file (Sales Ledger –
Customer File – Enter/Adjust Customer, Currency/Tax option, Tax Calculation Method field)
Tax rounding method is used:

• in the Sales Ledger module:
• when entering Sales Ledger invoices
• when calculating tax correctionals
• in the Purchase Ledger module:
• when entering Purchase Ledger invoices
• in the Sales Order module:
• when entering sales orders
(except for rounding parameters specified in the Scala currency file)
• when enquiring sales orders
(except for rounding parameters specified in the Scala currency file)
• when printing Sales Order documents
• when closing sales orders.
Tax calculation method is used:

• in the Sales Order module:
• when entering sales orders
• when enquiring sales orders
• when printing Sales Order documents
• when closing sales orders
Integration of Third Party Products into Scala (SP11)

Emeritor Integration
Emeritor is the Performance Group product for Internet purchases handling.
The Emeritor integration into Scala is available if:
• you are a registered Emeritor client
• you have installed the Scala add-in for Emeritor integration
To handle Emeritor purchase orders in Scala:

• include the Emeritor integration program pc0300 in Scala menu (System Utilities module)
You can use menu alternatives to set the Emeritor Configure and Access Web-site options as
separate menu items.
Use the Access Web-site option to access the Emeritor web site.
Refer to the System Utilities User’s Guide for details.
• in the new Emeritor menu (Configure option), setup the following parameters:
• Emeritor web site URL
specify the web site for Emeritor purchase handling
61
SYSTEM UTILITIES
• Connection Timeout
specify the timeout when establishing connection to the Emeritor web site
• Supplier Code
specify the Scala supplier code to use for Emeritor purchase orders
• Order number series
specify the Scala purchase order number series for Emeritor purchase orders
Transferring Scala Data to Other Applications

(SP12)(#33179)
With Scala, you are able to prepare internal Scala data as XML messages and to transfer it to other
applications and/or enterprises.
To prepare Scala data as XML messages, the following setup is required:
• Configure the XML printer connection
• Create the DDF-files for the XML output
For more information, see the sections below.
After the XML printer connection is configured and the DDF-files for the XML output are prepared,
when you select printing to the XML output, the transferring utility based on the transfer method,
specified in the XML printer connection, Printer path Network parameter, is activated.
Configuring XML Printer Connection

Search Path:
Document/Installation – Terminal & Printer Definition – Printer Connections
To configure the printer connection for the XML output, set the following parameters:
• Printer Name
Enter the name of the printer starting with EDI (for example, EDI/XML)
• Printer path Network
The following transfer method options are available:
Transfer method Field content

1. Defined by XML file content Leave this field empty.
The transfer method is
defined in the XML file by the
PostInfo attribute. Examples of XML messages:
<Request RequestID='SalesOrder'
PostInfo=’ScaDES:SERVER'>
PostInfo='Post:http://WEBSITE/ScaDES.asp'>
PostInfo='Queue:.\private\sdes$'>
2. Scala Data Exchange Server text starting with : (semicolon)

(ScaDES) the rest of the text is treated as a name of the ScaDES server
You should install and

configure Scala
DataExchange server to use
this feature. Refer to Scala
Data Excahnge Server
documentation for more
62
SYSTEM UTILITIES
details.
3. Internet host text starting with an ampersend (&)
the rest of the text is treated as an URL of ASP
To post the XML message to
ASP, the XML parser
(msxml.dll) is to be installed.
This component is included by
default in Microsoft Internet
Explorer (version 4.x, 5.x, or
higher) if installed.
4. Microsoft Message Queue text starting with a dollar sign ($)
(MMSQ) the rest of the text is treated as a queue name
To use this feature, install and

configure MSMQ.
5. External Poster any external viewer name (for example, Poster.exe)
• Spool method
enter 3 (Print to external RTF viewer)
Creating DDF-files for XML Output

For XML Output:
• Use DDF-files for EDI
• For number formats, in DDF codes, use the DDF prefix . (period) that will print a period between
integer and fractional parts for numbers with non-zero fractional part and only integer part for
integer numbers
Example:
<.35> prints:
102.55
200
• For date formats, in DDF codes, use the DDF suffix @4 that will print in the YYYY-MM-DD
format
Example:
<17@4> prints:
2001-01-15
• For text formats, in DDF codes, use the DDF postfix & (ampersand) that adjusts the placement of
the next DDF-file fragment according to the current DDF code content length and replaces the
following characters in the DDF code content with the respective XML entities:
& &
< <
> >
‘ '
“ "
Example:
If the name of the company is Demis & Sons,
<89&> prints:
Demis & Sons
For more information on DDF prefixes, suffixes, and postfixes, see the Scala DDF Manual.
63
SYSTEM UTILITIES
Changes in Scala Menu Default Settings (SP13)

Search path:
Access Rights/Menus – Adjust Menus & Menu Passwords – Change Menu Type 2
The default settings for General Ledger entering transactions and entering bank transactions routines
are as follows:
Option Alt field’s content
Enter GL Transactions blank

Enter GL Bank Transactions 32
64
DDF
DDF
General
Additions to Extended DDF Format
<[Prefix] DDF Code [Selector] [Conversion] [Suffix] [Language] [Postfix]>
Component Format Value Description

Prefix The component is optional.
? * Leading asterisks
(asterisk) Required in some financial documents.
Example:
<*35> prints:
**********100
(SP12) (#33179)
Decimal symbol that prints a period between
. integer and fractional parts for numbers with
(period) non-zero fractional part and only integer part for
integer numbers
This setting overrides the Numerical
format settings in the Scala company file.
Required for XML output.
Examples:
<.35> prints:
102.55
200
_ Decimal symbol that prints an en dash (-)

(underscore) between integer and fractional parts for all
numbers (zeros as fractional part for integer
numbers).
Required in some financial documents.
Examples:
<_35> prints:
102-55
200-00
= Decimal symbol that prints an en dash (-)

(equal sign) between integer and fractional parts for numbers
with non-zero fractional part and an equal sign
for integer numbers
Required in some financial documents.
65
DDF

Examples:
<=35> prints:
102-55
200=
Postfix The component is optional.
? ; Fit flag that adjusts the placement of the next

(semicolon) DDF-file fragment according to the current DDF
code content length
Examples:
1. in the ddf-file:
1234567890<89>1234567890
in the printout:
<89> = ABC:
1234567890ABC 1234567890
<89> = ABCDEF:
1234567890ABCDEF34567890
2. in the ddf-file:
1234567890<89;>1234567890
in the printout:
<89> = ABC:
1234567890ABC1234567890
<89> = ABCDEF:
1234567890ABCDEF1234567890
(SP12) (#33179)
Fit/XML entity flag that adjusts the placement of
& the next DDF-file fragment according to the
(ampersand) current DDF code content length (see the
examples above) and replaces the following
characters in the DDF code content with the
respective XML entities:
& &
< <
> >
‘ '
“ "
Required for XML output.

With the Fit/XML entity flag, no conversion
of the DDF content to the OEM coding is
performed.
Example:
If the name of the company is Demis & Sons,
1. the DDF code <89> prints:
Demis & Sons
2. the DDF code <89&> prints:
Demis & Sons
66
DDF
? = alphanumeric character
# = numeric character (0–9)
Year Date Format (SP07-08)(SP10) (SP12)

All modules except Payroll and Promissory Notes:
Suffix Description
(in extended DDF format)
@0 the date is printed in 6-digit format with separators
@1 the date is printed in 8-digit format with separators
(SP10) (#26873)
@2 the date is printed in 6-digit format with no separators

@3 the date is printed in 8-digit format with no separators
(SP12) (#33179)
the date is printed in the YYYY-MM-DD format
@4 This setting overrides the Date format settings in
the Scala company file.
ISO 8601 format required for XML output.
Examples:
DDF code (date field) Printed Value
Date style (sequence of day,

month, and year, and date
separators) depends on the
company file’s Date Format and
Separator for Date format
parameters settings for all date
formats except @4.
<17> 15–01–00
<17@0>
<17@1> 15–01–2000
<17@2> 150100
<17@3> 15012000
<17@4> 2000-01-15
Payroll and Promissory Notes:

The 4-digit-year format applies to:
Payroll
– Professional Reports
– Calculation-Statistical Reports
Promissory Notes
– Reports
in the RUNTIME and TERMDEF blocks.
67
DDF
RUNTIME block
Optional field M format:
M [n] [@p] (group 99)
Component Value Description
n 0 no matter
1
2
(or no n
component)
@p @0 the date is entered in 6-digit format
(or no @p
component)
@1 the date is entered in 8-digit format
TERMDEF block
Chain operation M format:
M [n] [@p]
Component Value Description
n 0 date with separators
(or no n
component)
1 date in words
always 4-digit year format
2 date without separators

@p @0 the date is printed in 6-digit format
(or no @p
component)
@1 the date is printed in 8-digit format
Examples:
M format Printed Value
Date style (sequence of day,

month, and year, and date
separators) depends on the
company file’s Date Format and
Separator for Date format
parameters settings.
M 15–01–00
M0
M@0
M0@0
68
DDF
M@1 15–01–2000
M0@1
M1 the 15-th of January 2000
M1@0
M1@1
M2 150100
M2@0
M2@1 15012000
DDF Codes for Replacement Items (#32720)

Table 5.1: Fields from Stock Control, Stock Code File
Do not use the DDF code 229.
288 Stock code of replacement item
69
DDF
General Ledger
Coding Slip (#26528)
Program: gl003p.dll
DDF-file: gl02cc00.ddf
gl02cc00.edi when EDI is used
cc = Company code
If the file is not found, a search is made for the DDF-file for Company 01.
If this file is not found, the program displays an error message and terminates.
Data for the Document Head

04 Customer, supplier
05 Document number or invoice number
(#26634)
DDF codes 40 and 41 cannot be used in this section.
Data for the Document Lines (#26634)

49 Debit amount
50 Credit amount
Example of DDF File for Periodic Transaction Remeasurement Report

(#33265)
DDF File:
:START-SELECTION
==================SELECTION=====================
ACCOUNTS
From: <321> To: <322>
:END-SELECTION
:START-FORM
====================FORM========================
Date: <01> Tra.GL No.:<02> Tr.No<03> Line No.:<29>
Source Acc: <08> <13>
Amount: <18> <24> <06> <07> --> <25> <19>
--> <14> <26> <11> <12>
<$14>
================================================
:END-FORM
:START-TOTAL
=====================TOTAL======================
Total target: <342>
Total source: <341>
<$341>
================================================
:END-TOTAL
Sales Ledger
DDF Code for Invoice Currency Balance in Statement by Date (SP01) (#29167)
Program: sl0171.dll
DDF-file: sl06cc0z.ddf
sl06cc0z.edf when EDI is used
cc = Company code
z= Language code
f= Document code
If the file is not found, a search is made for the DDF-file with document code f (0).
If this file is not found, a search is made for the DDF-file for Company 01 with document code f.
If this file is not found, a search is made for the DDF-file for Company 01 with document code f and
language code 0.
Data for Document Lines

47 balance in the invoice currency
60 balance in the accounting currency
70
DDF
DDF Codes for Location Information (US/Canada) (SP11) (#29206)

DDF codes used in Sales Ledger documents
Use the following DDF codes to include in the Sales Ledger documents:
• The company location information
90 city
23 state
24 ZIP code
• The customer location information
498 city
111 state
482 ZIP code
Purchase Ledger
Statement by Supplier (#25590)
Program: pl0180.dll
DDF-file: pl01cc0z.ddf
pl01cc0z.edi when EDI is used
cc = Company code
z= Language code
If this file is not found, a search is made for the DDF-file for Company 01 with language code 0.
The structure of the DDF-file is the same as for Statement.

Additional DDF numbers in Document Lines
50 Invoice amount in accounting currency, credit
51 Payment amount in accounting currency, debit
52 Balance amount in accounting currency
53 Reference/Comment
54 Total amount in accounting currency
55 Accounting currency name
59 Running balance amount in accounting currency
Sales Order
Common DDF Codes in Sales Order Documents
Legend:
DDF Info Type (DDF codes)
• Document
(DDF/Program)
cc – company file
z – language code
1. Order Header (DDF codes 600 – 716, 790 – 799)

• Invoice
(or00cc0z.ddf /or0081.dll)
• History Invoice
71
DDF
• Tax Invoice
• Quotation
• Order Confirmation
• Delivery Note
• History Delivery Note
• Picking List
• Delivery Proposal
• Product Label
• Export Declaration
• EUR Certificate
• Export Proforma Invoice
• Export Document
(or8cc00.ddf, or18cc01.ddf /or0184.dll)
• Export Document with Consignment Note
(or8cc00.ddf , or18cc01.ddf /or0185.dll)
• Summarised Export Document
• All Transport Documents
(or11cc0z.ddf, or12cc0z.ddf ,or13cc0z.ddf, or14cc0z.ddf, or15cc0z.ddf, or16cc0z.ddf,
or17cc0z.ddf/or0071.dll, or0072.dll)
2. Order Line (DDF codes 800 – 885, 990 – 999)

• Invoice
• History Invoice
• Tax Invoice
• Quotation
• Delivery Note
72
DDF

• Picking List
• Product Label
• EUR Certificate
• Export Document
3. Delivery Line (DDF code <Annn>)

• Invoice
• History Invoice
• Tax Invoice
• Delivery Note
• Picking List
4. Batch (DDF code <Bnnn>)

• Invoice
• History Invoice
• Tax Invoice
73
DDF
• Delivery Note
• Picking List
5. Export Invoice (DDF code <Xnnn>)

• Invoice
• History Invoice
• All Transport Documents except Consignment Address Label
(or11cc0z.ddf, or13cc0z.ddf, or14cc0z.ddf, or15cc0z.ddf, or16cc0z.ddf,
or17cc0z.ddf/or0071.dll)
6. Stock/Warehouse (DDF code <Dnnn>)

• Delivery Note
• Picking List
7. Ordering Customer (DDF code <Cnnn>)

• Invoice
• History Invoice
• Tax Invoice
• Quotation
74
DDF
• Delivery Note
• Picking List
• Product Label
• EUR Certificate
• Export Document
8. Stock Item (DDF codes 200 – 381, 390 – 399)

• Invoice
• History Invoice
• Tax Invoice
• Quotation
• Delivery Note
• Picking List
75
DDF
• Product Label
• EUR Certificate
• Export Document
9. Customer Information (DDF codes 400 – 514, 590 – 599)

• Invoice
• History Invoice
• Tax Invoice
• Quotation
• Delivery Note
• Picking List
• Product Label
• EUR Certificate
• Export Document
76
DDF

DDF Code for Gross Amount (SP04)(#31487)

The DDF code applies in the following Sales Order documents
• Invoice/Credit Note/History Invoice
• Tax Invoice
• Quotation
• Picking List
• Delivery Note/History Delivery Note
Data for Document End

DDF codes for the FLOATEND block:
Only for lines starting with *8
190 Gross amount (sum of VAT basis and VAT amount)
New DDF Codes in Sales Order Documents (SP04-09) (#28661)

The changes apply for the following Sales Order documents:
• Invoice/Credit Note/History Invoice
• Tax Invoice
• Quotation
• Picking List
• Delivery Note/History Delivery Note
Data for all sections:

1001 Order currency exchange rate on BE date
1002 Invoice currency exchange rate on BE date

Data for the BODY blocks:
1003 Customer/stock remark
Data for the Document End

Data for the FLOATEND block:
41 Gross VAT percentage
77
DDF
1000 Net VAT percentage
174 All lines total discount without VAT (price without VAT with discount – price without VAT
without discount)
New DDF Codes in Sales Order Documents (SP13)

:START-FLOATEND
Text for the end of document. Printed after the last line of the invoice.
• Lines starting with *N are printed only if the order contains an allowance.
• Lines starting with *O are printed only if the order contains a surcharge.
• Lines starting with *P are printed only if the order contains an advance.
:END-FLOATEND
DDF Codes for FLOATEND Block

1010 Tax name
1011 Allowance
1012 Surcharge
1013 Advance
DDF Code for Other Tax Amount in Sales Order and Direct Invoicing
Document Lines (SP13) (#34540)
The new DDF code applies for the following documents:
• Invoice/Credit Note/History Invoice (OR)
• Order Confirmation (OR)
• Delivery Note/History Delivery Note (OR)
• Invoice/Credit Note (DI)

Data for the BODY0 block:
1016 Other tax amount
To use the DDF code 1016, activate the feature Printing Other Tax Amount in Document Lines
in the feature setup option (System Utilities/Office Autom. – Miscellaneous – Feature Activation
set-up – Edit Feature set-up).
DDF Codes for Price for Internal Customer (SP12)(#29666)

Program: or0081.dll
or0281.dll History invoice
DDF-file: or00cc0z.ddf
or00cc0z.edf when EDI is used
cc = Company code
z= Language code
f= Document code
language code 0.
78
DDF
Data for BATCH section

For internal customers:
1006 price

For internal customers:
1007 total price
DDF Code for Historical Invoice Prefix (SP11) (#23793)

Program: or0081.dll
cc = Company code
z= Language code
f= Document code
language code 0.

03 Invoice number with the prefix specified in the company file
620 Invoice number without prefix
708 Prefix from order head
Example:
<708><608> – invoice number with prefix from order head
For long ddf codes, there is a gap between the invoice number and invoice prefix.
To avoid this gap, use the ”;” modificator:
<708;><608>
New DDF Codes for Invoice/Credit Note/History Invoice

Program: or0081.dll
cc = Company code
z= Language code
f= Document code
language code 0.
Data for Document Head (SP12) (#32863) (#32199)

Order header file data (DDF codes 600–799). See Table 10 in the chapter General DDF Codes.
79
DDF
New DDF code in Table 10: Fields from Order/Invoicing, Order Header File
704 Copy counter
In addition:
00 Text and number to be printed on a copy; for each printing, copy numbering starts from
1
(see the Printing Document Copies section below for details)
1008 Text and number to be printed on a copy; for each sequential printing, copy numbering
starts from the number of the previously printed copy
(see the Printing Document Copies section below for details)
For historical documents, numbering continues.
If the respective order of the already printed document has been adjusted, the copy
counter is zeroed.
Printing Document Copies

• The number of document copies to be printed (in addition to the original document) is specified
in the Sales Order No. of Invoice Copies parameter settings.
Example:
if No. of Invoice Copies = 2, three documents are printed.
• The text to be printed on the top of the original document when it is printed for the first time
is specified in this DDF-file, after the document header section (START-HEAD – END-HEAD),
in the first line (with the number of lines in the document body) starting from the 4-th position.
This text is optional.
Example:
for the DDF-file containing the following lines:
…
:END-HEAD
50 Original
…
the word Original will be printed in the top right of the original document when it is printed for
the first time.
• The text to be printed on document copies when using the DDF codes <00> and <1008> is
specified in this DDF-file, after the document header section (START-HEAD – END-HEAD), in
the second line.
Example:
for the DDF-file containing the following lines:
…
:END-HEAD
50
Copy No:
…
the DDF codes <00> and <1008> will print the word Copy No: following by the respective copy
number (see examples below).
• Examples of the DDF codes <00>, <704>, <1008> contents:
For No. of Invoice Copies = 2
and the following DDF-file:
…
:END-HEAD
80
DDF
50 Original
Copy No:
…
First-time printing:
Original Document:
<00>: Original
<704>: 0
<1008>: Original
Copy 1:
<00>: Copy No: 1
<704>: 1
<1008>: Copy No: 1
Copy 2:
<00>: Copy No: 2
<704>: 2
<1008>: Copy No: 2
Second-time printing:
Original Document:
<00>: Original
<704>: 3
<1008>: Copy No: 3
Copy 1:
<00>: Copy No: 1
<704>: 4
<1008>: Copy No: 4
Copy 2:
<00>: Copy No: 2
<704>: 5
<1008>: Copy No: 5
Printing from History (after the document was closed):
81
DDF
Original Document:
<00>: Original
<704>: 6
<1008>: Copy No: 6
Copy 1:
<00>: Copy No: 1
<704>: 7
<1008>: Copy No: 7
Copy 2:
<00>: Copy No: 2
<704>: 8
<1008>: Copy No: 8
Document Names
The document names for invoices, invoice specifications, and credit notes are specified in this DDF-
file after the document header section (START-HEAD – END-HEAD), in the 3-rd, 4-th, and 6-th lines
respectively.
These document names are printed by the DDF code <18>.
Example:
…
:END-HEAD
50
Copy No:
INVOICE
SPECIFICATION
Amount to pay:
CREDIT NOTE
…
In addition, you can specify the document names for historical invoices and credit notes in the
following DDF-file.
cc = Company code
z= Language code
f= Document code
language code 0.
Structure of DDF File

HISTORICAL INVOICE
Document name for historical invoice.
82
DDF
HISTORICAL CREDIT NOTE

Document name for historical credit note.
Data for Document Lines (SP10) (#29824)(#22001) (#29824)

Stock code file data (DDF codes 200–399). See Table 5.1 in the chapter General DDF codes.
Batch file data (DDF codes B00–B99). Used in the BATCH block. See Table 7 in the chapter General
DDF codes.
Order line file data (DDF codes 800–999). See Table 11 in the chapter General DDF codes.
Delivery line file data (DDF codes A00–A99). See Table 12 in the chapter General DDF codes.
In addition:
1004 Number of parcels in order line
Rounding and displaying of decimals using the 1004 code depends on the Stock Control
parameter “No. of Decimals Unit Package”.
1005 Residual Delivery Quantity (Quantity Ordered minus Quantity Delivered)
This DDF code is also valid for the following documents: Print Quotations, Confirmation,
Delivery Note, Picking List, Delivery Proposal, Tax Invoice, Proforma Invoice and
History Delivery Note.
Cash Discount and VAT DDF Codes (Invoice Credit Note/History Invoice)
(#26922)
Invoice/Credit Note/History Invoice

Program: or0081.dll
cc = company code
z = language code
f = document code
If the file is not found, the program searches for the DDF with document code 0.
If this file is not found, the program searches for the DDF for Company 01 with document code f.
If this file is not found, the program searches for the DDF-file for Company 01 with document code f
and language code 0.
Structure of the DDF-file

:START-FLOATEND
• Lines with DDF codes 187, 188 starting with *I are printed if the invoice currency does not coincide with the
accounting currency and Total Vat is not zero (The codes can be used without *I)
• Lines starting with *M are printed for each nonzero cash discount as defined by payment terms (DDF codes 138,
139, 63, 64, 189; the codes cannot be used without *M).
:END-FLOATEND

187 Total VAT in the accounting currency
188 Accounting currency name
138 Cash discount days (from payment terms)

139 Cash discount % (from payment terms)
83
DDF
63 Discount gross amount, taxes included (Total * Discount Percent / 100)

64 Discount tax amount (Total VAT * Discount Percent / 100)
189 Discount net amount, without taxes (Discount Gross Amount – Discount Tax Amount)
84
DDF
DDF Codes for Allocation Quantity in Delivery Proposal (SP13) (#34112)

Program: or0211.dll
DDF file: or05cc0z.ddf
cc = Company code
z= Language code
f= Document code
If the file is not found, a search is made for the DDF file with document code f (0).
If this file is not found, a search is made for the DDF file for Company 01 with document code f.
If this file is not found, a search is made for the DDF file for Company 01 with document code f and
language code 0.

Order line file data (DDF codes 800–999). See Table 11 in the chapter General DDF Codes.
832 Allocated quantity in sales units in all delivery proposals for this sales order
852 Allocated quantity in stock units in all delivery proposals for this sales order
In addition:
1014 Allocated quantity in sales units in the current delivery proposal

1015 Allocated quantity in stock units in the current delivery proposal
Use the DDF codes 832, 852, 1014, and 1015 in the BODY0 section.
Order Consolidation (#30087)

Invoice/Credit Note/History Invoice
When an invoice was created in the Order Consolidation routine, the data for document lines is defined
in the stand-alone DDF-file:
Program: or0100.dll
cc = Company code
z= Language code
f= Document code
If this file is not found, a search is made for the DDF-file for Сompany 01 with document code f and
language code 0.

:START-MERGE
Definition of document lines for each sales order consolidated in the invoice.
:END-MERGE
Data for the Document Lines

Fields from Order/Invoicing, Order Header File (DDF codes 600–799). See Table 10 in the chapter
General DDF codes.
• Line starting with *1 is used for Order discount % (DDF code 619).
• Line starting with *2 is used for Number of delivery note (DDF code 622).
• Line starting with *3 is used for Reference (DDF code 617).
• Line starting with *4 is used for Repeat order dates (DDF codes 638, 639).
85
DDF
Correct Example for Delivery Note/History Delivery Note (#28840)

Program: or0171.dll
or0291.dll History delivery note
cc = Company code
z= Language code
f= Document code
language code 0.
DDF-file for Delivery Note

:START-HEAD
<00>
<120>
<121> <18> <03> <05>
<122> Date Your Reference
<123> <02> <13>
Order Our Reference
<04> <12>
Delivery Address: Customer:

<34> <06>
<35> <07>
<36> <08>
<37> <09>
Terms of Payment
<14>
Terms of Delivery
Remarks: <15>
<27> Del.time Way of Delivery
<28> <615> <16>
--------------------------- ------------------------------------------------
ITM STOCK CODE---------- DESCRIPTION-------------- QTY.O QTY.S UNIT--
--------------------------- ------------------------------------------------
:END-HEAD
41
C O P Y N o :
DISPATCH NOTE
:START-BODY0
<48> <50> <51> <57> <58> <56L07>
:END-BODY0
:START-BODY1
<48> <50> <51> <57> <58> <56L07>
:END-BODY1
:START-BODY2
<48> <50> <51> <57> <58> <56L07>
:END-BODY2
:START-BODY3
<52>
:END-BODY3
:START-BODY4
<51>
:END-BODY4
:START-FLOATEND
+----------------------+
¦NO OF PACKAGE<130> EA¦
¦NET WEIGHT <127> KG¦
¦GROS WEIGHT <128> KG¦
¦VOLUME <129> M3¦
+----------------------+
*A <83>
:END-FLOATEND
:START-END
--------------------------- --------------------------------------------------
<124>
<125>
<126>
:END-END
:START-FORMEND
--------------------------- --------------------------------------------------
<124>
<125>
<126>
:END-FORMEND
:START-FEED
:END-FEED
86
DDF
DDF Codes for Customer Stock Code (Invoice/Credit Note/History

Invoice, Tax Invoice, Quotation, Order Confirmation, Delivery
Note/History Delivery Note, Delivery Proposal, Product Label) (#24309)
56 Stock code or Customer stock code
104 Customer stock code
Unavailable DDF Codes in Delivery Note/History Delivery Note (#23777)

Structure of DDF-file
:START-BODY0
• Lines starting with *D (DDF numbers 191–199) CANNOT be used.
:END-BODY0
:START-BODY1
• Lines starting with *D (DDF numbers 191–199) CANNOT be used.
:END-BODY1
Unavailable DDF Codes in Product Label (#29960)

Data for Entire Document
Batch file data (DDF codes B00–B99) CANNOT be used.
Unavailable DDF Codes in Summarised Export Document (#26069)

Stock code file data (DDF codes 200–399), batch file data (DDF codes B00–B99), order line file data
(DDF codes 800–999), and delivery line file data (DDF codes A00–A39) CANNOT be used.
Changes in DDF Codes for Transport Documents (#25341)

The changes will apply for the following Sales Order transport documents:
• Consignment Note
• Postal Address Card
• Postal Cash on Delivery Slip
• General Parcel Slip
• TNT Parcel Service Form
• Securicor Parcel Form
Program: or0071.dll
DDF-file: or11cc0z.ddf Consignment note
or11cc0z.edi Consignment note when EDI is used
or13cc0z.ddf Postal address card
or13cc0z.edi Postal address card when EDI is used
or14cc0z.ddf Postal cash on delivery slip
or14cc0z.edi Postal cash on delivery slip when EDI is used
or15cc0z.ddf General parcel slip
or15cc0z.edi General parcel slip when EDI is used
or16cc0z.ddf TNT parcel service form
or16cc0z.edi TNT parcel service form when EDI is used
or17cc0z.ddf Securicor parcel form
or17cc0z.edi Securicor parcel form when EDI is used
cc = Company code
87
DDF
z= Language code
38 Delivery postcode
74 Delivery telephone number
Purchase Order
Purchase Order, Order Confirmation Reminder, Delivery Reminder:
DDF Codes from Stock Control(#25438)
New DDF Unit Codes(SP08) (#25886)
New DDF Code for Customer Order Number (for Direct Orders) (SP11)
(#28846)
DDF Code for Undelivered Quantity(#30373)

DDF Codes for Stock Items’ Text Lines and Extra Descriptions(SP09)(#30668)
Program: pc0031.dll
DDF-file: pc00cc0z.ddf Purchase order
pc00cc0z.edi Purchase order when EDI is used
pc01cc0z.ddf Order Confirmation reminder
pc01cc0z.edi Order Confirmation reminder when EDI is used
pc02cc0z.ddf Delivery reminder
pc02cc0z.edi Delivery reminder when EDI is used
cc = Company code
z= Language code

:START-BODY2
• Lines starting with *n <51> print the following lines from the stock item’s extra descriptions:
•
• *1 <51> – lines 1 – 10
• *2 <51> – lines 11 – 20
• *3 <51> – lines 21 – 30
• *4 <51> – lines 31 – 40
• *5 <51> – lines 1 – 40
•
The DDF code <51> prints the stock item’s text lines.
If you use both DDF codes <51> (for stock item’s text lines) and *n <51> (for stock item’s
extra descriptions), the stock item’s extra descriptions will always be printed before the stock
item’s text lines.
:END-BODY2

195 Customer order number (for direct orders)

Data from the warehouse file (DDF codes W00–W99). See Table 31.
88
DDF
56 Purchase unit, description
for Body 0 Section:

57 Undelivered quantity (ordered – delivered)
New DDF codes for Body 0 Section:

196 Stock unit, description
197 Sales unit, description
198 MPC unit, description
199 Other unit, description
Table 31: Fields from Stock Control, Warehouse File for Purchase Order
W00 Stock code
W01 Warehouse
W02 Stock balance
W03 Reserved quantity
W04 Backorder quantity
W05 Ordered quantity
W06 Stock-taking difference
W07 Delivery time to the warehouse
W08 Latest stock-taking date
W09 Re-order levels
W10 Economic order quantity
W11 Budgeted sales during year
W12 Shelf space, standard
W13 Lowest purchase price
W15 Allocated quantity
W16 Value of stock-taking difference
W17 Minimum purchase quantity
W18 Maximum purchase quantity
W19 Delivery time unit
W21 Supplier
W22 Alternative supplier
W27 Own supplier
W28 FIFO value
W53 Latest delivery date from supplier
W54 Latest delivery date to customer
W55 Latest order date to supplier
W56 Weighted average price
W57 Standard cost
W58 Landed cost
W59 Purchase surcharge
W60 Budget profile
DDF Codes for Body 3 Section in Goods Received Note (#26446)

Program: pc0241.dll
DDF-file pc08cc00.ddf Goods received note
pc08cc0z.edi Goods received note when EDI is used
cc = Company code
z= Language code

After BODY2 section:
89
DDF
:START-BODY3
Block for delivery lines information.
:END-BODY3
Data for BODY3 section

Delivery line file data (DDF codes A00–A40). See Table 15 in the chapter General DDF codes.
Table 12 is not used.
Stock control batch file data (DDF codes B00–B36). See Table 7 in the chapter General DDF codes.
New DDF Code for Goods Received Note Number (SP11) (#28478)
Table 15: Fields from Purchase Order, Delivery Line File
All DDF codes starting with A must be included in the Body 3 section only.
A40 Goods received note No
Direct Invoicing
DDF Code for Tax Name in Invoice/Credit Note (SP13) (#34316)
DDF Code for Other Tax Amount in Invoice Line (SP13) (#34540)
Program: di0020.dll
DDF file: di00cc0z.ddf
di00cc0z.edf when EDI is used
cc = Company code
z= Language code
f= Document code
language code 0.

Data for the BODY0 block:
198 Other tax amount
To use the DDF code 198, activate the feature Printing Other Tax Amount in Invoice Line in the
feature setup option (System Utilities/Office Autom. – Miscellaneous – Feature Activation set-up –
Edit Feature set-up).
Data for Document End

46 Tax name
The DDF code 46 can be used only in lines starting with *5.
90
DDF
Project Management
FloatEnd Lines with Asterisks in Invoice, Credit Note, and Invoice
Proposal (#35095)
Program: pr0111.dll
DDF file: pr00cc0z.ddf Invoice/Credit note
pr00cc0z.edi Invoice/Credit note when EDI is used.
pr08cc0z.ddf Invoice proposal
pr08cc0z.edi Invoice proposal when EDI is used.
cc = Company code
z = Language code
f = Document code
language code 0.
Structure of DDF
:START-FLOATEND
• Lines starting with *9 are printed only if there is a total amount (used together with DDF code 71).
• Lines starting with *A are printed only if there is a net amount (used together with DDF code 45).
:END-FLOATEND
Printing Serial Number and Extra Text in Invoice (SP09) (#23980)

If a Serial No and/or a Text are entered via the TX function for a stock item that is entered in the Sales
Order via the Project Management, the following settings are required for printing those in the project
invoice:
In the DDF-file for Invoice Proposal/Print Invoice, put a ‘#A <70>’ line in M1 or M2, or M21 block as
shown below:
:START-HEAD-M
M A T E R I A L
=============
:END-HEAD-M
:START-BODY-M1
:END-BODY-M1
:START-BODY-M2
:END-BODY-M2
:START-BODY-M21
<S10L20> <201> <S17R09> <S23R12> <62R14>
*1<S10L20> <201> <S17R09>
#A <70>
:END-BODY-M21
:START-BODY-MT
______________________
TOTAL MATERIAL <50R14>
:END-BODY-MT
Service Management
DDF Code for Document Flag, Proforma Invoice (#27922)
Table 24: Fields from Service Management, Order Header File
For Document Flag, Proforma Invoice, use the DDF code G104 (the DDF code G82 is obsolete).
Correct DDF Codes for Price per Unit in Quotation and Order
Confirmation (#30508)
Program: sm0061.dll
DDF-file: sm12cc0z.ddf Quotation
91
DDF
sm12cc0z.edi Quotation when EDI is used

sm13cc0z.ddf Order confirmation
sm13cc0z.edi Order confirmation when EDI is used
cc = Company code
z= Language code
f= Document code
language code 0.
If this file is not found, an error message displays and the program terminates.

Material Lines
59 Price per unit excluding discount
60 Price per unit including discount
DDF Changes for Quotation and Order Confirmation (SP12)(#33685)

Program: sm0061.dll
DDF-file: sm12cc0z.ddf Quotation
sm12cc0z.edi Quotation when EDI is used
sm13cc0z.ddf Order confirmation
sm13cc0z.edi Order confirmation when EDI is used
cc = Company code
z= Language code
f= Document code
language code 0.
Use the DDF code 193 instead of 62.
DDF Changes for Picking Lists (SP12)(#33685)

Program: sm0311.dll
DDF file: sm15cc0z.ddf Picking note local
sm15cc0z.edi Picking note local when EDI is used
sm18cc0z.ddf Picking note external
sm18cc0z.edi Picking note external when EDI is used
sm19cc0z.ddf Return note
sm19cc0z.edi Return note when EDI is used
cc = Company code
z= Language code
f= Document code
language code 0.

:START-BODY-M20
For lines beginning with *8, the BoM stock items are not printed.
92
DDF
:END-BODY-M20
MPC
Printing Extra Stock Items (SP10) (#31104)
In all MPC documents where extra item descriptions are available.
The DDF codes Z01 – Z40 are not used.
Document Head
V01
|
V40 Extra item descriptions 1 to 40
Configuration (#33265)
Program: mp0783.dll
DDF file: mp22cc0z.ddfConfiguration
mp22cc0z.edi Configuration when EDI is being used
cc = Company code
z= Language code
If this file is not found, a search is made for the DDF-file for Company 01.
If this file is not found, a search is made for the DDF-file for Company 01 and language code 0.
If this file is not found, an error message displays and the program terminates.

:START-HEAD
Definition of the document head, which is printed first on each page. The headings of the
document lines are also defined here.
:END-HEAD
54
Number of lines in the document body. This number should be equal to the number of lines on the
paper less the number of lines in the document head (HEAD) minus 2. Note, that it is not so
important if the number is less than it should be, however if the number is greater, the information
will spill over onto the next page.
COPY No:
Text for copy.
CONFIGURATION
Document name.
:START-BODY0
Not used.
:END-BODY0
:START-BODY1
Block for open item info
:END-BODY1
:START-BODY2
Block for open quantity
:END-BODY2
:START-BODY3
Block for open time
:END-BODY3
:START-BODY4
Block for accessory list, head
:END-BODY4
:START-BODY5
93
DDF
Block for accessory list, lines

:END-BODY5
:START-FLOATEND
Block indicating how the document is to end. This block is normally blank.
:END-FLOATEND
:START-END
Block indicating how the document is to end. This will be printed out when the whole document
body has been printed out and the program has fed the number of lines into the document body.
The block should also contain the document end as FORMEND below. This block is normally
blank.
:END-END
:START-FORMEND
Block indicating the end of each page of the document. This information will not be printed on the
last page when END is used as described above. This block is normally blank.
:END-FORMEND
:START-TRANSP
Definition of the transport line, which is printed at the top of the following pages. This block is
normally blank.
:END-TRANSP
:START-FEED
Block for feeding lines onto a document. Can be used if formats are created using printer graphics.
As a standard, this block usually contains one blank line (one blank line must exist).
:END-FEED
Data for Entire Document

Company data:
78 Company code
79 Company name
80 Reference
81 Address line 1
82 Address line 2
83 Address line 3
84 Fiscal code
85 Telephone number
86 Fax number
87 Telex number
88 Postal giro number
89 Bank giro number
90 Bank name
91 Remark, line 1
92 Remark, line 2
Stock code file data (DDF codes 200–399). See Table 5.1 in the chapter General DDF Codes.
Customer data:
136 Customer name
137 Address line 1
138 Address line 2
139 Address line 3
140 Address line 4
141 Reference 1
142 Reference 2
143 Reference 3
144 Reference 4
145 Telephone number
146 Telex number
147 Telefax number
Work order data (DDF codes K000–121):
94
DDF
K00 Work order number

K01 Stock code
K02 Warehouse code
K03 Planned quantity
K04 Manufactured quantity
K05 Alternate
K06 Scheduling code
K07 Customer code
K08 Sales order number
K09 Sales Order line
K10 Required delivery date
K11 Planned start date
K12 Planned due date
K13 Due date
K14 Work order type
K15 Material reservation date
K16 Text 1
K17 Text 2
K18 Text 3
K19 Option exists
K20 Extra description exists
K21 Open time exists
K22 Planner
K23 Selection term
K25 Registered date
K26 Last change date
K29 Responsible change
K30 Change version
K31 Scheduled date
K32 Stop date
K33 Priority
K34 Responsible priority
K35 Staging
K36 Staging date
K37 Work order closed date
K38 Planned lead time
K39 Lead time
K40 Work order number
K41 Routings exists
K42 Lot
K43 Address 1
K44 Address 2
K45 Address 3
K47 Address 4
K48 Material requisition date
K49 Traveller date
K50 Label 1 date
K51 Label 2 date
K52 Traveller vendor date
K53 Reporting vendor date
K54 Job ticket date
K55 Operation list date
K56 Product cost (y/n)
K57 Actual cost (y/n)
K58 Summarised actual cost (y/n)
K59 Actual cost date
K60 Material issued
K61 All material issued
K62 Only 2 or 3 components
K63 Operation started
K64 All operations finished
K65 Automatic make operation list
K66 Number of material shortage
K67 Accounting string
K70 Accounting code
95
DDF
K71 Number of picking lists

K72 Number of material requisitions
K73 Number of travellers
K74 Number of labels
K75 Number of labels 2
K76 Number of traveller vendors
K77 Number of reporting vendors
K78 Number of job tickets
K79 Number of operation lists
K80 Actual start date
K81 Address 5
K82 Responsible stop
K83 BoM exists
K84 Old quantity
K85 Old due date
K86 Total scrap
K87 Status 1
K88 Status 2
K89 Sales order structure line
K90 Number of units per lot
K91 Size of lot
K92 Rest quantity
K93 Old size of lot
K94 Shop scheduling
K95 Make work order for material list
K96 Work order number series
K97 WIP accounting
K98 Number of shortages, critical
K99 Version stock
In addition:
120 Header
00 Document name
01 Copy number
02 Page number
03 Time
04 Date
05 Work order number
06 Parent item
07 Item description 1
09 Warehouse
10 Warehouse name
11 Item status
12 Planned quantity
13 Unit
17 Actual start date for work order
18 Actual due date for work order
19 Date of last receipt
25 Date of last receipt
26 Creation date
27 Order line cost
28 Type of configuration (0 – Work order created, 1 – Item on stock, 2 – History record)
35 Statistic number
36 Net weight
37 Gross weight
38 Volume
39 Item note 1
40 Item note 2
41 Item location
42 Project
43 Size of package
96
DDF
109 Date (YYWW)

110 Date (YYWWD)
113 Work order start date (YYWW)
114 Work order start date (YYWWD)
115 Work order due date (YYWW)
116 Work order due date (YYWWD)
123 Date (YYMMDD)
125 Work order start date (YYMMDD)
126 Work order due date (YYMMDD)
130 Work order number without zeroes
163 Total net weight
164 Total gross weight
165 Total volume
Data for Body 1, Body 2, Body 3

200 Question number
201 Instruction line 1
204 Open component
20 Open quantity (BoM)
21 Open scrap factor (BoM)
22 Open item (BoM)
23 Open setup time (Op)
24 Open run time (Op)
25 Date of latest receipt
26 Record creation date
27 Order line cost
Data for Body 4

213 Accessory list
214 Segment
215 Accessory list description
Data for Body 5

216 Accessory
217 Description line 1
218 Description line 2
219 Accessory quantity
Example of DDF-File
:START-HEAD
<76> <00> Page: <02>
<01>
<97>
<03> <04>
WO.NR STOCK ITEM DESCRIPTION START DUE QTY UNIT

<05> <06L15> <07L20> <17> <18> <12> <13>
COST : <27> <08L20> TYP: <28>
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
QUERY/STO.IT/ACCESORIES DESCRIPTION QUANTITY/TIME
ДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДДД
:END-HEAD
54
C O P Y N R :
C O N F I G U R A T I O N
:START-BODY0
:END-BODY0
:START-BODY1
<200L20> open item
<204> <205>
:END-BODY1
:START-BODY2
<200L20> open quantity
<204> <205> <207>
97
DDF
:END-BODY2
:START-BODY3
<200L20> open time
<220> <221> <212>
:END-BODY3
:START-BODY4
<213> <215>
:END-BODY4
:START-BODY5
<216> <217> <219>
:END-BODY5
:START-FLOATEND
:END-FLOATEND
:START-END
:END-END
:START-FORMEND
:END-FORMEND
:START-TRANSP
:END-TRANSP
:START-FEED
:END-FEED
Payroll
Payslip DDF Codes Enhancement (SP05) (#24414)
Information for Document End
The DDF codes <45> and <53> use data from the pa0070st.lan file as follows:
line number data format data description

in the pa0070st.lan file
1 “mmmmmm” all wage types between 000000 and mmmmmm are
used for calculation of the ddf code <53>
2 “nnnnnn” all wage types between 000000 and nnnnnn are
used for calculation of the ddf code <45>
The other lines are optional.
These lines (in pairs) can contain the ddf code ranges that are excluded from the calculation of the ddf
code <53>
3 “xxxxxx” wage types between xxxxxx and yyyyyy are
excluded from the calculation of the ddf code <53>
4 “yyyyyy”
…
…
System Utilities
DDF File for VAT Report (#33265)
VAT Report
DDF file: sy01cc0z.ddf
sy01cc0z.edi when EDI is used
cc = Company code
z= Language code
98
DDF
Country Specific Documents

DDF Code for Delivery State Code in US/Canada Purchase Order, Order
Confirmation, and Delivery Reminder (SP12) (#32261)
Program: pc0031.dll
DDF-file: pc00cc0z.ddf Purchase order
pc00cc0z.edi Purchase order when EDI is used
pc01cc0z.ddf Order Confirmation reminder
pc01cc0z.edi Order Confirmation reminder when EDI is used
pc02cc0z.ddf Delivery reminder
pc02cc0z.edi Delivery reminder when EDI is used
cc = Company code
z= Language code
Data for Document Head

114 Delivery state code
DDF Codes for United Kingdom Cheque (SP09) (#26628)(#26629)(#26630)

Program: ple20100.dll
DDF-file: plxxccbz.ddf
cc = company code
b= cheque form
z= language code
If the file is not found, the program searches for the DDF-file for Company 01.
If this file is not found, the program searches for the DDF-file for Company 01 with cheque form 0.
If this file is not found, the program searches for the DDF-file for Company 01 with cheque form 0 and
language code 0.
The following DDF codes:

20 – 28
30 – 82
248 – 255
283 – 287
can be used only within the LSPEC section of the Cheque Printing DDF layout. All other DDF-
codes (unless where stated) can be used throughout the Cheque Printing DDF layout.
DDF Codes
Data from Company File
DDF codes 85–99. See Table 1 in the General DDF codes chapter.
Data from Supplier File

002 Supplier complete name
003 Supplier address 1
006 Supplier reference
007 Supplier remark 1
008 Supplier remark 2
009 Supplier customer code
217 Supplier total in words
99
DDF
218 Supplier amount in figures, without leading spaces (only in cheque)

220 Supplier code
221 Supplier name
222 Address 1
223 Address 2
224 Address 3
225 Address 4
226 Supplier postcode
227 Supplier reference
228 Remark 1
229 Remark 2
230 Customer code
231 Postal Giro account
232 Bank Giro account
233 Bank account number
234 Bank office
235 SWIFT address
236 Country code
237 Supplier invoicing/factoring company
238 Payee (invoicing company or supplier name if invoicing company is blank)
240 Account segment on supplier
241 Segment 1 on supplier
Data from Invoice File

030 Supplier code
031 Invoice number
032 Transaction number
033 Invoice date
034 Invoice BE date
035 Invoice due date
036 Invoice discount date 1
037 Invoice discount 1 (%)
042 Invoice amount in the accounting currency (only in letter)
043 Invoice amount in the original currency (only in letter)
044 Invoice currency code
045 Invoice sales tax amount
046 Invoice accounting string
047 Transaction number Invoice
048 BE date (invoice)
049 Supplier bank code
050 Invoice way of payment
051 Invoice payment block (0/1)
052 Invoice authorisation code 1
053 Commentary text
054 Invoice latest payment date
055 Invoice paid amount in the accounting currency
056 Invoice paid amount in the original currency
057 Payment sent (0/1)
058 Payment priority
059 Storno invoice (0/1)
061 Recurring invoice updated (0/1)
062 Invoice order number
100
DDF
063 Invoice TR date

065 DTA sent amount
066 Recurring invoices (0/1)
067 Invoice state bank code
068 Invoice preliminary booking (0/1)
069 Internal reference number
070 Invoice original company code
071 Invoice clearing nominal ledger account
072 Reference/comment
073 Invoice currency contract (0/1)
074 Invoice fixed exchange rate
075 Invoice contract number
076 Invoice withholding tax code
077 Invoice payment auth. (0/1)
078 Invoice withholding tax
079 Invoice VAT code (0-99)
080 Invoice authorisation code 2
081 Invoice 1099 tax code
082 Invoice 1099 Amount
250 Account segment on invoice
251 Segment 1 on invoice
283 Invoice repeat interval
284 Invoice repeat start date
285 Invoice repeat stop date
286 Invoice repeat amount
287 Invoice repeat percentage
288 Pence amount in figures for pay amount in words in the accounting currency
289 Amount in words type 1 in the accounting currency (e.g., one eight eight for 188) (only
in cheque, amount only for current cheque)
290 Amount in words type 1 in the original currency type 1 (e.g., one eight eight for 188)
(only in cheque, amount only for current cheque)
291 Amount in words type 2 in the accounting currency (e.g., one hundred eighty eight
and 00 US Dollars for 188) (only in cheque, amount only for current cheque)
292 Amount in words type 2 in the original currency (e.g., one hundred eighty eight and 00
US Dollars for 188) (only in cheque, amount only for current cheque)
296 Invoice amount to pay less withholding tax in the original currency (only in letter
section]
297 Invoice amount to pay less withholding tax in the accounting currency (only in letter
section)
Data from Payment Proposal File

020 Supplier code
021 Invoice number
022 Payment block (0/1)
023 Amount paid
024 Discount amount
025 Calculated due date
026 Payment 1099 amount
027 Payment 1099 code
028 Way of payment
Data from Cheque Parameters

010 City/Town
011 Signature 1
101
DDF
012 Signature 2
Other Information (Calculated)

001 Page number
013 Cheque number
014 Payment date
015 System date
016 PGO number
019 Amount in figures (B)
029 Supplier total in figures (left justified)
100-
199 Lines from LSPEC section.
260 Accounting currency name (3-letter code)
265 Pence Amount in figures for SUPPLIER TOTAL in the accounting currency (only
if ‘Total amount per supplier’ = “yes”)
266 Supplier total in words type 2 in the original currency) (e.g., one hundred eighty
eight and 00 US Dollars for 188). Prints “CANCELLED” if the printout goes over
a page. (only in cheque section and if ‘Total amount per supplier’ = ‘yes’)
267 Supplier total in words type 2 in the accounting currency ) (e.g., one hundred
eighty eight and 00 US Dollars for 188). Prints “CANCELLED” if the printout goes
over a page. (only in cheque section and if ‘Total amount per supplier’ = ‘yes’)
268 Supplier total in words type 1 in the original currency) (e.g., one eight eight for
188). Prints “CANCELLED” if the printout goes over a page (only in cheque
section and if ‘Total amount per supplier’ = ‘yes’)
269 Supplier total in words type 1 in the accounting currency) (e.g., one eight eight
for 188). Prints “CANCELLED” if the printout goes over a page. (only in cheque
section and if ‘Total amount per supplier’ = ‘yes’)
274 Supplier total in figures in the original currency. Prints “CANCELLED” if the
printout goes over a page (only in cheque section and if ‘Total amount per
supplier’ = ‘yes’)
275 Supplier total in figures in the accounting currency. Prints “CANCELLED” if the
printout goes over a page (only in cheque section and if ‘Total amount per
supplier’ = ‘yes’)
276 Supplier amount
277 Supplier net amount
278 Withholding tax in the accounting currency
279 Withholding tax in the original currency
293 Amount in figures in the accounting currency less withholding tax (only in
cheque, amount only for current cheque)
294 Amount in figures in the original currency less withholding tax (only in cheque,
amount only for current cheque)
295 Currency of last or current Invoice displayed as a 3-letter code from the currency
file). Can be used on Remittance or Cheque.
Only meaningful on Cheque if paying in a foreign currency, and all
Invoices are in that currency.
298 Pence amount in figures for pay amount in words in the original currency
299 Pence amount in figures for Supplier total the in original currency (only if ‘Total
amount per supplier’ = ‘yes’)
Number of boxes for amount in words

The DDF layout can now specify how many boxes are available for Scala to use when printing
amounts in words. This is how many units are available.
Example:
If this value is 7, then Scala will print values for 7 boxes (Million’s, Hundred Thousand’s, Ten
Thousand’s, Thousand’s, Hundred’s, Ten’s, and One’s). Leading zero values will be printed as
asterisks (*******).
Therefore, 21,784 will be printed as:
102
DDF
******* ******* ..TWO.. ..ONE.. .SEVEN. .EIGHT. ..FOUR.

The Number of Boxes value is specified at the end of the DDF layout, on the line following the
concatenation word “AND” (which is currently the last line). The last three lines of the DDF-file
should then appear similar to the following illustration:
US Dollars
AND
7
Amount in Pence
Three new DDF codes are available to print the Pence Amount on its own. This should be used for
printing the Pence Amount associated with the amount in words, if you require such functionality.
DDF code 288 will print the Pence Amount for the accounting currency pay amount.
DDF code 298 will print the Pence Amount for the original currency pay amount.
DDF code 299 will print the Pence Amount for the supplier total in original currency.
Example
:START-CHECK
<221> <15>
<222>
<223>
<224>
<225> A/C CODE: <220>
<226>
R E M I T T A N C E A D V I C E
=================================
Invoice Date Invoice No Amount Paid Total Invoice

____________ __________ ___________ _____ _______
<100>
----------
Total Payment: <274>
==========
<15> <13> <221> <274>
<268R54>
:END-CHECK
:START-LSPEC
<033> <021> <023R10> <023R10> <42>
:END-LSPEC
- - C A N C E L L E D - -
CANCELLED
**ZERO*
**ONE**
**TWO**
*THREE*
**FOUR*
**FIVE*
**SIX**
*SEVEN*
*EIGHT*
**NINE*
**TEN**
ELEVEN
TWELVE
THIRTEEN
FOURTEEN
FIFTEEN
SIXTEEN
SEVENTEEN
EIGHTEEN
NINETEEN
TWENTY
TWENTY ONE
TWENTY TWO
103
DDF
TWENTY THREE
TWENTY FOUR
TWENTY FIVE
TWENTY SIX
TWENTY SEVEN
TWENTY EIGHT
TWENTY NINE
THIRTY
FORTY
FIFTY
SIXTY
SEVENTY
EIGHTY
NINETY
ONE
ONE THOUSAND
THOUSAND
ONE MILLION
MILLION
ONE BILLION
BILLION
ONE TRILLION
TRILLION
ONE HUNDRED
HUNDRED
ONE HUNDRED
FIVE HUNDRED
SEVEN HUNDRED
NINE HUNDRED
POUNDS
AND
7
PENCE
New DDF Codes and Files for Finnish Transport Documents (SP12) (#33124)
Program: or0073.dll
DDF file: or9fcc0z.ddf
f = 1 – Transport document
2 – Address label
3 – Postal Address form 1
4 – Postal Address form 2
5 – Postal C.O.D. form
cc = Company code
z= Language code
If the file is not found, the program searches for the DDF-file for Company 01.
If this file is not found, the program searches for the DDF-file for Company 01 with language code 0.
In addition:
18 Delivery date in the dd.mm.yyyy format
70 Volume
129 Additional services (for example, LP1234)
130 Transport time (9,14,16, or 21)
131 Article bar code
132 Additional service 1, number
133 Additional service 1, text
142 Content line 1
150 Special handling text (for example, fragile)
151 Transport unit text
152 License plate follow up bar code
153 Destination zip bar code
154 Contract bar code
191 Reference number
192 Bank bar code
DDF File for Transport Document

:START-TDOK
104
DDF
<50> <57> <01>
<51> <58> <04L10>

<52>
<38>
<06L20> <05> <16>

<07L20>
<08L20> <39>
<09L20>
<38>
<53>
<54> <15>
<55>
<09> <24> <25>

<27>
<28>
*1 <41L18> <40> <43> <42L20> <44> <46>
<71> <178>
<11> <176>
<12>
<13> <56>
<177>
<04>
<104>
<105>
<106>
VAT.REG.NO.
RECEIVER/DATE CARRIER/DATE SENDER/DATE
:END-TDOK
DDF File for Postal Address Form 1 (#31862)

:START-TDOK
^XA
^xfe:posti2
^fnid_10^fd<130> ^fs
^fnid_21^fd<50L22> ^fs
^fnid_25^fd ^fs
^fnid_26^fd ^fs
^fnid_30^fd<50> ^fs
^fnid_31^fd<06> ^fs
^fnid_32^fd<07> ^fs
^fnid_33^fd<08> ^fs
^fnid_34^fd<09> ^fs
^fnid_35^fd ^fs
^fnid_36^fd ^fs
^fnid_40^fd<18> ^fs
^fnid_41^fd<178R08> ^fs
^fnid_42^fd<70R08> ^fs
^fnid_71^fd<71> ^fs
^fnid_73^fd<59> ^fs
^fnid_220^fd<152> ^fs
^fnid_230^fd<131> ^fs
^xz
:END-TDOK
euro
mk
2W2101
2W2102
2W2103
2W2104
C.O.D.
105
DDF
Multiple packages
Payer other than sender
Handled separately
Registration
Saturday delivery
Transport unit transport
Receiver’s name is stored
Copy of receiver’s confirmation
Fragile
size
VAK
roller
effective pallet
EUR-pallet
FIN-pallet
DDF File for Postal Address Form 2 (#31862)

:START-TDOK
^XA
^xfe:posti2
^CI0
^fnid_25^fd ^fs
^fnid_26^fd ^fs
^fnid_30^fd<50> ^fs
^fnid_31^fd<06> ^fs
^fnid_32^fd<07> ^fs
^fnid_33^fd<08> ^fs
^fnid_34^fd<09> ^fs
^fnid_35^fd ^fs
^fnid_36^fd ^fs
^fnid_40^fd<18> ^fs
^fnid_41^fd<178R08> ^fs
^fnid_87^fd<04> ^fs
^fnid_220^fd<152> ^fs
^fnid_230^fd<131> ^fs
^fnid_240^fd<153> ^fs
^xz
:END-TDOK
euro
mk
2W2101
2W2102
2W2103
2W2104
C.O.D.
Multiple packages
Handled separately
Registration
Saturday delivery
Fragile
size
VAK
roller
effective pallet
EUR-pallet
FIN-pallet
DDF File for Postal C.O.D. Form (#31862)

:START-TDOK
^XA
^xfe:posti22
^CI0
^fnid_25^fd ^fs
^fnid_26^fd ^fs
^fnid_30^fd<50> ^fs
^fnid_31^fd<06> ^fs
^fnid_32^fd<07> ^fs
^fnid_33^fd<08> ^fs
^fnid_34^fd<09> ^fs
^fnid_35^fd ^fs
^fnid_36^fd ^fs
^fnid_40^fd<18> ^fs
^fnid_41^fd<178R08> ^fs
^fnid_87^fd<04> ^fs
^fnid_220^fd<152> ^fs
^fnid_260^fd<192> ^fs
^fnid_230^fd<131> ^fs
^xz
:END-TDOK
euro
mk
2W2101
2W2102
2W2103
2W2104
C.O.D.
Multiple packages
106
DDF
Handled separately
Registration
Saturday delivery
Fragile
size
VAK
roller
effective pallet
EUR-pallet
FIN-pallet
For Russia: Payment Method R1 (Domestic Payments to CitiBank) and

Payment Method R2 (Foreign Payments to CitiBank)
Program: plr1048.dll Payment Methods R1, R2
DDF file: pl00ccr1.ddf Payment Method R1
pl00ccr2.ddf Payment Method R2
cc = Company code
If the file is not found, a search is made for the DDF file for Company 01.

:START-HEAD
:END-HEAD
:START-BODY
:END-BODY
:START-FOOTER
:END-FOOTER
DDF Codes
Bank information:
B00 Supplier code
B01 Bank number
B02 Bank Name
B03 Extended bank code
B04 Account number
B05 Address line 1
B06 Address line 2
B07 Address line 3
B08 Address line 4
B09 Zip code
B10 Telephone
B11 Telefax
B12 Correspondent bank name
B13 Correspondent extended code
B14 Correspondent account number.
B15 Correspondednt address line 1
B16 Correspondent address line 2
B17 Correspondent addess line 3
B18 Correspondent address line 4
107
DDF
B19 Payment Priority
Supplier information:
400 Supplier code
401 Supplier name
402 Address line 1
403 Address line 2
404 Address line 3
405 Reference
406 Category
407 Telephon number
408 Telex number
409 Telefax number
410 Customer code
411 Way of payment
414 Bank Account number
415 Bank office
416 SWIFT Address
417 Country code
418 Invoicing company
419 Interest late payment
420 Accounting string
424 Tax code
425 Currency code
426 Language code
427 Terms of payment
428 Terms of delivery
429 Delivery way
430 Balance
431 Purchase previous year
432 Purchase YTD
433 Purchase period
434 Last invoice date
435 Last payment date
436 Internal note 1
437 Internal note 2
439 Scala customer code
440 Alpha search key
441 Zip code
442 Default nominal ledger account
443 Payment block
108
DDF
444 Purchase next YTD

445 Purchase next period
446 Import supplier code (0-9)
447 Fiscal code
448 Bank code
449 Type of organisation (0-9)
450 Include in tax reports (0/1)
451 Deduction of tax (0/1)
452 Address line 4
453 Cash method on Sales Tax Reports (0/1)
454 Delivery address number (EDI)
455 Tax code 1 [0-99]
456 Automatic Accounting code
457 Application code 3
458 Withholding tax rate
459 Complete name
460 Investment Fee %
461 1099-Reporting (0/1)
462 1099-Reporting code
463 ABC code
464 Payment in advance
465 Lock supplier for orders (0/1)
590
|
599 Accounting Dimensions (from Supplier file)
Invoice information:
600 Supplier code
601 Invoice number
602 Transaction number
603 Invoice date
604 BE date
605 Due date
606 Discount date 1
607 Discount 1 (%)
608 Discount date 2
609 Discount 2 (%)
610 Discount date 3
611 Discount 3 (%)
612 Invoice amount in the accounting currency
613 Invoice amount in the invoice currency
614 Currency code
615 Sales tax amount
616 Accounting string
617 Invoice transaction number
109
DDF
618 Invoice BE date

619 Supplier bank code (only first 2 characters are used)
620 Way of payment
621 Payment block (0/1)
622 Authorisation code 1
623 Comment text
624 Latest payment date
625 Paid amount in the accounting currency
626 Paid amount in the invoice currency
627 Payment sent (0/1)
629 Storno invoice (0/1)
631 Recurring Invoice Updated (0/1)
632 Order number
633 Invoice transaction date
635 DTA sent amount
636 Recurring invoices (0/1)
637 State bank code
638 Preliminary booking (0/1)
640 Original company code
641 Clearing nominal Ledger account
643 Currency Contract (0/1)
644 Fixed exchange rate
645 Contract number
646 Withholding tax code
647 Payment authorisation (0/1)
648 Withholding tax
649 Tax code (0-99)
650 Authorisation code 2
651 1099 tax code
652 1099 amount
653 Repeat interval
654 Repeat start date
655 Repeat stop date
656 Repeat amount
657 Repeat percentage
658 Withholding tax percentage
690
|
699 Accounting Dimensions (from Sales Ledger file)
Other DDF Codes:

01 Supplier code
110
DDF
02 Supplier name
03 Address 1
04 Address 2
05 Address 3
06 Reference by supplier
07 Remark 1
08 Remark 2
09 Our code by supplier
10 City/Town
11 Signature 1
12 Signature 2
13 Payment number
14 Payment date (DD/MM/YY)
15 System date (DD/MM/YY)
16 Address 4
20 Invoice number
22 Invoice date
23 Amount paid
24 Discount amount
26 Commentary text
30 Post Giro account
31 BLZ
33 Bank office
44 SWIFT address
45 Tax code
46 Fiscal code
47 VAT amount
48 Effective partial VAT
49 Payment priority
50 Invoice amount without Withholding tax in the accounting currency
51 Withholding tax in the accounting currency
52 Invoice amount without Withholding tax in the original currency
53 Withholding tax in the original currency
54 Invoice currency
55 Invoice amount in the original currency
56 Invoice currency
58 Invoice VAT amount
60 System date (YYYMMDD)
111
DDF
85 Company cCode
86 Company name
87 Reference
88 Address 1
89 Address 2
90 Address 3
91 Fiscal code
92 Telephone number
93 Telefax number
94 Telex number
96 Bank account
97 Bank name
98 Remark 1
99 Remark 2
112
COUNTRY SPECIFIC UTILITIES
Country Specific Utilities

US/Canada
State and ZIP Codes for International Locations (#24941)
The state code IT and the ZIP code 00000 should be used for international locations (out of the US
and Canada); the tax rates will be zeros, but the system will write all transactions to the Taxware
Audit File. For more information, see the TaxWare International documentation.
ZIP Code Length for Companies with No Taxware Installed (SP08)

• Zip Code
For companies with no Taxware International software packages installed, up-to-10-digit ZIP
code can be entered.
ZIP Code Length Extension for Companies with Taxware Installed (SP10)
(#30453)
• Zip Code
For companies with Taxware International software packages installed, the 5-digit ZIP code
can be extended up to 10 digits.
Hungary
Purchase VAT Reports (SP11) (#30343)
Search path:
Reports/Statistics – VAT Report Suppliers – Purchase Tax Report/Invoice
To be able to use the Hungarian VAT legal requirements in VAT reports, the respective country
code must have been set up.
2. The additional selection criteria for the purchase VAT reports (Hungarian VAT) are as follows:
• Use tabled summary section
y Use new style summary section (per current financial year).
n Use old style summary section (per VAT code).
• Amounts to display
1 VAT amount will be displayed.
2 BASIS amount will be displayed.
3 GROSS amount (BASIS+VAT) will be displayed.
• Use invoice date
y For the summary section, the invoice date will be used as a selection
criterion.
n For the summary section, the BE date will be used as a selection criterion.
• Summary only for particular VAT code
y Show summary only for a particular VAT code.
113
n Show summary for all VAT codes.

• VAT code for summary
Select VAT code to be displayed in the summary section (use standard Scala viewing options).
This field is available only if the previous field is set to “yes”.
Example of a Purchase Tax Report (Hungarian legal requirements)

Scala 5.1 * * PURCHASE TAX REPORT/TRANSACTION * * 22-02-00 14:57:43 Page 1
PERIOD 00-00-00 -- 99-99-99
COMPANY 31 FIN.YEAR 00===============================================================================/Scala/PL0174/5
REFER.NO.- SUPP CODE TC % REM- BASIS DISCOUNTS NET BASIS PAY.DATE
INV.DATE TRANS.D. PURCH TAX INVOICE TOTAL AMOUNT PAID
======================================++++++++++++++================================================================
01. month
445935 LOC 01 10.00 900.00 0.00 900.00 20-02-99
01-01-99 01-01-99 100.00 1000.00 1000.00
445936 LOC 01 10.00 720.00 0.00 720.00 15-01-99
10-01-99 10-01-99 80.00 800.00 800.00
445951 LOC2 02 20.00 720.00 0.00 720.00 20-01-99
12-01-99 12-01-99 180.00 900.00 900.00
445937 LOC 01 10.00 540.00 0.00 540.00 20-01-99
19-01-99 19-01-99 60.00 600.00 600.00
445938 LOC 01 10.00 540.00- 0.00 540.00- 20-01-99
20-01-99 20-01-99 60.00- 600.00- 600.00-
445952 LOC2 01 10.00 900.00 0.00 900.00 19-03-99
22-01-99 22-01-99 100.00 1000.00 1000.00
445939 LOC 01 10.00 1800.00 0.00 1800.00 19-03-99
27-01-99 27-01-99 200.00 2000.00 2000.00
-------------------------> MONTHLY TOTAL : 5040.00 0.00 5040.00

660.00 5700.00
TOTAL PAID BEFORE THE 20th OF THE NEXT MONTH: 900.00
02. month
445940 LOC 01 10.00 4500.00 0.00 4500.00 20-05-99
09-02-99 09-02-99 500.00 5000.00 5000.00
445941 LOC 01 10.00 810.00 0.00 810.00 19-03-99
20-02-99 20-02-99 90.00 900.00 900.00
445958 LOC2 00 0.00 900.00 0.00 900.00
21-02-99 21-02-99 0.00 900.00
-------------------------> MONTHLY TOTAL : 6210.00 0.00 6210.00

590.00 6800.00
03. month
445944 LOC 01 10.00 630.00- 0.00 630.00- 25-04-99
12-03-99 12-03-99 70.00- 700.00- 700.00-
445942 LOC 01 10.00 810.00- 0.00 810.00- 19-03-99
19-03-99 19-03-99 90.00- 900.00- 900.00-
445943 LOC 01 10.00 5400.00 0.00 5400.00 21-05-99
19-03-99 19-03-99 600.00 6000.00 6000.00
445953 LOC2 02 20.00 480.00 0.00 480.00 20-05-99
28-03-99 28-03-99 120.00 600.00 600.00
-------------------------> MONTHLY TOTAL : 4440.00 0.00 4440.00

560.00 5000.00
04. month
445955 VAT2 02 20.00 800.00 0.00 800.00
15-04-99 15-04-99 200.00 1000.00
445956 TMP 01 10.00 900.00 0.00 900.00 25-04-99
15-04-99 15-04-99 100.00 1000.00 1000.00
445945 LOC 01 10.00 630.00 0.00 630.00 25-04-99
20-04-99 20-04-99 70.00 700.00 700.00
445956 TMP 01 10.00 10.00 100.00- 90.00- 25-04-99
15-04-99 25-04-99 10.00- 100.00- 1000.00
445957 LOC2 01 10.00 1800.00 0.00 1800.00 17-04-00
25-04-99 25-04-99 200.00 2000.00 2000.00
445959 LOC2 01 10.00 450.00 0.00 450.00 19-05-99
20-01-99 25-04-99 50.00 500.00 500.00
-------------------------> MONTHLY TOTAL : 4590.00 100.00- 4490.00

610.00 5100.00
05. month
445947 VAT2 02 20.00 7200.00 0.00 7200.00 18-01-00
19-05-99 19-05-99 1800.00 9000.00 9000.00
-------------------------> MONTHLY TOTAL : 7200.00 0.00 7200.00

1800.00 9000.00
12. month
445954 LOC2 01 10.00 1080.00 0.00 1080.00 20-01-00
01-12-99 01-12-99 120.00 1200.00 1200.00
445946 VAT2 02 20.00 5740.00 700.00- 5040.00 29-12-99
20-12-99 20-12-99 1260.00 6300.00 7000.00
-------------------------> MONTHLY TOTAL : 6820.00 700.00- 6120.00

1380.00 7500.00
01. month
445948 VAT2 02 20.00 400.00 0.00 400.00 19-04-00
03-01-00 03-01-00 100.00 500.00 500.00
445949 VAT2 02 20.00 240.00- 0.00 240.00- 01-02-00
20-01-00 20-01-00 60.00- 300.00- 300.00-
445950 VAT2 02 20.00 240.00 0.00 240.00 01-02-00
31-01-00 31-01-00 60.00 300.00 300.00
-------------------------> MONTHLY TOTAL : 400.00 0.00 400.00

100.00 500.00
04. month
114
445948 VAT2 02 20.00 10.00 50.00- 40.00- 19-04-00

03-01-00 19-04-00 10.00- 50.00- 500.00
-------------------------> MONTHLY TOTAL : 10.00 50.00- 40.00-

10.00- 50.00-
--------------------------------------------------------------------------------------------------------------------
TOTAL 34710.00 850.00- 33860.00
5690.00 39550.00
Scala 5.1 * * PURCHASE TAX REPORT/TRANSACTION * * 22-02-00 14:57:44 Page 2

FINANCIAL YEAR 00. SUMMARY
COMPANY 31 FIN.YEAR 00===============================================================================/Scala/PL0174/5
BE-DATE: ----------- JANUARY ------------- APRIL -------------- JULY ----------- OCTOBER
---------- FEBRUARY --------------- MAY ------------ AUGUST ---------- NOVEMBER
PAY. DATE: ------------- MARCH -------------- JUNE --------- SEPTEMBER ---------- DECEMBER
====================================================================================================================
JANUARY 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
---------------------------------------------------------------------------------------------------------------
FEBRUARY 0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
---------------------------------------------------------------------------------------------------------------
MARCH 90.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
---------------------------------------------------------------------------------------------------------------
T O T A L 90.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
0.00 0.00 0.00 0.00
Parameters :
Trans. date : 00-00-00 -- 99-99-99

Invoice date : 00-00-00 -- 99-99-99
Supplier code : LOC 0 -- LOC 99
Reference num. : -- 00000
VAT code : 00 -- 99
* * * * * * * * * * * * E N D O F R E P O R T * * * * * * * * * * * *
UK, Belgium
Calculating VAT (SP11) (#28235)
Sales Ledger
Search path:
Invoices/Journal – Enter Supplier Invoices/Credit Notes
Purchase Ledger
Search path:
Invoices/Journal – Enter Supplier Invoices
or
Invoices/Journal – Enter Credit Notes
• VAT Amount
The standard VAT calculation in the Sales Ledger and Purchase Ledger modules is as follows:
VAT is calculated as the respective percentage of the total invoice amount (Amount field); a cash
discount (if any) applies only at the time of payment.
For companies set in Scala with the country code of the UK (44) and Belgium (32):
The company file Cash Discount on Gross Amount parameter must be set to no.
VAT is calculated as the respective percentage of the total invoice amount (Amount field) reduced
by the cash discount applied (if any).
Example:
Total Invoice Amount (net, excluding VAT): 100
Cash Discount: 20%
VAT rate: 10%
For countries other than UK and Belgium:
VAT Amount: 10 (100 * 10%)
115
For UK and Belgium:

VAT Amount: 8 ((100 –20)* 10%)
Germany
German Payment Method in Sales Ledger and Purchase Ledger Modules
(SP11)
Sales Ledger
Payments in Euro for German payment methods are available.
Search path:
Sales Ledger/Purchase Ledger – Payments/Journal/Cash Flow – Automatic Payments – Print Payment
Notices
Update is possible after creating a transfer file and printing a covering letter.
Printing Discounts
• Collection Pay
y Discounts are printed only for customers with one invoice.
Printing the suppliers’ payments avis is recommended.
n Discounts are printed after each customer invoice
Negative values in the transfer file are not allowed.
Israel
Extended Tax Support (SP13) (#34776)
With the extended tax functionality, the withholding tax for Purchase Ledger invoices with withholding
tax information is calculated when entering payments based on the withholding tax code specified for
the invoice supplier in the supplier file. The withholding tax amount is posted to the withholding tax
account as specified in the Automatic Accounting Schedule, position 28.
In automatic payments routines, for Israeli extended tax functionality, use the automatic payment
methods I1 – Israeli Bank Company Disk and I2 – Israeli Cheque Printing. When printing cheques, use
the DDF codes 30 and 47 for the withholding tax amount and percentage respectively.
Moreover, with the extended tax functionality, the Israeli specific tax reports are available.
The functionality features are available once the functionality is set up (see below).
Setting Up
1. Activate the SEM-01 Extended Tax Support feature in the feature activation setup.
2. Define the withholding tax codes to be linked with the suppliers.
3. Define the withholding tax district codes used as a selection criterion for the Withholding Tax
Summary report.
4. Specify the withholding tax codes and the withholding tax district codes for suppliers; the
withholding tax of the specified code will be automatically calculated when entering payments for
the supplier’s invoices with withholding tax to be calculated (that is, in the invoice entering
routine, W.hold Tax parameter set to yes).
116
Feature Activation
Search path:
System Utilities/Office Autom. – Miscellaneous – Feature Activation set-up – Edit Feature set-up
To activate the Israeli extended tax functionality, select the SEM-01 Extended Tax Support
checkbox.
Withholding Tax Codes

Search path:
Purchase Ledger – Miscellaneous – Country Specific Utilities – Extended Tax Support – WH
TAX/District Codes – Withholding Tax Codes
• Withholding Tax Code
Enter a new code for the withholding tax (up to 4 alphanumeric characters) or the existing one for
the withholding tax you want to adjust.
To delete the withholding tax district code, enter a minus (–), the code of the withholding tax
to be deleted, confirm deletion and press Esc.
? (withholding tax codes)
• Text
Enter the withholding tax description.
• % of total amount
Enter the percentage of the withholding tax.
To specify the withholding tax as a fixed amount, leave this field blank and enter the respective
amount in the next field.
• Fixed amount
Enter the withholding tax fixed amount.
Used if the withholding tax percentage (previous field) is not specified.
• Deducted only if between
Enter the date range when this withholding tax applies.
• Nominal Account
? ?. (accounts in alphabetical order)
! !. (accounts with current balances)
# #. (accounts with descriptions)
• Withholding Tax
Enter the code of another withholding tax that will be used if the invoice date is not within the
specified date range above.
Withholding Tax District Codes

Search path:
Purchase Ledger – Miscellaneous – Country Specific Utilities – Extended Tax Support – WH
TAX/District Codes – Tax District Codes
• Tax District Code
Enter a new district code for the withholding tax (up to 8 alphanumeric characters) or the existing
one for the withholding tax district you want to adjust.
To delete the withholding tax district code, enter a minus (–), the code of the withholding tax
district to be deleted, confirm deletion and press Esc.
? (district codes)
117
• Text
Enter the district description.
Supplier’s Withholding Tax

Search path:
Purchase Ledger – Supplier File – Enter Suppliers, Codes option
• With-holding tax code
Enter the code of the withholding tax to be used for this supplier’s invoices.
• Tax District Code
Enter the code of the withholding tax district for this supplier.
? (district codes)
Reports
Search path:
Purchase Ledger – Miscellaneous – Country Specific Utilities – Extended Tax Support
The following specific withholding tax reports are available:
• Yearly Withholding Tax Report
• Monthly Tax Report
• Withholding Tax Report
• Withholding Tax Summary
• Tax Report to File specified in the report selection criteria
Yearly Withholding Tax Report

LAN file: pl0902
Selection criteria:
• Payment Date range
• Supplier Code range
Monthly Tax Report

LAN file: pl0903
Selection criteria:
• Book Entry Date range
The list of the suppliers’ invoices according to the specified selection criteria is displayed on screen.
To select/deselect invoices to be included in the report, press Enter.
The invoices to be included in the report are marked with an asterisk (*) in the INCL column.
To start report printing, press Esc.
Withholding Tax Report

LAN file: pl0904
Selection criteria:
118
The list of the suppliers’ invoices according to the specified selection criteria is displayed on screen.
To select/deselect invoices to be included in the report, press Enter.
The invoices to be included in the report are marked with an asterisk (*) in the INCL column.
To start report printing, press Esc.
Withholding Tax Summary

LAN file: pl0906
Selection criteria:
• Tax District range
• Excluded Withholding Tax Code
Tax Report to File

Selection criteria:
• Invoice Date range
• Output File Name including the full path (for example, a:\taxreport)
Output file structure for all lines except the last one:
Field Position Length Value

Company tax registration number 1 9
10 2 96
Financial year 12 2
Supplier tax registration number 18 9
Supplier name 41 22
Supplier address line 1 63 21
Supplier address line 2 84 13
Paid invoice amount 97 11
Withholding tax amount 108 9
Withholding tax district code 135 8
Supplier category description 147 14
End of record 215 2 60
Output file structure for the last line:
Field Position Length Value

Company tax registration number 1 9
10 2 96
Financial year 12 2
Company PostGiro number 22 9
119
Total paid invoice amount 102 12

Total withholding tax amount 114 10
End of record 215 2 70
120
WORKING WITH SCALA
Working with Scala

Scala Automation Manager (SP10)
Scala Automation Manager is an option within Scala 5.1 that enables Scala Global Series users to
install, manage, and run VBA Projects (customisations) created with Scala 5.1 Developer. Both Scala
5.1 with the licensed Scala Automation Manager option and Scala 5.1 Developer contain VBA.
Scala Automation Manager is targeted for those clients who wish to extend their Scala functionality
without changing the core system.
For detailed system requirements, see the Scala 5.1 Installation and Operation Instructions.
Warning!
Projects created within one Scala 5.1 Developer installation cannot be used in other installations
of Scala 5.1 Developer. However, if you have both Scala 5.1 and Scala 5.1 Developer (licensed for
the same client), you are able to share VBA projects between these two products without any
restrictions. To this end, there is a mechanism of VBA projects licensing with Scala E-Repository –
the Scala library of VBA projects. Licensing of individual customisations supports controlled
deployment of modifications and also provides up-to-date information about the complete supply of
available customisations worldwide.
Features
Scala Automation Manager allows to:
• Organise and use VBA Projects
You can import, use or delete Project Items in the Project Organiser.
• Use Macros
You can run macros stored in your projects.
(SP13)
• Access Scala e-Repository through Scala menu links
You can access VBA projects stored in Scala e-Repository.
Organising Projects
General
Customisations developed for Scala 5.1 with Scala 5.1 Developer are stored in VBA Project files with
the extension .prj.
Import of a VBA project to the Scala system also requires a special Project License Code (PLC). PLC
is provided as a file (separate for each VBA project) with the same name as a VBA Project file and
extension .plc; PLC is Scala installation specific.
Refer to Scala Installation and Operation Instructions for information on getting PLC for a VBA
project.
Project Access Levels

Scala Automation Manager allows you to import, use, or delete projects in compliance with the
relevant project access level. The following access levels are supported:
• Scala (A VBA project can be used in all Scala companies by any user for all financial years)
• Company (A VBA project can be used by any user in the specified Scala company)
121
WORKING WITH SCALA
• Financial year (A VBA project can be used for the specified financial year)
• Group (A VBA project can be used by the specified user group)
• User (A VBA project can be used by the specified user)
• Private (A VBA project can be used by the user who imported project)
All SYS users from all Scala companies have equal rights. Any SYS user has the highest
project access level and can manage security levels for the other regular (non-SYS) users.
Regular users are not allowed to modify project access levels.
Importing Projects
1. Before importing a VBA project, copy both the project file (for example, Scala VBA
project_Example.prj) and the PLC file (for example, Scala VBA project_Example.plc) to the
VBAProjects directory; the VBAProjects directory is in the root of your Scala installation.
1. To be able to import a project with any level, log on as the SYS user.
Other regular users are allowed to import only the projects with the access level Private.
2. Then, to import a project, select the Organise Project option:
Search path:
Tools - Visual Basic for Application - Organise Project
Disabled menu items are available only in Scala 5.1 with Developer license.
If there are no projects, the Organise project window is blank. If projects havebeen created, this
window contains a list of existing project.
4. Right click the window to view the context menu and select the Import Project option.
(SP13)
The Scala e-Repository link provides you with access to the web-based Scala
Repository of VBA projects.
5. On the next window, select the VBA project you want to import (for example,
Scala VBA project_Example.prj) and click Open to complete the import procedure.
Adjusting Project Properties

Scala Automation Manager allows you to adjust Project properties when completing the import
procedure described above. However, only SYS users can change the project’s properties. For any SYS
user, the respective window pops up automatically providing you with access to the Levels tab where
you can adjust Project properties. For any other (non-SYS) user, the Levels tab is invisible.
In Windows 9x operating system, you will not see the Security tab either.
The Security, VBA, VBA 2, and Description tabs are for information only.
On the Levels tag, a SYS user can set any access level for a Project (from Private to Scala) by
selecting the respective check box. Click OK to confirm the settings.
122
WORKING WITH SCALA
Other users can call Project Properties from the Organise Project window:
Right click the Project item and select Properties from the context menu of the project and click OK.
Executing Projects
Once the project has been imported, it can be executed. No special execution activities are required.
The instruction when and how a VBA project will be executed is stored in the project. Additional
information might be provided with the VBA project.
Deleting Projects
To delete a project of any levels, log on in Scala as the SYS user. Other users can delete only the
projects imported by them; that is, the projects with the access level Private.
Search path:
Tools - Visual Basic for Application - Organise Project - Delete
Using Macros
Scala Automation Manager allows you to run macros that have been preliminary created in the
projects. You can start a Macro from the macro menu option.
Search path:
Tools - Visual Basic for Application – Macros
Enable Events option allows to use Scala VBA Events in Macros. You can enable or disable Events
at discretion. See the Scala 5.1 Developer’s Guide for description of Scala VBA Events.
A project can include several macros, and you can use several projects simultaneously. Thus, when
starting macros, the system allows you to select the macro to be executed from the list of available
macros.
123
WORKING WITH SCALA
Macros can be started by clicking the relevant buttons on the Tool Bar Menu provided that the project
contains the appropriate buttons or they have been created by the user. (Refer to the Scala 5.1 Working
with Scala for Windows User’s Guide for details on creating buttons on the Tool Bar Menu).
Scala e-Repository (SP13)

To access VBA projects stored in Scala e-Repository available for common use, you have two options:
After having been logged on to a Scala Company:
• in the Scala Tools menu, select Scala e-Repository
• in the Tools – Visual Basic for Applications – Organise Projects menu, select Scala e-
Repository in the context-sensitive menu on mouse-right-button click.
To proceed with Scala e-Repository loading, in the ScalaWeb message box, select yes; your existing
Scala license and system configuration information will be sent to the Scala e-Repository web site.
Deleting Customised Button from Scala Toolbar (#29684)

To delete a customised button from Scala Toolbar, do the following:
1. Press and hold Alt.
2. In Scala Toolbar, select a button you want to delete and drag it out.
Scala Menu External Links (SP13)

From the Scala Tools menu, you have access to:
• Scala e-Repository web site – the library of VBA projects that can be integrated into the client
Scala system to customise Scala behaviour
To access Scala e-Repository, in the ScalaWeb message box, select yes (your existing Scala
license and system configuration information will be sent to the Scala e-Repository web site).
For users having license for Scala 5.1 with Automation Manager option or Scala 5.1
Developer, the Scala e-Repository web site is also available from the Tools – Visual Basic for
Applications – Organise Projects menu, Scala e-Repository in the context-sensitive menu on
mouse-right-button click.
• Scala Release Library located on the Scala Clients web site (www.scala-clients.com ) – the
official site for Scala clients including Release Library that contains downloads of latest Scala
Releases, Service Packs, and Hot Fixes
To access Scala Release Library, in the ScalaWeb message box, select yes (your existing Scala
license and system configuration information will be sent to the Scala Clients web site); log on to
the Scala Clients site and under Download, select the Download link.
124
WORKING WITH SCALA
By clicking on the corresponding button you are accepting Scala's privacy policy (insert
hyperlink) and agreeing to the transmission of your licence and Scala configuration data.
Scala uses this information to decide whether you are authorised to access Scala's web-based
Release Library and to configure the options to your specific needs. If you do not consent to
the transmission of this information, do not wish your access to be logged or your corporate
policy prohibits such activity then please contact your local Scala representative who can
provide all the items from the release library via an alternative delivery mechanism.
125
TROUBLESHOOTING
Troubleshooting
Troubleshooting Blocking Sessions when Generating
Long Reports (SP13) (#30342)
The feature is implemented for Sales Ledger Balance Reports (Sales Ledger – Reports/Statistics –
Balance Report) and Sales/Invoicing Statistics (Statistics – Customer/Stock Statistics –
Sales/Invoicing Statistics).
For other reports, the feature can be implemented upon request.
To avoid blocking sessions on SQL Server computers when generating long Scala reports (based
on huge databases), do the following:
• start SQL Server Agent (including Qgovernor)
• in system Registry, add a new Qgoverner string value to the required location:
• for all local computer users:
HKEY_LOCAL_MACHINE\Software\Scala Business Solutions
NV\Scala\5.1\
• for the current user:
HKEY_CURRENT_USER \Software\Scala Business Solutions
NV\Scala\5.1\
If there are several Scala systems installed on the workstation, select the respective Location
subtree.
To evaluate the Qgoverner value, do the following:
• run SQL Query Analyzer and create the select query from one of the huge tables:
select * from SL010100 where SL01001 between ‘CUSTOMER_001’ and
‘CUSTOMER_999’
• if the current query runs 15 minutes, and you want to split queries running more than 5
minutes, limit query selection to satisfy the time request:
‘CUSTOMER_300’
• then run:
SET QUERY_GOVERNOR_COST_LIMIT 2
Go
‘CUSTOMER_300’
Go
• If the SQL Query Analyzer produces the following error:
Server: Msg 8649, Level 17, State 1, Line 1
The query has been canceled because the estimated cost of this query (12) exceeds the
configured threshold of 2. Contact the system administrator.
Re-run the last script several times with different QUERY_GOVERNOR_COST_LIMIT
parameters unless this error disappears.
126
TROUBLESHOOTING
• Set the Qgoverner value in Scala registry to the QUERY_GOVERNOR_COST_LIMIT

parameter.
When generating long Scala queries/reports, Qgovernor captures cost from the execution plan and,
if cost exceeds the value in the Qgoverner registry key, the respective query will be split to the set
of sub-queries based on the SQL Server statistics information.
Warning!
Once the tables sizes are increased, re-evaluate the Qgoverner value; otherwise, you may get
incomplete queries/reports results.
Troubleshooting Scala Backup on MS SQL 2000 (SP13)

(#34210)
Search Path:
Backup Local Hard Disk
When backing up/restoring Scala data on MS SQL 2000, you may get the following (logged in Scala
log file) error message:
INCOMPLETE BACKUP. ONLY 0 ROWS COPIED.
This problem relates to the MS SQL 2000 issue when the SQL Server’s code page settings differ from
the Windows workstation’s regional settings.
To resolve the problem, in system Registry, add a new BackUpCodePage string value to the required
location:
• for all local computer users:
HKEY_LOCAL_MACHINE\Software\Scala Business Solutions
NV\Scala\5.1\
• for the current user:
HKEY_CURRENT_USER \Software\Scala Business Solutions
NV\Scala\5.1\
If there are several Scala systems installed on the workstation, select the respective Location
subtree.
and set its value as follows:
0 conversion of SQL Server’s data to the ANSI/Windows code page when backing up; and,
vice versa, when restoring
1 conversion of SQL Server’s data to the OEM code page when backing up; and, vice versa,
(default) when restoring
–1 no conversion from one code page to another
<value> conversion of SQL Server’s data to the specified code page (for example, 850) when backing
up; and, vice versa, when restoring
Warning!
This option does not work with some code page numbers (for example, 866).
Country Specific
Sorting with Japanese Regional Settings (SP13) (#30630)
On Windows with default Japanese regional options (settings) and Scala database on Pervasive
SQL Server 7 (2000), for correct sorting of data prior to SR13, rebuild all data files.
127
LIST OF NEW FEATURES AND CORRECTED BUGS
List of New Features and

Corrected Bugs
(SP01)
RTF Option (SY)
(#30032)
RTF Spool File Options (SY)
(#30603)
Changing System Date (SY)
(#23533)
Availability of the Copying Parameters option when Creating New Data Files (SY), Scala 5.0
SP26, Scala 5.1 SP07)
(SP11)
New switch for overwriting parameters when creating new data files (SY, Scala 5.1 SP11)
(#31794)
– New switch for overwriting parameters when creating new data files (SY, Scala 5.1 SP11)
(#19236)
Rebuilding Files for Btrieve and SQL databases (SY)
(SP02)
Rebuilding indexes in SQL (SY)
(SP11)
System limitations when rebuilding stock (SY, Scala 5.1,SP11)
(#31937)
– System limitations when rebuilding stock (SY, Scala 5.1,SP11)
(SP11)
(#31938)
(SP11)
(#27865)
(SP02)
Copying Automatic Accounting Schedule (SY)
(#30935)
EMU Conversion for more than one year (SY/EMU)
(#31257)
EMU simulation transactions (SY/EMU)
(#31490)
EMU printing of rounding transactions (SY/EMU)
(SP01)
Deleting Old Data after EMU Conversion (SY)
(SP01)
Information on EMU Conversion in Company File (SY)
(SP03)
Choice of Basis for VAT Calculation (SY)
(#29332)
Note on ScaUser (SY)
(#31828)
Creating Companies with Own Menus (SY)
(SP09)
User File Security (SY)
(#28461)
User File Security (SY, Scala 5.0 SP29, Scala 5.1 SP09)
(SP12)
Special Prefix to Be Used for Scala Commands (SY, Scala 5.1 SP12)
(#23806)
– Special Prefix to Be Used for Scala Commands (SY, Scala 5.1 SP12)
(#29933)
Password Troubleshooting (SY)
(SP11)
Backup/restore in Scala SQL (SY, Scala 5.1 SP11)
(SP01)
Currency System in Scala 5.1 (SY)
128
(SP04)
Currency Calculator (SY)
(SP03)
Rounding Tolerance for Invoice Closing (SY)
(SP10)
Three Decimals Option in VAT Rate (SY; Scala 5.1 SP10)
(#28688)
Three Decimals Option in VAT Rate (SY)
(SP08)
Additional Multilingual Support (SY, Scala 5.1 SP08)
(SP04)
Menu Customisation for Currency System options (SY)
(SP01)
Currency System Converter (Scala 5.0 to Scala 5.1) (SY)
(#29744)
Restricted Usage of Quotation Marks with Text Variables and Commas in Input-Output Files
(SY)
(#30601)
VAT code 00 is compulsory for the system to work properly
(SP13)
Language Dependent Tax Name (Scala 5.1 SP13)
(SP13)
Tax Rounding and Calculation Options for Customers and Suppliers (Scala 5.1 SP13)
(SP11)
Integration of Third Party Products into Scala (Scala 5.1 SP11)
(SP12)
Transferring Scala Data to Other Applications (SY, Scala 5.1 SP12)
(#33179)
– Transferring Scala Data to Other Applications (SY, Scala 5.1 SP12)
(SP13)
Changes in Scala Menu Default Settings (SY, Scala 5.1 SR13)
(SP12)
DDF formats for XML output (DDF, Scala 5.1 SP12)
(#33179)
– DDF formats for XML output (DDF, Scala 5.1 SP12)
(SP12)
(#33179)
(SP07-08)
4-Digit-Year Date Format (DDF, Scala 5.1 SP07–08)
(SP10)
New DDF date formats (DDF, Scala 5.1 SP10)
(SP12)
New DDF date format @4 (DDF, Scala 5.1 SP12)
(SP10)
Year Date Format (DDF, Scala 5.1 SP10)
(#26873)
– Year Date Format (DDF, Scala 5.1 SP10)
(SP12)
(#33179)
(#32720)
DDF Codes for Replacement Items (DDF)
(#26528)
DDF code for document number (DDF – GL)
(#26634)
DDF code for Debit and Credit Amounts in Coding Slip(DDF – GL, Scala 5.0 SP28, Scala 5.1
SP09)
(#26634)
– DDF code for Debit and Credit Amounts in Coding Slip(DDF – GL, Scala 5.0 SP28, Scala 5.1
SP09)
(#33265)
Changes and Additions in/to DDF Manual (DDF)
(SP01)
DDF Code for Invoice Currency Balance in Statement by Date (DDF – SL, Scala 5.0 SP19, Scala
5.1 SP01)
(#29167)
– DDF Code for Invoice Currency Balance in Statement by Date (DDF – SL, Scala 5.0 SP19,
Scala 5.1 SP01)
(SP11)
DDF codes for Location Information (US/Canada) (DDF – SL, Scala 5.0 SP31, Scala 5.1 SP11)
(#29206)
– DDF codes for Location Information (US/Canada) (DDF – SL, Scala 5.0 SP31, Scala 5.1
SP11)
129
(#25590)
Statement by Supplier (DDF – PL, Scala 5.1 SP07)
(SP04)
DDF Code for Gross Amount (DDF – OR, Scala 5.1 SP04)
(#31487)
– DDF Code for Gross Amount (DDF – OR, Scala 5.1 SP04)
(SP04-09)
New DDF codes in Sales Order Documents (DDF – OR, Scala 5.1 SP04–09)
(#28661)
– New DDF codes in Sales Order Documents (DDF – OR, Scala 5.1 SP04)
(SP13)
New DDF Codes in Sales Order Reports (DDF – OR, Scala 5.1 SR13)
(SP13)
DDF Code for Other Tax Amount in Invoice Line (DDF – OR, Scala 5.1 SR13)
(#34540)
– DDF Code for Other Tax Amount in Invoice Line (DDF – OR, Scala 5.1 SR13)
(SP12)
DDF Codes for Price for Internal Customer (DDF-OR, Scala 5.1 SP12)
(#29666)
– DDF Codes for Price for Internal Customer (DDF-OR, Scala 5.1 SP12)
(SP11)
DDF code for Historical Invoice Prefix (DDF – OR, Scala 5.0 SP31, Scala 5.1 SP11)
(#23793)
– DDF code for Historical Invoice Prefix (DDF – OR, Scala 5.0 SP31, Scala 5.1 SP11)
(SP12)
New DDF code for Copy No text (DDF – OR, Scala 5.1 SP12)
(#32863)
– New DDF code for Copy No text (DDF – OR, Scala 5.1 SP12)
(#32199)
– New DDF code for Copy No text (DDF – OR, Scala 5.1 SP12)
(SP10)
New DDF code for printing number of parcels in order lines (DDF – OR, Scala 5.1 SP10)
(#29824)
– New DDF code 1004 for printing number of parcels in order lines (DDF – OR, Scala 5.1
SP10)
(#22001)
– New DDF code 1005 for printing residual delivery quantity in order lines (DDF – OR, Scala
5.1 SP10)
(#29824)
– New DDF code 1004 for printing number of parcels in order lines (DDF – OR, Scala 5.1
SP10)
(#26922)
Cash Discount and VAT DDF codes for Invoice, Credit Note and History Invoice (DDF – OR,
Scala 5.1 SP08)
(SP13)
Delivery Proposal DDF Codes for Allocation Quantity (DDF – OR, Scala 5.1 SP13)
(#34112)
– Delivery Proposal DDF Codes for Allocation Quantity (DDF – OR, Scala 5.1 SP13)
(#30087)
Order Consolidation (DDF – OR)
(#28840)
Correct Example for Delivery Note (DDF – OR)
(#24309)
DDF numbers for Customer Stock Code (DDF – OR)
(#23777)
Unavailable DDF numbers in Delivery Note/History Delivery Note (DDF – OR)
(#29960)
Unavailable DDF codes in Product Label (DDF – OR)
(#26069)
Unavailable DDF numbers in Summarised Export Document (DDF – OR)
(#25341)
Changes in DDF number for OR transport documents (DDF – OR, SP06)
(#25438)
DDF codes from Stock Control for Purchase Order, Order Confirmation Reminder, Delivery
Reminder (DDF – PC, Scala 5.0 SP27, Scala 5.1 SP08)
(SP08)
Additional DDF Unit Codes for Purchase Order, Order Confirmation Reminder, Delivery
Reminder (DDF – PC, Scala 5.0 SP27, Scala 5.1 Sp08)
(#25886)
– Additional DDF Unit Codes for Purchase Order, Order Confirmation Reminder, Delivery
Reminder (DDF – PC, Scala 5.0 SP27, Scala 5.1 Sp08)
(SP11)
New DDF Code for Customer Purchase Order Number in Purchase Order, Order Confirmation
Reminder, Delivery Reminder (DDF – PC, Scala 5.0 SP31, Scala 5.1 SP11)
130
(#28846)
– New DDF Code for Customer Purchase Order Number in Purchase Order, Order Confirmation
Reminder, Delivery Reminder (DDF – PC, Scala 5.0 SP31, Scala 5.1 SP11)
(#30373)
DDF Code for Undelivered quantity (DDF – PC)
(SP09)
DDF Codes for Stock Items’ Text Lines and Extra Descriptions (DDF – PC, Scala 5.1 SP09)
(#30668)
– DDF Codes for Stock Items’ Text Lines and Extra Descriptions (DDF – PC, Scala 5.1 SP09)
(#26446)
DDF Codes for Body 3 Section in Goods Received Note (DDF – PC)
(SP11)
New DDF Codes in Goods Received Note (DDF – PC, Scala 5.1 SP11)
(#28478)
New DDF Codes in Goods Received Note (DDF – PC, Scala 5.1 SP11)
(SP13)
DDF Code for Tax Name in Invoice/Credit Note (DDF – DI, Scala 5.1 SP13)
(#34316)
– DDF Code for Tax Name in Invoice/Credit Note (DDF – DI, Scala 5.1 SP13)
(SP13)
DDF Code for Other Tax Amount in Invoice Line (DDF – DI, Scala 5.1 SR13)
(#34540)
– DDF Code for Other Tax Amount in Invoice Line (DDF – DI, Scala 5.1 SR13)
(#35095)
FloatEnd Lines with Asterisk in Invoice, Credit Note, and Invoice Proposal (DDF – PR)
(SP09)
Printing Serial Number and Extra Text in PR Invoice (DDF – PR, Scala 5.0 SP29, Scala 5.1 SP09)
(#23980)
Printing Serial Number and Extra Text in PR Invoice (DDF – PR, Scala 5.0 SP29, Scala 5.1
SP09)
(#27922)
DDF Code for Document Flag, Proforma Invoice (DDF – SM)
(#30508)
Correction of description for code 60 (DDF – SM Scala 5.1)
(SP12)
DDF Changes for Quotation and Order Confirmation (DDF – SM, Scala 5.1 SP12)
(#33685)
– DDF Changes for Quotation and Order Confirmation (DDF – SM, Scala 5.1 SP12)
(SP12)
In addition to #33685 DDF Changes for Picking Lists (DDF – SM, Scala 5.1 SP12)
(#33685)
– In addition to #33685 DDF Changes for Picking Lists (DDF – SM, Scala 5.1 SP12)
(SP10)
Printing Extra Stock Items (DDF – MPC, Scala 5.1 SP10)
(#31104)
– Printing Extra Stock Items (DDF – MPC, Scala 5.1 SP10)
(#33265)
(SP05)
Payslip DDF codes Enhancement (DDF – PA, Scala 5.0 SP24, Scala 5.1 SP05)
(#24414)
– Payslip DDF codes Enhancement (DDF – PA, Scala 5.0 SP24, Scala 5.1 SP05)
(#33265)
(SP12)
DDF Code for State Code in Purchase Order (DDF – PC, Scala 5.0 SP24, Scala 5.1 SP12)
(#32261)
– DDF Code for State Code in Purchase Order (DDF – PC, Scala 5.0 SP24, Scala 5.1 SP12)
(SP09)
DDF codes for UK Cheque Printing (DDF – PL, Scala 5.0 SP29, Scala 5.1 SP09)
(#26628)
– DDF codes for UK Cheque Printing (DDF – PL, Scala 5.0 SP29, Scala 5.1 SP09)
(#26629)
(#26630)
(SP12)
Additions to Finnish transport document (DDF – OR, Scala 5.1 SP12)
(#33124)
– Additions to Finnish transport document (DDF – OR, Scala 5.1 SP12)
(#31862)
Printing Finnish bank bar codes (DDF – OR, Scala 5.1 SP12)
(#31862)
– Printing Finnish bank bar codes (DDF – OR, Scala 5.1 SP12)
(#31862)
– Printing Finnish bank bar codes (DDF – OR, Scala 5.1 SP12)
(#24941)
State and ZIP Codes for International Locations (SL – Country Specific – US/Canada)
131
(SP08)
ZIP Code Length for North American Companies (SL – Country Specific – US/Canada, Scala 5.1
SP08)
(SP10)
ZIP Code Length Extension for North American Companies with Taxware package installed (SL,
Scala 5.1 SP10)
(#30453)
– ZIP Code Length Extension for North American Companies with Taxware package installed
(SL, Scala 5.1 SP10)
(SP11)
Hungarian VAT legal requirements in purchase VAT reports (PL, Scala 5.1 SP 11, Scala 5.0
SP31)
(#30343)
Hungarian VAT legal requirements in purchase VAT reports (PL, Scala 5.1 SP 11, Scala 5.0
SP31)
(SP11)
Calculating VAT (SL, PL, Scala 5.1 SP11)
(#28235)
– Calculating VAT (SL, PL, Scala 5.1 SP11)
(SP11)
German Payment Method in Sales and Purchase Ledger Modules (SL, PL, Scala 5.1 SP11)
(SP13)
Extended Tax Support (PL, Scala 5.1 SP13)
(#34776)
– Extended Tax Support (PL, Scala 5.1 SP13)
(SP10)
Scala Automation Manager (Scala 5.1 SP10)
(SP13)
Scala e-Repository link (Scala 5.1 SR13)
(SP13)
(SP13)
(#29684)
Deleting the Customised Button from Scala Toolbar (SFW)
(SP13)
Scala Menu External Links (SFW, Scala 5.1 SR13)
(SP13)
Troubleshooting Blocking Sessions when Generating Long Reports (Scala 5.1 SP13)
(#30342)
– Troubleshooting Blocking Sessions when Generating Long Reports (Scala 5.1 SP13)
(SP13)
Troubleshooting Scala Backup on MS SQL 2000 (Scala 5.1 SP13)
(#34210)
– Troubleshooting Scala Backup on MS SQL 2000 (Scala 5.1 SP13)
(SP13)
Sorting on Japanese Settings (Scala 5.1 SP13)
(#30630)
– Sorting on Japanese Settings (Scala 5.1 SP13)
132

Add 51 Sa

Uploaded by

Document Information

Original Title

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

Add 51 Sa

Uploaded by

Copyright:

Available Formats

Scala 5.

Publication number: EN-2003-C-0301 2

Integration of Third Party Products into Scala ________________________________________61

DDF Changes for Picking Lists ________________________________________________92

RTF Option (SP01)

RTF Spool File Options (#30032)

// Shell creation to be able to interact with the user

// Check if we have exactly 1 parameter

WSHShell.Popup("Invalid number of parameters!",0,"Printout Script",0);

// Create Word object

// Wait for printout finishing

//Quit from script

Changing System Date (#30603)

Creating New Data Files

n Create all data files for selected modules.

* To select all modules.

Statistics and Balance in Stock Item File

SC01085 Qty Period [SCUNIT]

Statistics and Balance in Stock Location File

Field No. Description of the Field

Field No. Description of the Field

SC33028 User Defined Field 5

Batch Costs File

Costs for Consolidating Currency

Costs of Transactions for Goods Return

What to do if the cost of goods in a warehouse is changed after rebuild

TEST * * STOCK TRANSACTION LIST * * 09/15/99 18:20:55 Page 1

List of Problems that CANNOT be Fixed by the Utility

Copying Automatic Accounting Schedule (SP02)

Use the routine: To copy the Automatic Accounting Schedule of the

1. Select the module to copy the Automatic Accounting Schedule from.

45. Revaluation (04) 46. Stock Received (05)

343. Stock Received (38) 344. Accr. Received (38)

EMU Data Conversion

EMU Conversion Wizard

Select the conversion utilities (menu items), one after another.

Description of Conversion Utilities

EMU Conversion Set-up Utility

Creating EMU Conversion Account Correspondence Table

Adjusting EMU Conversion Account Correspondence Table

Source Special Function codes Valid Target Special Function codes

Entering EMU Conversion Automatic Accounting Schedule

There are 6 following items in the automatic accounting schedule:

Printing EMU Conversion Account Correspondence Table

Entering/Adjusting Conversion Parameters

Conversion Rate Date : 02/09/99

Tolerance for Transaction : 0.10

Source Currency Code FA : 00 FIM

Enter/Adjust Convert Payroll Setup

EMU Conversion of Monetary Fields

Balances before Conversion Balance after

Materials 100 3 33.33

4. Enter the missing accounts back into the Chart of Accounts.

Update Chart of Accounts

Source Account Target Account

Source Account Target Account

1. Account 1. Account 1. Account

Convert Fixed Assets Module

Convert Purchase Invoices

Convert Sales Invoices

Convert Sales Orders

Convert Purchase Orders

Sign off Conversion for a Year