» Sage ERP Accpac 5.6A Product Update 3 Readme

Sage ERP Accpac 5.6A Product Update 3 Readme

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

Updating Programs

Important: This product update contains database changes for Accounts Receivable and Order Entry. After installing the update, you must reactivate your data for these programs for 5.6A. If you have not previously installed Sage ERP Accpac 5.6A Product Update 2, you will also need to reactivate your data for Bank Services for 5.6A.

Upgrading from Version 5.3

Important: If you upgraded Bank Services from version 5.3 to version 5.6 before you installed Product Update 1, make sure you run Bank Services' data repair utility before you reverse transactions posted in version 5.3. If you have not already run this utility, contact Customer Support for assistance.

Upgrading to Version 6.0

Important: After installing Sage ERP Accpac 5.6A Product Update 3, if you subsequently upgrade from Sage ERP Accpac version 5.6 to 6.0, you must install Sage ERP Accpac 6.0A Product Update 1 or later before activating your data to avoid possible data corruption issues.

Product Update 3 New Features and Enhancements

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. To learn more and download the Credit Card Scrub utility, visit www.sageaccpacinfo.com/PCI.

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.

^ Back to top

Bank Services

• Improved the performance of the Data Integrity Report for Bank Services. For more information, see Knowledgebase article 210-31337.

^ Back to top

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.)
  For more information, see Knowledgebase articles 210-31271 and 201-32037.

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

^ Back to top

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.)
  For more information, see Knowledgebase articles 210-31271 and 201-32037.

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

^ Back to top

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.

^ Back to top

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

For more information, see Knowledgebase article 210-31805.

• 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:

  1. In the IC56A directory in your Sage ERP Accpac program files, open the file ic.ini in text editing software.
  2. Edit the line UseActualCostForPI=NO so it reads UseActualCostForPI=YES.

  For more information, see Knowledgebase article 210-31246.

^ Back to top

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.

^ Back to top

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.

^ Back to top

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.

^ Back to top

Canadian and US Payroll

• Fixed a problem that prevented descriptions from appearing in the Transaction History finder.

^ Back to top

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.

^ Back to top

Changes Included in Product Update 2

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

System Manager

• Fixed all known problems with the use of Asian characters in data entry fields and on the desktop when using English Windows. The program no longer truncates Asian characters, the Finder is now operational, and Asian characters appear correctly in lists and tables. For more information, see Knowledgebase article 210-31068.
• Fixed a problem that occurred when running Sage ERP Accpac processes over a long period of time. Memory leaks caused core processes to run out of memory eventually, and crash. For more information, see Knowledgebase article 210-31059.
• Fixed a problem that occurred when signing on to web-deployed Sage Accpac through a browser and when macros attempted to sign on to Sage ERP Accpac, if you used Windows Authentication. The system did not let you open a Sage Accpac session.
• Fixed a problem that could occur in a very active multiuser environment where user passwords were corrupted in database profiles. (This problem occurred only in heavily used systems with many workstations.)
• Fixed a problem that occurred when Sage ERP Accpac tables exceeded 261 fields. If 3rd-party programs inflated tables beyond this size, forms that used those tables would close immediately when you tried to open them.
• Fixed a problem that prevented DBSpy from reporting error codes from most database calls.

^ Back to top

Bank Services

• Fixed a problem that occurred when reconciling OFX statements, where the program mismatched and reconciled incorrect transactions. For more information, see Knowledgebase article 210-30058.
• Fixed a problem that occurred when manually clearing withdrawals on OFX statements, where the program did not recognize transaction numbers that started with letters. For more information, see Knowledgebase article 210-30095.
• Fixed a problem that occurred when manually clearing withdrawals on OFX statements if you selected the option to match deposits by deposit slip. When you tried to clear a withdrawal, the program incorrectly reported that the amount on the OFX statements was different than the amount used in Bank Services. (This problem did not occur if you selected the option to match deposits by transaction number.) For more information, see Knowledgebase article 210-30095.
• Improved the performance of the Bank Reconciliation form. The program now displays outstanding transactions faster than in earlier releases of version 5.6 for bank accounts that have a large number of reconciled checks. For more information, see Knowledgebase article 210-31027.
• Fixed a problem that could prevent you from posting source currency bank entries if your Company Profile was set up to report errors when posting transactions to locked periods. If you tried to post a bank entry that used a rate date from a locked period, the system reported that the fiscal period was locked, even if the bank entry date did not fall in a locked period.
• Fixed a problem that could occur if your Fiscal Calendar contained a discrepancy of two years or more between a fiscal year and the fiscal year/periods contained in that fiscal year. In this very unusual circumstance, when you processed transactions, the program always checked the locked status for the first period in the fiscal year, regardless of the period to which you entered the transaction.
  

  For example, if you printed an Accounts Payable check that you entered for period 6 that started June 1 and ended June 30, 2010, but that period fell into fiscal year 2008 in the Fiscal Calendar, you could receive an error, a warning, or no message, depending on the setting for the Locked Fiscal Period option in the Company Profile. If the first period was locked, you received an error, and you could not post the check. However, if your system was set to display a warning or no message, you could post the check, but it would be posted to period 1.

