» Sage 300 ERP 2012 Product Update 1 Release Notes

Sage 300 ERP 2012 Product Update 1 Release Notes

Product Update 1 contains a modified version of one or more Sage 300 ERP 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 ERP.

Updating Programs

Important! This product update contains database changes for Project and Job Costing. After installing the update, you will need to reactivate your data for this program for version 2012.

Important! This update includes changes to the Sage 300 ERP Portal. If you have installed the portal, the installation program will need to stop and restart Internet Information Services (IIS) and the Sage 300 ERP Tomcat service.

Note: After installing this update, you should clear your browser’s cache. (Some fixes included in the update will not take effect until you do.)

Upgrading to Later Versions

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

Compatibility with Sage Programs

Sage 300 ERP is now compatible with Sage Fixed Assets 2013.

For a complete list of compatible programs, database platforms, and operating systems, see the Sage 300 ERP 2012 Compatibility Guide on the Sage Customer Portal.

SAP Crystal Reports® Runtime Engine

As described in the 2012 Release Notes, reports in the Sage 300 ERP Desktop are now printed using the SAP Crystal Reports® runtime engine for .NET Framework 4, which is installed with Sage 300 ERP.

• Potential issues when reporting via macros. The COM API for SAP Crystal Reports® is no longer supported by SAP, and is not included in the SAP Crystal Reports® runtime engine for .NET Framework 4, which is installed with Sage 300 ERP. (SAP Crystal Reports® now supports only .NET and Java interfaces.)

  If you use any macros that write to the SAP Crystal Reports® COM API, you must modify these programs to use the .NET interface or the Sage 300 ERP COM API.

  • For developer documentation on using the Sage 300 ERP COM API, visit the Sage 300 ERP Development Partner Wiki at http://dppwiki.sage300erp.com.
  • For more information about reporting via macros, including a sample macro to print O/E quotes, see http://smist08.wordpress.com/2012/09/15/reporting-via-macros.
• Slower performance when printing reports. We are continuing to work with SAP to resolve the issue of slower performance when printing reports using the updated SAP Crystal Reports® runtime engine for .NET Framework 4. The previous version of the runtime engine is no longer supported by SAP, so this change is required to ensure continued support for all reporting features.

Errors and Omissions in Release Documentation

Sage makes every effort to provide accurate product documentation, and we apologize for any inconvenience caused by the following errors and omissions in the release documentation for Sage 300 ERP 2012.

• In the 2012 Release Notes, we neglected to mention that if you use Pervasive PSQL, Sage 300 ERP 2012 only supports Pervasive PSQL version 11.2 and later. Older versions of Pervasive PSQL (version 11.0 and earlier) are not supported. To learn more about supported platforms and system requirements for Sage 300 ERP 2012, please review the Sage 300 ERP 2012 Compatibility Guide.
• In the 2012 Release Notes, we noted that reports in the Sage 300 ERP Desktop are now printed using the SAP Crystal Reports® runtime engine for .NET Framework 4, which is installed with Sage 300 ERP. The text that followed this note implied that you require the 2011 version of SAP Crystal Reports® to create and customize reports and forms for Sage 300 ERP. This is not the case. You can continue to use the 2008 version of SAP Crystal Reports® to edit or create reports for Sage 300 ERP 2012.
• We did not enhance comment entry in Order Entry as was erroneously reported in the 2012 Release Notes, Order Entry help, Portal Learning Center help, and the What's New Guide.

Viewing Help for EFT Direct Products and Financial Link Professional

The Windows Help program (WinHlp32.exe) is not included in Microsoft Windows Vista and later versions of Windows, such as Windows 7 and Windows 8.

To view the help files for our EFT Direct and Financial Link Professional programs, download and install the Windows Help program from the Microsoft Download Center. Be sure to install the correct program for your version of Windows:

• WinHelp for Windows Vista
• WinHelp for Windows 7
• WinHelp for Windows 8

Product Update 1 New Features and Enhancements

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

To watch video feature tours of new features and enhancements in the Sage 300 ERP 2012 release and in Product Update 1, visit our YouTube channel at www.youtube.com/Sage300Doc.

Company Colors

If you use Sage 300 ERP to manage multiple companies, you can now assign a unique color to each company. This color appears in a border around the Sage 300 ERP desktop and screens, making it easier to see which company's information you are viewing and avoid data entry errors.

• On the Database Setup screen, select the Assign Colors Automatically option to assign colors to all companies you have set up.
• On the Edit Database Profile screen, you can change the color assigned to a specific company, or select No Color if you want the border around that company's screens to use your default system colors.

