The following sections describe new features and feature enhancements included in Product Update 3.
Support for New Payment Processing Module
This Product Update includes support for Payment Processing 5.6 — a Sage ERP Accpac program that lets you process credit card payments from your customers. Payment Processing 5.6 replaces the previous credit card functionality in Sage ERP Accpac 5.6 with an integrated, PCI-compliant solution for processing transactions and securely storing credit card information.
Important: If you currently use Sage ERP Accpac 5.6 to store customer credit card information, you must run the Sage ERP Accpac Credit Card Scrub utility before you install and activate Payment Processing. This utility exports and removes credit card records that do not meet PCI compliance standards from your system. For an overview of product features and integration with Accounts Receivable and Order Entry 5.6, see the Payment Processing Overview topic in the Payment Processing help.
Product Update 3 Program Fixes
The following sections describe program fixes included in Product Update 3.
System Manager
- Fixed a problem that caused Chinese characters to appear in some fields if you did not enter contact information in License Manager. For more information, see Knowledgebase article 210-31459.
- Fixed a problem that caused unexpected behavior, such as program crashes or slow performance, after activating certain programs.
Although all dependencies among released Sage ERP Accpac version 5.6A programs were validated, activation did not check for certain "datalevel" upgrades (smaller changes, such as those introduced with a product update, with other program fixes, and by third-party programs) that are necessary to support some programs. Activation proceeded, apparently without error, even though some supporting database elements were not present.
Bank Services
- Improved the performance of the Data Integrity Report for Bank Services. For more information, see Knowledgebase article 210-31337.
Accounts Payable
- Fixed a problem that prevented separate G/L batches from being successfully created when multiple users posted A/P batches at the same time. Posting A/P batches now creates separate G/L batches according to the posting sequence.
If you want to post multiple A/P batches to a single G/L batch, you can:
- Use the A/P Post Batches form and select a range of batches to post to a single G/L batch, or
- Change G/L integration settings to create G/L transactions by adding to an existing batch. This will add G/L transactions to the highest numbered G/L Batch with "Open" status. (For example, if there are 10 open G/L batches numbered 1 through 10, when you post A/P batches, the G/L transactions will be added to G/L Batch 10.)
- Fixed a problem that could cause slow performance for PSQL in A/P Vendor Activity when both the "Include Fully Paid Transactions" and "Include Pending Amounts" options are selected on the Transactions tab. For more information, see Knowledgebase article 210-31399.
- Fixed an alignment issue that occurred when printing T5018 information on the Canada Revenue Agency T5018 (CPRS) pre-printed form. For more information, see Knowledgebase article 210-31823.
- Fixed a problem that could prevent some payments from clearing when posting a reconciliation. When this problem occurred, the program displayed the error message "Incorrect procedure. Requested check was cleared previously." For more information, see Knowledgebase article 210-31799.
Accounts Receivable
- Fixed a problem that prevented separate G/L batches from being successfully created when multiple users posted A/R batches at the same time. Posting A/R batches now creates separate G/L batches according to the posting sequence.
If you want to post multiple A/R batches to a single G/L batch, you can:
- Use the A/R Post Batches form and select a range of batches to post to a single G/L batch, or
- Change G/L integration settings to create G/L transactions by adding to an existing batch. This will add G/L transactions to the highest numbered G/L Batch with "Open" status. (For example, if there are 10 open G/L batches numbered 1 through 10, when you post A/R batches, the G/L transactions will be added to G/L Batch 10.)
- Fixed a problem that could cause slow performance for PSQL in A/R Customer Inquiry when both the "Include Fully Paid Transactions" and "Include Pending Amounts" options are selected on the Documents tab. For more information, see Knowledgebase article 210-31470.
- Fixed a problem in A/R Customer Inquiry that caused completed orders to appear on the O/E Orders tab for the selected customer. The tab now shows only open orders for the selected customer. For more information, see Knowledgebase article 210-31470.
General Ledger
- Fixed a rare problem that could cause the program to terminate unexpectedly with a "UI container error" when a non-ADMIN user edited a recurring entry in G/L Setup. For more information, see Knowledgebase article 210-31288.
Inventory Control
- Fixed a problem that could cause I/C Inquiry forms to incorrectly display a stock quantity of 0 if you posted a transaction using the Serial/Lot Reconciliations form or the Lot Splits/Combines form.
- Fixed a problem that could cause the I/C Reserved Stock Listing Report (ICXRS04) to display duplicated inventory. This problem occurred only if multiple inventory lots had the same lot number. For more information, see Knowledgebase article 210-31366.
- Fixed a problem in Day End Processing that could cause a CSTP XIFO cost error to appear when processing an item with missing cost information. For more information, see Knowledgebase article 210-21899.
- Fixed a problem in Day End Processing that could cause a "record modified by another user" error to appear during posting even if no one had modified records in the database.
- Restored the ability for 3rd-party developers to prevent the serial/lot entry popup form from appearing in I/C, O/E, and P/O transactions. For more information, see Knowledgebase article 210-31460.
- Fixed a problem in Day End Processing that could cause a "Quantity to reconcile does not match Serial quantity" error to appear when receiving lot/serial numbers in SN/LT Reconciliation for a serialized/lotted item.
For an item that is serialized and lotted, in addition to supporting the scenario where the serial and lot quantities are the same as the quantity entered, the system now supports the following scenarios:
- serial quantity = quantity entered, and the lot quantity is zero
- lot quantity = quantity entered, and the serial quantity is zero
- Fixed a problem that could occur when checking the integrity of Inventory Control data. The program sometimes displayed the message "E: Internal error. create-icintckCreate" even if no issues existed with Inventory Control data.
- Fixed a problem that could occur while verifying quantities for an assembly. If the unit of measure you specified for the master item did not match the stocking unit of measure for the item, a conversion issue could cause Inventory Control to incorrectly report that insufficient quantities existed for the assembly.
- Fixed a problem that could cause the I/C Serial/Lot Stock Listing report to display both available and unavailable lot numbers as expired stock.
- You can now specify actual (average) cost as the default inventory valuation method to be used when generating an inventory worksheet and creating adjustment entries. The method you specify determines the cost that appears in the Adjustment Unit Cost Per Costing Unit column on the I/C Physical Inventory Quantities form.
Inventory Control currently sets the default inventory valuation method as follows:
- If item uses standard costing method: standard cost
- If item uses most recent costing method: most recent cost
- If item uses another costing method: actual (average) cost
If you want to set up Inventory Control so that actual cost is always specified as the default inventory valuation method:
- In the IC56A directory in your Sage ERP Accpac program files, open the file ic.ini in text editing software.
- Edit the line UseActualCostForPI=NO so it reads UseActualCostForPI=YES.
For more information, see Knowledgebase article 210-31246.
For more information, see Knowledgebase article 210-31805.
Purchase Orders
- Fixed a problem that could allow you to take a purchase order off hold, without warning, for a vendor who is on hold in Accounts Payable. For more information, see Knowledgebase article 210-31739.
Order Entry
- Added the ability to 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.
- Fixed a problem that allowed shipments and invoices to be posted for an inactive customer. (Previously, if an order had been posted for the customer before the customer was set to inactive, you could use the Order Entry form to post a shipment and invoice for the order.) For more information, see Knowledgebase article 210-31456.
- Fixed a problem that could cause the Shipment Total to be incorrectly calculated for an order, when the order includes an item whose Discount Rounding Method is set to "Round Up to a Multiple of" on the I/C Item Pricing form.
- Fixed a 3rd-party development problem that could prevent an invoice from being posted in O/E when the option to "Create A/R batch during Posting" is set on the I/C Options and O/E Options forms. For more information, see Knowledgebase article 210-31669.
- Fixed a problem that could cause the "Invoice Batch. Attempt to modify a different record than was retrieved" error to appear when the Ready to Post setting of an O/E-generated A/R invoice batch is changed from yes to no. For more information, see Knowledgebase article 210-31784.
Project and Job Costing
- Fixed a problem that could occur if you imported an adjustment that adjusted several lines. The program displayed the error "Invalid input. Line 2. Document already adjusted/transferred on this Adjustment." In some cases, the program assigned adjustments to the wrong lines.
This problem occurred only if the document being adjusted included multiple lines with identical contract, category, project, and resource information. For more information, see Knowledgebase article 210-32057.
- Fixed a problem that occurred when checking the integrity of Project and Job Costing data. Data Integrity reported errors for standard contracts when an identical name was used for multiple resources (for example, if you used the same name for a miscellaneous and a subcontractor resource).
- Fixed a problem that occurred when checking the integrity of Project and Job Costing data. Data Integrity reported errors for posted timecards for employees with Inactive status, even if the employees were active when the timecards were posted. Data Integrity no longer checks posted timecard documents for Project and Job Costing. For more information, see Knowledgebase article 210-31272.
- Fixed a problem in the PJC Detailed Transaction Report (PMDTTRAN.rpt) that prevented the Contract Cost Totals and Contract Billing Totals from appearing in the print output. For more information, see Knowledgebase article 210-31442.
- Fixed a problem that could prevent optional field values for timecard details from appearing in a billing worksheet generated for "Item" Invoice Type transactions on the Create Billing Worksheet form. For more information, see Knowledgebase article 210-26884.
- Fixed a 3rd-party development problem that caused the tree in Contract Maintenance to display incorrectly if the Contract Categories view (PMCATGT) is subclassed to increase the length of the Category Description field. For more information, see Knowledgebase article 210-31656.
- Fixed a problem in Contract Maintenance that could cause the error "Criteria error. Open Document Detail. Syntax error. Invalid boolean" to appear for no reason when changing the status of a project to "Completed." For more information, see Knowledgebase article 210-31683.
Canadian and US Payroll
- Fixed a problem that prevented descriptions from appearing in the Transaction History finder.
Ops Inquiry
- Fixed a problem that prevented you from creating inquiries (using PO inquiry, IC History inquiry, or OE inquiry) if you did not have full user rights to the Ops Inquiry program folder.
- Fixed the Fiscal Year fields in PO inquiry, so that you can select Start and End dates using a finder.
Uni Sales Analysis
- Fixed a problem that prevented you from creating inquiries (using Inquiry & Report) if you did not have full user rights to the Uni Sales Analysis program folder.
Web Deployment
- If you have installed non-English language packs (French, Spanish, Simplified or Traditional Chinese), Web Deployment now displays all forms in the correct language. For more information, see Knowledgebase article 210-31308.
