momentumpro v3.1 sp5 patch 01 release notes · a remote desktop or citrix terminal server is...

MomentumPro® V3.1 SP5 Patch 01 Release Notes

MomentumPro® V3.1 SP5 Patch 01 Release Notes

Information in this document is subject to change without notice. Companies, names

and data used in examples herein are fictitious unless otherwise noted. No part of this

document may be reproduced or transmitted in any form or by any means, electronic

or mechanical, for any purpose, without the express written permission of Markinson

Technologies Pty Ltd.

© 2018 Markinson Technologies Pty Ltd. All Rights Reserved.

® MomentumPro is a registered trademark of Markinson Technologies Pty Ltd.

CONTACT MARKINSON BUSINESS SOFTWARE SOLUTIONS

Telephone: 1300 137 729

Email: [email protected]

Internet: www.markinson.com.au

[email protected]

www.markinson.com.au

momentumpro © 2014 Markinson Technologies Contents iii

Contents

1. Welcome to MomentumPro Enterprise V3.1 ............................................... 6

1.1 Prerequisites ......................................................................................... 6

1.2 Documentation Conventions ................................................................... 7

1.3 Minimum Product Requirements .............................................................. 8

1.3.1 Technical Specifications ............................................................... 8

1.4 Platform ............................................................................................... 8

1.5 Operating Systems ................................................................................ 8

1.5.1 Client ........................................................................................ 8

1.5.2 Application Server ....................................................................... 9

1.5.3 Database Server ......................................................................... 9

1.6 Remote Support .................................................................................... 9

1.7 Email Interface ................................................................................... 10

1.8 Network requirements .......................................................................... 10

1.9 Electronic Document Management ......................................................... 10

2. New Features in this release ................................................................... 12

2.1 Currency field expansion (Stage 2) ........................................................ 12

2.2 Product Pareto Classification by warehouse ............................................. 13

2.2.1 Maintenance and Inquiry of warehouse specific Pareto classes ........ 13

2.2.2 Automatic Inventory Ranking ..................................................... 14

2.2.3 Product filtering by Pareto Class .................................................. 15

2.2.3.1 Bulk Maintenance ................................................................. 15

2.2.3.2 Operational programs. ........................................................... 15

2.2.3.3 Reports and Exports .............................................................. 16

2.2.4 Product Import ......................................................................... 16

2.2.4.1 Inventory Detail record format ............................................... 16

2.3 Bulk Load/Update of Program Access ..................................................... 19

2.3.1 Access Security Import .............................................................. 19

2.3.1.1 Access Security Import – CSV data format ............................... 19

2.3.2 Example CSV Access Security Data ............................................. 20

2.3.3 Access Security Maintenance ...................................................... 20

2.3.4 Access Security Export............................................................... 26

2.3.4.1 Access security export data format ......................................... 27

3. Issues Resolved in this release ............................................................... 28

3.1 Accounts Payable ................................................................................ 28

3.1.1 Supplier Invoice Inquiry – Freight Amount not displayed ................ 28

momentumpro © 2014 Markinson Technologies Contents iv

3.1.2 Creditors Management Report excluding transactions .................... 28

3.1.3 Error matching a GRN line to a Supplier Invoice ............................ 28

3.2 Accounts Receivable ............................................................................ 29

3.2.1 Customer Inquiry Movements option slow .................................... 29

3.2.2 Total incorrect in Sales Analysis by Group .................................. 29

3.3 Administration .................................................................................... 30

3.3.1 Batch tasks rescheduled for wrong day ....................................... 30

3.4 Banking ............................................................................................. 31

3.4.1 Statement Date for bank account not updated ............................. 31

3.5 E-Gateway .......................................................................................... 32

3.5.1 Failed Supplier Invoice Import file incorrectly archived................... 32

3.6 Importing ........................................................................................... 33

3.6.1 Entered Quantity not refreshed in Import Shipment Receipts ......... 33

3.6.2 Session crashes when creating an A/P Sundry Credit Note ............ 33

3.7 Internal Distribution............................................................................. 34

3.7.1 Security applied incorrectly for Local shipment freight supplier ....... 34

3.8 Inventory ........................................................................................... 35

3.8.1 Supplier Product unable to be deleted via Product Import .............. 35

3.9 MomentumPro Integration .................................................................... 36

3.9.1 AddSalesOrderA API – Delivery sales ID not loaded ....................... 36

3.9.2 Original sell price not recorded in AddSaleLine API ....................... 36

3.10 Pricing ............................................................................................... 37

3.10.1 Price Schedules by Product – Screen Highlight Issue ..................... 37

3.11 Production .......................................................................................... 38

3.11.1 Productions Orders - Sundry Products Costed Incorrectly ............... 38

3.12 Sales Processing.................................................................................. 39

3.12.1 Sales Processing – Line Detail Screen Display Issue ...................... 39

3.12.2 Error when selecting S/Order option of Customer Quote Inquiry ..... 39

3.12.3 Invoices with sundry products in update error .............................. 39

3.12.4 No notification or event log for order commitment process failure ... 39

3.13 Service .............................................................................................. 41

3.13.1 Outstanding Order Balance incorrectly updated ............................. 41

3.13.2 Diary Option Slow in Service Orders .......................................... 41

3.13.3 Service order completion allowed with non-charged issues ............. 41

3.14 Warehousing ....................................................................................... 42

3.14.1 Stocktake Count Entry displays incorrect Count Totals ................... 42

3.14.2 Stocktakes that are set to “In Progress” can be deleted ................. 42

4. Database Schema Changes in this Release .............................................. 43

4.1 What you need to know........................................................................ 43

momentumpro © 2014 Markinson Technologies Contents v

4.2 Database Schema introduction .............................................................. 43

4.3 Changes to the live database ................................................................ 44

4.4 Changes to the markin Database ........................................................... 45

