» Sage 300 ERP 2012

Sage 300 ERP 2012 Release Notes

Thank you for choosing a Sage accounting product.

This file contains important information about Sage 300 ERP, including information about product changes that are not in the documentation.

General Information

• The names of many Sage products changed in 2012. For a list of product name changes, and for general information about how the changes affect the Sage products you use, visit na.sage.com/sage-na/company/brand.

  Note: If you are integrating Sage 300 ERP 2012 with a pre-2012 version of a Sage Fixed Assets product, the name you select on the Product list on the Fixed Assets Options screen may have changed. For more information, see the Sage Fixed Assets Integration with Sage 300 ERP section in this document.

• Sage 300 ERP 2012 tables now feature alternate row shading (or "color banding") to help you quickly scan table rows for information.
• Sage 300 ERP 2012 supports upgrades only from versions 5.6 and 6.0.
• You require version 2012 (internally versioned as 6.1A) of all core programs that you plan to use, with the following exceptions:
  • Canadian Payroll 6.0
  • US Payroll 6.0
• If you are upgrading from a prior version, you must upgrade all Sage 300 ERP programs (except Canadian Payroll and US Payroll) to 2012 at the same time. With the exception of payroll programs, Sage 300 ERP 2012 programs do not work with programs from earlier versions.
• You can deploy Sage 300 ERP 2012 in a web portal that includes the following features:
  • Enhanced Inquiry features
  • "Snapshots" that present your General Ledger, Accounts Payable, and Accounts Receivable data graphically
  • Convenient shortcuts to the tasks and reports you use most often

  All these features are customizable by individual users. For information about requirements and known issues, see Sage 300 ERP Portal.

• If you use the Web Deployment option (distinct from the new portal), note that:
  • Sage 300 ERP Web Reporting by Crystal is not supported on Windows Server 2008. The server on which you deploy Sage 300 ERP over the web must use Windows 2003.
  • Version 2012 does not support the DCOM remoting channel for Web Deployment.

  • Adobe Reader is now required to view and print reports in PDF format. To download the latest version of the free Adobe Reader software, visit http://get.adobe.com/reader.

• You need a unique activation code for each Pervasive installation.

  If you use Pervasive PSQL as the database engine for your company and system databases, you must have a unique activation code for each computer on which you install this software. You cannot install the software with a code that has been used on another machine.

  A unique activation code is issued for each copy of the software that you purchase. (For more information about Pervasive licensing requirements, see the chapter on license administration in the Pervasive PSQL User Guide.)

• 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.
  • You now require SAP Crystal Reports® for Sage 300 ERP to customize Sage 300 ERP reports and forms. If you create or customize your own reports, you can take advantage of the following features in the 2011 version of SAP Crystal Reports®:
    • Improved report grouping, sorting, and filtering
    • A new tamper-proof file format (.RPTR)
  • If your print destination is set to File, a new Export Reports screen appears when you print reports. You now navigate to the location where you want to save the file, specify a file name, and then use the Save As Type option to select the format for the file. However, unlike earlier versions, you must export the entire report. The new screen has no option for selecting a range of pages.
  • You may experience 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. We are working with SAP to resolve this issue.
• Sage 300 ERP 2012 includes a new way of managing work and opening screens: visual process flows.

  A visual process flow is an interactive workflow diagram that shows the steps required to complete a complex task or process. You can click each step to access the screen or feature that allows you to perform the step.

  Sage 300 ERP includes some standard process flows that are ready to use. You can also create your own custom process flows.

  A visual process flow must be assigned to a user before that user can view and use it. You use the Assign Visual Process Flows screen to assign process flows to users.

• If you use workstation setup, you must also run Sage 300 ERP Intelligence Reporting workstation setup (located in BX61A\WSSetup) on every workstation where you will view and use Intelligence Reporting screens.

Sage Advisor Update and Product Enhancement Program

Sage 300 ERP 2012 includes two new features designed to improve your experience as you use and update Sage products:

• New Sage Advisor Update console. Sage 300 ERP 2012 includes Sage Advisor Update, a new console that notifies you when updates are available for the Sage products you use. You can use this console to set notification options, review information about available updates, download updates, and monitor the status of your Sage Business Care account.

  After you install Sage 300 ERP 2012, a Sage Advisor Update icon appears in your taskbar tray. You can click this icon at any time to view the Sage Advisor Update console.

  Note: Installing updates can affect customizations or integrated products. If you have questions about how installing an available update may affect your software, contact your Sage business partner.

• New Sage Advisor Product Enhancement Program. Sage 300 ERP 2012 also includes the Sage Advisor Product Enhancement Program (PEP). Designed to help us better meet the needs of our customers, PEP gathers information about how customers use Sage 300 ERP. We use this information to develop new features and improvements.

  PEP collects information anonymously, and does not collect any private data from your databases. The information is sent to Sage over a secure connection, and is used for internal purposes only.

  To learn more about how information is collected and used, see the Sage Privacy Policy, available at na.sage.com/Sage-NA/privacy-policy.

  If you do not want Sage to collect information about your system, you can opt out of PEP from the System Information screen.