Sage 300 ERP Payroll Enhancements

For information about new features and changes in the Canadian and US versions of Sage 300 ERP Payroll 2012 (also called "Sage HRMS Payroll for Sage 300 ERP 7.0"), and for information about upgrading from previous versions of Sage 300 ERP Payroll, see the Sage 300 ERP Payroll Help and release documentation.

Note: Sage 300 ERP Payroll is not included in Sage 300 ERP 2012 Product Update 1. Installation files for Canadian Payroll and US Payroll are available separately.

Important! If you use Pervasive PSQL, Sage 300 ERP Payroll requires version 11.2 or later. If you are using an earlier version of Pervasive PSQL, you must upgrade your database software before installing to avoid activation errors or database corruption. If you attempt to activate Sage 300 ERP Payroll using an unsupported version of Pervasive PSQL, you may experience activation errors and data corruption that prevent all users from signing in to Sage 300 ERP. For information about resolving this problem, see Knowledgebase article 210-1003219.

Online Paystubs and Payroll History for Employees

If you use Sage 300 ERP Payroll 2012, you can now publish payroll information to a secure website, enabling your employees to sign in, review, and print their paystubs and payroll history.

Online paystubs and payroll history are powered by Sage Source, a Sage-hosted web-based service and benefits portal for Sage customers and employees. To learn more about Sage Source and how you can use it to leverage online tools and services from both Sage and third party providers, visit http://na.sage.com/sage-source.

Sage 300 ERP Payroll customers will receive an email message with instructions for getting started. If you have questions, contact your business partner or Sage 300 ERP product support at http://na.sage.com/sage-na/support-and-training.

Improved Help and Documentation

We've revised Inventory Control and General Ledger 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\61A\ENG:

• Inventory Control User's Guide
• General Ledger User's Guide
• Financial Reporter User's Guide

This product update also includes French- and Chinese-language versions of Purchase Orders help and the Purchase Orders User's Guide.

New Report Designer Add-In for Sage 300 ERP Intelligence Reporting

A new Report Designer add-in enhances the Report Designer module by presenting an alternative to the current report layout generator, allowing you to take control of all design aspects of your reporting layouts.

You use the add-in to create reusable pieces (Excel functions) that you can assemble to create a report. These pieces communicate with a new in-memory processing engine that significantly improves reporting speed and performance.

