Sage Pro 100 ERP Version 7.5 Service Pack 2 Readme Addendum to Documentation – April 1, 2009 Copyright© 2008 by Sage Software, Inc. All Rights Reserved. Sage Software, Inc ® is an industry-leading developer of accounting and e-business management solutions for small and medium sized enterprises. For more information, visit us at http://www.sageproerp.com/ These instructions supplement and clarify the program documentation for Sage Pro 100 ERP version 7.5, Build 3500.00, Service Pack 2. TABLE OF CONTENTS 1. General Information 2. Installation Instructions 3. 941 Update Requires Data Dictionary Update : PTR 90511 4. Run p89088_update 5. Run p90562_datafix 6. Run p89916_datafix 7. Run p89613_datafix 8. Run_p90082_datafix 9. PTR Update Information 1. General Information Please consult with your Service Provider before installing this Service Pack. 2. Installation Instructions All updates must be installed to the appropriate Sage Pro ERP folder. 1. Copy the SagePro75B3500_00_100_SP2.exe file into a temporary folder (for example, C:\temp\). 2. Verify that all users are logged out of Sage Pro 100 ERP and close the application. 3. Verify that you have made a complete backup of your Sage Pro 100 ERP program folders, system data and company data before installing this Service Pack. 4. Delete the ‘DataViews’ folder from the Sage Pro 100 ERP root directory (i.e. C:\Pro75\). 6. Navigate to the temporary folder selected in Step 1 and run the SagePro75B3500_00_100_SP2.exe self-extracting zip file. 7. Follow one of the steps listed below based on the Sage Pro ERP applications installed in your system (i.e.: AP, AR, CU, GL, IC, JC, PE, PO, PR, SO, WA and WO): Option 1. If all applications are installed, then change the “Unzip to folder” to your Sage Pro ERP root directory (i.e. C:\Pro75\). Click “Unzip”. This will unzip all files and folders contained in the Service Pack. Then go to Step 8. Option 2. If Sage Pro ERP has limited applications installed, in the dialog; change the “Unzip to folder” to a new temporary folder (for example, C:\Temp1). Click “Unzip”. This will unzip all files and folders contained in the Service Pack into the new temporary folder. · Copy all of the files (not the folders) extracted in the new temporary folder (for example, C:\Temp1) to your Sage Pro ERP root directory (i.e. C:\Pro75) · Copy the files in each subdirectory of the new temporary folder (for example, C:\Temp1\IC) to the respective subdirectory in the Sage Pro ERP root folder (i.e. C:\Pro75\IC) only for the applications that are installed in Sage Pro ERP. Note that folders will exist in your Sage Pro folder for applications that you do not have installed. Do not copy any files into those folders (for example, if you do not have the IC application installed, do not copy the files in C:\Temp1\IC into your C:\Pro75\IC folder). Also, do not delete any of these folders. · Be sure to copy the files that are inside the SM folder of the new temporary folder to the SM folder in your Sage Pro ERP root folder (i.e. C:\Temp1\SM\*.* to C:\Pro75\SM) · If you have Payroll installed, copy the entire folder DdImport from the new temporary folder to the Sage Pro ERP root folder (i.e. Copy C:\Temp1\DdImport to C:\Pro75) 8. Follow steps in the next sections based on the applications that you have installed. 3. Payroll issue : PTR 90511 : 941 Update Requires Data Dictionary Update A New field QCOBA in PREMWG has been added to store COBRA Premium assistance Payment Amounts. 1. Start Sage Pro 100 ERP. 2. Log in as the Administrator. 3. Select File | Open | System Manager. 4. SM | Maintain | Dictionary | Import/Export 5. Set Action to “Import” and Table ID to “PREMWG” and Proceed 6. Select Folder : “C:\PRO75\DDImport\PREMWG” and Import dictionary files. 7. SM | Transaction | System Recovery | Update from Data Dictionary 8. Select all Payroll companies and Press Enter Key 9. Rebuild all indexes and Update files for Payroll applications from data dictionary. Note : If you already have updated QCOBRA field by using March 2009 PUP installation, skip PTR 90511 data update. 4. Payroll issue : Run p89088_update P89088_update updates the PRPTCLxx.DBF table in Your Sage Pro 100 ERP installation to support HSA employer’s and employee’s contributions. 1. Start Sage Pro 100 ERP. 2. Log in as the Administrator. 3. Select File | Open | FoxPro Access. 4. Type "DO P89088_UPDATE" without the quotes. Steps 4 needs to be repeated if there are more than one company where data discrepancy need to be removed. 5. Press "ENTER" to return to the Sage Pro 100 ERP application. 5. Payroll issue : Run p90562_datafix P90562_datafix updates the Employee’s history tax PREHTXxx.DBF table in Your Sage Pro 100 ERP installation to reverse Group Term Life Pay Amount from Employee’s State Wage. 1. Start Sage Pro 100 ERP. 2. Log in as the Administrator. 3. Select File | Open | FoxPro Access. 4. Type "DO P90562_DATAFIX" without the quotes. Steps 4 needs to be repeated if there are more than one company where data discrepancy need to be removed. 5. Press "ENTER" to return to the Sage Pro 100 ERP application. 6. Payroll issue : Run p89916_datafix P89916_datafix updates the CLOSING PAYROLL LEAVES SOME DATA IN CURRENT AND IN HISTORY. 1. Start Sage Pro 100 ERP. 2. Log in as the Administrator. 3. Select File | Open | FoxPro Access. 4. Type "DO P89916_DATAFIX" without the quotes. Steps 4 needs to be repeated if there are more than one company where data discrepancy need to be removed. 5. Press "ENTER" to return to the Sage Pro 100 ERP application. 7. Payroll issue : Run p89613_datafix P89613_datafix will delete the duplicate invoice records from ARYMST and ARYTRN tables 1. Start Sage Pro 100 ERP. 2. Log in as the Administrator. 3. Select the company for which the fixtool is to be run. 4. Select File | Open | FoxPro Access. 5. Type "DO P89613_DATAFIX" without the quotes. 6. Press "ENTER" to return to the Sage Pro 100 ERP application. Steps 3 - 6 needs to be repeated if there are more than one company where data discrepancy need to be removed. 8. Payroll issue : Run p90082_datafix P90082_datafix will This Program will correct the data discrepancy created in the ICTRAN tables due to the erroneous conversion of transaction type in the landed cost transfer. 1. Start Sage Pro 100 ERP. 2. Log in as the Administrator. 3. Select the company for which the fixtool is to be run. 4. Select File | Open | FoxPro Access. 6. Type "DO P90082_DATAFIX" without the quotes. 6. Press "ENTER" to return to the Sage Pro 100 ERP application. Steps 3 - 6 needs to be repeated if there are more than one company where data discrepancy need to be removed. Note : The Recalculate Application Balances should return no errors relating to: discrepancy in ICILOC, which were created when applying to shortage, on transfer from landed cost location. 9. PTR Update Information Appl. PTR# Issue AP 89517 Problem: With the new methodology of storing Inventory history in the ICISUM table, new code was written to calculate prior periods... default being 12 periods for the above mentioned reports. The resulting value of the last period is stored in variable lc_CuttOffPeriod. When this variable is used in the SQL statements for these reports, it has been written using greater than and thus misses the last period in the range chosen (again, defaulted to 12, it would be missing the 12th prior period). In this way, the above mentioned reports in Pro Series 7.4 can not match Pro Series 7.3 if there is usage in that 12th period. AP 89673 In Pro 7.4 the users could create new vendors and assign the Default and Control account for the vendor. However, in Sage Pro 7.5 the users are not able to enter in the Default and Control accounts in the Vendor Maintenance screen. AP 89752 When the client is releasing to GL from AP, they are experiencing a batch that has an empty total number with no transaction details. AP 90178 Printing the AP-PO Audit Trail report with a date range that should only include current transactions does not filter out old archived data. AR 89613 Duplicate invoice records in arymst when archiving AR. This occurs when converting from an installation prior to Sage Pro 7.4 to Sage Pro 7.5 CU 90112 Parent class location will always be used regardless of import location of custom class. GL 90419 The General Ledger Total Company and General Ledger Single Segment reports are slow in SQL databases with large numbers of records. The update statement put in for PTRs 85388 and 85161 to show AP entry comments on the report is what is causing the problem. Update uses GLDENT which has about 1.5 million records in this case. IC 88537 Customer wants ability to reverse the issue of serialized inventory so that you can get the inventory back with the same serial number. IN 87588 The Solution: Future Service Packs need documentation that includes steps for the Users that do NOT have all applications. Users should be advised to how to install the Service Pack into a temporary folder and manually copy the required files for their particular installation. They should also be warned not to delete any folders or files that are already in their Pro installations. JC 90017 In a Multi-VAT company (with or without MC installed) a user creates a PO in Job Cost selecting a non-stock item as the line item on the PO. After saving the PO the user goes to the PO module to receive that purchase order in full. then when the user views the IC Journal Report or goes to JC Job Master Maintenance screen to view the Detail Inquiry on the job they will see that the cost of that item gets doubled. JC 90063 If you import time cards into a JC application using Multiple VAT taxation, the first record in the import file fails to post. JC 90153 An error 11 will occur when posting a non-check payment to a payable in JC. It appears to be failing when trying to update APMAST. MM 89605 Customer reported that the batch printing mode in 7.5 does not work properly, it does not seem to pick up the misc code. PE 89573 It is possible for items to duplicate issues for components on a configurable BOM that also creates a work order. This will happen if the user saves a sales order with a BOM configuration. If they edit the sales order and add a line all records will be added to PETRAN. When the sales order is shipped all items in PETRAN will be issued and the finished good received in. When the WO is completed it will also issue and receive the inventory. This will create the duplicate postings. PE 89766 The wrong cost of a finished good item will get issued incorrectly on a sales order shipment if the sell unit of measure factor is not = to 1. PE 90186 Customer reported that after converting to 7.5, they are receiving duplicate overship records from PE transactions in ICTRAN. PO 89765 Partner reported that using Landed Cost in a standard cost company, the resulting cost used when transferring from the Landed Cost Location to the Warehouse location is not the standard cost + variance, but it is actually the landed cost itself. PO 90092 When entering a PO return the transaction always comes from the default location in IC. Example in company 99 is WH1. You will notice the header screen of the PO keeps reverting to WH1 even after the users enters in another location. This does not happen in 7.4. PR 89053 When they do PR reports and it allows them the choice to choose employees are departments it takes about 2 minutes, just to get past the option in the option grid (they don’t even select the employee or department. I have fixed it to be done in under 23 seconds (see attached prproc.org, rename it to prproc.prg) for my fix. The way I have fixed it: Instead of using m_CopyTo to copy from the VFP temp table to SQL, I created the table in SQL and then did m_AppendFrom and made it use DTS. This got the option to run much faster. PR 89088 The employees are allowed to contribute to their own account also. The client would like to be able to do so by doing this as a deduction (just like a 401K plan). This money will be taken out of their pay and pay it to the bank that holds their HSA acct. This also needs to be reported in box 12 code W on the W2. PR 89574 When printing the check register or the payroll register, the deductions of some of the employees are missing. PR 89749 When the client is doing payroll, they realized that they have set SUTA tax to have a maximum of 500. When they do the next payroll, they hit over the 500 dollar limit. The issue is that the taxable wages should have stopped at 500.00 and record the remaining wages to over limit. Instead, it added the whole amount to the taxable wages, thus this is not correct. PR 89916 While closing payroll, a direct deposit posting that has not been posted has left posting information in history and current tables. The posting information should either go all in History tables or Current tables, not both. PR 90410 Posted earnings report run from history with large tables is unacceptably slow in SQL. PR 90427 Posted earnings report run from both current and history with large tables is unacceptably slow in SQL. Due to m_copyto which pulls history data from server. PR 90428 Payroll Tax Reguster report run from both current and history with large tables is unacceptably slow in SQL. Due to m_copyto which pulls history data from server. PR 90562 The GPTERMLIFE pay class is marked as SWT Taxable so pay based on this pay class is included in SWT wages. SM 89759 Whe the user wants to modify the Structure of their fiscal calendar (closing early, etc), once reclassifying, they get the following error message: SM 90409 User reported that an error 12 exists trying to edit a fiscal calendar in an install with no IC. SO 89461 Importing in 3 drop ship lines does not mark the second line as a drop ship item and assigns the second drop ship line to the default location defined in the header screen. It should recognize the line as a drop ship item. SO 89521 Customer reported that printing an order from the add order screen through fax/email only will not mark the order as printed (will not flag prtid in SOMAST) SO 89529 Variable not found when printing Labels SO 89603 While the Client Partially shipped items, the client reprints the packing slip. On one of the items, it says that it shipped -4 items but in fact they shipped none. SO 89740 After applying SP1 to 7.5 the following message appears when entering a sales order for a non-stock finished good assigned to a BOM set to explode at time of shipment. This message was put in as part of a fix for PTR 88690. The user is complaining that this message slows down their process. Many of their items are non-stock and never have a cost associated with them. The raw good on the BOM also do not have a cost so there is no cost to rollup. SO 89951 Shipping lotted items when the first item on the SO has no price and is not lotted gives the following error: Item EGM2SAMPAFA at location WH1 not found in item quantities file. Inventory update cancelled. You can continue with the process but you will end up with partial file updates which corrupts data integrity. SO 90116 Customer reported that are experiencing an error 12 printing batch orders after shipping multiple orders, and cancelling one. SO 90353 When ICYTRN reaches a certain size, it will impact the time it takes to print packing slips from SO. SO 90421 In the Order Entry screen there is a PO number field. The following errors will appear if you include an apostrophe (') in this field. WA 89855 The client defined an event ORDERENTRY. This allows the user to be notified by email after a Sales Order has been entered. Once the polling starts in Order Entry, it does not send an email out. WO 89602 Std cost rollup for components does not update the ICILOC.Slsdcst field. This means the sales order item cost field is not updateed which can impanct decsions by sales on sales pricing. WO 89604 If a WO is created with a serialized finish good and a serialized component and the component serial number is assigned the assigned number will be cleared when editing the WO