Installing Sage 300 ERP

For detailed instructions on installing Sage 300 ERP, see the Sage 300 ERP Installation and Administration Guide.

Note: Version 2012 installs components that support the deployment of the Sage 300 ERP Portal. The installation program installs Java 6 Runtime Environment and Sage 300 ERP Tomcat silently. (Tomcat is installed as a private instance in your Program Files folder under \Common Files\Sage\Sage 300 ERP\Tomcat.)

Important! If you are using Windows Vista, Windows 2008, or Windows 7, you must log in as the Windows administrator user the first time you run Sage 300 ERP.

^ Back to top

Removing Sage 300 ERP

Before removing Sage 300 ERP, you must:

• Close all instances of the Sage 300 ERP Desktop.
• Close all applications that integrate with Sage 300 ERP.
• Stop all Sage 300 ERP services that are running, such as Sage Accpac .Net Remoting and Sage Accpac Tomcat.

To remove Sage 300 ERP 2012, use Windows' Control Panel, as follows:

• If you are using Windows XP, open Add Or Remove Programs, select Sage 300 ERP 2012, and then click Remove. At the message asking whether to remove the program completely, click Yes.
• If you are using Windows Vista, or later, from Programs And Features, open Uninstall Or Change A Program, and then double-click Sage 300 ERP 2012.

To remove individual Sage 300 ERP programs, use Windows' Control Panel, as follows:

• If you are using Windows XP, open Add Or Remove Programs, select Sage 300 ERP 2012, and then click Change. Click Modify, and then use the Select Features screen to select the programs you want to install and clear the selections for programs you want to remove.
• If you are using Windows Vista, or later, from Programs And Features, open Uninstall Or Change A Program. Click Sage 300 ERP 2012, and then click Change. (Do not double-click Sage 300 ERP 2012.) Click Modify, and then use the Select Features screen to select the programs you want to install and clear the selections for programs you want to remove.

^ Back to top

System Manager

Important! If you will be creating data on a 64-bit version of a supported Windows operating system, refer to the Sage 300 ERP Upgrade Guide for information on locating and using the 32-bit version of the ODBC Administrator.

New Features and Improvements

System Manager 2012 includes the following significant changes:

• Improved LanPak licensing. You need only one LanPak to open multiple company databases from the Sage 300 ERP Desktop or from the portal.

  Note: You must open the databases from the same workstation using the same Windows user profile.

• Improved Finder results when using Microsoft SQL with case-sensitive collation. If you use Microsoft SQL with case-sensitive collation, you can now set up the Finder to show records in search results that do not exactly match the case of text you enter in the Filter field. (In previous versions, records that did not exactly match the case of the text you entered did not appear in results. For example, if you searched for records that contain "client," records that contain "Client" or "CLIENT" did not appear in results.)

  To set up the Finder so that search results include all case variations of text you specify:

  1. In the Sage 300 ERP Runtime folder, edit a4w.ini.
  2. Under [A4WSQLS], add "ForceCaseInsensitiveLike=yes".

  For more information, see Knowledgebase article 201-1000971.

• New recommended collation method for Microsoft SQL databases. The Installation and Administration Guide (in Chapter 3) now recommends using a binary collation method, such as Latin1_general_bin, for Microsoft SQL databases.
• Changes to product activation, including validation of client ID based on activation code. Sage 300 ERP now validates client ID based on the activation code provided by Sage. If you need to change your client ID, open the License Manager screen, and on the License Information tab, click the Change button.

  To enter serial numbers and activation codes for all Sage 300 ERP 2012 programs, use the License Manager screen. If you need to enter license information for pre-2012 programs and OEM products, use the License Information screen.

• New Assign Visual Process Flows screen. Sage 300 ERP 2012 allows you to create and use interactive workflow diagrams called visual process flows.

  A visual process flow must be assigned to a user before that user can view and use it. You use the Assign Visual Process Flows screen to assign process flows to users.

Known Issues

• Database Setup supports Portal databases created using Microsoft SQL Server (full or Express edition) only.  In Database Setup, the Database Format field on the Configure Portal screen is now read-only and is set to Microsoft SQL Server.

  If you are upgrading from version 6.0A, and you used Pervasive PSQL to create your Portal database, you must recreate your Portal database in Microsoft SQL Server. To create your Portal database, follow the instructions in the Sage 300 ERP Installation and Administration Guide.

  If you are upgrading from version 6.0, and you used Microsoft SQL Server to create your Portal database, your database will be automatically upgraded for use with the 2012 Portal, and all existing settings will be preserved.

• You need a unique activation code for each Pervasive installation. If you use Pervasive PSQL as the database engine for your company and system databases, you must have a unique activation code for each computer on which you install this software. You cannot install the software with a code that has been used on another computer.

  A unique activation code is issued for each copy of the software that you purchase. For more information about Pervasive licensing requirements, see the chapter on license administration in the Pervasive PSQL User Guide.

^ Back to top

Sage 300 ERP Portal

