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.com




Release Notes for Release 4.1.4
QAD CSS Version: 4.1.4
Release Date: April, 2005
MFG/PRO Compatibility: MFG/PRO eB2, through SP8 and eB2.1 SP2
A number of significant enhancements are included in this release and may require additional configuration and installation changes depending on your system configuration. The release notes provide an overview of major enhancements. For a list of ECOs included in this release, see the file CSS 4.1.4 ECO List on the product CD.
The following documentation has been updated for this release:
Installation Guide: QAD Customer Self Service (78-0618C)
Administration Guide: QAD Customer Self Service (78-0619B)
Implementation Guide: QAD Customer Self Service (78-0627B)
QAD CSS 4.1.4 includes the following major enhancements:
1
This release of QAD CSS is fully compatible with the Shared Services Domain eB2.1 release of MFG/PRO. See Integration with MFG/PRO eB2.1 for details. Updates to accommodate multiple domains in the MFG/PRO eB2.1 database have affected the installation steps for QAD CSS and also require that users perform a conversion.
Note: To support MFG/PRO eB2.1 integration, a number of changes have been made to the QAD CSS code base that may affect customizations. Customers with customizations should review the interfaces to procedures in the extension layer to see if any parameters have changed. To update customizations, you may want to contact QAD Services for assistance.
2
This release includes support for using QAD CSS with an MFG/PRO system that is integrated with Trade Management (TrM). TrM customers must first be set up correctly in QAD CSS; therefore, TrM can be used only for business-to-business (B2B) order processing, not for business-to-consumer (B2C) since B2C lets undefined users order items. In addition, the bonus stock and manual price list features of TrM in sales orders are not supported for orders generated in QAD CSS.
The following combinations of MFG/PRO and TrM versions have been certified:
MFG/PRO eB2 SP8, TrM 2.6 SP1
MFG/PRO eB2.1 SP2, TrM 2.7
Important: If you plan to use QAD CSS with TrM, you must also download and install ECO P2YY.
3
This release includes support for using QAD CSS with an MFG/PRO system that is integrated with European Accounting (EA).
Note: While both EA and TrM integration are supported in this release, only one can be used at a time. MFG/PRO does not currently support using both European Accounting and Trade Management in the same database.
4
A new system registry setting has been added to manage the display of inventory amounts in the product catalog. The runGetWhseQyt setting affects the display of quantity for the default site and for all sites.
5
A new system registry setting has been added to let you choose between the display of promise date or due date in the order summary during check out and in various order-related reports. The showDueOrPromDate setting affects the date display during check out and in the following reports:
Packing Slip Reprint
Order Tracking
Order Summary
Order by Order Report
Order by Item Report
Invoice History Report
6
A number of changes have been made to QAD CSS to ensure that it properly handles the unavailability of WebSpeed or the MFG/PRO database. This might happen due to network problems or planned backups. For WebSpeed issues, errors are captured and displayed to the user. Details on how to set this up are included in the installation guide.
Note: When the Web server is down, the standard browser error displays indicating the page cannot be found.
When QAD CSS is available but MFG/PRO is not, some functions cannot be used. Users attempting to run most order-related reports will receive an error page, indicating that the report cannot be run and they should try again later. Users can browse the QAD CSS catalog, but they cannot add items to the shopping cart or check out. Either buttons are disabled or appropriate messages display.
Once MFG/PRO is running again, QAD CSS must be shut down and restarted to connect properly.
7
The uploadFilePath registry setting is no longer used for managing files created during Catalog and Customer Load.
Integration with MFG/PRO eB2.1
QAD CSS is designed so that a single version of QAD CSS can support multiple versions of MFG/PRO using an adapter developed to accommodate the specific requirements of each release. Version 4.1.4 now has an adapter that works with MFG/PRO eB2.1. To accommodate the presence of multiple domains in the eB2.1 database, the concept of data sources has been introduced into QAD CSS.
Note: While QAD CSS can be used with multiple MFG/PRO versions, one instance of QAD CSS can be used with only one version of MFG/PRO at a time. You cannot connect to both MFG/PRO eB2 and eB2.1 databases simultaneously.
A new Data Source Maintenance function has been added to the Administration|System Control menu. Using this program, you can specify which domains in an MFG/PRO eB2.1 database your QAD CSS instance should be able to interact with.
The ability to interact with domains has affected installation and conversion in an MFG/PRO eB2.1 environment. To connect to an eB2.1 database, you must
Set the PROPATH correctly during installation to point to the mfg directory rather than the qad directory.
Specify a valid domain in the MFG/PRO database you are using with QAD CSS. The first data source record is created based on this domain name during installation and is automatically associated with the demo user. This is required for an administrator to log in and set up the system. You can add additional data sources after logging in to the system.
Restart WebSpeed after making these changes.
You can then log in to QAD CSS and create additional data sources as required for your specific implementation.
If you are upgrading to QAD CSS 4.1.4 from an earlier release, all existing users must have an associated data source. This is initially set to the domain supplied during installation. If you are using more than one domain, you will need to manually modify user records after you create the additional data sources.
All items and customers must be associated with a data source. Data source has been added to the Catalog and Customer Load functions so that you can specify which domain to load item and customer records into. In addition, the following programs have been updated to include a field for data source:
 
 
Address Maintenance
Item Types Maintenance
Contact Cross-Reference Maintenance
Special Maintenance
Customer Maintenance
User Maintenance
Customer Item Maintenance
Order Archive Report
When a B2B user logs in to QAD CSS, the system knows which domain to access based on the user’s associated customer record. In a B2C scenario when a user is undefined, a default domain must be used. This is determined by checking the domain associated with the record specified for the defaultCustomerProfile registry setting. The user’s domain determines which items they can view in the catalog. When an administrator logs in, the domain associated with their user ID determines what displays on some of the administrative reports, such as items and customers.
A new system registry setting—QADUDomain—is used to determine the domain to use for the administrative user defined for managing the background integration between QAD CSS and MFG/PRO. In MFG/PRO eB2, two settings are needed: QADUser and QADUPasswd. MFG/PRO eB2.1 databases require the additional QADUDomain setting.
Integration with Trade Management
When TrM is being used with MFG/PRO, items and customers are defined in both MFG/PRO database tables and tables in the TrM database. Customers and items in MFG/PRO are identified as belonging to TrM by having a value for the Promotion Group field. Within TrM, they are further identified by division.
Several changes to the load functions were made to accommodate loading MFG/PRO data with TrM-specific field values:
The Customer Load selection criteria now includes Promo Group so that it is easy to identify and select TrM customers.
The Catalog Load selection criteria now includes Division so that it is easy to identify and select TrM items.
When TrM is activated, QAD CSS now manages the following:
When a user logs in, the system checks to see if the user’s associated customer is defined as a TrM customer in MFG/PRO. If so, it stores the value of the customer group, customer promotion group, and division as part of the user’s session. It also stores the value of the TrM division currency and uses this rather than the user currency.
When shoppers identified as TrM customers view the product catalog in QAD CSS, they see only items defined for their division in TrM; only TrM items can be viewed, not both TrM and non-TrM. (If a TrM customer belongs to multiple divisions, the first division is used to determine the catalog displayed.)
All pricing calculations are done using TrM price lists both in the catalog and in Sales Order Maintenance. If none are available, the price stored in the customer item detail record is used as with standard MFG/PRO pricing.
The CIM process used to load QAD CSS orders into MFG/PRO has been adjusted for the additional pop-up frames associated with TRM functionality that display in Sales Order Maintenance. Default values are provided so no errors are generated.
Two new e-mail events can be used to display TrM-specific error conditions.
Note: The concept of master customers applies to TrM customers as well as non-TrM customers; a TrM customer can be associated with another TrM master customer and view that customer’s items, as long as they both belong to the same division.
Sales Order Processing
Under the following conditions, special TrM processing takes place when a QAD CSS sales order is loaded into MFG/PRO:
Integrate with TrM is Yes in Sales Order Control (7.1.24).
The order sold-to address is a TrM customer, indicated by a value in the Promo Group field in Customer Maintenance (2.1.1).
The order item is defined in TrM by specifying a value for the Promo Group in Item Master Maintenance (1.4.1).
The sold-to address and item belong to a valid TrM division.
The division currency of the sold-to is the same as the order currency.
All items on the sales order belong to the same division.
TrM price lists have been created; otherwise, standard MFG/PRO pricing is used.
In this case, MFG/PRO uses TrM-specific data from the sales order header and line detail to select applicable TrM-generated price lists using the MFG/PRO best pricing logic. Price lists created in MFG/PRO are not considered.
When a sales order is loaded into MFG/PRO with TrM activated, the following processing occurs:
The division defaults from the customer sold-to address.
For B2C customers, the customer division is set to blank so that no special TrM processing can occur.
Bonus Stock is set to No for all TrM transactions.
Two new events have been added to Email Master Maintenance that are generated during processing of TrM orders:
When the currency associated with the TrM division is different from the sales order currency, an error prevents the CIM load and an e-mail event is triggered to notify the customer service representative (CSR).
When a valid exchange rate does not exist during order pricing, a message is sent to the CSR and the system uses the price stored in the QAD CSS customer item detail record (wpro_cust_item).
 
