PRONTO-Xi Dimensions Service Pack 2 Release Notes

Pronto Software © 2011 Software Version: 700.2 Release Notes

Page ii Commercial in Confidence

© Copyright 2011 Pronto Software Pty Ltd. All rights reserved.

Release Notes, Version 700.2

Trademarks

® - PRONTO, PRONTO ENTERPRISE MANAGEMENT SYSTEM, PRONTO SOFTWARE (Logo) and PRONTO-Xi, are trademarks registered by Pronto Software Pty Ltd (ABN 47 001 337 248) in the United States of America, Australia and other countries.

™- trademarks of Pronto Software Pty Ltd (ABN 47 001 337 248)

IBM® and Cognos® are trademarks of International Business Machines Corporation.

Disclaimer

The information contained within this document is provided on an “AS IS” basis, is subject to change without notice, and is not warranted to be error-free.

PRONTO-Xi Table of Contents

Release Notes Software Version: 700.2 Pronto Software © 2011

Commercial in Confidence Page iii

Table of Contents

Introduction .............................................................................................................................................. 1

Business Intelligence ............................................................................................................................... 2

Framework ............................................................................................................................................... 2

New and Changed Features ................................................................................................................... 2

Enhanced Reporting Hierarchies Functionality ................................................................................. 3

Masking Changes ................................................................................................................................... 3

Fix List ............................................................................................................................................................ 5

Accounts Payable .................................................................................................................................. 5

Accounts Receivable ............................................................................................................................. 5

Customer Relationship Management ................................................................................................. 5

General Ledger ....................................................................................................................................... 6

Human Resource Management .......................................................................................................... 7

Inventory ................................................................................................................................................... 7

Maintenance Management ................................................................................................................. 8

Manufacturing ....................................................................................................................................... 10

Payroll ...................................................................................................................................................... 10

Point of Sale ............................................................................................................................................ 11

Project ..................................................................................................................................................... 11

Rep Commissions .................................................................................................................................. 11

Sales Orders ............................................................................................................................................ 12

Service ..................................................................................................................................................... 12

Warehouse Management System ..................................................................................................... 13

Reports and Dashboards ...................................................................................................................... 14

New and Changed Features ................................................................................................................. 14

New Dashboards ................................................................................................................................... 14

Service .................................................................................................................................................. 14

Project .................................................................................................................................................. 14

New Reports ........................................................................................................................................... 14

Enhancements and Fixes ........................................................................................................................ 15

Reports and Dashboards Limitations .................................................................................................... 15

Reports and Dashboards ..................................................................................................................... 15

Parameter Screens and Parameters ................................................................................................. 17

Browsers................................................................................................................................................... 18

Studios and Applications ...................................................................................................................... 20


New Capabilities ................................................................................................................................... 20

Enhancements and Fixes ........................................................................................................................ 20

Studio Limitations ...................................................................................................................................... 20

Installation and Licensing ..................................................................................................................... 22

Upgrade Path ........................................................................................................................................... 22


Documentation ...................................................................................................................................... 23

Fix List .......................................................................................................................................................... 23

PRONTO-Xi Modules .............................................................................................................................. 24

Major Changes ...................................................................................................................................... 24

Table of Contents PRONTO-Xi


Page iv Commercial in Confidence

Alert Intelligence ...................................................................................................................................... 24

Dynamic Recipients Supporting Security Role as Email Address .................................................. 24

EasyEDI ....................................................................................................................................................... 24

Dynamic ABN Allocation ..................................................................................................................... 24

Point of Sale ............................................................................................................................................... 25

Refund of Serial Items in POS ............................................................................................................... 25

POS Entry Field Increased in Size ........................................................................................................ 25

RF ................................................................................................................................................................. 25

Radio Frequency (RF) Despatch By Order ....................................................................................... 25

Service ........................................................................................................................................................ 25

Issue Editing Multiple Serial Items on Service Call ............................................................................ 25

Documentation Updates ........................................................................................................................ 26

PRONTO-Xi Help Speed Operation Improvement ........................................................................... 26

PRONTO-Xi Visual Debugger Help ...................................................................................................... 26

Help Zoom Functionality Fixed ............................................................................................................ 26

PRONTO-Xi Enterprise Management System ...................................................................................... 28

Maintenance and Wizard Available for Custom Hierarchies .......................................................... 28

Keyword Rebuild Optimised ................................................................................................................... 28

Tree Menus Being Used Instead of Popup Menus .............................................................................. 28

Advanced Forecasting System ............................................................................................................ 29

Incorrect Calculation of U-Statistics in Advanced Forecasting ....................................................... 29

Forecast Record Not Removed Completely ...................................................................................... 29

Accounts Payable ................................................................................................................................. 30

Payment Commitments Report in Detail Mode Not Using Min/Max .............................................. 30

Exchange Loss/Gain on Payment of Foreign Currency Invoices .................................................... 30

Incorrect Posting of Tax for Settlement Discount ................................................................................ 30

Supplier Purchase Invoice on Contract Purchase Order .................................................................. 30

Unbalanced GL Batch for F Type Supplier Invoice ............................................................................ 31

Override Foreign Tax Amount of Invoice to Contract Purchase Order ......................................... 31

Supplier Invoice Posting Incorrect Quantity to Project ...................................................................... 31

Part Invoicing Not Splitting the Order Correctly ................................................................................. 31

Bank Transfer Currency Rate Not Based on Transaction Date ........................................................ 32

Incorrect Posting for Supplier Foreign Transaction ............................................................................. 32

Type 'X' Invoice in Foreign Currency is Not Posted ............................................................................. 32

Variance Purchase Order Has Different Tax Code than Original Purchase Order ...................... 32

Updated Tax Amount Not Shown in Invoice Detail Screen .............................................................. 32

Accounts Receivable ........................................................................................................................... 34

Account Consolidation Issue ................................................................................................................. 34

EIS Territory Variance Showing Incorrect Figures ................................................................................ 34

Overdue Customers and Interest Charging Issue .............................................................................. 34

Customer Account Code Conversion Issue ........................................................................................ 34

Customer Copy / Customer Delete ...................................................................................................... 34

Duplicate Document Number When Posting Uploaded Cash Receipts ....................................... 35

Incorrect Consolidation of Cheques in Informal Bank Slip Report .................................................. 35

Direct Debit BPay Layout Issue .............................................................................................................. 35

Wrong Partial Payment Posted for Foreign Customer ....................................................................... 35

Tax Not Posted for Multi-Project Invoicing ........................................................................................... 35

Postdated Transaction Receipts Issue .................................................................................................. 36

Front Counter Cash Receipts Issue........................................................................................................ 36



Commercial in Confidence Page v

Unallocated Cash Allocate Issue .......................................................................................................... 36

Supplier Cash Receipts on Foreign Bank ............................................................................................. 36

Incorrect Local Amount Calculation on Foreign Customer Journal ............................................... 37

Future Aged Transactions Issue .............................................................................................................. 37

Improved Handling of Disputed Invoices ............................................................................................ 37

Customer ABN and Rental Map Key Issue ........................................................................................... 37

Alert Intelligence ................................................................................................................................... 38

Dynamic Email Option Not Working for payroll-employee-details Table ...................................... 38

Email Notification Issue ............................................................................................................................ 38

Dynamic Recipients Supporting Security Role as Email Address ..................................................... 38

Application Services ............................................................................................................................. 39

Automatic Close of Cash Drawer ......................................................................................................... 39

Business Intelligence ............................................................................................................................. 40

Reporting Hierarchies - Bulk Maintenance .......................................................................................... 40

Customer Relationship Management ................................................................................................. 41

OLE Connections Not Released After Sync ......................................................................................... 41

Data Mining Issue ..................................................................................................................................... 41

Contact Drilldown for Reports Issue ...................................................................................................... 41

Opportunity Transactions Issue .............................................................................................................. 41

CRM Contact Entry Issue ......................................................................................................................... 41

CRM Outlook Sync Ignoring Date ......................................................................................................... 42

Data Intelligence ................................................................................................................................... 43

Displayed Data Different to Actual Data ............................................................................................ 43

Electronic Data Interchange (EDI) ....................................................................................................... 44

Outgoing POA Document Not Displaying UOM Correctly ............................................................... 44

Item Codes Not Mapping Automatically ............................................................................................ 44

ASN Ship to Code Field is Blank ............................................................................................................. 44

Line Date Not Passed Through to Sales Order .................................................................................... 44

FaxMail ................................................................................................................................................... 45

Default Field Values Not Working in FaxMail Transmission Screen ................................................... 45

Defaults Not Saving on FaxMail Transmission Screen ......................................................................... 45

Fixed Assets ............................................................................................................................................ 46

Incorrect Cost Posting for Serialised Fixed Asset ................................................................................. 46

General Ledger ..................................................................................................................................... 47

Data Grid Filter Not Working ................................................................................................................... 47

Incorrect Information Displayed in GL Batch ...................................................................................... 47

Expand Button Not Shown in FRW When Print Offset > 0 .................................................................. 47

General Ledger Chart of Accounts Issue ............................................................................................ 47

Cognos GL Master Chart Hierarchies ................................................................................................... 47

General Ledger Enquiry Commitments Screen Issue ........................................................................ 48

Financial Report Is Printing ^Z in Excel for Column Type Z ................................................................ 48

Customer Price Enquiry Issue .................................................................................................................. 48

Multiple BF Transactions Results in Wrong Opening Balance ........................................................... 48

Reload GL Transactions from Archive Issue ......................................................................................... 49

Tax Analysis Display Issue ........................................................................................................................ 49

GL Cash Flow Image - Starting Position Accounts ............................................................................. 49



Page vi Commercial in Confidence

Budget Import from File Still Running after Session Disconnected ................................................... 49

GL Reporting Hierarchy Template Rules............................................................................................... 50

Reporting Hierarchies Tree Menu .......................................................................................................... 50

Maintain Ledger Locks Issue ................................................................................................................... 50

Inventory ................................................................................................................................................ 51

Stock Take Count Entry Issue .................................................................................................................. 51

GL Account Code for Issue Item in Kit .................................................................................................. 51

Multi-GTIN Updating the Item Master Unit of Measure ...................................................................... 51

Reorder Report Not Accepting Screen Defaults ................................................................................ 51

Console Commitments Drilldown Issue ................................................................................................ 51

Display Issue in Inventory Console Enquiry ........................................................................................... 52

Maintain Serials Display Issue .................................................................................................................. 52

‘Can Build’ Tab Missing in Inventory Enquiry Console........................................................................ 52

Daily Warehouse Report Issue ................................................................................................................ 52

Maintain Special Pricing Display Issue .................................................................................................. 52

Item Copy Issue ........................................................................................................................................ 52

Build/Merge an Item with Bill of Materials Issue .................................................................................. 53

Correcting Configured Component .................................................................................................... 53

Inventory Console - Can Build Option .................................................................................................. 53

Stocktake Not Showing Already Counted Details ............................................................................. 53

QA Hold Item Not in QA Hold Control Screens ................................................................................... 53

Incorrect Values Shown in Issue to Work Order Screen ..................................................................... 54

Inventory Enquiry Console Issue ............................................................................................................. 54

Stock Take Difference Report - Items with Zero On Hand................................................................. 54

Inventory Console - Manufacturing/Can Build Tab ........................................................................... 54

Maintenance Management ................................................................................................................. 55

Work Order Forecasting Issue ................................................................................................................. 55

Completed Work Orders Issue ............................................................................................................... 55

Export File to MS Project in Incorrect Format ....................................................................................... 55

Forecast Work Order Creation Issue ..................................................................................................... 55

Work Request Required Date Issue ....................................................................................................... 55

Reference Monitor Point Issue................................................................................................................ 56

Default Field Values Not Retained in Work Request Entry ................................................................ 56

Convert PM Task Issue.............................................................................................................................. 56

PM Tasks Calculated Fields ..................................................................................................................... 56

Work Request Required by Date Issue ................................................................................................. 56

Actual Start Date Field Not Set in Quick Work Order Entry ............................................................... 56

Plant Item Changing to Next Item in Monitor Point ........................................................................... 57

Manufacturing ....................................................................................................................................... 58

Work Order of Backflushed Item Cannot Be Completed ................................................................. 58

Kit Recursion Issue ..................................................................................................................................... 58

Inconsistent Results in MRP ...................................................................................................................... 58

Work Order Entry - Subcontract Purchase Orders Issue .................................................................... 58

Cannot Review Serial Details in Work Order Maintenance .............................................................. 58

Changing Routing Parameters with Production Booked In.............................................................. 59

No Option to Auto View Project Card and Label Document ......................................................... 59

Missing Information in Work Order Issue Report .................................................................................. 59

Cannot Perform Production Reversal for a Lot Tracked Finished Item ........................................... 59

Error in Production Docket for Downtime ............................................................................................ 59

Cannot Enter Return Location when Returning Components ......................................................... 60



Commercial in Confidence Page vii

Maintain Work Orders Display Issue ...................................................................................................... 60

Cannot Edit Create PO Field in Work Order Entry .............................................................................. 60

Irrelevant Information Displayed in Shortage Report......................................................................... 60

Planning Policy and Days Cover in MRP Processing .......................................................................... 60

Subcontract Purchase Orders Not Appending to Open Purchase Orders ................................... 61

Unable to Commit Work Orders Created from Reorder ................................................................... 61

Unable to Use Factory when Adding to Reorder ............................................................................... 61

Work Order Not Created for Correct Component Warehouse ....................................................... 61

Incorrect Price on Purchase Orders Created from Reorder ............................................................. 61

Production Reversal - Laboratory Item Tests Issue .............................................................................. 62

Load Work Orders - Multiple Factories Issues ....................................................................................... 62

Work Order Missing Information for Multiple Bills of Materials ........................................................... 62

Work Orders Incorrectly Set to Completed ......................................................................................... 62

Manually Committed Work Order Component Using Incorrect UOM ........................................... 62

Error in Split Sales Order Link to Work Order ......................................................................................... 63

Serial Required When Entering Labour Docket ................................................................................... 63

Payroll and Human Resource Management ...................................................................................... 64

Payroll YTD/Trans Rebuild Warning Message Changed .................................................................... 64

Maintain an Employee Message Issue ................................................................................................. 64

Payroll YTD Earnings Report Incorrect ................................................................................................... 64

Payroll Number Maintenance (Masking) Issue ................................................................................... 64

Superannuation Remittance Advice Issue .......................................................................................... 64

Productivity Leisure Day Timesheet Transactions Issue ...................................................................... 64

Shift Allowance Display Issue .................................................................................................................. 65

Employee Leave Request Processing Issue ......................................................................................... 65

Incorrect Posting for Project Oncosts ................................................................................................... 65

Point of Sale............................................................................................................................................ 66

POS Entry Field Increased in Size ............................................................................................................ 66

Point of Sale Entry Kit Refund Issue ........................................................................................................ 66

Refund of Serial Items in POS .................................................................................................................. 66

Serial Item Issue ......................................................................................................................................... 66

Cannot Exit Special Order Refund Screen ........................................................................................... 66

Operator ID Not Tracked for Auditing Purposes ................................................................................. 67

POS Timeout Not Resetting Menu.......................................................................................................... 67

Max Balance for Petty Cash Can Be Exceeded ................................................................................ 67

POS Payment Issue ................................................................................................................................... 67

Record Locking Issue When Using Price Override .............................................................................. 67

Invoice Not Re-Printing With Correct Backorder Quantities ............................................................. 68

Stock Identifiers Returning Items Linked to Different Customer ....................................................... 68

Backorder Items Marked as Taken ........................................................................................................ 68

Issues Performing Account Payments Using Tyro Terminals .............................................................. 68

Cash Drawer Transaction History Issue ................................................................................................. 69

Cash Reconciliation History Not Showing All Stores ........................................................................... 69

Integrated EFTPOS Inconsistent With Account Payment .................................................................. 69

Suppress Lines = S Duplicating POS Backorders .................................................................................. 69

Project Costing ...................................................................................................................................... 70

Travel Rate Not Coming Across to Sales Order................................................................................... 70

Post Timesheets Branch Mask Issue ....................................................................................................... 70

Credit Note Creation Using Return Pick ............................................................................................... 70

Project Type Change to Grandparent Issue ....................................................................................... 70



Page viii Commercial in Confidence

Display Issue with Paid Field on Claims Screen ................................................................................... 70

Variations for Project Issue ...................................................................................................................... 71

Timesheet Details List Report Issue ......................................................................................................... 71

Enquire on Summary Mode Not Displaying Correct Order .............................................................. 71

Cost Category Conversion Issue ........................................................................................................... 71

Claim Totals Not Printing Correctly ........................................................................................................ 71

Sort Order Not Correct when Importing Master Items ....................................................................... 71

Budget Summary Screen Display Issue ................................................................................................. 72

Project Budget Details Issue ................................................................................................................... 72

Incorrect Default Value for Profit Takeup End Field ........................................................................... 72

Create Subcontracts Issue...................................................................................................................... 72

Project Maintenance Printing Issue ....................................................................................................... 73

Claims Schedule Not Printing Totals for Large Schedules ................................................................. 73

Task Resource Report Issue ..................................................................................................................... 73

Unbalanced GL Batch for Sales Order Linked to Project .................................................................. 73

Timesheet Details Report Issue ............................................................................................................... 73

Unable to Remove Details from Cost Categories in Forecast.......................................................... 74

Incorrect Display of Cash Receipts in Cash Position Report ............................................................. 74

Totals Incorrect on Claim Print with Variation Included .................................................................... 74

Performance Issues with Delete Complete/Lost Projects Function ................................................. 74

Forecast Update Process Can Remove Budget Details ................................................................... 74

Overall Executive Report Issue ............................................................................................................... 75

Line Number Sequence Issue with Subcontract/Supplier Agreement ........................................... 75

Able to Print Unapproved Agreements ................................................................................................ 75

Timesheet Negative Entry Issue .............................................................................................................. 75

Claim Schedule Report Issue .................................................................................................................. 75

Project at Status ‘C’ (Created) Cannot be Removed or Edited ..................................................... 76

Create Project Quotation Issue ............................................................................................................. 76

Purchase Orders .................................................................................................................................... 77

Shipment Create Issue ............................................................................................................................. 77

Purchase Order Not Updating Header Correctly ............................................................................... 77

Item Code Conversion Error ................................................................................................................... 77

Purchase Order Return Allows Lot Quantity to Go Negative ........................................................... 77

Goods Receipting Subcontract PO - Additional Requirement ....................................................... 77

Order Total Not Updating ....................................................................................................................... 78

Incorrect Use by Date for Purchased Tracked Item........................................................................... 78

Big Item Price Incorrectly Multiplied by 100 ......................................................................................... 78

Purchase Order Officer Limit Issue on Backorder Maintenance ..................................................... 78

Purchase Order Update Issue ................................................................................................................ 78

Multiple GL Description Not Defaulting ................................................................................................ 79

Warehouse Masking Not Functioning Correctly ................................................................................. 79

Contract Order Report Truncation Issue .............................................................................................. 79

Purchase Order Cancellation Issue ...................................................................................................... 79

Subcontractor Order Maintenance Agreement Types..................................................................... 79

Incorrect Value Outputted by Field Code ‘CC’ in Totals Section ................................................... 79

Print Multiple Purchase Orders Fails ....................................................................................................... 80

Contracts Order Report .......................................................................................................................... 80

Can Print Unapproved Subcontract Agreement ............................................................................... 80

Able to Print Unapproved Subcontract Agreements ........................................................................ 80

UOM Not Set Correctly for Random Weight Item .............................................................................. 80

Conversion Factor Set to Zero on Return Purchase Order ................................................................ 81



Commercial in Confidence Page ix

Outside Work - Out Source WMS Assembly Orders ............................................................................ 81

System Error During Purchase Order Receiving Using RF ................................................................... 81

Recost Of Shipment Posts Purchase Cost to IR and IV Accounts .................................................... 81