New Features and Improvements

Version 2012 of the Sage 300 ERP Portal includes the following new features and improvements:

• A new Sage 300 ERP plugin supports browsers other than Internet Explorer. The portal now supports current versions of Internet Explorer, Firefox, Chrome, and Safari.

  If you open the portal using a browser other than Internet Explorer and you do not have Sage 300 ERP installed on your workstation, you must install the Sage 300 ERP plug-in when the browser prompts you to install missing plug-ins.

• New data sources and query templates.

  • Use the new O/E Transactions data source and two new query templates to quickly and easily retrieve sales history and invoice information from your company database, and to create and save sales reports that meet your own needs.
  • Use the new P/O Transactions data source and two new query templates to look up purchase orders and purchase order transaction history, and to create and save purchasing reports.
  • Use the new I/C Transactions data source and two new query templates to look up information on inventory items, quantities, costs and transaction history, and to create and save inventory reports.

  If you are new to Sage 300 ERP Inquiry, see the topics under "Inquiry" in the Learning Center for more information.

Program Requirements

• The Sage 300 ERP Portal:
  
  • Uses Java technology to support "back-end" server processes. It requires Apache Tomcat 6 and the 32-bit version of the Java 6 Runtime Environment, which are installed automatically if you select the Portal option during installation. Apache Tomcat is installed as a Windows service with the name Sage 300 ERP Tomcat.

    Note: 64-bit versions of the Java Runtime Environment are not supported.

  • Uses its own database to store portal-specific information, such as landing-page customizations, shortcut preferences, and other settings for users. We recommend that you set up the portal database in a database separate from the Sage 300 ERP company database.
• You must use Microsoft SQL Server (full or Express edition) to create your portal database.
• If you use Internet Explorer as your browser, note that you must use Internet Explorer 9 or later to open the portal.

Additional Information

• Use the Configure Portal screen, available in the Database Setup utility, to create a connection to the portal database.
• Sage 300 ERP uses the port number to identify particular Microsoft SQL Server or SQL Express databases on a server. If you have more than one instance, you must assign a unique port number to each instance in your database software, and then specify the port number for the portal database in the Configure Portal screen.

Known Issues

• After adding a new location in Sage 300 ERP, the location will appear on the Location Finder list, but it may not appear on the Advanced Search list for the Location Finder until the new location has been used in an order. (This issue occurs in the new screens that appear in the Sage 300 ERP Portal. It does not occur in the Sage 300 ERP Desktop.)
• Crystal-based reporting is not supported in the Sage 300 ERP Portal for company data stored in an Oracle database. Support will be added in a future release.
• The portal uses location information to determine formats for dates, times, and numbers that appear in the portal. However, because they have different capabilities and limitations, different browsers may supply inconsistent location information to the portal. For example, Internet Explorer can identify system and user localization settings, while other browsers rely on browser language settings. Although the portal uses settings that are consistent among all browsers wherever possible, if your browser's list of preferred languages is different from the system's regional settings, dates, times, and numbers may occasionally appear in unexpected formats.
• In Internet Explorer 9, clicking the Accelerator button may cause Sage 300 ERP web screens to stop responding. (This button appears when you highlight text on web screens.) This is a known issue in Internet Explorer 9 for applications that use the Google Web Toolkit (GWT).

  To work around this issue:

  1. In Internet Explorer, click Tools > Internet options > Advanced.
  2. In the Browsing group, clear the option Display Accelerator button on selection.

^ Back to top

Troubleshooting the Sage 300 ERP Portal

Note: The installation program sets required properties in IIS, and you should not have to change them. For more information about these settings and for troubleshooting tips, see Chapter 5 in the Installation and Administration Guide.

^ Back to top

Bank Services

New Features and Improvements

Bank Services 2012 is compatible with all Sage 300 ERP 2012 programs.

Known Issues

There are no known issues.

^ Back to top

Tax Services

New Features and Improvements

Tax Services 2012 is compatible with all Sage 300 ERP 2012 programs.

Known Issues

There are no known issues.

^ Back to top

G/L Subledger Services

New Features and Improvements

G/L Subledger Services 2012 is compatible with all Sage 300 ERP 2012 programs.

Known Issues

There are no known issues.

^ Back to top

Accounts Receivable

New Features and Improvements

Accounts Receivable 2012 includes the following new features and improvements:

• Changes to Receipt Entry. You can now see and edit the Deposit Date on the Receipt Entry screen.
• A new Print O/E Invoice button that allows you to print O/E invoices directly from the A/R Document Inquiry screen.
• A new Same As Customer Address option on the A/R Credit Card Information screen. If you use Payment Processing, you can select this option when adding a new credit card to automatically fill in billing details with name and address information from the customer record.

Known Issues

There are no known issues.

^ Back to top

Accounts Payable

New Features and Improvements

Accounts Payable 2012 includes the following new features and improvements:

• US tax forms updated. The 1099 and 1096 forms have been updated to meet the following changed IRS specifications for 2011:
  • The alignment and positioning of some information has been changed so that it prints in the correct place on these forms.
  • For 1099/CPRS code 14 (gross proceeds paid to an attorney), the minimum to report is now $600.

