» Sage 300 2014 Product Update 1 Release Notes

Sage 300 2014 Product Update 1 Release Notes

Product Update 1 contains a modified version of one or more Sage 300 program components. It is not a full upgrade or a product replacement. It is valid only until we release the next product update or the next version of Sage 300.

Updating Programs

Before installing this product update, read the following important information:

• This update includes changes to the Sage 300 Portal. If you have installed the portal, the installation program will need to stop and restart Internet Information Services (IIS) and the Sage 300 Tomcat service.
• After installing this update, you must uninstall and then reinstall workstation setup on any workstations you use. This step is required to support a fix for printing datapiped reports, which is included with this product update.
• After installing this update, you should clear your browser’s cache. (Some fixes included in the update will not take effect until you do.)

  If you use Web Deployment, you may also need to delete some downloaded files to ensure that this product update is installed correctly. For more information, see Knowledgebase article 34330.

Upgrading to Later Versions

Important! If you upgrade to a later version of Sage 300, you must install all released product updates for that version before activating your data to avoid possible data corruption issues.

Compatibility with Sage Programs

For a complete list of compatible programs, database platforms, and operating systems, see the Sage 300 2014 Compatibility Guide in the Sage Knowledgebase.

Sage CRM Integration Known Issues

• You may experience a problem that prevents you from opening Sage 300 screens from Sage CRM. To fix this problem, see Knowledgebase article 34906.
• Sage CRM Integration with Sage 300 does not currently support Oracle databases. Sage CRM Integration support for Oracle databases will be added in Sage CRM 7.2E, which is scheduled for release in July, 2014.

For information about integration changes and other known issues, and to download the integration upgrade package, see Knowledgebase article 35474.

Product Update 1 New Features and Enhancements

The following sections describe new features and enhancements included in Product Update 1.

Importing and Exporting

Sage 300 now supports the xlsx file format that was introduced in Microsoft Excel 2007.

Note: If Excel 2007 is not available as a file type when importing or exporting, you must install Microsoft Access Database Engine 2007. For more information, see Knowledgebase article 35473.

Accounts Receivable

Transaction entry screens (Adjustment Entry, Invoice Entry, Receipt Entry, and Refund Entry) now include an Entered By field that indicates who entered the transaction.

Accounts Payable

Transaction entry screens (Adjustment Entry, Invoice Entry, and Payment Entry) now include an Entered By field that indicates who entered the transaction.

Purchase Orders

You can now create invoices and credit notes that have a total of zero.

^ Back to top

Product Update 1 Program Fixes

The following sections describe program fixes included in Product Update 1.

System Manager

• Fixed a problem that could prevent you from importing data if you used the Browse button to select an import file. For more information, see Knowledgebase article 30101.
• Fixed a problem that could cause some screens to stop responding if you moved columns in a table. For more information, see Knowledgebase article 23705.
• Fixed a problem with memory management that could impair performance.
• Fixed a problem that caused Chinese characters to be displayed incorrectly. The problem occurred if you selected English as the format in Windows Region and Language settings. For more information, see Knowledgebase article 24626.
• Fixed a problem that caused Thai characters to be displayed incorrectly on Finder screens, and could cause issues when entering Thai characters in some text fields. For more information, see Knowledgebase article 24128.
• Fixed two problems that could cause screens to stop responding if you selected a field or control that became unavailable when selected.
  Example:

  On the A/P Invoice Entry screen, after you enter information for an entry, the batch fields become unavailable.

  So, if you entered any information for an entry (such as a vendor number), and then selected a batch field (such as Batch Date), one or more error messages appeared, and then the screen stopped responding.

  For more information, see Knowledgebase articles 24510 and 28880.

Report Printing

• Fixed a problem that could occur when printing reports from an Oracle database that included multiple companies. The reports could include data for the wrong company.
• You can now print order confirmations and quotes from Sage CRM, and you can print snapshot reports from the Sage 300 Portal for Oracle databases.
• Fixed a problem that could trigger an Assertion error message when you used a third-party program to print reports. For more information, see Knowledgebase article 30364.
• When exporting in Text format from a report preview, you can now specify Characters per inch and Number of lines per page.
• Fixed a problem that could cause your computer to run out of memory after processing and printing (or previewing) a number of invoices individually.
• Fixed a problem that prevented you from printing datapiped reports.

Accounts Payable