Quality Management System .............................................................................................................. 82

Invoice Dispute Entry Issue ...................................................................................................................... 82

Actual Hours Incorrectly Populated ...................................................................................................... 82

Rental/Contract ..................................................................................................................................... 83

Changing the Contract End Date with Options ................................................................................. 83

Rental Contract Integrity Issue ............................................................................................................... 83

Repairs Management ........................................................................................................................... 84

Repair Dockets Not Printing Repair Notes Correctly .......................................................................... 84

Sales Orders ........................................................................................................................................... 85

B Type Credit Note Not Using Original Price ........................................................................................ 85

Kit with Special Items Issue ...................................................................................................................... 85

Sales Order Charge Type Not Validated When ‘Charges Split By’ = Blank ................................... 85

RF Overship Without Reallocation Issue ............................................................................................... 85

ScanPack Despatch Enhancement ..................................................................................................... 85

Returned Lot Cannot Be Released to Sales Order ............................................................................. 86

Sales to PO Gross Profit UOM/Currency Issue ...................................................................................... 86

Credit Note for Manual Invoice ............................................................................................................. 86

Cannot Amend Delivery Address for Sales Order Quotation .......................................................... 86

Internal Item Issue Postings Not Showing Subledger .......................................................................... 86

Sales Representative Split Issue .............................................................................................................. 87

Cannot Reuse Serial Numbers in WMS RF Picking .............................................................................. 87

Full Order Entry Issue ................................................................................................................................. 87

Sales Order Update Issue ........................................................................................................................ 87

Sales Order Posting Period Not Showing Date Value ........................................................................ 87

Sales Order Delivery Address Update Issue ......................................................................................... 88

Cost Not Displayed When Item Code is Entered................................................................................ 88

Tax Rate Being Calculated Incorrectly ................................................................................................ 88

Batched SO Update - Transfer Orders Issue ......................................................................................... 88

Work Order Link Screen Display Issue .................................................................................................... 89

‘N’ Type Sales Order Line Not Displaying Item Code in Screen Title ............................................... 89

CRM Record Not Creating From Sales Order Entry ............................................................................ 89

Updating Purchased Tracked Item Issue ............................................................................................. 89

Sales Order Line Delete Not in Sequential Order................................................................................ 89

Reprint Sales Orders Issue ........................................................................................................................ 90

Sales Order Edit ABN Printing .................................................................................................................. 90

Own Box Option Issue .............................................................................................................................. 90

Sales Order to Service Call Linkage Issue............................................................................................. 90

Sales Order Update - Serial Details ........................................................................................................ 90

Order Status Report Corrupting Selection Dates in Batch Mode .................................................... 91

Available Credit During Order Entry Issue ............................................................................................ 91

Sales Order Load from Flat File Issue ..................................................................................................... 91

Full Order Entry Issues ............................................................................................................................... 91

Tax Figures Not Correct in Sales Order Enquiry ................................................................................... 91

Transfers Not Appearing in Non-WMS Screen ..................................................................................... 92

Consignment Note Number Field Size Increased ............................................................................... 92

WMS RF Despatch - Warehouse Transaction ...................................................................................... 92



Page x Commercial in Confidence

Sales Order Edit of GL Coded Sales Orders ......................................................................................... 92

Catalogue Sales Updated to Wrong Period ....................................................................................... 93

Sales Order Conclusion - Customer Required Date ........................................................................... 93

Enter Manual Invoices Issue .................................................................................................................... 93

Sales Order Edit Now Restricts GL Coding Sales Orders .................................................................... 93

Credit and Recharge Lines with Zero Amounts .................................................................................. 94

Project Codes Not Allowed in Invoice Entry ........................................................................................ 94

Manual Invoices Not Calculating Tax on Charges ............................................................................ 94

Project Orders on Backorder Losing Their Quantities ......................................................................... 94

GL Batch Not Balanced When Tax at Order Level ............................................................................ 94

Unable to Despatch Orders ................................................................................................................... 95

Sales Order Invoice Reprinting ............................................................................................................... 95

Charge Line Can Be Entered in Multi-Project Invoicing .................................................................... 95

Full Invoice Entry - GL Coding Sales Orders ......................................................................................... 95

Invoice Exclusion Not Working in Daily Sales Report .......................................................................... 95

Descriptions Truncated in Sales History Report .................................................................................... 95

Order Status Report Issue ........................................................................................................................ 96

Kit Item Price Incorrect After Quantity Change ................................................................................. 96

Missing Columns in Sales Order Archived Enquiry .............................................................................. 96

Archived Order Enquiry Date Filter Issue .............................................................................................. 96

Changes Not Saved When Exiting Delivery Address Screen ............................................................ 96

Less Than Min GP Message Incorrect for Labour Items ..................................................................... 97

Posting Issue with General Terms Rebates in Sales Order Update .................................................. 97

Service .................................................................................................................................................... 98

‘In-Stock’ Serials Not Prompting for Customer .................................................................................... 98

Page Number Truncated in Sales History Report ................................................................................ 98

Contract Maintenance Pricing Issue .................................................................................................... 98

Issue Editing Multiple Serial Items on Service Call ............................................................................... 98

Service Call Fault Lines Issue ................................................................................................................... 98

Service Call Parts Not Charged on Invoice ......................................................................................... 99

Sales Order for PM Calls Issue ................................................................................................................. 99

Cannot Print Quotation for an Arrear Billing Contract ...................................................................... 99

Miscellaneous Minor Enhancements to Service Module .................................................................. 99

Service Call Received Date / Time ..................................................................................................... 100

Duplicate Sequence Numbers on Units ............................................................................................. 100

Field Named Incorrectly in Selective Call Screens ........................................................................... 100

Service Lost Contracts Report Issue .................................................................................................... 100

Workshop Repair Enquiry Unknown Message ................................................................................... 100

Service Call Cancellation Issue ............................................................................................................ 100

Can Print General Notes in Call Maintenance Entry ....................................................................... 101

Full Credit Contract Invoice Has No Amount .................................................................................... 101

Incorrect Note Type for Schedule Notes ............................................................................................ 101

Call Info Mode Causing I/O Error in Allocation Screen ................................................................... 101

Missing Fields in Lost Contract Report ................................................................................................. 101

Territory Not Displayed in Service-Engineers for Service Territory Screen ..................................... 101

PDA Showing Incorrect Required Date .............................................................................................. 102

No Replenishment Warehouse Range With F2 (Lookup) ................................................................ 102

Incorrect Default Telephone Number in Call Logging .................................................................... 102

Log Calls Issue ......................................................................................................................................... 102

Contract Keywords Not Updated Automatically ............................................................................. 102

Task Intelligence .................................................................................................................................. 103



Commercial in Confidence Page xi

Tasks Not Running in Correct Environment ........................................................................................ 103

TrueForm ............................................................................................................................................... 104

TrueForm Print Preview - Default Reader Adobe Acrobat .............................................................. 104

TrueForm Documents Not Previewing Correct Project .................................................................... 104

Address Conversion Entries Issue ......................................................................................................... 104

Warehouse Management System ..................................................................................................... 105

Warehouse Audit Report Issue ............................................................................................................. 105

References Truncated in RF Inventory ................................................................................................ 105

Putaway Record Not Cleared for QA Lot-Tracked Item ................................................................. 105

Cannot Putaway QA Item in Type 2 or 3 Warehouse Using RF ...................................................... 105

Service Level Report Not Showing Correct Quantities .................................................................... 105

System Administration ......................................................................................................................... 106

Maintain GL Masking Issue .................................................................................................................... 106

Standard Message Code Issue ............................................................................................................ 106

Reporting Capabilities - Bulk Users Additions..................................................................................... 106

Reporting Capability - Group Temporary Licencing ....................................................................... 106

Masking Based Session Parameters for Cognos ............................................................................... 106

Upgrade Issue- Cognos Synonyms Not In Shared GL Area ............................................................ 107

Upgrade View Creation ........................................................................................................................ 107

Additional System Upgrade Function Added ................................................................................... 107

Component Libraries ........................................................................................................................... 108

Public Exportable Procedure for Calculating Available Stock ...................................................... 108

Public Exportable Procedure for Controlling Company List ........................................................... 108

Public Exportable Procedure for Inventory Price Recalculation ................................................... 108

Public Exportable Procedure for Overriding Label Print Quantity ................................................. 108

Public Exportable Procedure for Purchase Order Update ............................................................. 109

Public Exportable Procedures for Quality Management System .................................................. 109

Public Exportable Procedure for Custom Call Allocation ............................................................... 109

Public Exportable Procedure for Foreign Currency Date ............................................................... 109

Public Exportable Procedure for Invoice Variance Screen ............................................................ 109

Public Exportable Procedure for WMS ScanPack ............................................................................ 110

Public Exportable Procedure for Employee Conversion Program ................................................ 110

Public Exportable Procedure for Repair Orders ................................................................................ 110

Public Exportable Procedure for Project Timesheet Posting........................................................... 110

Public Exportable Procedure for Sales Order Conclusion ............................................................... 110

Public Exportable Procedure for Scale Factor .................................................................................. 111

Public Exportable Procedure for Overdue Customers/Charge Interest ...................................... 111

Public Exportable Procedures for Preventative Maintenance Scheduling ................................. 111

Public Exportable Procedures for PM Run Report ............................................................................ 111

Public Exportable Procedure for GL Consolidation ......................................................................... 112

Additional Calling Parameters for Cash Receipt - Load Data into System ................................. 112

Additional Calling Methods for Customer Maintenance Licence Screen .................................. 112

User-Definable Fields Added to Despatch/Delivered Edit/Confirm ............................................. 112

PRONTO-Xi Introduction


Commercial in Confidence Page 1

Introduction

The purpose of these release notes is to provide details of all changes included in this service pack release that relate to the PRONTO-Xi product.

The first part of this document includes all the significant updates and changes made to the PRONTO-Xi Business Intelligence module since its initial release (p.2).

The second part of this document describes the changes to the remaining PRONTO-Xi modules.

Before upgrading to this release, ensure that all information is read and acted upon if necessary.

Caution: It is possible that late changes made to PRONTO-Xi Business Intelligence before the service pack release are not included in this document.

Business Intelligence PRONTO-Xi


Page 2 Commercial in Confidence

Business Intelligence

The purpose of these release notes is to provide details of all software changes included in this service pack for PRONTO-Xi Business Intelligence.

Service Pack 2 Highlights

New user-definable dashboards for Service and Project New PRONTO-Xi Analytics Dimensions – Inventory New reporting data packages for Accounts Receivable New core reports for Manufacturing New fields added across many reporting data packages and Analytics Dimensions New hierarchies and enhanced hierarchy functionality

Framework

The PRONTO-Xi Business Intelligence framework includes the packages, schemas, fields, joins, and layout elements. This section includes information about:

New and changed features (p.2), including the new package and schema releases Framework fixes (p.5)

New and Changed Features

New Analytics Dimension

PRONTO-Xi Analytics Dimensions – Inventory extends the capabilities already available with the Inventory reporting data package by allowing users the ability to perform dimensional reporting, such as drill up and down, on their pre-defined hierarchies.

This package includes many similar reporting fields to its corresponding reporting data package, such as:

Item Transactions - Stock Movements of all types Warehouse - Warehouse balances Warehouse History - Warehouse End of Period Balances Stocktake - Stocktake Variance/Counts Reorder - Reorder requirements (to purchase) Replenish - Replenish requirements (between warehouses) Item FIFO - FIFO details for ageing of stock items.

New PRONTO-Xi Reporting Data Package

PRONTO-Xi Dimensions Service Pack 2 offers the new Rep Commissions reporting data package. The package provides users with access to simplified reporting data for quick report authoring and querying using BI Manager or BI Designer products. It allows different styles of reports to be produced, to suit every user’s needs within areas such as: - daily productivity, tracking, costing and forecasting.

NEW PACKAGE

SDR Package

57757 Rep Commissions

PRONTO-Xi Business Intelligence



Enhanced Reporting Hierarchies Functionality

The reporting hierarchies now include additional functions to help you build and maintain your hierarchies and their level data. These include:

The new Hierarchy Builder (EMS M010) (SDR 57679) that allows you to see and more easily manage the following hierarchies:

o Item

o Customer

o Supplier

o Project

o Fixed Asset

o Plant Item

o Employee

o Service Contract

o Rental Contract

The Detail Entry mode (SDR 57679) on the Hierarchy Builder screen also allows you to quickly create a new hierarchy in a single, simple PRONTO-Xi screen.

A Bulk Update mode (SDR 57995) is available from each Hierarchy Maintenance screen that allows you to selectively filter the records in each hierarchy, mark records to edit, then edit and update the level details for these marked records.

A Set and Update mode (SDR 57995) is available from each Crosscheck Hierarchy screen that allows you to enter level details for multiple marked records.

The Master Chart mode (SDR 58030) in the GL Hierarchy Template (GL M041) function allows hierarchy template rules to be defined for one or more hierarchy sets. These rules can be defined on the GL Reporting Hierarchy Template based on the Account Type.

For more information about these new hierarchy functions, and how to use them, see the PRONTO-Xi Business Intelligence Help.

Masking Changes

SDR Description

57949 Cognos Masking Control A new control has been added to the PRONTO-Xi Reporting Server Administration folder that allows the masking used in BI to differ from what is applied by PRONTO-Xi backend functions. This has two primary benefits: It can be used as a method to simplify the SQL code that Cognos generates and

passes to the database as a query. This can improve response times significantly, depending on the query.

It can be used to make the masking differ. In many cases the masking in the backend has been applied for operational functions rather than reporting, i.e. prevent a user posting to a Project Branch they do not have access to but you do not care whether they can report across all branches.

Some users will also have full access masking defined in the backend, i.e. ???? Territory Masking. This now translates to Do not apply Territory Masking as the user has full access anyway. The individual controls will be maintained using PRONTO-Xi functions so as masking rules are changed they will be reflected in the Session Parameters for that user, unless the specific session parameters have the Override Flag set, which will prevent any auto-update of the session parameter value.

57859 Masking Session Parameters (4GL)




Masking based Session Parameters for Cognos have so far used masking by default. This results in complex SQL statements being generated by the Cognos server. This SDR and corresponding changes in Cognos model (SDR 57949) makes the use of masking optional for customers who do not use masking. Module/Function: SYS M167

57952 Masking of Facts only in Cognos packages The initial releases of the Cognos packages included masking on both the Fact and Attribute type query subjects. This has now been changed to only apply masking to the Fact query subjects. This has several benefits, including: Less complex SQL being generated, even when facts are reported meaning that

queries will be processed quicker. Much less SQL generated if only attributes are reported meaning that queries

are processed faster. Queries that include attributes of sub-ledger or associated data will include

data that would not be included if masking of the sub-ledger item or associated data excluded it based on non-existence, e.g. GL Transactions that don't have an associated project would not be reported under the old method if the transaction was not related to a project.

The various masking controls in PRONTO-Xi are primarily used to control operational access to hide specific facts. It is rarely used to completely hide records (except for GL, which is not affected by this change). Therefore, this change aligns more closely to the PRONTO-Xi masking result.

57926 Cognos Warehouse Masking Release 700.0 and Service Pack 700.1 defined that warehouse masking logic effectively excluded masking for Special and Labour type stock items which do not have Item Warehouse detail records. This was to enable special or labour items to be listed in a warehouse details report. This need was invalid and this masking is now changed so that only items with warehouse details can be reported with warehouse details.




Fix List

The following fixes have been applied to packages since the previous release.

Accounts Payable ........................................................................................................................................ 5 Accounts Receivable .................................................................................................................................. 5 Customer Relationship Management ................................................................................................. 5 General Ledger ............................................................................................................................................. 6 Human Resource Management ............................................................................................................. 7 Inventory ........................................................................................................................................................ 7 Maintenance Management ...................................................................................................................... 8 Manufacturing ............................................................................................................................................ 10 Payroll ............................................................................................................................................................ 10 Point of Sale ................................................................................................................................................. 11 Project ............................................................................................................................................................ 11 Rep Commissions ...................................................................................................................................... 11 Sales Orders ................................................................................................................................................. 12 Service ............................................................................................................................................................ 12 Warehouse Management System ....................................................................................................... 13

Accounts Payable

SDR Package Description Impact

57777 Accounts Payable

The Supplier Commitments namespace had an error whereby the Supplier Commitments Details was sourcing cre-trans details and the Supplier Commitments Facts referenced cre-trans-all.

Errors corrected.

Accounts Receivable


57756 Accounts Receivable

Added Customer Promotions and Customer Promotions transaction namespaces

New namespace

58004 Accounts Receivable

Added new fields to Customer Ageing fact: Outstanding Orders Balance Disputed Invoices Balance

New fields

Customer Relationship Management


57739 Customer Relationship Management

Report changed to have proper grouping. Corrected a bug in the transaction count and added Trans. No. to show all transactions.

The CRM- Campaign Transaction Statistics report can now be ungrouped in Business Insight.

55389 Customer Relationship Management

CRM Reporting System Structure Changes, including various status and type descriptor tables and a defined CRM account hierarchy object. These tables are loaded upon upgrade and are used primarily by the Cognos reporting system.

Various new objects created to store data that was previously only ever derived using program logic.




General Ledger


57634 General Ledger - Master Chart

Added 11 more GL hierarchies for other GL Master Chart elements. The initial release only allowed for natural account selection of the GL Chart of Account to be used in the GL Reporting Hierarchies. This is now extended to allow hierarchies to be built on any other elements of the GL Chart: Company Business Unit Corporate Break Region Section Department Cost Centre Sub-Section State Territory

Each menu option in the GL X056 menu will prompt for the GL Chart element to be used. This list is based on the currently used elements in the dataset. For example, if the dataset used Company, Department, and Business Unit, only these options are displayed in the menu.

Added hierarchies

58030 General Ledger - Master Chart

Added mode to GL Chart of Account Maintenance screen (GL M008) for A chart accounts. The Hierarchy Template Rule code can now be defined (for one or more hierarchy sets). This rule code can be defined on the GL Reporting Hierarchy Template based on the Account Type.

Added mode

57866 General Ledger

Added relative facts to both GL and Sales to allow for period-based reporting of facts based on a year or period that is prompted or selected during report creation or run.

Added facts


Added the following generic tables that are needed to run in the PRONTO_GL or PRONTO_PAY environments: PRONTO_GL system-table system-control system-user-control system-control-time-dimension asset-register gl-chart-of-accounts job-cost-master

PRONTO_PAY system-table system-control system-user-control system-control-time-dimension system-user-masking-access

Added tables


Cognos - GL Package Renaming of Folder and DMR Hierarchy Within the GL Package, there exists both flat relational namespaces such as Master Chart and GL Transactions, as well as the DMR based namespace. The DMR namespaces were named Reporting Hierarchies but are now named General Ledger (Analytics) to make it more obvious that this is actually a DMR and contains drillable standard hierarchies.

Renamed folder and DMR




Within the Master Chart dimension, the first standard hierarchy was named GL Account Code but is now named GL Account. The Code in the original name indicated that the result would be a code rather than the account description which is what is actually derived by this hierarchy.

Human Resource Management


57821 Human Resource Management

Added training and accident details to allow reporting and analysis. There are now two types of employee facts - Employee Detail and Employee Master. Employee Master, when added to a report displays terminated employees. Employee Detail only displays active employees.

New fields added.

Inventory


57895 Inventory Analytics Dimension