Known Issues

There are no known issues.

^ Back to top

General Ledger

New Features and Improvements

General Ledger 2012 includes the following new features and improvements:

• Includes Sage 300 ERP Intelligence Reporting. If you install General Ledger, Sage 300 ERP Intelligence Reporting is automatically installed.
• New Exclude Inactive Accounts option for the Chart of Accounts report. You can now exclude inactive accounts from the Chart of Accounts report.
• New batch reversal feature. You can now reverse a whole batch or an individual entry in a batch.

Known Issues

There are no known issues.

^ Back to top

Inventory Control

New Features and Improvements

Inventory Control 2012 includes the following new features and improvements:

• A new Include Inactive Items option on the Inventory Worksheet screen and the Inventory Reconciliation screen. This option allows you to specify whether or not to include inactive items on the reports generated from those screens.
• An alternate method for generating physical inventory adjustments for standard cost items.

  In earlier versions, Sage 300 ERP used an item's standard cost when computing inventory adjustments for the Generate Inventory Worksheet form. Standard cost is now a default that you can override if you require a different inventory valuation.

  To adjust standard cost items using the average (actual) cost, rather than the standard cost, when generating inventory worksheets, you edit the IC.INI file. In the Physical Inventory section of the IC.INI file, change the value of the UseActualCostForPI switch to Yes. The next time you use the Generate Inventory Worksheet form to adjust inventory, the adjustments will be based on average cost.

• New security authorizations.

  A new portal-related Sage 300 ERP Inquiry security authorization allows you to query Inventory Control data in the Sage 300 ERP Portal. If you also have Export Processing authorization for Inventory Control, you can print or export the results of these queries.

• A new Inventory Control data source for Sage 300 ERP Inquiry.

  You can now use Sage 300 ERP Inquiry (in the portal) to look up information on Inventory Control items and to create ad hoc item reports.

Known Issues

• When running Day End Processing, if you have deleted an opportunity in Sage CRM for which there are outstanding quotes in Sage 300 ERP, processing fails and an error message informs you that the opportunity could not be found.

  To delete expired quotes and complete Day End Processing:

  1. In Sage 300 ERP, delete quotes associated with the deleted opportunity. (A "Failed to update Sage CRM Opportunity" error message appears, but the quotes are deleted.)
  2. Run Day End Processing again.
• When printing the Inventory Worksheet, if you clear the option to include inactive items, the summary line at the end of the report (for example, "72 items printed") displays an incorrect number of items printed. For more information, see Knowledgebase article 210-1002288.

^ Back to top

Order Entry

New Features and Improvements

Order Entry 2012 includes the following new features and improvements:

• New security authorizations. Order Entry 2012 includes a new portal-related Sage 300 ERP Inquiry security authorization. This authorization allows you to query Order Entry data in the Sage 300 ERP Portal. If you also have Export Processing authorization for Order Entry, you can print or export the results of these queries.
• A new Order Entry data source for Inquiry. You can now use Inquiry (in the portal) to look up information on Order Entry transactions, including:
  • Sales by customer, range of dates, or territory.
  • Cycle time for customer orders.
  • Average sales in a specific date range.
  • Order Entry invoices posted to Accounts Receivable within a specific date range.
• A new Capture Payments With Invoices screen. If you use Payment Processing, this new screen appears in O/E Transactions. You can use it to capture and invoice pre-authorized credit card payments for multiple Order Entry documents in a single batch.
• A new Copy Current Order option on the File menu on the Order Entry screen. This option allows you to copy an order directly from the Order Entry screen.
• A new field beside the On Hold option that allows you to enter a note about why you are placing an order on hold.
• A new Entered By field on transaction entry screens (Order Entry, Shipment Entry, Invoice Entry, and Credit/Debit Note Entry), which indicates who entered the transaction.
• A new Deliver By field that allows you to enter a date on an order to indicate when your customer would like the order delivered.
• A new Create PO button on the Order Entry screen that allows you to create a purchase order based on an order on Order Entry.
• Improved help. We've revised Order Entry help to improve search results, enhance the readability of help topics, and make it easier for you to find important information and instructions.
• Shipment tracking fields on the Order Entry screen are in a more convenient location. The Ship Via and Tracking No. fields now appear on the Order tab (instead of the Customer tab).

Known Issues

There are no known issues.

^ Back to top

Purchase Orders

New Features and Improvements

Purchase Orders 2012 includes the following new features and improvements:

• New security authorizations. A new portal-related Sage 300 ERP Inquiry security authorization allows you to query Purchase Orders data in the Sage 300 ERP Portal. If you also have Export Processing authorization for Purchase Orders, you can print or export the results of these queries.
• A new Purchase Orders data source for Sage 300 ERP Inquiry. You can now use Sage 300 ERP Inquiry (in the portal) to look up information on Purchase Orders transactions.
• Improved help. We've revised Purchase Orders help to improve search results, enhance the readability of help topics, and make it easier for you to find important information and instructions.