^ Back to top

Accounts Payable

• A new form, T5018 Electronic Filing, is now available in the A/P Periodic Processing folder. You use this form to file Canadian T5018 information returns electronically. For more information, and for instructions on using this new form, refer to the revised Accounts Payable help included with this product update.
• Updated the 1099 Electronic Filing form to meet changed IRS specifications for the 2010 year. For more information, see Knowledgebase article 210-31250.
• Fixed a problem that prevented the creation of source codes for Accounts Payable when activating this program for a new company database.
• Fixed a problem that occurred when importing multicurrency invoices. The program used the session date, rather than the rate date specified in the imported transaction, to determine the exchange rate.

^ Back to top

Accounts Receivable

• Improved performance of the Customer Inquiry form when national account members are included in queries for national account customers. For more information, see Knowledgebase article 210-31051.
• Fixed a problem that prevented the creation of source codes for Accounts Receivable when activating this program for a new company database.

^ Back to top

General Ledger

• Fixed a problem that caused a runtime error when using the GIFI.xls and Budget.xls macros with 32-bit Microsoft Office 2010. After retrieving data into an Excel spreadsheet, an error occurred, causing Excel to close.

^ Back to top

Inventory Control

• Fixed a problem that caused SN/LT Data Conversion to fail if an existing Inventory Control cost adjustment included two detail lines with the same item number.
• Fixed a problem that prevented you from changing the account set for serialized or lotted items that used an account set with serial or lot costing.
• Fixed a problem that prevented some reports from displaying the costing method, and also caused some reports to display an incorrect number of items. For more information, see Knowledgebase article 210-29030.
• Fixed a problem that allowed the creation of invoices where the serial quantity was different from the quantity shipped for items that used serial costing. If you selected the option Allow Serial Quantity To Be Different From The Quantity In The Entries in the item record, and then changed the costing method for the item’s account set to Serial, you could create an invoice where the serial quantity was different from the quantity shipped.
• Fixed a problem that caused different values to appear in the summary and details of the Lot Tracking reports after upgrading to version 5.6. In some cases, the program displayed the error message "Convert LTHIST's cost adjustment with the same item numbers in two or more detail lines to IC Adjustment Detail lots failed" during the upgrade. For more information, see Knowledgebase article 210-30049.
• Fixed a problem that could occur when upgrading to version 5.6, causing conversion of Order Entry shipment history to Inventory Control serial number history to fail. For more information, see Knowledgebase article 210-30319.
• Fixed a problem that occurred during disassembly of a sub-assembly, which caused the program to display incorrect component quantities after disassembly. For more information, see Knowledgebase article 210-31052.
• Fixed a problem that could cause an error during Day End processing if you use the option to cost items during posting.
  

  When Day End Processing encountered a shipment that included two or more details with the same item number, if one of the details had a zero quantity and the other details had non-zero quantities, you would receive the error "Item Valuation. Record already exists," and Day End Processing would stop. (This might occur, for example, if the shipment included the same item at different locations but you shipped only from one location, or if the shipment was for multiple orders with duplicate items and you shipped only some of the items.)

^ Back to top

Purchase Orders