New package added. This package is separately licensed and, to access it, users must be granted access to Capability 519. The new package contains similar namespaces as the flat Inventory schema, that is: Item Transactions - Stock Movements of all types Warehouse - Warehouse balances Warehouse History - Warehouse End of Period Balances Stocktake - Stocktake Variance/Counts Reorder - Reorder requirements (to purchase) Replenish - Replenish requirements (between

warehouses Item FIFO - FIFO details for ageing of stock items

These namespace provide similar details to the matching namespace in the flat schema packages but with the benefit of having pre-defined hierarchies that can be used for drilldown and member selection.

New Analytics package.

57766 Inventory Added the primary fields of the Chemical Specifications to the Item query subject that appears in several packages and namespaces.

New item query subject.

57953 Inventory Added Item/Warehouse FIFO details of current stock holding. Details include Lots and other receipt details and provides a basis for ageing reporting and analysis.


57956 Inventory Added a new namespace, Warehouse History, that contains details of the QOH, Cost, and Value that is optionally recorded at the point of EOP or EOY roll. These can be used to see trends in the stock holding details.





Maintenance Management


55457 Maintenance Management

Maintenance Management Data Reporting Changes It was found that various data elements were not stored as reportable data and therefore, Cognos would not be able to see this data for queries, reports or BI analysis. These fell into three broad types: Data stored in #defines for various status, types and

other rules Data constructed by complex calculations for online

enquiries and reports Data stored badly in note text, etc.

DESCRIPTOR TABLES Various descriptor tables were added for types, status etc. Currently there is no access to these new tables (apart from browse) but they can be seen and used in Cognos queries, reports and parameter pages. CALCULATIONS The primary calculation that typically needed to be exposed for reporting is based on PM Task and Component forecasting, i.e when is this PM Task or Component Change next due based for reporting is based on PM Task and Component forecasting, or when is this PM Task or Component Change next due based on the PM Task frequency, UOM, Monitor Point or Calendar calculation. These calculations are not simply linear expressions that could be performed by Cognos and therefore, we needed to store the results so that the result can be reported without the need for any calculation. Three primary changes were made to store these results: PM TASK CALCULATIONS A new table, plant-master-pm-task-calc, has been added. This table is updated using dictionary triggers on the PM Task, PM Task Plant Item and Monitor Point tables. Any changes to these tables will call tlib/tlibplant to recalculate the Next Due, Earliest and Latest dates based on the new information from the trigger. PM TASK RUNS One of the primary reports required in Cognos will be the ability to report on Forecast PM Tasks for tasks that will occur (based on current trends and values) in the future. The current 4GL report performs this in a hard-copy report which cannot be consumed in Cognos. A new function, PM Task Runs, has been added. During PM Task Forecast generation, a Run Code is prompted for. This can be either left blank or a new or existing PM Task Run code can be entered. Regardless of whether a Run Code is defined, the forecast run will store its results for the Run in a new set of tables which can then be reported on in Cognos. If the Run code is left blank, the blank Run code details will be deleted and recreated. If a Run code is defined,

Improved performance of existing reports and queries.




the associated Run code details will be deleted and recreated. Run codes can be made private, meaning that only the Run code is linked to the current login-id and cannot be overridden or recreated by any other user. Run codes can also be locked to prevent re-creation and their details will be held as they are. The combination of the Private and Locked functions provides a method of storing PM Task Forecast results for future comparison with other runs or other details. e.g. Jan 2011 to Dec 2011 Budget Run master details can be created from the Forecast PM Work Orders creation screen. A Run consists of a header code, description, private flag and status A run can have associated details, ie, details of the PM Tasks that would be triggered from the PM Forecast process as well as the details of any existing or generated work orders that are considered by the forecast process. Run Details can be accessed from Plant Item / Enquiries mode / Forecast PM Task Runs PM Task / Plant Items / Runs mode Work Orders / Forecast PM Task Work Orders / Review mode. DATA STORAGE Several elements of data were stored poorly and would have made reporting in Cognos problematic. PLANT ITEM/ASSET DETAILS Many of the fields on the main Plant Item screen were shared with the Fixed Asset (asset-register and others) tables if the Plant Item was related to a Fixed Asset. This caused reporting and also other operational issues. If the Plant Item was not related to a Fixed Asset the various fields were stored in a series of note lines (plant-master-detail). The changes made now mean that these fields are dedicated fields on the plant-master table itself. Field Old field New Field Location - If plt-asset-no > spaces then asset-register.asset-current-location-desc, else plant-master-detail.plt-detail-text type XX, seq 1 plt-location Serial No. If plt-asset-no > spaces then asset-register.asset-ident-no, else plant-master-detail.plt-detail-text type XX, seq 2 plt-serial-no Model - plt-model Supplier - plt-supplier Manufacturer - plt-manufacturer Location Code - plt-location-code Sub Location - plt-sub-location Install Date plt-install-date Warranty Date plt-warranty-date PO Order No. plt-po-order-no Capital Cost plt-capital-cost Track Component plt-track-component Expected Life plt-expected-life Warranty Life plt-warranty-life




MONITOR POINT DETAILS Several fields were held in inappropriate fields that were in some cases shared fields dependent upon the monitor point input type. Field Old field New Field Reference Plant Item plt-monitor-location plt-monitor-reference-plant Update from W/O plt-monitor-supplier plt-monitor-update-flag Max Per Day plt-monitor-labour-est-hours plt-monitor-max-per-day PM TASK Several fields were held in inappropriate fields that were in array storage which could not be used easily by Cognos. Field Old field New Field Included Task 1 plt-pm-includes-task[1] plt-pm-included-task1 Included Task 2 plt-pm-includes-task[2] plt-pm-included-task2 Included Task 3 plt-pm-includes-task[3] plt-pm-included-task3 Included Task 4 plt-pm-includes-task[4] plt-pm-included-task4 PM TASK COMPONENT CHANGEOUTS These changeout instructions were held in PM Task notes (plant-pm-details) and have been moved into a new dedicated object.

57904 Maintenance Management

PM Tasks Calculated fields The upgrade of PM Tasks to the Dimensions release will now populate the table used by Cognos for PM Task Next Due Date reporting.

Manufacturing


57888 Manufacturing Added two manufacturing reports: Manufacturing - MRP Exceptions Manufacturing - Work Order Status

Added reports.

57887 Manufacturing Added Project Master query subject to the Work Order namespace.

This allows reporting of project-related information when linked to a job.

Payroll


57111 Payroll Payroll - Earnings List by Category Code This report was not reporting the Standard Tax column correctly. The individual detail rows were correct, but the subtotals by employee

Added reports.




and category were not and in some cases repeated the same values. A change has been made to the underlying Payroll model to ensure these values now report correctly.

Point of Sale


57776 Point of Sale

Added POS promotional coupons to POS schema. Added name Space for Promotional Coupons. Promotional Coupon Facts Promotional Coupon Promotional Coupon Redeemed

Sales Order Header (sales order that the coupon was used on) Time (Linked to Sales Order Date) POS.M020

Added namespace and fields.

Project


57954 Project Expanded the Project schema to include project variations in a new namespace. This new namespace includes multiple dimension hierarchies based on the projects variations as well as other related hierarchies such as Project, Time, and several other Reporting hierarchies.

New namespace.

547955 Project Cognos Project DMR Issue Register Details Project Issue Register details have been added as a new namespace in the Project DMR. This namespace includes details of the Project Issue Register, that is typically used to record and process non-financial actions for a project, such as progress enquiries, Requests for Quotations, Requests for Variations, and so on.

New namespace.

Rep Commissions


57757 Rep Commission

Added Rep Commissions package. This package contains one namespace with several query items: Rep Master Rep Commission Payable Customer Sales Order (linked to Payable Transactions) Time (linked to Payable Invoice Date)

New hierarchies: Customer Customer Rep Item Product Group Territory Rep Warehouse

New package




Sales Orders


57720 Sales Orders

Added field codes to report on the Service Call associated with the Sales order.

so-add-to-mail-flag exposed.

57773 Sales Orders

Altered header masking from an item/line based warehouse masking to masking at the item/line level.

Some details from the Sales Order Header namespace within the Sales Order package were incorrect due to masking that referred to item codes at the line level.

57767 Sales Orders

Added Project query subject folder within both the Sales Order and Sales Order Header namespaces.

New project query subjects.

57659 Sales Orders

Added other reason codes, CR, HR, VR, and SL. These fields are available in both the Sales Order and Sales Order Header namespaces and include code, code description, and code and description combination. Shortship Reason (SL) has been added to the Sales Order namespace within the Sales Order package. As this only applies to Sales Order Lines, it does not exist in the Sales Order Header namespace.

New fields.

57655 Sales Orders

Added Stock Budgets at Item and Warehouse level within new namespace named Item Sales by Whse (Budgeted).

Sales Qty and Value were not displayed. New namespace.

57692 Sales Orders

Added Sales Order and Sales Order Line details that are associated with Item transactions. New fields include Carrier, Order Source, Order Type, and Line Type, plus facts Discounts, and Ordered Amounts.

New fields.

57866 Sales Orders

Added series of relative facts to both GL and Sales to allow for period-based reporting of facts based on a year or period that is prompted or and selected during report creation or run.

Added facts.

Service


57657 Service Added Service Call Sales Order Dates. Exposed the Sales Order Date and Invoice Date of the Sales Order bound to the Service Call. Within the Service Calls and Service Current Calls namespaces in the Service package, there is now a folder called Sales Order that contains these two dates. These dates are also exposed in the Service Call Facts and Service Current Call Facts in the Days folder as a measure of the days between call completion and the two order dates.

New fields.

58078 Service Service Engineers with multiple Service Centres. Reporting engineer transactions were duplicated when

Corrected error




the same engineer code was used across multiple service centres.

Warehouse Management System


57765 Warehouse Management System

Added new namespace to the Warehouse package to allow reporting on Warehouse locations and the items that are currently in those locations.

New namespace.

57926 Warehouse Management System

Release 700.0 and Service Pack 700.1 defined that warehouse masking logic effectively excluded masking for Special and Labour type stock items without Item Warehouse detail records. This was done to allow special or labour items to be listed in a warehouse details report. This need was found to be invalid and so this masking has now been changed so that only items with warehouse details can be reported with whse details.

New namespace.




Reports and Dashboards

The list of Business Intelligence Reports, and the Business Dashboards and Analytics Dashboards dashboard products, is continually growing and evolving. Each addition and change is documented in the following areas:

New and changed features (p.14), including added reports and dashboards A list of all fixes (p.15) for reports and dashboards since the last release A list of limitations (p.15), including available workarounds


New Dashboards

PRONTO-Xi Business Intelligence Dashboard - Service PRONTO-Xi Business Intelligence Dashboard - Project PRONTO-Xi Business Intelligence Analytics Dashboard - Service PRONTO-Xi Business Intelligence Analytics Dashboard - Project

Service

Service Centre managers require an at-a-glance understanding of how their service metrics are performing to ensure optimal productivity and service engineer utilisation. The PRONTO-Xi Business Dashboards help Service Centre managers optimise their operation’s effectiveness.

For the new Service Business Dashboard, key performance metrics available include:

Contracts due for renewal in the next 30 days Unallocated calls for the day Unallocated calls for the day % Outstanding calls Current call counts by active status Overdue unallocated calls by call service centres

Project

For the new Project Business Dashboard, key performance metrics available include:

Project profit, income and costs per year Unpaid claims Claims to be submitted Claims to be certified In progress cost to complete by branch In progress project count, total contract amount by project type

New Reports

Manufacturing – MRP Exceptions (SDR 57888)

This report assists in the MRP planning process as it allows operators to identify exceptions and therefore, facilitate any necessary rectification.

Manufacturing – Work Order Status (SDR 57888)

This report provides detailed visibility of current work orders and their statuses through the full cycle from the Entered to Finished status. It provides an overview of all current activities and workloads.




Enhancements and Fixes

SDR Report Description Impact

57713 Accounts Payable - Aged Trial Balance By Supplier

Balance Selection prompt corrected. Sort order fixed.

Incorrect filtering and sequencing.

57713 Accounts Payable - Aged Trial Balance by Supplier Type

Balance Selection prompt corrected. Incorrect filtering and sequencing.

57713 Accounts Receivable - Aged Trial Balance by Customer


57713 Accounts Payable - Aged Trial Balance by Customer Territory


57769 Accounts Payable and Accounts Receivable - Aged Trial Balance by supplier and Aged Trial Balance by supplier type

Accounts Receivable and Accounts Payable Report issues Aged Trial Balance by supplier -

fixed missing total on the future column.

Aged Trial Balance by supplier type - fixed missing total on the future column and not sorted on supplier code.

Foreign currency Exposure - corrected summary values.

Totals added and errors corrected.

57969 Purchase Orders - Order Detail Status filter changed to look at the status code rather than the status description.

Corrected status filter.

Reports and Dashboards Limitations

The following limitations relate to the PRONTO-Xi Business Intelligence reports and dashboards.

Reports and Dashboards (p.15) Parameter screens and parameters (p.17) Browser issues (p.18)

Reports and Dashboards

The following limitations relate to the running, display, and general functionality of the PRONTO-Xi Business Intelligence reports and dashboards.

Limitation Workarounds and Notes

Any report saved in a public folder can be visible to users with corresponding roles in other company datasets.

You should carefully consider where you save your confidential or restricted reports to ensure that users logged into other datasets cannot inappropriately see the report and its data.

Reports in HTML format do not display the last page number if you navigate directly to the last page.

If you navigate through the pages one-by-one all page numbers are displayed. This is a regular feature of IBM Cognos as the reports are rendered on a page-by-page basis for optimised performance. If it is important that all pages are displayed, or you must know the number of returned pages, then export




to another format, such as PDF, which pulls all the data into the report.

Note: The time required to process a report in PDF format is longer than for HTML format.

Hyperlink columns are always displayed in the CSV output, even if rendering is set to No.

No workaround.

The modification date of the parent report is updated when saving a report to My Folders or emailing it.

No workaround.

When running PRONTO-Xi Business Intelligence in then backpane, when launching a studio, a new blank browser window opens and must be closed manually.

For some PRONTO-Xi Business Intelligence studios, it is preferable to log in using a browser.

In first generation of Analytics Dashboards, expanding a menu, then minimising it and expanding it again displays a More option. This option does not do anything.

This issue will be fixed after the dashboard redesign in Business Insight.

Script error when running reports with XHTML or HTML Fragment outputs in Advanced Options.

XHTML or HTML Fragment advanced options are not intended as browser report viewing options. For more information, see the Report Formats topic in the Cognos Connection User Guide.

A script error occurs if you click Bottom on a report and right-click Lineage.

Use the Page up and Page down options instead.

When viewing reports in Excel 2007, an extra cell can be added to the right which means a value is not aligned underneath its correct heading.

You can manually correct the formatting if needed.

Clicking the Bottom hyperlink in a HTML report and then clicking Page Up can cause gaps to appear at the bottom of each page.

This does not occur if you use the Page Down hyperlink to navigate to the bottom of the report.

Hyperlinks are displayed in Excel reports but do not work as expected.

Hyperlinks are not supported in Excel. If hyperlinks are required, use PDF or HTML outputs for the report.

When saving a report in PDF format the default file name is not the same report name as when saving to other formats.

No workaround.

When running a large report, the Select a Delivery Method screen is sometimes displayed, but then disappears.

This screen disappears once the report is loaded, and does not display at all, or displays only briefly, when loading a smaller report that loads quickly. The delivery method options are available in the report viewer screen.

The General, Back, Search, and Finish buttons are displayed in the middle of the parameter screen instead of at the bottom.

This can occur when running a report with advanced options.

Emailing a report as an Excel 2002 file saves the report in .MHT format instead of .XLS.

This is because each report page is rendered to its own Excel 2002 worksheet, in a single Excel 2002 workbook. MHT files can be opened directly in Excel.

SQL statements are limited in size. This can be an issue when individual records are




manually selected for filtering instead of using ranges or patterns.

Parameter Screens and Parameters

The following relate to limitations and workarounds for using report parameter screens.


When setting defaults for drop-down lists, Use values do not work.

Use Display values instead.

An error occurs in Oracle databases when there are more than 1000 values in a list box and the user selects all of them.

No workaround. This is a limitation of the Oracle database.

An error message is displayed if a large number of results are selected on the Search screen and the Insert button is clicked twice.

No workaround as this is a browser issue. This can occur when making a very large results selection.

A p is placed in front of the displayed field names on the run confirmation screen.

This reflects the current naming convention for field names.

Report totals can differ when using default parameters compared to when using Select All.

For example, in an Inventory report, selecting everything in the prompt for ABC class limits the output to inventory items with ABC classes. There can be items without an ABC class specified. To get items without ABC classes, nothing should be selected in the prompt. There is currently is no way to filter items with ABC class A, for example and items without any ABC classes, at the same time.

Values in columns can be wrapped if the value is too large for the column.

No workaround.

Factory warehouses are included by default. To exclude these, use the prompt page or change the report to add another filter.

When you select multiple results in the Search screen, clicking the Insert button multiple times copies the selected items multiple times.

This does not occur if an individual item is selected.

You cannot perform a search lookup on Stylecode.

This field can contain many thousands of entries and would make screen rendering impractically slow. Use Ranges and Wildcard searches to provide similar functionality.

The Totals section of a report can contain totals for columns that do not require totals, for example, Invoice number.

This is standard report format for first generation reports. No workaround.

The negative sign (-) is displayed above the number if the value is too large for the column.

This is standard report format for first generation reports. No workaround.

The results on the search screen do not resize to fit longer items. Also, if the keyword is the same as the item code, the same information is displayed twice as the format is: <keyword> - <Item Code> - <Description>.

No workaround.

The search functionality only searches for No workaround. This is the way IBM Cognos has




keywords and does not search in other fields.

implemented keyword searches.

Pressing Enter when in a field in the parameters screen can open the search screen, the next parameter screen, or run the report.

Pressing the Enter key is not recommended since it can produce variable results depending on the functionality of the current parameter screen. Use the parameter screen buttons to navigate the parameter screens.

In the Cash Drawer Transaction List report, changing the sales order updates the batch reference for the cash receipt, not the sales order, which is a separate batch.

This report contains the batch reference for the cash receipts and not the Sales Order. These are separate batch references.

The Retail - Layby locations by Pickup date report displays all layby orders, regardless of whether they have a location or not.

No workaround.

Due to page refresh functionality, boxes on the search screen can move or resize during searching or while removing and adding results.

No workaround. This is the way the parameter screens are implemented in IBM Cognos.

No results are displayed when you select K – Kit Item in the Inventory - Valuation by Item Code report.

No workaround.

When setting properties for a report (Set properties Report Set) and changing a date selection field from the default of Entered Dates and today’s date, the default date of today’s date is still displayed when you view all prompt values (Set properties Report View all).

The date range selected is used when you run the report, not today’s date. This also occurs if you set properties for the report and select Related Links View passed source values from the report viewer.

The Yesterday and Last n Days options are not available for date selection in the Project Costing – Project Detail report.

There is no direct relationship between the project master and time dimensions tables.

In the Item code range search omit the last character that will vary and add an underscore to capture that at the Item code text box level.

To use wild card characters, use the standalone Item Code text box instead of the Range text box.

The Payroll Tax by Payroll Number report displays tax based on payroll number. No state-based tax is displayed in this report.

To see state based tax values, run the Payroll Tax by State report.

It is not possible to search by employee number in Leave Liability, Superannuation History or Superannuation Remittance.

No workaround. This feature is scheduled to be added in a future version.

Browsers

The following relate to limitations and workarounds for browser interfaces in PRONTO-Xi Business Intelligence.


PDFs do not open in Google Chrome.

Google Chrome is not supported by IBM Cognos.

Firefox is not supported for Active Reports.

Firefox 4 is not supported for Active Reports. For other Firefox versions, the UnMHT add-on must be




installed to view Active Reports.

Unexpected behaviour or errors occur when using internet browser Back button.

Use of the browser Back button is not recommended. To return to a previous page, use the return arrow button in the top right corner of the screen.

See the PRONTO-Xi Specifications Guide for more information on browser support.




Studios and Applications

This section contains information specifically relating to the PRONTO-Xi Business Intelligence applications.

For information about new and changed features and limitations in the following IBM Cognos studios and applications, see the IBM Cognos website.

IBM Cognos Connection IBM Cognos Business Insight IBM Cognos Business Insight Advanced IBM Cognos Report Studio

The following topics include:

New and changed features (p.20), including major studio or application changes A list of all fixes (p.20) since the last release A list of limitations (p.20), including available workarounds


New Capabilities

The Analytics Dimensions and Analytics Widgets are now licensed capabilities (in addition to Administration, Business Insight, Business Insight Advanced, and Report Studio capabilities), accessed through the PRONTO-Xi Reporting Capabilities (SYS M168) function.

NEW CAPABILITY IDS

Module Analytics Dimensions Analytics Dashboards

Accounts Payable 500 501

Accounts Receivable 502 503

Sales Orders 504 505

Project Costing 506 507

Service 508 509

Maintenance Management 510 511

Inventory 518 519

Enhancements and Fixes

The IBM Cognos BI 10.1 FP1 was incorporated into the PRONTO-Xi Business Intelligence release with Service Pack 1.

For a list of fixes, see the official IBM Cognos documentation at https://www-304.ibm.com/support/docview.wss?uid=swg27020853.

Studio Limitations

The following relate to limitations and workarounds for report authoring in Business Insight and Report Studio.


Filters not updating in Business Insight.

Once added, filters do not automatically refresh to include new data. To ensure you include all data in a filtered report, you must




perform the following steps for each filter widget in the report: 1. Select Widget Actions Properties and then the Filter tab. 2. In the Use only the following values box, either click Select all,

or select any unselected check boxes in the list to add them into the report.

3. Select OK to save the filter settings.

Widgets and filters flashing (IBM Fix Pack 1 issue).

This is an issue in Internet Explorer version 8. You can run PRONTO-Xi Business Intelligence in an external Firefox browser window to avoid this issue.

Drilldown limitation in Excel exports.

When drilling down one level in a report and exporting it to Excel, only the top level data of the DMR is reported. This is not an issue for PDF outputs where you will get the correct data for the selected DMR level.

Text formatting lost when drilling up and down a DMR in a Business Insight widget.

For example, decimal place formatting is lost. No workaround available.

Error messages are received when launching and using Business Insight in the PRONTO-Xi backplane or dockable window.

We recommend that you launch Business Insight in a separate browser window external to PRONTO-Xi.

Data manipulation in complex crosstabs in Business Insight is limited.

Columns or rows cannot be removed or ungrouped, however, sorting is possible. Limited data manipulation is available when you convert the crosstab into a Table List within Business Insight. But converting back to a crosstab after making such changes does not work. It is recommended that you only manipulate very simple crosstabs in Business Insight.

Error messages received during Report Studio sessions.

Report Studio sessions can expire if they are left open too long in a web browser. An error message is displayed. Log-in again through the File menu to save any work and continue.

When two reports with a filter on the same data item are dragged on to Business Insight, filtering one report means that the other report changes.

Business Insight filters both automatically. However, if a particular data item is in a report but there is no filter for that data item, then Business Insight does not filter that report. This is correct as there is no filter specified in that report for that particular data item.

When exporting a report to PDF in Business Insight the filter conditions are displayed at the top of the page.

This is a feature of Business Insight.

The You are leaving the webpage message is displayed when you change something.

Select Save to stop this message.




Installation and Licensing

The PRONTO-Xi Business Intelligence installation is under continual development as we refine our existing processes, add platforms, and update them to match technology changes.

Upgrade Path

The following valid upgrade and installation paths apply to Service Pack 2:

Upgrade 700.1 to 700.2 Initial installation of 700.2

Important: Version 700.0 to 700.2 upgrades must be performed manually.


SDR area Description Impact

57307 Licensing CAP data grid views are now built from valid licenses. Added Bulk mode on the Reporting Capabilities

screen to allow you to add or remove users in bulk from capabilities.

Changed capability names from widgets to dashboard.

Various

57812 Licensing Reporting Capabilities - Group Temporary Licensing When the PRONTO-Xi Business Intelligence licenses are purchased for your organisation, you can additionally purchase temporary licenses for specific capabilities that have an agreed expiry date. Users can be a licensed member of a capability in one the following three categories: Permanent licensed members Members with a license with no expiry date

Temporary licensed members Members with a license that does have an expiry date

Expired licensed members Members with a temporary license that has expired

As you add new users, permanent licences are always consumed first. New users that you add above the allowable number of permanent licenses are added as temporary licenses where they are available. You can transfer a temporary licence to a permanent license using the Temp/Perm mode. You can transfer an expired licensed member to a permanent licensed member using the Expired mode but another permanent licensed member must be removed first.

Note: It is possible to purchase multiple temporary licences for the same capability, each with a different expiry date.

Key Data Module/Function: SYS M168

Temporary License management features




Documentation

These documentation release notes include notifications for:

major updates to the online and print help documentation added help documentation help skin fixes, changes, and enhancements

Fix List

DOCUMENTATION AND HELP

Description Impact

Help search engine updated to provide better user search results. Improved search

PRONTO-Xi Modules PRONTO-Xi



PRONTO-Xi Modules

The purpose of this section of the release notes is to provide details of all software changes included in this service pack for the non-PRONTO-Xi Business Intelligence modules.

Major Changes

The following major changes to the PRONTO-Xi application suite are included in this service pack.

Alert Intelligence

Dynamic Recipients Supporting Security Role as Email Address

Previously, it was only possible to specify a single email address for a field-based dynamic recipient. You can now enter a role in the Email Address column by preceding the role name with R_.

For example, to send a notification to all users assigned to the role A8, specify the recipient R_A8.

EasyEDI

Dynamic ABN Allocation

The Australian Business Number, or ABN, is a unique identifier issued by the Australian Business Register (ABR) which is operated by the Australian Taxation Office (ATO). The ABN is required to be quoted under many circumstances when trading.

Any site using PRONTO-Xi can record their ABN to be used in sales and EDI trading. However, many sites operate a multiple company structure out of a single PRONTO-Xi data set, so need to use more than one ABN.

In 700 Service Pack 2, dynamic selection of the ABN is now available for processing of an EDI invoice out. EasyEDI now checks to see if there is an applicable ABN against the warehouse or territory before defaulting to the ABN stored on the company address.

In this way, a multiple company dataset can ensure that the appropriate ABN is quoted for each transaction.

PRONTO-Xi PRONTO-Xi Modules



Point of Sale

Refund of Serial Items in POS

When refunding serialised items, you can now scan the serial number of the previously sold item. This provides more flexibility for the operator.

Note: This only applies when the Allow Refunds flag is set to V.

POS Entry Field Increased in Size

The POS Entry field has been increased to 99 characters to allow the user to scan, for example, a long barcode supplied by third party loyalty card providers. This supports the use of pre-validate triggers such as special barcodes and increases the flexibility in this area.

RF

Radio Frequency (RF) Despatch By Order

Previously, the RF scan despatch required the nomination of a carrier and service level first, and then the sales order or SSCC related to that carrier. The nominated order was rejected if it was not already assigned to the carrier.

This process has proven restrictive and has been changed.

Now, you can process by SO #/SSCC and then confirm the carrier detail. The carrier detail displays but can be changed. On the warehouse floor, users can change the expected carrier in order to save money, travel earlier than assumed, later than assumed, and so on.

This gives you the option to vary the despatch process via the RF unit in the same way that it can be varied on a terminal screen.

Service

Issue Editing Multiple Serial Items on Service Call

It has long been possible to define multiple serial items on a single service call, but once entered, there was no way of editing the list of serial items originally selected.

A new drill-down button has been added next to the Quantity field on the Service Call Maintenance screen, which will open the list of selected serial items. This screen allows the list to be modified. After exiting this screen, you are prompted whether to change the quantity on the service call to match the number of serials now in the list (This is optional).

Additionally, the following enhancements have been implemented:

Completed PM Calls

Within the Contract Maintenance (SERV M118) function, the Open PM Dockets option now has a new mode called Completed PM Calls which allows access to any completed PM Calls/Dockets for the current contract.

Attached Projects

Within the Project Maintenance (PROJ M117) function, the Attached option has new fields on the data grid including dates, etc. of the attached projects/project calls.

Engineer Lookup

The Engineer lookup screen, which is located in several places such as the Engineer Allocation (SERV M017) function, has been changed to allow the Skill and Territory codes as sortable and filterable columns on the data grid.




Documentation Updates

PRONTO-Xi Help Speed Operation Improvement

A new online Help format was provided with the PRONTO-Xi Dimensions software release. In this initial version of the new PRONTO-Xi Online Help, some load time issues were experienced, particularly if you were trying to access the help over a network with a reasonable amount of network traffic.

In PRONTO-Xi Dimensions Service Pack 2, the speed of operation of the PRONTO-Xi Online Help has been optimised, such that it will work at a similar speed to the pre-Dimensions chm version, whether you have the help installed locally or on a network.

For more information on installing and using the PRONTO-Xi Online Help, see the installation guide in the doc folder on the PRONTO-Xi Dimensions DVD.

PRONTO-Xi Visual Debugger Help

The PRONTO-Xi Dimensions release saw the introduction of a new 4GL Visual Debugger program.

Now in 700 Service Pack 2, an Online Help file is provided with the PRONTO-Xi Visual Debugger.

The PRONTO-Xi Visual Debugger provides the functionality to perform the following operations in a GUI environment:

Execute statement View and set field value Set watch field value Set breakpoints Other functions and tools

Help Zoom Functionality Fixed

In the initial release of the PRONTO-Xi Dimensions Online Help, the zooming functionality was broken. This meant that you were unable to adjust the size of the help to suit your viewing preference. This issue has now been fixed.




You can zoom in and out using the Ctrl + and Ctrl - keys. The most recent zoom setting will also be remembered if you close and then reopen the help.




PRONTO-Xi Enterprise Management System

Maintenance and Wizard Available for Custom

Hierarchies

SDR: 57679

A custom hierarchy maintenance and wizard entry program is available, initially supporting nine of the available custom hierarchy types. This process also allows you to have your system automatically update the custom hierarchies you create using object triggers, to detect data entry affecting objects associated with your hierarchy and adapting your existing hierarchies to include/exclude those changes.

Key Data Module/Function: EMS M010

Keyword Rebuild Optimised

SDR: 57772

The various keyword build routines such as Stock Items, Service Calls, Customers, Suppliers, Service Contracts and so on, are optimised by reducing the disc based I/O operations where possible. The result is that individual item builds as well as bulk load and full rebuild functions are more efficient and quicker.

Tree Menus Being Used Instead of Popup Menus

SDR: 57243

When browsing a table, such as gl-trans in Proman > Browse > gl-trans > Browse > highlight a line > Index/Keys, it now creates a tree menu to the left instead of the pop up menu. This issue has been rectified.

Key Data Module/Function: EMS X000




Advanced Forecasting System

Incorrect Calculation of U-Statistics in Advanced

Forecasting

SDR: 57683

The calculation for u-statistics in Advanced Forecasting was not applying the square root. This issue has been rectified.

Key Data Module/Function: FCS M012

Forecast Record Not Removed Completely

SDR: 57867

When the forecast for an item has been removed in Forecast Maintenance, running Initialisation and Generate Forecast reinstated the previous forecast records. This issue has been rectified.

Key Data Module/Function: FCS M012




Accounts Payable

Payment Commitments Report in Detail Mode Not Using

Min/Max

SDR: 57464

The issue is related to not using the minimum and maximum payment fields when running the report in detail mode. However, these two field options are meant to be used only when the report is running in summary mode to check if the totals are within the entered range. This issue has been rectified by making the two option fields read only in detail mode.

Key Data Module/Function: AP R048

Exchange Loss/Gain on Payment of Foreign Currency

Invoices

SDR: 57543

This SDR corrects the posting of foreign currency loss/gain when paying foreign invoices using the Selective Invoice Payment function (AP T003). This function now posts the loss/gain as per the Manual Cash Payment function AP T034. Foreign currency loss/gain will occur when the currency rate on the invoice does not match the current rate for that currency.

This SDR also now supports the payment of foreign invoices from a bank account with a currency other than the invoice currency, something that was previously possible using the Manual Cash Payment function but not the Selective Invoice Payment function.

Key Data Module/Function: AP T003

Incorrect Posting of Tax for Settlement Discount

SDR: 58069

When processing a payment for a supplier, the tax component of the settlement discount is not posted to the General Ledger if the purchase order is attached to a shipment. This issue has been rectified.


Supplier Purchase Invoice on Contract Purchase Order

SDR: 55122

When entering a P type invoice against a contract purchase order (type T), the system allows the user to enter a negative amount for the invoice. This is in lieu of a credit note, or to reverse out a duplicate invoice. However, the Curr. Amt Ex-Tax field on the extra details screen was not showing the correct remaining balance if a negative amount was entered. This issue has been rectified.





Unbalanced GL Batch for F Type Supplier Invoice

SDR: 57845

When the local invoiced amount of an F type invoice is overwritten with a value of minor difference, the difference cannot be picked up by a currency change due to rounding. This results in the GL other side still being calculated using the old invoiced amount and creates an unbalanced GL batch. This issue has been rectified.


Override Foreign Tax Amount of Invoice to Contract

Purchase Order

SDR: 57864

The following issues have been rectified:

When the tax amount in the invoice details of a P type invoice to a contract purchase order in foreign currency is overwritten, the tax amount is wrongly treated as a local amount and results in the invoiced amount and tax amount being calculated wrongly.

When an F invoice associated with a contract purchase order is approved, posted local tax converted directly from the foreign tax amount may have rounding which makes it different from previously posted tax amount.

When an F invoice with multiple GL entries of the same tax code is approved and associated with a normal purchase order, an I/O error of duplicate tmp-tax-file records is generated.


Supplier Invoice Posting Incorrect Quantity to Project

SDR: 57889

When the Allow On-Order Invoicing MFF is set to 0 or 3, a purchase order with special lines only can be completed by supplier invoicing. If the purchase order is linked to a project, it is completed by supplier invoicing.

In R700, the received quantity is not updated to the project transaction. In R700, the received quantity and amounts are not updated to the purchase order. The received quantity is used in the project transaction for the next I type invoice entered in

the same batch.

These issues have been rectified.


Part Invoicing Not Splitting the Order Correctly

SDR: 57988

When a purchase order is split for partial invoice, lines split into the suffix order are not removed from the original order. This causes the variance amount of the invoice and received total of the original order to be calculated incorrectly. This issue has been rectified.





Bank Transfer Currency Rate Not Based on Transaction

Date

SDR: 58034

When processing a bank transfer, the currency rate is not based on transaction date but on the current date. An exportable procedure was added per customer to override the rate based on the currency rate change history.


Incorrect Posting for Supplier Foreign Transaction

SDR: 57815

When changing the reference on a supplier foreign transaction, the RQ type transaction has an incorrect sign for the foreign amount. This issue has been rectified.

Key Data Module/Function: AP M001

Type 'X' Invoice in Foreign Currency is Not Posted

SDR: 58015

Type 'X' invoice created for shipment freight charge in foreign currency is not posting to the GL and not creating the cre-trans entry correctly. This issue has been rectified.


Variance Purchase Order Has Different Tax Code than

Original Purchase Order

SDR: 58037

The following issues relating to the invoicing of a purchase order with a variance have been rectified:

The system uses the default tax code rather than the code from the original order in the created variance order.

Invoice 'Disc%' and 'Per' are entered in the wrong line. Currently they are entered as PO 'Disc%' and 'Per'.

Invoiced amount and invoiced tax amount in the original and variance orders are incorrect.


Updated Tax Amount Not Shown in Invoice Detail Screen

SDR: 58072

The following issues have been rectified on this SDR:

1. When a 'P' type supplier invoice is raised for a contract purchase order: Tax code is not displayed upon entry to the Invoice Details screen. Tax amount is not updated in the Invoice Details screen after tax amount is changed in the

Tax Details screen.




The screen total is not updated correctly after tax amount is changed in the tax details screen.

2. When an 'I' type supplier invoice is raised, recharge to customer is not shown for update after included tax amount is changed in Invoice Details screen.

3. When the tax amount of a 'P' type supplier invoice for a contract purchase order is updated with a one cent difference, rounding causes the GL batch out of balance.





Accounts Receivable

Account Consolidation Issue

SDR: 56533

The account consolidation was crashing when duplicate promotions were found in the customer promotions file. This issue has been rectified.

Key Data Module/Function: AR M005

EIS Territory Variance Showing Incorrect Figures

SDR: 56648

When looking at the Territory Sales Overall data, the total column shows incorrect figures for the Variance MTD and YTD columns. This issue has been rectified.

Key Data Module/Function: AR E020

Overdue Customers and Interest Charging Issue

SDR: 56653

When the Overdue Customers listing was set to charge interest on overdue accounts and to include credits in the total overdue, (Include Credits = Y), the process was not including orphan rebate credits. This issue has been rectified.

Key Data Module/Function: AR T050

Customer Account Code Conversion Issue

SDR: 57296

The Document Address Mapping details were not being converted. This issue has been rectified.


Customer Copy / Customer Delete

SDR: 57480

Bulk customer delete and manual customer delete from customer maintenance now remove all the same customer related tables. The customer copy from customer maintenance has had additional tables added. The use of these tables can be controlled by a new public exportable procedure.





Duplicate Document Number When Posting Uploaded

Cash Receipts

SDR: 57537

The cheque number (document number) of H payment method type transactions were being duplicated when posting cash receipts, which have been uploaded from a flat file. This issue has been rectified.


Incorrect Consolidation of Cheques in Informal Bank Slip

Report

SDR: 57551

The Informal Bank Slip report can be run so that cheques are consolidated when they have the same cheque number, payee detail and date. However, if you receive two cheques with the same cheque number, on the same date, for the same bank account, but from different customers (so the payee details are different), the report consolidates the cheques incorrectly. This issue has been rectified.

Key Data Module/Function: GL R001

Direct Debit BPay Layout Issue

SDR: 57559

Direct Debit BPay layout is not padding trailing spaces at the end of the record as specified in the layout. This issue has been rectified.


Wrong Partial Payment Posted for Foreign Customer

SDR: 57758

When a partial cash receipt is processed in foreign currency, the amount gets changed with the full amount and has caused discrepancy in the General Ledger. This issue has been rectified.


Tax Not Posted for Multi-Project Invoicing

SDR: 57823

The following issues relating to multi-project invoicing have been rectified:

If tax is applied at line level, the tax amount is not posted and results in an unbalanced GL batch.

If tax is applied at order level, the GL batch is not correct with tax not included in the DCTRL amount.

If tax is applied at line level, the calculated line taxes always use the tax rate of the first entered sales order line during sales order line entry.




Key Data Module/Function: SO T017

Postdated Transaction Receipts Issue

SDR: 57849

Tax entered as part of the credit card charge was not being included in the display totals area of the transaction selection screen, making it difficult to reconcile the receipt visually. This issue has been rectified.


Front Counter Cash Receipts Issue

SDR: 57871

When using a gift voucher to pay for an invoice, if the transaction is cancelled (action type = U for undo receipt), the process was not reversing the gift voucher details. It needed to reset the gift voucher back to its previous status and value. This issue has been rectified.


Unallocated Cash Allocate Issue

SDR: 58105

Major Impact:

The size of the reference field was increased on a previous SDR to accommodate a larger invoice number, and the upgrade right-justified all existing references.

Unfortunately, this included any CU transactions, which contained two leading spaces in the reference instead of CU. This was not a problem for cash or cheques, but if the tender type was postdated (for example, American Express Card); the allocation of the unallocated payment to an invoice changed the transaction type to PD on both the customer and the ZAMEX accounts.

The result was that the CU on the customer account was changed to CR instead of PD. This would normally indicate that the transaction was finalised and the money was now in the bank, however, this was not the case, and there were no General Ledger transactions. Also, the CU on the ZAMEX account was not touched, which meant there were detached CUs on this account, which cannot be matched to the customer account transaction.

If your site is experiencing this issue, it will require manual intervention to restore the transactions to the correct status so they can be offset when the physical payment is made. Contact support for assistance in correcting the data.


Supplier Cash Receipts on Foreign Bank

SDR: 56732

Cash receipts on a foreign bank cannot currently be processed to a supplier account. To achieve the same result for a supplier, the user must process a negative cash payment.

However, there was a loop-hole in the cash receipt program which seemed to allow a cash receipt on a foreign bank to be entered for a supplier. This occurred if there was a customer set up with the same account number as the supplier account number. Although the receipt was processed, there




was no General Ledger posting to the foreign bank account and no exchange loss/gain transactions if required. This issue has been rectified.


Incorrect Local Amount Calculation on Foreign

Customer Journal

SDR: 57645

When you enter a foreign customer journal using the reference of another foreign customer journal with a balance, the local value defaults incorrectly. This means that the remaining balance on the journal is incorrect and makes it impossible to post the correct amount in the journal. This issue has been rectified.


Future Aged Transactions Issue

SDR: 57747

Allocated cash receipts entered with a future period transaction date were not showing as part of the ageing screens. This issue has been rectified.

Key Data Module/Function: AR M001 Major Function Flags: Allow Ageing of Unallocated Credits = 1

Improved Handling of Disputed Invoices

SDR: 58046

These are no longer removed from the system after being marked as disputed. Also disputed invoices can now be marked as being not disputed.

Key Data Module/Function: QMS M008

Customer ABN and Rental Map Key Issue

SDR: 58118

Rental map key was wrongly populated from the Customer master through the "DA" type record in the name and address master. This issue has been rectified.

Key Data Module/Function: RENT M015




Alert Intelligence

Dynamic Email Option Not Working for payroll-

employee-details Table

SDR: 57547

Selecting the field n.employee-no in the table payroll-employee-details did not work in Dynamic Email/SMS/Fax options. This issue has been rectified.

Key Data Module/Function: AI M001

Email Notification Issue

SDR: 57837

Grouped Email notifications were being delayed in preparation. This issue has been rectified.


Dynamic Recipients Supporting Security Role as Email

Address

SDR: 57977

It was only possible to specify a single email address for a field-based dynamic recipient. You can now enter a role in the Email Address column by preceding the role name with R_. For example, to send a notification to all users assigned to the role A8, specify the recipient R_A8.





Application Services

Automatic Close of Cash Drawer

SDR: 56855

When the Cash Drawer Number major function flag was set to 6, the automatic bulk-close of cash drawers was failing when run in batch mode, for example, Application Service. This issue has been rectified.

Key Data Module/Function: APPS M001




Business Intelligence

Reporting Hierarchies - Bulk Maintenance

SDR: 57995

Each of the Reporting Hierarchies has had two new functions added to it.

The Crosscheck function now has modes to allow the missing hierarchy items to be marked and then set with level details defined by the operator.

The Maintenance function now has a Bulk Update mode that takes the operator through three steps to update details of existing hierarchy details:

1. Select Range of items based on the items code/range and existing level values

2. Mark/Select the items to update from the list produced by step 1

3. Update (or clear) the level values for the items marked in step 2

These functions will assist when dealing with multiple items where hierarchy details are required.





Customer Relationship Management

OLE Connections Not Released After Sync

SDR: 57668

When MS Outlook synchronisation is done for contacts, which are numbered more than 250, the OLE connection is not released and the synchronisation stops without completing. This issue has been rectified.

Key Data Module/Function: CRM T001

Data Mining Issue

SDR: 57606

The Account Criteria Selection filters were being ignored if there was a value in the Attribute Expression filter. This issue has been rectified.

Key Data Module/Function: CRM M006

Contact Drilldown for Reports Issue

SDR: 57738

The drilldown for a CRM Contact was not working correctly, instead it displayed an error about unknown parameters. This issue has been rectified.

Key Data Module/Function: CRM

Opportunity Transactions Issue

SDR: 57788

These transactions were not being sorted by date. This issue has been rectified.


CRM Contact Entry Issue

SDR: 57921

Keywords were not being automatically updated when a contact was maintained (that is, entered, corrected, and so on). This issue has been rectified.





CRM Outlook Sync Ignoring Date

SDR: 58088

When synchronising the PRONTO-Xi calendar with your MS Outlook calendar, the Numbers of Weeks History to Keep option was sometimes ignored. This issue has been rectified.

Key Data Module/Function: CRM T001




Data Intelligence

Displayed Data Different to Actual Data

SDR: 57993

DI project is created using two objects connected by the OUTER join resulted in invalid data. This happens when a filter is used for a secondary object and the data is displayed differently to what actually is. This issue cannot be rectified due to the runtime behaviour.

Key Data Module/Function: DI M002




Electronic Data Interchange (EDI)

Outgoing POA Document Not Displaying UOM Correctly

SDR: 57711

When an outgoing POA document is created from a sales order, which has been created by an incoming PO document, the unit for the inventory item was not the same as the unit from the PO document. This issue has been rectified.


Item Codes Not Mapping Automatically

SDR: 57715

If an incoming orders file as a zero number GTIN, any subsequent VP item codes were not being mapped automatically. This issue has been rectified.


ASN Ship to Code Field is Blank

SDR: 58133

Delivery address is available in the Customer master, and the sales order for the customer is created manually without using the EDI module. When the ASN is despatched through the ScanPack module for this customer, which is defined as a trading partner, the ship to code field will now be populated from the ship to code table.

Key Data Module/Function: SCAN M006

Line Date Not Passed Through to Sales Order

SDR: 58201

If an expected delivery date has been set on an incoming EDI ORDERS file, it will now be passed to the newly created sales order. This will be useful in splitting the sales order based on the delivery dates set on the lines.





FaxMail

Default Field Values Not Working in FaxMail Transmission

Screen

SDR: 57665

Default values can now be set for any field in the FaxMail Transmission (FAXM R001) function for repeated use.

Key Data Module/Function: FAXM R001

Defaults Not Saving on FaxMail Transmission Screen

SDR: 57863

The default values for the From fields on FaxMail Transmission were not being saved. This issue has been rectified.

Key Data Module/Function: FAXM R001




Fixed Assets

Incorrect Cost Posting for Serialised Fixed Asset

SDR: 57362

When actual costing is used, a serialised inventory item can be received into stock at different costs. If two serial units from the same stock item are allocated as fixed assets in the same batch, the posting was not extracting the correct cost for the serial unit. It just used the cost from the first serial unit attached to the stock item. This meant that the cost postings were incorrect and variations on cost were generated. This issue has been rectified.

Key Data Module/Function: FA T002 Major Function Flags: Inventory Cost to Use = T




General Ledger

Data Grid Filter Not Working

SDR: 55898

If a Statement Reconciliation has a default view with a filter on it, for example, filter is set for value EQUALS 1, then whenever you open that data grid, the row with the filtered record is not displayed. You have to use the up arrow to display the record in order to select it. This issue has been rectified.

Key Data Module/Function: GL T010

Incorrect Information Displayed in GL Batch

SDR: 57125

When (I)mmediate withholding tax is selected in Accounts Payable when entering a supplier’s invoice, in the resulting batch, all the tax lines have withholding tax in the Detail field. This is not correct; the GST/VAT portion should not say withholding tax. This issue has been rectified.


Expand Button Not Shown in FRW When Print Offset > 0

SDR: 57384

When the print offset was greater than ZERO for the row, the expand or drilldown button was suppressed. This issue has been rectified.


General Ledger Chart of Accounts Issue

SDR: 57633

When entering a new General Ledger account, access to the Level field had been inadvertently removed. Access has now been restored. The Level field should be accessible if the account is newly entered, or an existing account which has no balances and no history.

Key Data Module/Function: GL M008

Cognos GL Master Chart Hierarchies

SDR: 57634

The initial release of Cognos allowed for only the Natural Account section of the GL Chart of Accounts to be used in the GL Reporting Hierarchies. This issue has been extended to allow hierarchies to be built on any other elements of the GL Chart that have been used. This includes:

Company Business Unit Corporate Break Region Section




Department Cost Centre Sub-Section State Territory

The 5 menu options within the new GL.X056 menu will prompt for the GL Chart element that is to be used. This list of Chart elements will be based on what elements are currently used in the dataset. If this dataset uses Company, Region and Business Unit, only these 3 options will be shown when any of the Set Maintenance, Level Maintenance, etc. is selected.

These new hierarchies are available to use within the various Cognos namespaces.

Key Data Module/Function: GL X056, GL M047, GL M048, GL M049, GL M050, GL M051

General Ledger Enquiry Commitments Screen Issue

SDR: 57684

During General Ledger Enquiry, the user can select Commitments from the [Extra] mode. However, the [Find] mode was not working on the screen. This issue has been rectified.

Key Data Module/Function: GL E003

Financial Report Is Printing ^Z in Excel for Column Type Z

SDR: 57754

When Financial Report is run having a type Z column, it is printed as ^Z instead of a SPACE. And if the spreadsheet is only for update and has been changed to have embedded formula, this is also overwritten. This issue has been rectified.


Customer Price Enquiry Issue

SDR: 57761

If the user chose not to enter a customer code in the enquiry screen and used [ESC] to return to the menu, the system was attempting to find a customer account with blank as the account code, and then display an error message and aborting. This issue has been rectified. The system now returns directly to the menu.

Key Data Module/Function: SO E063

Multiple BF Transactions Results in Wrong Opening

Balance

SDR: 57856


When the General Ledger is archived for the last period of the year, multiple BF transactions are created for the GLAPP account. This results in the opening balance being wrongly calculated and overwritten by the General Ledger integrity.

The General Ledger integrity report does not fix up multiple BF transactions for a GL account.




Key Data Module/Function: GL X040

Reload GL Transactions from Archive Issue

SDR: 57982

This program can be used after upgrade from R670 to R700 to move archived GL transactions back into the transaction file. General Ledger transactions are no longer archived into a separate file in R700. The program was created with an incorrect [module.function], which meant it could not be called using a short cut and if help was requested from the input screen, the manual displayed details of a different program. This issue has been rectified.


Tax Analysis Display Issue

SDR: 57991

The program was losing currency on the highlighted summary transaction when returning from the Full Detail screen. If you then selected the Row Detail mode expecting to see the details of the highlighted screen transaction, the details of the last current row in the Full Detail screen were shown instead. This issue has been rectified.


GL Cash Flow Image - Starting Position Accounts

SDR: 57994

This function used to rely on either a manually entered Starting Position value, or a custom/public exportable procedure to determine the default for this field.

A new menu option has been added to the RH side of the screen to allow specific GL Accounts to be defined. The sum of these GL Accounts current and future balances will now form the basis for the default of the Starting Position value. Typically these GL Accounts would be the Bank accounts but in fact any account can be defined, even a Quantity type account.


Budget Import from File Still Running after Session

Disconnected

SDR: 58026

If a user session is terminated during a budget load to GL from Excel (GL.M184), the program loops continuously populating a temporary file until all space is consumed and the system stops. This issue has been rectified.





GL Reporting Hierarchy Template Rules

SDR: 58030

A new mode has been added to the GL Master Chart screen for A chart accounts so that a Hierarchy Template Rule code can be defined (for one or more hierarchy sets). This rule code can be then defined on the GL reporting Hierarchy Template based on the Account Type.


Reporting Hierarchies Tree Menu

SDR: 58084

An issue with recurring display in tree-menu view mode has been rectified.

Maintain Ledger Locks Issue

SDR: 58160

The default radio buttons on this screen are now set correctly.





Inventory

Stock Take Count Entry Issue

SDR: 56972

Entry of stock take counts using the T (Ticket) option was writing the ticket number to the location reference and FIFO costing reference, if the item was not lot tracked. This issue has been rectified.

Key Data Module/Function: INV M159

GL Account Code for Issue Item in Kit

SDR: 57016

For an Issue controlled item in a kit, if you set a warehouse specific GL account code for it, it was not picked up when updating purchase orders. This issue has been rectified.

Key Data Module/Function: PO T029

Multi-GTIN Updating the Item Master Unit of Measure

SDR: 57491

When multiple GTIN are maintained for an item, the master unit of measure for the item gets updated if the default record was changed. This issue has been rectified.


Reorder Report Not Accepting Screen Defaults

SDR: 57517

Some of the fields on the reorder report do not obey the screen default fields. This issue has been rectified.


Console Commitments Drilldown Issue

SDR: 57570

The drilldown on a commitment displayed the wrong status. This issue has been rectified.

Key Data Module/Function: INV E005




Display Issue in Inventory Console Enquiry

SDR: 57582

The console enquiry of Location Quantity By Warehouse was showing LOST Location as available stock. This issue has been rectified.


Maintain Serials Display Issue

SDR: 57617

The Trace mode in the Serial Number Maintenance function displays each of the orders that have been linked to the particular serial number. If both a sales order and a credit note had been linked to the serial, the sales order description was incorrectly displayed as a credit note also. This issue has been rectified.


‘Can Build’ Tab Missing in Inventory Enquiry Console

SDR: 57806

This change reinstated a loss of functionality from v650. The Can Build tab can now be used to display component availability for kits as well as manufactured items.


Daily Warehouse Report Issue

SDR: 57807

The status of a sales order following another order with a status of Repair Completed was incorrect. This issue has been rectified.

Key Data Module/Function: INV R055

Maintain Special Pricing Display Issue

SDR: 57835

When scrolling through the Detail screen, the customer name and item description were not being refreshed. This issue has been rectified.


Item Copy Issue

SDR: 57880

The Actual Promotional Value was being copied across when a new item was copied. This issue has been rectified.





Build/Merge an Item with Bill of Materials Issue

SDR: 57924

This change rectified an issue with the inability to build/merge an item with Bill of Materials.

Key Data Module/Function: INV T012

Correcting Configured Component

SDR: 57959

Prior to this change, replacing a configured component using the correct mode, was not removing associated formula from the product configurator. This issue has been rectified.

Key Data Module/Function: MANU M071

Inventory Console - Can Build Option

SDR: 58116

Prior to this change, performing Can Build enquiry on a bill containing an inactive phantom subassembly resulted in subscripting error. This issue has been rectified.


Stocktake Not Showing Already Counted Details

SDR: 56714

In some situations when a stocktake count is entered, re-frozen, and then entered again, the previous counts were not being shown. This issue has been rectified.


QA Hold Item Not in QA Hold Control Screens

SDR: 57476

When the pallet tickets were printed for an item on QA control, they were no longer appearing on the QA Hold Control screens. This has now been changed.

Key Data Module/Function: INV T021




Incorrect Values Shown in Issue to Work Order Screen

SDR: 58181

For items with 4 decimal places on a Bill of Materials, when issuing stock, the required and issue quantities are showing incorrect values. This problem has been rectified.


Inventory Enquiry Console Issue

SDR: 58196

The Bill of Materials details button is not showing the correct content of the bill when you select the bill of materials header button first. This issue has been rectified.


Stock Take Difference Report - Items with Zero On Hand

SDR: 58210

This change reinstated a change of functionality from v650. With this change, the difference report will now honour the Print Variances Only option for items with zero on hand and zero count.


Inventory Console - Manufacturing/Can Build Tab

SDR: 58221

Prior to this change, when the Can Build tab is selected for an item with no bill of materials, PRONTO-Xi displayed the full list of bill of materials in the system, which can be confusing. A message will now be displayed instead.





Maintenance Management

Work Order Forecasting Issue

SDR: 56843

A work order was not being created early enough to purchase an Indent item that was a component of a kit. This issue has been rectified.

Key Data Module/Function: PLT M134

Completed Work Orders Issue

SDR: 57442

Purchase orders could not be reviewed for completed work orders. This issue has been rectified.


Export File to MS Project in Incorrect Format

SDR: 57548

MS Project does not recognise the created export file. This issue has been rectified.

Key Data Module/Function: PLT R028

Forecast Work Order Creation Issue

SDR: 57685

A Forecast Work Order was populating the Actual Start Time instead of the Estimated Start Time when a PM Task with a Start Time populated was used in the Scheduled PM Work orders function. This issue has been rectified.


Work Request Required Date Issue

SDR: 57746

The work request was not being set as per the number of offset days in the N1 system table when the Control Date was set to Y. This issue has been rectified.





Reference Monitor Point Issue

SDR: 57832

The Current Value and the Latest Reading Date from the reference monitor point is not being updated on the Component Plant Item either through a manual entry or a work order update. This issue has been rectified.


Default Field Values Not Retained in Work Request Entry

SDR: 57855

Default set ups were not defaulting in subsequent entries of work requests. This issue has been rectified.


Convert PM Task Issue

SDR: 57873

If one user is in PM Task Maintenance/Enquiry while another user is trying to perform PM task conversion, the conversion failed. This issue has been rectified


PM Tasks Calculated Fields

SDR: 57904

When upgrading PRONTO-Xi to the Dimensions release (V700.n), the table used by Cognos for PM Task Next Due Date reporting will now be populated correctly.

Work Request Required by Date Issue

SDR: 58010

An entry in the Required by Date was reverting to today’s date plus any offset in the N1 priority code. This issue has been rectified.


Actual Start Date Field Not Set in Quick Work Order Entry

SDR: 58213

The Actual Start Date was not being set after the completion of a quick work order. This issue has been rectified.





Plant Item Changing to Next Item in Monitor Point

SDR: 58146

A plant item has monitor points and is linked to another plant item. When viewing the monitor points and then readings through the plant item, selecting escape changes the plant item to the next record, not the original record. This issue has been rectified.





Manufacturing

Work Order of Backflushed Item Cannot Be Completed

SDR: 54836

Work order of backflushed manufacturing item cannot be completed if there are committed components of negative on hand quantity. This issue has been rectified.


Kit Recursion Issue

SDR: 55140

When setting up a Kit BOM, you now cannot set up the situation where Kit1 is the parent of Kit2 and Kit2 is the parent of Kit1.


Inconsistent Results in MRP

SDR: 56515

When a sales order delivery date was in the future but within the minimum stock cover days for an item, there was some doubling up of Net requirement and Planned Order received amounts in MRP. This issue has been rectified.

Key Data Module/Function: MRP E001

Work Order Entry - Subcontract Purchase Orders Issue

SDR: 56959

During work order entry, if the Auto Create Contractor flag = Yes, the subcontractor orders are automatically generated. If this flag is set to No, there is an option during entry to generate the subcontractor orders for this work order. When setting this flag to Yes, the subcontractor orders were not being created. This issue has been rectified.

Key Data Module/Function: MANU M027 Major Function Flags: Auto Create Subcontract PO’s = NO

Cannot Review Serial Details in Work Order Maintenance

SDR: 56978

Reviewing the details of components for a work order allows for a review of the serial numbers that have been issued for a serial tracked item. If the serial Trace Level is set to 0, this option was not available. This mode now allows for optional maintenance/review of serials for the work order, with this trace level.

Key Data Module/Function: MANU M073 Major Function Flags: Serial Trace Level = 0 (Optional)




Changing Routing Parameters with Production Booked In

SDR:57213

The validation error for routing sequence number when production has started should only trigger if the value has been changed. And changing of other routing parameters should be allowed at any time. This issue has been rectified.


No Option to Auto View Project Card and Label

Document

SDR: 57252

When the project card or label document is printed, it does not follow the environment setting for the variable PROXMLREPORTS to view automatically. It was always spooled. This issue has been rectified.

Key Data Module/Function: MANU R069

Missing Information in Work Order Issue Report

SDR: 57419

When the Work Order Issue report is generated from Work Order Maintenance, there is missing information, such as work order number, parent item code and work order date. This issue has been rectified.


Cannot Perform Production Reversal for a Lot Tracked

Finished Item

SDR: 57560

This change reinstated a function that allowed for the reversal of production entered, but not updated, for a lot tracked finished item. When there is a requirement to reverse all production that has been entered and specific lot in stock, a production docket is required for each reversal, that is, one to cover production entered but not updated, one for each lot reversal.

Key Data Module/Function: MANU T014 Major Function Flags: Batch/Lot Reference Format = ‘7’

Error in Production Docket for Downtime

SDR:57568

An error occurred if a production docket for downtime had no associated work order. This issue has been rectified.





Cannot Enter Return Location when Returning

Components

SDR: 57607

Returning issued components on a work order back to a warehouse was not allowing entry of the return location after the first return item. This issue has been rectified.


Maintain Work Orders Display Issue

SDR: 57677

The Issue Qty for labour type item code is now displaying correctly on the Issue Inventory to Work Order screen.


Cannot Edit Create PO Field in Work Order Entry

SDR: 57703

The Create POs field could not be entered when creating a work entry, due to it relying on routing information to be entered first. This issue has been rectified.


Irrelevant Information Displayed in Shortage Report

SDR: 57770

When a component is purchased in with a quantity sufficient for use in a work order, the Availability/Shortage report in shortage mode will show the component in the Purchase Order Summary section of the report. The component should not be shown in the report if there is no shortage. This issue has been rectified.

Key Data Module/Function: MANU R021

Planning Policy and Days Cover in MRP Processing

SDR: 57822

For an item setup with weekly or monthly planning policy, MRP processing was suggesting daily planned orders. This issue has been rectified. The handling of Min Days Cover has also been changed to be the safety time. Previously, if safety stock was also set up for the item, the determination of planned quantity was based on the greater of these two values.

Key Data Module/Function: MRP M001




Subcontract Purchase Orders Not Appending to Open

Purchase Orders

SDR: 57899

When re-ordering items, and creating a work order, if there was already an open PO for that item, the new order was not appending to the existing order. This issue has been rectified.

Note that this issue only occurred when the Create New PO for Subc. routings major function flag is set to N.

Key Data Module/Function: PO M026

Unable to Commit Work Orders Created from Reorder

SDR: 57896

When creating work orders from the Reorder All Items screen, you could not commit the work order. This issue has been rectified.


Unable to Use Factory when Adding to Reorder

SDR: 57897

When adding a manufactured item to the Reorder All Items screen, you were unable to use the existing Factory Supplier for that item. This issue has been rectified.


Work Order Not Created for Correct Component

Warehouse

SDR: 57898

When creating a work order from the Reorder screen, if you override the default component warehouse, it is not being used on the work order that is created. This issue has been rectified.


Incorrect Price on Purchase Orders Created from

Reorder

SDR: 57950

When creating a work order from the Reorder All Items screen, subcontract purchase orders were not being appended to with the correct price. This issue has been rectified.





Production Reversal - Laboratory Item Tests Issue

SDR: 58017

This change rectified an issue with incorrect evaluation of available quantity for lot reversal when the MFF licence system is not used, but there are laboratory item test results.

Key Data Module/Function: MANU M043 Major Function Flags: Licence System Usage <> ‘3’ or ‘4’

Load Work Orders - Multiple Factories Issues

SDR: 58042


Work orders were created with incorrect finished items, from linked sales orders, due to incorrect association of BOM ID for a bill with no default route.

For a finished item with multiple factories setup, PRONTO-Xi was incorrectly using the bill with the default factory, even though the finished goods warehouse was linked to a different factory.

Key Data Module/Function: MANU M021, MANU.M027, MANU.M023

Work Order Missing Information for Multiple Bills of

Materials

SDR: 57951

When creating a work order, the version code for multiple Bills of Materials is missing in the selection screen. This issue has been rectified.


Work Orders Incorrectly Set to Completed

SDR: 57309

Work orders were being set to Completed Updated when they were not within the Tolerance percentage, when they should remain at In Progress. This issue has been resolved.

Key Data Module/Function: MANU T001

Manually Committed Work Order Component Using

Incorrect UOM

SDR: 57667

Components manually committed to a work order were calculating the wrong Quantity Per value when the component had an alternate unit of measure and conversion factor. This issue has been rectified.





Error in Split Sales Order Link to Work Order

SDR: 57743

If a sales order contains multiple manufactured items and is split into multiple sales orders with suffixes linked to work orders, the link information for each order is wrong. This issue has been rectified.


Serial Required When Entering Labour Docket

SDR: 58207

When a work order is raised from a project and a labour docket is added, a serial is being forced to be entered. This issue has been fixed.





Payroll and Human Resource Management

Payroll YTD/Trans Rebuild Warning Message Changed

SDR: 57406

Changed the warning message on the screen to ensure that all conditions are satisfied before proceeding.

Key Data Module/Function: PAY M061

Maintain an Employee Message Issue

SDR: 57533

When maintaining a terminated employee, the Employee not updated on Details file message is unnecessary and has been removed.


Payroll YTD Earnings Report Incorrect

SDR: 57689

Column totals (and column details) on the Earnings YTD report is unable to handle large number of digits and it is displayed as 1.055801E+8 or characters similar to this. This issue has been rectified now by lengthening the total fields but not the column details as it is not practical to go into such big number of hours per employee.

Key Data Module/Function: PAY R016

Payroll Number Maintenance (Masking) Issue

SDR: 57729

When a new payroll number was added to the system, the process was only adding it to the masked security access of the user entering the record. This has been modified to ensure that any user, whose masking allows access to the new number, has it added to their masking details.


Superannuation Remittance Advice Issue

SDR: 57784

The Help on the Super Fund Company returned the code of Super Fund Id. This issue has been rectified.

Key Data Module/Function: PAY R054

Productivity Leisure Day Timesheet Transactions Issue

SDR: 57847

The posting program to transfer data from timesheets to payroll for processing did not recognise user defined Productivity Leisure Day timesheet transactions. As a result, it failed to set one of the




fields correctly. This meant that the employee’s Productivity Leisure Days leave history and current balances were not updated when the pay was processed. This issue has been rectified.

Key Data Module/Function: SYS T033

Shift Allowance Display Issue

SDR: 57439

The Shift Allowance value in table SA is rounding up or down if the value is above $1000. This issue has been rectified.

Key Data Module/Function: SYS M477 Table Entry: ‘SA’

Employee Leave Request Processing Issue

SDR: 57722

An employee's leave request was not processed if there was no permanent transaction for the employee. This issue has been rectified.


Incorrect Posting for Project Oncosts

SDR: 58023

Oncost posting to a project did not have the same sign as the amount posted to General Ledger for payroll deductions. This issue has been rectified.

Key Data Module/Function: PAY T001




Point of Sale

POS Entry Field Increased in Size

SDR: 57456

The POS entry field has been increased to 99 characters to allow the user to scan in a long barcode and then use the pre-validate trigger to select the data they want out of it.

Key Data Module/Function: POS M017

Point of Sale Entry Kit Refund Issue

SDR: 55193

In POS refund, a kit item should be refunded at the price of the original sales order. This issue has been rectified.


Refund of Serial Items in POS

SDR: 56846

When refunding serialised items, you can now scan the serial number of the previously sold item. This only applies when the Allow Refunds flag is set to V.


Serial Item Issue

SDR:57417

During a POS Sale, it is possible to identify and add an item to the order by entering the serial number of the item being sold. If this is done and then the sales line is not completed when prompted for a price override, the serial was still incorrectly linked to the sales order line. This link is now only created once the sales order line is created.

Key Data Module/Function: POS M017 Major Function Flags: POS - Price Override = ‘R’

Cannot Exit Special Order Refund Screen

SDR:57472

When cancelling a layby in Point of Sale entry, the Special Order Refund screen is displayed. Close command C has been provided to escape out of the screen.





Operator ID Not Tracked for Auditing Purposes

SDR: 57534

Operator ID of POS was not written in the sales order audit record when a state change happened by the POS process. This issue has been rectified.


POS Timeout Not Resetting Menu

SDR: 57561

When using the GUI POS, a Rep Timeout is set and the Rep logs back in after a timeout, the menu buttons will be reset to the front menu.


Max Balance for Petty Cash Can Be Exceeded

SDR: 57562

The maximum amount of petty cash that can be withdrawn from a cash drawer before the next cash drawer reconciliation can be set as the Max Balance for a store ID. The system was allowing money to be taken as petty cash from the cash drawer above this limit. This issue has been rectified.

Key Data Module/Function: POS T002

POS Payment Issue

SDR: 57584

When paying for backordered items by EFT, sometimes the payment is rejected. If the user opted to remove an item from the sale and pay for the remainder using an alternate tender type, the display on the screen still showed the original amount, and after paying for the items currently on the sale, the system still demanded payment for the removed item. This issue has been rectified and the system only displays and expects payment for the items actually still on the sale.


Record Locking Issue When Using Price Override

SDR: 57648

During a POS Sales Transaction, if the operator used the ‘.’ option to display the Price Override option and then changed the price, sales order related records remained locked until another line or function was performed. This could cause locking issues for other users and has now been rectified.

Key Data Module/Function: POS M017 Major Function Flags: Cash Drawer - Price Override = YES




Invoice Not Re-Printing With Correct Backorder

Quantities

SDR: 57868

When an invoice is reprinted, if the Print Backorder Info is set to Y, and if there are backorders created splitting the original sales order, the sales invoice report will show backorder lines as well in the report.


Stock Identifiers Returning Items Linked to Different

Customer

SDR: 57983

When setting up stock identifiers, two customers might have the same identifier for two different stock items. But when the stock identifier is entered in POS order line, the system now selects the correct stock item set up for the customer entered in the POS order.


Backorder Items Marked as Taken

SDR: 58021

When sales order lines are entered in a POS order with backorder quantities, the system creates a split order and moves all the backorder sales order lines with backordered quantities to the split order and sets the status of that to backorder. The Print Flag of the backorder lines should be blank as the backorders created using normal sales order process. This issue has been rectified.


Issues Performing Account Payments Using Tyro

Terminals

SDR: 58049


1) RPOS - Declined Cards in Tyro Processed as Accepted

