In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |

  •     QAD Glossary

  • Release Notes for Release
    QAD CSS Version:
    Release Date: May, 2006
    MFG/PRO Compatibility: MFG/PRO eB through SP9 and eB2 through SP8
    The following fixes and changes are included in this release and may require additional configuration and installation changes depending on your system configuration.
    If you are upgrading to from an earlier version of QAD CSS, a conversion is required. See Upgrading from 4.1.3 to the Current Release for details.
    New Features
    You can now use the new EX072 e-mail event to let designated system administrators know when the proper Global Tax Management (GTM) setup does not exist in MFG/PRO.
    Event ID
    Event Name
    Event Status
    Send Copy to User
    Send Copy to CSR
    Tax - Warning
    QAD CSS Tax environment not found
    Sales Order for [@orderNum] on [@eventDate] does not include actual tax values. This is due to unavailability of corresponding tax environment setup.
    Please contact the Customer Support Administrator.
    Temp Load input file: [@TransFile]
    Temp Load output file: [@TransFileOut]
    Corrections to Existing Features
    A number of corrections have been made to ensure that sales quotes and orders are loaded correctly in all circumstances including the following:
    Orders are in non-US English.
    Special characters are used in input fields.
    Optional pop-ups are enabled such as adding items to the installed base.
    Comments are added to the order before loading into MFG/PRO.
    A new address is created and optional pop-ups such as time zone and self-billing are enabled in Customer Address Maintenance.
    An error has been corrected that prevented e-mail from being sent even though the e-mail server was properly set up.
    When a record is modified from a page in a browse, the browse now redisplays the same page. Previously, the browse displayed page 1, even though the modified record was accessed from a different page.
    When menus are generated, you can reorder menus as needed. However, Customer Selection must always be the last item on the menu listing or the generation fails. A message now displays the specific cause of this error.
    Prices on the Invoice History Report now correctly display in the currency associated with the customer generating the report when the customer’s currency is not the base currency.
    The display font used for country and county in shipping and address fields is now the same.
    The copyright year has been updated to reflect the current year.
    A B2C user will now receive an e-mail with a temporary password when they provide the correct answer to the secret question. Previously, this feature only worked for B2B users.
    The customer lookup in User Maintenance now displays only customers defined in QAD CSS.
    The length of the phone number field on the Address Setup screen is now limited to 16 characters to conform to the acceptable length in MFG/PRO.
    Performance of CIM has been improved.
    When freight terms are associated with the default customer in MFG/PRO, new customers created based on the default now inherit the default freight terms.
    An error in the menu system that prevented a page from displaying during Order Entry 3 has been corrected
    A Javascript error that could display in Detail Menu Button Maintenance when the button order was changed has been corrected.
    The active link for UPS in QAD CSS shipping documents has been corrected to point to the correct URL.
    When the item number search function is invoked on the Order Entry 1 page, the system now returns the correct value even if a space is added to the end of the item number.
    You can now include a space in the list of valid credit card types in Credit Card Vendor Maintenance. Previously, if you used a space to separate values, they would not display on the Online Processing page during order processing.
    Performance in lookups has been enhanced.
    Search behavior in most maintenance functions has been corrected. Blank search now behaves as expected and returns all records.
    Display issues that occurred when a B2C user logged in to a B2B environment and vice versa have been fixed.
    Selecting an item from the lookup on the To Item field in Order By Item Report now works correctly.
    The User Master Report now works properly when the Show Customers option is selected and a large number of user records exist.
    The system now correctly assigns a number to an order created in QAD CSS when Sales Order Control (7.1.24) is temporarily locked in MFG/PRO. This situation happens only when the system has been set up to derive numbers from MFG/PRO (UseERPOrderNumber is Yes in QAD CSS system registry).
    When you disable the ShowExtendedPrices registry settings, prices are now properly suppressed in the shopping cart from Order Entry 2.
    When Address Verification is enabled in Credit Card Vendor Maintenance, the AVS data is properly sent to MFG/PRO and stored with the transaction.
    When a customer orders an item in QAD CSS and no available inventory is found at the customer site, the system will now locate inventory at the item master site and successfully create a quote.
    When a customer has unique bill-to and ship-to addresses defined in MFG/PRO, the proper ship-to address now displays on the confirmation screen during order entry.
    A problem that occurred when you attempted to add a new contact cross-reference in Administration Menu|Contact Cross-Reference has been fixed.
    The length of the item number field displayed when an e-mail confirmation is sent for an order (E-mail event EX001) has been increased from 8 characters to 18, to correspond to the maximum item number length in MFG/PRO. In addition, a problem sending this event in an MFG/PRO eB2.1 environment because of a missing domain value has been corrected.
    A fully shipped and invoiced order now always displays with a blank status when viewed by a customer in QAD CSS. Previously, if the order was on hold (action status of HD), the status field was not cleared even after the order fully shipped.
    An internal error that generated a message about a missing program in the Web server log file has been corrected.
    A problem related to the default country that occurred when editing bill-to and ship-to customers in the Address Book page has been corrected.
    A number of problems related to pricing items in QAD CSS when discount price lists apply have been fixed.
    A problem displaying currency amounts for prices in the catalog when the currency format is not American has been corrected.
    A number of minor format corrections have been made to the System Registry Report.
    The Update Ship-To field has been removed as an option in Order Control Maintenance. The integration between MFG/PRO and QAD CSS does not support modification of ship-to address data stored in MFG/PRO, only creation of new records. A number of other problems that could occur when the ship-to address was changed on an order during order-entry have been corrected.
    When data fails to load into MFG/PRO, selected users are now properly notified by e-mail so that they can take corrective action.
    In previous versions of QAD CSS, if you changed the ship-to address on an order to a non-taxable address and the original ship-to was taxable, the order quote was not regenerated. This could lead to misleading order totals. QAD CSS now regenerates the quote when the ship-to address is changed.
    The e-mail message generated by the system when a user logs in and event EX031 is enabled now includes the user name, rather than the user ID.
    Non-standard submit behavior has been corrected in the Customer Credit Report.
    Additional Notes and Corrections to the Documentation
    When defining a credit card vendor in Credit Card Vendor Maintenance, you need to specify the fully qualified path to the directory containing the executable programs required for sending credit card transactions in the Path to a Processing Program directory field. Note that the system assumes the final component of the path is a directory named /bin and appends /bin to the path you enter in this field. This additional note will be added to the next revision of Implementation Guide: QAD Customer Self Service when the book is republished.
    Upgrading from 4.1.3 to the Current Release
    Use the following instructions to upgrade from QAD CSS 4.1.3 to on UNIX, Linux, or Windows platforms. Refer to the installation guide you received with 4.1.3 for any additional details.
    The steps required to upgrade QAD CSS are:
    Install the new media to your QAD CSS server.
    These instructions assume that you are installing to a new location and not overwriting your existing 4.1.3 system. After upgrading and testing the new QAD CSS version, you can switch over to your production system.
    Set up QAD CSS environment values.
    Convert the old database.
    The upgrade method supports an in-place conversion of your existing QAD CSS database. You copy it to the installation directory before executing the conversion.
    Compile the QAD CSS code.
    Installing New QAD CSS Media
    Complete these steps to install the new QAD CSS media.
    Log on as a user that has permission to execute the installation script and update the installation directories.
    On UNIX systems, mount the CD-ROM. On Windows, place the CD in a CD-ROM drive.
    Note: Copying the distribution files from the CD to a temporary directory on disk can increase extraction speed.
    Launch a command window and change directories to the install directory on the CD:
    cd /install
    Launch the installation script in that directory:
    For Windows, launch install.exe.
    A welcome screen displays. Press Enter. Use the following table to enter the appropriate values for script execution.
    User Values
    License agreement
    Install log file
    Accept default or enter a new location and name
    QAD CSS installation directory
    Default is /qadcss; typically, this should not be the same location as your existing QAD CSS 4.1.3 files
    File extraction
    Progress directory
    Your Progress install directory
    Windows: icon folder name
    Default is CSS 4.1.3
    Script end
    Note: At the end of the script, the name and location of the installation log file display. Open the log file in a text editor to check for errors.
    Setting Up QAD CSS Environment Values
    Before beginning the conversion, you must define some environment variables required by MFG/UTIL.
    Launch MFG/UTIL from the CSSInstallDir using the following command:
    For Windows, launch MFG/UTIL from the icon on the Start menu.
    Select CSS Setup from the Configure CSS menu. Use the following table to update your QAD CSS configuration.
    CSS Database Directory
    This is CSSInstallDir /database by default.
    CSS Install Directory
    The CSSInstallDir defined during install.
    Progress Install Directory
    The Progress install directory as identified during the install.
    MFG/PRO Install Directory
    The MFGPROInstallDir for the MFG/PRO instance CSS will connect with.
    WebServer Host Name
    The server name or IP address of the Web server. This should also include a domain name. The in the sample screen is the domain name.
    WebSpeed Broker Name
    The name of the broker you plan to use; this guide uses qadcss as an example.
    Important: To preserve your previous 4.1.3 installation of QAD CSS, make sure you specify a different broker name.
    WebSpeed Broker Port
    Any available port.
    Choose OK to save the changes.
    Converting the Database
    The database conversion is completed using a set of options on the Upgrade CSS menu in MFG/UTIL.
    Conversion Overview
    Completing the conversion involves the following activities, represented by options on the MFG/UTIL Upgrade CSS menu:
    Copy your 4.1.3 database to the installation directory.
    Run a script that dumps the data from your 4.1.3 database and converts the data to
    Load the data that was dumped in step 1 into the updated tables.
    Update the version to reflect the QAD CSS release.
    Note: The option Dump Data from Database on the Upgrade CSS menu is currently not required since the data is dumped automatically during the first step.
    Running the Conversion
    Use the following procedure to convert your existing QAD CSS database.
    Copy the database to be upgraded from its existing location to the /database directory under your QAD CSS installation.
    Change your current directory to CSSInstallDir.
    Use procopy to copy your 4.1.3 version database to:
    Start MFG/UTIL and choose Convert CSS to from the Upgrade CSS menu.
    In the Connect Database screen, connect to the existing CSS database to be converted (the one copied in step 1). The log window displays showing a successful connection.
    The system performs CSS 4.1.3 data conversion and dumps all the .d files in the CSSInstallDir /convdata directory. When this is complete, choose Close to continue.
    Choose Load Data into Database from the Upgrade CSS menu. In the Connect Database screen, connect to your CSS database.
    In the Load Data Contents screen, use the Browse button to locate the CSSInstallDir /convdata directory and choose OK.
    In the Table Selection for Load screen, all the tables are automatically selected. Choose OK.
    The system loads updated data into the database. When this is complete, choose Close to continue.
    Choose Update Product and Version from the Upgrade CSS menu. Enter the correct version name and database name. The version name for the current version is ex The database is the QAD CSS database name located in:
    CSSInstallDir /database
    The Log Window displays and shows progress. Choose Close.
    Choose File|View Log to view the MFG/UTIL log file and ensure that the conversion completed successfully.
    Compiling QAD CSS Source Code
    Make sure that the Web server, AdminServer, NameServer, and Broker are all configured and started properly. Follow these steps to compile the QAD CSS source code from the WebSpeed Workshop:
    Using a Web browser, go to the WebSpeed Workshop by entering the following URL:
    http://webServer / webServerScriptsDirectory/
    Note: The webServerScriptsDirectory is typically your Web server /cgi-bin directory.
    Note: In Windows environments, cgiip.exe is typically specified rather than
    Choose File Tools from the menu on the left.
    Compile compme3.1.html in the WebSpeed Workshop.
    Run compme3.1.html from the post-compilation dialog.
    In Filter, enter .html. Highlight all files to be recompiled and click Compile.
    Note: Do not compile the .html files in the tools directory, such as rp_rpt_template.html. These files are intended to be used as samples for creating your own programs and contain code that may cause compile errors.
    Typically, you compile the .html files only. When you are ready to move to a production environment, you can also compile the program files (.p). However, since these are loaded persistently, compiling them does not improve performance significantly.
    The compilation process may take a few minutes.
    Compile the two .w files in CSSInstallDir/qadcss/css/cl/. In Filter, enter .w. Highlight all files to be recompiled and click Compile.
    You have completed the upgrade to QAD CSS