• Fixed a problem that prevented some optional field records from being posted to General Ledger.
• Fixed a problem that prevented the requisition cost from being updated if you created a requisition without vendor information, and then added vendor information.
• You can now change the G/L expense account for non-inventory items when you enter invoices, returns, debit notes, and credit notes, provided the option Create GL Entries For Non-inventory Expenses From Receipt/Return is not selected for your Purchase Orders system. Previously, you could not change the expense account for invoices, returns, debit notes, and credit notes, regardless of the setting for this option.
• Fixed a problem that produced blank Aged Purchase Order reports for single-currency companies that use ZAR as their functional currency.
• You can now import a receipt that is applied to a purchase order and that includes serial numbers or lot numbers without receiving an error message.

^ Back to top

Order Entry

• Fixed a problem that could cause incorrect information to appear in the OEAUDD audit table. If you entered an item followed by a miscellaneous charge in Order Entry, shipped and invoiced the order, and then ran Day End Processing, the extended cost for the item replaced the extended cost for the miscellaneous charge in the OEAUDD audit table.
• 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 form. 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."
• Fixed a problem that could prevent the Quantity Reserved For Order field on the I/C Lot Numbers form from being updated. If you shipped an order that included an item with a lot number, and then later set the Quantity Shipped amount to zero, the Quantity Reserved For Order field was not updated on the I/C Lot Numbers form.
• Fixed a problem that could occur when importing an O/E order with a new Inventory Control item. If the item had no location details and the Allow Negative Inventory Levels option in Inventory Control was not selected, the import failed and the program displayed the error message "Invalid input. Negative inventory levels are not allowed for item X at location Y."
• Fixed a problem that could prevent some detail lines from appearing in the OEINV01 and OEINV02 reports if your database was very large and you had not cleared history for a long time.
• Fixed a problem that occurred when selecting a customer or clicking the Totals tab on the Order Entry form. If you were using a Terms Code with a Discount Type of Discount Date Table, the program displayed the error message "Discount date entered cannot be later than the due date." For more information, see Knowledgebase article 210-30011.
• Fixed a problem that could occur if you inserted new items below the first item for a previously posted shipment, posted the shipment, and then repeated this process a number of times. When running Day End Processing after posting the shipment, the program displayed the error message "Shipment Cost-To-Clear Detail. Record already exists." For more information, see Knowledgebase article 210-30222.
• Fixed a problem that prevented setting Quantity Backordered to zero. If you created a partial shipment for an order, changed the default Quantity Backordered to zero, posted the order, and then reopened the order, the Quantity Backordered reverted to the original default value.
• Fixed a problem that occurred if you selected the option Print Only Labels Marked As Required when printing shipping labels by order number. An error message appeared saying that no records were found in the range you specified, even if there were required labels in the range.

• Fixed a problem that could occur when using the Copy Orders form to create a new order. If you changed the quantity ordered for an item that was not serialized or lotted in the new order, a warning appeared telling you that the Serials/Lots form would not be displayed. (Once you closed the warning, you could create and post the new order.)

• Fixed another problem that occurred when using the Copy Orders form to create a new order. The program used the tax group defined for the customer in the A/R Customer record. The program now checks whether a primary ship-to location exists for the customer, and if it does, it uses the tax group for the customer's primary ship-to location.

^ Back to top

Project and Job Costing

• Improved performance when posting revise estimate transactions for large databases.
• Fixed a problem that enabled some Timecard users to view, edit, and post other users' unposted timecards, although they did not have authorization to do so.
• You can now create a new invoice batch in Accounts Receivable when you post a billing worksheet, even if there is an unposted job-related batch in Accounts Receivable.
  

  If you always want to create a new Accounts Receivable batch whenever you post a billing worksheet, open the pm.ini file (using Notepad or another text editor), and insert the following line in the [General] section:

  CreateNewARBatch=1

• Fixed a problem that could occur when multiple users worked with billing worksheets and job-related invoice batches at the same time. If you opened a job-related invoice batch for editing in Accounts Receivable, and then another user posted a new billing worksheet before you saved your changes in the open batch, the program appended new invoices to your open batch and immediately changed the batch status to Ready To Post. Your changes were not saved, so you had to reopen the batch and re-enter the changes.
• Fixed a problem that could occur when upgrading to version 5.6, if you had changed the cost class used by cost type in the earlier version. When activating version 5.6, the program displayed the error message "Project Resource Activities. Attempt to modify a different record than was retrieved" or "Incorrect procedure. Update view PMRESC Failed," and the upgrade failed.
• Fixed a problem that could cause the PJC Detailed Transactions report to include excess details. If a contract included two or more resources with identical codes and you processed a transaction for one of the resources, the report also included a detail for the other resource. (The transactions were posted correctly, however.)