When an account payment is done and in the Tyro terminal the transaction is declined, the control is returned to the POS screen. The user then presses escape button which will allow the screen to process the payment, even though the Tyro machine has cancelled the payment. This issue has been rectified.

2) RPOS - Integrated EFTPOS Account Payment Issue

When processing an account payment though a cash drawer that does not have integrated EFTPOS, it still tries to send it via integrated EFTPOS due to the tender type flag set to Y, although when you process a sale through POS it works correctly and does not try to initiate the integrated EFTPOS. This issue has been rectified.

3) .request and .event File Copy in WINDOWS OS Using Tyro Terminals




While using WINDOWS OS, the file copy from the current working directory to the file watcher directory was not happening for the .request and .event files.


Cash Drawer Transaction History Issue

SDR: 56723

The cash drawer transaction history was not displaying the related sales order if there were multiple tender types associated with a transaction. This issue has been rectified.


Cash Reconciliation History Not Showing All Stores

SDR: 57651

When entering in a space for the store-id in the Cash Reconciliation History, not all stores were being shown. This has now been resolved.

Key Data Module/Function: AR E015

Integrated EFTPOS Inconsistent With Account Payment

SDR: 58167

In Cash Drawer Configuration, EFTPOS Setup set as ‘N’ and Eft/Type set as ‘Y’ in Tender type. In this scenario, when an account payment with this tender type is done, the system will proceed with the payment without calling any third party software to complete the payment.


