Sage 300 2014 Product Update 5 Release Notes

Product Update 5 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.

Depending on your purchase agreement, some features described here may not be available in your product.

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.
• If you use Canadian Payroll or US Payroll, you require version 2016 (internally versioned as 7.2A) of these programs.

• After installing this product update:

  • Because of database changes contained in this product update, you must reactivate your data for the following programs:

    • Tax Services
    • Accounts Receivable
    • Accounts Payable
    • Inventory Control
    • Purchase Orders
  • You must uninstall and then reinstall workstation setup on any workstations you use.
  • 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.

  • If you use Sage CRM Integration and you have not previously installed product update 2, you should uninstall and then reinstall the Sage CRM Synchronization Component. (The new message added in this update will not take effect until you do.) For more information, see Knowledgebase article 42238.

Updating Sage 300 Intelligence Reporting

Product updates for Sage 300 Intelligence Reporting are not included with product updates for Sage 300. If you use Sage 300 Intelligence Reporting, check that you have installed the most current product update.

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.

2016 U.S. Tax Forms

For the 2016 tax year, the IRS has not made changes to the 1099-MISC paper forms or electronic filing format. This product update has no changes to the Print 1099/1096 Forms screen or the 1099 Electronic Filing screen.

Known Issues

• If you use Sage CRM integrated with Sage 300, you may experience a problem that prevents you from opening Sage 300 screens from Sage CRM. To fix this problem, see Knowledgebase article 34906.
• When using Sage 300 in web deployment, it is not possible to print. For more information, see Knowledgebase article 71268.

Error in Product Update 1 Release Notes

Sage makes every effort to provide accurate product documentation, and we apologize for any inconvenience caused by the following error in the Product Update 1 documentation for Sage 300 2014:

We stated that Sage CRM Integration support for Oracle databases would be added in Sage CRM 7.2E. In fact, Sage CRM 7.2E is not required, and we have now added Sage CRM Integration support for Oracle databases.

^ Back to top

Product Update 5 New Features and Enhancements

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

System Manager

• On the Licenses tab of the License Manager, a new Count column displays the maximum number of employees for a product subscription. If you have a Sage Payroll subscription, this column displays the number of employees for whom you can calculate payroll.

  Note: A count of 999 indicates that you can calculate payroll for an unlimited number of employees.

• We've added a Live Chat button to the ribbon on the Sage 300 desktop to make it easier for you to contact our friendly support team.

^ Back to top

Product Update 5 Program Fixes

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

Running Macros

• Fixed a problem that prevented you from using the GETRATES macro to update currency rates.

System Manager

• When signing on to Sage 300, if security is turned on, the cursor now appears in the Password field by default (on the Open Company screen). For more information, see Knowledgebase article 75657.

Bank Services

• The decimal symbol specified in your system’s regional settings now appears correctly in numeric values (such as €100,00). For more information, see Knowledgebase article 72628.

Accounts Payable

• Updated the 1099 form and the 1096 form to meet changed IRS specifications for the 2015 year.

  Important! When printing these forms directly to a printer, you must select the Report Paper Size option on the Print Destination screen. For more information, see Knowledgebase article 73134.

Inventory Control

• If you update costing during posting instead of during day-end processing, running day-end processing that includes I/C transfers is now faster. For more information, see Knowledgebase article 79285.

Canadian and US Payroll

• Fixed a problem that could cause Payroll subscriptions to not be recognized. If this problem occurred, you were prevented from using Payroll.

Sage CRM Integration

• Sage CRM 2017 is now supported.

^ Back to top

Product Update 4 Program Fixes

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

Portal

• Fixed a problem with the Balance Sheet and Income Statement snapshot reports, which prevented you from drilling down to see more detail about values displayed on those reports. For more information, see Knowledgebase article 58655.

Web Deployment

• Fixed a problem that occurred on screens in web deployment, which prevented you from printing messages. For more information, see Knowledgebase article 61758.

Report Printing

• Fixed a problem that prevented parameters for a custom report from appearing if you printed the report directly to your printer (without first previewing the report). For more information, see Knowledgebase article 43600.

Integration Between General Ledger and Other Programs

