The iScala 2.2 SR1 Products package includes: The iScala 2.2 SR1 package can be used for the following solutions: Release Number: PRD-S22-083 Release Date: 12 May 2004 iScala 2.2 SR1 Products can be installed as a new system, or as an upgrade to your current Scala 5.1 SR13 (SP15), iScala 2.1, and
iScala 2.2 Installations.
 top | The purpose of this section is to describe the supported and required software for iScala 2.2 SR1. Scala Business Solutions N.V. (SBS) reserves the right to change the requirements listed in the present document to comply with
changes in technology or the discontinuation of support from required software by copyright owners. If a software vendor decides to
discontinue one of the products listed as a supported software by SBS, the software is automatically discontinued as an SBS supported
system. Software support is discontinued on the same date as the software vendor discontinues standard support for their standard retail
product. NoteAll software listed in the Sofware Requirements section of the present document has been tested for compatibility with iScala
2.2 SR1 Products in English only. Only localisations for which English is not explicitely stated in the present document, and that are
listed as supported languages, are accepted. |
top | The following server operating systems are supported: Microsoft Windows 2000 Server (SP4 or above, unless otherwise stated when a new service pack or hotfix is
released) Microsoft Windows 2000 Advanced Server (SP4 or above, unless otherwise stated when a new service pack or hotfix is
released) Microsoft Windows Server 2003 Standard Edition Microsoft Windows Server 2003 Enterprise Edition (32-bit version)
The following virtual machine software can be used to run the supported server operating systems: NoteA distributed SQL Server location is supported for company databases, as well as for the system database and for system
services. Only one installation of iScala 2.2 SR1 administration services is supported per server. The following program must be installed on the server: Database Management Systems (DBMS)The following database management systems are supported: Microsoft SQL Server 2000 (SP3 or above, unless otherwise stated when a new service pack or hotfix is released) Microsoft SQL Server 2000 Desktop Engine (SP3 or above, unless otherwise stated when a new service pack or hotfix is
released) Microsoft SQL Server 2000 Analysis Services (English version with the latest available service pack. Optional for
iScala OLAP)
NoteThe iScala Small Business Server can only be installed on a machine with Microsoft SQL Server 2000 Desktop Engine.
|
|
top | Additional requirements for General For remote operations, the following server operating systems are supported: Microsoft Windows 2000 Server with Terminal Services Microsoft Windows 2000 Advanced Server with Terminal Services Microsoft Windows Server 2003 Standard Edition with Terminal Services Microsoft Windows Server 2003 Enterprise Edition with Terminal Services Citrix MetaFrame 1.8 for Windows 2000 Servers (English version only) Citrix Metaframe XP for Windows (XPs, XPa, XPe) (English version only)
If Unicode is not licensed, the default regional settings on the server for remote operations must be set to the same code
page as the ANSI code page of the database. (This limitation is not applicable if a Unicode license is available.) Workstation Operating SystemsThe following workstation operating systems are supported: Microsoft Windows 2000 Professional (SP4 or above, unless otherwise stated when a new service pack or hotfix is
released) Microsoft Windows XP Professional (SP1 or above, unless otherwise stated when a new service pack or hotfix is
released)
The following virtual machine software can be used to run the supported workstation operating systems: Client software for iScala Windows Solution cannot be installed on Windows 9x and Windows Millennium workstations. Required Workstation SoftwareThe following software must be installed on the workstation: |
|
top | Windows Solution for Web ServicesAdditional requirements for General The following programs must be additionally installed: Microsoft Internet Information Services (IIS) 5.1 or higher (Common files and WWW Server are required, SMTP and FTP
are optional) Microsoft COM+ 1.5 or above Microsoft MSXML Engine 4.0 (SP1 or above, unless otherwise stated when a new service pack is released)
Required Workstation SoftwareAdditional requirements for General The following software must be installed on the workstation:
Microsoft Internet Explorer 6.0 (SP1 or above, unless otherwise stated when a new service pack is released). Typical
set of components. Microsoft MSXML Engine 4.0 (SP1 or above, unless otherwise stated when a new service pack is released)
|
|
top | Additional requirements for General The following programs must be additionally installed: Microsoft Internet Information Server (IIS) 5.1 (or above, unless otherwise stated when a new service pack is
released) Microsoft COM+ 1.5 or above Microsoft MSXML Engine 4.0 (SP1 or above, unless otherwise stated when a new service pack is released)
Supported Workstation SoftwareOne of the following software components must be installed on the workstation: |
|
top | Additional requirements for General The following programs must be additionally installed: Microsoft Internet Information Server (IIS) 5.1 (or above, unless otherwise stated when a new service pack is
released) Microsoft COM+ 1.5 or above Microsoft MSXML Engine 4.0 (SP1 or above, unless otherwise stated when a new service pack is released) Microsoft Sharepoint Portal Server 2001 (SP1 or above, unless otherwise stated when a new service pack is released)
(English version only) or Microsoft SQL Dashboard 3.0 (English version only).
Required Workstation SoftwareThe following software must be installed on the workstation: |
|
top | Additional requirements for General The following programs must be additionally installed: Microsoft Internet Information Services (IIS) 5.1 or higher (Common files and WWW Server are required, SMTP and FTP
are optional) Microsoft Message Queuing Services (MSMQ) 2.0 (optional) IBM MQ Series Services 5.1 (or above) (optional) (English version only) Microsoft BizTalk Server 2002 (optional) (English version only)
|
|
|
top | The purpose of this section is to describe the recommended hardware for iScala 2.2 SR1. Any configuration that does not meet the hardware requirements outlined below is not supported unless approved by a local Scala
representative. For more information about hardware requirements or to get customised requirements for the size of your installation, please
contact your local Scala representative. NoteAll the requirements are created with the assumption that iScala is the only application running on the computer. More powerful
hardware is required to run other applications on the same computer. Hardware requirements are subject to change due to changes in the product and technology. |
top | We recommend having a dedicated server for the installation of DBMS and iScala 2.2 SR1. Recommended configuration for communities of up to 50 users: Dual Pentium III - 1 GHz or faster processor system (Dual Xeon - 3 GHz is preferable but not mandatory, at the time of
the current release: Spring 2004) 1024 MB RAM or more (4GB is preferable but not mandatory) Hardware RAID-1 for OS, DBMS and iScala binaries (2GB for the DBMS and iScala installation) Hardware RAID-5 with 6 spindles for iScala databases (at least 1GB for the initial installation) 100Mb network connection.
|
|
top | Additional requirements for General Server Hardware RequirementsThe same as General Workstation Hardware RequirementsRecommended configuration: Pentium III - 600 MHz or faster processor (Pentium IV - 2 GHz is preferable but not mandatory, at the time of the
current release: Spring 2004). 128MB RAM (256MB RAM is preferable). Fast video card in 1024x768 resolution hi-colour 100 Mb switched network connection
When using VMware virtual machine software, the following additional hardware requirements apply: Hardware Requirements for Remote OperationsWe strongly recommend having a dedicated server for remote operations. Recommended configuration for communities of up to 20 users: Quad Pentium III - 600 MHz or faster processor system (Quad Xeon - 3 GHz is preferable but not mandatory, at the time
of the current release: Spring 2004) 256MB RAM and 64MB RAM per concurrent user Hardware RAID-1 for OS and iScala binaries (2GB for the iScala installation) 100Mb network connection
|
|
top | Windows Solution for Web ServicesThe Server Hardware Requirements are the same as General.
WarningPlease ensure that the Windows Solution for Web Services works with the same database as the Windows Solution, acting as an
additional virtual user. The processing of XML messages, due to the multithreading capabilities of this product, may result in an additional load on
the Server, equivalent to a number of concurrent users working with the system. This number can vary from 1 to 50 depending on the message
load. |
|
top | The Server Hardware Requirements are the same as General.
WarningPlease ensure that the Web Solution works with the same database as the Windows Solution, acting as an additional virtual
user. The processing of XML messages, due to the multithreading capabilities of this product, may result in an additional load on
the Server, equivalent to a number of concurrent users working with the system. This number can vary from 1 to 50 depending on the message
load. |
|
top | The Server Hardware Requirements are the same as General.
WarningPlease ensure that the Portal Solution works with the same database as the Windows Solution, acting as an additional virtual
user. The processing of XML messages, due to the multithreading capabilities of this product, may result in an additional load on
the Server, equivalent to a number of concurrent users working with the system. This number can vary from 1 to 50 depending on the message
load. |
|
top | The Server Hardware Requirements are the same as General. WarningPlease ensure that the Connectivity Solution works with the same database as the Windows Solution, acting as an additional
virtual user. The processing of XML messages, due to the multithreading capabilities of this product, may result in an additional load on
the Server, equivalent to a number of concurrent users working with the system. This number can vary from 1 to 50 depending on the message
load. |
|
|
top | iScala 2.2 SR1 supports the following languages:
|
|
top | The purpose of this document is to outline the new features of iScala 2.2 SR1 Products compared to iScala 2.2 Commercial Release
Products. Refer to the online help system for any iScala 2.2 SR1 Product for more information. You can access the online help system by
pressing F1 from the Windows client after installation, and address the relevant topics within the iScala Documentation Kit (see
iScala.chm). Differences between iScala 2.2 Commercial Release Products and iScala 2.2 SR1 Products are described in the What's
new section of the online help system. |
top | Customer Relationship ManagementSales Process Integration Users can work with Leads and Opportunities by using Microsoft® CRM Environment. While entering an
Opportunity, users can assign various items to an Opportunity (for example, products, services, time activities, cost activities). The
system then sends a request to iScala, where price, currency, and discount calculations are performed according to the iScala settings, and
this information is sent back to update an Opportunity. Standard Scala Connectivity Manager interfaces are implemented on the CRM server side. These interfaces are called from the
Customer Request and
Sales Order/Quotation forms (Web solution) and Customer
Request workflow processes (CRM). Thus, iScala Customer Requests and their subordinate Sales Orders/Quotations are linked to CRM
Opportunities, and iScala Sales Orders/Quotations are filled with with CRM Opportunity Product
lines. To accommodate the concept of a "Complex Solution Order" (a company can sell not only finished products, but
also related services, or may have to manufacture the product; and this may not be known to a sales person when first registering the
Opportunity), Opportunities get converted to sales orders via iScala Customer Request, which is a snapshot of an Opportunity. Integrated User Interface The user interaction between Microsoft CRM and iScala happens as one process. You can: Open the Customer Request form (iScala Web solution) from the Opportunity form
(CRM). Open the Sales Order/Quotation form (iScala Web solution) from the Sales main
navigation pane (CRM), the Account form (CRM), and the Opportunity form (CRM). Show Invoice Lists (iScala Web solution) in the Account
form (CRM) and the Opportunity form (CRM). Calculate iScala prices and discounts for Opportunity
Products (CRM). Display iScala price lists and currencies in lookup fields of the
Opportunity form (CRM).
Version History of Sales OrdersSales order version history is designed to store complete information about deleted sales orders/quotations or about quotations
converted to orders. Both deleted sales orders and converted quotations are automatically saved with a version number taken from an
internal counter. A new field storing information on the sales order owner has been added to the order parameters. When data is being
synchronised between iScala and CRM, iScala user credentials are sent to CRM and the appropriate CRM user is selected, to provide the
activity on the CRM side. A new field for storing CRM currency has been added to company parameters. During synchronisation between iScala and CRM data,
the corresponding conversion of monetary amount from iScala currencies to the CRM currency is performed. Account Number Enhancement The iScala Customer counter from Sales Ledger parameters can be used while entering Account Numbers in the Account form
(CRM). CRM Snap-In in the iScala Administration ConsoleThe snap-in, which has been redesigned according to the iScala user interface standards, now allows you to: Edit mappings between iScala and CRM users. Edit rules, default values, and options for mappings between iScala and CRM entities.
The snap-in also provides support for iScala License and Lan services. CRM Data Consistency Checking (Mass Update) Tool The performance of the tool, for large amounts of synchronised data, has been increased. A new mode has been introduced for showing differences between iScala and CRM data and their partial
synchronisation. Support for iScala License and Lan services has been implemented.
|
|
top | Search/Sort Sales Orders by Site Code/Project CodeThe Site Code and Project Code fields have been added to Sales Order header, linking sales orders to the corresponding
projects. The sales orders can be sorted and searched with these new fields. Using Global Calendar in MPCReplaces the MPC Shop Floor Calendar with the global calendar functionality for calculation of work centre capacity, start and
due dates when using lead time. A new manager has been introduced for importing generic calendars. Enhanced Graphical Planning in MPCThe Graphical Planning is a tool for planning Work Orders created from Sales Orders. Planning can only be made for Work Orders
in a batch-queue, not for existing Work Orders; it can also be used as an enquiry that displays the load for the selected Work
Centres. Late Cost Transactions SupportThe user can now fully control the purchase order life cycle after the order has been invoiced. It is possible to enter
additional costs after invoicing. Box Handling functionality allows you to: Create, adjust, and delete shipment information. Register received boxes according to the previously specified shipment information. Move stock items between boxes. Create Box
Picking Proposals. Print box delivery documents. Register a box delivered to a customer according to the previously created Box Picking Proposals.
Warehouse Application IntegrationIt is now possible to to integrate a third-party Warehouse Management system with iScala, in order to automate warehouse
management for all types of stock including purchased items, raw materials, and finished goods. The external application can take full
control of selected sales orders, purchase orders, work orders, and their associated order lines. New Stock or Manufacturing Bill-Of-Materials can be created in either the Warehouse or iScala Systems and
synchronised. Details of goods to be picked for Sales and Work orders created in iScala can be sent to the warehouse system in near
real-time or when requested by the warehouse system. Details of goods to be returned against purchase orders (i.e., items to be returned to the supplier) created in iScala
can be sent to the warehouse system in near-real time or when requested by the warehouse system. Details of actual goods picked can be sent from the warehouse system back to iScala for processing. Details of anticipated goods from Purchase Orders and completed Work Orders can be sent from iScala to the Warehouse
system in near-real time or when requested by the warehouse system. Details of expected goods to be returned from a sales orders (i.e., items to be returned by the customer) created in
iScala can be sent to the warehouse system in near-real time or when requested by the warehouse system. Details of actual goods received can be received into iScala as Goods Received Note. The Warehouse system can send details to iScala about changes in the location of goods within a warehouse. The Warehouse system can send details to iScala about the movement of stock between iScala warehouses (e.g. to report the
move of goods into a damaged warehouse). The Warehouse system can send details to iScala about the movement of stock between iScala warehouses (e.g. to report
the move of goods into a damaged warehouse). The Warehouse system can send details to iScala about stock balance for a specific date, to
maintain the stock balance history in iScala. iScala can send details to the warehouse systems of required stock movements (i.e., send internal picking lists for stock
that needs to be shipped to another warehouse). A bar-code system can send actual stock quantity details to iScala (either in reply to a stock count or in cases where
the operator notices low stock levels and wants to ensure that iScala records are accurate). While an operation is performed by the Warehouse system, the access to specific data can be
temporarily locked, to avoid conflicts during the synchronisation with iScala. Support is included for Serial Numbers (in Sales and Purchase Orders) and Batch Control. Support is included for Structure and MPC Bill-Of-Materials.
Manufacturing Application IntegrationIt is now possible to to integrate a third-party Manufacturing system with iScala, to let engineers modify the standard Work
Orders within the Engineering Application and them back to iScala for merging into production plans along with all other Work
Orders. New Bills-Of-Material can be created in either the Manufacturing or iScala Systems and synchronised. Work orders created in iScala can be sent to the manufacturing system in near realtime or when requested by the
manufacturing system. Once sent, work orders can be modified as required in the manufacturing system and then back into iScala for inclusion
in the normal production planning process. Details of inventory issued to a work order can be sent from iScala to the Manufacturing System
After completion of a work order, details of actual production can be sent back to iScala. Details of by-products and scrapped materials can be sent from the manufacturing system back to iScala. If back-flushing is used in iScala then this is also supported when actual production details are received into
iScala. Standard Code Conversions are supported within the XML Mapper tool to let predefined code conversions to be configured
and maintained as needed. For example this may be used to convert external stock codes to internal Scala codes.
Stock Taking List Support in
Bar-Code for Distribution SolutionThe Bar-Code for Distribution Connectivity Solution has been extended to support stock taking by using stock taking lists.
The StockTakingListNum element has been added to the Stock Transaction
In manager, and the corresponding business event and process have been introduced. |
|
top | Service and Project ManagementJob Conflicts in Preventive MaintenanceService Orders with Jobs can be created automatically by Preventive Maintenance. Some Jobs can be set so they cannot be
executed at the same time, such as an oil change and raw material replenishment. A conflict will occur when mutually exclusive jobs are
scheduled at the same time. Access Rights on Price and Cost FieldsIt is now possible to manage access rights to critical fields, such as Costs, Purchasing, and Selling Prices at the field
level. This functionality was introduced in iScala 2.2 and is now supported in the OR, PC, SC, and SM modules. |
|
top | The Developer Toolbox is a package for developers containing products required to customise iScala, including the development
of a fully integrated new code: Although the products within the toolbox have been available individually in earlier releases, the UI Designer and Workflow
Designer have been improved, and the Toolbox repackages all of these products. |
|
top | The Business Toolbox is a package for consultants and business people containing products required to customise iScala,
including reports, queries, screens, and simple behaviour. Most of the products within the toolbox have been available individually in
earlier releases. The UI Designer and Workflow Designer have been improved, and the Toolbox repackages all of these products. The Business Toolbox version of UI Designer allows you to change the layout for existing screens. You cannot add new fields
or change the business logic behind the screens. The Business Toolbox version of Workflow Designer allows you to change events for existing processes. You cannot create new
processes or new external managers. Uses Lumigent Entegra™ (a third party tool) to produce the audit trail. All transactions initiated from iScala may be
logged so that the source can be identified as iScala, including the iScala user identification. External transactions can also be logged
and identified as external. Users can generate Sales Proposals using Microsoft® Word 2003 as a template and store changes
made to proposals as well as populate proposals with customer and product data from iScala. The necessary managers are available to allow iScala integration with a Sales Proposal Document in Office 2003, via smart
tags. |
|
top | Support for More Languages Within One InstallationThe limitation of 10 document and data languages in iScala has been removed. Alignment of Chinese and Japanese TextsAlignment problems when displaying Chinese and Japanese texts in headers have been removed. Korean and Traditional Chinese Languages SupportKorean and Traditional Chinese languages support has been added. |
|
|
top | Changes in DDF and RPT TemplatesThe structure of RPT templates has been changed in iScala 2.2 SR1. In addition, some new DDF codes have been added. If you have
customised RPT templates or plan to use newly implemented DDF codes, be sure to upgrade the corresponding templates, based on
PRD-S22-083-003_iScala 2.2 Products SR1 DDF, RPT
Changes.xls. Changes in XSLT Transformations, Processes, and SchemasIn iScala 2.2 SR1, a number of SCS solutions and processes have been repackaged to eliminate the process duplication among
solutions. If you have customised or custom processes, be sure to upgrade them, based on
PRD-S22-083-004_iScala 2.2 Products SR1 XSLT, Schema Changes.xls. You may want to use the Workflow Migration Tool, a utility included on the iScala Distribution Kit. |
|
top | Known Issues and LimitationsBelow are known issues and limitations for iScala 2.2 SR1. Known issues are supposed to be corrected later. Limitations are attributes of the present release. |
top | Number of copies OR parameters are ignored. Printing a list of OR documents using several report templates selected dynamically during report generation is not
supported (the case when specific report templates (the Document Code property of a Customer file) are
assigned to customers whose invoices are printed in one run). The following OR switches are ignored: One Picking List/WH, Sorted Picking List, Qty. on Delivery Note, Backorders on
Invoices.
Sales Order Support for iScala CRMThe following functionality is not supported: Batch handling Serial numbers MPC ATP MA connection Project management connection Quotation grouping US addresses Maintenance of standard items/templates Bin management Structure groups/BOM Configurable handling Lead time model Co-printability (discount) UDDB Common ID concept (electronic banking address) Request handling Copy from actual orders and history Pharma functionality Hospitality Partner versions Latin America version Advanced version Multidimensional accounting (multiple sources for accounting dimensions settings for order header & order
lines) Stock item long description Access rights to Cost/Prices fields (those used in BackOffice)
In addition: Blocked stock items support is limited (Controlled Distribution,
End/Life From, Obsolete From parameters are ignored. Only delivery rule 2
is supported). Tax calculation support is limited (Tax Liability parameter is ignored,
Tax Code is always taken from the Stock Item). Only delivery rules 0 (Entering orders regardless of the stock balance) and 2 (Inability to enter orders for
discontinued stock items) are supported. Delivery proposal, product labels, tax invoice, detailed history->invoice, detailed history->delivery note are
not supported. Hard allocation for goods is not supported. Packaging in order lines is not supported (Quantity Equals Packages/Units parameter
is ignored). Sections (CD command) for quotation are not supported. Changing warehouse in order line is not supported. The Source of Currencies OR parameter is ignored. Order currency is determined by the
price list currency; invoice currency is determined by the currency specified for the customer in the customer file. Multiple delivery addresses are not supported in sales order entry. No copies are printed for order confirmation, delivery note and invoice. Creating and editing Credit Notes is not supported. The Normal Order Type and Info from Delivery
Customer OR parameters are ignored.
|
|
top | Web Solution Known IssuesBusiness destinations are not supported. Printing does not work under WinDS for Windows forms. In WinDS, report data are successfully generated but the standard WinDS dialog for choosing one of iScala printing
Output Channels does not appear, and the report is not generated. The problem is in integration of legacy WinDS (SfWIII) components and new
.NET printing components. All fields defined in a report template are printed, even if no data is supplied. In BackOffice, they can be
shown/hidden at run time, in accordance with the business logic. Number and date formats are different from those in BackOffice reports. Values are not always correctly rounded. Printing flags are not checked during printout. Sub-reports are not always printed correctly. The Web-based printing uses Crystal Report Templates files (RPT files) and an XML-DDF repository, in order to
recognize which SCS managers shall be called to retrieve data for reporting and how to translate the retrieved XML data into DDF fields of
RPT. But in some cases, RPT does not allow the unique DDF to XML mapping. These cases do not occur in standard reports
supplied with iScala, but may exist at current clients. To fix this issue, some changes are required in the iScaEdit tool (iScala Document
Editor tool for editing DDF reports).
UI Locking and Session SupportSales Order Support for iScala CRMCross-currency calculations are not always correct. Application bug appears when the Order currency is different from the CRM currency. Total balance rounding is not correct. Order discount cannot be specified manually. The following data fields are read-only: Payment Term Freight Freight Tax Code Insurance Insurance Tax Code Packaging Packaging Tax Code Own Freight Price List Code
Detain order discount is not supported.
|
|
|
top | If you need a technical support or want to get answers to technical questions, please address them to
Scala Customer Support. |
|