Suppress Lines = S Duplicating POS Backorders

SDR: 57947

In the invoice layout, if the Suppress Order Lines flag has set to 'S', the POS order will be split if there are backorder lines during the print invoice process. If that has happened, the POS order should not split again to create another suffix backorder at a later level of order process. This issue has been rectified.





Project Costing

Travel Rate Not Coming Across to Sales Order

SDR: 57138

When invoicing a service call, the travel rate is the item price of the sales order line created for the travel time. The item price was not being recorded on the sales order. This issue has been rectified.

Key Data Module/Function: SERV M096

Post Timesheets Branch Mask Issue

SDR: 57142

Where a number of time sheets are entered for a range of different branches and the posting program is restricted to a particular branch, an error report is produced for projects that are not from the entered branch. This issue has been rectified.


Credit Note Creation Using Return Pick

SDR: 57182

Credit note creation using Return Pick allows return of more than the quantity shipped on the original picking slip if the user entered multiple credit notes for the same picking slip but partial quantities. A new screen has been added to show the sold quantity and the returned quantity to let the user know how much is available to return in the next credit note.

Key Data Module/Function: PROJ M117

Project Type Change to Grandparent Issue

SDR: 57226

If a project is entered as a quotation with a type N for normal and then has purchase orders raised and finished against it, the project type can then be changed to a Grandparent (P) having other projects added to it. This issue has been rectified. Stopped project type changes to grandparent when there is cost category added.