^ Back to top

Canadian and US Payroll

• Fixed a problem with the display of names in Timecard's finder. The Employee Timecard Finder now displays an employee’s first and last name details correctly.

^ Back to top

Intercompany Transactions (ICT)

• Fixed a problem that occurred when posting Accounts Payable batches from ICT. If one of the entries in a batch had an error that prevented it from being posted, subsequent entries in the batch would be posted to ICT General Ledger, but not to the remote company’s Accounts Payable. This resulted in discrepancies between the ICT General Ledger and the remote company’s Accounts Payable.

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

• Fixed a problem that could create a data integrity error after you cleared printed invoice posting journals using ICT's A/P Clear History form. Errors were reported under ‘Posting Journal Generated AP Entries and GL Details’ in the report generated after running the data integrity check.

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.

^ Back to top

Ops Inquiry

• Fixed a problem that occurred when running Ops Inquiry report if the Customer Group field contained four or more characters.
• Fixed a problem that prevented the Misys-SLT tab from being displayed.

Item Number Change

• Fixed a problem that prevented you from changing item numbers in PJC material returns transaction when running MS SQL.

^ Back to top

Changes Included in Product Update 1

This section describes program changes that were included in Product Update 1.

Improved LanPak Registration

Sage is implementing several new business processes that will help us to deliver an extraordinary customer experience.

One of our customer service enhancements is a streamlined license registration process. Now, when you purchase new LanPak licenses, you register only one LanPak serial number and one activation code for all users and database types.

Note: You now use the License Manager to register all new LanPak licenses. The Register button is not available for new LanPaks on the License Information form.

To record a new LanPak license in the License Manager:

1. On the Sage ERP Accpac desktop, click Help > Licenses > License Manager.
2. Check the License Information tab to make sure that the name in the Company field matches the name Sage used to issue the LanPak activation code. (Change the Company field only if the names don’t match.)
3. Click the Users tab.
   Note: The system allows you to register only one of the new LanPak licenses. If a new temporary LanPak license exists for this version, skip to step 6, and then follow the remaining instructions to enter your permanent registration on the existing line.
4. Right-click the grid, and then select Insert from the menu that appears.
   The new entry shows your current Sage ERP Accpac version and edition.
5. In the new line, double-click the License Type column, and then select LanPak from the list.
   Do not select a database-specific entry!
6. Double-click in the Count column, and then type the total number of users who require Sage ERP Accpac access for this installation. (The count is the sum of existing users plus the new users for whom you’re adding LanPak licenses.)
   If you already have a permanent license for this version, the system asks you to confirm whether you want to overwrite the existing license.
   If you receive this message, click Yes.
   The system immediately deletes any existing LanPak licenses.
7. Double-click in the Serial Number column, and then type the LanPak serial number that Sage provided.
8. Double-click in the Activation Code column, and then type the activation code that Sage provided.
   If you don’t yet have an activation code, you can create a temporary license by leaving the activation code blank.
9. Press Tab, or click elsewhere on the grid, to leave the field.
   The system changes the Count to the purchased amount (if necessary) and enters Activated in the Activation Code field.
   Important: You must record at least one LanPak 5.6 license to use Sage ERP Accpac.
10. Click Close, and then click OK.

For new installations, note the following:

• You enter your 10-digit customer account number in the Client ID field on the License Information tab. (You don’t have to change this field for existing installations.)
• You enter other information in the License Manager as described in Chapter 6 in the Sage Accpac Installation and System Administrator's Guide.

After Registering New LanPak Licenses

Note that once you register a new LanPak license, you can’t add new database-specific licenses. New LanPak licenses are effective for all supported database types.

Update for Integration Access Packs

We have also fixed a problem with IAP user licenses, which are required to run some external applications. The License Manager now correctly generates licenses for the 100 Edition and 200 Edition of Sage Accpac ERP.

^ Back to top

Updated Workflow Macros

Product Update 1 includes several AVB macros that can help you to manage your workflow. These macros were available in earlier versions, but not in the initial release of version 5.6:

