Waring MBB520 Datasheet download pdf (Page 19)

Release Notes - New Features included in Release 2.4.0

Page 19 of 89

4.2.2.4 Resultant Call Cross References (SR4073)

A new call cross-reference type of 'CLR' has been introduced to allow a call which has been raised

as a result of a previous call to be cross-referenced to that other call. This allows a distinction from

those calls that are cross-referenced purely for informational purposes or where a call is dependent

on another call.

4.2.2.5 Enhancements to Call Enquiries (SR4130)

The CALE (Call Enquiry) transaction has been enhanced to display the call contact's e-mail address

and telephone number, where defined, and also details of the most recent activity logged against the

call.

The CLXR (Call Cross-References Enquiry) transaction has also been enhanced to display a

"Relation" indicator for each cross-reference. The indicator will be "Parent" where the entered call

is defined as a cross-reference against another call, or "Child" for all other cross-references defined

against the entered call.

4.2.2.6 Call Text Searching (SR4218_02)

The CTSH (Call Text Search) transaction has been enhanced to improve the speed and quality of

data retrieval.

The routine will search through 'bundles' of seven lines of text at one time, ignoring line breaks and

intervening words. For example, if a user enters a text string such as 'system error 301', they could

see calls containing the following strings of text:

• 'System error 301'

• 'The system reported an error code 301'

• 'System Error 301 was displayed'

4.2.3 Sales and Distribution (SORD)

4.2.3.1 Sales Order Quantity Unit of Measure Changes (SR3127)

A new option has been introduced to allow sales orders for a given product to be raised in different

units of measure and for this to remain visible as orders are progressed e.g. for printing on sales

documentation.

Prior to this enhancement it was possible to raise orders in different units of measure, but visibility

of the entered units was lost, as the sales quantity was converted into the default product unit

defined on PDMT, before being stored on the database.

Manual Set-Up Procedures

This option is controlled by a new management parameter (FSAM – “Single Selling Unit per

Prod”). If set to ‘Y’, the default, the software works as it did prior to this enhancement. If set to ‘N’,

the quantity is stored in the quantity unit defined at sales order entry (SIAD).

1 2 ... 14 15 16 17 18 19 20 21 22 23 24 ... 88 89

No comments

Waring MBB520 Datasheet Page 19