Display Issue with Paid Field on Claims Screen

SDR: 57544

The Paid field on the Actual Claims for Project screen is now displayed as exclusive of Tax.





Variations for Project Issue

SDR: 57557

Variation details are wrong at the initial entry of variation. This issue has been rectified.


Timesheet Details List Report Issue

SDR: 57566

Records were printed that were outside of the branch filter values. This issue has been rectified.

Key Data Module/Function: SYS R035

Enquire on Summary Mode Not Displaying Correct Order

SDR: 57586

In Project Maintenance/Summary/Transactions, an enquiry did not display the correct order. This issue has been rectified.


Cost Category Conversion Issue

SDR: 57591

This function was not executing properly in both Batch and Sequence modes. This issue has been rectified.


Claim Totals Not Printing Correctly

SDR: 57595

The values in the Project Claim Schedule Breakdown report should show the correct values from the claims created for the project. This issue has been rectified.


Sort Order Not Correct when Importing Master Items

SDR: 57626

When using the import process from the claim schedule, the sort order of created master items is incorrect. This issue has been rectified.





Budget Summary Screen Display Issue

SDR: 57627

The Forecast Cost value was not displaying when called from the Project Summary Screen Maintenance function. This issue has been rectified.


Project Budget Details Issue

SDR: 57636

Entry of the Project Budget Detail records was duplicating the entered record for an S special line entry. This issue has been rectified.


Incorrect Default Value for Profit Takeup End Field

SDR: 57652

When performing a Project Profit Takeup (PROJ.T002), the system did not return any values if the Project end field (ws-end-job) was left blank. ws-end-job field should have been populated with trailing ‘~’. This issue has been rectified.

Key Data Module/Function: PROJ T002

Create Subcontracts Issue

SDR: 57676

There is an YY table code for PO to allocate the next purchase order number. PO is the system default, but individual sequences can be set up by warehouse by setting up POMEL or POSYD.

When the user scrolled up on the screen to the warehouse field, and then scrolled back down through the screen fields, the system was generating a new purchase order each time the warehouse field was entered. This was regardless of whether the warehouse code had been changed. The previously generated purchase orders were left in the system in a status of Being Entered.

This issue has been rectified as follows:

The purchase order number is only changed if a new warehouse code is entered, and the new warehouse does not use the same sequence as the previous code.

If the new warehouse code uses a different sequence, then the previous order will be set to Cancelled before the new order is generated.





Project Maintenance Printing Issue

SDR: 57686

When a Project Claim was certified, the spool file created was not being displayed as the current file by the report manager. This issue has been rectified.


Claims Schedule Not Printing Totals for Large Schedules

SDR: 57707

When a claim amount entered or changed the sub totals, the full total of the claim schedule for the specific claim should update accordingly. This issue has been rectified.


Task Resource Report Issue

SDR: 57742

A project code of 8 characters was being truncated to 7 characters. This issue has been rectified.

Key Data Module/Function: PROJ R050

Unbalanced GL Batch for Sales Order Linked to Project

SDR: 57771

The following issues in relation to tax at order level have been rectified:

Invoiced amount of a sales order raised for a project is displayed wrongly in project maintenance.

When a sales order raised for a project is updated, the project invoiced amount is calculated wrongly by including the tax amount and results in an unbalanced batch.

When a sales order in foreign currency raised for a project is updated, the DCTRL amount is calculated wrongly by excluding the tax amount and results in currency exchange loss/gain.


Timesheet Details Report Issue

SDR: 57774

The report did not print the project’s branch, description or account for a completed timesheet. This issue has been rectified.

Key Data Module/Function: SYS R035




Unable to Remove Details from Cost Categories in

Forecast

SDR: 57796

From Forecast Cost to Complete, you can add details to the Cost Category using the Detail mode. These details can be removed using the Remove mode. After removing details, the modified Cost Category needs to be updated to update the project details correctly. The Remove mode will not work if the deleted detail record is the last record for the cost category and Bulk Delete does not work properly either. User can enter a note line in the details after a bulk delete or delete the last record to update the project values correctly. This issue has been rectified.


Incorrect Display of Cash Receipts in Cash Position

Report

SDR: 57816

Cash receipts are now reported as GST exclusive.


Totals Incorrect on Claim Print with Variation Included

SDR: 57830

When a project has claim schedule with multiple levels, and variations included into the middle of the contract sections, the Project Claim Schedule Breakdown report gives wrong figures for subtotals. The contract and variations individual sections are also wrong. This issue has been rectified.


Performance Issues with Delete Complete/Lost Projects

Function

SDR: 57850

The performance of this process has now been improved.


Forecast Update Process Can Remove Budget Details

SDR: 57862

The Detail mode in the Forecast Cost to Complete Project screen should show the details of the cost category selected. If a forecast has been done for the cost category, the details of the last forecast should be displayed. This issue has been rectified.





Overall Executive Report Issue

SDR: 57883

A subproject can be created from a Finished project. If the status of the report selected was I (In Progress), then any In Progress subprojects were not selected on the report. This issue has been rectified.


Line Number Sequence Issue with Subcontract/Supplier

Agreement

SDR: 57902

When entering subcontract agreement details, the user could change the sequence number to zero. Since the system uses sequence number zero for other purposes, the commitment of the project update process ignored this record. This issue has been rectified.


Able to Print Unapproved Agreements

SDR: 58132

Using the Subcontract Enquiry screen, any displayed unapproved subcontracts could be printed. This issue has been rectified.

Key Data Module/Function: PROJ E006

Timesheet Negative Entry Issue

SDR: 57200

When a timesheet is entered for hours which are greater than the normal working hours, overtime or time and a half charges are incurred. If these are reversed (using a negative time value on a timesheet), they are not correctly reversed in the Chargeout screen on the project. This issue has been rectified.


Claim Schedule Report Issue

SDR: 58060

The Completed to Date percentages for the Contracts and Variations pages were incorrect. This issue has been rectified.





Project at Status ‘C’ (Created) Cannot be Removed or

Edited

SDR: 58186

Projects with the status of Created will not be created if the user does not confirm the entry of the project, and existing projects with the status of Created with no details can be removed using the Remove mode in the Project Entry screen.


Create Project Quotation Issue

SDR: 58202

When printing the Project Sheet report at the conclusion of project quotation entry and the Full Details option is selected, the stock code description and notes were not printed. This issue has been rectified.





Purchase Orders

Shipment Create Issue

SDR: 54547

Foreign values in multiple purchase orders in a shipment are not being converted correctly to the local values. This issue has been rectified.


Purchase Order Not Updating Header Correctly

SDR: 56518

Audit Trail for the Purchase Orders screen should display all the status changes of the process order during its life cycle. This issue has been rectified.


Item Code Conversion Error

SDR: 56801

If costing is set up using Inwards Item Maintenance (INV.M417) and stock conversion is run, a duplicate error is generated. This issue has been rectified.


Purchase Order Return Allows Lot Quantity to Go

Negative

SDR:56992

When a return purchase order contains multiple lines of the same lot tracked item, the system only checks availability by lines. This results in more than available quantity to be allocated. When the order is updated, the warehouse on hand quantity of the lot tracked item can go negative. This issue has been rectified.


Goods Receipting Subcontract PO - Additional

Requirement

SDR: 57126

Prior to this change, PRONTO-Xi incorrectly reported subcontract variance when goods receipting a subcontract purchase order with additional requirement, manually linked to a work order route. This issue has been rectified.

Key Data Module/Function: PO M101 Major Function Flags:




- Production Costing Method = ‘0’ - Auto Create of Subcontract POs = ‘N’ - Auto Update of Subcontract Route = ‘Y’

Order Total Not Updating

SDR: 57165

When adding a positive charge line to a PO Return Order, the Order Total does not get updated. This issue has been rectified.


Incorrect Use by Date for Purchased Tracked Item

SDR: 57266

The use by date for a lot tracked item is not being refreshed and passed to a purchase tracked item during the Purchase Order update. Use by date only applies to lot/serialised tracked item. This issue has been rectified.


Big Item Price Incorrectly Multiplied by 100

SDR: 57314

A large item price entered in a purchase order line is multiplied by 100 and Unit is set to 100. This issue has been rectified.


Purchase Order Officer Limit Issue on Backorder

Maintenance

SDR: 57395

When a backorder is created during purchase order goods receiving, the system was not setting the stock and non-stock totals on the order header. This meant that a user with officer limits set at low levels, could actually add additional lines to the backorder which caused the order total to exceed the limits, but not to be set on approval required. This issue has been rectified.

Key Data Module/Function: PO M006 Table Entry: Purchasing Officer Limits set low

Purchase Order Update Issue

SDR: 57576

When an invoice is entered prior to goods receipt, and when part goods receiving the order, after updating it causes stock integrity errors. This issue has been rectified.

Key Data Module/Function: PO T029 Major Function Flags: Allow ‘on order’ invoicing = 1




Multiple GL Description Not Defaulting

SDR: 57768

When entering an S (Special) lines on a PO and using multiple GL Accounts, the text within the Special Note line used to default into the Transaction Description field on the multiple screen, but this is not happening now. This issue has been rectified.

Key Data Module/Function: PO M011 Major Function Flags: SYS.M063, Length of Note Line = 0/1

Warehouse Masking Not Functioning Correctly

SDR: 57848

When enquiring on a PO using the PO Enquiry by Item function, warehouse masking is not applied properly. You can access warehouses that you shouldn’t be able to access. This issue has been rectified.

Key Data Module/Function: PO E003

Contract Order Report Truncation Issue

SDR: 57870

The quantities on the report now print to 9 digits and the values to 11 digits.

Key Data Module/Function: PO R023

Purchase Order Cancellation Issue

SDR: 57925

A purchase order of type T (Contract) could be cancelled after an invoice had been raised. This issue has been rectified.


Subcontractor Order Maintenance Agreement Types

SDR: 57929

In the Subcontractor Order screen, only the purchase orders with agreement types R (Rates), L (Lump sum) or S (Supply) can be processed.


Incorrect Value Outputted by Field Code ‘CC’ in Totals

Section

SDR: 58000

This code should print the purchase order total (unconverted), for example, if total is foreign it should print as a foreign amount. During the tax conversions between R670 and R700, this was broken, and for some reason the total was converted to local currency, which is incorrect. This change removes the conversion and restores the way it used to work in R670.





Print Multiple Purchase Orders Fails

SDR: 58019

When trying to print multiple purchase orders using option M, an I/O error occurs. This issue has been rectified.


Contracts Order Report

SDR: 58083

The Total Received figure is now correct.


Can Print Unapproved Subcontract Agreement

SDR: 58122

A subcontractor agreement is created at an unapproved status. Lines are entered on the agreement. When finishing the line entry, the default option is to print the order regardless of whether the agreement is approved or not. This issue has been rectified.


Able to Print Unapproved Subcontract Agreements

SDR: 58141

In the Subcontractor Order Maintenance screen, it is possible to select Print for an unapproved Subcontractor order. This issue has been rectified.


UOM Not Set Correctly for Random Weight Item

SDR: 55509

For an item code with an issue control code set to 'W' (Random Weight). When goods are returned, besides entering the Return Qty, the user is allowed to change the corresponding Base Qty for the base UOM. The default value of this Base Qty is the total base UOM of total quantity return. This issue has been fixed.


Major Function Flags -Sales Order Entry/Edit Procedures -Initial Lines Mode = 'A'




Conversion Factor Set to Zero on Return Purchase Order

SDR: 56584

When returning stock on a PO Return, when you enter and accept a Reason code, the conversion factor is set to 0 (zero). This issue has been rectified now and the conversion factor will remain as it is.


Outside Work - Out Source WMS Assembly Orders

SDR: 58038


Purchase order raised for outside work was not created with a Firm Planned status, when the order total was below the supplier's minimum order amount.

WMS Order Processing was showing conflicting warehouse order statuses, even though the assembly process can be completed without error. With this change, WMS Order Processing will now show the appropriate sales order status for these orders.

Key Data Module/Function: SO M001, WHSE M064

Major Function Flags -Raise PO from SO != 0

System Error During Purchase Order Receiving Using RF

SDR: 58142

When the RF Receive Allow Accumulation major function flag is set to ‘Y’, and when the purchase receipting is concluded on the RF unit, a system error is generated. This issue has been rectified.

Key Data Module/Function: RF M002

Recost Of Shipment Posts Purchase Cost to IR and IV

Accounts

SDR: 58143

If standard cost is being used for an item and all purchased quantity of the item received using shipment are transferred to destination warehouse, the final recost of the shipment causes the cost of purchase to be posted to the IV account, the other side to the IR account. The average cost of the item is also changed in the destination warehouse. This issue has been rectified.





Quality Management System

Invoice Dispute Entry Issue

SDR: 57478

An error message was displayed when entering an Invoice Dispute. This issue has been rectified.


Actual Hours Incorrectly Populated

SDR: 57565

The Actual Hours were incorrectly populated when logging an enquiry and entering Resolution notes. This issue has been rectified.

Key Data Module/Function: MIS M009




Rental/Contract

Changing the Contract End Date with Options

SDR: 57509

Contract end date can be changed using the End Date option in the Extras menu of Rental Contracts. Having a lump sum charge is not affecting the end date change process. If the contract has a lump sum charge, this will be invoiced in the first invoice created for the contract.


Rental Contract Integrity Issue

SDR: 57601

Rental contract integrity was reporting a misleading error when a serial number had been sold on a sales order that was the same number as the rental contract being checked. The integrity now checks that the serial is not related to a sales order rather than the contact before reporting an issue.





Repairs Management

Repair Dockets Not Printing Repair Notes Correctly

SDR: 58086

The repair dockets should display the fault notes entered during the process of the repair order in full.

Key Data Module/Function: RPR M019




Sales Orders

B Type Credit Note Not Using Original Price

SDR: 56383

When processing a B type credit note, the original item price was not being used on the lines when you choose to use it. This issue has been rectified.

Key Data Module/Function: SO M001

Kit with Special Items Issue

SDR: 57009

When a sales order with kit item is created from a quotation and the kit item contains a special item, and if the sales order goes on backorder, special order line quantity becomes shipped instead of backordered. The order status changes to Ready for Picking instead of Backorder. This issue has been rectified.


Sales Order Charge Type Not Validated When ‘Charges

Split By’ = Blank

SDR: 57030

When the charges split by in Accounts Receivable major function flag is set to Blank, the charge type in the sales order line is not being validated when a selected type from the list is manually changed. This issue has been rectified.


RF Overship Without Reallocation Issue

SDR: 57068

This change corrected an issue with the inability to overship available stock from the same location.

Key Data Module/Function: WHSE.M014, WHSE.M013 Major Function Flags: -Must Scan Warehouse Locations = N -Reallocation = N -Allow Overshipment = Y

ScanPack Despatch Enhancement

SDR: 57089

ScanPack despatch has been enhanced to first ask for the sales order number or a box (SSCC) number to initiate the despatch process. Also, the carrier can be overridden if the user wants to use another carrier.





Returned Lot Cannot Be Released to Sales Order

SDR: 57199

When a credit note is issued using the return and re-invoice option for a tracked item, the lot is returned to stock but cannot be re-issued to the returning invoice. The lot is shown as a due out quantity and cannot be re-invoiced. This issue has been rectified.


Sales to PO Gross Profit UOM/Currency Issue

SDR: 57238

When the Raise P/Order from S/Order (SYS M326) major function flag is set to 6 and used for indent item with alternative unit of measure, gross profit shown is incorrect when creating a purchase order from a sales order. This issue has been rectified.

Key Data Module/Function: SO M002 Major Function Flags: SYS.M326, Raise P/Order from S/Order = 6

Credit Note for Manual Invoice

SDR: 57393

A credit note was raised for a manual invoice which contains General Ledger accounts not stock codes. When the credit note was updated, it attempted to update bin locations for non-existent stock, and failed. This issue has been rectified.


Cannot Amend Delivery Address for Sales Order

Quotation

SDR: 57454

For quotation type sales orders, the delivery address can be amended even after the header screen entry is completed.


Internal Item Issue Postings Not Showing Subledger

SDR: 57468

Subledger details will be now displayed in GL batch when an internal issue linked to a work order is posted.





Sales Representative Split Issue

SDR: 57549

With the Stop and Ask Flag set to 2, if no rep code is entered the user is prompted to enter multiple reps and percentage split. When the order was initially being entered, if the user exited from the percentage split screen without entering a rep, they were not prompted to enter a valid rep code. This issue has been rectified.

Key Data Module/Function: SO M001 Major Function Flags: Stop and Ask = 2

Cannot Reuse Serial Numbers in WMS RF Picking

SDR: 57579

With this change, RF picking process will allow for the de-duplication of existing serial numbers as in normal despatch.

Key Data Module/Function: WHSE M013 Major Function Flags: Serial Number Traceability = 1

Full Order Entry Issue

SDR: 57588

For COD customers, the status of the very first sales order was being set to Credit on Hold. This issue has been rectified.


Sales Order Update Issue

SDR: 57592

When performing a partial credit note to return stock to the inventory for a type 3 warehouse of lot tracked item, it causes inventory integrity. This issue has been rectified.


Sales Order Posting Period Not Showing Date Value

SDR: 57602

The Sales Order Enquiry was not showing the correct date value for Posting Period. This issue has been rectified.





Sales Order Delivery Address Update Issue

SDR: 57613

When a customer has multiple delivery addresses defined, a delivery address needs to be selected at order entry. With the Copy Delivery address flag set to Yes, the selected delivery address details are written to the sales order. If the delivery address details for the sales order are corrected using the Delivery Address Correct mode, the changed details were being updated to the DA delivery record and not the selected record.

If the Correct mode is used and there are multiple delivery address records for the customer, the customer record will not be updated. If the user selects the Other mode from the maintenance screen and then Correct mode when on the required delivery address record, both the customer and sales order details are updated.

Key Data Module/Function: SO M001 Major Function Flags: -SO - Delivery Add/Inst Permanent = YES -SO - Copy Del Add to Order = YES

Cost Not Displayed When Item Code is Entered

SDR: 57615

In Sales Order entry, the cost will now be displayed as soon as the item code is entered. This will help the user to see the profit of the item as soon as the item code is entered.


Tax Rate Being Calculated Incorrectly

SDR: 57616

When the customer type is changed in the Sales Order Edit option, the new stock codes entered will now pick up tax rates based on the updated customer type.


Batched SO Update - Transfer Orders Issue

SDR: 57619

Prior to this change, batched SO update with parameters -b -transfer was processing all orders, instead of transfer orders only. This issue has been rectified.

Recommendation: We recommend that the background process be submitted through the Application Services.

Key Data Module/Function: APPS M001




Work Order Link Screen Display Issue

SDR: 57630

The Sales Order to Work Order Link Enquiry screen was always displaying the link status description as Unknown. This issue has been rectified and the correct description is now displayed.


‘N’ Type Sales Order Line Not Displaying Item Code in

Screen Title

SDR: 57647

A sales order line created for a normal stock item and then corrected will now correctly display the item code along with the item description as the title of the SO line correction screen.


CRM Record Not Creating From Sales Order Entry

SDR: 57664

A new customer can be created while entering a sales order. If the CRM module is set up to create a CRM account when creating a customer, a CRM account should be created from sales order entry process after creating the new customer. This issue has been rectified.


Updating Purchased Tracked Item Issue

SDR: 57671

When updating sales orders that have Purchased tracked item in type 2 warehouse, the update process should not include due out quantity from a location that has already been allocated to another order. This issue has been rectified.


Sales Order Line Delete Not in Sequential Order

SDR: 57682

Removal of sales order lines in Maintenance is not in sequential order when the database is in Oracle. This issue has been rectified.





Reprint Sales Orders Issue

SDR: 57698

A customised version of m54custom did not have the spool file name returned and caused the program to crash.

Two calls to m54custom within the reprint program also did not expect the spool file name to be returned. This did not cause a problem, but the returns have been added as a precaution. This issue has been rectified.

Key Data Module/Function: SO R028 Major Function Flags: SO Procedures, Allow Future Dating = 3 (consolidated)

Sales Order Edit ABN Printing

SDR: 57702

When an EDI is setup using INVOIC document type to print the invoice electronically, the ABN number printed is per the following business rule:

If there is a setup of ABN number in the TC system table code. This ABN number is used first. If the TC system table code is not set up, the system will check the WH system table code for

the ABN number. If the WH system table code is not set up with ABN, PRONTO-Xi will take the ABN number from

the company table.


Own Box Option Issue

SDR: 57716

Prior to this change, PRONTO-Xi did not allow the manual selection of the own box option. This issue has been rectified.

Key Data Module/Function: WHSE M013, WHSE M014 Major Function Flags -Special Functions Allowed: Own Box = Y

Sales Order to Service Call Linkage Issue

SDR: 57717

Several Sales Order programs still assumed that the service-call-master.call-no field was still 6 numeric rather than 8. This issue has been rectified.

Key Data Module/Function: SO X001

Sales Order Update - Serial Details

SDR: 57735

Prior to this change, updating a sales order for a trade in of a serialised item was incorrectly updating the serial cost of the serial sold, with that of the serial returned. This issue has been rectified.




Key Data Module/Function: SO T017 Major Function Flags: -Cost to Use to Value Stock = T -Allow Negative Quantities = Y

Order Status Report Corrupting Selection Dates in Batch

Mode

SDR: 57748

The Sales Order Status report is corrupting any entered selection Date Ranges when run in Batch mode. This issue has been rectified.

Key Data Module/Function: SO R115

Available Credit During Order Entry Issue

SDR: 57801

The Available Credit amount did not display correctly if that figure was 8 digits or more. This issue has been rectified.


Sales Order Load from Flat File Issue

SDR: 57818

Sales orders generated from the sales order load program did not have any promotional discounts applied, if the item price was passed in the file. This has been changed to still use the passed price but to also capture any promotional off invoice or deferred discounts.

Key Data Module/Function: SO M068 Major Function Flags: -Price Search Include 16

Full Order Entry Issues

SDR: 57826

When in Correct mode, the Tally Window will be displayed to allow editing of the piece details. The note line will be correctly updated with the piece details of the current sales order line.


Tax Figures Not Correct in Sales Order Enquiry

SDR: 57891

When using Order level tax and wholesale pricing, some of the shipped values were not displaying the correct amount with regards to tax. This issue has been rectified.





Transfers Not Appearing in Non-WMS Screen

SDR: 57943

Transfer Sales Orders were not appearing in the Non-WMS Resource Transaction Maintenance screen when their processing had begun. This issue has been rectified and they can now be processed from this screen.


Consignment Note Number Field Size Increased

SDR: 57958

The maximum number of characters allowed for a consignment number is 10. You are now not permitted to enter more than 10 characters for a consignment note number.


WMS RF Despatch - Warehouse Transaction

SDR: 57967

With this change, a WMS order despatch via an RF unit will now have a DE warehouse transaction recorded, as in normal despatch.


Sales Order Edit of GL Coded Sales Orders

SDR: 57981

GL Coded Sales Orders for Labour and Specials (income) can be entered in [SO.M334]. These orders must be one or the other. They cannot have both labour and specials on the same order.

If the sales order contains specials, then transactions are written into the sales-order-gl-coding object. Should the user then use sales order edit, the system checks for entries in this object and, if found, does not display the [Tax Details] mode on the lines screen. In Correct mode, the user is able to enter/change the tax code on the specials screen.

The labour order would normally show the [Tax Details] mode on the lines edit screen. However, the user had removed the specials line in sales order edit and replaced it with a labour line and no [Tax Details] mode appeared on the screen.

This issue was caused by 2 things:

The decision on whether or not to display the mode is made in the sales order header program, based on the existence of the records in sales-order-gl-coding. The line edit screen cannot change what modes are shown part-way through processing.