• Fixed a problem that could occur in programs other than General Ledger, which could prevent you from performing actions that create G/L entries (such as posting transactions or running day-end processing). This problem occurred only if you use an Asian language such as Japanese, Chinese, or Korean.

System Manager

• Fixed a problem that caused a “Propagating System Tables” message to appear when opening a database.
• Fixed a problem with the View menu on the Sage 300 Desktop, which caused the Toolbar and Status Bar options to be reset (making the toolbar and status bar visible) each time you signed in to Sage 300. For more information, see Knowledgebase article 66316.

Bank Services

• Fixed a problem that could cause a “Lines Reconciled should not be greater than Lines” error message to appear after sorting transactions on the Reconcile Statements screen. The error message did not always appear immediately after sorting transactions. For more information, see Knowledgebase article 70222.

Accounts Receivable

• On the Address tab of the Customers screen, you can now navigate from the National Account No. field to the Business Reg. No. field by pressing Tab.

Accounts Payable

• Fixed a problem that could prevent you from printing invoices or statements to email, if you were printing a large number of invoices or statements. For more information, see Knowledgebase article 20598.
• Fixed a problem that could occur if your system is set up to prevent printing checks with duplicate numbers (on the Options screen, error is specified in the Check for Duplicate Checks field). When you tried to print a check with a duplicate check number, no error message appeared. For more information, see Knowledgebase article 60212.

Inventory Control

• Fixed a problem on the Location Details screen that occurred when drilling down from the Quantity on S/O field for a kitting component item, which prevented the drilldown screen from displaying more than 11 orders. For more information, see Knowledgebase article 58321.
• An item that is in a quarantined lot can no longer be used as a component of an assembly. For more information, see Knowledgebase article 66362.

• Fixed problems that could prevent Day-End processing from completing. The problems occurred if the day-end process included one of the following:

  • Purchase Orders transactions with vendor item details. For more information, see Knowledgebase article 69605.
  • A transaction with a long comment, and the comment included characters from Asian languages (such as Chinese, Japanese, and Korean). For more information, see Knowledgebase article 50484.
• Fixed a problem that could prevent you from posting a shipment if the shipment had previously been saved, and if the shipment included an item with a default price list that displays prices to more decimal places than the number of decimal places used for the functional currency. For more information, see Knowledgebase article 38395.

Purchase Orders

• Fixed a problem with the Receipt Number finder on the Receipt Entry screen, which prevented the Reference column from appearing in the finder and caused some other columns in the finder to be labelled incorrectly. For more information, see Knowledgebase article 63449.

Order Entry

• Fixed a problem that prevented you from opening the Sales History screen from the Order Entry or Shipment Entry screens. For more information, see Knowledgebase article 56111.
• Fixed a problem that occurred when converting a quote to an order, which could prevent some optional fields from being copied to the order. This problem occurred only for optional fields that were not set up to be auto-inserted. For more information, see Knowledgebase article 51566.
• Fixed a problem on the Items/Taxes screen for miscellaneous charges on shipments, which caused the Zoom button to not appear for the Optional Fields option. For more information, see Knowledgebase article 61785.
• Fixed a problem that could prevent some orders from appearing on the Invoice Action report if you printed by order number. This problem occurred if you selected at least one shipped status and at least one invoiced status in the Include Orders section (for example, Partially Shipped and Partially Invoiced). For more information, see Knowledgebase article 54949.
• You can now specify whether a message appears when you post an order with an expected ship date that is later than the Deliver By date. To do this, you edit the [ValidateREQUESTEDEXPSHIPDate] setting in the OE.INI file. For more information, see Knowledgebase article 21367.
• Fixed a problem on the Invoice Entry screen that could cause the system to incorrectly indicate that the customer had exceeded their credit limit. This problem occurred only if you made multiple shipments to the customer for a single order, and you were invoicing one of those shipments.
• Fixed a problem that could cause an error when posting a shipment if Inventory Control is set to cost items during Day End Processing and does not allow negative inventory, and if the Default Quantity Committed option is selected on the O/E Options screen. If you created a shipment for an order, and then later set the Quantity Shipped amount to zero, when you tried to post the shipment, the program displayed the error message "Invalid Input. Negative inventory is not allowed." For more information, see Knowledgebase article 57928.
• Fixed a problem that could incorrectly cause a "Negative inventory levels are not allowed" error message to appear when checking data integrity.