• Workflow.avb Macro (Purchase Orders)
• WorkReq.avb Macro (Purchase Orders)
• Workmon.avb Macro (Purchase Orders)
• Oeordact.avb Macro (Order Entry)
• Reverseinvoice.avb Macro (Order Entry)

To ensure compatibility with version 5.6, this update installs two files from Microsoft’s security update KB957924, which enable the macros to work in Sage ERP Accpac version 5.6. The files are msflxgrd.ocx and richtx032.ocx.

To run the macros:

1. On the Macro menu, click Run.
   The Run Macro dialog box appears.
2. From the Files Of Type list, select VBA Macro Files.
3. Double-click the macro you want to use.

The rest of this section describes the individual macros.

^ Back to top

Workflow.avb (Purchase Orders)

Employees can use the Workflow.avb macro to send requisitions for approval. The employee highlights the requisition for which approval is required and sends it as an e-mail attachment to the manager's e-mail address.

Note: The Workflow.avb macro should be available only to employees with rights to enter a requisition in Purchase Orders.

WorkReq.avb Macro (Purchase Orders)

Employees can use the WorkReq.avb macro to request approval to purchase items and to specify the estimated cost of the purchase. The request is sent as an attachment to the e-mail address specified on the request for approval. A requisition is automatically posted for the request in Purchase Orders.

Note: The WorkReq.avb macro should be available only to employees with rights to enter a requisition in Purchase Orders.

Workmon.avb Macro (Purchase Orders)

Managers can use the Workmon.avb macro to approve requests for purchases from employees. When a manager receives a Requisition Request by e-mail from an employee, the manager can either approve or reject the request.

If the manager approves the request, a purchase order is created automatically for the items, and an e-mail confirmation is sent to the employee.

If the manager rejects the request, an e-mail is sent to the employee. The manager can provide the reason for rejecting the request.

Note: The Workmon.avb macro should be available only to employees with authority to approve or reject requests for purchases.

Oeordact.avb Macro (Order Entry)

You can use the OEordact.avb macro to create a dynamic Order Action report in Microsoft Excel.

You can specify whether to print details or a summary report, you can select the orders to include according to their item status, print status, and whether they have been invoiced, and you can select ranges of order numbers, dates, customers, salespersons, and order totals.

^ Back to top

Reverseinvoice.avb Macro (Order Entry)

Employees can use the reverseinvoice.avb macro to create a credit note and recreate shipments for a specified invoice.

Note: Be sure that the invoice has been processed by Day End Processing before you try to reverse it using the macro.

^ Back to top

Product Update 1 Program Fixes

The following sections describe program fixes that were included in Product Update 1:

• Bank Services
• General Ledger
• Accounts Payable
• Inventory Control
• Purchase Orders
• Order Entry
• Serialized Inventory
• Project and Job Costing
• Return Material Authorizations
• Item Number Change
• Vendor Number Change
• Canadian and US Payroll

Bank Services

• If you activate your data after installing this product update, you can view and reverse deposits posted in version 5.3A.
• Attempting to reverse an A/R deposit no longer causes a bank reconciliation to fail to post. We strongly recommend that you run Data Integrity for Accounts Receivable and Bank Services after installing this product update.
• Deleting a bank entry for a bank other than the default bank now deletes the correct bank entry and removes the associated transaction properly from the Reconciliation tab, so you can post the reconciliation. (Before this product update, the program correctly removed transactions only for the default bank.) Note: You must install Product Update 1 before you can delete a bank entry for a non-default bank successfully. If you continue to have problems afterwards, you may want to contact your Business Partner or Customer Support.

^ Back to top

General Ledger

• G/L Period End Maintenance no longer stops when you try to delete inactive accounts for which there are unposted journal entries. The program now displays an error message, and proceeds with the remaining period-end maintenance tasks.

^ Back to top

Accounts Payable

• A/P Invoice Entry correctly inserts details for distribution sets.

^ Back to top

Inventory Control

