March 2005

1. Monthly Product Update March 2005

2. Infrastructure to License e.net Run Time Product Implemented Business Case: Third party product developers can now develop applications that can use e.net Business Objects without having to configure e.net licenses on the customer’s system Port 06

3. Presented By Diane Fryer

4. Agenda • Overview of Enhancements • Distribution • Manufacturing • General • Business Objects • Known Issues

5. Issue 009 Enhancements Distribution Ports 14 - 17

6. Product Configurator – allow creation of master/sub jobs • What has been done • A new 'Create sub job for • component' option has been added to: • Product Configurator • Component Maintenance • Product Configurator • Job Creations program Why this was done To automatically enable you to create linked sub jobs when creating a master job that has made-in components. Port 14

7. Product Configurator – apply invalid selection criteria to entire sections The List of Configurations now reports on invalid selection criteria against each section New Source and Invalid checkboxes enable the designation of an entire section as being either the Source or Invalid Port 14

8. Product Configurator - Associate setup time with Selection Criteria What was done You can now use Selection Criteria as a factor to calculate set-up time for internal operations. Why this was done To associate Selection Criteria as a factor when calculating set-up time for internal operations. Port 14

9. Product Configurator – check components on hold • What was done • When called by Sales • Orders, Product Configurator • now checks the stock code On • Hold status when: • either no parent part exists • OR • the parent created is a kit type • When called by Quotations, • Product Configurator displays an • ‘On Hold’ warning message Why this was done There is a need to establish whether a selected component is on hold. Port 14

10. Product Configurator – Update BOM costs What was done The BOM costs are now updated for the single level of a new parent created in the Product Configurator. These costs are updated in the BOM creation process. In a Standard Costing environment, it is useful if the BOM costs are immediately updated when a new parent is created using the Product Configurator. This avoids having to wait until the Cost Implosion has been run to view the updated costs. Port 14

11. Product Configurator - SQL optimization What was done The Product Configurator program has been enhanced to improve performance in a SQL environment when processing complex configurations Port 14

12. Product Configurator browse on non-stocked codes defined in Quotations • What was done • The following programs now allow you to browse on the non-stocked code in Quotations: • Product Configurator Component • Maintenance • Product Configurator when • creating a non-stocked parent. • This is only available if the Quotations module is installed. Port 14

13. Product Configurator - optionally update warehouse costs What was done The option: 'Do not update Warehouse cost for existing parent‘ has been added to the Configuration tab of the Inventory Setup program. Why this was done This allows the prevention of warehouse costs being updated when configuring a product from within Sales orders for an existing parent that does not have a bill of material and for which the quantity on hand is zero. Port 17

14. P/O – changes to emailing of P/0 docs What was done The Purchase Order Document programs that request email configuration information now use a generic email interface program. This allows you to query recipient email addresses, Cc recipients and enter up to 5000 characters of body text. Why this was done To address the need to query and retrieve recipient email address details and to enter more text to accompany attachments • The following programs • now use the standard • SYSPRO email interface: • Purchase Order Entry • Requisition Entry • Blanket P/O Entry • Purchase Order Print • Requisition Print • Blanket P/O Print Port 16

15. S/O Batch Printing caters for printer preferences & additional fields • What has been done • The Sales Order Batch Printing program allows a specific printer to be used for each of the following document types: • Delivery notes • Order acknowledgements • Invoices • Credit/Debit notes • Dispatch notes • Dispatch invoices and consolidated dispatch invoices • SCT transfer and Dispatch SCT transfer • The Operator name can be printed in the heading section on all S/O documents • A maximum of 10 custom form fields can be printed on any S/O document • Geographic Area code and name can be printed on Header of all S/0 documents • Order acknowledgement can optionally be printed for debit/credit notes • Customer selection allowed for all S/O documents except SCT’s • Why this was done • Additional information needed to be printed on S/O documents • Different types of S/O documents typically require a specific stationery format or printer to be used. Port 14

16. S/O Batch Printing caters for printer preferences & additional fields …1 Port 14

17. S/O Batch Printing caters for printer preferences & additional fields …2 Port 14

18. Issue 009 Enhancements Manufacturing Ports 14 – 17

19. BOM - Route selection added to ABC Recoveries Estimate report • What was done • A route selection has been added to the Recoveries Estimate Report allowing you to indicate the specific route for which you want to print overhead recovery costs against an item. • The layout of the import file has changed to accommodate the route selection Port 17

20. Quotations - Add custom forms for non-stocked codes What was done You can now include a custom form for non-stocked items. Why this was done To provide greater flexibility when setting up non-stocked codes Port 14

21. Quotations – allow without expiry date What was done There is a new 'Allowzero expiry date' option in the Quotations Setup program Why this was done There is a requirement to capture quotations without an initial expiry date (i.e. to retain quotes indefinitely). Port 14