• Fixed a problem that prevented you from saving a distribution code when you used an apostrophe in the description for the code. For more information, see Knowledgebase article 26698.
• Fixed a problem that prevented you from printing a 1099 report if the Short Name in the vendor record contains double quotes. For more information, see Knowledgebase article 29037.

Accounts Receivable

• Fixed a problem on the Customer Inquiry screen that caused document amounts to be calculated incorrectly on the OE Orders and OE Invoices tabs. This problem occurred if you used Divide as the rate operation for currency rates. For more information, see Knowledgebase article 25133.

General Ledger

• Fixed a problem on the Journal Entry screen that could prevent you from importing XML files. For more information, see Knowledgebase article 29499.

Inventory Control

• You can now run Day End Processing for A/R receipt entries and A/R receipt batches with long numbers. Previously, Day End Processing could not handle A/R receipt entries with numbers longer than 3 digits, or A/R receipt batches with numbers longer than 4 digits. For more information, see Knowledgebase article 27973.
• Fixed a problem that prevented you from splitting or combining lots before running Day End Processing. For more information, see Knowledgebase article 24983.
• Fixed a problem that could cause costing information to become incorrect for serialized and lotted items after running Day End Processing.

  Note: This update corrects the cause of the problem, but not your data. After you install this product update, the problem will not recur, but any existing problems with your data will remain. For more information, see Knowledgebase article 24496.

• Fixed a problem that could cause a “Run-time error” message to appear when you closed the Serial Numbers screen or the Lot Numbers screen. For more information, see Knowledgebase article 33469.

Purchase Orders

• Fixed a problem on the Purchase Orders screen that could cause purchase orders to be sent to the wrong vendor when using Vendor’s E-mail or Contact E-mail as the delivery method.

  Note: This fix makes all purchase orders datapiped purchase orders. If you have been using non-datapiped (ODBC) purchase orders and you want to continue using them, you must edit the PORPT.INI file. For more information, see Knowledgebase article 21367.

Order Entry

• Fixed a problem that could cause an incorrect default unit of measure to appear for a manufacturer’s item on the Items/Taxes screen for shipments, credit notes, or debit notes. For more information, see Knowledgebase article 31279.
• Fixed a problem that caused an incorrect default unit of measure to appear for an item in Order Entry transactions when you used Pricing Unit as the Default Order UOM in Order Entry. If the I/C item's Base Price Type was Base Price for Multiple Units of Measure, the stocking unit of measure appeared as the default UOM in orders, shipments, debit notes, and credit notes, even if the price list specified a different default unit of measure. We fixed a similar problem that occurred for the Sales Price Type. For more information, see Knowledgebase article 30864.
• Fixed a problem that prevented you from posting credit notes using a macro if you did not allow negative inventory. For more information, see Knowledgebase article 29591.
• Fixed a problem on the Order Entry screen that could cause Extended Cost amounts for details to be calculated incorrectly. This problem occurred if the Costing UOM and the Order UOM were different, and if you changed both the order type and the quantity ordered. For more information, see Knowledgebase article 27871.
• Fixed a problem that could cause blank pages to be printed when printing the Transaction List report. This problem occurred only when printing the report without order details. For more information, see Knowledgebase article 31353.
• Fixed a problem on the Invoices screen that could cause invoices to be sent to the wrong customer when using Customer’s E-mail or Contact E-mail as the delivery method.

  Note: This fix makes all invoices datapiped invoices. If you have been using non-datapiped (ODBC) invoices and you want to continue using them, you must edit the OERPT.INI file. For more information, see Knowledgebase article 21367.

Project and Job Costing

• On the Projects tab of the Contract Maintenance screen, a Finder is now available for the Work in Progress field and the Cost of Sales field. For more information, see Knowledgebase article 30343.

Sage 300 Intelligence Reporting

• This update includes several fixes for Sage 300 Intelligence Reporting. For more information, see the Release Notes for Sage 300 ERP Intelligence Reporting on the Sage Customer Portal.

Sage CRM Integration

• Fixed a problem that could prevent you from creating or saving an order that included a detail with negative inventory quantity, if you do not allow negative inventory. This problem occurred only if you use the Default Quantity Committed option in Order Entry. For more information, see Knowledgebase article 30091.

Sales Analysis

• Fixed a problem that prevented you from selecting the Service Manager Invoices/Returns option on the Setup Options screen, even if Service Manager was activated. For more information, see Knowledgebase article 24285.