Project and Job Costing

• When using a workstation, adding a new category for a project is now faster. For more information, see Knowledgebase article 61544.

Ops Inquiry

• Fixed a problem with internal usage transactions on the Trans. tab of the IC Item Inquiry screen, which caused "Not Found" to appear in the Trans. Type field. For more information, see Knowledgebase article 64631.

Sales Analysis

• Fixed a problem that prevented you from opening screens in Sales Analysis if you have a 10-digit client ID specified in your Sales Analysis license file. For more information, see Knowledgebase article 20225.

Item Number Change

• Fixed a problem that could occur when combining lotted items, which caused the resulting item to have incorrect information in the Quantity Committed field on the I/C Location Details screen.

^ Back to top

Product Update 3 New Features and Enhancements

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

System Manager

• When exporting a report to an Excel file or a Rich Text Format (RTF) file, you can now specify options for the exported file.
• A new Business Reg. No. field on the Company Profile screen allows you to enter the business registration number for your company. This number is required for tax purposes in some jurisdictions (such as Malaysia and Singapore).

^ Back to top

Product Update 3 Program Fixes

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

Installation

• Fixed a problem that could occur when installing Sage 300 workstation setup in a client-server environment, which prevented the Microsoft Office Access database engine 2007 component from being installed.

Importing and Exporting

• Fixed a problem that prevented you from browsing for records to import or export. When you clicked Browse, the following message appeared: “You can't open this location using this program. Please try a different location.” For more information, see Knowledgebase article 38412.

Visual Process Flows

• By default, custom visual process flows are now saved in the ProcessFlow folder located in the Sage 300 shared data folder. Previously, custom visual process flows were saved in the Programs folder.

  Important! Custom visual process flows can be assigned to users only if they are saved in the ProcessFlow folder located in the shared data folder.

System Manager

• Fixed a problem that prevented you from using Sage 300 if you do not have a multicurrency license, and your Sage 300 Shared Data Directory is shared and accessed using Universal Naming Convention (UNC) format \\server\sharename. For more information, see Knowledgebase article 55780.
• If you print a report to email as a Rich Text Format (RTF) file, the layout and formatting of the report is now correct. For more information, see Knowledgebase article 54811.

Accounts Receivable

• Character limits now work for optional fields on the Customers screen, and for optional fields in details on the Invoice Entry screen. (For example, if you specify a limit of 10 characters for an optional field, it is not possible to enter more than 10 characters in the field.) For more information, see Knowledgebase article 53731.

Accounts Payable

• Updated the 1099 form to meet changed IRS specifications for the 2014 year. For more information, see IRS Publication 1220.

  Note: 1099/CPRS code 11 is no longer used for 1099 forms, and is not included when you print or generate a 1099 form. However, code 11 has not been completely removed from Sage 300. If you previously used this code (for example, in vendor records), it will still appear in Sage 300 until you change it.

• Character limits now work for optional fields in details on the Invoice Entry screen. (For example, if you specify a limit of 10 characters for an optional field, it is not possible to enter more than 10 characters in the field.) For more information, see Knowledgebase article 53731.
• You can now apply credit notes and debit notes to an invoice that is on hold. For more information, see Knowledgebase article 58844.

Inventory Control

• Fixed a problem that occurred when you split a lot, which caused the cost of the newly created lots to have three decimal places, even if you use a currency code that allows fewer than three decimal places. This caused problems such as not being able to invoice a shipment for the lots created in the split. For more information, see Knowledgebase article 51913.
• Fixed a problem that could cause the average cost for an item to incorrectly be set to zero. This problem occurred if you created an adjustment using Both Increase as the adjustment type (increasing both the item quantity and item cost at a location), and then created a shipment that caused the item quantity at the location to become negative. For more information, see Knowledgebase article 56872.

Purchase Orders

• Fixed a problem that prevented you from printing the Transaction List report to a file.

Order Entry

• We have added a new customization option you can set in the OE.INI file, related to converting quotes to orders. The new option lets you specify whether dates in the Deliver By and Exp. Ship Date fields for details on the quote are copied to details on the order. For more information, see Knowledgebase article 21367.
• Character limits now work for optional fields on the Order Entry, Shipment Entry, and Invoice Entry screens. (For example, if you specify a limit of 10 characters for an optional field, it is not possible to enter more than 10 characters in the field.) For more information, see Knowledgebase article 53731.