22. Projects & Contracts – suppression of zero value heads on Contract Progress Report What was done A new option was added to Contract Progress Report This is only available if Printing the report in Detail Why this was done To give the user the option of printing heads which have Zero values. Port 15

23. Issue 009 Enhancements General Ports 14 – 17

24. Report Writer prints Report Totals on a separate page Why this was done To be able to supply Individuals with just their information Note: This option has no effect if the report only has a Report Total, or the report type is Extract or XML. What was done A new report option: 'Print Report Total on separate page' has been added Port 15

25. Use command line parameters to run MRP Requirements Calculation automatically Why this was done There is a need to be able to schedule the Requirements Calculation to run automatically (e.g. after hours) using a product like Microsoft Scheduled Tasks. "C:\Program Files\SYSPRO60\base\IMPAUT.EXE" /oper=ADMIN /comp=0 /prog=MRPP40 /link=Function:RECJ Log:C:\Mylog.txt /h • The following functions are supported in the /link parameter: • /link=Function:NEW (takes a new snapshot) • /link=Function:DEL (deletes the current snapshot) • /link=Function:REC (recalculates, recreating suggested jobs • /link=Function:RECJ (recalculates, retaining current suggested jobs) Port 15

26. Operator Amendment Journals • What was done • The Operator Maintenance program • now outputs amendment journals • for any changes made to operator • settings. • the date and time of the change • the tab page that was changed • the field that was changed • the value before the change • the value after the change • the operator who made the change Why this wasdone To enable Administrators to monitor changes made to operator settings. Operator settings affect defaults, options and security, each of which can have serious implications if changed Port 16

27. Browse on operators available Browse on operators available when printing or copying operators What has been done A new Operator Browse program is invoked automatically whenever the system detects that the standard Operator Browse is already in use. This allows operator browsing when listing, copying operators or copying operator printer settings. The new Operator Browse does not contain any operator maintenance functions Port 16

28. Word Printing – tag file per format What was done An individual tag file is now created for each MS Word Stationery Format called IMPWRF??.IMP where ?? indicates the last 2 characters of the relevant format program Why this was done Previously, a single MS Word tag file (IMPWRF.IMP) accommodated the tags for all SYSPRO's Stationery Format programs. This made it difficult for developers to work on more than one format at the same time. Target Audience: Developers Port 16

29. Generic Find caters for up to 15 search criteria fields What was done The Generic Find facility has been enhanced to cater for up to 15 search criteria fields. Previously, only 6 fields were catered for. In addition, the Find function available from the Browse on Sales Orders now allows you to use the Alternate key field as a search option. The Find functions still have to be enhanced to allow selection of the additional search criteria. In the future, developers will be able to provide additional search criteria for their Find functions Port 16

30. Provide ASCII/HEX/GUID conversion and True/False Logic functions for developers Why this was done There is a need for developers to be able to convert between ASCII and HEX formats, as well to be able to convert GUIDs between 16 byte (128 bit) formats and industry-standard 36-character formats. In addition, some developers require the ability to determine whether a result is True or False, according to a complex table of True/False and And/Or logic. What has been done Four new functions can be used by Developers to convert their data. A new function can be used to test if result is True of False. See all about this in the latest SDK.CHM Port 16

31. Issue 009 Enhancements Business Objects Ports 14 – 17

32. Product Configurator Finished Details Business Object - Security checks removed Why this was done When the Quotation Import and Maintenance Business Object is called from the Product Configurator Finished Details Business Object, the security check does not need to be repeated. What was done The Product Configurator Finished Details Business Object ignores the security activity checks in place for the Quotation Import and Maintenance Business Object because the required checks have already taken place. In addition, two elements were modified to cater for negative values Port 14

33. Product Configurator Business Object allows creation of master/sub jobs What was done The Product Configurator Business Object caters for the new option: 'Create sub job for component' that can be set against a component within the Configurator Component Maintenance program. Why this was done To enable e.net solutions developers to create linked sub jobs at the time of creating a master job with made-in components Port 17

34. Product Configurator B/O allows Invalid Selection Criteria to point to the Selection What was done The Product Configurator Business Object now allows Invalid Selection Criteria to point to the Selection instead of the individual Selection Criterion. In addition, you can set the Selection to be invalid. Why this wasdone To enable e.net solutions developers to cater for Invalid Selection Criteria Port 17

35. Product Configurator B/O allows setup time to be associated with Selection Criteria What was done The Product Configurator Business Object that processes operations, now caters for the option that allows you to use Selection Criteria as a factor against setup time for internal operations. Why this wasdone To enable e.net solutions developers to associate setup time with Selection Criteria when using the Product Configurator Business Object. Port 17

36. Product Configurator Business Object checks for components on hold • What was done • Error messages are returned if you attempt to: • create a kit type parent for which a mandatory component is on hold. • (Optional components that are on hold are ignored). • select a component that is on hold and you are not • creating a parent part or ignoring warnings. Why this wasdone To enable e.net solutions developers to check the on hold status of components when running the Product Configurator Business Object. Port 17

37. Product Configurator Business Object updates BOM costs What was done The BOM costs are now updated for the single level of a new parent created using the Product Configurator Business Object. These costs are updated in the BOM creation process. Why this wasdone To be able in a standard costing environment to update the BOM costs immediately, instead of having to run the cost implosion in order to update them. Port 17

38. Product Configurator Business Object optionally updates warehouse costs What was done The option: 'Do not update Warehouse cost for existing parent‘ has been added to the Configuration tab of the Inventory Setup program. Why this was done To enable e.net solutions developers to optionally update the warehouse cost of an existing parent when using the Product Configurator Business Object. Port 17

39. Build S/O Line B/O returns service charges, dangerous goods and stock text Why this was done To allow developers to return additional information relevant to a potential sales order line. What was done The S/O Build Sales Order Line Business Object includes three new options to control the return of data. Port 14

40. New Sales Order Document Query Business Object Why this was done The information provided by Sales Order Document Formats includes complex calculations that developers cannot easily reproduce from the raw data returned by other Sales Order Query Business Objects. This business object returns the information that can be printed on the Order Acknowledgement and Delivery Note documents in SYSPRO. • What has been done • New options added to existing elements • New element added • Filters that can be applied to restrict amount of data returned Port 16

41. S/O Query Business Object now returns information about dispatch invoices Why this was done The Sales Order Query Business Object now caters for invoice information produced from dispatch notes. Previously, only invoice information produced from sales orders was catered for. What was done The Sales Order Query Business Object now returns the invoice information of an invoice created for a dispatch note. Port 16

42. S/O & Inventory Query B/Objects now return additional UOM information • What was done • Sales Order Query • The following are returned in the stocking • Unit Of Measure: • Order quantity • Back Order quantity • There are four new elements • Inventory Query • The conversion factors for the following • Units of Measure are returned: • Alternate • Other • There are four new elements Why this was done It is necessary to see all quantities in the stocking and order units of measure to ensure that the correct quantities are picked. Port 16

43. S/Order Business Objects optionally returns warning conditions with warning message • What was done • The following Sales Order Business Objects now allow a warning to be • returned as a warning rather than as an error: • S/O Sales Order Import • S/O Change Sales Order Status • S/O Invoice Calculation from Sales Orders • Why this was done • To enable e.net solutions developers to distinguish between a warning that • can be ignored or an error that will cause the transaction to be rejected. Port 17

44. Sales Order Import Business Object caters for more elements • What was done • The Sales Order Import Business Object allows entry of 2 additional elements. • Allows existing merchandise line price to be changed to zero • Why this was done • To enable more elements to be passed when adding sales orders, thus avoiding operator maintenance later. Port 17

45. New WIP Tolerance Query Business Object for Progressive Scrap Why this was this done To enable e.net solutions developers to develop applications to query the progressive scrap tolerances of operations. Port 14

46. Issue 009 Known Issues Ports 14 – 17

47. Entries missing in Accounts Payable General Ledger Distribution This problem occurs on sites using software later than Issue 008 port 13 It has been corrected in Issue 009 port 14 For full details of how to correct the data ensure you read the entire notice on the Support Zone regarding this problem.

48. Cash Book Print program running slowly (SQL Only) When running the Cash Book Print program, the task takes longer than expected and results in an overload of resources on the server. The problem is in CSHP41 6.0.006. (Introduced in Issue 008 Port 33) This program has been fixed for SYSPRO 6 Issue 009 and is currently in QA. The patches will be made available as soon as possible.

49. Cash Book Print program running slowly (SQL Only) – temporary workaround Do the following before running the Cash Book Print: • Prevent Logins on all companies • Get all operators to logout of SYSPRO • Select Setup > System Setup. • On the General tab, in the Options block, type NoOpt in the Site field. • Save the system setup. • Log out and back in again (the new system settings will only take effect after exiting from SYSPRO) • Run the Cash Book Print. • Select Setup > System setup • Clear the Site field. • Save the system setup. • Log out and back in again

50. Cash Book – missing entries or incorrect entries on Distribution Report This problem was introduced in SYSPRO 6.0 Issue 009 Port 12. If you have not yet done so, please do not upgrade to Port 12 or later until a suitable patch has been implemented. Details Cash book Withdrawal and Deposits either do not reflect on Distribution Report or incorrect entries reflect in Distribution using exclusive tax. Solution The following programs are required to correct the problem IMPCSH.INT Ver 008 CSHP10.INT Ver 037 After downloading the new software, ensure that the Cash Book Setup program is loaded and saved. The program changes have resulted in the retraction of a recently released enhancement to allow tax values to be apportioned to the G/L code that is held against the tax code, instead of the entire value being posted to the default tax code for deposits and withdrawals.