momentumpro Welcome to MomentumPro Enterprise V3.1 6

1. Welcome to MomentumPro Enterprise V3.1

Welcome to the Release Notes for MomentumPro® Enterprise V3.1.

These release notes feature the following sections outlining the requirements for running the

system, enhancements and bug fixes implemented in this release of the product:

Welcome

This section outlines the prerequisites, documentation conventions and system

requirements for MomentumPro® V3.1.

New Features in this release

This section describes any new or enhanced features released in V3.1 Service Pack 5

Patch 01 (7.05.01).

Issues Resolved in this release

This section describes issues identified in MomentumPro® that have been resolved in

the patch.

Database Schema changes in this release

This section describes updates to the Database Schema and any new changes

released in V3.1 Service Pack 5 Patch 01 (7.05.01).

1.1 Prerequisites

In order to install and utilise MomentumPro® V3.1, please ensure that the following

mandatory prerequisites are met:

Review Product Licence and Licence Agreement

Ensure that you have a valid product licence for your installation and you are familiar with

the MomentumPro® Licence Agreement. Licence details and the MomentumPro Licence

Agreement may be updated periodically and must be reviewed following installation of

each patch update. The licence details and a current copy of the Licence Agreement are

recorded to the MomentumPro® database.

To view your licence details, launch your MomentumPro® Desktop, click on the Help

menu and select the About option to display the About MomentumPro screen. The

Licence Agreement may also be viewed via the Licence button on this screen.

Review the MomentumPro® Technical Specifications

Ensure that the current MomentumPro® Technical Specifications for V3.1 have been

reviewed and the appropriate steps taken to prepare your install environment.

MomentumPro® Installation Checklist Completed

Ensure that the current Installation Checklist for MomentumPro® V3.1 has been

completed prior to attempting patch update installation.


1.2 Documentation Conventions

The following conventions are used in this documentation:

FEATURE CONVENTION

Module or Function Title All indicated within the content of this document using

BOLD CAPITALISED text.

Example:

Maintaining Settings in the SUPPLIER

MAINTENANCE module.

Screen or Window Title All indicated within the content of this document using

Bold Italic text.

Example:

Select the supplier from the Supplier type dialog.

Buttons, Drop-down Lists, Radio Buttons,

Fields and Keyboard Keys

All indicated within the content of this document using

Bold text.

Example:

Press Ctrl+P on your keyboard then click on the OK

button.


1.3 Minimum Product Requirements

Configuration of your MomentumPro® system is dependant upon your existing or proposed

infrastructure, number of users and whether the system will be hosted from a local base, or

installed as part of a distributed system (client/server delivering a thin client solution).

Markinson highly recommends consulting a certified professional regarding these

specifications prior to configuring a server for your MomentumPro® solution.

Note

The following specifications are guidelines only and are subject to change without notice.

The base requirements for the install and implementation of MomentumPro® are outlined

below.

1.3.1 Technical Specifications

Technical Specifications have been produced to cater for the numerous install options and

environments upon which a MomentumPro® system may be installed, rather than being

incorporated in each set of release notes and installation guides.