Project and Job Costing

• Fixed a problem that could prevent you from posting job-related invoices and payments for a project if Completed was specified as the project status. This problem occurred even if No was entered in the Closed to Costs field on the Project Maintenance screen or the Contract Maintenance screen. For more information, see Knowledgebase article 49028.
• When you use the New Contract Wizard to copy a contract, account sets for projects are now copied. Previously, all projects in the new contract were assigned the same account set as the contract. For more information, see Knowledgebase article 53325.
• Transaction dates on the Expense and Time Detail tabs of the Timecards screen now default to the session date, if the session date is between the start date and end date specified for the timecard. Otherwise, transaction dates default to the start date specified for the timecard. For more information, see Knowledgebase article 58974.

Canadian and US Payroll

• Fixed a problem that caused the Payroll Timecards screen to stop responding if you entered an earning or a deduction. For more information, see Knowledgebase article 47787.

Sales Analysis

• Fixed a problem that could prevent you from using Sales Analysis. For more information, see Knowledgebase article 20225.

Account Code Change

• Fixed a problem that could occur if you use Purchase Orders as a stand-alone program, which prevented the General Ledger accounts on the P/O Account Sets screen from being updated with account code changes. For more information, see Knowledgebase article 51511.

Customer Number Change

• Fixed a problem that could occur if you use Sage 300 integrated with Sage CRM. If you combined customer numbers, some quotes or orders for the resulting customer did not appear in Sage CRM. For more information, see Knowledgebase article 46782.

^ Back to top

Product Update 2 New Features and Enhancements

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

Fresh, Modern Look and Feel

We’ve updated a selection of frequently used screens in Inventory Control to make it easier to find information and complete tasks:

• Redesigned buttons (such as the Zoom button and the Finder) are clearer and more meaningful.
• Required fields are now clearly indicated with an asterisk.

Improved Help and Documentation

We've revised Bank Services and Tax Services help to improve search results, enhance the readability of help topics, and make it easier for you to find important information and instructions.

We've also added the following new user's guides, available in Docs\62A\ENG:

• Bank Services User's Guide
• Tax Services User's Guide

This product update also includes French-language versions of:

• Accounts Payable help and the Accounts Payable User's Guide.
• Bank Services help and the Bank Services User's Guide.
• Tax Services help and the Tax Services User's Guide.
• G/L Consolidations help and the G/L Consolidations User's Guide.

System Manager

• On the Current Users screen, the Administrator user can now forcibly sign out users.
• When printing to e-mail, you can now select recipients from your Microsoft Outlook address book.

Inventory Control

• The Sales Statistics screen and the Transaction Statistics screen have been redesigned to provide more information. Both of these screens now display the following:

  • Detailed statistics for all periods in one year, which you select.
  • Statistics for each year for which you have kept statistics.
• Transaction entry screens (Adjustments, Assemblies/Disassemblies, Internal Usage, Receipts, Shipments, and Transfers) now include an Entered By field that indicates who entered the transaction.

Sage CRM Integration

CRM Integration now supports Oracle databases.

^ Back to top

Product Update 2 Program Fixes

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

Report Printing

• Fixed a problem that could cause a “Missing parameter values” message to appear when printing a customized report. This problem occurred if the customized report has a sub report that uses parameters that are declared in the main report, and parameter fields are used in formula fields. For more information, see Knowledgebase article 37341.
• Fixed a problem that could prevent a report from printing completely if the report uses parameters in an Excel spreadsheet. For more information, see Knowledgebase article 47534.

System Manager

• Fixed a problem that could cause a “UI container error” message to appear if you used a keyboard shortcut (such as Ctrl+C) in a table. For more information, see Knowledgebase article 32923.
• Fixed a problem that could prevent you from opening screens in web deployment. This problem occurred if help files were missing from the Web folder in your Sage 300 installation. For more information, see Knowledgebase article 40290.
• Fixed a problem that occurred if you pasted text into a field in a table by pressing Ctrl+V, which caused the cursor to appear near the beginning of the pasted text, rather than at the end. For more information, see Knowledgebase article 39187.
• Fixed a problem with COM APIs that could cause your computer to run out of memory. For more information, see Knowledgebase article 26149.
• Fixed a problem that could cause your computer to run out of memory if you printed a report multiple times without closing the report screen. For more information, see Knowledgebase article 47534.