• Day End Processing no longer displays the error “Invalid input. Location does not exist” when it encounters I/C adjustments that include non-stock items and non-existent locations.
• The I/C Movement Report correctly shows quantity changes from credit notes posted in previous versions.
• The I/C Item Valuation report now uses the quantity in stocking units of measure to determine quantities in inventory.
• You can save I/C Assembly entries even when there are insufficient item quantities on hand.
• You can allocate lot numbers when the stocking UOM is different from the lot UOM. Item validation is now correct, so you no longer receive the message “Invalid Input. There are insufficient quantities to be removed …”
• If you were using simplified serial numbers in earlier versions, activation now removes serial records that are no longer associated with document details.
• You can drill down to Ops Inquiry from I/C Stock Transactions Inquiry (provided Ops Inquiry is activated).

^ Back to top

Purchase Orders

• After upgrading from version 53A, you can edit purchase orders created in the earlier version without producing Day End Processing errors.
• You can no longer change the Expense account for non-inventory items during P/O Invoice Entry.
• You can now post a P/O Order Entry that includes a required optional field.
• The Item Finder now correctly displays item optional fields in standalone Purchase Orders programs.
• You can drill down to Ops Inquiry from P/O Order Entry (provided Ops Inquiry is activated).
• You can no longer change the G/L account for posted Purchase Orders transactions that use non-inventory or non-stock items.

Correction: Purchase Orders help suggests that you can partially invoice receipts for serialized or lotted items. Note that in version 5.6, partial invoicing of such receipts is not permitted.

^ Back to top

Order Entry

• O/E Invoice Entry no longer lets you post an invoice to a locked fiscal period when you create the invoice using O/E Order Entry or Shipment Entry.
• Order Entry now passes to Shipment Entry any tax classes that you override in O/E Order Entry.
• Drilling down from General Ledger to Order Entry no longer generates a query run error if the internal order number in the database is very large (more than 10 digits).
• You can drill down to Ops Inquiry from Shipment Entry, Invoice Entry, and Credit/Debit Note Entry (provided Ops Inquiry is activated).
• O/E Picking slips that print on multiple pages now include “Continued on Next Page.”
• Picking slips show complete references, without truncation.
• You can post quotes, standing orders, and future orders in Order Entry regardless of inventory levels.
• O/E Current Orders Inquiry now includes transactions that have blank Expected Ship Date fields.

^ Back to top

Serialized Inventory

• I/C Serial Number Transaction Inquiry shows transactions posted in any third-party programs.

^ Back to top

Project and Job Costing

• Taxes are allocated to the correct tax group when you post job-related costs from Order Entry and Purchase Orders. (The A/R item provides the default tax classes.)
• Posting revised estimates to an internal project no longer generates an error message.
• Creating material usage transactions that use different units of measure no longer generates the message “Negative inventory levels are not allowed for item” when there is sufficient stock.

^ Back to top

Return Material Authorizations

• Important: Product Update 1 includes a database change for RMA 5.6. RMA will be disabled until you reactivate your data.
• RA Entry includes a number of improvements in the way it handles lots, serials, and special characters.
• You cannot delete optional fields that are used in an RMA entry.
• The customer account set Finder displays only account sets that use the customer’s currency.
• You can no longer delete templates that are used in existing RMA documents.
• Price discounts are now calculated correctly after you change the customer type.

^ Back to top

Item Number Change

• You can now apply A/P payments and A/R receipts to job-related documents after using the Item Number Change program to change item numbers.

^ Back to top

Vendor Number Change

• Combining vendors that used the same document number on A/P invoices no longer generates an error for document numbers longer than 22 characters.

^ Back to top

Canadian Payroll

• We have improved the performance of paycheck printing and posting when there are many history details. For more information, see Knowledgebase article 210-29022.
• The overtime rate is calculated properly for overtime schedules that include multiple lines, where the first line includes Hours Over equal to zero.
• Cost center overrides work properly for employer deductions.
• You can import job-related timecards without receiving the error “P/M Job Resource Validation. Attempt to change read-only field ‘Billing Type’.”
• The Earnings report now prints the following new Box O codes for the RL1 Reporting field:
  
  • CA - Wage Earner Protection Program
  • CB - Tax-free Savings Account
  • CC – Beneficiary of an RDSP

US Payroll

• The overtime rate is calculated properly for overtime schedules that include multiple lines, where the first line includes Hours Over equal to zero.
• Cost center overrides work properly for employer deductions.
• You can import job-related timecards without receiving the error “P/M Job Resource Validation. Attempt to change read-only field ‘Billing Type’.”
• The Employee Information report now prints the current Arizona tax rates.

^ Back to top