The Markinson Support web site (http://support.markinson.com.au) features product

support documentation including Technical Specifications for all product versions.

1.4 Platform

The following runtime packages are required for MomentumPro® Enterprise V3.1 (SP5):

Progress OpenEdge 11.7 RDBMS

Progress OpenEdge 11.7 ABL

Java 1.8.0 (Provided with OpenEdge 11.7)

Microsoft .NET 4.0

1.5 Operating Systems

Operating systems required to run MomentumPro® Enterprise V3.1 (SP5) are outlined

below.

1.5.1 Client

The MomentumPro® Enterprise Client requires a supported Microsoft Windows PC, Windows

Terminal Server or Server image with .NET 4.0 or later installed. The following Windows PC

and server platforms are supported by MomentumPro® Enterprise V3.1 (SP5) with

OpenEdge 11.7 (32-bit client):

Windows 10

Windows 8.1

Windows 8

Windows 7

Windows Server 2012 R2

Windows Server 2012


http://support.markinson.com.au/


1.5.2 Application Server

The MomentumPro® Application Servers require a Microsoft Windows Server or Server

image supporting OpenEdge 11.7 Enterprise Application Server. For MomentumPro®

Enterprise implementations with a user count exceeding 25 users a dedicated server is

required. For user counts less than 50 users the application server and database server

may be consolidated to a single dedicated server installation. The following Windows Server

platforms are supported by MomentumPro® Enterprise V3.1 (SP5) and OpenEdge 11.7 (64-

bit and 32-bit):

Windows Server 2016 (64-bit only)


Windows Server 2012


1.5.3 Database Server

A dedicated database server is required for MomentumPro® Enterprise implementations with

a user count exceeding 50 users. The following database server platforms are supported by

MomentumPro® Enterprise V3.1 (SP5) and OpenEdge 11.7 (64-bit):

HP

o HPUX 11i v3

Microsoft

o Windows Server 2016

o Windows Server 2012 R2

o Windows Server 2012

o Windows Server 2008 R2

Sun

o Solaris (Versions: 10 & 11)

IBM

o AIX (Versions: 6.1 & 7.1)

Linux

o SUSE Enterprise Server (Version: 11 SP3)

o SUSE (Version: 12)

o CentOS (Versions: 6.6 - 7.4)

o Red Hat (Versions: 6.6 – 7.4)

o Oracle Linux (Versions: 6.6 – 7.4)

o Ubuntu (Version: 16.04 LTS)

1.6 Remote Support

For remote support purposes, Markinson Support Services requires the following:

Broadband Internet access via a secure port on the firewall.

Remote Desktop or Citrix Terminal Services access

FTP access for file transfer

Access is required to all MomentumPro servers


1.7 Email Interface

Access is required from the MomentumPro Application Server to a SMTP Mail Server for

system generated email notifications. Outbound SMTP Authentication restrictions on the

SMTP mail server are not supported. For mail servers requiring SMTP Authentication an

SMTP Relay server is required.

1.8 Network requirements

LAN

A LAN speed of 100 Mbps (100baseT) or better utilising TCP/IP Network Protocol is required

for effective communications between the MomentumPro servers and the MomentumPro

client installations.

WAN

A Remote Desktop or Citrix Terminal server is required for users remotely accessing the

MomentumPro Client.

1.9 Electronic Document Management

To fully support printing, faxing and emailing of documents (e.g. Customer Invoices,

Customer Statements and Supplier Purchase Orders etc.) MomentumPro® Enterprise V3.1

(SP4) requires integration with a Document Management solution:

The following Document Management products are currently supported.

BottomLine Transform 5.x (preferred solution)

Optio Transform Integration Sever - OTIS 8.0

Optio eComintegrate 7.7 (Legacy support)

o Requires Windows Server 2003 – 32bit

Aia ITP (Legacy support)

A separate Windows server is recommended for the Document Management Host server.

Specific server requirements are dependent upon the DM product implementation.

Support for faxing of documents requires implementation of a faxing solution. The following

solutions are currently supported.

For BottomLine Transform and OTIS 8.0:

o Bottomline Fax

o Internet Faxing solution

Please contact Markinson to discuss specific solutions

For Optio eComintegrate:

o OptioFax (Legacy support)

Requires Windows Server 2003 – 32bit



For Aia ITP

o Windows Fax (Legacy support)




Fax hardware (not required for Internet Faxing solution)

Brooktrout fax router (preferred for OptioFax)

Multi-Tech Class 2 fax modem (preferred for BottomLine Fax)

o Please contact Markinson for specific device requirements

Class 2 Serial fax modem

o Note: Use of a non-preferred fax modem will be subject to customer testing

and verification.

Printer hardware

The supported printers are dependent upon the specific Document Management host

solution installed.

The Optio eComintegrate 7.7 and OTIS 8.0 products have limited printer support.

Printers providing Postscript or PCL5e (plus TrueType Arial font) capability are

recommended. PCL6 printers are not supported by these products.

Document emailing

Access to an SMTP internet mail server is required from the Document Management

host server

momentumpro New Features in this release 12

2. New Features in this release

This section details the updates or enhancements to MomentumPro® implemented in patch

release 7.05.01 of MomentumPro® V3.1.

2.1 Currency field expansion (Stage 2)

The second stage of development to implement support for recording of low value currency

amounts in MomentumPro® has been completed in this release. Increased field sizes allow

MomentumPro to enter, display and operate using low value currencies such as the Thai

Baht and Philippine Piso.

Currency fields on screens throughout MomentumPro® have been modified to support entry

and display of currency amounts up to 999,999,999,999.99 for unit values and

99,999,999,999,999.99 for document totals. Default screen sizes and screen layouts have

also been altered where necessary to accommodate the larger field sizes.

As noted above, the increased field sizes now support entry and display of low value

currency amounts on all MomentumPro screens. Field sizes for MomentumPro reports and

standard MomentumPro document layouts however have not yet been updated. Any

currency amounts recorded in MomentumPro utilising the increased currency field sizes will

result in field size errors on the standard report outputs.

Development is planned for future MomentumPro® releases to provide reporting capability

for the extended currency values.

Note: Any changes required to customised documents or reports to accommodate the

increased field sizes may be requested via the Markinson Professional Services team.


2.2 Product Pareto Classification by warehouse

New functionality has been implemented for products allowing product Pareto classifications

to be assigned and maintained by warehouse entity. Pareto classifications may now

optionally be assigned to a product for each warehouse entity.

If a class is assigned to a product for a specific warehouse the warehouse class will be used

in place of the product class when performing operations for the warehouse. If a specific

warehouse class is not assigned the Pareto class assigned to the product record will be used.

2.2.1 Maintenance and Inquiry of warehouse specific Pareto classes

The warehouse Pareto class can be updated for individual warehouses by selecting the

Reorder option on the Product Details By Warehouse screen following drilldown on a

specific warehouse from Details by W/H screen in the PRODUCT MAINTENANCE

program. The warehouse specific classes may also be maintained for a product via the same

function in the PRODUCT DETAILS BY WAREHOUSE program.

The warehouse Pareto class field can be viewed on the Inventory Inquiry Reorder

Details screen in the INVENTORY INQUIRY program via drilldown of a warehouse on the

Reorder – Settings by W/H option.


2.2.2 Automatic Inventory Ranking

The AUTOMATIC INVENTORY RANKING program has been updated to provide ability to

set the specific warehouse Pareto classes. If a warehouse entity is selected in the

Warehouse field on the View Selection page the Inventory pareto class option will be

automatically defaulted in the Update to field on the Target field to Update wizard page.

When the ranking function is performed with this option selected the warehouse specific

classes will be updated to the products for the selected warehouse entity.


2.2.3 Product filtering by Pareto Class

2.2.3.1 Bulk Maintenance

The following bulk update programs have been enhanced to utilise the warehouse Pareto

classes when filtering products for updates processed with a specific warehouse selected.

When a specific warehouse is chosen for an update operation and a Pareto class is selected

in the product filter criteria any warehouse specific Pareto classes assigned to the products

will be used when filtering the products to be updated.

SET REORDER PARAMETERS IN BULK

AUTOMATIC PRICE UPDATE

SET PRODUCT DETAILS IN BULK

ASSIGN BARCODES IN BULK

CALCULATE REORDER PARAMETERS

SET PRICING PARAMETERS IN BULK

2.2.3.2 Operational programs.

The following operational processing programs have been updated to implement product

filtering utilising the warehouse Pareto classes when applicable. If a Pareto class is assigned

in the product filter criteria and a specific warehouse is selected, any Pareto classes defined

for the warehouse will be used when filtering the products. Similarly when performing

operations where a Distribution network is selected the Pareto classes defined against the

products for the main/distribution warehouse will be used.

CUSTOMER BACKORDER PROCESSING

CUSTOMER BACKORDER RUNS

PRODUCTION ORDER PROCESSING

PRODUCTION ORDER RUN

PURCHASE ORDER PROCESSING


PURCHASE ORDER RUN

PUT AWAY PROCESSING

2.2.3.3 Reports and Exports

As described above for the bulk update and operational programs the reports and data

export programs throughout MomentumPro have been updated to implement product

filtering utilising the warehouse Pareto classes where applicable.

In addition to the product filtering reports and exports have been updated to use warehouse

specific Pareto classes when generating report output including product Pareto classes.

Warehouse Pareto classes will be displayed on the relevant reports whenever the report

content relates product details for a specific warehouse. If the report output represents

consolidated details for multiple warehouses or non-warehouse specific content is displayed

the Pareto classes from the product master records will be used.

2.2.4 Product Import

The PRODUCT IMPORT program has been updated to include ability to assign and update

the warehouse specific Pareto classes.

2.2.4.1 Inventory Detail record format

The Inventory Detail record (Record type – Inventory) format has been updated to provide

a new ParetoClass field allowing the Pareto class for an inventory record to be assigned.

Inventory Detail (Record type – Inventory)

CSV COLUMN LABEL DESCRIPTION COMMENT

RecordType Record type

§

Type Inventory required

for all inventory detail records

RecordAction ‘A’ – Add or Amend,

‘D’ – Delete

If a RecordAction is not

specified, ‘A’ will be assumed.

ProductCode Product code

§

ProductGroup Product group code

§

Inventory-Warehouse Inventory detail

warehouse §

Inventory-SalesStatus Sales Status

(Standard, Kitting,

Not To Be Sold)

If SalesStatus is not

specified, ‘Standard’ will be

assumed.

Inventory-KitStatus Kit Status (Sell As Kit,

Sell As Components, Prompt When Used)

KitStatus will be ignored if

SalesStatus is not ‘Kitting’.

If KitStatus is not specified

‘Sell As Kit’ type will be assumed.

Inventory-MinimumSellQuantity Minimum sell quantity

Inventory-SalesAuditCode Sales Audit Code



Inventory-BasePrice Warehouse Base Price BasePrice will be ignored if

Separate warehouse pricing

is not enabled for the

warehouse.

Inventory-RetailPrice Warehouse Retail

Price

RetailPrice will be ignored if

Separate warehouse pricing

is not enabled for the warehouse.

Inventory-ProductPriceCode Warehouse Price Code

Inventory-ReorderStatus Reorder Status

(Standard,

Production Order,

Do Not Reorder)

If ReorderStatus is not

specified, ‘Standard’ will be assumed.

Inventory-PurchasingRestriction Purchasing Restriction

(Any Supplier,

Internal Suppliers

Only,

Main Supplier Only, Listed Suppliers Only)

If PurchasingRestriction is

not specified, ‘Any Supplier’ will be assumed.

Inventory-ReorderStrategy Reorder Strategy (

24 Mths Avg Sales,

24 Mths Conditional,

12 Mths Avg Sales,

12 Mths Conditional,

6 Mths Avg Sales,

6 Mths Conditional,

3 Mths Avg Sales,

3 Mths Conditional,

12 Mths Weighted

Avg,

12 Mth Wedighted

Cond,

Low Volume,

Firm Orders Only,

Seasonal,

Reverse Weighted

Avg,

Rev Weighted Cond)

If ReorderStrategy is not

specified, the configured default will be assumed.

Inventory-MaximumHolding Maximum holding

quantity

Inventory-ReorderPoint Reorder point

quantity or days

Inventory-SafetyStock Safety stock quantity

Inventory-MinimumOrderQuantity Minimum order quantity

Inventory-BuyMultiples Buy multiple quantity

Inventory-StockCover Stock cover days

Inventory-FutureTrend Future trend

percentage



Inventory-ReviewPeriod Review period days

Inventory-OverrideForecast Override forecast

quantity

Inventory-ClearOverrideForecast Clear and disable the

override forecast quantity

Yes or No

Inventory-OrderLeadTime Production order lead

time days

OrderLeadTime will be

ignored if reorder status is

not ‘Production order’.

Inventory-BuildTime Production order build

time days

BuildTime will be ignored if

reorder status is not ‘Production order’.

Inventory-ProductionPrinter Production printer ProductionPrinter will be

ignored if reorder status is not ‘Production order’.

Inventory-ParetoClass Warehouse Pareto

classification (A –

Z)

Inventory-LastCost Last purchase cost

Inventory-LastOriginalCost Last purchase cost in

original currency

Inventory-LastCostCurrency Last purchase cost

currency code

§ - Denotes mandatory column required for all inventory detail records

Unless otherwise noted above, the field types, size limitations and validation requirements

for the fields of the inventory detail record correspond with the equivalent fields in the

Product Details by Warehouse screens of the PRODUCT MAINTENANCE program.


2.3 Bulk Load/Update of Program Access

2.3.1 Access Security Import

A new ACCESS SECURITY IMPORT program has been implemented providing ability to

import access security details from a Comma Separated Values (CSV) data file. The import

program allows access details for programs, program folders and program options to be

updated for one or more MomentumPro security policies.

The CSV data format requires data columns to be provided according to the data format

described below. The order of the columns in the data file is not important, however each

column must be identified with a column header and the headers for all columns containing

data to be imported must be provided exactly as shown in the CSV Column Label column

of the data format table below. For convenience additional columns may be included in the

data file containing reference details etc. Any column with an unrecognised header will be

automatically ignored by the import.

During processing of the data import file the access security data will undergo three stages

of validation and processing.

The first stage of validation will verify the data format ensuring the basic data file

structure and content is correct. If the data file fails the first stage validation the

entire file will be rejected.

The second stage of validation will apply rules equivalent to the validation that would

occur if the access security data was created, deleted or maintained manually (e.g.

ensure that the item/program ID and access mode are valid). Any records that fail

during this stage will be flagged and will not be processed. The import program will

provide two options for processing in this situation.

Option 1: The import program will log details of the failures and will continue

processing to stage 3 below.

Option 2: The program will log details of the failures and will not proceed to stage 3.

During the third stage all valid records will be processed. Any processing errors for

individual access security data records occurring during this stage will be recorded to

the import log. Processing will continue until all valid records have been processed.

The validation log report will be generated for all data imports. The log report will contain

details of any validation errors occurring during the import process. Each log entry will

describe the validation error that occurred and will reference the relevant line number in the

import data file. The log report will also contain a summary of the records processed by the

import operation.

2.3.1.1 Access Security Import – CSV data format

The first row of the data file must contain the header labels identifying each column. The

individual labels for each column must be recorded in the header exactly as shown in the

data format table below. The columns in the data file may be provided in any order and with

the exception of the mandatory columns, the data file must include only the fields you wish

to assign or update.

Access Security Import data format CSV COLUMN

LABEL DESCRIPTION COMMENTS

RecordAction ‘A’ – Add or Amend

‘D’ - Delete

If a RecordAction is not specified, ‘A’

will be assumed.

SecurityPolicy Security policy code

§

Type Item type

§

(Program, Option, Work Groups Folder

or Modules Folder)

Program Program name/description

§ e.g. Customer Inquiry


CSV COLUMN

LABEL DESCRIPTION COMMENTS

Detail Option or Folder name

§§

Access

‘Full Access’

‘No Access’

‘Default’

§§§

‘Default’ access is valid for Program,

Work Groups Folder and Modules

Folder types only.

§ - Denotes mandatory column required for all Access Security records

§§ - Denotes mandatory column required for Program Options or Folder items only

§§§ - Denotes mandatory column required for RecordAction ‘A’ – Add or Amend records only

2.3.2 Example CSV Access Security Data

RecordAction,SecurityPolicy,Type,Program,Detail,Access

A,A1,Program,Customer Maintenance,,No Access

A,A1,Program,Credit Arrangement Maintenance,,No Access

A,A1,Program,A/R Credit Control in Bulk,,No Access

A,A1,Program,Set Customer Details in Bulk,,No Access

A,A1,Program,Credit Control,,No Access

A,A1,Program,Debtors Period Rollover,,No Access

A,A1,Program,A/R System Configuration,,No Access

D,A1,Program,Credit Notes,,

A,A1,Program,A/R Diagnostics,,Default

A,A1,Modules Folder,,Accounts Receivable - Maintenance,No Access

A,A1,Option,Billing Contract Maintenance,Billing Contract - Customers,No Access

In the example above:

The first row in the data is a Header/Labels row. This row identifies the content of

each column of data in the CSV file.

Rows 2 – 8 are defined to Add or Amend access security for the specified items. ‘No

Access’ will be assigned to the ‘A1’ security policy for each of these items.

Row 9 is defined to delete the access security from the ‘A1’ policy for the ‘Credit

Notes’ program item. Following the access security delete operation the item in the

policy will revert to the default access mode (i.e. ‘Default(No Access)’ or ‘Default(Full

Access)’) for the ‘A1’ policy.

Row 10 has is defined with an Add or Amend action however the Access column is

defined as ‘Default’. The ‘A/R Diagnostics’ program will therefore be reset to the

Default access in the security policy in the same manner as would occur for the

delete operation specified for row 9.

Row 11 will assign ‘No Access’ in the ‘A1’ policy for the ‘Accounts Receivable –

Maintenance’ ‘Modules Folder’

Row 12 will assign ‘No Access’ in the ‘A1’ policy for the ‘Billing Contract - Customers’

option in the ‘Billing Contract Maintenance’ program

2.3.3 Access Security Maintenance

A new ACCESS SECURITY MAINTENANCE program has been added to the MomentumPro

administration menu. The new program provides ability to maintain access for programs,

program folders and program options against specific security policies. The new

maintenance program includes the following features:

Copy access security details from another policy.

Assign access security to individual programs or program options.

Select multiple programs and/or options for a policy to assign access security.


Reset/remove previously assigned access security for one or more selected

programs, menu folders and/or options in a policy.

Following selection of a valid security policy from the main screen of the ACCESS

SECURITY MAINTENANCE program, all programs and menu folders are listed in the grid

with the applicable access setting shown for each of the listed items. If access has not be

explicitly assigned for an item in the policy, the access will be displayed as either

Default(Full Access) or Default(No Access) according to the Default Program Access

configuration setting.

The programs and menu folders listed in the grid may be filtered using one or more of the

following filter parameters.

Type – item/entry type (e.g. Program Folder, Program Option, Inquiry, Maintenance,

etc.)

Module – Application module (e.g. Accounts Receivable, Accounts Payable, Sales

Processing, etc.)

Access – Access assignment (i.e. Default, Full Access, No Access)

Individual items may be selected and deselected in the grid by highlighting the applicable

row and pressing the Spacebar. ‘Yes’ will be displayed in the Sel column for any row that

has been selected. The Select button in the toolbar below the grid may be used to select or

deselect all rows in the grid. If one or more items in the grid have been selected and the

Select button is pressed all the selected items will be deselected. If the Select button is

pressed and there are currently no items selected all the items listed will be selected.

The Process (F2) button may be selected from the toolbar below the grid to update the


selected items. The following processing actions allow the access for the items selected in

the grid (i.e. Sel column contains ‘Yes’) to be updated.

Assign FULL ACCESS for selected items

o This action may be used to assign Full Access to the selected items.

Assign NO ACCESS for selected items

o This action may be used to assign No Access to the selected items.

RESET Access for selected items

o This action may be used to reset or remove any explicit access security

assigned to the selected items. Security for the selected items will revert to

the default access security mode (i.e. either Default(Full Access) or

Default(No Access)

Access security for the options associated with a specific Program type item may be viewed

and maintained via drilldown on the grid. Upon drill down of a Program item the Program

Options screen will be displayed listing any options for the selected item. The current

access security setting for each option will be displayed as either Full Access or No Access.


As with the grid on the main Access Security Maintenance screen individual program

options may be selected and deselected in the options grid by highlighting the applicable

row and pressing the Spacebar. The Select button in the toolbar below the grid may be

used to select or deselect all rows in the grid. The Process (F2) grid toolbar button may be

pressed to update the selected rows. The following processing actions allow the access for

the selected options (i.e. Sel column contains ‘Yes’) to be updated.

Assign FULL ACCESS for selected items

o This action may be used to assign Full Access to the selected items.

Assign NO ACCESS for selected items

o This action may be used to assign No Access to the selected items.


Functionality has been provided in the maintenance program to copy access details from

another security policy via a Copy Access button on the program toolbar of the main

Access Security Maintenance screen.

When the Copy Access button is selected a Copy Access Security screen is displayed

providing ability to select a security policy to copy from along with a number of other

parameters for the copy operation. The following parameters are provided:

Security policy – The policy to copy from (i.e. source policy)

Filter options

Type – The item/entry type (e.g. Program Folder, Program Option, Inquiry,

Maintenance, etc.)

Module – Application module (e.g. Accounts Receivable, Accounts Payable, Sales

Processing, etc.)

Include program options – Include program options when copying items

Processing options

Overwrite existing access security

o If selected, access security for individual items in the target security policy

will be overwritten by the explicit access security details copied from the

source policy


2.3.4 Access Security Export

A new ACCESS SECURITY EXPORT program has been implemented providing ability to

export access security details for one or more security policies. The export program

produces a Comma Separated Values (CSV) data file containing the access security details

including columns and data values required for the ACCESS SECURITY IMPORT program

plus additional columns providing descriptive details for each item.

The export wizard provides an option to specify a Security policy to restrict the exported

access details. If a security policy is not provided the export will include access details for all

security policies. In addition to the Security policy the following filter criteria is also

provided.

Type - The item/entry type (e.g. Program Folder, Program Option, Inquiry,

Maintenance, etc.)

Access - Access assignment (i.e. Default, Full Access, No Access)

Module - Application module (e.g. Accounts Receivable, Accounts Payable, Sales

Processing, etc.)

Include program options

o If this flag is selected the export will include access details for program option

Include items with no explicit access assigned

o If this flag is selected the export will include items with a Default access

mode


2.3.4.1 Access security export data format

The ACCESS SECURITY EXPORT produces a CSV data file with the following columns.

CSV COLUMN

LABEL DESCRIPTION

SecurityPolicy Security policy code

Type Item type (Program, Option, Work Groups Folder or Modules Folder)

TypeDescription Item type description/additional detail

Group Module name or Menu folder

Program Program name/description

Detail Folder name or Program Option

Access Access (‘Full Access’, ‘No Access’ or ‘Default’)

momentumpro Issues Resolved in this release 28

3. Issues Resolved in this release

This section provides a summary of product issues resolved since the last release of

MomentumPro®, organised by module and function.

3.1 Accounts Payable

3.1.1 Supplier Invoice Inquiry – Freight Amount not displayed

ISSUE:

An issue has been identified causing the freight value recorded to a supplier invoice to not

be displayed in the Invoice/GRN Detail screen of the SUPPLIER INVOICE INQUIRY

program. This issue only occurred when the freight was recorded for a separate freight

supplier account.

RESOLUTION:

This issue has now been resolved. The freight value is now correctly displayed in the

SUPPLIER INVOICE INQUIRY program.

3.1.2 Creditors Management Report excluding transactions

ISSUE:

Issue identified affecting the CREDITORS MANAGEMENT REPORT.

The CREDITORS MANAGEMENT REPORT was incorrectly excluding transactions for any

creditor account that was inactive.

RESOLUTION:

The CREDITORS MANAGEMENT REPORT is now including transactions for inactive

creditor accounts.

3.1.3 Error matching a GRN line to a Supplier Invoice

ISSUE:

Issue identified affecting the SUPPLIER INVOICE ENTRY program.

When matching an entire GRN line to a supplier invoice in the SUPPLIER INVOICE ENTRY

program, the following error message was incorrectly displayed if the line has a conversion

factor.

The entered selected quantity/unit conversion will result in an invalid stock quantity.

This error only occurred when the quantity was entered in the Line Details screen.

RESOLUTION:

Errors regarding invalid quantities/unit conversions are no longer displayed when matching

a GRN line to a supplier invoice in the SUPPLIER INVOICE ENTRY program.


3.2 Accounts Receivable

3.2.1 Customer Inquiry Movements option slow

ISSUE:

Issue identified affecting the Movements option of CUSTOMER INQUIRY.

The Movements option of the CUSTOMER INQUIRY program was very slow and could take

several minutes for the movements to be displayed in the grid.

RESOLUTION:

There is no longer a large delay when selecting the Movements option of CUSTOMER

INQUIRY.

3.2.2 Total incorrect in Sales Analysis by Group

ISSUE:

Issue identified affecting the Sales Analysis by Group option of CUSTOMER INQUIRY.

When filtering group sales by a particular entity in the Sales Analysis by Group option of

CUSTOMER INQUIRY the totals displayed in the grid was the total for all entities rather

than the total for the entered entity.

RESOLUTION:

The totals are now correct in the Sales Analysis by Group option when filtering by a

particular entity.


3.3 Administration

3.3.1 Batch tasks rescheduled for wrong day

ISSUE:

Issue identified affecting the rescheduling of batch tasks.

Batch tasks that were scheduled to run on the last day of the month ran a day early. The

batch task initially ran on the correct day, but the re-scheduling process incorrectly set it to

run a day early for the following month.

RESOLUTION:

Batch tasks are now rescheduled to the correct day when they are set to run on the last day

of each month.


3.4 Banking

3.4.1 Statement Date for bank account not updated

ISSUE:

Issue identified affecting the BANK RECONCILIATION REPORT and SET BANK A/C

OPENING BALANCE programs.

The bank account statement date displayed in the BANK RECONCILIATION REPORT and

SET BANK A/C OPENING BALANCE programs was never updated.

RESOLUTION:

This Statement Date is no longer required and has been removed from these programs.


3.5 E-Gateway

3.5.1 Failed Supplier Invoice Import file incorrectly archived

ISSUE:

Issue identified affecting the E-Gateway SUPPLIER INVOICE IMPORT.

When an E-Gateway Supplier invoice import failed due to invalid data the import file was

incorrectly saved to the inbound/archive folder instead of the reject folder.

RESOLUTION:

Failed supplier invoice import data files are now correctly saved to the E-Gateway

inbound/reject folder.


3.6 Importing

3.6.1 Entered Quantity not refreshed in Import Shipment Receipts

ISSUE:

Issue identified affecting the IMPORT SHIPMENT RECIEPTS program.

When entering the serial details of a serially tracked product using the Put Away option of

IMPORT SHIPMENT RECEIPTS, the entered quantity in the grid was not refreshed,

leading the user to think the details may not have been entered.

RESOLUTION:

The entered quantity is now refreshed correctly after entering serial tracked products in

IMPORT SHIPMENT RECEIPTS.

3.6.2 Session crashes when creating an A/P Sundry Credit Note

ISSUE:

Issue identified affecting the A/P SUNDRY CREDIT NOTES program.

When processing a Credit Note in the A/P SUNDRY CREDIT NOTES program the

MomentumPro session would sometimes freeze up and then crash. This occurred when

crediting an A/P Sundry Invoice that had been assigned and then de-assigned from an

Import Shipment.

RESOLUTION:

A/P Sundry Credit notes can now be successfully processed without the session crashing.


3.7 Internal Distribution

3.7.1 Security applied incorrectly for Local shipment freight supplier

ISSUE:

Issue identified affecting the LOCAL SHIPMENT RECEIPTS program.

When recording freight charges via the Freight Charge Details screen in the LOCAL

SHIPMENT RECEIPTS program, if the selected freight supplier account was restricted and

the supplier’s restriction did not include the supplying warehouse entity the supplier was

incorrectly blocked.

RESOLUTION:

The LOCAL SHIPMENT RECEIPTS program now correctly applies usage security

restrictions for the freight supplier account. Restricted supplier accounts may now be

selected on the Freight Charge Details screen as long as the usage restriction includes the

delivery warehouse entity.


3.8 Inventory

3.8.1 Supplier Product unable to be deleted via Product Import

ISSUE:

Issue identified affecting the PRODUCT IMPORT program.

When attempting to delete a supplier product by entering a RecordAction of ‘D’ in the

product import file an error was incorrectly displayed when the PRODUCT IMPORT

program was run stating that the supplier product does not exist. The supplier product was

not deleted.

RESOLUTION:

Supplier products can now be deleted without error in the PRODUCT IMPORT program.


3.9 MomentumPro Integration

3.9.1 AddSalesOrderA API – Delivery sales ID not loaded

ISSUE:

When creating a new sales order via the AddSalesOrderA API, the sales ID recorded to the

sales order delivery section is not being saved to the resulting sales order document in

MomentumPro.

RESOLUTION:

The AddSalesOrderA API has been updated to correctly record the provided sales ID from

the sales order delivery section to the sales order document.

3.9.2 Original sell price not recorded in AddSaleLine API

ISSUE:

Issue identified affecting customers using the AddSaleLine method of the Sales Processing

Web Services class.

The original sell price and discount fields are not being recorded to the sales document via

AddSalesLine method.

RESOLUTION:

The original sell price and discount fields are now recorded to the sales document via the

AddSalesLine method.


3.10 Pricing

3.10.1 Price Schedules by Product – Screen Highlight Issue

ISSUE:

When editing prices in the PRICE SCHEDULES BY PRODUCT program, a screen issue may

occur causing the text highlight in the currently selected field to lose highlight. This use was

required to reselect the text in the required field to overwrite the value.

RESOLUTION:

This issue has now been resolved. The text highlighting is now maintained correctly in the

program.


3.11 Production

3.11.1 Productions Orders - Sundry Products Costed Incorrectly

ISSUE:

When using the START PRODUCTION ORDERS program to initiate production jobs, it was

possible for sundry item movements to be recorded with an incorrect cost value. This issue

only occurred when multiple fixed cost sundry items were issued on the same production

order from within the START PRODUCTION ORDERS program.

RESOLUTION:

The START PRODUCTION ORDERS program has now been updated to correctly apply the

cost for each fixed cost sundry item in a production order.


3.12 Sales Processing

3.12.1 Sales Processing – Line Detail Screen Display Issue

ISSUE:

An issue has been identified in the SALES PROCESSING program causing the Sales

Processing Line Details screen to popup unexpectedly at the end of the sale completion

process. This issue only occurred for sales requiring a cash payment and only when the OK

button on the SALES PROCESSING main screen was selected using the Enter key.

RESOLUTION:

This issue has now been resolved. The SALES PROCESSING program has now been

corrected to ensure the Sales Processing Line Details screen is not prompted at the end

of the sales process.

3.12.2 Error when selecting S/Order option of Customer Quote Inquiry

ISSUE:

Issue identified affecting the S/Order option of CUSTOMER QUOTE INQUIRY.

The following error was displayed when selecting the S/Order option of CUSTOMER

QUOTE INQUIRY whenever the sales order was not available.

Could not evaluate publisher handle expression while trying to execute SUBSCRIBE

statement. (6464)

RESOLUTION:

Errors are no longer displayed when selecting the S/Order option of CUSTOMER QUOTE

INQUIRY.

3.12.3 Invoices with sundry products in update error

ISSUE:

Issue identified affecting the OPEN INVOICES program.

When reducing the supplied quantity of a sundry product in the OPEN INVOICES program

and then processing the invoice then the invoice would go into update error because the line

totals did not agree with the invoice total. The invoice total was incorrect and was did not

take into consideration the reduction of the sundry product’s supplied quantity,

RESOLUTION:

Sales invoices with sundry products are now updated successfully.

3.12.4 No notification or event log for order commitment process failure

ISSUE:

Issue identified affecting the processing of committed stock to customer orders.

When processing a stock receipt or completing a production order, if a commitment for any

of the receipted or built product items was associated with an expired customer backorder

the commitment would correctly fail to be processed to the customer’s order. However,

when this occurred the system did not log an event or generate a notification highlighting

the failure.

RESOLUTION:

When a committed stock receipt or production build fails to be processed due to expiry of

the customer backorder an event describing the failure is now logged in the MomentumPro


Application Event Log. Notifications of failure events are also sent to the System Admin

email addresses configured in the OVERALL SYSTEM CONFIGURATION program.


3.13 Service

3.13.1 Outstanding Order Balance incorrectly updated

ISSUE:

Issue identified affecting the SERVICE ORDERS and TIMECARD ENTRY programs.

When increasing or decreasing the hours of a timecard associated to a service order the

outstanding order balance of the customer was not updated correctly and in some cases was

a negative value. This occurred when another non labour product exists on the service

order.

RESOLUTION:

The outstanding order balance of a customer is now updated correctly when timecard hours

are updated.

3.13.2 Diary Option Slow in Service Orders

ISSUE:

Issue identified affecting the Diary option of the SERVICE ORDERS program.

The Diary option of the SERVICE ORDERS program was taking up to 10 seconds for the

diaries to be displayed in the grid.

RESOLUTION:

There is no longer a delay when selecting the Diary option of SERVICE ORDERS program.

3.13.3 Service order completion allowed with non-charged issues

ISSUE:

Issue identified affecting the SERVICE ORDERS program.

The SERVICE ORDERS program was incorrectly allowing service orders to be completed

when one or more order lines with no required/charge quantity had issued quantity. This

caused the value of the issued stock to remain in Work in Progress in the General Ledger.

RESOLUTION:

It is no longer possible to complete a service order if an order line has issued quantity with

no required/charge quantity.


3.14 Warehousing

3.14.1 Stocktake Count Entry displays incorrect Count Totals

ISSUE:

Issue identified affecting the STOCKTAKE COUNT ENTRY program.

The STOCKTAKE COUNT ENTRY program was sometimes displaying incorrect Total Count

and Difference figures. The incorrect count figures were flowing through to the inventory

when the stocktake was processed.

RESOLUTION:

The STOCKTAKE COUNT ENTRY program now displays correct Total Count and

Difference figures.

3.14.2 Stocktakes that are set to “In Progress” can be deleted

ISSUE:

Issue identified affecting the STOCKTAKES program.

The STOCKTAKES program incorrectly allowed stocktakes that were set to “In Progress” to

be deleted. Once deleted the bins associated to the stocktake still had the “In progress” flag

set against them.

RESOLUTION:

An error is now displayed to the user preventing a stocktake from being deleted if it is set to

“In Progress”. The status must be set to “Not Started” before the stocktake can be deleted.

momentumpro Database Schema Changes in this Release 43

4. Database Schema Changes in this Release

4.1 What you need to know

The details below are provided for the reference of users who utilise reporting and/or query

tools such as Crystal Reports or Qlikview that connect to the MomentumPro databases via

an Open Database Connectivity (ODBC) interface. Database schema changes in this release

may impact existing reports or queries that utilise an ODBC interface. If you are unsure if

the schema changes will impact your existing reports or queries please contact your report

developer or query tool provider.

The database schema details in this document are provided for experienced users and/or

report or query developers as a supplement to a complete database schema document and

will assist with assessing the potential impact that schema changes applied in this release

will have on existing reports and queries.

4.2 Database Schema introduction

The MomentumPro Database Schema is a vital component of the MomentumPro Application.

The Database Schema describes the organisational structure and format details of the data

tables and fields throughout the application. The MomentumPro Database Schema is

structured to support the requirements of the MomentumPro application and as such the

data may often be represented in the database in a manner that is difficult to comprehend

outside of the application.

What are the “live” and “markin” databases?

The MomentumPro application data is arranged into two physical databases called “live”

and “markin”. The “live” database is the primary data storage location for the

MomentumPro application and contains the data unique to your business. The “markin”

database contains static application data used by the MomentumPro application programs.

No business specific data is stored in the “markin” database.


4.3 Changes to the live database

A new field has been added to the inventory (Inventory Detail) table.

FIELD NAME LABEL/DESCRIPTION DATA TYPE DEFAULT FORMAT

Class Pareto class Character X(1)

New indexes have been added to the movement table.

deb_id, tran_date, tran_time, mtrans_no, lineno

cred_id, tran_date, tran_type, mtrans_no, lineno

The data type has been altered for a field in the debtor (Customer Master) table.


credit_limit Credit limit Integer64 zz,zzz,zzz,zzz,zz9

The data type has been altered for a field in the dbcredit (Credit Arrangements) table.


credit_limit Credit limit Integer64 zz,zzz,zzz,zzz,zz9


4.4 Changes to the markin Database

There have been no changes to the markin database schema for this release.

momentumpro v3.1 sp5 patch 01 release notes · a remote desktop or citrix terminal server is...

Documents