Known Issues

There are no known issues.

^ Back to top

Canadian Payroll

New Features and Improvements

Canadian Payroll 6.0 is compatible with all Sage 300 ERP 2012 programs.

Sage 300 ERP 2012 includes Canadian Payroll 6.0 Product Update 1; and the July 1, 2012 payroll tax update.

Known Issues

There are no known issues.

^ Back to top

US Payroll

New Features and Improvements

US Payroll 6.0 is compatible with all Sage 300 ERP 2012 programs.

Sage 300 ERP 2012 includes US Payroll 6.0 Product Update 3; and the June 30, 2012 payroll tax update. This version of US payroll includes the following features and improvements added after 6.0 Product Update 1:

• New fields to support the Pennsylvania Political Subdivision Codes. The following fields now appear on the Local and Other Custom Taxes screen:
  • State
  • Local Tax Code

  Note: If you enter "PA" in the State field, Local Tax Code changes to Political Subdivision Code.

Known Issues

There are no known issues.

^ Back to top

Project and Job Costing

New Features and Improvements

Project and Job Costing 2012 is compatible with all Sage 300 ERP 2012 programs.

Known Issues

There are no known issues.

^ Back to top

Payment Processing

You use Payment Processing with Sage Exchange to process credit card payments from your customers. Sage Exchange is a secure payment-processing application that integrates Sage 300 ERP with Sage Payment Solutions.

Note: Before you can process credit card transactions, you must obtain a merchant account from Sage Payment Solutions. To apply for a merchant account, visit the Sage ERP Payment Solutions website.

Installing Sage Exchange

Sage Exchange is a secure payment-processing application that integrates Sage 300 ERP with Sage Payment Solutions. Sage Exchange must be installed on every computer you will use to process credit card payments.

To install Sage Exchange, ensure that the Sage Exchange option is selected when you install Sage 300 ERP. If the installation fails, or if you need to reinstall Sage Exchange, visit https://www.sageexchange.com/install/setup.exe to download the software.

Each computer you use to process credit card payments must have a working Internet connection.

Setting Up Payment Processing

To activate Payment Processing, use the Data Activation screen in Administrative Services. After activation, the Processing Codes screen becomes available in Common Services, and other payment processing screens become available in Accounts Receivable and Order Entry if you use those programs.

After activating Payment Processing, you must set up security authorizations (in Administrative Services); processing codes and options (in Common Services); and payment codes (in Accounts Receivable).

For more information about setting up and using the program, see the Payment Processing Help. To open the help file from the Sage 300 ERP Desktop, press F1, and then select Payment Processing.

New Features and Improvements

Payment Processing 2012 includes the following new features and improvements:

• Capture and invoice multiple pre-authorized payments in a single batch. In Order Entry, a new Capture Payments With Invoices screen lets you capture and invoice pre-authorized credit card payments for multiple Order Entry documents in a single batch.

  After processing, you can review a summary of payments processed, and you can print invoices and receipts. A new receipt batch is created automatically in Accounts Receivable for each processing code used to process payments.

• New options to customize and streamline payment processing. In Payment Processing, a new PMT Options screen includes the following options:
  • Require Capture of Pre-authorized Payments at Shipment. In previous versions of Payment Processing, users were required to capture pre-authorized payments before shipping an order. You can select this option to preserve the existing workflow, or you can clear the option if you want to allow warehouse staff to ship orders without capturing payments. If you clear the option, accounting staff can capture pre-authorized payments when invoicing the order.
  • Warn Before Forcing Expired Pre-authorizations. In previous versions of Payment Processing, a warning message appeared each time a user attempted to "force" payment for an expired pre-authorization. You can use this option to turn this warning off if you want to streamline the process of forcing payment for expired pre-authorizations.
• A new Same As Customer Address option on the PMT Process Credit Card screen. If you are entering a card for one-time use, you can select this option to automatically fill in billing details with name and address information from the customer record.

Known Issues

• Sage 300 ERP Payment Processing supports Canadian and US currencies. However, if you use currency codes other than the ISO 4217 standard (CAD and USD), an error appears when you try to specify a currency for a processing code on the Processing Codes setup screen.

  To fix this issue:

  1. In the directory where you installed Sage 300 ERP, open the YP61A folder.
  2. Open yp.ini in text editing software.
  3. In the [SPS] group, add an entry for the currency below the existing entries. (For example, if the last entry is currency2=CAD, you could add currency3=CDN.)
• If you use Web Deployment to open Sage 300 ERP screens in a browser, the Credit Card tab may not appear on the A/R Customers screen. (Note that "Web Deployment" does not refer to setting up the Sage 300 ERP Portal, but instead refers to the process of deploying Sage 300 ERP on a web server to support remote Web Client access.)

  To fix this issue, open C:\Downloaded Program Files, and then delete the file AccpacAR1300.ACCPACAR1300UICtrl. The Credit Card tab should appear the next time you open the screen.

^ Back to top

G/L Consolidations

New Features and Improvements