Accounts Receivable

• Fixed a problem that could prevent you from importing receipts for job-related invoices. The problem occurred if you tried to import multiple job-related invoices, or if you tried to import a job-related invoice with a discount or an adjustment. For more information, see Knowledgebase article 31205.
• Fixed a problem that could prevent you from exporting the Customers report to a CSV, TTX, or TXT file. For more information, see Knowledgebase article 34946.

Accounts Payable

• Fixed a problem that could prevent you from importing payments for job-related invoices. The problem occurred if you tried to import multiple job-related invoices, or if you tried to import a job-related invoice with a discount or an adjustment. For more information, see Knowledgebase article 31205.

General Ledger

• We have improved the message that appears if you try to create a new year, but cannot because a required segment code is missing. The improved message identifies the missing segment code, and provides direction for re-creating the segment code so that you can create the new year. For more information, see Knowledgebase article 40747.
• Fixed a problem in Financial Reporter that prevented you from saving reports in xlsx format. For more information, see Knowledgebase article 44914.

Inventory Control

• Fixed a problem that could cause items to appear on the Aged Inventory report, even if you specified that they should not (for example, items with a cost of zero could appear, even if you specified that the report should include only items with a Non Zero cost). For more information, see Knowledgebase article 37636.
• Fixed a problem that could prevent you from exporting the Posting Journals report to a CSV, TTX, or TXT file. For more information, see Knowledgebase article 34946.
• Fixed a problem on the Items screen that could cause the Items Finder to display no results, even if there were matching results that should have been displayed. This problem occurred if you entered Description in the Find By field, and you specified criteria for one or more optional fields. For more information, see Knowledgebase article 42760.

Sage CRM Integration

• Fixed a problem that caused the scroll bar on the Quotes tab and the Orders tab to not appear, or to appear intermittently. For more information, see Knowledgebase article 27906.
• We have added a message that appears if you update information for a customer or vendor contact, and a contact with the same name already exists in Sage CRM for the customer or vendor. The new message notifies you that there are multiple contacts in Sage CRM with the same name, and advises you to review contacts to ensure that these are not duplicates.

  Note: To enable this message, you must uninstall and then reinstall the Sage CRM Synchronization Component. For more information, see Knowledgebase article 42238.

• Fixed a problem that prevented you from promoting a Sage CRM company to a Sage 300 customer or vendor. For more information, see Knowledgebase article 25999.

Ops Inquiry

• Fixed a problem with the Finder for the Item field on the IC Item Inquiry screen, which could cause results to be displayed with the last column highlighted instead of the first. The problem occurred only when using Ops Inquiry for MS SQL Server. For more information, see Knowledgebase article 37116.
• Fixed a problem on the IC Item Inquiry screen that could cause incorrect information to appear in the Other Locations Qty and Other Locations Avail fields. (These fields appear if you display more than 20 locations on the screen; they display the total of all quantities for locations after the 19th location.) The problem occurred if a location included in the Other Locations fields had a non-zero quantity, and the following location had a quantity of zero. For more information, see Knowledgebase article 42786.
• Fixed a problem on the OE Invoice Inquiry screen that caused receipts and other transaction records to not appear on the Pays/Adjs tab. For more information, see Knowledgebase article 46056.

Customer Number Change

• Fixed a problem that could cause credit card information to be removed from a customer record when you changed or combined the customer’s number. For more information, see Knowledgebase article 32501.

Item Number Change

• Fixed a problem that could occur when combining items, which caused incorrect information to appear in the Base Price and Sale Price fields on the I/C Item Pricing screen. For more information, see Knowledgebase article 46288.
• Fixed a problem that occurred when combining lotted items, which prevented lot number details from being combined correctly. For more information, see Knowledgebase article 48419.

Sage 300 Intelligence Reporting

• A LanPak license is no longer required to open Sage 300 Intelligence Reporting from the Start List.

^ Back to top

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

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.

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 Intelligence Reporting.

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.

^ Back to top