Note: The Report Designer add-in for Sage Intelligence Reporting is not included in Sage 300 ERP 2012 Product Update 1. An installation file is available separately, and can be downloaded from the Sage Customer Portal (https://customers.sagenorthamerica.com) or the Sage Partner Portal (https://partners.sagenorthamerica.com).

Inventory Control

Ability to Ensure that Serial Numbers are Unique to Individual Items.

In earlier versions, Inventory Control allowed you to assign the same serial number to multiple items. This is now a default that you can override.

To ensure that no serial number is assigned to more than one item, you edit the IC.INI file. In the General section of the IC.INI file, change the value of the AllowSameSerialForMultiItems switch to No.

Note: Setting this switch to No does not change existing assigned serial numbers, so any existing duplicated serial numbers remain.

Sage CRM Integration

When viewing a Sage 300 ERP customer on the Company Summary screen, a new Item Inventory button appears. You can click this button to look up Sage 300 ERP inventory items in Sage CRM, and then create a new quote or order for an item.

For more information about using the inventory item lookup feature, see the Sage CRM Integration Guide.

Sage 300 ERP SDK

The AccpacReport COM object now supports exporting reports to Microsoft Excel .xls and .xlsx formats. For more information, see the Sage 300 ERP Development Partner Wiki and http://sdata.sage.com.

^ Back to top

Product Update 1 Program Fixes

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

System Manager

• Restored the ability to select an export format and destination after clicking the Export button in the print preview window for a report. (This feature was available in previous versions, but was not available in the 2012 release due to changes in the SAP Crystal Reports® runtime engine for .NET Framework 4, which is installed with Sage 300 ERP 2012.)

  In the 2012 release, clicking the Export button opened a Save As window, which allowed you to save the exported report as a file. Now, clicking the Export button opens an Export window, which you can use to select a format and destination for the exported report.

  • Available destinations are Application, Disk File, and Microsoft Mail.
  • Available formats include Microsoft Excel and Word (multiple formats), plus PDF, HTML, XML, CSV, RTF, TTX, and TXT.

  For more information, see Knowledgebase article 210-1002734.

• Fixed a problem that prevented printing certain reports to a printer. When you tried to print a report that required you to enter report parameters, the parameter screen did not appear if the print destination was set to Printer.

  Changes to the SAP Crystal Reports® .NET SDK prevented the parameter screen from appearing. Now, a new parameter screen appears when print destination is set to Printer. For more information, see Knowledgebase article 210-1003040.

• Fixed a problem that caused the License Manager to incorrectly display Unauthorized as the status for some licenses. When activating licenses with a seven-digit Client ID, the Status column on the Licenses tab incorrectly displayed Unauthorized instead of Current. For more information, see Knowledgebase article 210-1003140.
• Fixed a problem that caused third-party programs created using the XAPI to consume an additional LanPak license. When the problem occurred, the LanPak Users screen incorrectly displayed an additional current user, even if the program signed in with the user ID of a user who had already signed in to Sage 300 ERP. For more information, see Knowledgebase article 210-1003433.
• Fixed a problem that could prevent you from starting third-party programs created using the XAPI. The problem occurred if you tried to open multiple companies with the program. Even if you had enough IAP licenses, the program displayed the error message: “there are no IAP Licenses left at this time.” For more information, see Knowledgebase article 210-1004000.

Bank Services

• Fixed a problem that could cause the Reconcile Statements Summary to be out of balance. Previously, you could use the Reverse Transactions screen to select and reverse a bank entry that was reconciled and cleared. Now, you cannot select a bank entry on the Reverse Transactions screen if it has been cleared. To reverse the bank entry, you must first use the Reconcile Statements screen to change its status to Outstanding.

Accounts Payable

• Fixed a problem that could occur when using the A/P Print Checks screen to print checks. If you selected a large number of checks, a "UI container" error message appeared when printing or previewing, and the program stopped responding. For more information, see Knowledgebase article 210-1003500.

Accounts Receivable

• Fixed a problem that could cause inquiry screens to stop responding. The problem occurred only if you tried to use a custom screen to open the Customer Inquiry screen or the Document Inquiry screen multiple times.
• Improved the performance of the A/R Statements/Letters/Labels screen. When reprinting A/R statements, the program now produces the report faster.
• Fixed a problem that allowed users to enter a negative miscellaneous receipt amount on the A/R Receipt Entry screen, which created an incorrect balance in Bank Services. For more information, see Knowledgebase article 210-1000209.
• Fixed a problem that could cause the A/R Customer Inquiry screen or A/R Document Inquiry screen to stop responding. The problem occurred if you opened these screens from a screen developed by a third-party. For more information, see Knowledgebase article 210-1001230 or 210-32204.

General Ledger

• Fixed a problem that could cause information to be excluded incorrectly from the posting journals report. If a posting sequence included any entries to which you did not have access, the whole posting sequence was excluded from the report. For more information, see Knowledgebase article 210-1003729.

Inventory Control

• Fixed a performance issue that occurred when using the I/C Update Item Pricing screen to update item pricing for databases with large numbers of items. Previously, if you selected Item Number on the Select by list, the program searched all item records within the range of price list codes you specified, regardless of the range of item numbers you specified. Now, the program only searches and updates item pricing for records within the range of price list codes and item numbers you specify. For more information, see Knowledgebase article 210-1003616.
• Fixed a problem that occurred after deleting an inactive Bill of Material (BOM). When printing the I/C Item Valuation report, the deleted BOM appeared in the report, and displayed the item number and description from the item listed above it in the report.
• Fixed a problem that caused an "Error Code 5" error message to appear when trying to open Inventory Control reports. If you used the UI Profile Maintenance screen to create a custom profile ID for the I/C Stock Transactions Report, users to whom you assigned this profile ID received the error message when opening other Inventory Control reports. For more information, see Knowledgebase article 210-1002722.
• Fixed a problem that could cause a "Fractional quantities are not allowed" error message to appear when generating an inventory worksheet. The problem could occur if all the following conditions were true:
  • Fractional quantities were not allowed in Inventory Control.
  • You entered a Purchase Orders receipt using a different item unit of measure than the UOM used for the corresponding purchase order (for example, you received Each on the receipt for a purchase order in Dozen).
  • The quantity received was a fraction of the unit on the purchase order (for example, 4 Each).

  Now, a receipt is not posted if it would result in a fractional quantity that is not exactly representable in the order unit (that is, if the resulting fractional quantity cannot be calculated within 4 decimal places). For more information, see Knowledgebase article 210-1002023.

• Fixed a problem that occurred if you posted lot splits or combine transactions, or posted lot reconciliations before you ran Day End Processing. The lot costs would be incorrect. Now, you cannot post these transactions before running Day End Processing to update the item and location, and an error message appears if you try to do so.
• Fixed a problem that caused an "Extended Cost / Revenue cannot be less than zero" error message to appear after day end processing if you posted a job-related quote with a negative extended cost or revenue amount.

  Now, a warning message appears instead of an error after you post the quote, and may appear after you run Day End Processing. The message includes the contract, project, category, and resource (for standard projects), and indicates that the extended cost or revenue was not saved because it cannot be negative.

• Fixed a problem on the I/C Physical Inventory Quantities screen that could cause the Quantity Counted to be copied from one line to the next. The problem occurred if you entered or changed the Quantity Counted, and then navigated to the next line by pressing the Tab key. For more information, see Knowledgebase article 210-1003866.
• Fixed a problem on the I/C Location Details screen, which could occur when drilling down to location details from the Quantity on P/O field or the Quantity on S/O field. If the item number included a percent % character, no details were displayed when you drilled down. For more information, see Knowledgebase article 210-1000124.

Purchase Orders

• Fixed a problem that could occur when using the I/C Item Labels screen to print item labels for a Purchase Orders receipt. If the receipt included 32 or more items, item labels were printed in a different order than the order in which items appeared on the receipt.
• Fixed a problem that caused a "Requisition Invalid field index" or "ID is not a valid field ID" error message to appear when using the Requisition Number Finder on the Create P/O from Requisition screen (accessed from the Purchase Order Entry screen).

  The problem occurred if a third-party application used the OVERRIDE_SUBCLASS and MAKELONG protocols for subclassing and adding a calculated field. For more information, see Knowledgebase article 210-1002472.

Project and Job Costing

• Fixed a problem that could cause a "Budget Detail. Record already exists" error message to appear when selecting a category on the Budget Maintenance screen. For more information, see Knowledgebase article 210-1000495.
• Fixed a problem that could cause an error message to appear when selecting the budget set year in the PJC Budget Maintenance screen.

  If you selected the budget set year before specifying the contract, project, and category, and if budget costs were already assigned to a selected contract and year, the program displayed all budget costs as zero. However, when you edited the costs, and then clicked Add, you received the message "Budget Header. Record has been modified by another program." Now, no error message appears.

Sage CRM Integration

The following program fixes for Sage CRM are included with this product update:

• Fixed a problem that could cause performance issues in Sage CRM, and in some cases, caused error messages to appear, or caused the program to stop responding. The problem occurred because the integrated Quotes and Orders pages in Sage CRM reused session IDs for multiple processes. Now, the integrated pages use IIS to generate unique session IDs. For more information, see Knowledgebase article 210-1003574.
• Fixed a problem that allowed a Sage CRM user to delete an opportunity in Sage CRM for which there are outstanding amounts in Sage 300 ERP. Now, if there are outstanding amounts for an opportunity, an error message appears when a Sage CRM user attempts to delete the opportunity. For more information, see Knowledgebase article 201-1001849.
• If Sage CRM and Sage 300 ERP are installed on separate servers, the integrated Quotes and Orders screens are now supported in Internet Explorer, Firefox, Chrome, and Safari. For more information, see Knowledgebase article 210-9000475.
• Improved performance when promoting a customer to Sage 300 ERP, if your Sage 300 ERP database includes a large number of O/E transactions (shipments, invoices, credit notes, or debit notes). For more information, see Knowledgebase article 210-1004017.

Ops Inquiry

• Fixed a problem that prevented Ops Inquiry from saving changes to column order on the Stock Card-Detail tab of the IC Item Inquiry screen. For more information, see Knowledgebase article 210-1003023.
• Fixed a problem on the I/C Item Inquiry screen that could cause incorrect information to appear in the Total Quantity and Total Available fields. The problem occurred when viewing an item for which there was inventory at more than 20 locations. For more information, see Knowledgebase article 210-1003964.

Sales Analysis

• Fixed a problem that prevented Sales Analysis screens from appearing if the Client ID on the Sales Analysis license was greater than 2147483647. For more information, see Knowledgebase article 210-1002917.

Account Code Change

• Fixed a problem that caused the following error message to appear when combining allocation accounts:

  "G/L Acct Alloc Instructions: Internal Error: field number is out of range."

  Note: After combining allocation accounts, Account Code Change does not automatically update the percent allocated to the account. To set allocation to 100%, open the G/L Accounts screen, and on the Allocation tab, change the amount(s) in the Percent column so that the Total Percent field displays 100.

  For more information, see Knowledgebase article 210-1002285.

^ Back to top