Event ID
Event Name
Subject
Event Status
Send Copy to User
Send Copy to CSR
Body
Ex067
TRM CIM Order – Error
QAD CSS – Error in TRM Order with Currency
Yes
no
Yes
When attempting to create sales order [@orderNum], the TRM division currency [@TRMDivCurr] is different to the sales order currency [@SOCurr].
Ex068
TRM Exchange Rate – Error
QAD CSS – Error in TRM Pricing with Exchange Rate
Yes
no
Yes
The exchange rate to convert from currency [@Curr1] to currency [@Curr2] is missing.
Integration with European Accounting
When European Accounting (EA) is being used, additional information is associated with customers that can affect processing in sales orders and cause new pop-up windows to display. These features are managed by settings in European Accounting Control (26.23) and include:
VAT Registers
Suspended VAT
Correction Invoices
When VAT registers or suspended VAT is enabled, pop-ups display in Customer Maintenance. These affect the way B2C customers are created in MFG/PRO. Since these customers are created in the background, default values must be provided for the EA fields:
The value for VAT register is derived using Global Tax Management (GTM) data for the ship-from address and the ship-to address.
The values for the bank and payment method required by EA are derived from European Accounting Control.
The value for operation code is determined by the value specified for the customer record defined as the defaultCustomerProfile registry setting.
If Use Suspended VAT is Yes in European Accounting Control, the value for a new B2C customer is set to No by default.
Sales Order Processing
Special processing takes place when a QAD CSS sales order is loaded into MFG/PRO and European Accounting is installed:
The system checks the value of Use Correction Invoices in European Accounting Control. If this is Yes, it sets the value of Original Invoice to blank so that the new sales order is created as a normal order.
If Use Suspended VAT is Yes in European Accounting Control, the value for Suspended VAT on the order defaults from the customer sold-to address.
If VAT Registers is Yes in European Accounting Control, the values for VAT register and operation code default from the customer sold-to address.
Note: All taxable lines added to the order must have the same VAT register assigned to their associated tax environment or an error is generated. A new message has been added to the system (EX013) to accommodate this situation.
Managing Inventory Display with runGetWhseQty
You can use the new runGetWhseQty registry setting to determine how inventory availability displays in the catalog.
Note: To see these fields in the product catalog, they must be marked for display in Item Layout Maintenance.
The setting of runGetWhseQty has three possible values:
Off: Do not perform any calculation. Even if the quantity available has been marked to display in Item Layout Maintenance, no value displays on the screen.
Qty: Check the value of the runGetAllWhseQty and runGetDefWhseQty settings and display the quantity available based on those settings.
Text: Check the value of the runGetAllWhseQty and runGetDefWhseQty and display the text contained in one of two configurable messages, indicating that stock is available or unavailable.
When runGetWhseQty is set to Qty or Text, two other registry settings determine how the quantity available is determined. The values of runGetAllWhseQty and runGetDefWhseQty determine if these quantities are found in MFG/PRO or read from values stored in the QAD CSS customer item master (wpro_cust_item) table. In QAD CSS, whsQty is read for the default site and the totQty for all sites.
The messages that define the text displayed when the value of runGetWhseQty is Text are defined in Error Message Maintenance:
OP000244 displays when zero or less quantity is available at the default site or in all sites. The text of this message is currently set to Out of Stock, but you can modify it to meet your own requirements. The message text can also display the value of the symbol [@QtyAvail] when it is included.
OP000245 displays when a quantity greater than zero is available at the default site or in all sites. The text of this message is currently set to Available, but you can modify it to meet your own requirements. The message text can also display the value of the symbol [@QtyAvail] when it is included.
The combination of these three registry settings provides great flexibility in how you manage and display availability in the catalog. Here are some possible options:
If you do not want to display availability information, turn off the display in Item Layout Maintenance and set runGetWhseQty to Off. This optimizes performance when quantity information is not relevant.
To display full quantities for each item based on information from MFG/PRO, turn on the field display in Item Layout Maintenance, set appropriate side labels for the fields, set runGetWhseQty to Qty, and set both runGetDefWhseQty and runGetAllWhseQty to Yes.
To display a message based on availability information from MFG/PRO, choose which inventory to check: either default site or all sites. Then, turn on display for that field only in Item Layout Maintenance, leave the side label blank, set runGetWhseQty to Text, and set either runGetDefWhseQty or runGetAllWhseQty to Yes. The message Available displays when a quantity is available; otherwise, Out of Stock displays. These messages can be modified in Error Message Maintenance.
To just display a different message—such as Call for availability—for every item in the catalog, turn on the display for default site quantity in Item Layout Maintenance, leave the side label blank, set runGetWhseQty to Text, set runGetDefWhseQty and runGetAllWhseQty to No. Then change both message Op000244 and Op000245 to “Call for availability” in Error Message Maintenance.
To always display the quantity based on information maintained in QAD CSS (not MFG/PRO), turn on display for either the default site or all sites in Item Layout Maintenance, set appropriate side labels, set runGetWhseQty to Qty, and set both runGetDefWhseQty and runGetAllWhseQty to No.
Note: The catalog design applies to the entire catalog; you cannot set the display for individual items.