G/L Consolidations 2012 is compatible with all Sage 300 ERP 2012 programs.

Known Issues

There are no known issues.

^ Back to top

Intercompany Transactions

New Features and Improvements

Intercompany Transactions 2012 is compatible with all Sage 300 ERP 2012 programs.

Known Issues

There are no known issues.

^ Back to top

Return Material Authorization

New Features and Improvements

Return Material Authorization 2012 includes the following new features and improvements:

• Credit Note Return Type. You can now create Credit Note details for all three return types supported by Order Entry:

  • Items Returned to Inventory
  • Damaged Items
  • Price Adjustment
• Print Credit Notes. You can now print a Credit Note from a RMA detail line by clicking Print Credit Note on the detail Zoom/Integration tab.
• Print Order Confirmations. You can now print an Order Confirmation from a RMA detail line by clicking Print Order Confirmation on the detail Zoom/Integration tab.
• Print Vendor Returns. You can now print a Vendor Return from a RMA detail line by clicking Print Vendor Return on the detail Zoom/Integration tab.

• RMA serial quantity allocation validation. Allocated serial quantity validation will not take place when the item on the RMA detail is serialized, and comes from an O/E invoice where no serials have been allocated to the item.

  In the above circumstance, RMA will not validate the quantity of serials allocated because the originating O/E invoice detail record did not have allocated serial numbers, even if the item is presently marked as serialized.

• RMA Detail Comments and Instructions viewable when detail is flagged Complete. Previously, comments and instructions were not viewable from the RMA detail grid once the RMA transaction detail was flagged as Complete. However, it was possible to view the comments/instructions through the F9 zoom screen. This issue has been fixed. It is now possible to call up the comments/instruction popup form from the RMA detail grid for a detail that has been marked as complete.
• RMA Header Customer Claim Number duplicate check. The new template option Check Customer Claim No. will ignore, warn, or report an error when an RMA document is entered for a customer and the customer claim number is no longer unique to that customer.
• RMA Header Restocking Fee Percentage. There is a new field on the Customer tab of the RMA Entry screen: Restocking Fee Percentage. The field is automatically populated with default values from the chosen template if automatic restocking has been enabled on the template. RMA document restocking fee calculation will use the percentage found on the RMA Entry customer tab, not the percentage found on the template. The template value is only used as a default populating value.

• RMA Header Comments and O/E Credit Note Header Comments. RMA Header comments will be copied across to an O/E Credit Note header if all of the following conditions apply:

  • The O/E credit note is matched to an O/E invoice.
  • The RMA document is using an RMA template.
  • The template option Copy RMA Comments to Matched CR Note is turned on.

  When dealing with unmatched O/E Credit Notes, RMA Header comments will be copied across to the Credit Note of all of the following conditions apply:

  • The O/E credit note is unmatched (not tied to an O/E invoice).
  • The RMA document is using an RMA template.
  • The template option Copy RMA Comments to Unmatched CR Note is turned on.
• RMA Header Optional Field error when selecting an optional field. Fixed an issue with RMA header optional fields that prevented a user from choosing an optional field for the header. This issue was addressed as a hotfix for RMA 6.0A, and is included in the RMA 6.1A release.
• Pricelist code validation on completed RMA documents. When an RMA document is flagged "Completed" in the header, RMA Integrity Check will not validate the pricelist code if it is blank. This measure was introduced to handle RMA documents entered in older versions of RMA where blank Pricelist validation was not performed.
• Defaulting item cost to Most Recent Cost when assigned costing method cost is zero. When an item's costing method cost (Avg, Std, etc) is zero, RMA will default to the Most Recent Cost for the item, at the selected location.

• RMA Detail Quantity Credited Check and legacy records from prior versions of RMA. RMA documents that make use of a template have the option to have their detail lines checked for quantities already credited.

  For records upgraded from RMA version 5.3 and prior where required data linking RMA details to O/E invoices was not maintained, a user may be unable to update RMA detail records. To fix this problem the Quantity Credited Check is not performed when inadequate information exists on the RMA detail to be able to link the RMA line to an existing O/E invoice detail.

Known Issues

• On the Integration tab of the Return Authorization Entry screen, when trying to print a generated credit note or vendor return for a detail line, a "Run-time error 711" error message appears. If you click OK, the screen stops responding.

  To work around this issue:

  • In the Runtime folder, run RegAcc.exe, or
  • Print the credit note and vendor return reports in Order Entry and Purchase Orders before printing the reports in Return Material Authorization.

  For more information, see Knowledgebase article 210-1002289.

• After upgrading from Return Material Authorization 5.6 to 2012, miscellaneous details in existing data are incorrectly assigned the Damaged Items return type by default. As a result, when running Data Integrity after upgrading, the following message appears:

  "Invalid entry. Return Type must be set to Return To Inventory for lines of type Miscellaneous."

  For more information, see Knowledgebase article 210-1002286.

^ Back to top

Sage 300 ERP Intelligence Reporting

New Features and Improvements

Sage 300 ERP Intelligence Reporting 2012 includes the following new features and improvements:

