Pronto Release - Notes - 670 - 6
Pronto Release - Notes - 670 - 6
Pronto Release - Notes - 670 - 6
Version 670.6
TABLE OF CONTENTS
MAJOR CHANGES .......................................................................................................... 10
NEW ZEALAND TAX CHANGES ...................................................................................................... 10
“ASK W AREHOUSE BEFORE P/O#” MAJOR FUNCTION FLAG RETIRED ............................................. 11
MESSAGE BUS ENHANCEMENTS ................................................................................................... 11
PRONTO ENTERPRISE MANAGEMENT SYSTEM ........................................................ 12
CLIB100-FILL-A-CELL ROUTINE LIMITED TO 80 CHARACTERS .......................................................... 12
The appropriate action you need to take will be determined by how your version of PRONTO-Xi has been
configured for tax.
Select Administration > System Administration > Table Maintenance Menu > Tax Information (SYS
M157)
What letter is in the field Tax Type…..?
If the Tax Type
field is set to:
G You will need to update to the latest release:
Clients on 670.x versions will need to update to 670.6
Clients on 660.x versions will need to update to 660.9
Once updated to the latest release, you must make certain changes to PRONTO-Xi.
L Clients on 660 versions and 670 versions with tax type „L‟ will not need to update to the
latest version of PRONTO-Xi, but will need to install one or both of the following SMR‟s
before making any change to the rate of GST.
SMR 55494 – reprice sales orders .
SMR 55529 – POS refunds (for POS sites only)
In addition, clients with tax type „L‟ will need to make further changes, in a specific
sequence, to ensure their PRONTO-Xi handles the new rate of NZ GST appropriately.
Pronto Support has created clear and concise documents that detail the necessary changes to remain
compliant with the new NZ GST rate. To obtain these documents, please click on the following link:
http://kbase.pronto.com.au/intranet/documents/725/6037/NZ_GST_Summary.pdf
If you have any questions regarding PRONTO-Xi and the changes to the New Zealand GST rate effective 1st
October 2010, please contact your Local Pronto Support Centre.
A PMB Status Enquiry (MSG E001) function has been added that shows the current status of all
publisher-subscriber relationships based on communication availability, the last message created, the
last message sent and the last message acknowledged. The status enquiry screen utilises colour
coding to readily highlight exceptions that require further investigation.
An option to „retire‟ a subscriber that is no longer required to receive messages has been included on
the PMB Status Enquiry screen. This sets the status of the subscriber to „Inactive‟ in the PMB Entities
table and performs the necessary housekeeping operations within the Message Bus system, in
particular to remove no longer relevant records from the message queue tables.
To streamline the process of setting up the message bus on the publisher and subscriber machines,
and to reduce the likelihood of setup errors, a PMB Setup Wizard (MSG M015) function has been
developed. The Setup Wizard guides the administrator through the three stages of message bus
configuration: 1) Configuring the publisher machine, 2) Generating and sending the remote setup
package for the subscriber machine, 3) Loading the remote setup package on the subscriber
machine.
If a subscriber PC at a store is restarted by pressing the reset button, it is possible for the message
bus related application services to be placed in suspend mode thereby preventing further data being
received and/or acknowledged by the store. This issue has been resolved by the addition of a
„-pgm-reset‟ calling parameter to the „appservices‟ program (Application Services daemon/service)
that prevents the suspending of application services in the situation described above. To enable this
feature, the specified calling parameter should be added to the Windows scheduled task that has
been set up to start the Application Services service (refer to the „Automatically Starting the
Application Services Daemon‟ topic in the Application Services manual).
The logic relating to the deletion of acknowledged messages on the publisher machine has been
changed. Previously, a published message was marked as being acknowledged (by setting a field
value to „1‟) when an acknowledgment was received from the subscriber. This record was retained
until all subscribers had acknowledged the message and the minimum archive period had expired.
During periods of communication difficulties with particular subscribers, this could lead to an
accumulation of records in the subscriber message queue table and a reduction in overall
performance of the message bus system. To improve performance, when an acknowledgement is
received for a message, the corresponding record in the subscriber message queue is now deleted
immediately.
Each item of data to be published is written to an XML file in a configured directory. For high
transaction volume systems, this could lead to system performance issues if a very large number of
files accumulate in this single directory. The file generation logic has been enhanced to support the
automatic distribution of files between multiple subdirectories, thereby avoiding too many files being
created in a single directory. This feature is automatically enabled when the environment variable
PROMQFILEDIR is set. When this environment variable is not set (which is not recommended), all
files are written to the $DATADIR directory without the use of subdirectories.
Size of parameter field lp-text is clib100-fill-a-cell procedure increased to handle external calls to the routine
efficiently.
Accounts Payable
The cheque layout description can now be edited using the Correct mode.
Key Data
Module/Function: SYS M383
When an invoice was authorised and allocated to a project, the general ledger transaction did not have the
special account populated with JC.category. Because this field was empty, the mode [Project] did not
function to drill down to the project. This has been rectified and the field is now populated.
Key Data
Module/Function: AP T037
Major Function Flags
-Accts Payable Authorise Invoice = 1
In the Selective Invoice Payment program, if the „Supplier„ mode is used to add a new supplier, and an
existing supplier is entered, this duplicated the entries on screen. This issue has been rectified.
Key Data
Module/Function: AP T003
In Manual Cash Payment, when a foreign bank is selected and local charges are entered, a transaction of
type „JE‟ was written and was not visible when reconciling the local bank. This issue has been rectified by
now writing a type „J‟ transaction for the Bank Reconciliation.
Key Data
Module/Function: AP T034
In V670 the [Help] key on the Invoice No. field was restricted to certain transaction types as it was felt that it
was only applicable to searching for an invoice when entering credits. However, some users had found other
valid reasons for wishing to use [Help] on eg an "I" type entry, so the restriction has been removed, and the
[Help] can again be used on any transaction type.
Key Data
Module/Function: AP T020
When using the Print/Update Remittance/Cheque function, you can set a default on the Print Direct field.
However, if you access this screen from Selective Invoice Payment, this field default does not work. This
problem has been resolved now with a slight appearance change in the screen.
Key Data
Module/Function: AP T041
When GL accounts have more than 10 characters, it was not possible to cancel a cheque and the error
message „Account not valid‟ was displayed. This issue has been rectified.
Key Data
Module/Function: AP T038
When using the Auto Select Payment by Dates, if there is no data loaded onto the screen, the „Select‟ and
„DeSelect‟ buttons cause the program to error when selected. This issue has been rectified.
Key Data
Module/Function: AP M013
The Suppliers Integrity program generated a report even when there were no errors found to report on. This
does not happen in other integrity programs. The program was modified so that the report is only generated if
an error is found.
Key Data
Module/Function: AP M041
The „T‟ attribute on field in the remittance section of the cheque layout does not allow the user to select the
F2 lookup available on other fields. This F2 lookup is only available for Field Code „C‟ as it is a reference field
and those attributes are meant to be used for reference fields and not for amounts fields. However, system
will now allow to use the thousand separator attribute, which is „T‟, for all the amount field codes other than
discount amounts.
Key Data
Module/Function: SYS M383
The Unpresented Cheque Listing report ignores the cheque number filter and reports all cheques for the date
selected. This issue has been rectified.
Key Data
Module/Function: AP R002
When a „P‟ type invoice was entered for multiple purchase orders with zero cost, multiple variance orders
were created for the change of prices. If the invoice was then cancelled, only the first variance order was
deleted. The other variance orders remained in the system. This issue has been rectified.
Key Data
Module/Function: AP T020
When you use the F2 lookup on the Levies/ Volume field in „Maintain Supplier Accounts‟, the table that
appears has the heading „Settlement Discount Codes - CJ‟ which is wrong. This issue has been rectified to
show the heading as „Volume Rebate Codes - CJ‟.
Key Data
Module/Function: AP M001
When the Print Trans Notes report option is set to „Y‟, the credit limit and description are printed. However, it
was not using the same code to find the details as other programs. The code in this program was replaced
with i1crlimit include, so all programs are now consistent.
Key Data
Module/Function: AR R020
There is a table that stores the totals of current orders (unpaid) and disputed invoices for each customer.
These details show on the Customer‟s Credit Limit Balance screen along with an available credit limit.
If a customer has data in this table, and the credit limit on the account is set to zero (COD), the integrity does
not check the table to see if the totals are correct, as it is assumed that a COD account does not have unpaid
orders.
However, this means that after the account is paid, if the customer is left as COD, the totals in the table are
not updated and the Credit Limit Balance screen shows the customer as "Exceeded" their limit, even though
this is not the case.
The integrity has been modified to ensure that COD accounts are also checked to rectify this problem.
Key Data
Module/Function: AR M176
When processing the “Overdue Customers Charge Interest” report and selecting option „S‟ to create sales
orders, the tax component was not being calculated. This issue has been rectified.
Key Data
Module/Function: AR T050
Using the table payroll-employee-master in a scheduled event caused a failure in the event generation
(compile fails).This issue has been rectified.
Key Data
Module/Function: AI M001
An Alert Intelligence event is created and pointed to an external program. The external program has multiple
parameters. When the parameters are picked using the field picker, and the alert is activated, an error is
returned stating that there are an incorrect number of parameters. This issue has been rectified.
Key Data
Module/Function: AI M001
When a scheduled event is submitted to a batch queue, a batch queue entry is created with the following
parameters:
1. "-scheduled"
2 <name-of-object-being-submitted>
3. AI event number, or SPACES for all scheduled events for this object.
The scheduled event did not run when the name of the object was longer than 25 characters. This issue has
been rectified.
Key Data
Module/Function: SYS M175
Unable to perform a manual join between the core dictionary and the custom dictionary. The error message -
"ERROR: Table does not exist" was displayed. This issue has been rectified.
Key Data
Module/Function: AI M005
The „Avail‟ mode in the Work Order Maintenance screen always shows components as having zero on hand
quantity, even when there are non-zero on hand quantities for the components. This issue has been rectified.
Key Data
Module/Function: MANU M073
With this change, the entry of an override component warehouse on a bill of materials line will now be
validated for all line types.
Key Data
Module/Function: INV M151
A message is given after generating the report that there is no report created. This issue has been rectified.
Key Data
Module/Function: MANU R032
1. The process of loading work orders was creating suborders, but not reporting the suborders.
2. Suborders created as a result of a sale were not recording the sales order/work order link for suborders.
Key Data
Module/Function: MANU M021
Major Function Flags
-Load Work Order by Factory = „Y‟
This change corrected the recording of an incorrect lot number for a lot tracked finished item, when
production is made using a RF unit.
Key Data
Module/Function: MANU M001, M002, M004, M006, M010, M011
Major Function Flags
-Batch/Lot Reference Format = „3‟
When a firm planned work order raised for a sales order line is partially committed, a second work order will
be created for the committed quantity. This results in two work orders linked to the same sales order line. If
some quantities of the second work order are produced for the first time, then the backordered quantity of the
sales order will be split into a suffix order. But if some more quantities are produced, the suffix order was not
created for the second production. This issue has been rectified.
Key Data
Module/Function: MANU T001
This change corrected an issue with reversing a quantity already put away in a WMS pallet tracking
warehouse for non-lot tracked finished item.
When the finished item has not been putaway, production reversal will offset the quantity in the inwards
holding location for the work order. But if the item has already been putaway, PRONTO-Xi will now create an
entry in the inwards holding return location, for manual allocation, for the quantity reversed.
Key Data
Module/Function: MANU M043, M044, M045, T014
Major Function Flags
-WMS Pallet Tracking Required = „Y‟
This change corrected an issue with RF putaway of production reversal from a WMS warehouse, when the
finished item has already been putaway.
Key Data
Module/Function: WHSE T002
Major Function Flags
-WMS Pallet Tickets Required for Manual
-Stock Putaway = „Y‟
-, WMS Pallet Tracking Required = „Y‟
This change corrected an issue with the display of work orders linked to a selected document type and
document number.
Key Data
Module/Function: MANU E005
The Sales order number is being truncated on the work order status report. This has now been resolved.
Key Data
Module/Function: MANU R006
When there are no production dockets for the entered date range on the factory, the report failed. This issue
has been rectified.
Key Data
Module/Function: MANU R012
If the work order is raised to use a BOM that has a revision code, the Release Firm Planned Orders report
did not check the shortage base on the correct BOM revision, and then returned a no shortage status. This
issue has been rectified.
Key Data
Module/Function: MANU R021
Editing an Attribute, selecting Help, then escaping, temporarily blanked out the value. This has been rectified.
Key Data
Module/Function: CRM M001
A new parameter „-no-console‟ has been added to the calling methods for the crm/crmmaint program to
enable the setting for the „Use CRM Console‟ user preference to be ignored.
Key Data
Module/Function: CRM M006
When editing CRM full name and address details (non-console) and the F2 search tool is used in the parent
field - if nothing is selected and the user escapes, the value is cleared. This issue has been rectified.
Key Data
Module/Function: CRM M001
The street address was not being passed correctly to Google maps. This has been rectified.
Key Data
Module/Function: CRM M047
A user with access to only enquire on CRM data was able to maintain CRM data. Also, three additional
security checks for maintenance of Activities, Transactions and Notes have been added. If not specifically
defined, the maintenance of this data will not change.
Key Data
Module/Function: CRM E001
Two new modes have been added to the Review Opportunity Orders screen to enable copying and editing.
Key Data
Module/Function: CRM M001
Public Exportable Procedures Added for Contact Sync and Mail Merge
SDR:55107
Two new public export components have been added to allow improved control and crafting of CRM
functions for sites. Details of these new procedures can be found in the SDK under the following
module/program names
Several new procedures have been added to allow control over which CRM accounts are sync‟d and
additionally how accounts that are not directly related to the login rep-code are handled. These procedures
New procedures here allow for the mail merge to write a transaction against each account processed. The
content of the transaction can be controlled as well.
Key Data
Module/Function: CRM
When correcting CRM Account Details the postcode is changing without being changed by user. This issue
has been rectified.
Key Data
Module/Function: CRM M001
When copying a quote in CRM, if the user selects “No” to not create new order number (i.e. create suffix
order) and a new customer number is entered, the new quote is copied to the original customer and not the
customer entered. This issue has been rectified.
Key Data
Module/Function: CRM M001
The quotes for a prospect were no longer displayed when the prospect was converted to a Customer. This
has been rectified.
Key Data
Module/Function: CRM M001
Quotes could be created in the CRM module for Customers that had a status which disallowed quotes being
entered in the Sales Order module. This has been rectified.
Key Data
Module/Function: CRM M001
When creating a new activity that has a reminder that is due on a previous day, fields Reminder Date/Time
are not being set correctly. This issue has been rectified.
Key Data
Module/Function: CRM M005
The CRM console > Accounts > Sales Menu appeared in a tree format and covered the console in certain
situations. This issue has been rectified.
Key Data
Module/Function: CRM M047
When checking for duplications in the CRM soundex rebuild, hundreds of instances of a blank record are
displayed. This issue has been rectified.
Key Data
Module/Function: CRM M037
The Standard Transaction Type table MQ descriptions don‟t show correctly on the report run to list REP
statistics. This issue has been rectified.
Key Data
Module/Function: CRM R012
mmess-user-only-date1
mmess-user-only-alpha4-1
mmess-user-only-alpha4-2
mmess-user-only-num1
mmess-user-only-num2
can now be enabled on the following screens in the program crm/crmmaint using the Screen Customiser:
activity-review-by-rep, activity-review-by-rep-today
activity-review-by-rep-status,
activity-review-by-rep-priority,
export-act-by-rep, export-act-by-rep-today,
export-act-by-rep-status, export-act-sorted-by-rep,
export-act-by-rep-priority, and
review-all-activities-sorted-by-rep
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
The following user-defined fields from the sales-order-line table can now be enabled on the transfer-lines-
review screen in the program so/m5approve using the Screen Customiser:
sol-user-only-date1
sol-user-only-alpha4-1
sol-user-only-alpha4-2
sol-user-only-num1
sol-user-only-num2
The following user-defined fields from the sales-order-delivery table can now be enabled on the maintain-
financier screen in the program so/m5ordenq using the Screen Customiser:
so-dl-user-only-date1
so-dl-user-only-date2
so-dl-user-only-alpha30-1
so-dl-user-only-alpha30-2
so-dl-user-only-alpha4-1
so-dl-user-only-alpha4-2
so-dl-user-only-num1
so-dl-user-only-num2
Key Data
Module/Function: CRM, SO (various)
Data Intelligence
When using Aggregates within the Group By option with Data Intelligence an I/O error occurred when
attempting to re-select the project. This issue has been rectified.
Key Data
Module/Function: DI M002
When using Filters through DI, the “Match case” checkbox does not appear to be working correctly. If the
filters are set to NOT EQUAL TO and then you specify the value with the correct case, but then leave “Match
case” un-selected, the results are displayed even though the filters should have excluded these. This issue
has been rectified.
Key Data
Module/Function: DI M002
1. If a date macro or round function was used in a calculated field, the calculated field validation failed.
2. Any changes to the column sort order were not being saved between DI Project sessions.
3. If a calculated field was removed, the „Select Calculation‟ screen was being called unnecessarily.
Key Data
Module/Function: DI M001, DI M002
If the EDI order is split (suffix order created for half of the goods), both orders are scanpacked and then
despatched. If both the orders are despatched at once (i.e. first order despatched and then second suffix
order despatched without exiting the despatch screen in between orders), the ASN will only be generated for
the non-suffix order. If the orders were created as two separate orders, this does not happen. This issue has
been rectified.
Key Data
Module/Function: SCAN M006
The customer has received orders via paper and then received edi orders. The edi log does not appear to
report that there are duplicate customer references for manually keyed and archived orders. The duplicate
reference warning should work the same way that it does at manual order entry - based on the check for
duplicate flag and on the account / customer reference. This issue has been rectified.
Key Data
Module/Function: SYS M259
EDI order response acceptance codes are not correct when order responses are reset and recreated. This
issue has been rectified.
Key Data
Module/Function: SO M013
If an item with a condition code of „I‟ (Inactive) is in the EDI file it will be processed and will end up on the
order, even though keying the same item manually is not possible. This issue has been rectified.
Key Data
Module/Function: SYS M259
Key Data
Module/Function: SYS M259
When a Purchase Order Change document is loaded via EDI using the „ORDERS‟ document to update an
existing sales order, a „Zero Divide‟ error is generated for items loaded with a zero shipped quantity. This
issue has been rectified.
Key Data
Module/Function: SYS M259
EDI Purchase Order and Invoice document Header changes: The addition of new fields
Key Data
Module/Function: SYS M259
In the bank reconciliation, when entering a customer direct post where a partial amount is posted to a
general ledger account, the amount that is shown in the bank reconciliation summary is only the amount of
the general ledger post. This issue has been rectified.
Key Data
Module/Function: GL T010
Formal Bank Slip Not Created for Tender Types with BPS Flag = „P‟
SDR:55394
When the Formal Bank Slip is used, transactions with tender types where BPS flag is set to „P‟ will be loaded
onto the transaction list generated. These transactions will be allocated a bank slip number but will not be
printed on the Bank Pay-in Slip.
Key Data
Module/Function: GL M003
When entering a General Ledger Cash Payment and posting the expense side to a project, the GL entries
did not correctly reflect the Project Code and Cost Centre. The special account was also not written in
general ledger. This issue has been rectified enabling drilling down in to the project from the general ledger.
Key Data
Module/Function: GL T004
When consolidating subsidiary companies into the holding company, the opening balance on the holding
company account was being overwritten by each subsidiary company account opening balance. This has
been rectified and the subsidiary company opening balances now add to the existing holding company
opening balance.
Key Data
Module/Function: GL T020
The GL Reference field for journals etc does not automatically change to uppercase. This was previously the
case in earlier releases of PRONTO-Xi. This issue has been rectified.
Key Data
Module/Function: GL T007
When the period processing (SYS M137 - Period Processing Dates) for the corresponding ledger is set with
period = ZERO, the general ledger end of period/year processing is erroring due to subscripting error. This
has resolved.
Key Data
Module/Function: GL M164
This report was not printing the lines total if zero balance accounts were not printed. The problem has been
rectified.
Key Data
Module/Function: GL R024
When performing an integrity, and Check YTD Figures = NO, the system was setting a flag to NO indicating
it was not necessary to include the GLAPP account balances. However, if Check Opening Balance = YES
and Check History Balance = YES, the GLAPP account figure must be included to verify the opening balance
historically. As it was not included, the system found that there was an integrity error in the opening balances,
and „corrected‟ it to an incorrect figure. Under these circumstances, the flag needed to be set to YES to
ensure the value is included. This has been rectified.
Key Data
Module/Function: GL M011
When consolidating to the Holding Company, the process was not current on the Subledger gl-appropriation-
account object when retrieving the original account. Thus the original account was lost in the consolidated
ledger. This has been rectified.
Key Data
Module/Function: GL T020
When generating supplier transactions from an external file, the transaction tax code was being set. There is
a new method of storing the tax data, and if the tax code on the transaction is set, the system assumes it is
an OLD transaction. This caused problems with generating the tax on the discount.
Also, the system was not setting the discount flag on the transaction if the supplier has a settlement discount
code. The user had to manually set the flag on each transaction.
The program has been changed to set the „apply discount„ flag to YES if the supplier has a settlement
discount and the transaction tax code is output as SPACES. The tax on calculated for the discount is now
correct.
Key Data
Module/Function: AP T029
When you create a foreign invoice with a retention amount, and try to make a payment on this invoice for the
amount left after the retention, PRONTO-Xi does not accept the payment. This issue has been rectified.
Key Data
Module/Function: AP T034
When overriding the default conversion rate between subsidiary and holding companies, as set up in the
special report type, the system was overwriting the rate with the default conversion rate. This has been
rectified.
Key Data
Module/Function: GL T020
Inventory
After entering a stock code in the Inventory Enquiry screen, using the „?‟ option to bring up the Customer
Enquiry screen, and then selecting „Price Enq‟, the value in the Item Code field was blank instead of the code
entered. This issue has been rectified.
Key Data
Module/Function: INV E001
When a bin location is changed at stock warehouse detail for a stock code in a type 0 warehouse during a
stocktake, this caused the GL Update Inventory Ledger to fail. Now the change of bin location for a stock
code in a type 0 warehouse will not impact the update of inventory ledger via stocktaking process.
For a stocktake control code for a single warehouse code parameter of type 0 warehouse, when select „N‟ -
modify default parameters, the user is allowed to change the range of bin location. However, WARNING
message will displays to highlight it.
Key Data
Module/Function: INV T023
The adjustment program can now be called passing a batch reference for a number of transaction calls.
Specific to a call of „-b-adjust‟.
Key Data
Module/Function: INV T011
Technical Reference/Dict. Changes
stk/m4adjust can be called with „-b-adjust‟
can now also add „-batch„ bbbb „-gl-date‟ ddddd
The currency of the converted stock code is overwritten by the new stock code if using the up arrow to
navigate fields. This causes the wrong cost to be used in the conversion. This issue has been rectified.
Key Data
Module/Function: INV T013
With this change, when the recalculate option is based on current buy price and the price is ZERO, there is
now an option to prevent the replacement cost being set to ZERO
Key Data
Module/Function: INV T026
Inventory issue, for an internal customer, of stock items with freight charges now posts the freight charges to
the appropriate general ledger accounts.
Key Data
Module/Function: PO M015
The „Cannot Correct‟ message on the report was overwriting the detail of decimals for a particular Integrity
error. This has been rectified.
Key Data
Module/Function: INV M011
When an item was entered into the Inventory Enquiry function and an option was entered, the relevant
information window was shown. Upon exiting the results window you could then enter another item and the
last used option should default back into the field. This issue has been rectified.
Key Data
Module/Function: INV E001
When Print Total = Yes, and the report is run with report sequence W=Warehouse, the WHSE Totals are not
showing. This issue has been rectified.
Key Data
Module/Function: INV R099
Inventory valuation report is not displaying the correct cost or value. Report is not able to handle large values
correctly. This issue has been rectified.
Key Data
Module/Function: INV R104
With this change, selected keyword components will now be copied to the configured item for the new
quotation sales order.
Key Data
Module/Function: SO M122
Major Function Flags
-Configurator-Create BOM Quote Conv.=„Y‟
Table Entry:-
-PR/SO_ENTRY=so/m50consys
When the location code on a stocktake count is changed via the stocktake process, the locations are not
updated if it is a type 2 warehouse. This issue has been rectified.
Key Data
Module/Function: INV T023
If the Min Stock or Max Stock is changed for a multi-level kit, the kit‟s components and sub-kits may have
incorrect Min Stock or Max Stock. This has been rectified.
Key Data
Module/Function: INV M138, INV M419
With this change, it is now possible to do negative adjustment of a lot tracked inventory item out of LOST
location from a WMS warehouse, to a maximum of the total quantity for all lots in the location.
Key Data
Module/Function: INV T011
The user is only allowed to enter a Planning BOM of "C" via „Misc‟ mode, option „Co-Product‟. Attempt to
enter a „C‟ planning BOM via „Header‟ for non Co-Product is not permitted.
Key Data
Module/Function: INV M151
Reorder Policy descriptions on Inventory Maintenance Screen, did not match the descriptions in the help.
This issue has been rectified.
Key Data
Module/Function: INV M138
Stock that has been split using the „Repack/Split of Item‟ function may have incorrect cost recorded. This has
been rectified.
Key Data
Module/Function: INV T016
For the „2‟ enquiry ie Movements with Balance, the function did not distinguish between a Purchase Order
and other suffixed codes of the same order. This has been rectified.
Key Data
Module/Function: INV E001
Stock issue to a project via INV.T006 for Type „J‟ or „P‟ does not set document-no or document-type like
other transactions do. But related GL Trans are correctly set with the document type of „JI‟ and the next
document no. This makes Project Transaction tracking impossible. This issue has been rectified.
Key Data
Module/Function: INV T006
When missing FIFO costing records are inserted during stocktake update due to an imbalance in the FIFO
costing records, the quantities entered are incorrect if there is more than one FIFO costing record. This issue
has been rectified.
Key Data
Module/Function: INV T023
A new column „Supplier Priority‟ has been added to the „Page of Suppliers‟ in order to control the order in
which the suppliers are listed.
Key Data
Module/Function: INV E005
Now when accessing Inventory Enquiry using the „B‟ enquiry the „Detail‟ mode is now showing „Stock
Warehouse‟ screen information.
Key Data
Module/Function: INV E001
Direct Transfer can be used to transfer serial stock items between warehouses.
Key Data
Module/Function: INV T019
Key Data
Module/Function: MANU M071
When an item exists on an open catalogue that is still within its date range, keying the same item into a new
catalogue warns the user that the item is already in use elsewhere - this is correct. If the original catalogue is
closed and the date has lapsed, the warning message will still appear. This issue has been rectified.
Key Data
Module/Function: INV M103
iSupplyGlobal
When loading inventory items from stock-master into the iSupplyGlobal module using the “Rebuild All
iSupplyGlobal Items” option, and the multi UOM table has duplicate GTINS, the program errors. This issue
has been rectified.
Key Data
Module/Function: ISUP M025
Message Bus
All messaging services will now run for a maximum of 11 hours to release system resources and ensure that
message bus processing does not interfere with daytime trading when there is a large backlog of messages
to be processed. The message bus system will continue to process any residual messages the next time the
service runs.
To prevent too many files being created in a single directory, the Message Bus system will now save XML
files into two subdirectory levels below the directory specified by the PROMQFILEDIR environment variable.
Directory names are created using day of the month, hour segment*** of the day and minute of the hour.
First Level There will be 248 directories. 8 segments*** per day (1 for 3 hours) * 31 days
Example: If the xml file created on 1st of the month at 6:32:15, then the file path/name will be
/u2/data/bmsxi-reld/1-2/32/D1279692174X6SUgl-master9.xml
A setup wizard has been created to assist with configuring the publisher and subscriber systems. The setup
wizard has the following three options:
1. Select the "Publish Messages" option to enter Publisher details, Subscriber details, related subscriptions,
remote queue & package details
2. Select the "Send Remote Package Only" option to send the setup package from head office to the store
3. Select the "Subscribe Messages" option to set up Promq Service/listener, Application Service 10,11
company entries, load the remote package
Key Data
Module/Function: MSG
When creating a pay run for commissions, and the pay period end date of the pay run is the same as the
previous pay run for that payroll number, employees were not selected for the payrun even if ALL employees
is selected for the option Employees Due to be Paid or All Employees in the Select Employees for this Pay
Run process. The note at the top of the Select Employees for the Pay Run screen has been changed to let
the user know that employees with a Date Paid up Till date the same as the Employee Pay Period date will
not get selected as well.
Key Data
Module/Function: PAY M094
When converting an employee number that is being maintained by another user, the conversion process
failed with an I/O error. This issue has been rectified.
Key Data
Module/Function: PAY M055
When processing a payrun for a contractor, the GST amount should be added on to earnings rather than
being deducted.
Key Data
Module/Function: PAY M086
1. The "Deductions" heading was not printing in the blank space on the summary if there was no Union Fee
deduction (type "U") present.
2. User was not able to set a pay code Type "9" to "U"nion or "W"orkplace giving after-tax deductions.
3. The "Too many" allowances and/or deductions message was printing on the error report even although all
allowances and deductions are now printed individually.
Key Data
Module/Function: PAY R002
When non-working days were calculated on the leave entry screen, Saturday and Sunday were hard-coded
as non-working days. It was not taking into account:
1. A company who works Saturday and/or Sunday, even when a record was present in system-calendar-
control.
3. An individual employee variation to the company/state default, even if record was present.
The check for Saturday and Sunday will use employee, state, company hierarchy and base calculation on the
first record found.
Key Data
Module/Function: PAY M075
In Pay Transaction Smart Edit, user can now select from a list of pay codes when using the <F2> key.
Key Data
Module/Function: PAY M091
When previous pay period was for (eg) a 30 day month, and a report run for the next month of (eg) 31 days,
the program was calculating the period difference as 1 month and 1 day instead of 1 month. This has been
rectified.
Key Data
Module/Function: PAY R041
A public exportable procedure has been added to allow the flexibility of not updating the pay frequency based
on hours per cycle. Some industries have hours exceeding the normal hours per cycle.
Key Data
Module/Function: PAY M029
When calculating the tax owing on monthly paid employees, if the period salary ended in 33 cents, the
procedure was short-taxing the employee by about $4 compared to the ATO tables. This has been rectified.
Key Data
Module/Function: PAY M086
Plant Maintenance
If a plant PM task has materials added in the form of a kit and this kit does not have a Bill of Materials
header, the work order creation program created a „blank‟ work order. This issue has been rectified.
Key Data
Module/Function: PLT M134
In the Scheduled PM Work orders screen, completed work orders can be reopened using the Approve,
Release and Print mode. This mode has now been restricted to forecast work orders.
Key Data
Module/Function: PLT M134
A correction of the Plant Item was being lost if the Help on Parent Project was selected. This has been
rectified.
Key Data
Module/Function: PLT M001
The "Out" (Downtime) value was being incorrectly calculated. This has been rectified.
Key Data
Module/Function: PLT R012
On a Linux operating system if a user‟s windows login begins with "e" they cannot view plant structure tree.
This issue has been rectified.
Key Data
Module/Function: PLT E016
An Excel worksheet was closed down without saving if the Print function in the Maintain Work Order screen
was used. This has been rectified.
Key Data
Module/Function: PLT M001
If a user had PLT M001 security and selected an In Progress Order from the above screen a number of
functions eg entering Timesheets, Purchase Orders ,Requisitions etc were not available to them. This has
been rectified.
Key Data
Module/Function: PLT M001
In Plant Maintenance screen if Correct mode was selected and then F4, the Plant Item number was being
spaced out.
Key Data
Module/Function: PLT M079
For Purchase Orders the report prints the supplier code and then the stock item/purchase order number.
However if the supplier and the stock item were the same code then it was incorrectly printing the stock item
description. This has been rectified.
Key Data
Module/Function: PLT R021
A user without PLT S007 security was able to delete a Labour Category . This has been rectified.
Key Data
Module/Function: PLT M001
After entering all the screen data for a Plant Item the code for the item was being cleared. This has been
rectified.
Key Data
Module/Function: PLT M079
An issue whereby items could not be added to the materials list for „Forecast„ status plant work orders has
been corrected.
Key Data
Module/Function: PLT M001
When a default value is entered within the Screen Customiser to the field „lf-estimate-type‟ (Proforma), this
default value is not getting populated properly. This issue has been rectified.
Key Data
Module/Function: PLT M001
On completion of a Work Order the proforma number selected was not being displayed. This has been
rectified.
Key Data
Module/Function: PLT M133
The last digit of the requisition (Sales Order number) was being overwritten. This has been rectified.
Key Data
Module/Function: PLT R023
Under certain conditions a blank Work Order was created. This has been rectified.
Key Data
Module/Function: PLT M127
The description for a Special line was not being displayed. This has been rectified.
Key Data
Module/Function: PLT M001
All description lines (and Labour Category lines in Work Request) had to be entered through even if they
were blank. This has been rectified.
Key Data
Module/Function: PLT M137
Plant Work Order cost category budget values are set to ZERO when the detail mode is accessed, if there is
no detail on the category before release.
Key Data
Module/Function: PROJ M117
The MTBF was not being updated after a Work Order was completed. This has been rectified.
Key Data
Module/Function: PLT M001
While entering a new plant order, the work order should be assigned only once. That work order number
should not change even if the plant item code changed in the middle of the work order creation process.
Key Data
Module/Function: PLT M001
Point of Sale
To set sales order lines to backorder need to change the customer to a non-cash account.
Key Data
Module/Function: POS M017
The current messages displayed in POS when a customer is set to Closed / Deleted or Legal Action were
incorrect. This has been rectified.
Key Data
Module/Function: POS M017
When manually changing the status of a voucher from Inactive to Active, the posting should be DEBIT to the
GL provision Account and CREDIT to the Tender Type GL Account.
Key Data
Module/Function: POS M008
During Point of Sale entry, it is possible to input a keyword to search for an item. The list that appears from
the search result will also list the item price. This price may change (incorrectly) as the user scrolls through
the items. This is more likely to happen if special pricing is used. This has been rectified.
Key Data
Module/Function: POS M017
Any item security settings configured in the Accounts Receivable module, for example to prevent a customer
from purchasing a specific item or item group, will now also apply to purchases at Point of Sale.
Key Data
Module/Function: POS M017
When a layby order with multiple lines is created in POS, the Layby Locations screen displays all of the sales
order lines. If the corresponding sales order is then maintained in the Sales Order Edit function and lines
removed from the order, the Layby Locations screen was still showing the removed lines. This issue has
been rectified.
Key Data
Module/Function: POS M016
A new version (Version 2) of the public exportable procedure „public-reorder-buy-price‟ has been created with
the additional parameters of purchase-order.* purchase-order-line.* and reorder-whse-code. Refer to the
SDK for more details.
Key Data
Module/Function: PO M026
Refund Using a Different Tax Rate from the Original Sales Order line
SDR:55529
Refund of a sales item via Point of Sale uses a different tax rate from the original sales order line if the tax
rate has been changed after the original sales order has been updated. This issue has been rectified.
Key Data
Module/Function: POS M017
An I/O error was discovered when processing Repair Action "Enter Quote". It was found to be caused by
using a repair supplier which was only linked to the REPAIR QUOTE inventory item (ie not linked to REPAIR
PARTS or REPAIR LABOUR). The code has been modified to handle this situation.
Key Data
Module/Function: RPR M019
Table Entry:-
-Your Role - set P_RPR_ADM
When there is a POS order line with a backorder quantity and other POS order lines with shipped quantities,
after tendering money, the original sales order will split and will create a suffix order for the backordered lines
and set the status to Backorder.
The order no column in the POS Department Sales Report only allows 7 characters to appear on the report.
If 7 characters are used, the number gets pushed up against the Rep code field. This issue has been
rectified.
Key Data
Module/Function: POS R004
Receipting for an archived POS sales order creates a ZRNDBENEFIT line in sales-order-lines and leaves it
outstanding in the customer account. This issue has been rectified.
Key Data
Module/Function: POS M017
Project Costing
Budget Detail Lines cannot be deleted any more. This issue has been rectified.
Key Data
Module/Function: PROJ M117
The Budget Review screen was not being displayed when the range for the Cost Categories was a single
category. This issue has been rectified.
Key Data
Module/Function: PROJ M117
When running a Service Profit take up the automatic Bulk Forecast Update should consider projects only in
the range nominated.
Key Data
Module/Function: PROJ T005
When a claim was selected and the Cancel option selected, the wrong claim was cancelled. This issue has
been rectified.
Key Data
Module/Function: PROJ M011
The reports „Subcontract Payment Advice‟ and „Progress Claim Assessment Form‟ should show correct
retention amounts of the claim selected.
Key Data
Module/Function: PROJ M011
The same claim number was able to be used for the same contract to create multiple claims. This issue has
been rectified. Note: When entering claims, claim numbers can not have leading SPACES and if the claim
number has only two characters the first character can not be ZERO.
Key Data
Module/Function: PROJ E006
The claim schedule that is printed after a claim is submitted/invoiced prints negative amounts rather than
positive in the previously Claimed columns. This issue has been rectified.
Key Data
Module/Function: PROJ M037
In Project Maintenance changing a customer for a project did not change the Site Details for that project.
Now when a customer is changed a question is asked of the user if they wish to display the new site details.
If the answer is No the details are automatically updated to the details of the new customer. If Yes then the
user can accept ,reject or modify the details.
Key Data
Module/Function: PROJ M117
If a previously entered but unapproved subcontractor claim was edited and the previous claim had a retention
amount but after editing the retention amount was zeroed, the resultant batch would be out of balance as the
system remembered the original retention amount but did not spread the retention across the new claim
amounts. This issue has been rectified.
Key Data
Module/Function: PROJ E006
When Project is created with Budget Detail Lines, forecast details shows some discrepancies in its value
displays. This issue has been rectified.
Key Data
Module/Function: PROJ M117
The Grand Total line has been spread over 2 lines. The reported fields can now hold values 100 times
greater than previous values.
Key Data
Module/Function: PROJ R061
The Actual column in Purchase Orders for Project screen will show claimed amounts or received amount of
the selected purchase order against the project.
Key Data
Module/Function: PO E040
When issuing stock via Project Costing, if user cancels the line and corrects the project number, the
transaction is created against the correct project but the Quantity Issued is updated against the incorrect
project. This issue has been rectified.
Key Data
Module/Function: INV M054
Material Requisitions were created even if the user did not have INV S083 security. This issue has been
rectified.
Key Data
Module/Function: PROJ M117
If a multi-level kit is added to the budget details of a project, the components of sub-kits may not be added.
This issue has been rectified.
Key Data
Module/Function: PROJ M117
If F4 was used before the entry of the Branch the program went into an infinite loop. This issue has been
rectified.
Key Data
Module/Function: TEND M001
If a project has a subcontract raised for the current month, a partial claim for a future month then made,
approved and posted, then the forecast for "Cost to Complete" with the cut off date of the current month (i.e.
prior to the claim date, and after the sub-contract is raise) was done, the Cost to Complete screen should
show the Commitment as the claim has not been approved yet. Because claim approval has happened after
the cutoff date, that amount cannot be taken away from the current commitments.
Key Data
Module/Function: PROJ M117
The check box was losing its “tick” after being accepted. This issue has been rectified.
Key Data
Module/Function: PROJ M050
An incorrect Project Integrity Error Warning is produced when the projects linked to a grandparent project
have a different branch assigned to them. This has been removed from the project integrity report.
Key Data
Module/Function: PLT M006
The header has been removed from the options (last) page of this report.
Key Data
Module/Function: PROJ M048
The document/tracking details for project transactions were being overwritten by the document number of the
sales order used to bill the customer in some cases. This now does not occur and the original source
document/tracking identifiers remain with the transaction even once invoiced.
Key Data
Module/Function: PROJ
Profit take up at Parent Level for all IH statues projects in a parent/child relationship should not take Lost and
Quotation statues child projects into consideration to calculate profit percentage.
Key Data
Module/Function: PROJ T002
The project variation header screen allowed up/down arrow which could show variations for other projects.
These now only show variations for the current project
Key Data
Module/Function: PROJ M117
When the currency rate of a purchase order attached to a project changes, the purchase order details in the
project should reflect the changed values in the purchase order.
Key Data
Module/Function: PROJ M117
When a transaction is posted against a project.cost category the actual account code attached to that should
be fetched and displayed.
Key Data
Module/Function: PROJ M117
Quantity values can now be entered with up to 4 decimal places. Previously entry was restricted to 2 decimal
places only.
Key Data
Module/Function: PROJ M005
When a Sales Orders/Invoices created from a project progress invoicing process, if the sales order lines
created for the linked purchase order lines with special items the description of the special item, entered by
the user should appear as the line description of the sales order line.
Key Data
Module/Function: PROJ M050
In Stock Issue to a project, the system is no longer remembering the last cost-centre as a default for the next
line. This issue has been rectified.
Key Data
Module/Function: INV M054
When creating a new claim for a sub contract, current claim amount should be defaulted to ZERO. Then the
user can enter the current claim amount.
Key Data
Module/Function: PROJ E006
When a project has a child project and both the parent and child have costs added to them, then the
summary for both the month and week „Transactions‟ option is showing all transactions from both the parent
and child. This issue has been rectified.
Key Data
Module/Function: PROJ M117
In the Progress Claim Assessment, the tax component is not being printed. This issue has been rectified.
Key Data
Module/Function: PROJ M011
When flags are set to not use scale factors when calculating rates in project timesheets, the Timesheet detail
listing report (SYS.R035) shows rates using scale factors. When these timesheets are posted to the project,
they post the correct amount (without using scale factors). This issue has been rectified.
Key Data
Module/Function: SYS R035
The Budget Revenue amount (when including variations) was being reset to zero when the below mentioned
flag was set to P. This issue has been rectified.
Key Data
Module/Function: PROJ M021
Major Function Flags
-Project-Profit Rule, Contract Value = P
The report was not denoting Completed projects with a „~‟. This has been rectified.
Key Data
Module/Function: PROJ R061
Actual Cost Value Not Set Correctly for Serial Item with 100% Discount
SDR:54858
The actual cost of a serial number with 100% discount is not set to 0 after purchase order is updated. This
results in inventory integrity error. This issue has been rectified.
Key Data
Module/Function: PO M006
When an Agent Address is set up on a Supplier and your Purchase Order Layout, when you raise a PO and
change the Agent Address, it is not reflected on the printed Order. This issue has been rectified.
Key Data
Module/Function: PO R052
When Maintaining a Subcontractor it is possible to set the Warehouse to SPACES. This issue has been
rectified.
Key Data
Module/Function: PO M064
A "Do not show again" checkbox option to message "Buy Price Greater than Sell Price" while raising PO at
SO conclusion has been introduced
Key Data
Module/Function: SO M001
If the ESC key is hit to exit the charge line detail entry screen, the charge line is still being inserted in the
purchase order. This issue has been rectified.
Key Data
Module/Function: PO M011
When a "Q" type order is converted to an "On order" purchase order the system shows the original cancelled
order in the commitments list for the GL account. However the newly created Purchase order is not shown
under the commitment list. This issue has been rectified.
Key Data
Module/Function: PO M006
Key Data
Module/Function: PO E006
When viewing PO lines via the PO Enquiry screens, you can set up a custom view and set this view as the
default. But if the user sets a default custom view and switches to another order of a different status (i.e.
from „On Order‟ status to „Goods Updated‟), the original „On Order‟ line will switch back to standard view.
This issue has been rectified.
Key Data
Module/Function: PO E039
„Goods Exchange‟ Purchase Order Lines not Copied from Original P/O
SDR:54427
Purchase order line details of the original purchase order are not copied across when a „Goods Exchange‟
(i.e. type „X‟) order is entered. This issue has been rectified.
Key Data
Module/Function: PO M011
The shipment processing program terminates abnormally when the value of the field po-line-volume is
greater than the precision of the corresponding field in the purchase order costing file. When this situation
occurs, the system will now set the value of this field (po-line-volume) to its maximum allowed value, which is
9999.999999. An audit record is also written to the purchase audit file to indicate the real value of the field.
The formula to calculate the value for the volume for this purchase order line is:-
Purchase order line quantity * stock supplier pack cubic meter / stock supplier pack quantity
These values are store in the following fields of the purchase audit file:-
Key Data
Module/Function: PO M004
Indent items with incompatible hazardous class codes may not have their associated SO/PO link records
updated correctly during sales order splitting process. This has now been corrected.
Key Data
Module/Function: SO M023
Major Function Flags
-Raise P/Order from S/Order = „2‟
Table Entry:-
-Compatibility Class Codes - HX
When a kit is added to a purchase order, kit components of type "PO" or "Gn" may not be loaded into the
order. This issue has been rectified.
Key Data
Module/Function: PO M011, PO M026
When the major function flag „Ask for warehouse before PO number‟ is set to „1‟, the Copy function ignores
„accept‟ order and generates a PO order number without first prompting for the warehouse. Issue corrected,
now screen accept whse-code before generate PO order number.
Key Data
Module/Function: PO M014
Major Function Flags
-SYS.M063, Ask Warehouse Before P/O# = 1
When specific general ledger accounts are masked for a user, (ie excluded), the user is not allowed to enter
a purchase order with this account. However, the check was not done when copying an existing order, which
provided a loophole. This change is to rectify this and close the loophole. The copy function now checks any
general ledger accounts used on the order lines and if any which are excluded for the user are found, the
copy cannot proceed.
Key Data
Module/Function: PO M006
The warehouse code is now prompted for before the purchase order number. This has been changed to
make sure a valid warehouse code is always available when a purchase order record is inserted.
Key Data
Module/Function: PO M011
Major Function Flags
- Ask Warehouse before P/O. NOTE: this MFF has been removed.
Getting the next PO number is now dependent on the YY serial number record POwwww existing. ( where
wwwww is the warehouse code ). If this doesn‟t exist, the YY serial number record of PO is used.
For a type „Q‟ (Quote) purchase order, the status was not being changed to „PO Approval Required‟ when the
user‟s limit is exceeded. This issue has been rectified.
Key Data
Module/Function: PO M006
For type „F‟ (Fabric Order) purchase orders, at the end of the entry process a sample order is created. When
accessing this sample order using the Header mode on the Maintain Purchase Orders screen a message
was displayed that the order is locked awaiting update by another user, when this was not the case. This
issue has been rectified.
Key Data
Module/Function: PO M006
Prior to this change a requisition awaiting approval could be approved and the order processed when the
supplier was On Hold. Entry of a new order is not allowed when the supplier is in this status, so approval of
the requisition has now also been disallowed.
Key Data
Module/Function: PO M094
When receiving purchase orders, the sales backorders are not being released if the option "S" for Release
items to SO is selected. This issue has been rectified.
Key Data
Module/Function: PO M101
When a purchase order was entered for an item subject to a supplier quantity break price, the correct price
was found. However, if the item line was then changed, and the quantity altered, the system was not
rechecking the break points to see if the price had changed. This issue has been rectified.
Key Data
Module/Function: PO M011
In Purchase Order Entry, the tax code on the purchase order line for special item should default from the
supplier masterfile.
Key Data
Module/Function: PO M011
Emails were not being sent to QMS Managers of Level 3 when Customer Complaints and Disputed Invoices
were entered in the system. This issue has been rectified.
Key Data
Module/Function: QMS M008
Rental
In PRONTO-Xi release 670, it may be possible to enter an invalid customer when creating a rental contract.
This issue has been rectified.
Key Data
Module/Function: RENT M015
The customer„s postcode and telephone number were not copied to the sales order delivery address when
invoicing a contract. This issue has been rectified.
Key Data
Module/Function: RENT M015
The Serial Number was not being exported to Excel. This issue has been rectified.
Key Data
Module/Function: RENT M023
If you add a note in the options screen for a Hire Contract and then ship & receive the contract allowing the
receipt process to invoice and finish the contract a sales order line is created as an RN type with an „N‟ in the
stock code. When you then try to update the invoice it fails. This issue has been rectified.
Key Data
Module/Function: RENT M006
Repairs Management
If a repair order is rejected by the customer, the goods are returned and the customer is notified, but when
you process the customer collection the order goes to a status of „C/N rdy for picking„ and disappears out of
the Repair module. If you try to change the order in any way outside of the Repair Module, you get an error
saying „Can not change status of orders created by the Repairs module‟. This issue has been rectified.
Key Data
Module/Function: RPR M019
Sales Order
The Avail Cr. field in the sales order header was not showing the available credit amount of the current
customer when the customer was changed during sales order entry. This issue has been rectified.
Key Data
Module/Function: SO M001
Allocating stock to a fully paid backorder was putting the sales order on Credit Hold due to the COD credit
limit. This has now been resolved and the fully paid order will be put on Ready for Picking status.
Key Data
Module/Function: SO M023
If the tax code of the Tax line is not ZERO, you can enter an amount greater than ZERO as the total amount
of the tax line. Also User can change the tax code now.
Key Data
Module/Function: SO M001
When receiving cash at SO conclusion for a COD customer where the order is going to Backorder status,
when the customer pays the entire amount outstanding for the order by partial payments using different
payment methods, the „Receipt Options‟ screen comes up and the order cannot be finished without
suspending it and then going back in to release it and continue processing. This issue has been rectified.
Key Data
Module/Function: SO M001
When the claim order generated from a supplier rebate is updated, the amount posted to the DCTRL
account does not include the tax. This results in an unbalanced batch. This issue has been rectified.
Key Data
Module/Function: SREB X001
Changing a consignment number at dispatch, using Scanpack, does not save the new consignment number.
This issue has been rectified.
Key Data
Module/Function: SCAN M006
When sales orders are printed via consolidated invoice print, the JE transaction records against the customer
account were not being populated with the correct consolidated invoice number. This issue has been
rectified.
Key Data
Module/Function: SO R141
During credit note process, for stock code with stock issue control code set as „W‟ for random weight, the
user is allowed to enter the total weight of the new base quantity for the corresponding new quantity entered.
Key Data
Module/Function: SO M334
Major Function Flags
-Sales Order Entry/Edit Procedure
-, Initial Lines Mode = „A‟
For the Canadian Tax System, the Customer Price Enquiry does not display the tax inclusive price item. This
issue has been rectified.
Key Data
Module/Function: SO E063
Prior to this change, processing a cutting line using the special order entry program „so/m50cut‟, with a
negative and positive picking record for the same item on the same order (i.e. stock going into a location and
then immediately taken out of the location), would result in a negative „LOST‟ location entry for the parent
item, resulting in inventory integrity. This has now been corrected.
Key Data
Module/Function: SO M287
Major Function Flags
-Stock Fast Maintenance Format = „P‟
Table Entry:-
-PR/PAPERGUILL, PR/PAPERSHEET,
-, PR/PAPERSLIT, PR/SO_ENTRY = so/m50cut
Cannot correct the shipped quantity of a random weight stock item during despatch of the sales order. This
issue has been rectified.
Key Data
Module/Function: SO M287
Changes to the discount rate in the Reprice Order function were not audited. This issue has been rectified.
Key Data
Module/Function: SO M062
The „Receive Transfer Orders‟ function is not checking the inventory ledger period when asking for a
transaction date and is allowing inventory transactions to be posted into a closed period. This issue has been
rectified.
Key Data
Module/Function: SO T009
The Address Details screen, which is displayed when entering a sales order and can be accessed via
Customer Maintenance (AR M001) > Delivery > Multiple Delivery > Address, now has a Grid View mode
which allows the relevant delivery address to be selected via a data grid.
Key Data
Module/Function: SO M001
The Headings of this report were incorrect when irregular Period Processing Dates were used. This issue
has been rectified.
Key Data
Module/Function: SALE R014
If you have a rental contract and apply a discount to it, the invoice created should show the discount and it
should be able to update the invoice.
Key Data
Module/Function: SO T017
When using option „I‟ in the Invoice Print program, and when multiple orders are printed on to one, the Sales
Order numbers are not shown for each line, instead the invoice shows „MULTIPLE‟. This issue has been
resolved and the order number is now visible for each line.
Key Data
Module/Function: SO R100
If a user is not able to see the cost on stock items because they do not have access to cost in the user
access profile, when allocating serial numbers at sales order entry and sales order despatch the item cost is
displayed which is incorrect. This issue has been rectified.
Key Data
Module/Function: SO M001
Editing a sales order line and changing the selling UOM was causing the line to be incorrectly priced, if the
line was priced by the alternate UOM. Changing the UOM when the line has been priced by alternate will
recalculate the price and extended line amounts.
Key Data
Module/Function: SO M001
Major Function Flags
-SO Price/Disc not A or C
KIT Header is setup with a discount (C-Customer/ Item Group Discounts). If user is not Credit Release
Officer, Price/Discount Entered flag is set to „A‟ and Customer Line Discounts Allowed, A Sales Order Line
will end up having strange discount values for KIT item. This issue has been rectified.
Key Data
Module/Function: SO M001
When raising credit note for tally items where an alternate UOM is used, there may be issue allocating
quantity to pick (in the „Sales Order Picking Location„ screen). This issue has been rectified.
Key Data
Module/Function: SO M001
Major Function Flags
-‟Style Entry and Display Format‟ = "T"
-, „Confirm Required For Broken Packs‟ = "L
When sales order lines are entered from the command line using the program „m50fastent‟ and special
pricing is set up, the price returned was incorrect and inconsistent with the normal sales order entry and price
enquiry. This issue has been rectified.
Key Data
Module/Function: SO M001
Material Requisition from Quick Pick Slip Issue Causing Integrity Error
SDR:55253
A Material Store Requisition created via Quick Pick Slip Issue (PROJ M005), was not updating the general
ledger and project costing tables correctly. This issue has been rectified.
Key Data
Module/Function: SO T017
The cost of a multiple level configured item is not being calculated during quotation order entry as the
configured item is not being constructed correctly. This issue has been rectified.
Key Data
Module/Function: SO M001
Negative Wholesale Price not Displayed for Sales Order Charge Line
SDR:55439
Negative wholesale price cannot be displayed in the sales order line entry screen. This issue has been
rectified.
Key Data
Module/Function: SO M001
When sales order line is added/removed to/from an existing sales order of status „Ready for Picking„, the
number of pickable lines of the associated warehouse order picking header already loaded into a type 3
warehouse is not updated. This issue has been rectified.
Key Data
Module/Function: SO M001
Opportunity quotations no longer show as an error on the sales order integrity report.
Key Data
Module/Function: SO M005
Using the „Order Find‟ mode in the Enquire by Package screen would change the index key from package #
to Order No when displaying data. That will change sort order to Order No. It‟s no longer working now. This
issue has been rectified.
Key Data
Module/Function: SO E032
Orders were not being picked up when entering a reference number in Sales Order Enquiry by Specifying
Parameters. This issue has been rectified.
Key Data
Module/Function: SO E024
Sales Order packages and weight are refreshing to incorrect values when picking slip is being printed in the
Sales Order Edit. This issue has been rectified.
Key Data
Module/Function: SO M053
This SDR has reinstated a loss of functionality from v660 and earlier, that allows a credit note line to have a
positive quantity for items such as a re-stocking fee. For a special order quantity of 1 on a credit note, the
expected input would be -1.
Key Data
Module/Function: SO M001
This date was being displayed in non-standard date format. This issue has been rectified.
Key Data
Module/Function: SO M001
Key Data
Module/Function: SO M287
On the Release Quote screen a new (current) delivery date is calculated which overwrites the quote
expected delivery date when the quote is [Convert]ed to a normal order. However, the date was being
overwritten on the quotation when it was [Edit]ed or [Part Convert]ed.
Now, the estimated delivery date is only overwritten by the calculated date on the converted orders ie when
[Convert] is selected, or on the suffixed order when [Part Convert] is selected. In the second instance, the
original quotation order with the remaining stock retains the original date.
Key Data
Module/Function: SO M058
If a quotation with a configured item is copied to another order (without creating a new order number), and
the item is reconfigured in the new quotation, the new configuration may be incorrectly recorded against the
original quotation and not onto the new quotation as expected. This issue has been rectified.
Key Data
Module/Function: SO M001
Major Function Flags
-Configurator-Create BOM Quote Conv. = Y
The reason code for a rebate credit note is being overwritten by the zero price reason code of its sales order
line. This issue has been rectified.
Key Data
Module/Function: SO T017
This function to update the tax on an order has been added to the reprice order function specifically for NZ
clients using type "L" taxing method. For existing orders which have not yet been invoiced, the tax rate on the
tax code can be increased/decreased, and the lines and header information recalculated by using this
function and setting the "Update Tax Only" field to YES. In this mode, the order is not repriced ie the original
base price is not altered, but, if the tax rate is used on the order, the lines and header details are
recalculated.
Key Data
Module/Function: SO M062
Major Function Flags
-sys-tax-type = "L"
During the transitional period when the global sales tax rate is changed on the system, provision has been
made to stamp the old transactions with the old global tax rate so that credits may be generated later using
the old rate. However, if one of these orders is copied to create a current order, it was passing the old rate to
the new order. This issue has been rectified.
Now if an order which is stamped with the old rate is COPIED, the system will clear the old rate on the new
order and recalculate the tax and other header fields using the current global tax rate.
Note: This is NOT applicable to Scheduling orders. The user will have to maintain the tax rate manually using
the [Tax Chg] mode on sales order edit if they wish to alter the tax rate to the current tax rate.
Key Data
Module/Function: SO M122
Major Function Flags
-MFF Sales Tax Type = "G"
When entering an item with negative stock available and option S (Ship Available Only) is selected, the
quantity shipped was being set to the negative stock on hand value rather than zero. This issue has been
rectified.
Key Data
Module/Function: SO M001
When a sales order contains two manufactured items with different expected delivery dates it concludes with
status „To Be Manufactured‟ or „Work Order Raised‟. The status of the original sales order changes upon
split of the two sales order lines by expected delivery date. This issue has been rectified.
Key Data
Module/Function: SO M001
The Cursor now stops at the CRM prompt when the conditions described below are set.
Key Data
Module/Function: SO M001
Major Function Flags
-Project Costing = N, Stop And Ask What = A
When the Credit Note Penalty Charge is applied, the tax component was not being calculated. This issue has
been rectified.
Key Data
Module/Function: SO M001
The ability to open the Sales Order Enquiry screen in Find mode, as in earlier releases, has been restored by
adding a calling parameter „-e-find‟ to the sales order enquiry program „m5ordenq‟.
Key Data
Module/Function: SO E007
When a sales order is split and the original order only has backordered quantity, the status should be set to
backorder.
Key Data
Module/Function: SO M001
When despatching consolidated invoices and Print Invoices is set to „Y‟, the invoices do not need to be
printed and the status of the sales order should be set to Ready to Update, but were instead being set to
Ready to Print. This issue has been rectified.
Key Data
Module/Function: SO M287
The system was not current on the warehouse when selecting it from the Stock Balance screen, and
because of this it was allowing shipment when no stock and the stock balance to go into negative. This issue
has been rectified.
Key Data
Module/Function: SO M001
When there is rounding difference between the sales order line shipped cost and the actual warehouse cost,
the shipped cost of the sales order line will be updated with the actual warehouse cost when the order is
updated. However the stock movement still shows the original shipped cost. This also results in wrong
figures to be reported in the sales analysis report. This issue has been rectified.
Key Data
Module/Function: SO T017, SALE R056
When despatching sales orders using ScanPack, the sales order invoice date is not updated with the actual
delivery date. This issue has been rectified.
Key Data
Module/Function: SCAN M006
Table Entry:-
-Invoice layout > Misc Flag = 1 or 3
This new mode has been added for Global Tax type customers to enable the current global tax rate to be
changed and stamped as an override tax rate on rebates etc. sales orders.
Key Data
Module/Function: SO M053
Table Entry:-
-sys-tax-type = "G" [SYS.M157]
This new mode has been added for Global Tax type customers to enable the current global tax rate to be
changed and stamped as an override tax rate on rebates etc. sales orders.
Key Data
Module/Function: AR M313
Major Function Flags
-Sales Tax Type = "G"
The ordered and shipped amounts of a special sales order line created from customer charge entered during
ScanPack despatch do not contain tax amounts. This issue has been rectified.
Key Data
Module/Function: SCAN M006
For Canadian Tax System, the freight charge added to the sales order during despatch has no tax
component. This issue has been rectified.
Key Data
Module/Function: SO M287
If a form layout is designed to show or display the Tender Type and any values have been receipted on a
sale, this Tender Type changes after the sales order has been updated. This issue has been rectified.
Key Data
Module/Function: SO R028
When using [Correct] mode on an existing sales order, if the territory was changed, it changes the record to
be the new territory, but displayed the default territory on the screen. The default might be the customer
territory, or the cash drawer default territory or the warehouse, (or others) depending on the site set-up. The
program has been changed now so that the default is only displayed if the screen is in [Entry] mode.
Key Data
Module/Function: SO M053
Major Function Flags
-so-conclusion-flag = "9"
When the [Disc] mode was selected from the Sale Order Line entry screen, and then the option Other
Discount Options, followed by Total Sales Order Discount. After entering the details on the Apply Discount
screen, if the last line on the original order was a Note line, the system errored with an I/O error. This has
been corrected.
Key Data
Module/Function: SO M001
For Canadian Tax, the consolidated invoice is printing the incorrect values in the Totals section for the total
field codes Q, CW, KA, KB and AA. This issue has been rectified.
Key Data
Module/Function: SO R100
When a sales order is entered and no stock is available but is then shipped from another warehouse to the
sales order warehouse, a suffix order is raised for the transfer. If only part of the goods are transferred to the
sales order warehouse, another suffix order is created for the remaining stock. At this stage, if the goods that
are available are despatched, and an attempt is made to update the order, an I/O error may occur. This issue
has been rectified.
Key Data
Module/Function: SO T017
Major Function Flags
-Supply From Other Warehouse = "T", "A", "P"
1. Incorrect update of sales order/work order links, after the order has been split.
2. Linked work orders were not visible when the mode „Link to WO‟ was selected via the mode Extra/Extra
Options.
Key Data
Module/Function: SO M053
When option B is selected in the “Configuration Options” when adding a configured item to a sales order, a
work order for the subassembly is created but the work order number is not reported in the "Work Orders
Raised" report. This issue has been rectified
Key Data
Module/Function: SO M001
Major Function Flags
-Load Work Order by Factory = „Y‟
Table Entry:-
-PR/SO_ENTRY = m50consys/B
A Call being selected as „Non Serialised‟ was being saved as „Multiple‟. This issue has been rectified.
Key Data
Module/Function: SERV M032
Once call entry is complete the user is given an option screen to select the next action (Hold Call, Finish Call,
etc.). If you select Call Maintenance, Hold Call or Cancel Call you are exited from the call logging screen.
This was not the case in the previous release. This issue has been corrected by adding an option message-
box asking the user whether to return to call logging.
Key Data
Module/Function: SERV M116
Call Logging From Service Contract Not Setting Defaults from Contract
SDR:55207
Logging a call off a service contract should result in a number of contract values defaulting to the service call.
These include Service Centre, Caller, Phone Number of Caller, Customer Reference and Travel Zone. Some
of these were not being defaulted depending on how the Call was logged ie if Customer was entered first and
then the Contract selected , or the Contract entered first , or the Serial entered first. All the above Contract
values now default no matter how the Call was commenced.
Key Data
Module/Function: SERV M116
For the Canadian Tax System, creating a new customer while logging a call should allow user to enter the
province code and tax exemption flags.
Key Data
Module/Function: SERV M116
If you log a new call (without the wizard) on completion you are not prompted to enter notes any more. This
issue has been rectified.
Key Data
Module/Function: SERV M116
At call login if we change selected contract to something different, system didn‟t ask the user to select a new
serial item. Instead an error message was given at the call entry conclusion. This issue has been rectified.
Key Data
Module/Function: SERV M116
When adding notes to a service contract, the user id and the date-time stamp fields will now correctly display
the current user and time.
Key Data
Module/Function: SERV M118
A number of issues have been resolved concerning the default value of the call type when logging a call.
Key Data
Module/Function: SERV M116
The Cancel button in the „Service Engineer Transactions Found‟ screen was not working. This issue has
been rectified.
Key Data
Module/Function: SERV M096
When a sales order is created in docket entry and subsequently cancelled, the chargeout lines are not
reinstated for the project. This issue has been rectified.
Key Data
Module/Function: SERV M096
The maintenance of Notes is no longer allowed in the Repair History function of Contract Enquiry.
Key Data
Module/Function: SERV E003
Preferred Engineer, Consumables & Notes modes are enabled for record edit in Service Contract Enquiry.
Issues corrected.
Key Data
Module/Function: SERV E011
While logging a call in the 660 version of PRONT-Xi, site (contract) notes appeared early in the logging
procedure. In the 670 version of PRONTO-Xi, while these notes still exist in each contract, they do not
appear during the call logging process. This issue has been rectified.
Key Data
Module/Function: SERV M116
Title on the message box for confirmation of change of address has been rectified.
Key Data
Module/Function: SERV M096
Using CRM with only service contract enquiry access you maintain serial numbers. You can also access
contracts without any contract security. Issues corrected.
Key Data
Module/Function: CRM M001
Using CRM with only serial enquiry access you can no longer view the unit details. Insufficient access error to
SERV.M282 is returned. This issue has been rectified.
Key Data
Module/Function: CRM M001
When a Service Contract is used in conjunction with a Project, if the customer is changed on a contract this
must change in the Project as well. This issue has been rectified.
Key Data
Module/Function: SERV M118
Major Function Flags
-SYS.M069, Service System Method in {„1‟ „2‟}
This function was not defaulting the Contact and the Phone Number from the customer. This issue has been
rectified.
Key Data
Module/Function: SERV M116
When entering a new call against a service contract that does not have the status of „active‟, system forces
the user to enter a chargeable Call Type of „CA‟ or „WA‟. Even if a Call Type is selected that has the same
parameters as „CA‟, it is rejected. This issue has been rectified. Added same validations to wizard as well.
Key Data
Module/Function: SERV M116
When there is a default value in the “Critical Code” field, the exportable procedure „public-critical-date-time-
required‟ used to calculate the required date and time is not called. It is called correctly, however, when the
critical code field is modified. This issue has been rectified.
Key Data
Module/Function: SERV M116
After Call Login is completed, and when Fast Engineer Allocation is selected, there are 2 messages
appearing. These messages seem to be asking same question. This issue has been rectified..
Key Data
Module/Function: SERV M116
When loading engineer transactions into the timesheet screen, engineers with different service centre should
not be excluded.
Key Data
Module/Function: SERV M096
When allocating an engineer via Scheduled Tasks, the times entered on the allocation screen should
populate the start end times and allocated hours in the Engineer Scheduled Attendances
Key Data
Module/Function: SERV M096
Issues when accessing some transactions in Enquiry on Call screen. It allows entry/correct some records
specially notes. Issues corrected.
Key Data
Module/Function: SERV E002
Key Data
Module/Function: SERV M096
At the end of Call Logging more Fault Notes can be added. Any additions to the first line ie the Fault
description were not saved. This issue has been rectified.
Key Data
Module/Function: SERV M116
When copying a Contract the error „Customer does not exist‟ occurred when it should not. This issue has
been rectified.
Key Data
Module/Function: SERV M085
During the Closeout process, the message „Unable to find sales order 0‟ is misleading and has been
removed.
Key Data
Module/Function: SERV M096
If a docket entered and the order invoiced before finishing the call through the service order module, the
invoice number should display as it display the sales order no.
Key Data
Module/Function: SERV M032
During the Closeout process for a Service Call, a warning message "warning: outstanding
requisition/commitments exist" is displayed once to let the user know about existing un-receipted purchase
orders. If the goods are automatically received on a linked purchase order the purchase order status should
display as „goods updated‟.
Key Data
Module/Function: SERV M001
There was an overlap of lines on the Summary page. This issue has been rectified.
Key Data
Module/Function: SERV M297
In the Service Call Entry Wizard, at the Quoted Price prompt, the user will now be able to access the
Quotation Screen by using the F2 (Lookup Help) key.
Key Data
Module/Function: SERV M032
Key Data
Module/Function: SERV M116
The address entered for a call for a new customer was being carried over when the option „Next Call„ was
selected. This issue has been rectified.
Key Data
Module/Function: SERV M116
The non-serialized mode has been added to the Equipment/ Items for Contract screen.
Key Data
Module/Function: SERV M116
The Copy function allowed the entry of more than 2 characters. This issue has been rectified.
Key Data
Module/Function: INV M110
A call type can have a Proforma associated with it. Logging a call using this call type resulted in the project
created without any of the 24 fields of the Proforma header. This issue has been rectified.
Key Data
Module/Function: SERV M116
The Project code can now be changed for a copied Service Contract.
Key Data
Module/Function: SERV M118
If you are setup with Service Access but without Project Access you can still see project cost categories and
transactions. This issue has been rectified.
Key Data
Module/Function: SO M053
Major Function Flags
-SYS.M069, Service System Method = 2
Within the service/s10maint screen - Call Maintenance by Engineer console, add a read-only trigger against
call-backup-part-no. This appears to work successfully, however a duplicate field code is displayed on the
top left of the screen. This issue has been rectified.
Key Data
Module/Function: SERV E016
Invoking service/s10maint using the „-custmaint‟ and correct customer would take user straight to all of the
calls for that customer previously, but not anymore. This issue has been rectified.
Key Data
Module/Function: SERV M094
Once call is allocated to an Engineer using Service Scheduler, Notify Call option wouldn‟t notify the engineer.
It changes the status of the call only. This issue has been rectified.
Key Data
Module/Function: SERV M019
In „Call Maintenance by Call Number‟ (SERV.M096) selecting the „New Call‟ mode and passing just the
„Customer„ the user is asked to select the „Serial Number‟ twice. This issue has been rectified.
Key Data
Module/Function: SERV M096
The postcode could be blanked out when correcting the address if the suburb had been entered on line 4
(the suburb is normally entered on Line 3). This issue has been rectified.
Key Data
Module/Function: SYS M480
Invoice report should display the tax figures correctly from the sales order invoice details.
Key Data
Module/Function: SERV M296
When a service call is entered the engineer can be marked as „Notified‟. If the engineer then enters a
transaction type „N‟ (Non posting type) on exiting from this transaction the service call is returned to
„Allocated‟. This issue has been rectified.
Key Data
Module/Function: SERV T003
In a Canadian Tax System, if a service contract has a time zone with territory set up, the invoice created has
no tax component. This issue has been rectified.
Key Data
Module/Function: SERV M296
If you have enquiry only access to service (L2), which includes SERV.E003 (serial enquiry), when you access
the unit button from a call you get an error message with insufficient security to SERV.M282. This issue has
been rectified.
Key Data
Module/Function: SERV E002
The 2 user-defined fields on the create and maintain contract screens would not accept a Space unless this
was a defined code. This issue has been rectified.
Key Data
Module/Function: SERV M085
When in Call Maintenance by call number, the zone field is grey (this would usually indicate that the field is
read only), however upon selecting this field you are able to change the data. This issue has been rectified.
Key Data
Module/Function: SERV M096
When there are no pre-existing cheque/remittance layouts, there was a problem in going to EXTRA with a
message popping up „MUST enter an alternate layout for Remittances, if „Seperate Forms‟ is 0 or 1. This
issue has been rectified.
Key Data
Module/Function: SYS M383
Cannot Save and Exit Invoice Details screen of an „A‟ Type Invoice
SDR:55322
Cannot save and exit the Invoice Details screen after the full amount with tax has been entered for a type „A‟
invoice. This issue has been rectified.
Key Data
Module/Function: AP T020
User can now filter on description when on the line despatch screen.
Key Data
Module/Function: SO M287
When negative foreign transactions are entered in the Invoice Details screen, some of the transactions are
not converted to local currency for posting. This issue has been rectified.
Key Data
Module/Function: AP T020
1. The foreign invoiced amount including tax should not be modified due to rounding‟s from the posted local
tax amount. The exact entered foreign amounts should be used to avoid invoice discrepancy.
2. When an invoice is being approved, the screen totals are not calculated correctly if the base amount of the
GL other side transaction is being corrected.
Key Data
Module/Function: AP T020
„In-transit‟ purchase order is automatically set to „Completed‟ without goods receipt when the purchase order
is invoiced. This has now been modified to leave the status as „In-Transit‟.
Key Data
Module/Function: AP T020
When processing receipts, if a cash receipt is allocated to one customer, followed by an „Leave Un‟
(unallocated receipt) to the next customer, an incorrect error message appears with the reference from the
previous receipt. This issue has been rectified.
Key Data
Module/Function: AR T052
1. „P‟ type invoice for a contract purchase order is allowed to request authorisation. But when the invoice is
being posted, only one side of the GL is posted (i.e. CCTRL). When the invoice is authorised, no tax is
posted.
2. When a contract purchase order with normal stock item is invoiced without authorisation, the tax amount is
not posted.
3. A „P‟ type invoice for a contract purchase order requiring authorisation is posted. When it is being
authorised, the foreign amount posted to the supplier is rounded and does not match the original amount
posted by the „F‟; type invoice.
4. Tax amount can be modified if a new transaction is entered in the invoice details screen using tax inclusive
mode when invoice is being approved.
Key Data
Module/Function: AP T020
1) the base amount of the GL otherside which includes the provincial tax amount is not recalculated if the
provincial tax is being modified. This results in an unbalanced GL batch.
2) the base amounts in the unposted tax records are not recalculated if the federal tax is modified. This
results in wrong based amounts for the taxes being reported in tax tracking and analysis.
Key Data
Module/Function: AP T020
The verification of the invoice details screen total against the invoice total does not take account of the sign
of the dollar amount and screen entry mode (i.e. tax exclusive) of contract PO. This results in error message
„Transactions no longer balance to original invoice total. Please correct.‟ This occurs only if the contract PO
has a negative invoice total. This issue has been rectified.
Key Data
Module/Function: AP T020
This SDR contains details on how to upgrade the system when the Global Tax Rate (type G) is increased. A
method of ensuring future credit notes created against an invoice generated using the OLD tax rate, used the
old rate instead of the new tax rate. Please contact your support personnel for instructions on how to handle
this situation.
Key Data
Module/Function: SYS M195
While the user enters or corrects a user company startup sequence, the system module and function entered
will now be validated.
Key Data
Module/Function: SYS M195
If stock and non-stock limits were set to ZERO, the system was automatically setting the user to be Purchase
Officer = NO. Now, the system also checks to ensure requisition limit is also ZERO before doing so, to
enable a user to be set up as requisition only allowed.
Key Data
Module/Function: SYS M195
When entering a General Ledger cash payment to a foreign bank in tax inclusive mode, the entered tax
inclusive foreign amount is recalculated from the local amount and results in rounding. The „Balance to
Allocate‟ screen is now modified to use local currency for data entry and calculation.
Key Data
Module/Function: GL T004
When submitting a sequence name, the attached sequence numbers with Program Type set to Z were being
omitted. This issue has been rectified.
Key Data
Module/Function: SYS M176
Tax calculator is no longer available for type „P‟ and „R‟ type invoices when <F2> is pressed in the entry field
of currency amount. This issue has been rectified.
Key Data
Module/Function: AP T020
When tax record is manually entered in the tax details screen for „X‟ type invoices, the tax exemption code is
incorrect. It always copies from the tax record above. This issue has been rectified.
Key Data
Module/Function: AP T020
Tax records were not being created for variance orders created during supplier invoicing. This issue has
been rectified.
Key Data
Module/Function: AP T020
The amount posted to the WCLR account is incorrect and causes the G/L posting of a „R‟ type invoice for a
warranty claim to be out of balance. This issue has been rectified.
Key Data
Module/Function: AP T020
If a user creates a new company, then they are automatically set up as a user. However the masking for this
user in the company is empty. The person creating the company should have „????‟ for all masking. This
issue has been rectified.
Key Data
Module/Function: SYS M032
When invoices are entered with multiple purchase orders and Immediate withholding tax is used, the
withholding tax amount is incorrectly calculated. This issue has been rectified.
Key Data
Module/Function: AP T020
An error message is displayed when you attempt to setup the TrueForm Transmission window for the first
time or after the Reset Defaults button is selected. The message displayed reads „lf-folder: Invalid Check Box
value‟. This issue has been rectified.
Key Data
Module/Function: TFD M005
Stock on hold can be transferred into the LOST location but cannot be transferred out. This issue has been
rectified.
Key Data
Module/Function: WHSE M050
When there are 2 kit items on a sales order and one is short shipped on the total quantity , there is an extra
ZINVOICE record created for the already shipped components on the kit. This issue has been rectified.
Key Data
Module/Function: WHSE M013