» Sage 300 2012 Product Update 6 Release Notes
Sage 300 2012 Product Update 6 Release Notes
Product Update 6 contains a modified version of one or more Sage 300 program components. It is not a full upgrade or a product replacement. It is valid only until we release the next product update or the next version of Sage 300.
Updating Programs
Before installing this product update, read the following important information:
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
Sage 300 is now compatible with Sage Fixed Assets 2013.
Sage 300 is also compatible with the following Sage solutions:
- Sage Mobile Sales. Sage Mobile Sales is a tablet app that lets your sales team display your product catalog, check product availability, create quotes and orders, and process payments in the field.
- Sage Mobile Service. Sage Mobile Service is a smartphone app that lets your field service team review customer history, manage work orders, take before and after photos, and process payments onsite.
- Sage Billing and Payment. Sage Billing and Payment is a web application that automates the delivery of invoices and receipts and lets you accept electronic payments.
For more information about these solutions, visit www.sagemobileapps.com.
For a complete list of compatible programs, database platforms, and operating systems, see the Sage 300 2012 Compatibility Guide in the Sage Knowledgebase.
SAP Crystal Reports® Runtime Engine
As described in the 2012 Release Notes, reports in the Sage 300 Desktop are now printed using the SAP Crystal Reports® runtime engine for .NET Framework 4, which is installed with Sage 300.
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:
Video Feature Tours
To watch video feature tours of new features and enhancements, visit our YouTube channel at www.youtube.com/Sage300Doc.
Known Issues
- If you are using Sage 300 on a workstation in a client-server environment, you could have trouble viewing help. For example, your browser might display the message "Page cannot be displayed." For a solution, see Sage 300 Knowledgebase article 18477, or Microsoft support article 896054.
- When using Sage 300 in web deployment, it is not possible to print. For more information, see Knowledgebase article 71268.
Product Update 6 Program Fixes
The following sections describe program fixes included in Product Update 6.
Report Printing
-
Fixed a problem that could occur when exporting a report in XLS format, which caused information to be aligned incorrectly on the exported report. To ensure that information is aligned correctly when exporting in XLS format, select one of the following in the Column width based on objects in the field on the Export Options screen:
- Whole Report
- Page Headers
- Details
- 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 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.
Inventory Control
- Fixed a problem that prevented Day-End processing from completing if the day-end process included 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.
Order Entry
- 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.
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.
Product Update 5 New Features and Enhancements
The following sections describe new features and enhancements included in Product Update 5.
Improved Help and Documentation
This product update 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.
System Manager
- When printing to e-mail, you can now select recipients from your Microsoft Outlook address book.
- When exporting a report to an Excel file, you can now specify options for the exported file.
Product Update 5 Program Fixes
The following sections describe program fixes included in Product Update 5.
System Manager
- 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 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 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.
- 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.
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.
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.
General Ledger
- 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.
- 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.
Order Entry
- 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.
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.
Sage CRM Integration
- 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 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.
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 prevented you from changing account codes in Payroll 6.0A. For more information, see Knowledgebase article 40639.
- 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.
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 39552.
- 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.
Product Update 4 New Features and Enhancements
The following sections describe new features and enhancements included in Product Update 4.
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\61A\ENG:
- Bank Services User's Guide
- Tax Services User's Guide
This product update also includes French-language versions of:
- Tax Services help and the Tax Services User's Guide.
- G/L Consolidations help and the G/L Consolidations User's Guide.
Product Update 4 Program Fixes
The following sections describe program fixes included in Product Update 4.
Report Printing
- Fixed a problem that prevented you from restoring default report settings for customized reports if you used Printer as the print destination.
- 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.
- 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.
- 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.
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 selected a field or control that became unavailable when selected (similar to a fix made for Product Update 3). For more information, see Knowledgebase article 28880.
- Fixed a problem with memory management that could impair performance.
- 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.
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.
- 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.
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 AR Customers report to a CSV, TTX, or TXT file. For more information, see Knowledgebase article 34946.
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.
- 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.
Inventory Control
- 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.
Order Entry
- 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 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.
Project and Job Costing
- Fixed a problem on the Projects tab of the Contract Maintenance screen that prevented you from using the Finder in the Work in Progress field or the Cost of Sales field. For more information, see Knowledgebase article 30343.
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.
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.
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.
Product Update 3 New Features and Enhancements
The following sections describe new features and enhancements included in Product Update 3.
Improved Help and Documentation
This product update includes:
- French- and Chinese-language versions of General Ledger help and the General Ledger User's Guide and Financial Reporter User's Guide.
- Chinese-language versions of G/L Consolidations help and the G/L Consolidations User's Guide.
Accounts Payable
US tax forms - 1099 and 1096 - have been updated to meet the following changed IRS specifications for 2013:
Inventory Control
On the Lot Numbers screen and the Serial Numbers screen, you can now change the stock date.
Note: If you change the stock date, the expiry date is recalculated automatically.
Purchase Orders
If you do not allow negative inventory, you can now specify whether this setting is strictly enforced. To do this, you edit the [NegativeInventory] setting in the PO.INI file. For more information, see Knowledgebase article 21367.
Order Entry
- You can now specify whether miscellaneous charges are discountable by default. To do this, you edit the [ApplyInvoiceTermsDiscountToMiscCharge] setting in the OE.INI file. For more information, see Knowledgebase article 21367.
- The [UnconditionalPONumberEditInShipmentEntry] setting in the OE.INI file (added in Product Update 2) now applies to the PO Number field on both the Shipment Entry screen and the Invoice Entry screen.
Product Update 3 Program Fixes
The following sections describe program fixes included in Product Update 3.
System Manager
Accounts Payable
- Fixed a problem that prevented you from using SData for Vendor Remit-to Locations. For more information, see Knowledgebase article 210-1006739.
- Updated the 1099 form and the 1096 form to meet changed IRS specifications for the 2013 year. For more information, see Knowledgebase article 210-1007033.
- Fixed a problem on the Payment Entry screen that could prevent you from printing checks.
- Improved the performance of the A/P Create Payment Batch screen. The screen now opens faster, particularly when using a large database. For more information, see Knowledgebase article 25802.
Accounts Receivable
- Fixed a problem on the A/R Invoice Entry screen that prevented you from adding an item invoice, a credit note, or a debit note if the tax amount for the document was greater than the document amount. For more information, see Knowledgebase article 210-1006910.
- Fixed a problem on the Customer Inquiry screen that caused document amounts to be calculated incorrectly on the OE Orders and OE Invoices tabs. This problem occurred if you used Divide as the rate operation for currency rates. For more information, see Knowledgebase article 25133.
General Ledger
- Fixed a problem that could prevent you from printing the G/L Posting Journals Report if it included a posting sequence with a number higher than 1000. For more information, see Knowledgebase article 22327.
Inventory Control
- Fixed a problem that prevented you from reconciling serial numbers or lot numbers before running Day End Processing. For more information, see Knowledgebase article 210-1006753.
- Fixed a problem that prevented you from splitting or combining lots before running Day End Processing. For more information, see Knowledgebase article 24983.
- 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 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.
Order Entry
- Fixed a problem that prevented you from importing orders for customers who have exceeded their credit limit. For more information, see Knowledgebase article 24575.
- 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 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.
Project and Job Costing
- Fixed a problem that could occur when checking the integrity of Project and Job Costing data, which caused errors to appear incorrectly. This problem occurred only for Pervasive databases, and only if you checked the integrity of Project and Job Costing data multiple times consecutively.
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.
Account Code Change
- Fixed a problem that caused account codes to be updated incorrectly in the Expense Account and Liability Account fields on the Payroll Workers’ Compensation Codes screen.
Customer Number Change
- Fixed a problem that prevented you from viewing the End-User License Agreement from the About Customer Number Change screen.
Item Number Change
- Fixed a problem that caused a "Critical Error: [54353] unknown error writing record" error message to appear when changing item numbers in P/M Material Returns Detail. For more information, see Knowledgebase article 22837.
Product Update 2 New Features and Enhancements
The following sections describe new features and enhancements included in Product Update 2.
Improved Help and Documentation
We've revised Accounts Receivable, Accounts Payable, and G/L Consolidations 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:
- Accounts Receivable User's Guide
- Accounts Payable User's Guide
- G/L Consolidations User's Guide
This product update also includes French- and Chinese-language versions of Inventory Control help and the Inventory Control User's Guide.
General Ledger
Financial Reporter now supports Microsoft Excel 2013 32-bit.
Inventory Control
On the Lot Numbers Inquiry screen, a new Unit Cost field displays the unit cost for items in a lot, calculated based on the quantity of items in the lot and the total cost of the lot.
Order Entry
- You can now return serialized and lotted items to a location other than the location from which the items were shipped. (Previously, if you shipped and invoiced an order that included serialized or lotted items, and then selected the invoice in Credit Note Entry and tried to change the ship-to location, serial and lot numbers for the items were cleared.) For more information, see Knowledgebase article 210-31332.
-
You can now configure the PO Number field on the Shipment Entry screen to be editable at any time until the shipment is invoiced. To do this, add the following to the OE.INI file:
[UnconditionalPONumberEditInShipmentEntry]
Allowed=Yes
Sage CRM Integration
Sage 300 2012 now supports integration with Sage CRM 7.2.
For details about integration changes and known issues, and for information about downloading the integration upgrade package, see Knowledgebase article 210-1006642.
Product Update 2 Program Fixes
The following sections describe program fixes included in Product Update 2.
System Manager
- Fixed a problem that could occur when printing reports to some printers. If you selected Printer as the print destination, a "UI container" error message appeared when printing or previewing, and the program stopped responding. For more information, see Knowledgebase article 210-1005828.
- When printing a report to a file, the default destination is now Disk File. For more information, see Knowledgebase article 210-1005701.
- Fixed the following problems that could occur when exporting a report using Microsoft Mail as the destination:
- Text on the e-mailed report appeared smaller than text in the report preview. For more information, see Knowledgebase article 210-1004133.
- If you selected a range of pages, the email attachment included the full report, rather than the selected pages. For more information, see Knowledgebase article 210-1006249.
- Fixed a problem that could occur when entering optional fields on entry screens. If you navigated to the Value field for an optional field by pressing Tab, and then began typing, the text you entered became mixed up.
- For Sage 300 .NET Remoting Service, the default Windows Service Startup Type is now Automatic. For more information, see Knowledgebase article 210-1004918.
- Fixed a problem that caused Sage 300 Tomcat to sometimes restart unexpectedly. For more information, see Knowledgebase article 210-1006103.
- Fixed a problem that prevented the Export Options screen from appearing when exporting a report to CSV format. For more information, see Knowledgebase article 210-1005814.
Bank Services
- Improved the performance of the Reconcile Statements screen if a default bank is specified. In most situations, the screen now opens more quickly. For more information, see Knowledgebase article 210-1005534.
Accounts Payable
- Updated the T5018 report format (APCPRS.rpt) to match changes in the layout of form T5018-12b. For more information, see Knowledgebase article 210-1005859.
Accounts Receivable
- Fixed a problem that could occur when using the Create Retainage Batch screen to create a retainage batch, which could prevent some transactions from being processed in the batch. This problem occurred only for transactions that were originally created in Order Entry, and that have outstanding retainage but no retention period specified. For more information, see Knowledgebase article 210-1004150.
Inventory Control
- Fixed a problem that could occur after using the I/C Serial/Lot Reconciliations screen to ship a serialized item, causing incorrect costs to appear for items. If the serial number was returned and then shipped again, the Unit Cost field for the item on Sage 300 screens incorrectly displayed a figure that was half of the actual cost.
- Fixed a problem that could cause a lot to be incorrectly put under quarantine when you transferred it to a different location. The problem occurred only if the lot had previously been quarantined. For more information, see Knowledgebase article 210-1004797.
- Fixed a problem with the Items Wizard that could prevent vendor details from appearing for existing items. The problem could occur if you entered an item number and then changed it to an existing item number.
- Fixed a problem that could cause the cost of an inventory item to be updated incorrectly if the item had a negative cost. This problem occurred if you posted an O/E shipment that included an item with a negative cost, and you later reduced the quantity of the item on the shipment or related invoice. The incorrect cost information appeared on O/E, I/C, and P/O screens. For more information, see Knowledgebase article 210-1005421.
Purchase Orders
- Fixed a problem that could occur if you use standalone Purchase Orders without Inventory Control. If you tried to export items from the P/O Items screen to an Excel file, or if you tried to use the SDK View Tester to open the PO0148 View, an "Internal error. cannot get user cost names (1118 ICPCOD1.C)" error message appeared.
- Fixed a problem that could cause the cost of an inventory item to be updated incorrectly if the item had a negative cost. This problem occurred if you posted an O/E shipment that included an item with a negative cost, and you later reduced the quantity of the item on the shipment or related invoice. The incorrect cost information appeared on O/E, I/C, and P/O screens. For more information, see Knowledgebase article 210-1005421.
- Fixed a problem that prevented credit notes for additional costs from being correctly applied to items that use serial or lot costing. The problem caused the credit to be applied to the item cost but not the serial or lot cost. For more information, see Knowledgebase article 210-1005803.
Order Entry
- Fixed a problem that could cause an incorrect default unit of measure to appear for a manufacturer’s item on the O/E Shipment Entry and Credit/Debit Note Entry screens. For more information, see Knowledgebase article 210-1004770.
- Fixed a problem that prevented the UNITCOST, EXTCOSTH and EXTCOSTS fields in the OEAUDD table from being populated when posting a shipment, invoice, or credit note for a kitting item.
- Fixed a problem that could cause a lot to be incorrectly put under quarantine when you returned it to inventory. The problem occurred only if the lot had previously been quarantined. For more information, see Knowledgebase article 210-1004797.
- Fixed a problem that could occur when using the Copy Orders screen to copy a quote, which could cause an incorrect quantity to be displayed in the Qty Ordered field. This problem occurred if the quote you were copying had been copied from another quote, and had a different Qty Ordered than that original quote.
Example: Quote 2 is a copy of quote 1, except that it has a different Qty Ordered. If you tried to copy quote 2, the Copy Orders screen incorrectly displayed the Qty Ordered from quote 1.
For more information, see Knowledgebase article 210-1004822.
- Fixed a problem that could cause the cost of an inventory item to be updated incorrectly if the item had a negative cost. This problem occurred if you posted an O/E shipment that included an item with a negative cost, and you later reduced the quantity of the item on the shipment or related invoice. The incorrect cost information appeared on O/E, I/C, and P/O screens. For more information, see Knowledgebase article 210-1005421.
Project and Job Costing
- Fixed a problem that could prevent category details from appearing on the Contract Maintenance screen if you had a large number of contracts. For more information, see Knowledgebase article 210-1004881.
- Fixed a problem that caused imported contracts to use the general ledger accounts from the account set instead of the import file. For more information, see Knowledgebase article 210-1005708.
Payment Processing
- Fixed a problem that prevented you from activating Payment Processing if you do not use Order Entry. For more information, see Knowledgebase article 210-1005955.
Sage CRM Integration
- Fixed a problem that caused a "java.util.concurrent.ExecutionException" error message to appear when printing a Crystal Report from Sage CRM. The error occurred if the report contained a sub-report with information from a database other than the Sage 300 company database. For more information, see Knowledgebase article 210-1004095.
Ops Inquiry
- Fixed a problem on the I/C Item Inquiry screen that caused the Total Quantity and Total Available fields to exclude committed quantities. For more information, see Knowledgebase article 210-1005488.
- Fixed a problem on the I/C Item Inquiry screen that could cause incorrect information to appear in the Total Available field. The problem occurred when viewing an item for which there was inventory at more than 20 locations.
Account Code Change
- Fixed a problem that caused “Internal Error: field number is out of range” error messages to appear when posting after increasing or decreasing the segment length. For more information, see Knowledgebase article 210-1003108.
Item Number Change
- Fixed a problem that prevented the receipts posting journal from being updated in Inventory Control when you changed an item number. For more information, see Knowledgebase article 210-1006064.
Sage Advisor Update
- Fixed a problem that caused Sage Advisor Update to incorrectly indicate that your Business Care plan was expired. This problem occurred in Sage 300 Standard (100) and Sage 300 Advanced (200) Editions. For more information, see Knowledgebase article 210-1004870.
Product Update 1 New Features and Enhancements
The following sections describe new features and enhancements included in Product Update 1.
Company Colors
If you use Sage 300 to manage multiple companies, you can now assign a unique color to each company. This color appears in a border around the Sage 300 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.
Note:
- This feature is available only in programs created using the Sage 300 Software Development Kit (SDK). If you use Options products (Ops Inquiry and Sales Analysis), Number Changers, or other integrated programs that were not created using the Sage 300 SDK, company colors will not appear in screens for those programs.
- This feature is available for web-deployed systems. However, before you can view company colors on a workstation using an existing web-deployed system, you must install the new Sage 300 .NET library from <Sage 300 Installation Folder>\Web\cabs, and then delete all files matching a4w*.* from C:\Windows\Downloaded Program Files.
- Company colors appear in borders around the Sage 300 desktop and screens, but do not appear on pop-up screens ("zoom forms"), dialog boxes, and messages.
Sage 300 Payroll Enhancements
For information about new features and changes in the Canadian and US versions of Sage 300 Payroll 2012 (also called "Sage HRMS Payroll for Sage 300 7.0"), and for information about upgrading from previous versions of Sage 300 Payroll, see the Sage 300 Payroll Help and release documentation.
Note: Sage 300 Payroll is not included in Sage 300 2012 Product Update 1. Installation files for Canadian Payroll and US Payroll are available separately.
Important! If you use Pervasive PSQL, Sage 300 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 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. For information about resolving this problem, see Knowledgebase article 210-1003219.
Online Paystubs and Payroll History for Employees
If you use Sage 300 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 Payroll customers will receive an email message with instructions for getting started. If you have questions, contact your business partner or Sage 300 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 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 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 customer on the Company Summary screen, a new Item Inventory button appears. You can click this button to look up Sage 300 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.
Note:
- To use the new inventory item lookup feature, you must install the new version of Sage 300 Integration for Sage CRM (the Sage CRM-side integration component) included with this product update. For more information, see "Upgrading Sage CRM 7.1 Integrated with Sage 300 2012 to Support Sage 300 Product Update 1" in the Sage CRM Integration Upgrade Guide.
- The Item Inventory button appears on the Company Summary screen only if a company is a Sage 300 customer. It does not appear when viewing other company types such as vendors, or when viewing non-integrated companies.
-
Before you can create a new quote or new order for an item from the Sage CRM Item Inventory screen, default values must be specified in Sage 300 for the following O/E Order Entry fields:
- Price List
- Location
- Any automatically inserted optional fields (if you use Transaction Analysis and Optional Field Creator)
For more information, see the Sage CRM Integration Guide.
Sage 300 SDK
The AccpacReport COM object now supports exporting reports to Microsoft Excel .xls and .xlsx formats. For more information, see the Sage 300 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 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. 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
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
Important!
- To implement the program fixes described in this section, you must install the new version of Sage 300 Integration for Sage CRM (the Sage CRM-side integration component) included with this product update. For more information, see "Upgrading Sage CRM 7.1 Integrated with Sage 300 2012 to Support Sage 300 Product Update 1" in the Sage CRMIntegration Upgrade Guide.
- If you have installed Sage CRM and Sage 300 on separate servers, see "Setting up Sage CRM and Sage 300 on Separate Servers" in Chapter 4 of the Sage CRMIntegration Guide for important information about changes to server configuration. You must follow the revised integration procedures described in this section to enable multi-browser support in a two-server setup.
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. 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 210-1001849.
- If Sage CRM and Sage 300 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, if your Sage 300 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