• Automatically installed with General Ledger. If you install General Ledger, Sage 300 ERP Intelligence Reporting is automatically installed.
• New Report Designer. The new Report Designer lets you "drag and drop" columns and predefined calculations to easily create new financial reports.
  • A new Formula Builder enables you to create additional calculated fields.
  • A new "What If Analyzer" includes a sliding scale you can use to dynamically change amounts while forecasting, budgeting, and creating projections.
• New Reporting Trees. Reporting trees enable you to model sophisticated reporting structures so you can view your organization in many different ways with the click of a button.
• New report distribution feature. You can use the new report distribution feature to quickly and easily send reports to a file, FTP site, or e-mail message in a number of standard formats.
• New reporting options. You can now exclude inactive accounts from the GL Chart of Accounts Reports, filter by range of fiscal years on the G/L Transactions Listing Report, and exclude inactive I/C items from I/C Physical Inventory reports.
• New Report Designer progress bar. A progress bar now appears when you are generating layouts, enabling you to view progress or cancel report layout generation.
• Improved "Refresh Data" in Report Designer. When refreshing data, all new accounts are placed into the correct account groupings in the correct order, using the same formatting as the rest of the report.
• Simplified Drill Down. In financial reports, you can now right-click a value and select Drill Down.
• Option to remember sign-in credentials. When signing in to Sage 300 ERP Intelligence Reporting, you can now save your User and Database credentials.
• Improved performance and efficiency of Universal Query Engine. The Universal Query Engine now uses a newer version of SQL Compact Edition, with improved parsing of SQL queries and faster data cache creation.
• Improved performance of Financial Reports report.
• New aggregated reports. Two new reports — Aggregated Financial Reports and Aggregated Financial Reports Designer — allow you to run financial reports without negatively impacting performance.
• Enhanced usability of the BI Tools ribbon. You can now point to a button on the ribbon to view a "tool tip" with information about the button.

Known Issues

• When trying to open the Connector, Report Manager, or Security Manager screen, a "File Not Found" error message may appear. To work around this issue, open the Runtime folder and run RegAcc.exe.
• If you use workstation setup, an "Exception occurred" error message appears when trying to open the Security Manager screen.

  To work around this issue, install Sage 300 ERP (not workstation setup) on each workstation where you will use the Security Manager screen.

  Note: When specifying installation folders, specify a local folder for program data, and specify the data folder on the server for shared data.

  For more information, see Knowledgebase article 210-1002287.

^ Back to top

Sage CRM Integration with Sage 300 ERP

New Features and Improvements

Sage 300 ERP 2012 Integration with Sage CRM 7.1 SP2 includes the following new features and improvements:

• Changes to program installation. Note the following important changes to the process of installing and integrating Sage 300 ERP and Sage CRM:

  • Sage 300 ERP Integration for Sage CRM (the Sage CRM-side integration component) is not part of the Sage CRM install, and must be installed separately.
  • Sage 300 ERP Integration Component (the Sage 300 ERP-side integration component) is now part of the all-in-one Sage 300 ERP install, so you do not need to install it separately if you select Sage CRM Integration when installing Sage 300 ERP.

  For details and updated installation instructions, see the Sage CRM Integration Upgrade Guide and Sage CRM Integration Guide.

• Support for multiple browsers. You can now use Mozilla Firefox, Apple Safari, and Google Chrome to view and use integrated screens that appear in a browser window, including the Quotes and Orders screens. However, note the following exceptions:
  • If Sage CRM and Sage 300 ERP are installed on separate servers, the integrated Quotes and Orders screens are supported only in Internet Explorer.
  • Integrated screens that appear in a separate window, such as A/R Invoice Entry, are supported only in Internet Explorer.
• A new Sales Split panel on the integrated Quote Entry and Order Entry screens. If you track commissions for sales staff, you can use this panel to allocate transaction totals to up to five salespersons.

For an overview of new features in Sage CRM 7.1 SP2, see the Sage CRM v7.1 SP2 What's New Guide on the Sage CRM Community website.

For a complete list of customer-facing changes and upgrade information for Sage CRM integrated with Sage 300 ERP, see the Sage CRM Integration Upgrade Guide.

For system requirements and instructions on setting up Sage CRM integration with Sage 300 ERP, see the Sage CRM Integration Guide.

Known Issues

• If you are upgrading from a previous version of Sage 300 ERP integrated with Sage CRM:

  • During the upgrade process, you may see a warning message stating that the CheckPhoneEmail script has found some discrepancies. If you see this message, you can safely proceed with the upgrade; any discrepancies will be resolved automatically when you install Sage 300 ERP Integration for Sage CRM.

    Note: After upgrading Sage CRM, you should always upgrade Sage 300 ERP Integration for Sage CRM (the Sage CRM-side integration component). After upgrading Sage CRM and the integration component, you can use the Sage CRM phone/email checker (CheckPhoneEmail.exe) to identify any customized areas where changes to database tables may have caused discrepancies in phone and email data. For more information, see Chapter 8 of the Sage CRM v7.1 SP2 Installation and Upgrade Guide.

  • After upgrading, you may need to clear your browser cache to see the new features added for the 2012 release.