The removal of the special line failed to also remove the sales-order-gl-coding records, so the system assumed that the order was for specials when it displayed the line edit screen, and the line edit screen assumed that the order was for labour (and that the [Tax Details] mode was present when correct mode was used.

This issue has been rectified, and the coding records are now removed if the special line is removed. However, the user will still have to complete the order and re-enter the lines edit screen for the [Tax Details] mode to appear. It is not good practice to change these types of orders in this manner once they are created. They are designed to be created, printed and updated in one process.





Catalogue Sales Updated to Wrong Period

SDR: 57996

When a sales order with a catalogue item is updated, the sales information is updated to the wrong period of the catalogue year in the data files deb-catalog-detail, deb-catalog-customer and deb-catalog-sales. Instead of using the catalogue month, it uses the financial period.

When a sales order is updated and split into a backorder, the full ordered amount will be updated to the three data files. But when the backorder is updated, the backorder amount will be added to the data files again. These will cause the ordered amount to be overstated.

The enquiry screens By Catalogue and By Catalogue/Item display sales information by financial periods instead of calendar months.

Exportable procedures have been added to allow customisation of catalogue periods. If the periods are customised, previously entered data must be converted to the new periods before customisation.


Sales Order Conclusion - Customer Required Date

SDR: 58032

A default of the current date has been added to the customer required date to allow for more streamlined data entry.

Key Data Module/Function: SO M001 Major Function Flags: SO conclusion: alter customer ref = 2

Enter Manual Invoices Issue

SDR: 58054

The process was attempting to limit the number of SN lines on the order when a project was involved. However, the total of SN lines was increased directly after entry of the account code rather than when the line was completed. Therefore, if you alter the account code half way through the line, the total was increased multiple times. This issue has been rectified.


Sales Order Edit Now Restricts GL Coding Sales Orders

SDR: 58056

The ability to modify orders created in GL Coding Sales Orders has been blocked in the Sales Order Edit function. These orders are not compatible with normal orders. If you want to change GL Coding Orders, you should use the Maintain Invoice Orders (AR M225) function instead.





Credit and Recharge Lines with Zero Amounts

SDR: 58063

When doing a credit and recharge credit note, where a new price was entered, the original invoice line had ZERO amounts. This issue has been rectified.


Project Codes Not Allowed in Invoice Entry

SDR: 58064

When entering a project-code.cost-category directly into the GL account in manual invoice entry, it was not allowed when you had GL masking set up. This issue has been rectified.


Manual Invoices Not Calculating Tax on Charges

SDR: 58097

Charge lines did not have their tax amounts calculated correctly. This issue has been rectified.


Project Orders on Backorder Losing Their Quantities

SDR: 58108

Orders created from a project material requisition that were on backorder were losing their ordered/backordered quantities when viewed through Manual Invoices. This issue has been rectified.


GL Batch Not Balanced When Tax at Order Level

SDR: 58112


When tax is applied at order level of a foreign normal sales order or a multi-project invoice, rounding in the posted tax amounts results in unbalanced GL batch.

The local invoiced amount of customer transaction has added the tax amount twice.





Unable to Despatch Orders

SDR: 58117

Orders for type 3 (WMS Controlled) warehouses were unable to be despatched without manually entering zone cartons. This issue has been rectified.


Sales Order Invoice Reprinting

SDR: 58121

When tax is calculated at the order level, the line tax inclusive and exclusive amounts were inconsistent between invoice print and invoice reprint. This issue has been rectified.


Charge Line Can Be Entered in Multi-Project Invoicing

SDR: 58128

Charge lines can be entered even though a project line exists. This results in unbalanced GL batch when the sales order is updated. This issue has been rectified.


Full Invoice Entry - GL Coding Sales Orders

SDR: 58130

GL coding sales orders are stock code based orders. The tax code for the stock code should be maintained via the Tax Default and Exemption Maintenance screen. Alternatively, the user could modify the tax code using the Tax Detail mode. The Tax Code prompt is now disabled.


Invoice Exclusion Not Working in Daily Sales Report

SDR: 58092

Option to exclude invoices generated within service was not excluding all sources. This issue has been rectified.


Descriptions Truncated in Sales History Report

SDR: 57971

When creating a custom report using the Custom Sales History report, the descriptions were being truncated if they were too long. This issue has been rectified.




Key Data Module/Function: SALE R070

Order Status Report Issue

SDR: 58137

The report was not filtering correctly on customer name when a status was entered. This issue has been fixed


Kit Item Price Incorrect After Quantity Change

SDR: 55885

When a sales order is raised with a kit item in sales order line for a customer with GST exemption code attached, the kit price does not adjust correctly when the kit line shipped quantity changes. This issue has been rectified.


Missing Columns in Sales Order Archived Enquiry

SDR: 57736

The new columns Order Unit Ex Tax and Order Unit Per Ex Tax were missing in Sales Order Enquiry and Archived. This issue has been rectified.


Archived Order Enquiry Date Filter Issue

SDR: 58029

When enquiring on archived orders, the date range filter will be considered when an item number is entered as one of the parameters. The date range will be used to display the orders to filter the orders according to the processing date range.


Changes Not Saved When Exiting Delivery Address

Screen

SDR: 58127

If a customer had a DA and numeral type address record, ie 01 - 09, then escaping from the Delivery Address screen did not save the DA details. This issue has been rectified.





Less Than Min GP Message Incorrect for Labour Items

SDR: 58176

When entering an item in a sales order, if the gross profit of the order is less than the minimum gross profit set up for the system, a warning message will displayed to let the user know. This is the same as labour type items as well.


Posting Issue with General Terms Rebates in Sales Order

Update

SDR: 58222

Sales order general terms rebates were not always posting. This occurred if there happens to be another promotion with a zero end date for the same customer and item code, and the promotion is on hold. This issue has been resolved.


Major Function Flags - Level of customer rebates = 2 or 3




Service

‘In-Stock’ Serials Not Prompting for Customer

SDR: 56893

When logging calls, serial items with status In Stock should prompt for customer entry, because the Customer field is not auto filled. But Customer entry is not prompted. This issue has been rectified.


Page Number Truncated in Sales History Report

SDR: 57040

When you create a Custom Sales History report the page number is pushed off the side of the report and not shown if your company name takes up more than 38 characters. This issue has been rectified.

Key Data Module/Function: SALE R070

Contract Maintenance Pricing Issue

SDR: 57327

For the equipment pricing, if the RRP value is set to zero, the Price column value will be regarded as a dollar value. If the RRP value is set to non-zero, the Price column value will be regarded as a percentage and used as a percentage of the RRP value to calculate the contract rate.


Issue Editing Multiple Serial Items on Service Call

SDR: 57558

It has long been possible to define multiple serial items on a single service call but once entered, there was no way of editing the list of serial items originally selected.

A new drilldown button has been added alongside the Quantity field on the Service Call Maintenance screen, which will open the list of selected serial items. This screen allows the list to be modified. After exiting this screen, you are prompted whether to change the quantity on the service call to match the number of serials now in the list. This is optional.


Service Call Fault Lines Issue

SDR: 57612

The first line of a Fault note was being duplicated if the lines were being resequenced. This issue has been rectified.





Service Call Parts Not Charged on Invoice

SDR: 57641

Service call type can be set up with charge for parts set to N. Then the material issues will not be charged against the call. The application does not show zero cost material lines in the sales docket if the above flag set to N. But customers would like to see material issues with zero cost.

To do that, the above flag can be used but you also need to modify the public procedure public-modify-job-cost-trans to pass correct values. If the user does not want to print zero cost material lines, the above flag has to set to D.

Key Data Module/Function: SERV T003

Sales Order for PM Calls Issue

SDR: 57643

The sales order produced for a finished PM Call had incorrect values for the item group for the second and subsequent sales order lines. This issue has been rectified.


Cannot Print Quotation for an Arrear Billing Contract

SDR: 57650

Quotation of an arrear billing service contract at Entered status cannot be printed using the Extra > Print Quotation mode. This issue has been rectified.


Miscellaneous Minor Enhancements to Service Module

SDR: 57656

The following minor enhancements have been implemented:

Completed PM Calls

Within the Contract Maintenance (SERV M118) function, the Open PM Dockets option now has a new mode called Completed PM Calls which allows access to any completed PM Calls/Dockets for the current contract.

Attached Projects

Within the Project Maintenance (PROJ M117) function, the Attached option has new fields on the data grid including dates, etc. of the attached projects/project calls.

Engineer Lookup

The Engineer lookup screen, which is located in several places such as the Engineer Allocation (SERV M017) function, has been changed to allow the Skill and Territory codes as sortable and filterable columns on the data grid.

Key Data Module/Function: SERV X001




Service Call Received Date / Time

SDR: 57793

Both the Service Call Log Call and Wizard screens now allow for the Received Date and Time to be altered during the entry process. These 2 fields could always be changed using the maintenance screen and can be defined during the Service Call creation processes.


Duplicate Sequence Numbers on Units

SDR: 57804

When adding a serial unit to a service contract, the sequence number of the new unit cannot be the same as an existing sequence number already added to the contract. This issue has been rectified.


Field Named Incorrectly in Selective Call Screens

SDR: 57854

The Fault filter is the filter for resolution codes. This can be seen by the table displayed when selecting the help. The display has been renamed to Resolution.


Service Lost Contracts Report Issue

SDR: 57865

This report was not selecting Contracts that had been marked as Lost but had not been archived. This issue has been rectified. The Service Contract program Purge/Archive Contracts now prompts whether lost contracts should be purged.

Key Data Module/Function: CNRT M003

Workshop Repair Enquiry Unknown Message

SDR: 57869

From Workshop Repair Enquiry screen, if you select the Service mode, an erroneous message appears and nothing else happens. This issue has been rectified.


Service Call Cancellation Issue

SDR: 57872

Scheduled times were not being cleared when a call was cancelled. This issue has been rectified.





Can Print General Notes in Call Maintenance Entry

SDR: 57886

The Print option when entering a General Note was not available. This issue has been rectified.


Full Credit Contract Invoice Has No Amount

SDR: 57948

Service Contract Credit for Full amount with re-invoice required produces zero value credit. This issue has been rectified.


Incorrect Note Type for Schedule Notes

SDR: 57963

The correct service contract note type is now set for the Schedule notes.


Call Info Mode Causing I/O Error in Allocation Screen

SDR: 57966

An I/O error occurred if the user exited from the Engineer Allocation screen, selected the Call Info mode and then exited from that screen. This issue has been rectified.


Missing Fields in Lost Contract Report

SDR: 58011

The Contract Number and Reference have been added to this report.

Key Data Module/Function: SERV R081

Territory Not Displayed in Service-Engineers for Service

Territory Screen

SDR: 58070

This screen now displays the territory selected. The territory and skill columns in the Engineers for Service Centre screen are now sortable, filterable, and so on.





PDA Showing Incorrect Required Date

SDR: 56874

When a service call is logged it populates the Date Required field with what the user enters, or it defaults to. Then engineer/engineers are allocated and the allocated Date Required can be specified for a different day/times. When the engineer notified via messages to the PDA with call details, they received call-required-date-time instead of engineer-required-date-time. This issue has been rectified.

Key Data Module/Function: MSRV T001

No Replenishment Warehouse Range With F2 (Lookup)

SDR: 58007

In the Add Lines mode of Warehouse Replenishment, use F2 to look up the warehouse table (WH) and select the Start and End Warehouse, and execute. The results returned are only for the End Warehouse. If the same process is run with the warehouse range manually entered, the results contain records for multiple warehouses. This issue has been rectified.


Incorrect Default Telephone Number in Call Logging

SDR: 58120

The telephone number now defaults from the Customer Maintenance screen and not from the Delivery Address record.


Log Calls Issue

SDR: 58190

When logging calls, the unit item entered should not be cleared when TBA or Non Serialized is entered at the Serial No. prompt. This issue has been rectified.


Contract Keywords Not Updated Automatically

SDR: 58217

Service contract uses the contract-key-words table. If a keyword is changed on the contract this should change automatically on the keywords table, which was not happening. This issue has been rectified.





Task Intelligence

Tasks Not Running in Correct Environment

SDR: 54071

When running a task in one company, for another company, any associated reports that are created are not always created in the correct report directory. This issue has been rectified.

Key Data Module/Function: TI M004




TrueForm

TrueForm Print Preview - Default Reader Adobe Acrobat

SDR: 58048

A change has been made to remove the error message displayed once a previewed document has been closed using TrueForm print preview.

Key Data Module/Function: TFD E001

TrueForm Documents Not Previewing Correct Project

SDR: 57714

If different TrueForm document/projects used the same layout code, the preview was not working. This issue has been rectified. To achieve this, each layout/source/type combination must have a unique report name.

Key Data Module/Function: TFD E001

Address Conversion Entries Issue

SDR: 58131

FaxMail contact document mapping can have account codes which may have been deleted from the Accounts Receivable module. Under these circumstances, when an address conversion is done using the Faxmail to TrueForm Conversion (TFM M002) function, duplicate entries were created in the FaxMail Document Address Mapping option. This issue has been rectified.

Key Data Module/Function: TFM M002




Warehouse Management System

Warehouse Audit Report Issue

SDR: 57631

Pre-pick warehouse transactions were printing with the From and To location reversed. This issue has been rectified.

Key Data Module/Function: WHSE R012 Major Function Flags: -Pick from Bulk = NO -Emergency Replenishments = YES

References Truncated in RF Inventory

SDR: 57817

When you do a transfer in WMS RF, the reference in the selection window is truncated. The full length of the reference is 20 characters. This issue has been rectified.

Key Data Module/Function: WHSE M012

Putaway Record Not Cleared for QA Lot-Tracked Item

SDR: 57857

When a QA lot tracked item is received into a type 3 warehouse via RF PO Receipt, it results in a putaway record (location 00000000) not getting cleared after the final replenishment process is completed. This issue has been rectified.

Key Data Module/Function: RF M001

Cannot Putaway QA Item in Type 2 or 3 Warehouse Using

RF

SDR: 57934

When an item with condition Q for QA Hold is received into a type 2 or 3 warehouse, it cannot be putaway using an RF gun and an error Nothing to Putaway message is displayed. This issue has been rectified.

Key Data Module/Function: WHSE T002

Service Level Report Not Showing Correct Quantities

SDR: 57860

When reporting on items with different units of measure, the pick quantities being displayed were not correct. This issue has been fixed.

Key Data Module/Function: WHSE R023




System Administration

Maintain GL Masking Issue

SDR: 57688

If you had companies set up with the environment SYSGLDATA set (shared GL) and some companies not shared, there was a problem if you tried to change the GL masking of a non-shared company, or vice versa. When removing a company from a user, the system was also removing the GL Masking even if the user had access to another company with the same shared GL. This issue has been rectified.


Standard Message Code Issue

SDR: 57705

When entering a new code and description, the text field was displaying the text from the previous code. This issue has been rectified.

Note: Use the Notes mode to enter text for the new code.


Reporting Capabilities - Bulk Users Additions

SDR: 57811

Replaced the All mode for multiple user additions to a single capability, with the Bulk mode, which allows multiple user additions over a range of capabilities and gives greater flexibility.


Reporting Capability - Group Temporary Licencing

SDR: 57812

Temporary licences are now available for reporting capabilities. When new users are added, permanent licences are used first. New users above the allowable permanent licences are added as temporary licences. There may be multiple temporary licences for the same capability, each with a different expiry dates. Users that were added a temporary licence can be exchanged for a permanent licence [SYS M168] > Temp/Perm mode. Users that have had the licence expired can have their licence reactivated using the Expired mode but a licenced user will have to be removed to accommodate this.


Masking Based Session Parameters for Cognos

SDR: 57859

The changes in Cognos model (SDR 57949) make masking optional for those customers who do not use masking.





Upgrade Issue- Cognos Synonyms Not In Shared GL Area

SDR: 57923

When upgrade occurs for a company, the SYSGLPATH environment is checked to check if they have a standalone GL. If no GL exists, the Cognos synonyms must be created. A problem occurred when SYSGLPATH was set to ‘.’. The synonyms were incorrectly created. A change has been made to ensure the synonyms are ignored in this instance.

Upgrade View Creation

SDR: 58085

Handle creation of the gl-chart-of-accounts synonym if a Shared GL Data area is in use and the Shared GL Data area is not actually a company.


Additional System Upgrade Function Added

SDR: 58149

A conversion procedure has been added to convert service-link object of field 'call-link-ref-no' to left-justify.

Key Data Module/Function: System Upgrade Function




Component Libraries

Public Exportable Procedure for Calculating Available

Stock

SDR: 56687

A public exportable procedure has been added to the standard available stock calculation program. This allows the customer to change the available stock for an item after it has been calculated in the standard way.


Public Exportable Procedure for Controlling Company

List

SDR: 57694

The new procedure public-determine-if-company-to-be-shown has been added to the bms/bmsmenu.spl program to allow programmers to determine if a company needs to be shown in the company selection list based on custom logic.


Public Exportable Procedure for Inventory Price

Recalculation

SDR: 57224

The price recalculation has always updated the promotional prices on the stock item since inception. This does not suit some users.

An exportable procedure has been added to the program, called public-update-promotion-and-rrp-flags. The core offering sets 3 flags to TRUE:

Update promotion prices Update Recommended Retail price Update RRP including tax

The core program will update all these prices as well as the level break prices. If the user does not want the recalculation to affect one or all of these prices, they can create a customised version of the program, and set the required field/s to FALSE.


Public Exportable Procedure for Overriding Label Print

Quantity

SDR: 57782

A public exportable procedure, public-override-label-quantity-v2, has been added to the stk/m42stklab.spl program to allow programmers to override label print quantity.





Public Exportable Procedure for Purchase Order Update

SDR: 58013

A public exportable procedure, public-exclude-po-from-bulk-update-by-status, has been added that allows purchase orders of a particular status to be excluded during bulk updating of purchase orders.


Public Exportable Procedures for Quality Management

System

SDR: 57587

Added public exportable procedures for the following purposes:

Allow override of the call to the keyword entry screen during the complaint entry process. This screen is not always required as a part of this process.

Allow override of the setting of the status of a complaint when all problem logs associated with that complaint have been rectified to allow the user to leave the complaint open in this circumstance.


Public Exportable Procedure for Custom Call Allocation

SDR: 57673

A public exportable procedure, public-allocate-engineer, has been added to the service/s10engallo.spl program to enable custom allocation of an engineer to a call.


Public Exportable Procedure for Foreign Currency Date

SDR: 57778

The default setting of the Change Date for the system currency history as today() was 1 day. This procedure allows you to select any date you want to set for this Change Date of currency history.


Public Exportable Procedure for Invoice Variance

Screen

SDR: 57781

Added a public exportable procedure called public-after-ask-po-edit-or-continue to sys/m81fastci.spl. This can be used to enable customisation to stop the user from exiting the Invoice Variance screen without entering a value in the Action field.





Public Exportable Procedure for WMS ScanPack

SDR: 57965

A public exportable procedure, public-pre-serial-validation, has been added to allow for custom requirements, prior to standard serialised item’s validation. An example would be to trap operator error and prevent incorrect scanning of bin location when a serial number is expected.

Key Data Module/Function: WHSE M013 Major Function Flag: Serial Number Traceability = 1

Public Exportable Procedure for Employee Conversion

Program

SDR: 57763

A new public exportable procedure has been added to the detail of the Employee Conversion program that can be used to convert custom and other tables for an employee that is having their employee number changed.


Public Exportable Procedure for Repair Orders

SDR: 56777

A public exportable procedure has been added to allow user flexibility to use the supplier’s price for the item entered or REPAIR QUOTE item.

Key Data Module/Function: RPR M019

Public Exportable Procedure for Project Timesheet

Posting

SDR: 57874

A new public exportable procedure, public-set-jc-trans-amount, has been added to the timesheet posting program at the point the program is determining the amount for the resultant project transaction.

This procedure is passed various entire records (such as the employee, project, timesheet record, and so on) as well as other fields and flags which PRONTO-Xi has used to determine the transaction amount. This procedure is also passed the transaction amount that PRONTO-Xi has derived.

This procedure can be used to override this amount if required based on customer/business logic.


Public Exportable Procedure for Sales Order Conclusion

SDR: 58006

A public exportable procedure, public-pre-status-unlocked, to enable customisation and modification of sales order details. If changes were made to the order the totals displayed did not reflect this. The totals are now redisplayed after the public exportable procedure has been called.





Public Exportable Procedure for Scale Factor

SDR: 57978

A public exportable procedure has been added to cater for the extra scale factors.

Public Exportable Procedure for Overdue

Customers/Charge Interest

SDR: 56803

A misunderstanding has been documented as to how this program works. It was designed to be run in the NIGHT sequence on a daily basis similar to the ageing process for weekly accounts. Therefore, it ignores the current ledger period, and performs ageing based on today’s date.

As an add-on to this, the Overdue Customers Report also ignores the current ledger period, and bases the comparison on the invoice due date against today’s date. This is the standard functionality, and the user manual will be changed to reflect this method.

However, we have now added a new public exportable procedure called public-get-comparison-date, which will allow the user to change the comparison date. Be aware of the consequences of changing the comparison date if you are running NIGHTLY sequence to print this report for weekly accounts.


Public Exportable Procedures for Preventative

Maintenance Scheduling

SDR: 57704

The following public exportable procedures have been added to the program service/s14schedpm.spl:

public-check-insert-summary-pm-call: allows programmers to determine if a particular summary PM procedure should have a PM call raised for it.

public-check-insert-detailed-pm-call: allows programmers to determine if a particular detailed PM procedure should have a PM call raised for it.

public-check-insert-call: allows programmers to determine if a particular PM procedure should have a call raised for it, and take other action if not (for example adding the piece of equipment to an existing call).

public-after-insert-call: allows programmers to do extra processing after creating a service call.


Public Exportable Procedures for PM Run Report

SDR: 57783

The following public exportable procedures have been added to the program service/s82pmrun.spl:

public-new-page-for-site: allows programmers to optionally start a new page after each site. public-print-text-filename: allows programmers to print additional text on the PM run report

using a flat file.




Key Data Module/Function: SERV R009

Public Exportable Procedure for GL Consolidation

SDR: 58228

A public exportable procedure has been added to allow the custom masking of the GL account code.

Key Data Module/Function: GL T020

Additional Calling Parameters for Cash Receipt - Load

Data into System

SDR: 57882

Previously this loading program returned two values. The following two additional return values have been added:

return value number 3 - additional message for G/L Batch Failed. return value number 4 - additional message for G/L Batch Failed.

Additional Calling Methods for Customer Maintenance

Licence Screen

SDR: 58124

Calling methods have been added to the licence screens to allow them to be called from custom programs or triggers.

These methods require security AR E001 or AR M001.


User-Definable Fields Added to Despatch/Delivered

Edit/Confirm

SDR: 57610

The following Screen Customiser user-definable fields have been added to the Despatch Details (get-rest-of-header-info) screen in the Despatch/Delivered Edit/Confirm (SO M287) function:

so-user-only-date1 so-user-only-date2 so-user-only-alpha20-1 so-user-only-alpha20-2 so-user-only-alpha4-1 so-user-only-alpha4-2 so-user-only-alpha4-3 so-user-only-alpha4-4 so-user-only-num1 so-user-only-num2 so-user-only-num3 so-user-only-num4