• If you do not use Pervasive PSQL, but you install Sage 300 ERP Pervasive sample data, the following error messages may appear:
  • When activating the Sage 300 ERP integration (EW) component in Sage 300 ERP: "Internal error. EW Library: Cannot open EW.INI file."
  • When using the integrated Quotes and Orders screens in Sage CRM:
    • "Unable to download the schema from the server."
    • "Unable to create resource class."
• If Sage CRM and Sage 300 ERP are installed on separate servers, the integrated Quotes and Orders screens are supported only in Internet Explorer.
• If you use Internet Explorer 8 or 9, we recommend you do not use Compatibility View for Sage CRM screens. To turn off compatibility mode for your Sage CRM website:
  1. On the Tools menu, click Compatibility View Settings.
  2. If your Sage CRM website appears in the Websites you've added to compatibility view field, select the website and click Remove.
  3. Make sure the Display intranet sites in Compatibility View and Display all websites in Compatibility View options are not selected.
•  The following known issues may occur when using the integrated Quotes and Orders screens in Sage CRM:
  • When printing documents, the buttons on the Print window respond as expected, but sometimes appear styled as labels instead of buttons.
  • When working with an order or a quote in Sage CRM, if you open the Custom Fields panel, information below the panel is pushed down out of view. Before you can scroll down to view it, you must click anywhere inside the document header (except the Custom Fields panel) to restore the scrollable area.
  • If you use Internet Explorer, column labels in the table sometimes disappear when you click the scroll arrow in the table. If you click the scroll arrow again, the labels become visible.
  • If you use Internet Explorer, vertical scrollbars may not appear in Finders in the table after you click a Finder for a header field. To work around this problem, you can:
    • Avoid using Finders in header fields before entering details.
    • Open the screen in another browser (Firefox, Chrome, or Safari).
    • Click the Advanced Search link in the Finder (where available).

^ Back to top

Sage Fixed Assets Integration with Sage 300 ERP

New Features and Improvements

Sage Fixed Assets Integration with Sage 300 ERP 2012 is compatible with all Sage 300 ERP 2012 programs.

Known Issues

• Some Sage Fixed Assets products were renamed in 2012, so if you are integrating Sage 300 ERP with a pre-2012 version of a Sage Fixed Assets product, the name you select on the Product list on the Options screen may have changed.

  If you are integrating Sage 300 ERP 2012 with a pre-2012 version of one of the Sage Fixed Assets products listed below, select the corresponding 2012 product name on the Options screen.

  Pre-2012 Product Name	2012 Product Name
  Sage FAS Canada 50 Asset Accounting	Sage FAS Canada 50 Asset Accounting (no change)
  Sage FAS Canada 100 Asset Accounting	Sage Fixed Assets Canadian Edition - Depreciation
  Sage FAS Canada 500 Asset Accounting	Sage Fixed Assets Canadian Edition - Premier Depreciation
  Sage FAS Canada 100 Asset Accounting - Network Edition	Sage Fixed Assets Canadian Edition - Depreciation/Network
  Sage FAS 50 Asset Accounting	Sage Fixed Assets - Lite Depreciation
  Sage FAS 100 Asset Accounting	Sage Fixed Assets - Depreciation
  Sage FAS 500 Asset Accounting	Sage Fixed Assets - Premier Depreciation
  Sage FAS 100 Asset Accounting - Network Edition	Sage Fixed Assets - Depreciation/Network

• Sage Fixed Assets does not force book defaults on assets created from Sage 300 ERP, even if you select the Create Assets By Applying Template Then Forcing Book Defaults option on the Integration tab of the F/A Options screen.

  To work around this issue, you can manually force the book defaults in Sage Fixed Assets. To do this, select the asset, and on the Asset menu, select Apply Book Defaults.

^ Back to top

Options Products for Sage 300 ERP

New Features and Improvements

The 2012 versions of Options products are compatible with all Sage 300 ERP 2012 programs.

Known Issues

• Accounts Receivable payment codes more than 6 characters long are truncated when retrieving data to Sales Analysis. For more information, see Knowledgebase article 210-1002189.

^ Back to top

Number Changers for Sage 300 ERP

New Features and Improvements

The 2012 versions of Number Changers are compatible with all Sage 300 ERP 2012 programs.

Known Issues

There are no known issues.

^ Back to top

Changes to the SDK

The SDK now supports SData 1.1. For more information about SData, see sdata.sage.com.

^ Back to top

Changes to RVSpy

RVSpy includes new features that make this utility easier to use:

• A new Filter menu includes the Views and Calls commands.
• The Help menu includes an Error Meanings command that displays a list of numeric codes for the errors that appear in the Spy log, along with their more meaningful names.
• A new Comment field lets you insert comments while RVSpy is running.
• The program now checks for existing log files. If a log file already exists, you will be asked if you want to overwrite or append to it when you start RVSpy.

^ Back to top