Professional Documents
Culture Documents
AMOS Business Suite Vrs. 9.2 Reference Manual
AMOS Business Suite Vrs. 9.2 Reference Manual
Version 9.2
Reference Manual
Copyright
Copyright E 2010 SpecTec Group Holding Ltd., Limassol, Cyprus World rights reserved. No part of this publication may be stored
in a retrieval system, transmitted or reproduced in any way, including but not limited to photocopy, photography, magnetic or other
record, without the prior agreement and written permission from SpecTec Group Holding Ltd. Documentation office.
Furthermore, unless specifically stated in the Software Purchase Agreement duly signed by both SpecTec Group Holding Ltd. and
the user, the user will not distribute, reproduce, or allow access to by a third party this documentation, without the prior, written
approval from SpecTec Group Holding Ltd. Documentation office.
Whenever an authorised copy is made of all or any part of the documentation, all titles, copyright notices, patent notices or other
proprietary markings must also be reproduced in full and included with the copied product. The User shall not alter or remove any
copyright notices, patent notices or other proprietary markings affixed to or distributed throughout the documentation.
Disclaimer
SpecTec Group Holding Ltd. makes every effort to ensure the information contained in this document is correct at the time of printing.
However, as products of SpecTec Group Holding Ltd. are constantly being updated and maintained, discrepancies may arise from
time to time between this documentation and the Product to which it applies. SpecTec Group Holding Ltd. makes no representations
or warranties regarding the content or accuracy of the documentation, and specifically disclaims any implied warranties of
merchantability of fitness for any particular purpose. Information in this documentation may change at any time and does not represent
a commitment on the part of SpecTec Group Holding Ltd. SpecTec Group Holding Ltd. reserves the right to make documentation
changes from time to time in regards to style, layout, and content without any obligation by SpecTec Group Holding Ltd. to notify
any person of such changes or provide users with updated documentation revisions. Furthermore, the product described in this
documentation may change without notice.
Trademarks
All brand and product names to be found in this document or the product to which it applies are trademarks of their respective
companies.
ii
Table of Contents
Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 The AMOS Business Suite Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2 The Client/Server Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2.1 The Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.2.2 The Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.3 How to use this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
iii
3.7.5 Currency Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.7.6 Quality Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.7.7 Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.7.8 Vessel Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.7.9 Job Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.7.10 Job Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.7.11 QA Grades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.7.12 Stock Grades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.7.13 Account Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.7.14 World Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.7.15 Countries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.7.16 Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.7.17 Berth Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.8 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.8.1 Job Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
3.8.2 Component Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.8.3 Function Criticality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.8.4 Function Criticality Indicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.8.5 Project Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.8.6 Reschedule Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.8.7 Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.8.8 Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.8.9 Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.8.10 Causes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.8.11 Failure Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.8.12 Failure Effects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.8.13 Failure Descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.8.14 Failure Detection Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.8.15 Failure Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.9 Stock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.9.1 Stock Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
3.9.2 Price Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.9.3 Transfer Reasons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.10 Purchase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.10.1 Order Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.10.2 Delivery Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.10.3 Payment Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.10.4 Delivery Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.10.5 Receipt Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.10.6 Voucher Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.10.7 Expense Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.10.8 Finalise Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.11 Attachment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.11.1 Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.11.2 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
3.11.3 Attachment Source and Reference Definition Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.12 Quality Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.12.1 Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.12.2 Job Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.12.3 Document Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.13 Non Conformity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.13.1 Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.13.2 Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.13.3 Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.13.4 Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.14 Emergency Response System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.15 Claims . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.16 Voyage Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
iv
3.16.1 Cargo Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.16.2 Cargo Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.16.3 Cargo Attribute Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.16.4 Delay Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.16.5 Delay Reason . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.16.6 Event Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.17 Personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.17.1 Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.17.2 Company . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.17.3 Evaluation Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.17.4 Evaluation Grade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.17.5 Leave Days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.17.6 Manning Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.17.7 Rank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.17.8 Rank Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.17.9 Ship Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.17.10 Trade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.17.11 Vessel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
3.17.12 Vessel Characteristic Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.17.13 Vessel Department . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.17.14 Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.17.15 Contract Leave Days . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.17.16 Disability Grade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.17.17 Employee Address Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.17.18 Family Relation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.17.19 Institute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
3.17.20 Marital Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.17.21 Sailing Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.17.22 Sickness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.17.23 Sickness Nature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.17.24 Sickness Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.17.25 Standard Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.17.26 Standard Document Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
3.17.27 Termination Reason . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.17.28 Trade Union . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.17.29 Airport . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.17.30 Crew Effect Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.17.31 Ship Store Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.17.32 Slopchest Departments and Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.17.33 Slopchest Stock Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.17.34 Employee Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
3.18 Payroll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.18.2 Bank . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.18.3 Bargain Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.18.4 Currency Rounding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.18.5 Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.18.6 Wage Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
3.19 Tools Menu Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.19.1 Approval Limits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.19.2 Account Code Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.19.3 Cost Centres . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.19.4 Transaction Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.19.5 Stock Grade Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.19.6 Depreciation Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
v
Chapter 4 Export/Import: Data Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.1 Exchanging Data with the Head Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.2 Automated Export and Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.2.1 Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.2.2 Task Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
4.3 Manual Export and Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.3.1 Manual Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.3.2 Manual Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
4.4 Selection File Commands for Import and Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.4.1 Export Selection Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
4.4.2 Import Selection Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
4.4.3 Selection File Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
4.5 Setting Up Export and Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
4.6 Export Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
4.7 Import Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4.8 Portal Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
vi
9.3.5 Self Assessment Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
vii
Chapter 15 System Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
15.1 The Parameters Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
15.2 Auto-- Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
15.2.1 Creating New Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
15.3 Default Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
15.4 Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
15.5 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
15.5.1 Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
15.5.2 Budget . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
15.5.3 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
15.5.4 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
15.5.5 Payroll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
15.5.6 Personnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
15.5.7 Purchase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
15.5.8 Self Assessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
15.5.9 ShipDex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
15.5.10 Stock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
15.5.11 Voyage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
15.6 Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
15.7 Transaction Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
15.8 User Defined Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
viii
Chapter 21 Installations and Departments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
21.1 Creating Installations and Departments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
21.1.1 Installation Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
21.2 Switching Departments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
21.3 Multi Company Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
ix
Chapter 26 Transaction Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
26.1 Transaction Code Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
26.2 Transaction Codes Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
26.3 Applying Transaction Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
x
Your AMOS Support Network
An up--to--date list of email addresses and telephone numbers is available on the Contact Support page of our website, at www.spectec.net
Americas (US)
Email : [email protected]
Phone : USA +1 954 962 9908 ext. 21
Asia--Pacific (APAC)
Email : [email protected]
Phone : Singapore +65 622 071 16
Russia (CIS)
Email : [email protected]
Phone : Russia +7 812 324 5110
Additional Manuals
For additional copies of user guides or installation manuals, please contact your local sales office.
xi
Chapter 1 Introduction
S The client program AMOS Business Suite is installed on each PC where it is to be run.
S The type of interface library depends on which database management system is used at the
installation. For example, for the Adaptive Server Anywhere database system, an ODBC (Open
Database Connectivity) interface may be used.
S The database engine typically resides on the database server machine (or on a PC in a stand-- alone
configuration). During installation, it is necessary to set certain parameters that allow AMOS
Business Suite to communicate with the database engine through the interface library.
1
S The amos.db database file is created when the application is installed. It is the selected database
engine that actually creates the database file according to its internal structural rules.
S When AMOS Business Suite is upgraded to a new version, the installation program automatically
handles the updating of the database. Please note that the AMOS Business Suite application can
only communicate with the database file through the interface library and the database engine.
2
> Parameters Chapter 15
> Number Series Chapter 16
> Work Flow Chapter 17
> Mandatory Fields Chapter 18
> Audit Trail Configuration Section 6.2
> Dashboard Alerts Chapter 19
> Overview Panels Configuration Chapter 10
> Printer Tasks Chapter 20
> Installations > Company, Installation/Depart-
ment, Installation Groups;
Chapter 21
> Extension Features > Chapter 22
> Accounting > Account Code Categories, Cost
Centres; Chapter 5
> Budget > Chapter 23
> CBM References Chapter 24
> e-- Business > e-- Business Portals, Formats;
Chapter 25
> Self Assessment Section 9.3
> Stock Transaction Codes; Chapter 26
Stock Grade Categories, De-
preciation Levels; Section 3.19
> Update System License Section 2.1.2
Utilities > Section 2.5
Mobile > (All commands) See the AMOS Mobile User
Guide
Change Password Chapter 11
View PSR Report Section 7.1
Options Chapter 12
Delegate Mailbox Access Chapter 13
Mailbox Access Log
Transfer Mailbox Contents
Work Flow Notifications
3
Chapter 2 Using AMOS Business Suite
The AMOS Business Suite is an integrated framework of several leading AMOS applications. Each AMOS
application is configured as a Plug--in of the Business Suite and is individually enabled by license codes.
When the Business Suite is installed, only the plug--in applications that you have entered a license code
for will be accessible.
Note If you dont have a logon account or you have forgotten your password, contact your system administrator.
If your logon details are accepted, the AMOS Business Suite desktop will then be displayed.
Note Your organisation may use one or more additional security options available within AMOS such as
complex passwords, maximum password age, minimum password length, maximum number of logon
attempts and/or restriction of recently used passwords when registering a new one. Ask your system
administrator if you are unsure if any of these features are employed.
4
Figure 2 An Example Window for Updating a License
To switch the Dashboard on and ...go to Tools > Options and check or clear the Enable Dash-
off... board checkbox in the Dashboard tab.
To switch the Task Bar on or off... ...go to Tools > Options and check or clear the Task bar
checkbox in the General tab.
To hide or display the List Bar/Icon ...go to Tools > Options and click the radio buttons in the
Bar... General tab.
To display the list of Views in your ...go to Tools > Options and ensure that the List Bar/Icon
side bar... Bar radio button in the General tab is On.
5
Figure 3 The Dashboard, with List Bar
See Chapter 12 for more information about the Tools > Options window.
Your Dashboard is split into segments: the two standard segments are Alerts Overview and Notifications.
2.2.1.2 Notifications
This area of the Dashboard contains a list of modules for which workflow is in use in your system. For each
module, you will see the number of workflow notifications presently awaiting acknowledgement (for the
logged in user). Double--clicking on a module name will take you directly to the Work Flow Notifications
window, which contains the list of all notifications awaiting acknowledgement by the current user.
6
2.2.2 The Windows in AMOS
Figure 4 shows the AMOS main window (when the dashboard is switched off). It controls any other
windows that you open with AMOS, and it contains:
S The pull down menus. These menus contain all the commands in AMOS.
S The main toolbar. These buttons are shortcuts to frequently used parts of AMOS.
Note The modules and commands available to you are controlled by the software license purchased by your
company, and some commands are user defined. The illustrations in this manual may therefore differ from
what you see on your screen.
When you first open AMOS Business Suite the window that appears will have a title bar, usually blue in
colour. The title bar informs you which installation (vessel) and department you are viewing information
for. In the following example, the installation is AMOS Voyager and the department is Maintenance.
In addition to the main title bar, each window that is opened within the application has its own Window
Title Bar. These title bars display the name of the open window and, depending on the information you
are viewing, sometimes extra details of the individual item displayed within the window.
7
All of the commands and functions available within the application can be accessed through the Menu Bar.
Once you open a data window, the Menu Bar changes to include the Edit and sometimes the Options menu
items as illustrated below.
When your license does not include certain functionality, those menus will be greyed out. Greyed out
menus can be hidden by setting the parameter Hide Inaccessible Menu Entries to TRUE.
If you have Toolbar tips activated (at Tools > Options), a description of the buttons function will appear
when you hover over it with the mouse.
Note The number of visible buttons may vary depending on how the application has been set--up, the license that
is in use and your access level within the system.
8
Figure 10 Customise Toolbar Menu
To choose from a more comprehensive set of options, go to Tools > Options. There are extra options on
the General tab. For example, you can choose the default window settings from the drop--down list. For
more about the Tools > Options window, see Chapter 12.
Wherever you see key combinations towards the right side of menu options, as above, you can use them
as an alternative. If the shortcut takes the form of Ctrl+? or Alt+?, press the Control or Alt key and the
key represented by the ? at the same time.
Note The availability of Keyboard Shortcuts depends on the currently active window and how the application
has been set up at your installation.
9
2.2.2.7 Active Window Refresh
Select Edit > Refresh, or press the F5 key to refresh the contents of the active window without re--opening
or re--filtering the existing window.
10
Figure 12 The Switch Department Window
If you have any open windows, click the Close Windows button first.
3. After a moment, you will see the new Department appear in the top line of the AMOS window.
2.3.2 Filters
AMOS Business Suite makes extensive use of Filters throughout the application. As the AMOS Business
Suite database builds over time, the powerful filter function becomes very useful. Filters are used to narrow
down the lists in the windows by allowing you to define the criteria for the data you wish to retrieve from
the database. For example, if you want to see a list of only the tankers in the sites window, you can specify
a filter that shows only those entries. At any time you can re--filter within a window by clicking the Filter
button in the toolbar. Filters change their appearance according to the register you are working with.
11
Of course, if there is no record with the specified criteria registered, then the result box will come up empty
and ask you if you wish to create a new entry.
Note Searching / filtering using the or characters is not supported by the system, so do not include these
characters in any field when adding search criteria to a filter.
Click this button to open a secondary window to help you select pre--defined values from your database.
Sometimes the lookup list has its own filter, which opens first.
If you know the starting letter or number of the information you are searching for, you can enter it into the
standard filter window before clicking on OK in order to restrict the look--up filter by displaying only
records beginning with the letter/number you have entered.
Look up filters enable you to quickly find the information you are searching for. The following window
shows a typical example of a look--up window. It is possible to sort information and search using either
the code or the name associated with the information you are viewing. You choose the type of information
you want to select from by clicking in one of the two radio buttons and then type the first letters of the
information you are searching for. As you type the letters, the highlight moves automatically to the first
record starting with those letters. Once the highlight is on the record you want to use, click OK.
Some of these filters may also have an additional Details button which can be used to open a window
containing read--only information regarding the highlighted selection.
12
2.3.5 Column Sorting
After you have opened a window, you can sort the records it contains by clicking on the column headers.
Once sorted, the column sort order is indicated by an arrow icon in the column header.
In most cases, all the columns in a table are sortable and their sort state is indicated by an arrow icon in
the column header. If there is no arrow then the column is unsorted.
Once the symbol is visible, click and hold the left mouse button, and drag the symbol sideways until you
have the desired column width. Then release the mouse button.
To move a column to a different position, place the pointer in the header of the column you wish to move,
then click and hold the left mouse button. The column will become black. Drag the mouse cursor to the
desired column position and then release the mouse button to drop the column in place.
13
This facility allows you to re--organise the columns in any way you choose.
Note This technique does not permanently change the column order within AMOS. If you close and then re--open
the window, the column order will revert to the default setting. However if you re--apply a filter without
closing the window, the column order will remain as you altered it.
If you want to have a more permanent re--ordering of the columns in a window you can save the window
as a View which you can select again and again through the Select View function described in section
2.2.1.
Click on the line and drag it to where you want to divide the list. Each pane will have its own scrollbar.
14
Note If you switch from the classic editor to enhanced editor, any modified details screens will contain hidden
formatting code. This formatting code will become visible if the editor is switched back to classic, and will
be displayed as the first 5 or 6 lines when viewed. This formatting text must be removed manually.
Note When text is present in a details window, the keyboard input language will change to the language of that
text, if it is different from the set keyboard input language. If a details window is empty, the keyboard input
remains on the set language.
2.3.8.1 Templates
AMOS provides a feature called Templates, which makes it possible to define how a Details tab or Full
Description window should be presented on screen. Using a template, the Details tab/window can be given
the appearance of a specialised input form.
Users can create new templates using PowerBuilder, and import them into the Business Suite. These
templates can then be attached to the Details tabs in the application such that the users can fill in forms
rather than write information into blank pages. This process can assist the user by asking for the required
information.
The templates are usually attached to the Details tabs using the Edit > Change Template menu command.
However, a template may be attached automatically on creation of a new table entry, by setting a default
parameter.
Note Read more about creating and using templates, and the Templates register in Chapter 27.
15
Figure 19 Edit Menu
If there is no facility to choose fields in the current window, the Field Chooser menu option will not be
visible.
Cut Removes the highlighted text and places it on the clipboard.
Copy Places a copy of the highlighted text on the clipboard.
Paste Places the contents of the clipboard at the cursor position.
New Record Creates a new, blank, record.
Save Changes Saves any changes made to information.
Refresh Updates the current window with recent information.
Delete Record Deletes the currently highlighted record.
Select All Tags all records in the current window (checks all boxes).
Deselect All Un--tags all records in the current window (clears boxes).
Change Template Changes the template to be used for details screens.
Note Changing a template may make it impossible to read existing information that has already been entered
using a different template or without a template altogether.
Field Chooser Gives access to the Field Chooser window where you can select which fields are
to be shown in the lower data window of certain screens. When you select this command, a list of the
columns available for this window is displayed. Check the boxes for those columns you wish to appear in
the list.
Search Opens a Search field in the top of the list part of the window. Typing directly in the field
allows you to search within the listed records, whether they have already been filtered them or not. Holding
the SHIFT key and clicking in the field opens an Advanced Search dialog, where further search parameters
can be entered.
16
2.3.10 Calendar Facility
AMOS Business Suite contains a Calendar Facility that can be used to select dates within data entry
windows and filter windows.
If you double--click in a date field, or press the F2 key on your keyboard while the cursor is in a date field,
a calendar opens. This enables you to select the required date, which will automatically be entered in the
correct format.
If you prefer to type the dates in manually, you can do so by typing two digits each for the day, month and
year separated with a space.
When you enter the date information in this way, the date field will automatically adjust to the default view
when you press enter or move to another field.
Note The format of the date within AMOS Business Suite is controlled by the default settings within your
operating system. On a Windows based machine, open the Regional Settings function within Control
Panel.
17
2.4 Printing
2.4.1 Printer Setup
Select File > Printer Setup to view a list of the defined printers. The default Windows printer is used unless
you select a different printer from the Printer Set--up window.
Click the Setup button to enter the Properties dialog box for the selected printer. The options available in
this box depend on the printer and printer driver selected.
2.4.2 Print
Select File > Print to print the contents of the active window on the default Windows printer. There is a
corresponding toolbar button. To print on a different printer, select File > Printer Setup before starting
the printout.
2.6 Help
The application includes context--sensitive help. Context--sensitive means that when you open the Help,
it will open at the appropriate page so you should not need to search through the file to find the information
you need.
To obtain help on a particular window, make the window active by clicking in it, then press the F1 button
on your keyboard or for the filter windows click the Help button. The Help window will open, initially
located towards the upper--right corner of your display, at the page applicable to the window.
Note The various application modules in the AMOS Business Suite each have their own Help files, and registers
and functions that are common to more than one module are also described in the Framework Help file (the
Help file for the background application within which the modules run). The Help files are opened via the
application windows, and there are no links between the various Help files, so if the wrong window is active
when you press the F1 key, you may find yourself in the wrong Help file! Several Help files can be open
simultaneously.
18
2.6.1 Navigating Through the Help File
The Help file document that opens may be linked to other documents containing additional relevant
information. Click on the links, normally in blue text and underlined, to open the new document.
The Help window itself also contains several controls to simplify navigation through the help file.
19
Chapter 3 The Registers
AMOS Business Suite stores entered information in registers. Selecting File > Open Register gives
access to them. Some other registers are contained on the Tools menu. These are discussed in section
3.19.
S A filter window may appear after you select an Open Register sub-- command.
S After you fill in the filter, the window of the selected register appears on the screen. In addition,
the Options menu may appear in the main menu bar. The contents of this menu vary from register
to register. In the following section, a description of the Options menu is included for each
register if applicable.
S The Edit menu is also added to the main menu bar when a register window has been opened. The
menu normally contains commands used to cut, paste and copy information, and to create, delete
and save records in the selected register. Other commands may be available depending on the
currently active window.
S Access control determines which user groups have access to each individual register. Access
control is described in Chapter 14.
3.1 Addresses
File > Open Register > Addresses
The Addresses register is for storing information about all companies and persons with whom your
organisation deals.
Select File > Open Register > Addresses to open the filter for addresses. There is a corresponding
toolbar button. Once you have entered some search criteria in the filter, click OK to proceed to the main
window.
20
Figure 23 The Addresses Window
The Addresses window is for entering information about companies and persons.
S Each address in the list at the bottom of the window contains a check box to the left. If you tag
multiple addresses, certain processes can be performed on all selected addresses at once.
S The Currency Code drop-- down window is for selecting the default currency of the vendor. This
value is inherited by new purchase forms placed against the vendor unless overridden by the code
in the Vendors tab of the selected Stock Type/Item.
S Checking the Goods Receivable checkbox indicates that the address is classed as an authorised
goods received address. Purchased items that arrive at this address are authorised for payment
through the voucher system prior to arrival at their final destination.
21
3.1.2 The Addresses Register --- Contacts Tab
For every address you create you can add contact persons in the Contacts tab. You can add multiple
contacts per address, and the information to enter includes the persons name, emails, phone and mobile
numbers. It is important to select Active from the drop-- down list for each contact that is current. If a
contact is no longer valid but you want to preserve the details, select Disabled from the drop-- down list.
3.2 Employees
File > Open Register > Employees
The Employees register is for storing information about the employees in your organisation.
Note If your license includes the Personnel module, this register is superseded by the one found at Crewing
> Employee. Creation of new employee records in this register will be disabled, although fields other
than Code, Last Name and First Name will still be editable.
S Assign each registered employee a unique Code (this could for example be the initials of the
employee).
S Use the lookup button next to the Address field to select information from the Address register.
S The contents of the Discipline drop-- down list are linked from the register with the same name,
described in section 3.7.2.
22
S The fields starting with E-- Uxx are user-- defined fields. See section 15.8 for more information on
these fields.
3.3 Locations
File > Open Register > Locations
The Locations Register takes the form of a hierarchy and is for defining various physical locations at an
installation where components and stock items can be stored or located. The Components window
contains a Location field and buttons with access to a selectable list of locations or a hierarchical list
of locations.
23
S Each time you update an existing currency rate, create a new entry for the same rate. This
preserves the historical information belonging to the already existing rate. When you create a new
record for an already existing currency rate, the old rate is replaced in the register by the newer
one upon saving.
S Select Options > Show All to display all rates entered to date. There is a corresponding toolbar
button.
24
Figure 28 Example of the Vessel Details - General tab
Note The greyed-- out fields fetch their data from the information you fill in on the Log tab.
25
Figure 29 The General Registers
Most general register windows are fairly simple, and usually do not have an associated Options menu.
The Edit menus contain similar commands to those found on the secondary toolbar: It is possible to
create a new record or delete an existing one, to save changes, and to use the cut, copy and paste functions.
3.7.1 Templates
File > Open Register > General > Templates
Various documents used in AMOS Business Suite require different layouts. Creating Templates provides
the ability to customise the presentation of the Details tabs/Full Description windows found throughout
AMOS Business Suite. When a template is selected in a particular window, the user will then be
presented with a form that may contain drop-- down lists, selection boxes, input fields and other controls,
upon opening the Details tab/Full Description window.
To utilise templates:
1. Create a form definition in PowerBuilder or the Form Designer window.
2. Connect the definition to a unique template Code and Description in this register.
Click the New button on the toolbar to get a blank line, and enter a Code and Description for a new
template. Then go to Options > Import to connect a form definition to the selected Template record.
Check the Obsolete checkbox in the event that a template is out of use, and this will remove it from
drop-- down lists in the system, thereby preventing future selection and use of that template.
26
Figure 30 The Templates Register
You can also convert normal templates to enhanced using the Options menu: whether a template is
already enhanced or not is indicated in the Enhanced column. The original template can be marked
Obsolete in the process to disable future selection.
See Chapter 27 in this guide for information on:
S Creating forms in the form designer,
S Connecting form definitions to the template codes, and
S Converting templates from basic to enhanced, and assigning access.
See Chapter 28 for a brief introduction to using PowerBuilder to design your own templates and reports.
3.7.2 Disciplines
File > Open Register > General > Disciplines
The Disciplines register is for defining various labour functions. Once this has been done, costs may be
tracked by disciplines, for example. It is possible to check a discipline as External:
External disciplines are indicated with the character *. For example, the filter for work orders contains
an Only Disciplines list that differentiates between internal and external disciplines:
27
Figure 32 The Only Disciplines Area of a Work Order
External disciplines are used in conjunction with work orders if you wish to purchase those services
externally.
28
3.7.5 Currency Codes
File > Open Register > General > Currency Codes
The Currency Codes register is for storing information about which currencies your organisation uses.
The Currency Rates register, described in section 3.4, is for entering new and updated exchange rates
between the currencies as changes occur.
3.7.7 Units
File > Open Register > General > Units
The Units register is for defining the various quantity units typically used for stock items. The units
registered here will be listed in the Stock Units drop-- down list in the Stock Items window, if the Use
Stock Types parameter is set to TRUE. If the parameter is set to FALSE, the values from the Units
register will not be available in the list.
29
Checking the checkbox in the column Decimals indicates whether decimals can be used in combination
with the selected unit of measurement.
In the right hand side of the window, are three columns called Source Unit, Conversion Expression and
Formula. Select a unit in the Name column, and using the lookup button choose a Source Unit to convert
to, and enter an expression that results in the appropriate conversion. The resulting formula will appear
automatically in the Formula column when the record is Saved.
30
3.7.11 QA Grades
File > Open Register > General > QA Grades
The QA Grades register is for defining various quality assurance grades to assign to suppliers. The
Addresses window (see section 3.1) contains a QA Grading drop-- down list from which a QA grade may
be selected for a supplier. Similarly, when an option is selected in the Stock Items window, the Options
menu gives access to the commands Vendors and Preferred Vendor and these windows also contain
fields that display the quality grading.
The Categories available in the drop-- down window are defined in the window at Tools > Configuration
> Stock > Stock Grade Categories.
31
Figure 40 The Account Code Register
If you are using the Accounting module, this register is linked to Cost Centres and recorded in the
Account Transactions window (described in Chapter 5).
32
3.7.15 Countries
File > Open Register > General > Countries
Use this register to input country Names, country Codes and Country Regions into the system.
33
3.7.16 Ports
File > Open Register > General > Ports
This register is a list of the ports that your company vessels could visit.
34
3.8 Maintenance
AMOS M&P contains registers that allow you to differentiate between various aspects of maintenance
tasks to be carried out. The commands in the Maintenance menu are discussed in the AMOS Business
Suite - M&P User Guide.
To open a maintenance register, go to File > Open Register > Maintenance:
35
Figure 47 Example of the Job Descriptions Register
The Class drop-- down list displays the contents of the Job Classes register, described in section 3.7.10.
36
Attachments
You can connect attachments to a job description. These may for example be scanned images from
documentation/drawings or video films explaining maintenance details. Selecting Attachments opens
the window to connect attachments to the job description. There is a corresponding toolbar button.
Select View Attachment to preview the attachment.
Permits to Work
This menu item is for attaching one or more Permits to Work to the currently selected Job Description.
Select the required permit from a drop-- down list. Click the New toolbar button to add further permits
to work if required.
The contents of the drop-- down window are entered and maintained using the Permits to Work register
described in section 3.5.
The Permits to Work are automatically attached to all new work orders that are based on the job
description to which they are attached and are issued and acknowledged within the work orders window.
The work orders window is described in the AMOS Business Suite - M&P User Guide.
Components
A job description may be connected to one or more defined components. The Components command
opens the window where connected components are listed. A single job description may be connected
to multiple components. Within this window, selecting Options > Component Jobs (or double-- clicking
on a component) opens the Component Jobs window and scrolls to the job for the combination of the
selected Job Description and component. Jobs and Job Descriptions are connected to Components in the
Components window. The Components window and Component Jobs window are discussed in detail in
the AMOS Business Suite - M&P User Guide.
Maintenance Log
When users report work, AMOS M&P stores the information in the maintenance log. The Maintenance
Log command opens the Maintenance Log window.
When you select a line in the Maintenance Log window, the Options menu contains commands to view
or register History, Stock Used, Resources Used and Counter Settings respectively. There are
corresponding toolbar buttons for these commands.
Move Job References
AMOS M&P allows you to replace all occurrences of a Job Description with another one. The Move Job
References command opens the window where all occurrences of the selected job description in the
database are replaced by the job description you select from the next dialog.
This function can be protected by Group, at Tools > Configuration > Access Control > Groups, then
selecting Access Control from the Options menu and selecting the Functions tab.
Create Component Type Job
This menu item allows you to create a Component Type Job for the currently highlighted Job Description.
Use the filter to locate the Component Type to create the job for. When you have selected the component
type, click OK to open the Jobs window and complete the remaining details.
Create Component Job
This function allows you to create a Component Job for the currently highlighted Job Description. Use
the filter to locate the Component to create the job for. When you have selected the component, click
OK to open the Jobs window and complete the remaining details.
37
Copy Job Description
Select Options > Copy Job Description to create a copy of the selected job description. You can only
copy and make a new revision from an Active job description.
38
3.8.4 Function Criticality Indicator
File > Open Register > Maintenance > Function Criticality Indicator
To visibly differentiate between function criticality levels, it is possible to assign a graphical indicator
to each level. To do so, the available indicators to be used must first be defined here in the Function
Criticality Indicator register. To register a list of indicators, click New to get a blank line. Then select
an icon from the predefined options in the drop-- down list. Its number and the corresponding image
appear. Save the indicators - they can then be added to the levels defined in the Function Criticality
register. See the section above.
39
3.8.6 Reschedule Limits
File > Open Register > Maintenance > Reschedule Limits
The Reschedule Limits register is for defining the limits within which a selected Maintenance Task can
be rescheduled. Each Reschedule Limit is a set amount of days before and after the calculated due date
within which a Task can be carried out. For example, you can define a periodic frequency code Q with
the name Quarter and define that this corresponds with a frequency of every three months. You can then
define the number of days before and after the scheduled date that a Maintenance task based upon this
periodic frequency can be rescheduled.
3.8.7 Criteria
File > Open Register > Maintenance > Criteria
Below is an example of maintenance criteria that may be entered in this register. The Advanced tab in
the Work Orders filter may be used to select work orders that belong to a selected maintenance criterion.
40
3.8.8 Types
File > Open Register > Maintenance > Types
Figure 56 shows an example of maintenance types that may be defined in this register. The Advanced
tab of the Work Orders filter may be used to select work orders that belong to a selected maintenance
type. The Budget Code column is used to define the default budget code for each maintenance type.
3.8.9 Classes
File > Open Register > Maintenance > Classes
Below is an example of maintenance classes that may be defined in this register. The Advanced tab of
the Work Orders filter may be used to select work orders that belong to a selected maintenance class.
41
3.8.10 Causes
File > Open Register > Maintenance > Causes
This register resembles the other Maintenance registers described in the previous sections. The
Advanced tab of the Work Orders filter may be used to filter according to a selected maintenance cause.
42
3.8.12 Failure Effects
File > Open Register > Maintenance > Failure Effects
Use this register to maintain a list of Effects that a particular equipment failure could have on the vessel
or voyage. For example, Delay in Voyage, Delay in Operations, Vessel Stoppage, etc.
43
3.8.15 Failure Severity
File > Open Register > Maintenance > Failure Severity
Different modes of failure will have different effects on the piece of equipment they occur on. Depending
on the failure, the equipment may or may not continue functioning. Use this register to create a list of
Severity Values, for example Critical Failure, Non Critical Failure, etc.
3.9 Stock
The AMOS M&P integrated application contains registers to differentiate between various aspects of
stock handling. The use of these registers and relevant commands in the Stock menu are discussed in the
AMOS Business Suite - M&P User Guide.
To open a stock register, select File > Open Register > Stock:
44
3.9.2 Price Classes
File > Open Register > Stock > Price Classes
The Price Classes register is for storing the various formulae that are applied to stock item values. Price
Classes are used to add varying levels of administration or transport costs to an item or to reflect different
international tax rates.
Go to Options > Try Formula to check that the formula that you entered for each price class works
correctly. A dialog box opens showing the result of applying the highlighted formula to a reference
amount.
45
3.10 Purchase
The AMOS M&P integrated application contains registers that allow you to define certain aspects of
purchase forms according to your own requirements. The information entered in these registers is then
available in various purchase windows in the form of drop-- down lists enabling the user to select the
required item. When setting up these tables remember that they may be used for future e-- Business
functions. Whilst the information entered is generally defined by the individual organisation, where
possible it is advisable to adopt an international standard for these tables such as the International Marine
Purchasing Association (IMPA) codes. The AMOS Business Suite - M&P User Guide contains further
information on the purchasing functions.
To open a Purchase register, go to File > Open Register > Purchase:
46
Figure 65 The Delivery Terms Register
47
3.10.5 Receipt Status
File > Open Register > Purchase > Receipt Status
This register contains the options for receipt status available in purchase form line items.
3.11 Attachment
Within the AMOS Business Suite you can connect attachments to a variety of records. For example, these
may be scanned images from the component documentation or films explaining maintenance details.
The File > Open Register > Attachment contains the sub-- menu for working with attachments. Select
Sources to set up internal or external tools for displaying attachments and References to build a library
of attachments for use in AMOS Business Suite. To read more about working with attachments in AMOS
Business Suite, see the Chapter Defining and Using Attachments in the User Guide for M&P, Q&S or
Personnel.
3.11.1 Sources
File > Open Register > Attachment > Sources
Before attachments can be viewed, define an attachments source tool for the viewing tool. AMOS
Business Suite offers an internal viewer that can display bitmaps such as BMP and PCX, in addition to
a number of other formats. Other viewers and Windows programs on your PC may be defined as external
viewers.
48
Figure 69 The Attachment Sources Register
From the Service Type drop-- down list, select Internal to define the internal viewer as an image source,
and select External to define a different program. If you select External, fill in the name of the tool in
the Start Command field including the full path. If you want to use drag and drop to add attachments
later, define a source with Service Type Default Association.
The Start Command must end with the characters %IMAGE REFERENCE%. This tells the tool to
display the image supplied by AMOS. Use the field Display Command to specify a DDE command.
It is necessary to know the names and syntax of DDE commands supported by the tool to use this
function.
Attachments can be stored by default in the Graphics Directory, or externally outside of AMOS. The
Graphics Directory is defined in the Parameters > Directories window, and if the corresponding field
in this window is left blank, attachments opened from this source are retrieved from the defined Graphics
Directory. However, to store attachments in multiple directories, you can define an alternate location
here using the Graphics Directory lookup to browse to a folder in your system, and select it.
See section 3.11.3 for a sample of an Attachment Source and Reference definition using a DDE command
for an external viewer.
3.11.2 References
File > Open Register > Attachment > References
After defining attachment sources, begin to build up a library of attachments in AMOS Business Suite.
When the library has been established, attachment references may be connected to one or more relevant
components, stock items, and job descriptions.
The attachments for use must be stored in a specific folder. Normally, this would be the Graphics
sub-- folder in the folder where the AMOS Business Suite has been installed. Ensure that the parameter
for the Graphics Directory contains the name and path of the folder you are going to use for this purpose.
This is described in section 15.4 of this reference manual. If the attachment is stored in a folder other
than this directory, the alternate location must be defined on the Attachment Source entry (see Sources,
above).
49
Figure 70 The Attachment References Register
For each attachment a Source, a Code, a Name and a Reference are specified. The Reference is the path
to the file for use. Click the Browse button to select the reference. You can store attachments in the
database for replication purposes by checking the Store in DB checkbox.
When an attachment is not stored in the database and a user adds it to a record, AMOS will refer to the
setting of the parameter Attachment File Stamp to determine if the date and time on the file should be
left as is, or updated to match the date and time found on the database server.
Note When an attachment is stored in the database the original file reference is also stored, enabling the user
to remove the file at a later date. If the original file is found, the attachment is removed from the database.
If the original file is not found a warning is displayed. If the user proceeds with the removal after the
warning message the attachment file is deleted.
See section 3.11.3 for a sample of an Attachment Source and Reference definition using a DDE command
for an external viewer.
50
3.12 Quality Procedures
The registers for use with AMOS Q&S functions are accessed at File > Open Register > Quality
Procedures.
The commands in the Quality menu are discussed in the AMOS Business Suite - Q&S User Guide.
3.12.1 Categories
File > Open Register > Quality Procedures > Categories
Procedures belong to different procedure categories. Before you create a new procedure, determine
whether you need to create a new procedure category.
Having entered a Code and Title for a template, select Options > Template to open the Document
Templates window and create a template associated with the new template title.
3.13.1 Type
File > Open Register > Non Conformity > Type
This register is for defining types of non-- conformity and their corresponding codes. You can edit existing
field information, or click New to add a new row and enter a suitable code and name. To delete a row,
select the row and click the Delete button. On completion, Save the changes.
51
3.13.2 Category
File > Open Register > Non Conformity > Category
There are two category levels of non-- conformity occurrences, Main and Sub. Each main category can
contain a number of sub-- categories. To define a new main or sub-- category, select File > Open Register
> Non Conformity > Category and choose Main or Sub.
Main
When you select a main category in the upper list, the Sub-- Category list displays the sub-- categories
already defined.
The right side of the window allows you to add sub-- categories, grouped by a main category.
Note If your organisation has a limited number of vessels, it is important not to define too many different
categories. If you do, it will be difficult to use AMOS Q&S to produce significant statistical data during
analysis.
3.13.3 Severity
File > Open Register > Non Conformity > Severity
Use the Severity register to define suitable descriptions for the levels of severity, with pre-- defined levels
from 5 (the lowest level) to 1 (the highest level).
3.13.4 Cause
File > Open Register > Non Conformity > Cause
The Cause register is for defining a set of causes and corresponding codes for non-- conformity
occurrences. You add and delete causes the same way you work with the Non Conformity Severity
register, as described in the previous section.
52
3.14 Emergency Response System
Select File > Open Register > Emergency Response System > Contact Types to add contact types.
These contacts are available for use within the ERS module. The contact types are divided into three
groups:
S External.
S Internal.
S Vessel Specific.
3.15 Claims
Select File > Open Register > Claims > Insurance Category to enter the register for defining Insurance
Categories. These categories are then available for use with the Insurance window (Quality >
Insurance).
53
3.16.6 Event Type
File > Open Register > Voyage Managment > Event Type
A loading or discharging operation is effectively a series of events. These events can include, for
example: first line ashore, first hose connected, first hatch open, last hatch closed etc. Some events are
mandatory for a particular cargo type, and some are voluntary. The mandatory events can be programmed
to appear in the window automatically in the correct order when a loading or discharging operation is
created. The user then inputs the dates and times when these events occur and saves the data.
All the possible events are pre-- defined in the Event Type Management register. Mandatory events for
a particular load type are defined by making the Load or Discharge sequence anything other than 0.
The event types are used in the Voyages window Event tab and Port Calls tab and the Cargoes window
Event tab.
3.17 Personnel
The Personnel registers store information about the crew members, and other data relevant to crew
administration. Selecting File > Open Register > Personnel opens the Personnel registers list in a new
window. The registers are contained in a hierarchy: click the + signs to expand the folders individual
registers are grouped into. Read about these registers in more detail in the AMOS Personnel User Guide.
3.17.1 Activity
File > Open Register > Personnel > Crew Management
This register lists the various employee activities. These activities can include Active on board, Inactive
on leave, Training, Sick leave etc. The activities are used in the Employee Overview window Service
tab.
3.17.2 Company
File > Open Register > Personnel > Crew Management
This register contains the names of the company, ship owners, ship managers and other companies the
employee may work for or that may own or run the vessels.
54
3.17.3 Evaluation Criteria
File > Open Register > Personnel > Crew Management
This register lists the various criteria for performing employee evaluations. The criteria are used in the
Employee Overview window Service tab under the Evaluation button.
3.17.7 Rank
File > Open Register > Personnel > Crew Management
This register lists the various ranks your company uses. The ranks are used in two places in AMOS
Personnel; in the Employee Overview window General tab and in the Employee Overview window
Contract tab. See sections 10.1.4 and 10.1.10 respectively for more information.
3.17.10 Trade
File > Open Register > Personnel > Crew Management
This register lists the trade areas (i.e. continents, seas, etc) frequented by your company vessels. The data
is used in the Vessel register. See section 3.17.11 for more information.
55
3.17.11 Vessel
File > Open Register > Personnel > Crew Management
Input the details of the company vessels into this register. If the AMOS Business Suite with Personnel
is to be used onboard the companys vessels as well as in the office, then it is recommended that each
vessels details are added to the database while you are in the installation department for that vessel. For
example, if the vessels name is AMOS Explorer, you should switch installation to AMOS Explorer
and register the details there.
56
Each position on the vessel has a normal Operational manning requirement (the number of personnel
normally employed in that position), and a Minimum requirement (the legally justifiable minimum
required to run the vessel safely).
Use the License Profiles table to define the licenses and certificates that must be held by the employees
to be selected for the various positions on the vessel.
3.17.14 Category
File > Open Register > Personnel > Employee
This register defines the codes and descriptions of the various categories of personnel within your
organisation.
3.17.19 Institute
File > Open Register > Personnel > Employee
This register defines the various educational institutes and schools that employees have attended to gain
qualifications. The data is used in the Employee Overview window Educ/Lic tab.
57
3.17.20 Marital Status
File > Open Register > Personnel > Employee
This register is a list of the possible marital statuses that company employees may have. The data is used
in the Employee Overview window General tab.
3.17.22 Sickness
File > Open Register > Personnel > Employee
This register is a list of the various illnesses that employees may contract. The data is used in the
Employee Overview window Medical Info tab.
58
Note The document types are listed in the Standard Document register in alpha/numerical order based on the
codes.
You must link a new document category to the specific Employee Detail tab in which you want it to
appear.
3.17.29 Airport
File > Open Register > Personnel > General
This register is a list of the airports that the employees need to use. The data is used in the Employee
Overview window.
59
3.18 Payroll
The Payroll registers are accessed at File > Open Register > Payroll. Read about these registers in more
detail in the AMOS Personnel User Guide.
3.18.1 Accumulators
File > Open Register > Payroll > Accumulators
This register is for defining the codes and descriptions for the various accumulators that wage types can
be linked to in order to be accumulated.
3.18.2 Bank
File > Open Register > Payroll > Bank
This register defines the information for the different banks that employees belong to.
3.18.5 Period
File > Open Register > Payroll > Period
This register defines the Month and Year of the first period when you start using the payroll.
60
3.18.6.1 The Options Menu for Wage Types
Edit Formula
To use a wage type in a calculation, place the cursor in the Wage Formula field and select Options > Edit
Formula. The Wage Formula window opens and you can make changes to the formulas for wage types
and accumulators as necessary.
Clear Formula
Select Options > Clear Formula to clear the Wage Formula field.
Click the New button to get a blank line and enter a value. You do not need to specify a currency - your
Base Currency Code is used by default. The Approval Limits are automatically sorted in ascending
order the next time the window is opened.
Since Approval Limits apply to Groups and not Users, any User that is a member of a particular Group
can approve purchases at a level less than or equal to their Approval Limit. If the User is a member of
more than one Group, then the highest Approval Limit of the Groups the User is a member of applies.
See Chapter 14 for assiging Approval Limits to Groups.
61
3.19.3 Cost Centres
Tools > Configuration > Accounting > Cost Centres
Cost Centres are separate financial areas that you register expenses against and record where resources
are used. A Cost Centre can be a Department, a collection of Departments, a machine or collection of
machines or any other unit/collection of units that your company wants to record transactions and costs
against.
This register is for defining and maintaining Cost Centres. To read more about Cost Centres and their
use in accounting, see Chapter 5.
62
Chapter 4 Export/Import: Data Synchronisation
Data Synchronisation is the process by which data is transferred between sites within your company. The
most common type of transfer is between the head office site which contains all data from all sites, and
the various remote sites. This chapter briefly explains the process of exchanging data between the head
office and the remote sites within your organisation.
Select File > Export/Import to access the sub-- menu containing the commands for exporting data from
and importing data into AMOS Business Suite databases.
63
4.2.1 Tasks
To create a task to handle export of data from the local database, import of data to it, or handle other
automated tasks, proceed as follows:
1. Select File > Export/Import > Tasks to access the export/import Tasks window.
2. The filter appears first; if you are searching for an existing task enter some details to restrict the
list. Otherwise, click OK to open the window.
3. Click the New button on the toolbar to create a new task, and provide the following information:
64
- If the task is only performed on certain days of the week, make sure that the correct weekdays
are checked.
S The Pre-- process and Post-- process fields are for naming batch files to carry out before and after
the selection file. The file extensions .Bat, .Com and .Cmd can be used. For example, a
Pre-- process batch file may be defined to get e-- mail files containing data to be imported by a task,
and a Post-- process batch file may contain commands to delete imported files. Such files should
be located on the same directory as the Selection File for the task. If not, the full path of such files
should be provided.
4. A defined task can be temporarily de-- activated: remove the checkmark from the Task Active box
of the desired task. Checking the box specifies that the task will run when the Task Server is
activated.
5. Save your task.
To perform a defined task manually:
6. Select the appropriate task in the list part of the window.
7. Go to Options > Perform Task to execute it.
A checkbox labelled Remote Work Flow will also be present in the Formats list, if the system
parameter Use Remote Work Flow is set to TRUE. Read about Remote Work Flow in Chapter
17.
3. Click OK. The tasks being processed are listed in the Task Server window. You can delete tasks
here if necessary.
65
Note To automate the task server operations using command line parameters:
The parameters available are:
S /Login=user/password
S /Taskserver=all | import | export | generic
S /StartIn=inst/dept
Example string:
C:\Program Files\AMOS\AMOS Business Suite\amosw.exe /Login=sysop/abcde
/Taskserver=all /StartIn=002/01
66
4.4 Selection File Commands for Import and Export
During data import or export, command files with the file extension .SEL specify how to handle the
import or export. There are two types of selection files: import and export.
67
4.4.2 Import Selection Files
Import selection files control the information that is received at the importing site. It is during these
imports that AMOS enforces database integrity: that is, a file is not imported unless all the information
is either already in the system or in the file you have received. If information is missing, the import will
fail. For this reason, the order in which files are imported is crucial.
The following commands apply to imports:
InsertData <On/Off>
Controls whether new table entries may be added during an Import operation. When On, new records
will be inserted into the database. When Off, no new records will be inserted.
StampDate <On/Off>
If this is set to On, the new or updated table has the field LastUpdated set to the current date during
import. If set to Off, the date in the LastUpdatedField remains the same. This is useful for importing data
and then resending the data to other sites.
StampMark <On/Off>
Controls whether the new or updated table entries have their ExportMarker field set during import. If
set to On, the new or updated table will have its ExportMarker field set to one (1) during import. Set to
Off, the value in the ExportMarker field remains the same. This is useful for importing data and then
resending the data to other sites.
OverwriteOldData <On/Off>
Controls whether updates to already existing table entries is allowed during import. If On, existing
records will be updated with the values in the imoprt file. Set to Off, no existing records will be updated.
IgnoreDeleted <On/Off>
When set to On, deleted records are not imported. Set to Off, the deleted records are imported.
Department All/<Installation number/Department number>
Specifies which installation and department to import data into. Use Department All to import from all
installations and departments.
Register <TableName>
Specifies which register (table) to import. You can combine this command with a criteria for import in
the form of an SQL restriction, as below. Note that the keyword is If:
If <SQL Select Statement>
Allows you to specify the criteria that the table entries must satisfy to be imported.
When using If statements, add the text amos. to specify additional tables within the search
criteria.
ExcludeFields <Table Field List>
Allows you to specify any table fields not to update during import; all other fields are
automatically included. This command cannot be used in combination with the command
IncludeFields.
IncludeFields <Table Field List>
Allows you to specify which table fields to update during import. All other fields are
automatically excluded. This command cannot be used in combination with the command
ExcludeFields.
The following keywords apply to import selection files:
LastExportedDate - the date of the last export for the specified installation/department;
LastImportedDate - the date of the last import for the the specified installation/department; and
Today - the current date.
68
4.4.3 Selection File Examples
Example 1:
MarkedRecordsOnly ON
UnmarkExportedRecords ON
Register Component
Register JobDescription
Example 2:
MarkedRecordsOnly ON
UnmarkExportedRecords ON
Register OrderForm
If ( FormType In (1,3) ) And ( FormStatus In (2,3) )
The If command is followed by an SQL statement defining the criteria that must be satisfied before
exporting a form.
The FormType field may have one of three values:
S 1 indicating a Purchase Order
S 2 indicating a Requisition Form
S 3 indicating a Query
The FormStatus field may have one of five values:
S 1 indicating Active
S 2 indicating Parked
S 3 indicating Filed
S 4 indicating Split
S 5 indicating Cancelled
The above Register command will only export order forms if they are of the type Purchase Order or Query
with the status of either Parked or Filed.
Example 3:
MarkedRecordsOnly ON
UnmarkExportedRecords ON
Register OrderLine
If OrderID In (Select OrderID From OrderForm Where ( FormType In (1,3) )
And (FormStatus In 2,3) )
This Register command will only export order lines attached to order forms of the type Purchase Order
or Query with a status of Parked or Filed.
Read the above If statement as follows:
Export the order line if its OrderID (that is the ID of the order to which it is attached) is in the set of
OrderIDs in the OrderForm table satisfying the condition that the order form type is PurchaseOrder or
Query with the status Parked or Filed.
Example 4:
MarkedRecordsOnly Off
Register ComponentType
If ( CompName Like %pump ) And ( VendorID In ( Select AddressID From Address Where Code Like
%SPEC))
This Register command will only export components types where the name contains the text pump and
are delivered by a vendor name that contains the text SPEC.
69
Example 5:
InsertData On
OverwriteOldData On
Register ComponentType
ExcludeFields Misc1
If ( CompName Like %PUMP)
This Register command will only import component types where the name contains the text pump, but
the field Misc1 will not update during the import.
Selection File Keywords
Three selection file keywords are implemented in AMOS. These are called Today, LastExportedDate
and LastImportedDate, and they make it possible to create very flexible selection files. Examples are
shown below.
Note When using keywords enclosed within parentheses (brackets) it is necessary for there to be a single space
between a parenthesis and the keyword.
Example: If ( LastExportedDate ..)
or If (.. LastImportedDate )
Today
If this keyword occurs in the selection file, it is replaced by the current date. Since all dates in AMOS
also contain a time component, the value substituted for the Today keyword depends on how it is used.
For example, in >=Today may be replaced by 1998-- 05-- 14 00:00:00.00000 if the date is 14 May. If the
expression <=Today is used for the same date, the replacement value is 23:59:59.99999.
LastExportedDate
If this keyword occurs in the selection file, it is replaced with the date/time of the last export performed
for the installation and department in question.
LastImportedDate
If this keyword occurs in the selection file, it is replaced with the date/time of the last import performed
for the installation and department in question.
Here are some examples of how to use these keywords:
Register WorkOrder If DueDate <= Today
Register WorkOrder If LastUpdated Between LastExportedDate and Today
Register WorkOrder If LastUpdated >= LastImportedDate and LastUpdated <= Today
Avoiding Problems with Import and Hierarchies
To avoid problems with hierarchies during import and export operations, use the command InitDBCmd
in the [Import] section of the AMOSW.INI file. The following examples show how to use it for the SQL
Anywhere and Oracle databases respectively.
SQL Anywhere:
[Import]
DBMS=ODBC
.
.
InitDBCmd01=SET OPTION WAIT_FOR_COMMIT = ON
Oracle:
[Import]
DBMS=OR8
.
.
InitDBCmd01=SET CONSTRAINTS ALL DEFERRED
70
Other Ways to Access Database Commands
You can press the CRTL SHIFT F9 keys together to access database commands. This opens a dialog
box where you select a command file to execute commands.
You can also add import and export commands in the [Import] and [Database] sections of the
AMOSW.INI file. If you do, number them from 01 to 99. Here is an example:
[Database]
DBMS=OR8
.
.
InitDBCmd01=Alter Session Set Optimizer_Mode= First_Rows
71
S File Extension for Export Files - the system maintains a sequence number for both import and
export operations. Since these sequence numbers are used to name the files created by these
operations, it is important to be able to differentiate between files created by export and ready for
transfer to another site and those received which are ready to be imported. This is done by defining
different file extensions for the various files handled by the Import/Export module. This
parameter defines the extension for export files generated by the system.
Default setting: EXP
S File Extenstion for Hand Terminal Files - a hand terminal may be used to record stock
transactions. The data from the hand terminal may be exported in the form of a file, which may
then be imported into AMOS stock levels. This parameter specifies the file extension for such
hand terminal files.
Default setting: HTD
S File Extension for Import Files - as a complementary parameter to the parameter File Extension
for Export Files, this value defines which extension identifies files ready to be imported by the
system.
Default setting: EXP
S File Extension for Successfully Imported Files - as a complementary parameter to the previous
one, this value defines which extension is to be given to import files that have been successfully
imported by the system.
Default setting: OK
The File Extension for Export Files and File Extension for Import Files are typically set in opposite
ways on a location and at the head office.
72
4.7 Import Log
Go to File > Export/Import > Import Log to view the Import Log. This is a log of the import operations.
There are four parameters associated with the portal log entitled Log Successful Portal Operations,
Show Error Messages During Portal Import, Show Error Messages During Portal Export and Store
Imported XML Document In Portal Log. These parameters are described in section 15.5.
Select Show XML in the Options menu for the portal log to display the stored XML document for the
selected portal log record.
73
Chapter 5 Account Transactions
Accounting functionality in AMOS is activated by a separate license, and provides a record of each
Account Transaction, its Type (Credit or Debit), the Cost Centre, Account Code, and all associated
transaction data.
Financial transactions are logged in the Account Transactions window as they occur. Transactions which
users perform in the following areas of AMOS are registered as Account Transactions:
S Vouchers
S Transport Documents
S Stock Transactions - Purchase Order Receipt, In/Out of Stock, Stock Control
S Transfer Document Transfer/Receipt
S Work Order Reporting
Once a transaction is listed in the window you can alter it if unlocked. With the correct level of access
control, you can generate manual transactions here as well. Manually created transactions can correct
locked transactions that are incorrect. To read about Account Transaction functionality, see section 5.1
Tracking Account Transactions.
The Tools > Configuration > Accounting > menu gives access to other windows which are used when
setting up your system to use Account Transaction functionality. These related windows and tasks to be
performed are described below in section 5.2, How to Set Up Account Transactions.
Note If On Board Accounting is activated in your system, then at the bottom of this window you can include
employee and period information in the account transactions, using two additional fields called
Employee and Period.
74
5.2 How to Set Up Account Transactions
The AMOS Business Suite Accounting module provides the ability to tie every Transaction that takes
place to a particular Account Code, which in turn can be assigned to Cost Centres.
If your system license includes the Accounting module, to set up and use Account Transactions:
1. Define your Cost Centres and grant Access Rights
2. Define Account Code Categories, and Account Codes
3. Link the Account Codes to Cost Centres
4. Track Account Transactions
75
The Cost Centres window contains an Options menu allowing you to add one or more Account Codes
(with Budget Codes if required) to each cost centre. These will then be the available accounts for the
selected cost centre. Read about linking Account Codes to Cost Centres in section 5.2.3.
76
5.2.2.2 Account Codes Register
Account Codes are defined and stored in the register at File > Open Register > General > Account
Codes. The Account Codes are assigned to Account Code Categories as discussed in the section above,
and then become available on purchase forms.
To create the Account Code Categories available in the drop-- down list see section 5.2.2.1.
To create a new Account Code:
1. Select an Account Code Category.
2. Click the New button on the toolbar.
3. Enter a Code and Description.
4. Activate the Account Code by checking the Active checkbox. This can be unchecked at any time
to deactivate the code.
77
Chapter 6 Audit Trails
When an Audit Trail has been placed on one or more columns in a table within the AMOS Business Suite,
you can track every change made in the selected window/field(s): the original value, the new value, the
date of the change made, the operation performed on that record (i.e. insertion, deletion or update), and
the user ID of the person who made the modifications. The results of an Audit Trail can be viewed in
the Audit Trail Log window. It is also possible to record all login activities on the system, in the Login
Audit Log. If Audit Trails and Login Audit Logs are already set up and enabled in your system, you can
read about viewing the logged results, in section 6.1 Viewing the Results of an Audit Trail.
The Tools > Configuration > menu gives access to the Audit Trail Configuration window which is for
setting up and enabling Audit Trail functionality. This related window and tasks are described below in
section 6.2 How to Set Up an Audit Trail.
78
The Audit Trail Configuration window is divided into sections. The left hand side displays a list of tables
that contain an audit trail trigger. The middle part of the window displays a list of columns belonging
to the table selected on the left that are part of the audit trail trigger. The right hand side contains a list
of user groups.
To create a new Audit Trail Configuration:
1. At the bottom of the Table section, click the New Table button and a blank line will appear.
2. Use the lookup button beside the blank line to select a table from the list of available tables.
3. In the Column section of the window, click the New Column button. A blank line will appear.
Note that this refers to the selected table only.
4. Use the lookup button next to the line to select the column you wish to audit. You can add as many
columns as necessary. Delete selected tables and columns by clicking the Delete buttons at the
bottom of the window.
5. Check the boxes of the User Groups to assign Access to the audit trail results in the Audit Trail
Log window.
6. Save the configuration.
7. To enable the configuration, select Options > Generate Triggers. In the dialog that appears, click
Yes. If you do not do this, you will be prompted to do so on closing the window. You must generate
the triggers to enable the configuration you created.
Once configured and enabled, the Audit Trail can be viewed in the Audit Trail Log window or in the
Audit Trail tab available on some windows.
79
Function Based System
Class Code and Criticality Changes - Functions
Due Date Changes - Functions
Planned job Changes - Functions
If a user tries to execute any of these reports before the audit trails are in place, the reports will not run.
To ensure that all the necessary columns are added correctly, simply go to Options > Add Bureau
Veritas columns. In the dialog which appears, click OK and the appropriate tables and columns are
added automatically. Assign User Group Access as described in section 6.2.1. Save the configuration
and enable it by generating the triggers, as above.
80
Chapter 7 Running and Printing Standard Reports
The AMOS Business Suite contains a set of standard reports, stored in a hierarchy in the Reports browser
window. You can also create electronic versions of reports, called Powersoft Reports (PSR Reports).
Read about these in section 7.1.
It is also possible to make and include your own user-- defined reports. See Chapter 28.
Go to Tools > Report to open the Reports window to select the report (pre-- defined or user-- defined) to
be run.
The reports are structured in folders. Click a folder to view its contents. When a folder is selected, the
defined reports of that category are shown in the list on the right.
To run and print a report:
1. Double-- click on it. A filter appears, with controls for specifying what the report should contain.
The filter is different for each report.
2. Specify the content you want included in your report. After specifying parameters, you can
preview the report or print it immediately.
3. Click Print Preview to preview the report on the screen before printing. For example, the preview
may look like this:
81
Figure 91 A Typical Report in Print Preview Mode
Click the Zoom button to select the zoom level. Use the four buttons to the right of the Zoom
button to browse the report pages: First Page, Previous Page, Next Page and Last Page.
After previewing, click the Print button on the toolbar.
The Print dialog opens, and you can print as usual. Your default Printer appears at the top of
the dialog. To print to another printer instead, click the Printer button. Then select a Printer in
the Printer Setup dialog. Otherwise, just click OK to print the report.
4. To skip the preview and print immediately, double-- click on the report and specify your
parameters in the filter. Then click OK in the filter to go straight to the Print dialog. Print to the
default printer by clicking OK again, or change the printer first using the Printer button.
Note If, in the Reports Preview window, you want to save the report as a PDF file, you will first need to install
a secondary freeware program - Ghostscript - on the computer. You can find a list of alternative mirror
sites from which you can download the application, on the Ghostscript Web site at:
http://www.ghostscript.com/doc/gnu/gnu705.htm
After downloading, run the executable file to install Ghostscript on your system. The default installation
folder is C:\gs. You can select a different folder and/or choose to install shortcuts to the Ghostscript
console and readme file.
82
Chapter 8 Hand Terminal Interface
A general file format allows AMOS Business Suite to support several standards. To support all the hand
terminal formats that exist, it is necessary to have a converter application. One such application is already
developed, and its source code is available for developers.
1. Go to Tools > Hand Terminal Interface. The window shown in Figure 92 appears.
2. Click the Select Department button and select the department from the window that pops up and
click OK.
3. Click Select Hand Terminal File and choose the file to import. You can set the default directory
for Hand Terminal Files see section 15.4.
4. After selecting the desired file, click the Read Hand Terminal File button to start the import of
data from the selected file.
83
O = out of stock
I = insert into stock
C = Stock Count
You must set the date in the given format.
84
Chapter 9 Self Assessments and Statistics
Note Self Assessment is a separate module and as such requires its own license key to activate and use it.
Without the license and user read access, the Self Assessment windows will not be visible in the Tools
menu or possible to use in the system.
The Self Assessment module allows your company to perform a self assessment of compliance with
Tanker Management Self Assessment (TMSA) requirements and standards. Self Assessment is a tool for
organising Key Performance Indicators (KPIs) within Elements and Sub-- Elements for assessment, and
a way for you to measure and evaluate your company. Performing regular Self Assessments ensures
continual improvement within your organisation. A minimum compliance to all elements of the standard
establishes the baseline from which your company will improve.
You should perform self assessments to:
S review the existing systems and practices within your organisation and evaluate these against
industry standards
S record performance and compare progress
S provide documented evidence in case of audits
The Self Assessment functionality is contained in three main windows. If Self Assessments are already
configured and in use in your system, users can:
S Perform an Assessment - a user performs periodic self assessments. That user evaluates each
KPI according to the present stage, and then compares the new assessment against previous results
to evaluate progress. See section 9.1.
S Analyse and review the data - the assessment data and the calculated scoring can be reviewed
in the Self Assessment Statistics window. See section 9.2.
To read about setting up the configuration of elements, sub-- elements and KPIs which users will perform
the assessments against, see section 9.3. The window for configuring a Self Assessment is found at Tools
> Configuration > Self Assessment.
One or more users must be assigned the responsibility to perform periodic self assessments. That user
evaluates each KPI according to the present stage, and then compares the new assessment against
previous results to evaluate progress.
There are several reasons why you may perform a new self-- assessment revision:
S It is the first time you have incorporated the Self Assessment module at an installation
S The standards you are comparing your company to have been changed and you must evaluate
against yourself against newer or more strict criteria
S You perform assessments at intervals and the appointed time has arrived
S You have changed the Work Flow Status of a previous Assessment revision (ie. cancelled it, issued
it, assessed it, etc) and so a new one is now required
Every Self Assessment is a new Revision. The exception to this rule is if you have a revision in progress,
that has not yet been scored and issued. In such a case you can continue to open the same revision and
add to it, at its initial status, until it is finished and ready to be assessed and issued through the Work Flow.
Previous assessments are stored as separate revisions and retained for historical evidence and
comparison. Each Self Assessment revision refers to a revision of the self assessment configuration.
Every new assessment revision is evaluated against the most recently issued set of configurations.
Meeting the KPIs in each element with a 100% score indicates that your company is performing at the
top standards demanded by the industry. To receive 100% on the element, you must receive 100% on
each KPI that belongs to the selected element.
85
To open the Self Assessment window, select Tools > Self Assessment:
The left side of the window contains a hierarchy view of the assessment revisions. If this is a first revision,
the hierarchy contains only one level, the current Draft or Active revision. The configuration revisions
are work flow controlled and only one Draft and one Active revision can exist at a time.
If other assessment revisions exist:
S Double click the revision number, or click the plus sign beside it to expand it and display the list
of elements evaluated against in that revision.
S Select any element to open it in the General tab and display the associated KPIs and the scoring,
if that element has been scored already.
86
9.2 Self Assessment Statistics
Go to Tools > Self Assessment Statistics to open a window containing the assessment data entered in
the Self Assessment window and the calculated scoring. Select the assessment you want to view the
details for in the tree view. The applicable information will appear in the tabs.
This tab contains one graph for each of the four TMSA stages. The horizontal axes display the number
of elements in that stage. The vertical axes display the percentages 0 to 100. Select an assessment revision
in the tree view and its scores for each element, in each stage, will appear in the graphs.
The list part of the Elements tab displays the same values as in the Graphs tab, for the selected assessment
revision, with the score for each element in each stage. The last column in the list, Score, displays the
average score for each element throughout all the stages, and the average score for all the stages.
The graph in the bottom left corner displays the stage each element has completed.
A stage is completed only when you receive a score of 100 for that stage, and every stage before it. For
example, to reach stage 3, the scores for stages 1, 2 and 3 must be 100. In this case, the graph would then
display a bar for that element reaching to stage 3.
87
The graph in the right hand corner displays the average score of all elements combined, for each of the
stages. At the bottom of the chart, the row called Score displays the average score of all the sub-- elements
for every stage. The last field in this row, at the far right, contains the average score of all the stages.
This tab contains a chart displaying the scoring for the sub-- elements. Each sub-- element appears in the
list, and the score for each sub-- element at each of the stages. The Score column contains the total score
for each sub-- element across the stages.
88
The configuration revisions are Work Flow controlled and only one Active and one Draft revision can
exist at a time. You must render an Active configuration revision Obsolete (AMOS Action File) to create
a new one with status Draft. When a revision of the configuration is ready, use the Work Flow to activate
it (AMOS Action Issue), and that configuration revision will become available in the Self Assessment
window, the next time a user performs a Self Assessment. The Work Flow dialog is accessed from the
Options menu.
There are three system parameters which control certain aspects of self assessment configuration, such
as the kind of answer a user can provide for a KPI. These parameters are explained in section 9.3.5.
At any time, you can create a new Configuration Revision or change an existing one. To create an entirely
new revision, proceed through the next four sections in order. To add an element, sub-- element, or KPI
to an existing revision, see the relevant section(s) only.
Note Self Assessment configurations are work flow controlled. The statuses in the Self Assessment Statistics
filter are hardcoded to Active and Obsolete and so we recommend incorporating these terms as the
user defined statuses when defining the Self Assessment Work Flow. (See Chapter 17 for general
information on configuring Work Flow).
2. Enter the name of the element, and its Weight Factor (this is a percentage of value the selected
element should have in comparison to the others).
3. Continue clicking the New button and adding as many elements as applicable. To remove an
element, select it and click the Delete button.
89
4. Save the new Element.
2. Fill in the name of the Sub-- Element, and its Weight Factor (this is a percentage of value the
selected sub-- element should have in comparison to the others).
3. Continue clicking the New button to add as many sub-- elements to each element as needed.
Remember to select the correct element first, if you are adding sub-- elements to more than one
main element.
To remove a sub-- element, select it and click the Delete button.
4. Save your information.
90
Figure 100 Adding a New KPI
3. Enter a name for the KPI, and a Weight Factor (this is a percentage of value the selected KPI
should have in comparison to the others).
4. The fields labelled 0% and 100% are for entering guidelines or boundaries. When the user is
scoring the assessment, these boundaries are a suggestion to help him/her determine the accurate
score. For example (according to the scope of the KPI) the boundaries could be as simple as Yes
and No - in other words, if your company complies fully with the KPI (Yes), the user enters a score
of 100%. If your company does not comply at all the with KPI (No) the user enters a score of 0%.
If your company partly complies with the KPI, the user can then enter a score of 50%, or according
to the amount of improvement needed.
5. To define that the answer must be either Yes or No with no other possible answers accepted, check
the Yes/No Answer box. If this box is checked, the 0% and 100% fields will become unavailable.
The user no longer has to use percentages to score the Self Assessments (for this KPI) but simply
provide a Yes or No answer.
Checking the N/A Option checkbox for a KPI gives the user the option to mark this KPI as not
applicable. If this box is not checked, answering N/A on this KPI is not allowed. If allowed, and
a user registers N/A as the answer, AMOS will prompt for a reason and enter this in the Remarks
field.
Yes/No and N/A answers are parameter-- enabled. See section 9.3.5.
6. You can add a Best Practice Guideline to the KPI. This is a description of the best possible
practice as defined by the industry, that would ensure a score of 100 % on the selected KPI. It
provides further guidelines to compare your company to. To add a Best Practice Guideline, click
the Guide button in the KPI section or go to Options > KPI Best Practice Guide Line. In the
description window that opens, enter the guideline.
7. Save your information.
91
Sub Element Start Code
Use this parameter to set the starting code for sub-- elements: should the first sub-- element within an
element have no code (followed by the next with code A, B, etc.) or should the first sub-- element have
code A (followed by B, C, etc.). These are indicated by setting <SPACE> for no code, or A.Default
setting: <SPACE>
Default setting: YES=0% AND NO=100%
92
Chapter 10 Overview Panels
Using AMOS Overview Panels gives users a quick status overview in different areas of AMOS - for
example, an Overview Panel can be designed to display overdue maintenance work in several different
ways, all in one place:
S gauges to show the total percentage of overdue work and the number of work orders due in the
next 30 days
S ratios showing the amount of unplanned work vs. planned work, planned work vs. total work due,
etc.
S graphs to show the amount of overdue work by maintenance cause and overdue work by
installation.
These gauges, graphs and ratios together would comprise one Overview Panel.
First, configure these panels to display the information you are interested in. Then, the results of your
configurations will be displayed in the Overview Panels window.
The window for viewing Overview Panels is located at Tools > Overview Panels. See section 10.1.
The window for configuring an Overview Panel is located at Tools > Configuration > Overview Panels
Configuration. See section 10.2.
93
Figure 101 Configuring a Panel for a Maintenance Overview
2. In the bottom half of the window, enter a Panel Name and Panel Description directly into the
list. This is the name for the entire panel and will remain there when you click on any of the
graphs/gauges. Define an individual Name for each gauge and graph in turn as you click on one
to set it.
3. Setting the ratio boxes and gauges may be done by dragging and dropping SQL statements from
any list view, into the SQL Maximum, SQL Primary and SQL Secondary boxes. This is done in
the same way as when defining alerts to appear on the dashboard. See section 19.1.2
(Automatically defining alerts), for more information. The three different SQL statements
control the displayed values as follows:
- SQL Maximum - defines the maximum value on the gauge itself.
- SQL Primary/Secondary - control the position of the first and second indicator lines on the
gauge.
Figure 102 A gauge. Max value 100, two indicators defined by SQL Primary/Secondary
94
4. To define the settings for the two graphs, click a graph and the DataWindow Syntax area becomes
active. Use the lookup button next to it to load the data window syntax from a PBL file. Any data
window syntax is valid so the presentation may not necessarily be a graph.
5. Save your settings and the Overview Panel will become available.
The Access tab contains a list of all defined Groups in your system and you can grant access to the
appropriate groups for the selected panel.
The result of these settings is displayed in the Overview Panels window at Tools > Overview Panels.
95
Chapter 11 Changing Passwords
You can change your own password at any time. Depending on your access rights, you may also be able
to change other users passwords for them.
For a user to change their own password, they must belong to a group with access rights to change
password. Set this at Tools > Configuration > Groups > Options > Access Control. The checkbox for
change password is in the Functions tab.
96
11.2 Changing Another Users Password
If you have the correct access rights, you can change another users password for them:
1. Open the Users window: go to Tools > Configuration > Access Control > Users.
2. In the window, select the user whose password you want to change.
3. Go to Options > Change Password. The same dialog as shown in section 11.1 above, opens.
4. Change the password the same way. The same parameters as described above may affect the
password.
5. Click OK to exit the dialog and return to the main window. The password is now changed.
6. Save before leaving the window.
97
Chapter 12 Options: Customising the AMOS Interface
The Options window allows you to customise certain aspects of the appearance and behaviour of the
AMOS Business Suite user interface. The settings you define here apply when you, the current user, are
logged in. Other users can enable their own settings which activate when they are logged into the system.
Access to these features is determined by the User Options entry in the Access Control Functions tab.
Without access you cannot reset options.
Select Tools > Options to open the Options window. This window can also be accessed directly from
the Task bar via a shortcut button. The window contains six tabs for customising the following aspects
of the AMOS Business Suite:
S General
S Views
S Predefined Fields
S Predefined Filters
S Dashboard
S Theme
98
S The Toolbar tips option controls whether a text description (tooltip) appears when the mouse
cursor is positioned over an icon on either the Standard Toolbar or the Window Toolbar.
S The Toolbar text option controls whether toolbar icons are displayed with a text description
below them. This feature is particularly useful for new users.
S The Confirm on Exit option controls whether the application requests confirmation prior to
exiting.
S If you check the box for Warning on Filter Without Given Criteria AMOS will issue a warning
message whenever you try to click OK to bypass a filter, anywhere in the system, without entering
any search criteria. The warning serves as a reminder that entering search criteria will shorten
both the listed results returned, and the wait time.
S The Windowing mode option gives the user the choice of opening windows as Maximized or
Cascaded. All open windows must be closed to activate this option.
S The Mailbox/Dashboard Check Interval (sec) field is used in conjunction with work flow. Enter
the number of seconds between checks in the field. Each time a check is made, the user is alerted
if there are any unacknowledged notifications in the Work Flow Notifications window.
S Idle Time Out (min) allows you to set the amount of time, in minutes, for which AMOS can be
idle before it locks. Once this amount of time has passed, the windows will remain open but the
logon dialog will appear and the current users password must be supplied before access is
allowed again. This function is disabled when set to 0. If enabled, the item Lock Application will
also appear on the File menu and can be manually selected at any time.
S The Standard toolbar position option controls the on screen position of the Standard Toolbar
i.e. Top, Bottom, Left, Right or Hidden.
S The Window toolbar position option controls the on screen position of the Window Toolbar i.e.
Top, Bottom, Left, Right or Hidden.
S The drop-- down under Tabs lets you choose whether window tabs should appear all in one line
with arrows to scroll through the tabs that are not visible, or stacked in multi-- lines and all visible
in the screen.
2. Open the Views tab and click Private, Group or System. Each of these opens the same New
View dialog. The difference is whether you want to create the view to be accessible only to you,
the logged in user - Private; to a particular user Group; or System-- wide.
Whether you are allowed to create views, and the scope you are allowed to select for each one,
depends on your access rights. Your access rights also determine if you are allowed to make
adjustments to existing views, or add or remove Groups from the Access list in the case of Group
views.
3. Enter a logical name in the Description field, in this case Stock Control. Click OK to return to
the Options window.
4. If you created a view with Group Scope, check the boxes in the Access column next to the Groups
who should be able to select this view.
5. Click Save. The next time the system is started, this view will be available for selection according
to its Scope and the identity of the logged user.
99
Figure 105 The Views tab
In addition to creating new Views, you can Update existing views, Delete views that are no longer
required and set one of the views as the Default view. Checking the Startup using default view
checkbox means the application automatically opens with the default view opened. Whether you can
adjust or delete existing views or change the default view to be used at startup, depends on your access
rights.
Selecting Tools > Select View or pressing the F6 key, opens the Select View dialog box with a list of
available views. Select a view by clicking on it and then click OK. This restores the various windows
and filter criteria associated with that view.
The List Bar or Icon Bar on the left hand side of your screen at all times, contains collapsible menus or
tabs with shortcuts to frequently used areas of the application. You can set your list of Views to appear
in the List Bar/Icon Bar underneath the Main menu/tab. Then, you can select a view from the bar at any
time without having to open the Tools > Select View window. The view will open up in place of the
window you were in. To display the list of Views in your bar, ensure that the List Bar/Icon Bar radio
button in the Options window General tab is On. Two shortcut buttons in the Task bar also open the list
of Views, and the Options window itself.
100
5. When you are satisfied with the windows predefined fields and layout, go to Tools > Options.
Open the Predefined Fields tab.
6. The tab contains buttons, available according to your access rights. Click one of the buttons to
save the windows layout:
S Private - if the currently open window is supported, a new record is inserted into the predefined
fields list with Scope set to Private. This means the saved configuration will apply only to you
as the current user.
S Group - if the currently open window is supported, a new record is inserted into the predefined
fields list with Scope set to Group. This means the saved configuration will apply to certain
Groups only. Groups are listed in the right side of the window and checking the box beside one
allows Access to the window configuration.
S System - if the currently open window is supported, a new record is inserted into the predefined
fields list with Scope set to System. This means the saved configuration will apply system wide.
7. The window containing the field you have modified the layout on appears in the Name column
on the left side of the window.
8. The Group Priority column is for adding a number in case of possible conflict - if a user belongs
to more than one group and each group has access to a different configuration for the same
window, the configuration the user will see is according to whichever one has the highest Group
Priority value set here. When more than one layout is configured for the same window, priority
for the logged in user is according to scope as follows - a configuration with Scope Private is given
first priority. Then, Group (according to the Group Priority number for each one if more than one
exists). System Scope configurations are given the lowest level of priority.
9. Click OK to save the predefined field configuration. Add further windows with predefined fields
in the same way. Click Delete to remove a predefined field configuration from the list.
Now, depending on the Scope and the identity of the logged in user, when one of these window is opened
only the chosen columns appear in the list part of the window. The columns will also appear in whatever
order they were saved in.
101
12.4 Options --- Predefined Filters Tab
In the same way as you can predefine which fields should appear in a window, you can also predefine
default filter criteria to be populated automatically into any given filter, upon selecting the relevant
window from the main menus. This functionality is the same as described in the section above, in regards
to Private, Group or System configurations, access and priority. The difference is, to save a set of filter
criteria, simply open a filter from a main menu (for example, Purchase > Forms). Then set the criteria
exactly as you wish to save it - for example, choose the Vendor to search on, Budget details, Form State
or Approval, etc. Remember that once this configuration is saved, this criteria will always be present by
default on the selected filter (according to scope and priority). This filter information can be changed
or added to upon opening the filter at any given time, but the same saved default will appear again the
next time the filter is accessed.
Once you have selected the criteria you wish to save as default, click OK and proceed to the window.
Then go to Tools > Options and select the Predefined Filters tab. As in the Predefined Fields tab, click
Private, Group or System according to the scope you wish to apply to the configuration. A new record
is inserted into the predefined filter list, with the Scope set accordingly. In the case of Group Scope, check
the Groups which should have Access.
The Group Priority column is for adding a number in case of conflict - if a user belongs to more than
one group and each group has access to a different configuration for the same filter, the configuration
the user will see is according to whichever has the highest Group Priority value set here. When more than
one layout is configured for the same filter, priority is according to scope as follows - a configuration
with scope Private is given first priority. Then, Group (according to the Group Priority number for each
one if more than one exists). System scope configurations are given the lowest level of priority.
102
This tab also contains a list of the defined Alerts that are available in the system. Each user can choose
from this list which Alerts they want present on their Dashboard. To do so:
1. Expand the list by clicking on the + signs.
2. To select an entire Group of Alerts, click on the root. Otherwise, select one Alert at a time.
3. Click the Select button and a checkmark will appear beside the Alert(s). Repeat, to select as many
Alerts as needed.
4. To remove an Alert, select it and click the Deselect button.
5. If any of the selected alert(s) has been configured to allow sending email when a threshold point
is reached, checking the Permit to send threshold email from my client checkbox enables this
functionality.
6. Checking the Show Alert Gauge box will display the selected Alert(s) as a gauge on the
Dashboard, next to the standard bars.
7. Click OK to close the dialog.
8. The next time the application is started, the selected Alerts will appear on the Dashboard.
Alerts will only appear in the Dashboard tab of the Options window, if they have been previously defined
in the Dashboard Alerts window. See Chapter 19 for instructions on defining Alerts.
103
12.6 Options --- Theme Tab
The Theme tab allows you to tailor the appearance of certain aspects of AMOS Business Suite using
predefined or customised themes. You can select a colour scheme from the Predefined Theme
drop-- down list and then set your own customisations in terms of colour and style and position of the
windows, headers and task bar, in the Theme Details area of the dialog. It is not possible to adjust the
settings if the Enable Theme checkbox is not checked. This box must be checked not only to adjust the
settings, but also to apply them throughout the system.
104
Chapter 13 Work Flow Notifications and Mailboxes
Work Flow Notifications, Delegate Mailbox Access, Mailbox Access Log and Transfer Mailbox
Contents are part of the Work Flow module. These items are all available on the Tools menu.
Read about the Work Flow module in Chapter 17.
105
Chapter 14 Users, Groups and Access Control
When a user logs into AMOS Business Suite, a database user called AMOS is automatically used behind
the scenes. This accesses the table of application users to check that the user logging in has a valid
password.
Each AMOS user receives a user ID and a password, validated at login. Users are then assigned to user
groups, which determine access to the various functions in the application. For example, you can grant
access to user-- defined reports to a specific group and then only those users belonging to the group will
have that access. Every User ID must belong to one or more User Groups.
To enable a user to access the system:
1. Create a User ID in the Users window. See section 14.1.
2. Go to the Groups window, create Groups and assign the User to one or more groups. See section
14.2.
3. Assign Access Rights to Groups. See section 14.3 to 14.5.
4. Use the Field Access window to further restrict both the visibility and editing of fields, by setting
access on selected fields and tabs. This access then applies to everyone, taking the logged in users
own access rights into consideration. See section 4.6.
14.1 Users
Every user requires a unique Login ID to access the system. Some companies use logins that represent
a position and not an individual user, for example Chief Engineer or Captain etc. To open the window
where you create user records, go to Tools > Configuration > Users.
The Users filter appears. Use it to specify criteria to narrow your search:
S Check the Only Enabled checkbox to search only for active users.
S Last login date - entering a date in the Users not Logged in After field searches only for users
whose last login date (as listed in the Users window) is before or the same as the given date.
106
The upper right part of the window shows the Groups that the selected user belongs to. A user may be
a member of multiple groups. It is not possible to check or uncheck the Active box in the Users window;
this is done in the Groups window. See section 14.2.
If you did not filter for Only Enabled users, a user could appear who is Locked Out of his/her account
- the Disabled checkbox is checked. To enable the account uncheck the box. Checking the disabled
checkbox totally disables the highlighted user and prevents their using the system.
To ensure that a user changes his/her password, select them in the list and check the Force New Password
at Login checkbox. The next time this user logs in the Change Password dialog will appear, requiring
them to change their password before they can proceed. The Force New Password checkbox will
automatically be unchecked once the user has changed their password. The selected users last login date
is shown in the Last Logged In field.
To create a new user:
1. Click the New button.
2. Enter the Login ID and the users Name.
In the case that your system license includes crewing you can link an Employee number from the
Employee window, using the Employee drop-- down list. This links together the details for
selected Employee with the Login ID and Name youve just created.
Next, assign a password to the new user:
3. Go to Options > Change Password.
4. The Change Password dialog opens. Type a password in the New Password field, and then
Confirm it in the field below.
5. Click OK to return to the main window.
6. Save the User. Remember that until the User is assigned to at least one Group, the login credentials
will not be valid. See section 14.2 for more on Groups.
4. Click OK to return to the main window. Delete the User in the list whose references you just
moved.
5. Save the changes.
107
If at any time you need to change a users password for them:
1. Select the user and go to Options > Change Password:
2. The Old password is masked for security. Type the New password into both of the lower boxes
to change the existing password.
3. Click OK to exit the dialog and return to the main window. The password is now changed.
4. Save before leaving the window.
Depending on how the parameters affecting passwords are setup, you may encounter an error message
when attempting to change a password.
The Password is not valid message informs you that the Enforce Password History parameter is set
to remember a number of previous passwords - for example if set to 2, the last 2 passwords you have
used will not be accepted now.
The Password is too short message informs you that the Minimum Password Length parameter has
been set to a certain number and the password you enter now must match or exceed that number of
characters.
Either comply with the instructions in the error messages or alter the respective parameters described
in section 15.5.
Note To enable users to change their own passwords, ensure that all users belong to groups that have access
rights to change password if you intend to use the advanced security options. Set this through the menu
option Tools > Configuration > Groups > Options > Access Control. The checkbox for change
password is in the Functions tab.
108
14.2 Groups
Defined users can belong to one or more user groups. Groups determine the access rights that a user is
assigned. A user group may be granted access to a selected department. To create a new group:
1. Select Tools > Configuration > Groups to open the Groups window:
2. Once inside the window, click the New button and enter a name for the Group.
3. Save the group.
4. Click in the Approval Limit field and a drop-- down list with the predefined limits will appear.
Once selected, that is the maximum amount which this group will be able to approve in
purchasing. Read more about Approval Limits in section 14.5.
5. Check the Global Access checkbox to give the group access to all defined installations and
departments. Once checked, you cannot assign or remove access to selected departments:
Options > Department Access is not available.
Unchecking the Global Access box allows you to limit the Departments that the Group will have
access to: while the group is selected go to Options > Department Access and a new window
opens. Check the boxes beside the Departments you want this group to access, and click Save.
Close the window to return to the main Groups window.
Note Another way to limit Department Access for Users in any Group is to take away their ability to switch
Departments (Access Control window > Functions tab > Switch Department). This limits them either
to the Start In Department or the Department they have access to via the command line parameters.
6. The Local checkbox determines whether the access rights set for a Group are local to the
installation you are at, or not. See section 14.2.2 Local Access.
7. Once you have defined one or more groups and one or more users, you link the users to the groups
(see section 14.2.1) and assign access rights (see section 14.3).
109
14.2.1 Assigning Users to Groups
The Members window is for specifying the members of the selected user group. To add a new member:
1. In the Groups window, select the Group you want to assign a user to.
2. Go to Options > Members. The Members window opens.
3. Click New, and click the lookup button to select from the list of defined users.
4. Check the Active checkbox to activate this user as a member within the group. After adding a user
to a group, access can be temporarily restricted by unchecking the Active box. This only
deactivates the user within the selected group: to disable the user system-- wide, check the
Disabled box in the User window.
5. Save your work and the user is added as a member of the selected group.
Users can be attached to more than one group at any time. You can remove a member from a group by
selecting the group and going to the Members window as above, and then deleting the user or unchecking
the Active checkbox. The user will then no longer have that groups access rights.
110
14.3 Setting Group Access Rights
To set different combinations of access rights for your groups, use the Groups window Options menu.
2. Click the New button and then use the lookup button to select the desired budget from the list.
The selected user group may have access to multiple Budget Codes.
To copy access settings from one group to another, while in the Budget Code Access window go
to Options > Copy from Group. A new dialog appears and you can select a group to copy settings
from.
Note All Budget Codes are accessible by all groups unless restrictions are effected:
S If access is granted to no groups, all groups have access.
S If access is granted to all groups, all groups have access.
S If access is granted to some groups, only those specified have access.
111
14.3.4 Procedure Category Access
Any user group can have access to multiple Procedure Categories. To assign access select the group, and
go to Options > Procedure Category Access. Then click the New button and select the desired
Procedure Category. Check the boxes to specify which kind of access should be granted: Read, Edit,
Insert, Delete. The selected user group may have access to multiple Procedure Categories. Save before
exiting this window.
To copy access control settings from one group to another, select the group to copy to in the Groups
window, open the Access Control window, and go to Options > Copy from Group. A dialog containing
all the groups will open and you can choose the group whose rights you want to copy here. Otherwise,
move through the tabs assigning access as appropriate.
Note If your system license includes the AMOS Personnel modules, the Groups Options menu will also show
the item Access Control Personnel. This window works in the same way as described below for the
Access Control window, only in regards to Personnel module-- specific registers, fields, functions and
reports/modules.
112
14.4.2 The Fields Tab
For granting access rights at field level. This tab contains a list of fields with a column of checkboxes
called Execute. Check the box beside every field the selected user group should access.
The Registers tab in the Access Control window also has checkboxes for Read, Edit, Insert and Delete,
but no Execute checkbox. The Fields, Functions and Reports/Modules tabs all contain Execute
checkboxes, but no other columns.
These four other tabs correspond to the Complete System row in the Combined tab. If you give a user
group Read access to the Complete System, they will have access to all the registers on the Registers
tab. By default, they will have Read access on the filter for each register. If you give a group Execute
access to the Complete System, they will have access to all Fields, Functions, and Reports/Modules, as
well as the ability to Insert and Delete data in all registers.
The General row in the Combined tab corresponds to any data windows (i.e. filters) not listed for a
specific access right here. All user groups need to have at least Read and Edit access to this row since
this will allow them to make changes to filters.
For example:
S the System Administrator group needs Execute access to the Complete System and General rows.
S to assign Read Only access for the entire system to the selected user group, the minimum access
rights required are Read access to the Complete System and Read and Edit access to General.
S to restrict the user group in the example above from certain areas in the system altogether, you
would give Read and Edit access on General (but no access to Complete System) and then specify
the particular Registers, Fields, Functions, and Reports/Modules they can see.
113
Keep in mind that access rights are cumulative: having either Insert or Delete access to a particular
Register implies that the Users in that Group will also have Read and Edit access to the Register.
However, assigning Delete access does not give Insert access by default or vice-- versa.
Click the New button to get a blank line and enter a value. You do not need to specify a currency - your
Base Currency Code is used by default. The Approval Limits are automatically sorted in ascending
order the next time the window is opened.
Since Approval Limits apply to Groups and not Users, any User that is a member of a particular Group
can approve purchases at a level less than or equal to their Approval Limit. If the User is a member of
more than one Group, then the highest Approval Limit of the Groups the User is a member of applies.
114
1. To create a new grouping, click the New button on the toolbar or go to Edit > New Record. You
can remove a line using the Delete button or Edit > Delete Record.
2. Select a grouping to add fields to. There are two ways to add the field or tab reference: by Point
and Click or Drag and Drop.
Either:
S Keeping the Field Access window open, open up another window and click in any field or tab.
Return to the Field Access window and click the New button at the bottom of the right side of the
window. The reference for the field/tab you just clicked, will be listed. Keep in mind, clicking
the New button causes AMOS to automatically add the last field/tab you clicked in outside this
window. Or,
S Keeping the Field Access window open and visible, open the window containing the fields you
want to define read-- only access on. Click in a field and drag it into the Field/Tab section on the
right side of the Field Access window. Drop it there. The reference to the field will be listed. This
only works for fields, not tabs.
Figure 120 Dragging and dropping fields from the Forms window
3. When a field/tab reference appears in the list, this means it is now protected and inaccessible until
you grant certain user groups the right to access it.
Figure 121 The Field Access window with Groupings and Fields/Tabs added
To define any conditions in regards to editing on a field/tab, create an expression. This allows you to
further control editing access to a field by basing the editing rights upon the value in the field or in other
fields in the same window: for example, to allow a user to modify a field on a purchase form if the form
is a requistion, but prevent editing that same field if the form is a purchase order. Users who already have
Execute access assigned to their group, will have edit access regardless of any expression defined on a
field.
115
1. Click the lookup button on the Edit if Expression is True column next to the selected field or
tab. A new dialog opens.
2. Define an expression. The functions and columns are listed in the bottom of the dialog, and the
buttons to the left allow you to create your expressions quickly and easily. Only columns in the
same window as the selected field will be listed. Click the Verify button to test the expression
to ensure it is acceptable. Click Ok to close the dialog.
When you have listed all the fields/tabs or groupings Save the window and open the Access Control
window to grant access to the protected fields:
1. Go to Tools > Configuration > Access Control > Groups. The Groups window opens.
2. Select a Group to set field level access for. Go to Options > Access Control.
3. Open the Fields tab and scroll down to the end, where you will now see the header User-- Defined
Field Access. Individual fields/tabs or groupings you have defined in the Field Access window
are listed here.
4. Two checkboxes appear next to each grouping: Execute and Read. Checking Execute to grant
edit access to the grouping automatically grants Read access as well. Checking Read allows the
user group read only access to the field grouping.
S When Read and Execute are checked, the users in that group will be able to see and edit the fields
in the grouping, according to their Group access rights. In other words, if they do not have edit
access on the window already, and you grant edit access on the protected field grouping, the
field(s) will still remain read-- only.
S When only Read is checked the users will be able to read, but not edit the given fields even if they
have Edit access rights in that window - unless an expression has been defined on the field,
allowing editing also.
S If you do not check Read (i.e. neither box is checked) the field will be completely hidden, even
if the group has Read or Edit access for the relevant window. In the case that a tab is defined as
unreadable, set the parameter Hide Inaccessible Menu Entries to True to hide the tab. Set it to
False to render the tab visible but disabled.
116
Chapter 15 System Parameters
Select Tools > Configuration > Parameters to open the Parameters window:
Figure 123 shows the System Administrator view. This view gives the user access to all areas of the system.
To understand the implications of this, it is necessary to first understand the issues of hierarchy and scope.
The AMOS Business Suite is a hierarchical view of an installation and the system has been programmed
to handle corporate entities as well as partnered organisations. The layers of this hierarchy correspond to
the physical and operational divisions within your actual organisation.
A company typically comprises one or more Installations. Whether these represent factories, office sites,
offshore platforms or ships, the defining factor is that they are often geographically separated entities
within the same organisation. Each is individually responsible for its own operations and technical
administration.
Each Installation is in turn made up of one or more departments. For example, a ship could be divided into
departments: Engine, Deck and Safety. A production plant might have Production and Transport
departments. Here the division typically represents groups at the same site who are separate cost centres
and therefore are responsible for their own maintenance expenses. They may require specific follow--up
or budgeting.
AMOS is designed to handle installation and departmental separation, and caters to each groups needs,
such as special component number schemes or division of stock information.
To meet these requirements, the configuration parameters have a scope within which they apply. This scope
can be:
S For a single department
S For all departments in a single installation
S For the entire organisation
In addition to providing scope, this hierarchy also provides for the inheritance of parameters. Therefore,
if the system does not find a particular parameter setting for the current department, it automatically looks
up the hierarchy to the installation directly over the department in the hierarchy. If no specific parameter
value has been set for the installation, then the system looks for and uses the value that has been set at the
global level.
It is simple to handle exceptions in the system, like a different component numbering scheme for a
particular department. The system administrator simply defines the numbering scheme at the global level
for the whole company, and then defines a specific one for the department in question.
117
15.1 The Parameters Interface
The Parameters interface contains the control room for The AMOS Business Suite and any changes made
here have deep consequences for the system operation. Take time to familiarise yourself thoroughly with
the logic behind and consequences of changes made in this section. The following sections provide a basic
idea of each of the parameters, but due to the complexity of the possible combination of results, it is not
practical to document every single parameter fully.
Note Some pre--set options do not show their apparent setting in the Value field. This is because the value field
shows a database field, as opposed to its intended function name.
15.2 Auto---Numbering
118
This set of parameters is divided into two types: Masks and Rules. Masks control how the system displays
certain fields, and which characters can be entered into these fields (e.g. input mask). Rules control the
format of the system--generated numbers.
In some cases, only a Mask may be defined, as with the definition of the appearance of component numbers.
Other numbers allow the definition of both a Mask and a Rule, as is the case of work order numbers the
rule controls how the system generates the number, and the mask controls how the number is presented.
In the Mask fields, the following characters control which characters are valid for each position in the
number:
S ! -- Any character -- any alphabetic characters are automatically uppercased by the system.
S ^ -- Any character -- any alphabetic characters are automatically lowercased by the system.
S A -- Any alphanumeric character.
S X -- Any character.
S # -- Any numeric character.
Any other character appearing in the mask is displayed in the input field as un--modifiable positions. These
separate sections of the number: for example, a typical Component Mask would be ###.##.##. This would
give potential Component numbers of 601.00.00, 712.47.01, etc. A typical Address Mask would be !!!###.
This would give potential Address Codes of ALF001, SUL002, etc.
The work order, purchase form and transport document numbers have both a mask and rule as they are
system generated numbers whose appearance can be controlled.
In the example above, the field Form Number Mask ends with two X--es to facilitate the entry of form
numbers that AMOS has split. For example, a purchase order may be split into two or more sub--forms,
and in that case, AMOS adds the character A to the form number. The two X--es in the Form Number Mask
allow the user to enter this modified number.
To start building a rule, click one of the Functions on the left. The lengths of the functions are pre--defined,
and cannot be changed: Year(2) is the two digit current year; Year(4) is the four digit current year; Month()
is the two digit current month; and Day() is the two digit current day. Several functions may be used in the
same rule. Once you have selected a function, it is displayed in the grey field in the upper part of the
window.
119
The Format field is for specifying whether the numbers should be preceded by zeros or not. The Month()
and Day() can have leading blanks, but leading zeroes is the preferred setting. The expression at the top
of the window shows 0 if Leading zeros is selected, and # if Leading blanks is used. If the wrong format
is shown for a function, click the function again to remove it from the expression, select the desired format,
and click the function once more to re--insert it in the expression.
The second half of the expression consists of values from the listed Columns. Columns get their values
from the current Installation, Department, and User, along with the values in the Number Series window.
The Length is the number of characters a column occupies. Specify a Length first and then click the Column
name. For example, Total[0,5] represents the Total column with a Length of 5 padded with leading zeros,
00001, 00002, etc.
The Component Type Number and Component Number Rules each have two additional Columns:
Component Class Code and Component Class Total. These allow you to specify numbering rules based
on the Component Class assigned to the data. The Stock Type/Item Number Rule has two additional
Columns also: Stock Class Code and Stock Class Total. This allows you to specify numbering rules based
on the Stock Class assigned to the data.
Once the rule is entered, click the Test button to see how the rule works.
The defined Rule is displayed according to the Mask defined for the field for which the Rule is being
created.
If the Rule does not produce the intended result, click the Clear Last button to remove the last part of the
expression under construction, or click the Clear All button to start fresh to rebuild it.
120
15.4 Directories
121
Transfer Directory
This directory defines the location where selection files and import files are found, and where generated
export files are placed.
Default setting: the Transfer sub--folder of the AMOS Business Suite Installation.
15.5 Options
This is the most general category of parameters, and contains a variety of switches and values varying from
file extensions for the Import/Export module to whether maintenance is to reported back at the employee
level or at the group (or discipline) level.
15.5.1 Accounting
Account Code Type for Maintenance
This parameter defines the type of Account Codes available for the Maintenance module lockup lists and
entry fields. If the parameter specifies only account code type Class of Cost, these will be the only type
of account codes available. For backward compatibility (new installation and upgrade), only the Class of
Cost option should be selected, and the Track Maintenance Transactions must be set to TRUE. You license
must include the accounting module of the AMOS Business Suite.
Default setting: 3 (Class of Cost)
Track Maintenance Transactions
This parameter, if set to TRUE, causes the application to track maintenance transactions. Your license must
include the accounting module of the AMOS Business Suite.
Default setting: TRUE
Track Purchase Transactions
This parameter, if set to TRUE, will cause the application to track purchase transactions. The current
license must include the accounting module of the AMOS Business Suite.
Default setting: TRUE
Track Stock Transactions
This parameter, if set to TRUE, will cause the application to track stock transactions. The current license
must include the accounting module of the AMOS Business Suite.
Default setting: TRUE
15.5.2 Budget
Allow User--Defined Impact on Purchase Budget
Setting this parameter to TRUE allows users to custom define which form status (Split, Cancelled, Parked,
etc.), affects which budget column (Committed, Paid or Forecast). A new field, Forecast, will appear in
the Budget windows and on Budget Reports.
Default Setting: FALSE
Budget at Line Item Level
This parameter has four possible values:
S Never -- no Budget at Line Item Level check box appears in the Forms window.
S Seldom -- there is an un--checked Budget at Line Item Level check box in the Forms window.
S Often -- there is a checked Budget at Line Item Level check box in the Forms window.
S Always -- there is no option in the Forms window since the option is always used.
Default setting: NEVER
Enforce Budget Approval
If this parameter is set to TRUE, in all lookup fields (excluding those in filters) where users can choose
a budget code, the list will contain only budget codes with status Approved.
Default setting: FALSE
122
Financial Year Early Start
Set this parameter to TRUE to allow for the early start of the financial year. Many US companies start their
financial year in October.
Default setting: FALSE
Interrupt Approval Warning Limit Adjustment, When Sub--Group Exists
The setting of this parameter indicates if the system should automatically update warning percentages on
sub--group levels that may belong to groups, when the percentages are updated at group level.
Default Setting: INTERRUPT
Month--End Close Period (Days)
Use this parameter to specify when monthly accounts are closed. For example, a value of 5 means that the
accounts are closed 5 days before the end of the month.
Default setting: 0
Start Date For Financial Year
Use this parameter to set the start of the financial year according to varying world--wide practices: e.g., the
UK starts its financial year on April 6th and France on January 1st. Once this date is set, it can be very
complicated to change.
Default Setting: 1998--01--01
Track Custom Clearance Expenses
This system switch controls the activation of the tracking of Custom Clearance expenses by the Budget
module. If you change the value from FALSE to TRUE, and any budget information already existed, you
will need to manually recalculate the budget figures.
Default setting: TRUE
Track Maintenance Expenses
This system switch controls the activation of the tracking of maintenance expenses by the Budget module.
If you change the value from FALSE to TRUE, and any budget information already existed, you will need
to manually recalculate the budget figures.
Default setting: TRUE
Track Purchase Expenses
When set to TRUE, this parameter activates the tracking of purchase expenses by the Budget module. If
tracking is turned on, the system checks that budget codes entered are valid. It automatically registers
financial transactions against the specified budget and signals the user if a budget is exceeded by a
pre--determined warning value. If you change the value from FALSE to TRUE, and any budget information
already existed, you will need to manually recalculate the budget figures.
Default setting: TRUE
Track Stock Expenses
Similar to the previous parameter, this system switch controls the activation of the tracking of
stock/inventory expenses by the Budget module. If you change the value from FALSE to TRUE, and any
budget information already existed, you will need to manually recalculate the budget figures.
Default setting: TRUE
Use Budget Control When Approving Forms
Setting this parameter to TRUE activates Budget Warning functionality.
Default Setting: FALSE
Use External Budget Figures for Budget Approval Warning Levels
Set to TRUE, for any or all installations, the system will verify Budget Warning percentages against an
external system rather than against AMOSs internal accumulated budget.
Default Setting: FALSE
123
Use Specification for Purchase Budget
This parameter allows you to specify whether to use Specifications to update budget figures for the
Purchase budget class.
Default setting: FALSE
Use Specification for Stock Budget
This parameter allows you to specify whether to use Specifications to update budget figures for the Stock
budget class.
Default setting: FALSE
Use Specifications for Maintenance Budget
This parameter allows you to specify whether to use Specifications to update budget figures for the
Maintenance budget class.
Default setting: FALSE
Use Voucher to Update Forms Details
This parameter lets you specify whether to use vouchers to update forms details.
Default setting: FALSE
15.5.3 General
Attachments -- Attachment File Stamp
When a file is attached to a record in AMOS, its date may require resetting. This parameter controls if the
date on attachments should be updated or not. When an attachment which is not stored in the database, is
added either by drag and drop onto an Attachments tab or by insertion in the Attachment References
window, AMOS will reference this parameter. Set to DATABASE TIME, AMOS uses the date and time
found on the database server to stamp the attachment. Set to LEAVE AS IS, AMOS will not update the date
and time on the attachment file.
Default setting: LEAVE AS IS
Attachments -- Attachments File Operation
Set this parameter to determine the systems action when a user tries to add an attachment which is not
already stored in the Graphics folder for that installation:
Set to WARN the user will be simply be warned that the attachment is not yet in the installations Graphics
folder and action will be prevented. Set to COPY, the attachment file will be copied automatically to the
Graphics folder without a user message. Set to MOVE, the file will be moved to the Graphics folder without
a message to the user. Set to ASK, the user can decide whether to Leave the file where it is, Copy it to the
Graphics folder, or Move it there.
Default setting: ASK
Attachments -- Attachments Maximum Size
Use this parameter to set the maximum size (kb) for any attachment used within the system.
Default setting: None
Attachments -- Attachments Oversize Action
When set to WARN, if a user tries to add an attachment which exceeds the size allowed by the parameter
Attachments Maximum Size, the user will receive a warning message indicating that the attachment
exceeds the maximum and allowing them to choose to proceed, or not. If this parameter is set to PREVENT,
and the user tries to add an oversize attachment, they will be stopped from adding the attachment.
Default setting: PREVENT
Attachments -- Attachments Store in Database
When a user adds an attachment, the setting of this parameter determines if the file should ALWAYS be
stored in the database, or NEVER. Or, if set to ASK, the user will be presented with a message upon adding
an attachment.
Default setting: NEVER
124
Dashboard -- Alerts Maximum Size
Setting this parameter determines the length of the longest bar(s) in the dashboard Alerts Overview. The
length of the bars can be based on the alert with the highest value amongst all the alerts, or the alert with
the highest value within the same alerts group.
Default setting: AMONG ALL ALERTS
Dashboard -- Use Separate Retrieval Thread
If set to TRUE, this parameter allows the system to perform the dashboard alerts calculation and data
retrieval in a separate thread. This enables the user to continue to work without being interrupted by
dashboard operations. In this case indicators on the dashboard will inform the user which alert is currently
being processed and the user is free to work in other parts of AMOS. Set to FALSE, the same work thread
within the application is used for these dashboard operations.
Default setting: FALSE
Database Compatible To Version
This parameter ensures column width compatibility through various versions of AMOS and should be set
to the same version number that the installation is using. The default options here vary depending on the
software version number.
Note It is important that all your installations of AMOS are of a compatible version to ensure that there are no
replication errors due to different column widths.
Database -- DB Error Text Marker
Use this parameter to enter in the text which should appear at the start and end of customised error
messages. Use the tab key to indicate the separation between title text and body text.
Default Settings Budget Code Status
This parameter controls the initial setting for a new budget in general. The default setting is 2. The figures
correspond to the following:
1 Parked
2 Preliminary
3 Approved
Default Settings Budget for Component Job
This parameter determines the search order when checking for a component jobs default budget code. The
default setting is Maintenance Type, Component which means that the default budget code is taken from
the maintenance type if one exists. Otherwise the budget code for the component is used. This parameter
has two states, the one described above and the reverse search order of Component, Maintenance Type.
This only applies if the Accounting module is not being used.
Default Settings Default Status On Component Transfer
This parameter controls the default value for components when transferred from one department to another
department. The status is applied at the time of transfer and is visible as the component status in the
receiving department.
Default setting: Available
Default Settings -- Default Value Mark Work as Completed
This parameter controls the Mark Work Order as Completed checkbox in the Report Work window. Setting
the parameter to FALSE unchecks the box.
Default setting: TRUE
Default Settings Default value Quotation Update Stock Item Field
This parameter controls the default state for the checkbox entitled Update Stock Items found in the
quotations window. If this parameter is set to TRUE, the checkbox will be checked by default.
Default setting: False
Default Settings Depreciation Level
When the Depreciation feature is activated, this setting controls the initial status of Stock Items. The default
setting is 1, which corresponds to level 1, which is normally new, or 0% depreciation. Up to 5 levels of
depreciation can be set.
125
Default Settings Form Type
A Purchasing module parameter, this value controls which type of form to create (i.e. requisition form,
query or purchase order) during automatic form creation. In a shipping scenario, it is normally the case that
vessels create requisition forms while shore side offices create purchase orders.
Default setting: PURCHASE ORDER
Default Settings Initial CBM Work Order Status
When the CBM (Condition Based Maintenance) module is active, this setting controls the Initial Status
of Work Orders. The available options are Requested, Planned and Issued.
Default setting: ISSUED
Default Settings Initial Corrective Action Work Order Status
This setting controls the Initial Status of Corrective Action Work Orders. The available options are
Requested, Planned and Issued.
Default setting: ISSUED
Default Settings Initial Periodic Work Order Status
This is for setting the initial status of automatically created periodic work orders.
Default setting: ISSUED
Default Settings -- Initial Project Work Order Status
This is for setting the initial status of Project work orders.
Default setting: ISSUED
Default Settings Initial Requisition Work Order Status
This is for setting the initial status of manually created work orders.
Default setting: ISSUED
Default Settings Initial Round Work Order Status
This is for setting the initial status of automatically generated round work orders.
Default setting: ISSUED
Default Settings Location for Stock Items
This is for defining and using multiple stock item locations. If several locations are defined in the Locations
hierarchy, one can be defined as the default location, automatically attached to each newly created stock
item.
Default setting: Empty
Default Settings Maintenance Cost Account Category
Set the Default Maintenance Cost Account Category using the following dialog:
Figure 128 The Set Default Maintenance Cost Account Category Dialog Box
Click the lookup button to select the correct category from the list provided. When a new component job
is created, an account of the chosen category is applied by default. This will only apply if the Accounting
module is being used.
Default setting: Empty
Default Settings Output Format for new Job Related to Components
One of three output formats may be selected in AMOS: List, Compact List and Detailed. List gives only
one line per selected job. Compact list gives a few lines containing the most important information.
Detailed contains the full job description.
Default setting: COMPACT
126
Default Settings Output Format for new Rounds
One of three output formats may be selected in AMOS: List, Compact List and Detailed. List gives only
one line per selected job, Compact list gives a few lines containing the most important information, while
Detailed contains the full job description.
Default setting: COMPACT
Default Settings Output Format for Work Requisitions
One of three output formats may be selected in AMOS: List, Compact List and Detailed. List gives only
one line per selected job, Compact list gives a few lines containing the most important information, while
Detailed contains the full job description.
Default setting: DETAIL
Default Settings Priority for new Job Related to Components
A job can be given a numerical priority of up to three digits; 1 being the highest priority and 999 being the
lowest. Your organisation decides which priorities to assign.
Default setting: 5
Default Settings Priority for new Rounds
A round can be given a priority of up to three digits; 1 being the highest priority and 999 being the lowest.
Your organisation decides which priorities to assign.
Default setting: 5
Default Settings Priority for Work Requisitions
A round can be given a priority of up to three digits; 1 being the highest priority and 999 being the lowest.
Your organisation decides which priorities to assign.
Default setting: 4
Default Settings Status for New Components
This field is used to set the status of new components introduced in the system. The possible options are:
(None), In Use, Available, Repair, Scrapped and Transferred.
Default setting: 3 (Available)
Editor
The following parameters concern the text editors used in AMOS.
Editor -- Additional Detail Data on Unit Level
This parameter works in conjunction with the parameter Editor -- Use Additional Note Field. They
determine the presence or absence of additional Details tabs in the Stock Type/Stock Item/Component
Type/Component windows, when any of those windows has an enhanced template in use:
S If both parameters are set to FALSE, only one Details tab will appear in the Component
Types/Components/Stock Types/Stock Item windows.
S When this parameter is set FALSE but the second is set to TRUE, two Details tabs will appear in
any of these windows which contains an enhanced template.
S When this parameter is set TRUE but the second is set to FALSE, only one Details tab will appear
in the Component Type/Stock Type windows, and two Details tabs (one linked to Type and one to
Item) will appear in the Components/Stock Item windows.
S If both parameters are set to TRUE, two Details tabs will appear in the Stock Types/Component
Types windows when an enhanced template is present. Four Details tabs (two linked to Type and
two linked to Item) will appear in the Components/Stock Items windows when an enhanced
template is present.
Default setting for both: FALSE
Editor -- Classic Editor Font
This parameter controls the display font for all the details forms created using the Classic Editor. It is also
reflected in printouts of these screens. Click the lookup button to access the font selection window. Choose
the type, style and size of the font you require and click OK to select.
127
Fonts can be implemented at a Global, Installation or Departmental level.
Default setting: Empty (system displays Arial)
Editor -- Max Size (kB)
This parameter is for controlling the maximum file size of details forms to avoid excessive data
retrieval/replication times.
The size can be any amount between 0 and 1000, where the number equals the maximum file size in
kilobytes for each details form in the system. If 0 is selected there is no limit on the file size.
Use care when applying this limit because it will be applied to each detail form instance. This means that
if you set the limit to 1,000 kilobytes (1 megabyte) and the limit is almost reached on 1000 detail forms,
the amount of data to be replicated will be 1,000,000 kilobytes (1 gigabyte).
Note Due to file conversion limitations, the maximum bitmap image file size is slightly less than half of the
designated amount in this parameter. If the parameter is set to 1000, the maximum bitmap size is 499
kilobytes. Other image formats may be inserted, but any image compression will be removed upon
insertion and that the maximum size may be reached unexpectedly.
Default setting: 0 (unlimited)
Note Due to a feature in the Enhanced Editor functionality, if an image is to be added to the page the user MUST
also include a minimum of one text character or space. If an image is added to an otherwise empty editor
page, it will disappear when an attempt is made to save the change.
Editor -- Type Common
This parameter determines the type of text editor used in Details windows within the common functionality
areas of AMOS, for example the Registers. See section 2.3.8 for further information on the Details forms.
Default setting: CLASSIC
Editor -- Type Custom Clearance
This parameter determines the type of text editor used in Details windows within the Custom Clearance
areas of AMOS. See section 2.3.8 for further information on the Details forms.
Default setting: CLASSIC
Editor -- Type Maintenance
This parameter determines the type of text editor used in Details windows within the Maintenance and
Stock related areas of AMOS. See section 2.3.8 for further information on the Details forms.
Default setting: CLASSIC
Editor -- Type Personnel
This parameter determines the type of text editor used in Details windows within the Personnel areas of
AMOS. See section 2.3.8 for further information on the Details forms.
Default setting: CLASSIC
Editor -- Type Purchase
This parameter determines the type of text editor used in Details windows within the Purchase and Budget
areas of AMOS. See section 2.3.8 for further information on the Details forms.
Default setting: CLASSIC
Editor -- Type Quality
This parameter determines the type of text editor used in Details windows within the Quality & Safety areas
of AMOS. See section 2.3.8 for further information on the Details forms.
Default setting: CLASSIC
Editor -- Type TMSA
This parameter determines the type of text editor used in Details windows within the Self Assessment areas
of AMOS. See section 2.3.8 for further information on the Details forms.
Default setting: CLASSIC
128
Editor -- Type Voyage
This parameter determines the type of text editor used in Details windows within the Voyage Management
areas of AMOS. See section 2.3.8 for further information on the Details forms.
Editor -- Use Additional Note Field
See Editor -- Additional Detail Data on Unit Level, above.
File Extensions
These parameters allow you to set the file extensions used in AMOS.
The default settings are as follows:
EXP -- Export Files, Import Files
HTD -- Hand Terminal Files
OK -- Successfully Imported Files
File Extensions -- Export Import Temp Character
This parameter allows the user to set the characters to be used for split files created during import.
File Extensions -- File Extension for Export Files
The system maintains a sequence number for both import and export operations. Since these sequence
numbers are used to name the files created by these operations, it is important to be able to differentiate
between files created by export and ready for transfer to another site and those received which are ready
to be imported. This is done by defining different file extensions for the various files handled by the
Import/Export module.
This parameter defines the extension for export files generated by the system.
Default setting: EXP
File Extensions -- File Extension for Hand Terminal Files
A hand terminal may be used to record stock transactions. The data from the hand terminal may be exported
in the form of a file, which may then be imported into AMOS stock levels. This parameter specifies the
file extension for such hand terminal files.
Default setting: HTD
File Extensions -- File Extension for Import Files
As a complementary parameter to the parameter File Extension for Export Files, this value defines which
extension identifies files ready to be imported by the system.
Default setting: EXP
File Extensions -- File Extension for successfully Imported Files
As a complementary parameter to the previous one, this value defines which extension is to be given to
import files that have been successfully imported by the system.
Default setting: OK
Portal
The following set of parameters controls the behaviour of AMOS e--Business Direct functionality.
Portal -- Billing Address
The Billing Address parameter is where the code for the address where purchase invoices should be sent
is maintained. When you enter the Billing Address filter you will be presented with the Addresses window
from which you can chose the correct address. The chosen address will be shown as an eight digit code.
Default value: Empty
Portal -- Log Successful Portal Operations
Set to TRUE, the system will store successful portal operations in the Portal Log.
Default Setting: FALSE
Portal -- Portal Line Item Reference Priority
If the value for this parameter is set to VendorRef, MakersRef the system writes the Vendor Reference value
into the XML file if both values are available. If only one of the two is available, that value is written into
the XML file. If this parameter is set to MakersRef, VendorRef the Makers Reference is written to the XML
file as the Identification value.
Default setting: MakersRef, VendorRef
129
Portal -- Prevent Update of Quotation When One is Selected
If set to TRUE, the system will not be able to import quotations which have been selected -- that is, which
have a vendor selected. If set to TRUE and no vendor is selected, the quotation will be imported. Set to
FALSE, the quotations will be available for import whether a vendor is selected or not.
Default setting: FALSE
Portal -- Show Error Messages During Portal Export
This parameter, if set to FALSE, allows Portal Export to continue uninterrupted in the event of errors
occurring during export. Any errors encountered are written to the portal log and can be viewed later. If
the parameter is set to TRUE you will receive an error message each time an export error occurs and further
data export will be stopped until the error message is cleared by the user.
Default setting: TRUE
Portal -- Show Error Messages During Portal Import
This parameter, if set to FALSE, allows Portal Import to continue uninterrupted in the event of errors
occurring during import. Any errors encountered are written to the portal log and can be viewed later. If
the parameter is set to TRUE you will receive an error message each time an import error occurs and further
data import will be stopped until the error message is cleared by the user.
Default setting: TRUE
Portal -- Store Imported XML Document in Portal Log
This parameter, when set to TRUE, allows you to see the imported XML document associated with the
selected error message in the Portal Log, accessed via the Options menu. If set to FALSE, there will be no
Options menu available and no XML documents will be stored.
Default setting: FALSE
Remote Workflow
These parameters control Remote Workflow system--wide. When these are set correctly, Remote
Workflow is enabled and can be switched on or off at user level.
Remote Workflow -- HTML Type
AMOS can produce two types of HTML files. The setting of this parameter determines which type AMOS
will produce. Setting this parameter to HTML/XML produces an HTML file containing an XML data
island. This requires JavaScript to be enabled within the browser and is only supported by Microsoft
Internet Explorer. This has always been supported by the AMOS Remote Workflow.
Setting this parameter to HTML/JSON produces an HTML file containing a JSON data island. This
requires JavaScript to be enabled within the browser and is supported by most major web browsers,
including Microsoft Internet Explorer. If you select HTML/JSON, you must define a JSON library.
Remote Workflow -- JSON Library
Processing JSON data requires a JSON library. Several JSON libraries are available on the internet. Use
this parameter to make the selected library available for the HTML file, either by referencing a URL or
by including the library directly into the HTML file itself. This parameter lets AMOS know how the
selected library should be linked to the HTML file. There are three values available:
-- INTERNAL -- uses the java script code found internally within AMOS, and inserts it into the
HTML file. This increases the size of the HTML file.
-- URL -- links the URL you provide here, into the HTML file; this will not considerably increase the
size of the HTML file.
-- FILE -- takes the java script code contained in the selected library file, and inserts it into the HTML
file. This increases the size of the HTML file produced according to the size of the selected file. You
indicate the location of the library file here. Keep in mind that AMOS does not verify the content
of the file -- it is inserted as it is.
Remote Workflow -- Mail Account Password
To perform workflow operations by email, the system needs to access an email account for sending and
receiving those mails. This parameter is for setting the password for the user mail account.
Remote Workflow -- Mail Account User
Use this parameter to set a mail account user, known to your mail server, which can receive the outgoing
mails from the system.
130
Remote Workflow -- Purchase Template
Set a purchase template, containing your company format. This will be presented to the user in the HTML
attachment and will look similar to the normal Workflow transformation dialog.
Remote Workflow -- Return Mail Address
Use this parameter to set the mail address for the system, which will receive the workflow data from the
remote user.
Remote Workflow -- Send Mail
This must be set to TRUE. FALSE can only be used in the setup process (to avoid sending the mail), for
debugging purposes.
Remote Workflow -- Use Remote Workflow
Set this parameter to TRUE to allow use of remote workflow in your system. Set to TRUE, users will have
the option to turn remote workflow on, in the Options window.
Report -- Default Report Filter Button
This parameter is to determine which button on the Report filter should be the default when executing a
report: OK or Print Preview.
Default setting: OK
Report -- Logo Bitmap used in Report Printout
If you want to include your company logo on printed reports you should use this parameter to navigate to
the file you want to use. The supported file types are:
.bmp .gif .jpg .jpeg .rle .wmf
Default setting: Empty
Search -- Indicator
Use this parameter to set whether Sound searching should be available or if the filters should only return
information as entered.
Search -- Sensitivity
Set a scale for sound searching sensitivity using this parameter. Higher sensitivity indicates that the filter
results must be returned as close to the sound as possible. Lower sensitivity means that more results (less
closely matched) can be returned.
Default setting: 10
System Access -- Account Lockout Threshold
This parameter determines the number of unsuccessful log--in attempts a user can make before being
locked out of the application. If the parameter is set to zero the lockout system will be disabled. A positive
number above zero should be entered if you want to use this feature. If you are using this feature you will
be informed of the number of any unsuccessful log--on attempts that have been made against your user
name once you log--on successfully.
Default setting: 0
System Access -- Create Log--In Audit Trail
This parameter, when set to TRUE, creates a log--in audit trail allowing you to track system usage. Use the
menu item Tools > View Log--In Audit Log to access the recorded details. There is an access control item
entitled Login Audit in the Registers tab which should be used to allow viewing of the audit trail. The log--in
audit log is always read--only, even if Edit, Insert and Delete access rights have been granted.
Default setting: TRUE
System Access -- Disable Account Period
Setting a number here indicates the number of days of inactivity on a user account (from the last logon)
that can go by before the account is disabled. If a user exceeds the number of days at their logon attempt,
their account will be disabled and they will receive a message. Set to 0, this parameter is ignored.
Default Setting: 0
System Access -- Enforce Complex Password
This parameter determines whether complex passwords must be used or not. If this parameter is set to true,
all passwords must contain at least 1 of the following:
-- Upper Case Character
-- Lower Case Character
131
-- Alphabetic Character
-- Non--Alphabetic Character
So, for example, an acceptable password could be Ab1.
When setting this parameter to TRUE for the first time, all users must be aware of the fact that passwords
have been previously stored in upper case only. In order to change their password at their next log--in they
will have to enter their old password in upper--case in order to continue.
Note Changing this parameter to TRUE is irreversible.
System Access -- Enforce Password History
This parameter controls how many previously used passwords for each user are retained in the system.
When you are prompted to change your password, controlled by the Maximum Password Age parameter,
you must enter a password that does not match one of the previously used passwords stored in the database.
This also applies to the manual Change Password feature covered in section NO TAG. Setting this
parameter to zero will disable this feature.
Default setting: 0
System Access -- Idle Timeout
This parameter allows you to set the amount of time, in minutes, for which AMOS can be idle before it
locks. Once this amount of time has passed, the windows will remain open but the logon dialog will appear
and the current users password must be supplied before access is allowed again. This parameter is disabled
when set to 0. If enabled, the item Lock Application will also appear on the File menu and can be manually
selected at any time.
Default setting: 0
System Access -- Maximum Password Age
This parameter determines the maximum allowed age, in number of days, of all passwords. This feature
is disabled if the value is set to zero.
Default setting: 0
System Access -- Minimum Password Length
This parameter determines the minimum allowed length, in number of characters, of all passwords. This
feature cannot be disabled as the minimum length must be at least 1.
Default setting: 1
System Access -- Password Backward Compatibility
There are two types of password decryptions. If you are running a database version in the office that is
newer than the one on a ship, you cannot use the new functionality. This parameter must be set to FALSE
when either installation does not support the new decryption method.
Default setting: FALSE
Allow Work Flow On Locked Objects
If this parameter is set to TRUE, it allows the user to perform Work Flow actions on objects which are
locked through the Work Flow definition.
Default Setting: FALSE
Ask User to Confirm Deletions
When this parameter is set to TRUE, the user is asked to confirm the deletion of a record. If set to FALSE,
no question is asked, and the record will be deleted when Save is selected.
Default setting: TRUE
Base Currency Code
AMOS Business Suite makes it possible define a base currency at the global, installation and department
level. At the global level, this value determines the base against which Current Rates are recorded. In
addition, it is also possible to define the default currency to be used when recording transactions and
presenting reports for the various installations and departments
Default setting: USD
Note If sites are to exchange information from the currency rates table then it is necessary for them to have the
same global base currency defined.
132
Create Component Archive On Transfer In
This parameter when TRUE allows the creation of Archive tables in receiving installations in order for the
recipients to view component information created in previous installations. Options are TRUE or FALSE.
Default setting: TRUE
Note This parameter should be set to the same value as the Delete Component Archive On Transfer Out
parameter.
Current Installation
This is one of the most important parameters in the system because it uniquely identifies the current
installation with a number. This number must not be changed after initial definition.
Default setting: 001
Delete Component Archive On Transfer Out
This parameter when TRUE allows the deletion of Archive tables in donating installations when the
component is transferred out. Options are TRUE or FALSE.
Default setting: TRUE
Note This parameter should be set to the same value as the Create Component Archive On Transfer In parameter.
Edit Stock Item Currency and Price on Required Parts
This parameter controls the Currency and Price columns in the Required Parts tab of the Work Orders
window. When set to TRUE, the information in these columns is editable.
Default Setting: FALSE
Enforce Rate Upon Currency Code Registration
If set to TRUE, the Currency Code register will contain fields to set the Rate and Valid From dates for new
currency code records.
Default setting: FALSE
Export File Encoding
Use this parameter to inform the system whether it should use ANSI or Unicode, in order to assign a unique
value to all characters.
Default setting: ANSI
Hand Terminal Reader
This option may be used to specify the interface program that is used to transfer data from a hand terminal
to AMOS.
Default setting: Empty.
Hide Inaccessible Menu Entries
This parameter prevents menu items that are not available to a user, due to his belonging to a group that
does not have access to this function, from displaying. If this parameter is left as FALSE, unavailable menu
items will continue to appear greyed out. If set to TRUE, any menu items that belong to modules that are
not covered by the current license will also be hidden.
Default setting: FALSE
ID Number Series
All database entries in the system are stamped with unique internal numbers. These numbers are built up
of two parts, the ID number and a running counter. The ID number ensures that no two sites can generate
the same internal number. The Current Installation parameter is often used to define the ID part of the
internal numbers, but this is not mandatory. Once an ID number has been defined and data is entered into
the database, no other installation can ever be assigned the same ID number as this would lead to duplicate
internal numbers.
Default setting: 001
Limit Global Search to Departmental Access
This parameter controls whether records belonging to a particular department are displayed as a result of
a Global Search. When set to TRUE, only the results belonging to departments to which the user has access
will be displayed.
Default Setting: FALSE
133
Limit Stock Types selection on Required Parts on Work Orders
This parameter defines which Stock Types are displayed in the list for adding them to the Required Parts
tab of a Work Order. Setting this parameter to TRUE limits the Stock Types to types of which are registered
against the department owning the Work Order. Set to FALSE, all Stock Types in the Select list are
displayed.
Default setting: FALSE
Mailbox Notification Sent
The Work Flow Notification window is updated as new records are assigned to a mailbox. However, if a
mailbox is shared or delegated, this parameter must be set to ALWAYS in order for all users who have
access to the mailbox, to see the notifications.
Default setting: ALWAYS
Open Attachments In New Window
This parameter determines how a new image is displayed when an image hotspot is clicked. If the value
is set to FALSE, a new image will be opened in the currently open window, and replace the image which
is there. When the value is set to TRUE, a new image will be opened in a separate window.
Default setting: FALSE.
Printer Task to Use When Printing Labels
This parameter is used to select a Printer Task to use when printing labels from the Stock Items window.
Default setting: Empty.
Reload DDDW When Opened
DDDW stands for Drop--Down Data Window, the drop--down lists of currency codes, disciplines units job
classes etc. present in the system. The contents of these drop--down lists in a window or dialog box are built
when the window or dialog opens up, and are not rebuilt unless the window is closed and reopened. As a
result, newly added items to the drop--down tables do not appear in a list until the window containing this
list is closed and reopened.
Set this parameter to TRUE, and the system re--builds drop--down lists each time the list itself is opened
by clicking on the drop--down arrow. Please note that this will slow down display of the list, but guarantee
that the list is at all times complete.
Default setting: FALSE
Restrict Work Flow Assign To Values
This parameter, when set to TRUE, will restrict the available users in the Assign To drop down list to those
that have Work Flow access defined for the resulting status. The list will contain all users that belong to
groups with defined access.
Default setting: FALSE
Single Window Instance
This parameter controls whether or not you can have the same data window open several times. If set to
true, a data window such as Components or Work Orders will only be allowed to open once. Any attempts
to open the same window again will not work. If you want to view different information within the same
window you can use the filter command to do so.
Default setting: FALSE
Start In Department
This parameter allows you to control which department the system logs automatically into when you start
the system. When setting this parameter, you can select from a list of the defined departments.
Default setting: 001/01
Use 9 Digits For PK Counters
As of version 6.0.00, AMOS M&P (and now AMOS Business Suite) has the ability to use 9 digits for
Primary Key counters as opposed to 6 digits. This parameter should be set to FALSE until all installations
have been upgraded to version 6.0.00 or higher. When this has been accomplished, the parameter can be
set to TRUE. The purpose of using the extra 3 digits is to avoid exhausting certain primary keys that may
have high usage. New users of AMOS M&P 6.0.00 and above or AMOS Business Suite should set this
parameter to TRUE.
Default setting: FALSE
134
Use Component Types
This parameter may be set to TRUE when the Component Types function is used in an organisation. This
functionality makes it possible to define types of components at the head office. All components used at
the various sites may then be assigned to the correct component type and data about the component type
is automatically inherited.
Default setting: FALSE
Use Stock Types
This parameter may be set to TRUE when the Stock Types function is used in an organisation. This
functionality makes it possible to define types of stock at the head office. All stock used at the various sites
may then be assigned to the correct stock type, and data about the stock type is automatically inherited.
Default setting: FALSE
Working Day Length
This parameter determines the amount of calculated work hours per day and can be set to any whole number
between 1 and 24. Changes made to this parameter will be reflected in the timeline display for work
planning.
Default setting: 24
15.5.4 Maintenance
Auto--File Completed CBM Work Order
If this value is set to TRUE, CBM work orders are filed automatically when the status is set to Completed.
If the value is set to FALSE, it is necessary to manually file such work orders.
Default setting: TRUE
Auto--File Completed Corrective Action Work Order
If this value is set to TRUE, automatically generated corrective action work orders are filed automatically
when the status is set to Completed. If the value is set to FALSE, it is necessary to manually file such work
orders.
Default setting: TRUE
Auto--File Completed Periodic Work Order
If this value is set to TRUE, automatically generated periodic work orders are filed automatically when
the status is set to Completed. If the value is set to FALSE, it is necessary to manually file such work orders.
Default setting: TRUE
Auto--File Completed Requisition Work Order
If this value is set to TRUE, manually requisitioned work orders are filed automatically when the status
is set to Completed. If the value is set to FALSE, it is necessary to manually file such work orders.
Default setting: TRUE
Auto--File Completed Round Work Order
If this value is set to TRUE, automatically generated work orders are filed automatically when the status
is set to Completed. If the value is set to FALSE, it is necessary to manually file such work orders.
Default setting: TRUE
Auto--File Controlled CBM Work Order
If this value is set to TRUE, CBM work orders are filed automatically when the status is set to Controlled.
If the value is set to FALSE, it is necessary to manually file such work orders.
Default setting: TRUE
Auto--File Controlled Corrective Action Work Order
If this value is set to TRUE, automatically generated corrective action work orders are filed automatically
when the status is set to Controlled. If the value is set to FALSE, it is necessary to manually file such work
orders.
Default setting: TRUE
135
Auto--File Controlled Periodic Work Order
If this value is set to TRUE, automatically generated periodic work orders are filed automatically when
the status is set to Controlled. If the value is set to FALSE, it is necessary to manually file such work orders.
Default setting: TRUE
Auto--File Controlled Requisition Work Order
If this value is set to TRUE, manually requisitioned work orders are filed automatically when the status
is set to Controlled. If the value is set to FALSE, it is necessary to manually file such work orders.
Default setting: TRUE
Auto--File Controlled Round Work Order
If this value is set to TRUE, automatically generated work orders are filed automatically when the status
is set to Controlled. If the value is set to FALSE, it is necessary to manually file such work orders.
Default setting: TRUE
Allow Negative Value Of Counters
This parameter, when set to TRUE, will allow a user to enter a lower counter value than the one previously
recorded. This facility can be used to correct values when counters are changed or if an error has been made
during the reading or inputting of the previous value. Note that this may affect certain counter based
maintenance procedures. If the parameter is set to FALSE a user will be prevented from entering a lower
value and an error message will appear, when updating in the Update dialog opened from the Component
> Counters tab or in the Counters > Update window. However, even when set to FALSE negative values
will be accepted with a warning when registered directly in the Components window > Counters tab.
Therefore, you can use field access controls to restrict the end users who can perform updates in the
Components window Counters tab.
Default setting: TRUE
Auto Inherit Counters
If this parameter is set to TRUE, components installed in sub--functions will automatically inherit counter
updates from the component installed in the respective parent function.
Note For each sub--function component that is to inherit the counter updates, the user must go to the components
Counter tab and set the Depends On value to the correct parent function component.
When the Auto Inherit Counters parameter is set to TRUE and a component is removed from its
sub--function, the Depends On value is removed automatically from that components Counters tab.
Default setting: FALSE
AutoFilter WO By Discipline
When set to TRUE, the list of work orders is automatically restricted to the discipline that the user who
is currently logged on belongs to.
Default setting: FALSE
Automatically Reschedule Work Orders
This parameter is useful during the process of establishing the AMOS database in the organisation. By
setting the value to FALSE, the program will not automatically generate work orders as components,
counters and jobs are defined. This makes the process of entering such information more efficient. When
this is completed, the parameter value is changed to TRUE, and you select Maintenance > Generate
Work Orders to kick--start the generating of work orders. When set to TRUE, work orders are generated
for component jobs whose component status has been changed (if a work order is needed according to the
component job settings).
Default value: TRUE
Calculate Estimates for Component Jobs
This parameter may be set to Average or to Never. If set to Average, the program automatically updates
the component job estimates. The values for Total Duration and Total Cost are estimated based on the
duration and the cost of required parts and/or resources that have been reported
Default setting: NEVER
136
Default Preference When Reporting Work
This parameter determines which default value is checked in the Report Work dialog box which appears
when you select Maintenance > Report Work. The possible values are Component, Function and Work
Order.
Default setting: COMPONENT
Function, Only Show Active Jobs
This parameter when set to TRUE, causes only active jobs to appear in the Functions Hierarchy window
Jobs tab. Any inactive jobs will be hidden.
Default setting: FALSE
Hierarchy, Show Numbers
Set to TRUE, the function/component numbers will show in the hierarchy windows folder structure by
default. Set to FALSE the numbers will not appear in the hierarchy until the user selects Options > Toggle
Numbers.
Default: FALSE
Job Description Revision Control
This parameter controls revisions of maintenance job descriptions. Setting it to TRUE enables multiple
versions of maintenance--type job descriptions to be stored in the Job Description table. There can only be
one current active and one draft version of any job description. The job descriptions available when
creating new records in component job, component type and requisition work are always of the status
Active.
Default Setting: FALSE
Limit Selection of Required Parts to Stock Items Only
When this parameter is set to TRUE, and Stock Types are in use, when a user adds Required Parts to a Work
Order, Component Job or Work Report only Stock Types for which Stock Items are registered in the current
department will be available for selection. Set to FALSE, all Stock Types will be available regardless of
whether items have been registered against them.
Default Setting: FALSE
Log Counters For Non--Counter Based Jobs
If this parameter is set to MANDATORY, reporting work against non--counter based jobs will require a
mandatory counter value to be entered, providing that the component has a counter association. If set to
OPTIONAL, job counters will remain mandatory while component counters will be optional.
Default setting: NEVER
Log Job Rescheduling
This parameter, when set to TRUE, enables the rescheduling log. Every time a work order is rescheduled
the reschedule log will be updated with information regarding the rescheduling. If the parameter is set to
FALSE there will be no recording of rescheduling information in the log.
Default setting: FALSE
Log Work With Employee
This switch makes it possible to select the level at which to record work carried out. This may be either
at the employee level, where reported work is attributed to a specific worker. In some organisations, it may
be more suitable to register maintenance done per discipline (e.g. mechanic, electrician, etc.) instead. If
this parameter is set to FALSE, reporting will be done using Disciplines instead of on an individual
employee basis.
Default setting: TRUE
Maintenance Log Modification Warning
This parameter, when set to TRUE, ensures that accidental modifications to the maintenance log cannot
be made. If the user tries to alter information in the maintenance log a warning message alerting the user
will appear. If set to FALSE the user can modify information without warning.
Default setting: FALSE
137
Reason on Component Job Change
This parameter, when set to TRUE will cause a dialog to appear on saving changes in the Component Jobs
window. When users have changed a jobs Required Disciplines, Periodic Frequency or Period, they will
not be able to save the changes until they provide a reason in the dialog.
Default setting: FALSE
Report History by default
This parameter controls whether the Report History option when reporting maintenance is switched on or
off by default.
Default setting: TRUE
Report Resources by default
This parameter controls whether the Report Resources Used option when reporting maintenance is
switched on or off by default.
Default setting: TRUE
Report Stock Usage by default
This parameter controls whether the Report Stock Used option when reporting maintenance is switched
on or off by default.
Default setting: TRUE
Report Work, Require Reason for Overdue Work
If this parameter is set to TRUE and the Date Done for reported work is later than the Due Date on the Work
Order, the Overdue dialog opens and the user must enter a reason for the late work.
Default setting: False
Report Work, Show Component parts
When this parameter is set to TRUE then the Stock Used tab of the Report Work window lists the required
parts for a work order and any items reported in the Spare Part Log as well as any parts linked to the
component on the work order.
Set to FALSE, the Report work window in the Stock Used tab lists only the required parts and any items
in the Spare Part Log.
Default setting: FALSE
Require Reason For Job Rescheduling
This parameter, when set to TRUE, forces the user to input a reason for job rescheduling. If set to FALSE
there is no requirement to enter a reason. Note that this parameter is ineffective if the parameter Log Job
Rescheduling is set to FALSE.
Default setting: FALSE
Restrict Replanning Of Started Work Orders
If set to TRUE, it is not possible to re--plan (to move) a work order in the work planning timeline once the
Started date has been set. This occurs the first time a user reports maintenance work against the work order.
Default setting: FALSE
Seconds Between each CBM Check
This parameter allows you to control the frequency at which the system checks for CBM activity.
Default setting: 180
Stock reservation trigger
This parameter controls whether stock items required for work orders are shown as reserved whilst the
work order continues to be active (Status), or whether the stock items are reserved only during the window
time period prior to the due completion date of the work order (StatusWindow).
Default setting: StatusWindow
Use Job Dependencies
If this parameter is set to TRUE, you can configure links between two or more component jobs inside the
Jobs window (accessed from the Components window). These links can also be configured in the Job
Planning window graphical timeline.
Default setting: FALSE
138
Use Maintenance Task
If Maintenance Tasks is part of your licence and this parameter is set to TRUE, the user can view
outstanding stock quantities on forms for Maintenance Tasks in the Stock Wanted window in a field called
Outstanding Tasks.
Default setting: FALSE
Use Work Flow
If this parameter is set to true, the Maintenance > Work Orders > Options drop down window alters to
include the Workflow function. The Workflow function allows users to pre--define and automate the
process sequence of work orders.
Default setting: FALSE
View Counter From Functions Perspective
This parameter controls whether the Update Counters facility is filtered and viewed from a functions
perspective rather than a component perspective.
Default setting: FALSE
Work Order Tracking Accuracy
This parameter controls the level to which Work Orders are tracked. The two possible parameters are Date
Only and Date/Time. Date Only lets you plan work by date whereas Date/Time lets you plan to the nearest
15 minutes.
Default setting: DATEONLY
15.5.5 Payroll
Payroll Calculation Period
Set this parameter to calculate the number of days for each month. Setting Exact Days causes every month
to be calculated exactly: i.e. January 31 days, February 28(or 29) days etc. Selecting Fixed 30 days causes
all months to be calculated with 30 days.
Default setting: EXACT DAYS
Payroll Current Period
Use this parameter to set the starting year/month for payroll calculations.
Variable Transactions -- Default Wage Type
Use this parameter to define a default wage type to be added automatically when you insert new variable
transactions into the Variable Transactions tab in the Employee Overview window.
Variable Transactions -- Identification Filter
When wage types are defined, each one can be identified as either Undefined, Variable, Fixed or
Calculation. Then, if this parameter is set to TRUE, when the user clicks the lookup button on the Wage
Type field in the Variable Transactions window, rather than presenting a full list of all wage types registered
in the system, AMOS will present a dialog where the user can select which Identification(s) to filter by.
Then, only Wage Types with the matching Identification will be presented for selection. If this parameter
is set to FALSE, all Wage Types will be presented for selection on a variable transaction, regardless of their
defined Identification.
Default setting: FALSE
Variable Transactions -- Payroll Currency Code
Set the default currency code for variable transactions using this parameter. The standard currency is
defined in the company and vessel registers.
Variable Transactions -- Show Account Number
Set to TRUE, the employees account number will be displayed in the variable transactions tab.
Variable Transactions -- Show Bargain Agreement
Set to TRUE, the employees bargain agreement will be automatically displayed.
139
Variable Transactions -- Show Company Code
Set to TRUE, the company code is automatically displayed.
Variable Transactions -- Show Currency Code
Set to TRUE, the currency code is automatically displayed.
Variable Transactions -- Show Employee First Name
Set to TRUE, the employee first name is automatically displayed.
Variable Transactions -- Show Employee Surname
Set to TRUE, the employee surname is automatically displayed.
Variable Transactions -- Show From Date
Set to TRUE, the from date is automatically displayed.
Variable Transactions -- Show Rank Code
Set to TRUE, the employee rank code is automatically displayed.
Variable Transactions -- Show Status Codes
Set to TRUE, the employee status code is automatically displayed.
Variable Transactions -- Show Vessel Code
Set to TRUE, the vessel code is automatically displayed.
15.5.6 Personnel
Employee Planning -- View Months From Now
Use this parameter to set the number of months from now that should be visible in the Employee Planning
window.
Address Format
Different countries have different standard layouts for addresses. This parameter defines the format to be
used when registering and displaying the employees addresses. Move the characters to change the order
of the fields.
Default setting: 123TZSC
Where 1, 2, 3 = street address
T = Town/city
Z = Zip or post code
S = State
C = Country.
Employee Number Sequence Max
This parameter defines the maximum number that can be used in the Employee Number. This can be used
to reduce errors. Clearing the values from both this parameter, and the Employee Number Sequence Min
parameter, enables the user to avoid auto--numbering in the Crewing > Employee window.
Default setting: 2000
Employee Number Sequence Min
This parameter defines the smallest number that can be used in the Employee Number. This can be used
to reduce errors. Clearing the values from both this parameter, and the Employee Number Sequence Min
parameter, enables the user to avoid auto--numbering in the Crewing > Employee window.
Default setting: 1 (number begins at 0001).
Leave Days -- 30 Days Deduction
When this parameter is set to TRUE, leave days are calculated with 30 days every month. Set to FALSE,
leave days are calculated according to exact days per month.
Default setting: TRUE
Store Documents in the Database
You can attach picture files, document files etc. of certificates, passports, visas and other documents to the
employees records. This parameter tells the system whether or not the files are to be stored in the database.
If they are not to be stored in the database, set this parameter to FALSE and then go to the Directories >
Crew Member Document Directory parameter and define where you want the files to be stored.
Default setting: TRUE
140
15.5.7 Purchase
Output -- Mail Attachment Type
Set the default output type for attachments sent with email to vendors etc. Selecting PDF GHOSTSCRIPT
requires that the Ghostscript driver is already installed on the PC. If the driver is not already installed, an
error will occur when printing an order form to email. Refer to the AMOS Business Suite Installation Guide
for more information about Ghostscript.
Default setting: PDF
Auto Set Delivery Portal Queue
When using e--Business Direct, you can set this parameter to automatically flag the Portal Queue
checkbox on NEW, UPDATED or ALL deliveries. By default, the checkbox will Never be marked. If the
box is checked, the delivery form is then automatically set to be sent with the next portal export.
Default setting: NEVER
Auto--Calculate Form Estimate
This parameter is used to determine if the form estimates are automatically calculated and updated if the
amount is changed. If the parameter has been set to FALSE, it is possible to perform the calculation
manually by selecting Estimate cost from the Options menu.
Default setting: FALSE
Auto--File Fully Received Form
If this parameter is set to TRUE, forms that have been fully received will be filed without prompting.
Note The value of this parameter is ignored when Work Flow on Purchase is in use.
Default setting: FALSE
Auto--Fill Delivery Details
This parameter is used to automatically transfer Forwarder and Destination details within the Deliveries
function in Purchase > Forms.
Default setting: FALSE
Auto--Set Budget Date
If this parameter is set to TRUE, the field Budget Date is set to the current date (Today) when a user prints
an original purchase order. If setting the Budget Date to Today means that the budget code is not valid on
that date, the form will not be printed.
Default value: FALSE
Auto--Update Multi--Vendor Details from Line Item
This parameter allows the system to update the details for all vendors that sell a particular item, with details
entered in a Line Item.
Default value: TRUE
Auto--Update Stock Details from Line Items
This parameter allows the system to update Stock Details with details entered in a Line Item. Set this
parameter to FALSE to prevent stock items updating automatically.
Default value: TRUE
Clean Up For Component In Stock Wanted
This parameter, when set to TRUE, will clear any entries made in the For Component column of the Stock
Wanted window once the desired forms have been generated. If the parameter is set to FALSE the
component number in the For Component column will be set as the default value for that stock item and
will be automatically entered in the column each time the Stock Wanted window is opened. To select a
default component click the lookup button. The parameter Component Search Range in Stock/Wanted
determines whether you are presented with a list of components associated with the selected stock item or
a list of all existing components when clicking the lookup button. This parameter is found in the
Parameters > Options > Stock section.
141
Note If a stock item has only one component associated with it, the component number will be automatically
inserted into the For Component column regardless of the value of this parameter.
Default setting: TRUE
Close Quotation After Query Select
This parameter, when set to TRUE, will automatically save all changes and close the quotations window
after you select a vendor. If the parameter is set to FALSE the user will have to save changes and then exit
the window in the normal way.
Default setting: FALSE
Commodity Purchase
If this parameter is set to TRUE, Purchase Forms (of all types) can be grouped according to Stock Class.
This allows organisations to process each form according to stock class instead of having forms with
multiple stock classes.
Default setting: Empty
Component Search Range in Order Lines
When adding a line item to a form in the Purchasing module, the stock number for the item to be purchased
must be entered. Then define which specific component to purchase it for.
By default this parameter is set to Any which has the effect that if you press the lookup button next to the
line item Component field, a complete list of components is presented.
However, AMOS allows you to attach a list of stock items to a component if you wish, tying for example
spare parts to a piece of equipment. By setting this parameter to Restrict, only those components to which
the selected stock item is attached are listed.
Default setting: ANY
Create New Form On Form Conversion
If this parameter is set to true, performing the following conversion will create a new form containing the
order information and the existing one will take the status Filed.
Note To utilise this feature, specify separate number series for each type of form to avoid having duplicate
numbers for different forms.
Default setting: FALSE
Form Generic Queue field
This parameter facilitates the interface between AMOS and other systems used to handle purchasing and/or
accounting data. When the option When Printed is checked, the Forms Queued For Transfer indicator is
set when an original purchase order is printed. When the option When Approved is checked, a form is
queued for transfer when it is approved.
Default setting: 0 (no value checked).
Form Status After Query Select
This parameter allows for the automatic status conversion of Query forms through the Purchase > Forms
> Quotations window using the Select function. The options contained in the dialog are Unchanged,
Active and Parked.
Default setting: UNCHANGED
Form Type After Query Select
This parameter allows for the automatic form type conversion of Query forms through the Purchase >
Forms > Quotations window using the Select function. The options contained in the dialog are
Unchanged, Purchase Order, Requisition Form and Query.
Default setting: UNCHANGED
142
Interrupt Automatic Form Creation
There are three options for setting this parameter. Set to If Missing Initial Value, the system will check for
initial values and present the Mandatory Fields window only if values are actually missing. The user must
then enter the values and click OK to continue. Set to ALWAYS, the system will interrupt Automatic
Creation of forms and present the Mandatory Fields window (whether values are missing or not) for the
user to enter values if necessary, and click OK to continue with form generation. Set to NEVER, the system
will carry on with automatic form generation regardless of whether any initial values are missing from
mandatory fields or not, creating the forms with database default values.
Default Setting: NEVER
Level of Approval
AMOS supports three methods of form approval:
S None
S Signing
S Actual approval
With None selected, approval is not required before an original purchase order can be printed. With Signing
selected, someone with password authority to approve forms can approve the form using any legal user
name. With Actual Approval selected, someone with password authority to approve forms can approve the
form using only their own user name.
Default setting: ACTUAL APPROVAL
Lock Approved Purchase Orders
If this parameter is set to TRUE, any purchase orders that have been approved are locked for all editing.
This includes all the line items for the form. The Functions tab of the Access Control dialog contains the
field Edit Approved Purchase Orders. If the field is checked, members of the selected group are allowed
to edit a locked purchase order. Once a purchase order has been locked, it is not possible to use the Convert
function to convert it to a different type of form.
Default value: FALSE
Lock Approved Requisition Forms
If this parameter is set to TRUE, any requisition forms that have been approved are locked for all editing.
This includes all the line items for the form. The Functions tab of the Access Control dialog contains the
field Edit Approved Requisition Forms. If the field is checked, members of the selected group are allowed
to edit a locked requisition form. Once a requisition form is locked, it is not possible to use the Convert
function to convert it to a different type of form.
Default value: FALSE
Lock Exported Requisition Forms
If this parameter is set to TRUE, any requisition forms that have been exported are locked for all editing.
This includes all the line items for the form. The Functions tab of the Access Control dialog contains the
field Edit Locked Requisition Forms. If the field is checked, members of the selected group are allowed
to edit a locked requisition form. Once a requisition is locked, it is not possible to use the Convert function
to convert it to a different type of form.
Default value: FALSE
Lock Line Items According to Stock Access
If set to TRUE, users will only be able to order line items according to their access rights for Stock Class.
Default setting: FALSE
Lock Ordered Form Fields
If this parameter is set to TRUE, it is possible to lock fields in order forms with the status Ordered. The
Functions tab of the Access Control dialog contains the field Edit Locked Form Fields. If the field is
checked, members of the selected group are allowed to edit locked form fields. When the parameter is set
to TRUE, the fields Budget Date, Budget Code, Ordered, Estimate and Currency are grey and inaccessible
for editing, as is Options > Estimate Cost.
Default value: FALSE
Note Even if Restrict is selected, you can still enter the number of any component by hand if you wish.
143
Multiple Departments In Order Forms
This parameter, when set to TRUE, allows Order Forms originating from other departments to be viewed
and modified in the current department. Select the desired department from the Department drop--down
list in the Purchase > Forms filter window. This does not allow for the creation of new Order Forms, and
the number of departments available depends on the users global access rights. To use the Split, Copy,
Convert and Receive Order Forms functions and to Add or Update Line Items against an Order Form in
the Slopchest module, set this parameter to FALSE.
Default setting: FALSE
Prevent Quotation Synchronisation
The setting of this parameter determines whether or not any changes in order form line item windows are
synchronised into the quotation lines. Set to NEVER, synchronisation is never allowed. Set to WHEN
SENT, synchronisation will be prevented if one or more quotations are marked as sent. Set to WHEN
RECEIVED, synchronisation will be prevented if one or more quotations are marked as received.
Default setting: WHEN SENT
Require Estimated Cost for Approval
This parameter, if set to TRUE will prevent a user from granting approval for a purchase form if the
Estimate: field in the Cost Overview section of the window is zero.
Default setting: FALSE
Reset Purchase Counter On Financial Year
This parameter, if set to TRUE, will reset the number series for Form, Purchase Order, Query and
Requisition Form on the first day of a new financial year. This is determined by the parameter Start Date
for Financial Year. If the parameter is set to FALSE, the reset will occur on the first of January each year.
Default setting: FALSE
Restrict Original PO Printing
If set to TRUE, this parameter restricts the printing of original purchase orders without a valid budget code
or an estimate.
Default setting: FALSE
Set Date Automatically During Receipt
This parameter controls whether the Receipt Date field of a purchase order is filled in automatically during
receipt. When set to FALSE, the user must enter the receipt date manually.
Default setting: TRUE
Use Latest Delivery Date of Order Lines
This parameter, when set to TRUE, activates the Latest Delivery Date field for purchase form line items.
Default setting: FALSE
Use Quotation Discount Given
This parameter determines whether the field Discount Given in a Quotation is to be used by the function
Options > Calculate to calculate the Quoted Price. If set to TRUE, this function reduces the Quoted Price
by the percentage specified in the Discount Given field.
Default setting: FALSE
Use Vendors Price
When adding items to an order form, the system automatically fills in the line item details from information
contained in the stock item register. If the vendor of the order form is known, the system by default looks
up the item price in the multi--vendor list and uses that price in the line item. However, this behaviour is
only suitable if you are keeping you multi--vendor prices up to date.
If this parameter is set to FALSE, the system instead uses the last purchased price in the line item.
Default setting: TRUE
Use Work Flow
If this parameter is set to true, the Purchase > Forms > Options drop down window expands to include
the Workflow function. The Workflow function allows users to pre--define and automate the process
sequence of purchase forms.
Default setting: FALSE
144
Validate Order Form Dates
If this parameter is set to true, all dates entered on purchase forms will be checked to make sure they follow
a logical date sequence, see below:
CreatedDate Date Created: is registered
ApprovedDate Date Approved: is after CreatedDate and before OrderedDate
OrderedDate Date Ordered: is after CreatedDate and before ReceivedDate
ConfirmationDate Date Confirmed: is after OrderedDate
ReceivedDate Date Received: is after OrderedDate
LatestDeliveryDate Date Latest Delivery Date: is after CreatedDate
Default setting: FALSE
15.5.9 ShipDex
Visualize Fields
The ShipDex interface allows inserts and updates to the AMOS database catalog. When this parameter is
set to TRUE ShipDex--specific fields will become visible.
Default setting: FALSE
15.5.10 Stock
Allow Removal of more Items than in Stock
This parameter controls whether a user is allowed to use or remove a greater quantity of an item than is
actually registered as being available in stock. This is relevant in some installations where a strict reporting
of stock movement is not practised, or when stock items may be removed directly from transit storage or
received shipments before they have been registered as received in stock.
Default setting: TRUE
Approval Required For Stock Transfer
This parameter determines whether approval is required for transfer of stock items between installations.
If the parameter is set to TRUE, a receiving installation will not be able to see a transfer document until
the status has been set to Approved at the donating installation.
Default setting: TRUE
145
Component Search Range in Stock > Wanted
When modifying a quantity in the Stock > Wanted window, the component number that the stock item
is required for may be entered. If there is only one component associated with the stock item then that
number is automatically inserted in the For Component column. If, however, there are several components
associated with the stock item, click the lookup button to choose the component number you require.
If this parameter is set to Any, clicking the lookup button causes a complete list of all components to be
shown. If this parameter is set to Restrict, only the components associated with the stock item will be
shown.
Default setting: ANY
Note Even if Restrict is selected, you can still enter the number of any component by hand.
In/Out of Stock on WO of Status
The setting of this parameter controls whether or not users are allowed to report stock movements in the
In/Out of Stock window against Work Orders with status Completed, Filed or both (as well as against
Active Work Orders). As stock usage can occur after a work order has already been reported, when this
parameter is set to Active and Completed or Active, Completed and Filed, that usage can still be recorded
against the finished work order, ensuring that all stock reported used against the work order is taken into
consideration in stock usage statistics for that work order. If a user selects a work order in the In/Out of
Stock window with one of these statuses, AMOS will warn the user that the transaction will be reported
against a job which is already finished.
Default setting: ACTIVE
Inherit Full Description From Parent
If this parameter is set to TRUE, child stock types that do not have a full description of their own
automatically inherit that of the parent stock type. If the description for the child stock type is subsequently
altered it is saved as the new description for the child stock type only.
Default setting: FALSE
List All Transfer Documents
If this parameter is set to TRUE, the installation lists all the transfer documents that have been submitted
from all installations. This may be quite useful at the main location if the parameter Approval Required
for Stock Transfer has been set to TRUE. At the main installation, it will then be possible to list all the
transfer documents in order to evaluate which should be approved.
Default setting: FALSE
Propose Work Order Required Parts
Allows the system to suggest values when performing an In/Out of Stock transaction for a Work Order.
Default setting: FALSE
Record Stock Usage When Reporting Work
Parameter restricts the ability to report stock usage against a work order, in order to stop double reporting
of stock usage, both in reporting Work Orders and In/Out of Stock functions.
Default setting: TRUE
Stock Control: Populate Actual Column
There are three possible settings for this parameter: In Stock, None, or 0 and the setting determines the
value which will be displayed in the Actual column upon opening the Stock Control window.
Set to IN STOCK, the Actual column will be populated already to match the In Stock column.
Set to NONE, no value will appear in the column at all.
Set to 0, a zero will appear in every line in the Actual column.
Default Setting: IN STOCK
Stock Price Logged
This parameter indicates whether you want the average or last purchased stock price to be used when
calculating stock values.
Default setting: AVERAGE
146
Stock Reservation, Required Booking
If set to TRUE, your system will require advance booking of parts, and users will see a field called Booking
Window, and a checkbox labelled Dynamic Booking in Component/Component Type Jobs > Required
Parts.
Default setting: FALSE
Use Stock Class Access
This parameter, when set to TRUE, allows you to restrict the various stock classes that can be accessed by
each group of users. The access control is to be found in the menu option Tools > Configuration > Groups
> Options > Stock Class Access. Note that if you want to restrict a groups Stock Class Access, you must
define the stock classes available to every group otherwise a group without defined stock classes will only
be able to access stock items with unspecified stock class.
Default setting: FALSE
Use Stock Item Depreciation
This parameter, which must be set before any stock items are entered into the system, tells the system
whether to use stock item depreciation. Depreciation levels are set at Tools > Configuration >
Depreciation Levels.
Default setting: FALSE
15.5.11 Voyage
IMOS Installed
Set this parameter to TRUE if you have IMOS installed on your system. Set to TRUE, this parameter
prevents the creation of any voyages/cargoes in AMOS.
Default setting: FALSE
Import Cargo Group
If you receive a cargo specification from IMOS referencing a cargo type not already defined in AMOS,
the cargo type is automatically created. To create the cargo type AMOS needs a cargo group. The Import
Cargo Group parameter defines the cargo group for cargo types created during import from IMOS.
Default setting: There is no default setting. This parameter must be set manually by the installation
engineer.
Lock Completed Voyages
When this parameter is set to TRUE, you cannot make changes to the details of any completed voyage.
Default setting: TRUE
Lock Discharged Cargoes
When this parameter is set to TRUE, you cannot add any new operations or events to completed cargo
discharge procedures.
Default setting: TRUE
Lock Planned Port Calls
When this parameter is set to TRUE, you cannot make changes to the details of any planned port calls.
Default setting: TRUE
Lock Planned Voyages
When this parameter is set to TRUE, you cannot make changes to the details of any planned voyage.
Default setting: TRUE
Lock Sailed Port Calls
When this parameter is set to TRUE, you cannot make changes to the details of any sailed port calls.
Default setting: TRUE
Unassigned Cargo Department
When a cargo is initially created it may not immediately be assigned to a particular department. This
parameter defines the default department responsible for newly created, unassigned cargo unless/until it
is assigned to a specific voyage.
Default setting: There is no default setting. This parameter must be set manually by the installation
engineer.
147
15.6 Sharing
Although some information may appear to be available from only within a single installation or
department, all information is actually stored in the same set of database tables regardless of which
installation or department they belong to. For the system to be able to show information belonging to a
particular department, it has been necessary to stamp all table entries with a marker indicating which
department they belong to. This mechanism works well for departmental types of information such as
components, stock items etc., but does not suit for information to access at a more global level e.g.
addresses disciplines, job classes and the like.
This set of parameters, one for each table in the database, control how the information contained/owned
by one department is shared out such that it can be accessed by other departments.
There are also three special parameters controlling how the data contained in a table are shared between
departments.
For example, an address register has been established in Inst/Dept 001/01, all addresses will have been
stamped as owned by that department. Unless sharing is defined, these addresses will only be accessible
from Inst/Dept 001/01. To share these addresses such that all departments have access to them, select to
modify the Global Sharing parameters. Then choose the Sharing tab and on the parameter entry reading
Addresses, specify Inst/Dept 001/01 from the list of defined departments. The addresses will now be
accessible from every department.
The same feature can also be used to share information across all departments of a particular installation
by defining sharing at the Installation level, or even at the Department level thereby sharing a single set
of data between two departments.
As described at the beginning of this section, parameter values are inherited downwards from the global
to the department level. For example, if a user logs onto to Inst/Dept 002/03, the system first checks to see
whether sharing has been defined for department 002/03. If nothing is defined, the system then checks to
see whether sharing has been defined for installation 002. If nothing is defined, the system then checks to
see whether sharing has been defined at the global level. If no sharing definitions are found, the system
then defaults to fetching information stamped as owned by department 002/03 (e.g. the current installation
and department).
If you intend to use the component transfer facility within AMOS, you will need to ensure that global
sharing is allowed for the following tables:
Address Component Class
Component Type Counter Type
Discipline Employee
Image Reference Image Reference/Hotspots
Image Reference Links Image Source
Job Class Job Description
Maintenance Cause Maintenance Class
Maintenance Criteria Maintenance Type
Note When defining data sharing, data access rights and data synchronisation, it is very important that you
consider the data ownership (office or vessel) and consequences of the import and export rules you apply,
not only at table level but even at field level. For example, sharing on a component/job record is normally
defined at installation level, but very often the owner of the information is not defined. In these cases, the
office (technical department) might insert new records and update the frequency while the vessel updates
the last done date and the next due date. With both vessel and office making changes, the import and export
rules must be properly defined and modified from the standard ones.
148
-- Mandatory -- every transaction must have a value for this code
-- Optional -- up to the user
-- Not Used -- this code is not in use
2. Next, select the Label parameter for the same Level. Enter a name to identify the transaction code
level by. Codes belonging to this level will be identified with the label you provide. For example,
Responsible or Project.
3. Save your work before exiting the window.
149
Chapter 16 Number Series
Several items registered in AMOS are automatically numbered by the system. Among other things, new
Work Orders and Components are assigned numbers by the system.
Two main factors determine the use of such numbers. Go to Tools > Configuration > Number Series
to open the filter for the Number Series window. Use the Inst/Dept drop-- down list to specify a
department. The Series Type list contains the different types of number series available in the system.
Click OK in the filter to go to the Number Series window. You can sort the window contents by clicking
the header field of the column you want to sort by. Click it once more to toggle the sorting between
descending and ascending.
The Number Series window is for initialising the various number series. In the Auto-- Numbering folder
in the Parameters window (described in section 15.2) you can define input masks to determine which
characters to use when registering data of the different types and rules to determine how numbers are
generated by AMOS.
The Installation/Department column corresponds to the rules you create. The Number Series Sharing
(see section 15.6) determines the Inst./Dept. values. For example, if you share the Address Number
Series globally out of Installation/Department 001/01, then only one entry for 001/01 is required here.
If you share the Form Number Series at the Installation level, then each Installation must have a Form
Number Series entry.
This also depends also on the type of Department. In the case of Work Orders, you may have a Food
Department that does not require the use of Work Orders because there is no equipment to maintain. In
that case, you wouldnt need a Number Series.
The Series Type is the Series you are sharing, i.e. Form, Work Order, Address, etc.
Four of the last five columns correspond to the Rule columns (described in section 15.2) ThisWeek,
ThisMonth, ThisYear, and Total. The columns Week, Month and Year display how many numbers have
been issued in the respective number series in these periods.
Use the Year Reset column to enter the number to reset a number series to at the start of a new year (resets
the column Year). Normally, the value is set to 0, but there are situations where it is relevant to choose
a different value. For example, different department may have different series for issued Forms. The
main office may use numbers from 0, while one installation may use the Year Reset value 1000, and have
the system assign numbers from that starting point at the beginning of the New Year. You must use the
column Year in your Rule for this column to have any effect.
150
Chapter 17 Workflow
Every task progresses to completion through a series of steps called a Work Flow. Configuring this work
flow allows AMOS to perform each of these steps in accordance with your companys existing procedures.
The work flow process can be divided into the following categories:
Select Tools > Configuration > Work Flow to open the Work Flow Configuration window.
The Work Flow Configuration window contains three tabs:
S Statuses
S Actions
S Initial Statuses
Note In the case of Maintenance, Purchase, and Quality Work Order Work Flows, there are two more tabs
present:
S Lock Type
S Lock Access
In addition to performing workflow operations while logged into the system, it is also possible for users
to perform certain workflow actions from remote locations, for the AMOS Purchase module only. This is
called Remote Work Flow. See section 17.3 for more.
151
17.1.1 Creating a List of Actions
Ensure the correct module is selected, as in step 1. above. Open the Actions tab.
The Actions tab is for listing all possible actions that can be used in the Work Flow progression of a record,
to change it from one status to the next. These actions are user defined and should be the same as your own
company processes. In this example, you would define a list of all possible actions that could actually be
carried out on a purchasing form in your organisation: Activating, Cancelling, Filing, Parking, etc.
To add actions, click inside the tab and click the New button on the toolbar. Then enter the action in the
blank line which appears. To delete an action select it and click the toolbar Delete button. Before leaving
this tab, be sure to Save your list.
152
Within this tab, you need to:
1. Create a list of Statuses.
2. Build the Work Flow Transformations.
3. Define AMOS Actions for each Transformation and assign Access to each Action.
Checking the In Use checkbox makes the status available for use in the relevant module.
Inform AMOS which status means Cancelled, by checking the Cancel checkbox beside that status. When
a transformation results in that status, the internal status will be set to cancelled and the work flow status
of the record set to the status identified here. Only one status per module can be marked to result as Cancel.
153
4. You can define a default destination mailbox for each transformation using the names in the Default
Mailbox drop--down list. If you check the checkbox beside this field, the mailbox is restricted.
When a user performs a work flow transformation in AMOS, they can select a mailbox in the
Change Work Flow Status dialog to assign the record to. If a Default Mailbox has been defined
for that transformation then that user Mailbox will be listed already in the Assign To field on the
Work Flow dialog. If the default mailbox has been restricted, the Assign To field will be read only.
5. The icon button beside the Default Mailbox field indicates whether or not an expression is present.
Expressions determine which workflow action(s) is visible and listed in the Change Work Flow
Status dialogs. A True (visible) state means that the transformation will be listed and a False
(invisible) state means that it will be hidden. Clicking the Expression button opens a dialog box.
If there is no previously defined expression for the transformation, the dialog box is empty and you
can create an expression. If there is an expression already defined, it will appear in the dialog box.
Click OK to close the dialog. If the expression is invalid, you will not be able to close it.
6. When you have created all necessary transformations for the status Active, select the next status
in your list and build transformations for that status in the same way.
7. Save your transformations.
4. While a Transformation is selected, the user defined status action appears in the Access to Action
list. Check the boxes of the user groups you wish to assign access to. Those who have access to each
action will be able to view and edit the information at each stage of the process. See section
17.1.2.3.1 for more about Access to Actions.
154
5. Repeat this process to assign AMOS Actions to all the Transformations.
6. Save before exiting this tab.
Note The AMOS Action File Full Received supports filing of a fully received purchase form, and is only
available to the Purchase module. When the user selects this action from the Change Work Flow Status
dialog, if the selected form is fully received, the new work flow status will be set according to the status
defined in the transformation. If the form is not fully received, it keeps its original status.
If you use this action, make sure that the action Receive is also part of the list and is listed as the second
action, after File Full Receive. If Receive is not in the list you will not be able to Save your
configurations and if it is listed first, your configurations will not work correctly.
Figure 134 The Work Flow Configuration Window -- Initial Statuses Tab
155
17.1.4 Work Flow Configuration --- Lock and Unlock
If you are configuring Work Flow for the Maintenance, Purchase or Quality Work Order modules, there
are two additional tabs available in the Work Flow window:
S Lock Type -- a list of all possible Locks that restrict or grant access to particular work flow statuses
to groups of users.
S Lock Access -- a list of all the Groups that can be assigned to different locking types.
The AMOS Work Flow actions Lock and Unlock make it possible to define any number of locking levels
in the Maintenance, Purchase and Quality Work Order work flows and grant specific group(s) the ability
to edit work orders or purchase forms which are assigned a specific locking level. This enables work flow
to control which groups can edit work orders or purchase forms of a particular work flow status. This can
be useful, for example, if work orders pass through a planning stage where they can be edited only by
members of a planning team and not by other users.
The locks are created in the Lock Type tab. To create a new lock, click the New button, and enter a code
and description for the lock. These locks appear by their codes, in the Lock Access tab. There is a column
of checkboxes under each lock code. Check or uncheck the boxes beside the user groups, to assign or
restrict access as necessary. In the Status tab, select a particular status you wish to apply locking actions
to. In the far right of the window, choose the AMOS Action Lock or Unlock, and the Lock Type that you
wish to lock or unlock for the selected status. You can lock and unlock as many lock types for the selected
status as necessary.
In the Initial Statuses tab you can assign Initial Lock types to apply at the initial status of a record, in other
words when it is created.
156
17.2 Using the Work Flow
Some aspects of using a configured work flow follow below.
157
If the access control entitled delegate mailbox access is enabled for the user, they will be able to delegate
any users mailbox to any other user.
158
S Purchase Template: a purchase template, containing the format your company uses. This will be
presented to the remote user in the HTML attachment and will look similar to the normal Workflow
transformation dialog used in local work flow.
S Send Mail: must be set to TRUE. FALSE can only be used in the setup process (to avoid sending
the mail), for debugging purposes.
S Use Remote Workflow: this system--wide parameter must be set to TRUE to allow use of remote
workflow in your system. Set to true, users will have the option to turn remote workflow on, in the
Options window.
You also need to define a directory to temporarily store the HTML files that are queued for export, before
they are sent to the remote user. Go to Tools > Configuration > Parameters > Directories:
S Remote Workflow Directory -- enter a valid folder to store the HTML files. For example, C:\Temp.
159
Figure 137 Creating an Address Record for the Employee
160
9. Enter a Discipline and the hours of Availability, and Save the record. Close the window.
10. Now link the Employee record created in step 5, to an AMOS User record:
Go to Tools > Configuration > Access Control > Users. Click the New button in the toolbar.
11. Enter a Login ID and Name, and fill in the Occupation and Comments fields as needed.
12. Use the Employee drop--down list to select the employee created in step 5.
161
17.3.4 Using Remote Work Flow
When a user has remote work flow functionality enabled and switched on, and he is not logged in to the
system locally, AMOS will send him email allowing him to use workflow from a remote location:
1. A local user opens the Forms window, creates a new form, and Saves it.
2. The local user performs a workflow transformation on the form in the Workflow dialog, and assigns
it to a user in the Assigned To drop--down list. The assigned user has remote workflow enabled and
on.
Note If the assigned to user does not have remote workflow enabled, nothing happens until he processes the
transformation in the usual way.
3. The system queues the form for export, and then sends an email to the assigned user. It arrives with
an HTML attachment.
Note Occasionally the remote user might receive a winmail.dat file. This is because of the mail client and/or
server configuration. In this case, the remote user should forward the mail to himself and it will convert
back to an HMTL document on being resent.
4. The remote user receives the mail, and processes the HTML file in the same way he would work
in the Workflow Transformation dialog -- assign to a user, selects an action to change the status, etc.
5. When finished with any changes to the HTML file, the remote user clicks Send. Closing the email
without clicking Send causes it to be ignored.
6. The email is sent back to AMOS, and processed by the system.
7. The system performs the updates to the workflow object, and saves it.
8. AMOS sends feedback to the remote user. The feedback email will contain one of three possible
responses:
S Ignored -- the remote user modifications have been ignored because the workflow action selected
contained instructions that can only be performed when logged into the system.
S Ignored -- the remote user modifications have been ignored because the status of the object was
changed before the system received the remote user response. This can occur if, for example, the
remote user has delegated his mailbox access to another user in his absence.
S Accepted -- the remote user modifications have been made and saved.
162
Chapter 18 Mandatory Fields
You can define fields as mandatory. This prevents the user from saving information in a window with
mandatory fields, until all required fields are filled. Separate error messages for each mandatory field
should be added to assist the user to enter the required data. Using mandatory fields means you can
specify information that must be included, for example on Order Forms, Work Orders, Component
records and other areas. Go to Tools > Configuration > Mandatory Fields to open the window for
defining which fields should be mandatory, and creating the error messages to go with them.
The window is divided into two areas, with Tables listed on the left side and Columns and Error
Messages listed on the right side. Select any Table already listed to see the Columns on the right side
which have been defined as mandatory fields for that table, and their associated error messages.
163
Remember:
S You can add several columns to a single table (one by one or all at once using multi-- select), each
denoting a different field with a dedicated error message.
S The error message can be up to 60 characters long.
S Existing records, if modified, also need to comply with the mandatory field requirements.
S There is no verification of the actual content in a mandatory field. Error messages only appear
if the field is empty.
S Deleting a Table also deletes all corresponding columns and error messages.
Note The lookup filters display either a complete list of database tables, or all of the columns within the
selected table. This means that it is possible to make any field mandatory regardless of the practicalities
of doing so. When defining mandatory fields, be sure to avoid illogical or impossible requests.
Note There is a parameter that controls the automatic creation of Forms with mandatory fields. See section
15.5.7, Interrupt Automatic Form Creation Due to Mandatory Fields parameter, for more information.
164
Chapter 19 The Dashboard: Alerts Overview
When AMOS Business Suite is started up the user has the option of opening the application to a
customisable homepage, or Dashboard. Users can add convenient information to their dashboard, such
as Alerts. What each user sees in their Dashboard will vary according to their own settings, and
alterations to their data. Switch your Dashboard on and off by checking or clearing the Enable
Dashboard checkbox in the Dashboard tab in the Options window at Tools > Options.
This Chapter discusses the Dashboard Alerts Overview. For information about other Dashboard features
and functions, see sections 2.2.1 and 12.4.
Each user can customise the list of Alerts that appear on his own Dashboard:
1. First, the Alerts which will be available in the system must be defined in this window as described
in section 19.1.
2. Then, in the Options window each user can change the alerts present in his or her Alerts Overview
by choosing from the list of available ones (see section 19.2).
You can adjust your view of the dashboard alerts by using a separate thread for retrieval, according to
the setting of the system parameter Use Separate Retrieval Thread (see section 15.5.3). If set to
TRUE, the user can continue to work without being interrupted by dashboard operations. In this case
indicators on the dashboard will inform the user which alert is currently being processed and although
the values will be updated immediately for each alert, the alerts bar and pie charts will be updated when
all alerts have been processed.
5. Open the Access Control tab. Check the boxes according to who should have Read access. Users
in User Groups with a checkmark here, will be able to choose these Alerts in the Options window,
to display on their Dashboards.
6. Save the Alert Group.
165
19.1.2 Defining a New Alert
1. Select a group, and click the New button on the toolbar. In the dialog that appears, click No.
2. Underneath the new Group, another icon will appear, titled Alert.
3. Enter a Name for the Alert.
4. In the Description field, enter the text you want to show in the Tooltip when the user positions
the cursor over the Alert on the Dashboard.
5. Click the button beside the Graph Bar Color field and then use the RGB colour model to define
the colours which the alert bars should appear in on the Dashboard.
Note To define if the length of the bar should be affected by the alerts with the highest value amongst all alerts,
or amongst the same group, set the parameter Alerts Maximum Size. See section 15.5.3.
6. Use the Designated Window drop-- down list to select the window to be opened automatically
when a user double-- clicks on this alert on the Dashboard. This field is only available if the
checkbox Row count defines the alert value is checked.
If you uncheck this box the alert displays in the same way, but its value is based on a calculation
and so there is no window to open by clicking the alert on the Dashboard.
7. In the SQL Syntax section, define an expression. This can be done manually or automatically:
Manually:
Note The system will modify the SQL expression you define, to retrieve the number of rows and not the
complete data you specify. This reduces the returned rows for speed and network traffic improvement.
However, a user can get an indication of what SQL is really performed, by pressing the SHIFT key and
moving the cursor over the alert in the Dashboard - a tooltip with the modified SQL will appear.
Use the following syntax: SELECT COUNT(expression)FROM tables WHERE predicates;
For example (see below step 8 in this section, for more detailed examples):
Display the number of overdue Maintenance Work Orders which are Issued:
SELECT COUNT (workorder.workorderid) FROM WorkOrder WHERE
( DueDate < getdate() ) AND ( WOStatus in (6) )
Automatically:
If you are not familiar with AMOS table structures and SQL commands, you can use filters and
drag and drop, to provide the information AMOS needs to make the SQL statement for you. For
example, to create an alert that informs the user how many overdue work orders are present in
the system, with the Alerts Configuration window still open, open the Maintenance > Work
Orders filter. Set the filter criteria to return only overdue work orders and click OK. When the
window opens, it will display a list of only those work orders that are overdue. Click anywhere
inside this list, and drag the mouse into the SQL Syntax box on the Alerts Configuration window.
AMOS will take this information and then convert it to an SQL statement for this alert, defining
that the user alert will track overdue work orders. The resulting SQL statement is dynamic,
meaning that it varies with your data. In other words, if there were only 20 overdue work orders
in the system at the time you defined the alert, but later on, the number increases to 30 - the alert
will reflect this change. Note that dragging and dropping from the Stock Wanted window, is not
supported.
166
Figure 143 Defining a New Alert
167
Note You can add comments into the SQL statement by placing // in front of your comment.
AMOS can also send an email to the responsible user address(es) as defined on the alert, along with the
predefined subject and text. To set a Threshold on an Alert:
1. Ensure the correct alert is selected on the left side of the window.
2. Click the button beside the Threshold Colour field and then use the RGB colour model to define
the colours the alert bar will change to on the Dashboard display, when the threshold is crossed.
3. Define an expression in the Threshold SQL Syntax area in either of the two ways as described
above. Again, you can use drag and drop to easily provide the information AMOS needs to make
the SQL statement for you.
4. Save the Threshold.
To enable AMOS to send automatic email notifications when this threshold is crossed:
5. Again, ensure the correct alert is selected on the left hand side. You cannot define an email
notification on an Alert Group. Open the Notifications tab.
6. If an email notification is already configured for the selected alert, it will appear here. Only one
email configuration can be defined per alert. Otherwise, the fields are blank and you can create
your new email configuration.
168
7. Using To, Cc and Bcc you can insert a string of addresses separated by semi-- colons. AMOS will
not verify these addresses.
8. Enter a pre-- defined Subject and Text. For example, Subject: Overdue Work Orders. Text: Please
process the work orders in your queue. The number of overdue work orders is above the
acceptable limit.
9. Save the pre-- defined mail. To enable the mail to be sent, see section 19.2.3.
Figure 146 The Tools > Options window: Dashboard tab and settings
169
19.2.2 Alert Gauge
It is also possible to display a gauge along side the Alert bars, with numbers on a dial visualising the alert
values. This gauge is switched on or off in the Tools > Options > Dashboard tab.
1. Go to Tools > Options. The Options window opens.
2. Open the Dashboard tab.
3. Enable the Alert Gauge by checking the Show Alert Gauge checkbox.
4. Click OK to close the dialog.
5. On the dashboard, a gauge with two indicators, one blue and the other red, will appear.
The blue indicator represents the value of the currently selected alert. The red indicator represents the
threshold value of the currently selected alert.
170
This function requires two arguments as per the following table:
The function must return a long value as per the table below:
When the dashboard calculates the value of an external alert, the function executes and the result is
displayed on the dashboard. When a user double-- clicks the alert to drill-- down, the function is called and
subsequently performs the drill-- down action.
171
Chapter 20 Printer Tasks
Once reports have been defined and added to the report hierarchy, you can define printer tasks to handle
the report printing on a selected printer.
The Reports Menu window (Tools > Configuration > Extension Features > Reports Menu), which
is described in section 28.6, contains a tab called Misc. where you can select a printer task name from
the drop-- down list in the field Printer Task.
To create the tasks that will appear in the drop-- down list in the Reports Menu window Printer Task field:
1. Select Tools > Configuration > Printer Tasks to open the corresponding window. Give each task
a name, and add a comment describing the task further:
2. Save the named Task. The Options menu becomes active. Go to Options > Printer Task
Configuration to open the Task Configuration dialog.
3. If no printer names appear when you open the drop-- down list in the Identification field, select
Options > System Printers (in the Task Configuration window) for AMOS to add the printer
definitions available on your PC into its own database.
AMOS imports the necessary information in a few minutes. After the process is completed, you
can select the desired printer from the drop-- down list.
S The Comments field is optional, you can use it to describe the selected printer.
S Use the Copies field to specify how many copies to print in the selected printer task.
S Click the lookup button next to the Paper Source field to get a window to select the paper source.
This window displays the defined paper sources in the selected printer.
4. Save the window and close it to return to the Printer Tasks dialog.
172
Chapter 21 Installations and Departments
The AMOS Business Suite contains functions to handle complex organisations. The
Installations/Departments window lists all the Installations (Office, Vessels, etc.) within your
organisation, and the Departments (Maintenance, Personnel, etc) which belong to each one. The
Installation Groups window is for arranging your installations into groups for easier management.
As you work in AMOS Business Suite, you can move from one department to another by selecting File
> Switch Department to change which department you will work in at present. Switching Departments
is discussed in section 21.2.
Furthermore, AMOS Business Suite allows you to handle more than one Company within the same
system; each one as a separate financial entity with one or more of its own installations. This
multi-- company management is defined in the Company window, and is discussed in section 21.3.
The left side of the window displays a hierarchy, containing the Installations and Departments already
registered. To add a new Department to an existing Installation, first select the Installation in the
hierarchy and then click New. In the New dialog, select Department and click OK. Carry on to Step
6. Or, to create a new Installation first:
1. Click the New button. In the New dialog, select Installation. Click OK.
2. A new Installation icon is added to the hierarchy. Fill in the Installation fields on the right side
of the window:
S Code/Installation - enter the code and name for the installation.
S There are two separate Comments fields available for any textual information your organisation
wants to connect to this installation.
S Site Code - a shortform code. For example, AVO for the installation AMOS Voyager.
3. Save the Installation.
4. To add a Department to it, ensure that the new Installation is still selected and click New.
5. In the New dialog, select Department and click OK.
6. A new Department icon is added beneath your new Installation. Fill in the Department fields on
the right side of the window:
S Code/Department - enter a code and name for the department.
S There are two separate Comments fields available for any textual information your organisation
wants to connect to this department.
S Cost Centre - select the default cost centre for this department from the drop-- down list.
7. Save the Department.
173
You can also move a department easily by dragging it from one installation and dropping it into another
installation. Departments cannot contain any sub-- levels.
To make an installation or department active and available, check the Active checkbox at both levels.
Uncheck the Active checkbox to deactivate the selected installation or department. Deactivated
installations/departments will not be a part of Global Search operations, and users will be prevented
from switching to these areas.
If you try to make any changes to an existing Installation or Department, on Saving AMOS will present
a Change Reason dialog. A reason for the change must be entered to appear in the Status Log, before
saving will be allowed. The Changed On and By dates are updated here automatically.
174
Note Close any open windows prior to switching departments. It is not possible to switch from one department
to another while windows are open.
The default sort order for Installations and Departments is by Code. If you change the Sort By setting
to Name, the installations are automatically ordered alphabetically with the departments within their
installation ordered alphabetically also.
175
Chapter 22 Extension Features
Extension Features allow you to customise certain areas of the AMOS Business Suite by integrating
certain external programs (modules), and user-- defined reports specifically required in your organisation.
Selecting Tools > Configuration > Extension Features opens a sub-- menu containing three items:
S Reports Menu - opens the window for creating a hierarchy of user-- defined reports. New reports
are added here and then appear (with correct access) in the standard Report browser.
S Modules Menu - allows you to integrate certain external programs and user-- defined
PowerBuilder modules into the AMOS Business Suite.
S Access Modules - for setting up new groupings (Access Modules) in the Access Control window
to add user-- defined reports and programs into. Then access rights can be assigned to these new
access modules.
Any previously added modules will appear in the left side of the window. You can organise these and
any new modules in any way you choose by using drag and drop to create a hierarchy structure. If you
make any alterations to the Modules menu, re-- start AMOS Business Suite to show the changes.
176
The example below shows you how to add the Calculator to your Modules menu:
1. Click the New button. Fill in the fields as follows:
S Menu Text - text that will appear in the Tools > Modules sub-- menu.
S Type - there are three selections:
- Executable for external programs;
- Executable blocking application for external programs that will halt the operation of AMOS
until they are run and closed; and
- PB Function for PowerBuilder executable programs.
S Start Command - lookup the location of the .exe file to launch the program.
S Microhelp - text that will appear in the lower left hand corner of the screen.
S Button Bitmap - use the lookup to select a bitmap graphic file (files with a BMP extension) to
place on the toolbar. Or choose a pre-- defined one from the drop-- down list.
S Item Text - text that will appear on the button if the option to display Toolbar Text is on. The
Toolbar Text option is turned on and off by the current user in the window at Tools > Options.
S Toolbar Tip - text that will appear when you hover over the button if the option to display Toolbar
tips is on. The Toolbar Tip option is turned on and off by the current user in the window at Tools
> Options.
S Order - where the button will appear on the toolbar; generally best set to higher values, i.e. 99
or 100 or greater.
S Space Before - amount of space between this button and the one to its left on the toolbar;
generally set to 1.
2. Save your module. Carry on to section 22.3 to create an Access Module to add the Calculator
module to. Until the Calculator is added into an Access Module, it will not be available for use.
Once there are modules/programs available and you have the correct access level within the system, the
Tools menu will contain the extra entry called Modules, and the sub-- menu will list the modules available
to you as below:
177
Figure 154 The Access Modules Window
2. Select an existing Access Module to add the calculator to, and go to Step 3.
Or, create a new Access Module by clicking the New button. Enter a Name, for example, External
Programs.
3. Ensure the correct Access Module is selected, and go to Options > Module Contents. A new
window opens.
4. Use the lookup button to select your new module - in this case, the Calculator. You can add more
than one program into the same Access Module if you want.
5. Click Save and close the Module Contents window to return to the Access Modules window.
6. Click Save in the Access Modules window and close the window.
Now, grant the relevant User Groups access to the program(s) in the access module. This is done in the
Access Control window:
7. Go to Tools > Configuration > Access Control > Groups. The Groups window opens.
8. Select a Group to grant access to.
9. Go to Options > Access Control. The Access Control window opens.
10. Open the Reports/Modules tab. Scroll down til you see the User-- defined Reports section with
your access module External Programs, underneath it.
11. Check the Execute checkbox beside the External Programs entry to allow the selected user group
access to the programs in the access module as listed in the Module Contents window.
178
Figure 156 Granting access
12. Save before exiting the window. Restart AMOS for these changes to take effect. User-- defined
modules will be available at Tools > Modules.
179
Chapter 23 Setting up Budget Codes and Formulas
Budget Codes and use of the AMOS Budgeting functions are discussed the AMOS M&P User Guide.
However, the three windows for configuring certain fundamental aspects of the Budget module are
accessed at Tools > Configuration > Budget, and are listed below.
180
4. Close the Parameters window, and go to Tools > Configuration > Budget > Budget
Commitment Formula. The corresponding window opens.
5. This window contains columns in three groups:
S Type - a list of form types: Purchase Order, Requisition Form and Query.
S Status - the workflow statuses that apply to forms, such as Split, Cancelled, etc.
S Impact - three lists with radio buttons: None, Forecast and Committed.
Note If Purchase workflow is in use, the system will only provide the workflow status column to register the
impact against.
6. Use this window to define whether or not each form/status combination will have an impact on
either the Forecast or Committed column in the Budget windows, or no impact at all.
7. Save your settings and close the window.
Read more about this functionality, in the AMOS M&P User Guide.
181
Chapter 24 Condition Based Maintenance
Condition--based Maintenance (CBM) provides a means of integrating various equipment measurements
and monitoring systems with the maintenance features of the AMOS Business Suite. Any or all
periodically planned jobs can be activated prior to their normal due date, as dictated by the deterioration
of the equipment. In this way, planned and condition--based work can be completely integrated.
In addition, the CBM module also offers an automated mechanism for updating counters in the system (like
running hours). These can be discreet values (like temperature or pressure), or accumulated ones (e.g.
running hours, take--offs, etc.).
Finally, AMOS supports a CBM dialog from several sources at the same time, allowing the system to
simultaneously connect the various data capture systems installed at the site.
Note Remember that the CBM is not an alarm system. CBM--active values should indicate non--critical states
as compared with alarm levels; therefore, the monitoring system must make a distinction between these
two degrees of severity. The principle behind the CBM module is to stop the trend before the alarm level
is reached. Since the CBM module is designed to provide a signal prior to the alarm level, maintenance
periods can then be stretched as far as possible without endangering the equipment. However, the CBM
Alarm interface does allow AMOS to communicate with any ECMS to process alarms. See section 24.5
for more information.
24.1 Overview
The CBM solution is based on the transfer of special information files between the data capture system(s)
and the AMOS Business Suite. These files are called CBM day--files, as they are named according to the
date when they are written.
These day--files are written by monitoring and other data capture systems to a directory shared with AMOS
and contain the ids of measure points or values which have either reached a pre--defined CBM--active
threshold, show an unwanted trend or simply have updated counter information.
The shared CBM directory must be on a file server which is accessible to the various systems, and where
the AMOS Business Suite has been instructed to search for day--files at pre--defined intervals. As day--files
are found, they are processed and deleted if the operation went without error. Otherwise, they are renamed
to prevent the system from attempting to process them again and the user is alerted.
During day--file processing, each line in the day--file is read by AMOS and matched to one or more
components in the system. At this point maintenance work is flagged as CBM--active and/or counters are
updated with new values.
182
Figure 158 An Example of the CBM Status Alternatives
AMOS signals the user of the general CBM status through the CBM state indicator at the bottom right--hand
corner of the screen.
This indicator is red if there is a single job with the CBM status of Unacknowledged. If there are no
unacknowledged jobs, but some have the status Acknowledged (e.g. CBM--active, but issued), then the
indicator is yellow. Otherwise, green shows that there are no CBM jobs which need immediate attention,
or which are pending.
183
Options > General > Default Settings > Initial CBM Work Order Status -- controls the Initial Status
of Work Orders when CBM is in use. The available options are Requested, Planned and Issued. Default
setting: ISSUED.
Options > General > File extensions -- these parameters allow you to set the file extensions used in
AMOS.
Options > General > Maintenance > Auto--Filing Of Work Orders > Auto--File Completed CBM
Work Order -- set to TRUE, CBM work orders are filed automatically when the status is set to Completed.
Set to FALSE, it is necessary to manually file such work orders. Default setting: TRUE.
Options > General > Maintenance > Auto--Filing Of Work Orders > Auto--File Controlled CBM
Work Order -- set to TRUE, CBM work orders are filed automatically when the status is set to Controlled.
Set to FALSE, it is necessary to manually file such work orders. Default setting: TRUE.
Options > General > Maintenance > Seconds Between each CBM Check -- controls the frequency at
which the system checks for CBM activity. Default setting: 180.
ID Two--character code identifying which data capture system this entry applies to,
as described at the start of this chapter. The ID is part of the file extension used
during import.
CBM Code The ID of the measure point in the data capture system. Part of the file content
and identifies the CBM Reference record.
Inst/Dept Contains the installation and department number of the component that this
measurement point is linked to.
Component This is for the number of the component whose counter is to be updated, or
whose CBM work is to be activated (or both).
Type This field tells whether this entry is of the counter update, measure point up-
date, or job activation type.
Job Code If this reference is for activating CBM work, then this field will contain the
code of the job attached to the specified component that is to be triggered.
Counter For counter update references, this field will indicate which counter to update.
184
This table is a global one, applying for the entire company, and specifying references to components in any
or all installations and departments.
Note There may be several references for the same CBM code, allowing a single signal from the data capture
or monitoring system to activate any number of jobs, or update any number of counters for different (or
the same) components. Similarly, the same component may appear in several references, again facilitating
both job activation and counter updates for the same piece of equipment.
24.4 Day---Files
As mentioned above, day--files are used to transfer CBM information between data capture and equipment
monitoring systems and the AMOS Business Suite. As was also mentioned above, day--file are named after
the date when written:
19970428.%NC
The filename is a date is in the form YYYYMMDD with an extension made up of a percent sign (%) followed
by a two--character code called the CBM id. This CBM id tells the system which data capture system
created the day--file.
CBM ids should be unique for every supplier of data capture and equipment monitoring systems. Some
examples are NC for NorControl and SP for SPM Instrument International. Since day--files created by
systems from different suppliers have dissimilar extensions, then these files can co--exist in the same CBM
directory without conflicting with each other.
Each day--file contains the CBM information accumulated for a single day from a single monitoring
system. When this system needs to register additional information for the same date, it must append this
data to the same day--file. CBM day--files are in ASCII text format, each line ending with a carriage return
character. These lines may be in one of two formats:
Where the <value> field shown above is a numeric value followed by a Counter code (like H for Hours).
Therefore, the following examples are all valid CBM day--file entries:
S MAIN_EXH_VALVE
S TEMP_POINT_3
S +10.5,DIESEL_GEN_1
S =53.25,MAIN_COMPRESSOR
S =1054H,PACKING_MACH_1
The first two lines above would be signals from the monitoring system that related CBM jobs needed to
be carried out. The third line specifies that 10.5 be added to the counter registered for the measurement code
DIESEL_GEN_1. The next line sets the counter for MAIN_COMPRESSOR to 53.25 (using the default
counter which is Hours). Finally, the last line also sets the total value of the Hours counter, this time
updating the PACKING_MACH_1 counter to 1,054 hours.
185
24.5.1 Flow of Events
1. An Alarm is generated by the ECMS.
If the Alarm is determined valid, it is marked for export, and then exported.
2. The AMOS CBM module receives information about the alarm. A work order is generated based
on this information.
3. AMOS exports the work order information.
4. The ECMS imports the work order information, and the alarm is locked.
5. AMOS users process the work order and mark it as completed. Notification of the work orders
status is exported.
6. The ECMS imports the work order information and the alarm is unlocked.
186
AlarmDate Not used by AMOS. No ECMS
Error Error message, if any from AMOS.* No AMOS
187
Chapter 25 The AMOS e---Business Direct Solution
AMOS e-- Business Direct transforms all the paperwork, manual entry of price information, and sending
out requests for quotations, into an automated process. It allows AMOS users to send purchase
documents such as Requests for Quote and Purchase Order, as email attachments in the form of an HTML
document, directly to vendors, upon printing the form to portal.
This portal works in the same way as the other drivers except that it bypasses the portal center the other
drivers require.
When sending purchasing forms between your system and selected vendors:
1. A user prints a form to the portal, and the form is tagged and queued for export.
2. The driver picks up that form, converts the data into XML, JSON or pure HTML, and creates an
HTML page.
3. The HTML page is stored in the portal outbox and sent automatically to the vendors email
address.
4. The vendor receives the email and can open and read it. He or she can also fill in information,
and then select a command on the page.
5. The system then produces another email with this data, and sends it back to the AMOS user.
6. AMOS reads the incoming mail and produces an import file.
7. The file is processed and the form is updated with the new data.
25.1 Configuration
Configuring the AMOS e-- Business Direct functionality consists of the following process:
1. Set Sharing
2. Set Access Rights
3. Set the System Parameters
4. Setup the AMOS e-- Business Direct Users within your organisation
5. Define the Portal format
6. Register the Portal
7. Connect the Vendors
You can also choose to create Import/Export Tasks to further automate the process, and to create custom
templates so that the emails sent to the vendor reflect your own company style.
188
25.1.2 Set Access Rights
Access rights to the following registers are required to set up the e-- Business Direct module:
S e-- Business Formats
S e-- Business Portals
e-- Business Direct users may require access to the following fields:
S Form: Portal Queue
S Quotations: Portal Queue
For advice on setting Access rights, please contact your local SpecTec representative. Note that access
to the Portal Queue checkbox allows users to simply check the box, thereby exporting the e-- portal and
bypassing the portal validation and print operation.
189
5. Save the record, and close the window.
If your system license contains AMOS Personnel, carry on to step 6.
If you do NOT have a license for Personnel, skip step 6 and go directly to 7.
6. Go to Crewing > Employee. In the Employee Overview window, click the New button and create
a new record for the employee. Be sure to follow your standard company procedure for creating
a new employee.
Save the new record and close the window.
7. Go to File > Open Register > Employees to link the address record to the employee record.
8. In the bottom list part of the window, find the employee record and select it. The employee ID,
Last Name and First Name appear automatically in the fields at the top of the window.
9. Click the Address lookup button and select the new address you created in step 3.
10. No further details are necessary; however you can add a Discipline and the hours of Availability
if that is in accordance with your company procedures.
11. Save the record. Close the window.
12. Now link the Employee record created in step 5, to an AMOS User record: Go to Tools >
Configuration > Users. Click the New button in the toolbar.
13. Enter a Login ID and Name, and fill in the Occupation and Comments fields as needed.
14. Use the Employee dropdown list to select the employee created in step 5.
190
Figure 162 Linking the Employee Record to an AMOS User Record
191
Note Portal Format Drivers (*.pfd files) are installed into the root installation folder at installation of AMOS
Purchase. The file amosebusinessdirect.pfd is the pfd for the AMOS e-- Business Direct solution.
S Import/Export Function - contains the necessary commands to activate the required function
from the driver file. If these fields are empty and the correct driver file installed click on the
lookup buttons at the right of these columns and the application will automatically import the
function files from the driver file.
S Version - contains the identification code for the driver you are using. Driver files may be
periodically updated and you can check this code to ensure that you are using the most up to date
drivers.
4. Save the information, and close the window.
192
- MailMessageFilePO - to insert a message as above, but specifically for POs, use this setting
to insert your custom text. If there is no value for this setting, any text entered for
MailMessageFile will be used for Purchase Orders.
- POFTemplate - an HTML filename with path, that contains your organisations Purchase Order
Form style.
- RFQTemplate - an HTML filename with path, that contains your organisations Request for
Quote style.
- SendMail - must be set to TRUE. FALSE can only be used in the setup process (to avoid sending
the mail), for debugging purposes.
- ReturnMailAddress - a valid address used to receive data back from the supplier.
- XMLConfiguration - the XML data island configuration file, which tells how to retrieve and
build the XML data that will reside inside the portal produced HTML document. See section 25.4
for more information.
- AllowUpdateInMultiVendor - if set to TRUE users can update multi vendor details from
portals. Conditions on address and portal level must be met to enable this: in the Address window,
check the Allow Update of Multi Vendor checkbox. The set purchase unit for the item must be
the same as the unit quoted by the supplier, to update price. The Update Stock Items checkbox
on the Quotations window must be checked. If the vendor exists on the Vendor tab in Stock Items,
the price will be updated. If the vendor does not exist on the Vendor tab, the vendor will be added
with the newly quoted price.
- AddCheckSum - set to TRUE, a comment will be inserted into the file to be used for tamper
control. See section 25.3 for more information.
- SMTPServer - the name of the SMTP server.
- SMTPPort - the port to connect to the server, usually port 25.
- SMTPUser - the user name on the SMTP server, if the server requires it.
- SMTPPassword - the user password on the SMTP server, if required.
- HTMLType - tells AMOS which type of HTML file to produce. There are three values available:
HTML/XML, HTML/JSON or HTML/NoScript. Read about these settings and the types of files
they produce, in section 25.5.
- JSONLibrary - when the HTMLType is set to HTML/JSON, this setting tells AMOS how to link
the JSON library to the produced HTML file. The three values available are: INTERNAL, URL
or FILE. See section 25.5.2.2 for more information.
- MarkOfTheWeb - due to increased security restrictions in the Local Machine Zone (when
running with WinXP SP2), dynamic data in HTML files sent to vendors is sometimes not
displayed. Mark of the Web (MOTW) is a feature of Windows Internet Explorer used to determine
the security zone of the page. When MOTW is set, the value will be added to the HTML document
and Internet Explorer will assign the page to the Internet Zone instead of the Local Machine Zone,
displaying the dynamic data correctly.
A sample setting string, assuming the use of custom templates, could look like this:
MailUser=JoeDoe;MailPassword=xyz;POFTemplate=Z:\AMOSe-- BusinessDirect\Pot.html;RF
QTemplate=Z:\AMOSe-- BusinessDirect\RFQt.html;
SendMail=TRUE
4. Save the information and close the window.
193
3. Make certain to enter the correct E-- Mail.
4. Use the drop-- down list to select the Portal you have created in the previous two sections.
194
25.2 Using AMOS e---Business Direct
The AMOS e-- Business Direct solution allows exchanges of the following forms, over email through the
designated portal:
From your organisation to a vendor:
S Requests for Quote (RFQ)
S Purchase Orders (PO)
From the external vendor, to your organisation:
S Quotations (QT)
S Purchase Order Confirmations (POC)
To utilise the functionality, first configure the system as described in the previous sections. Then:
1. Open the Form window, and create and save a new form as usual. When selecting the vendor(s),
ensure that each one is defined as a Portal vendor (see section 25.1.7).
2. Tag the form, and choose File > Print. The Print Tagged Forms dialog opens.
3. Select your Destination, in the Destn drop-- down list, as Portal.
4. Click OK.
5. After printing to portal, the Portal Queue checkbox on the form is marked and the form is queued
for export.
6. If you created import/export tasks for this function (see section 25.1.8), the portal is exported
automatically through the taskserver. If not, export it manually by selecting File > Export and
choosing the portal.
The Portal Queue form field will become unchecked, and an HTML file is created and held in
the folder defined for the portal.
7. AMOS connects to the mail client and the email is sent to the vendor.
8. The vendor receives the email, and can register details such as Currency and Price on a Query
form, or on a Purchase Order, can click command buttons to Accept or Reject the order, etc.
9. The vendor then clicks Send, and an email is sent to the AMOS user.
10. The returned forms are saved in the import directory in your system. If you created import/export
tasks for this function (see section 25.1.8), the portal is imported automatically through the task
server.
If not, import it manually by selecting File > Import, and choosing the portal.
11. AMOS connects to the mail client and retrieves the mail. The system performs the updates to the
form, transferring in the vendors input.
12. The updated form is now available as usual in the Forms window.
195
25.3 SMTP Options
AMOS offers SMTP as a system for sending mail through e-- Business Direct portals, in addition to the
default system MAPI. While systems running MAPI might receive security messages to indicate that
mails are being sent on their behalf, SMTP systems do not receive these warnings and therefore do not
require any acknowledgements before mails can be sent. To enable the use of SMTP, set the portal setting
SendingMailProtocol value to SMTP (see section 25.1.6). Then set the remaining portal settings for
SMTP as appropriate and the system will send mail using this protocol. There will be no mails in the
sendbox, as the system will not connect to a users mailbox on this protocol. If MAPI remains set as the
default protocol, mails will be sent as before and the other portal settings for SMTP will be ignored.
25.4 Customisation
Users can configure the data to be retrieved on Portals, making the user in full control of the e-- business
portal driver. This allows full customisation of the content of the HTML documents, including the
presentation of the data and which data to include.
For example, with this functionality users can write an SQL statement in the configuration file as
required and AMOS will then produce the data in XML format inside the HTML file. Advanced users
can remove all the HTML tags and extract the XML data , saving it into a separate .xml file. This xml
file can then be used in other applications that are able to read .xml files, such as Microsoft Excel.
The users SQL might result in text containing RTF formatting, since the SQL can retrieve data from
several columns, the text might be a combination of RTF text together with TXT text. For example,
<TXT> + <RTF> + <RTF> + <TXT> - where TXT is normal text without rtf formatting and RTF is text
with RTF formatting. AMOS can remove all the RTF formatting in any sub-- string and provide a string
with all text in TXT format (classic) only.
25.5.1 HTML/XML
Setting the HTMLType definition to HTML/XML produces an HTML file containing an XML data
island. This requires JavaScript to be enabled within the browser and is only supported by Microsoft
Internet Explorer.
Adding an XML data island into the HTML file and then reusing the data within the same HTML files
is a concept defined by Microsoft and not adopted by other suppliers of web browsers. This has always
been supported by the AMOS e-- Business Direct portal driver; read about it in section 25.4. AMOS
allows you to define the content of the data island and allows you to reuse it in both Purchase Order and
Quotation type HTML files.
196
The presentation of the HTML file and its data can be customised using the Portal Settings POF
Template and RFQ Template.
Below is a sample of a data customisation file:
<?xml version=1.0 encoding=UTF-- 8?>
<ebusinessdirect>
<amos version=1 author=John Smith created=20080228 company=CompanyA>
</amos>
<purchaseorder>
<dataisland name=MyData>
<sql>
25.5.2 HTML/JSON
Setting the HTMLType definition to HTML/JSON produces an HTML file containing a JSON data
island. This requires JavaScript to be enabled within the browser and is supported by most major web
browsers, including Microsoft Internet Explorer.
Note When using the HTML/JSON option to generate HTML documents: when the supplier sends the
information, the email produced containing the information to be sent back is presented editable to the
user filling in the HTML page. No changes should be made to the content of this email, as this would
render the information useless.
197
Below is a sample of a data customisation file:
<?xml version=1.0 encoding=UTF-- 8?>
<ebusinessdirect>
<amos version=1 author=John Smith created=20080228 company=CompanyA>
</amos>
<purchaseorder>
<dataisland name=MyData>
<sql>
25.5.3 HTML/NoScript
Setting the HTMLType definition to HTML/NoScript produces an HTML file with no data island which
therefore do not rquire the web browser to execute any java script. This is supported by most major web
browsers, and does not require JavaScript to be enabled within the browser. The resulting HTML file
will not be expanded by any data island as in the two previous scenarios. Because this new format does
not contain any java script it is also readable on smart phones like Blackberries and iPhones.
For security reasons some users might switch JavaScript functionality off.
Note When using the HTML/NoScript option to generate HTML documents: when the supplier sends the
information, the email produced containing the information to be sent back is presented editable to the
user filling in the HTML page. No changes should be made to the content of this email, as this would
render the information useless.
198
25.5.3.1 Customisation: Data and Presentation
To produce HTML files of this type, all the necessary data is populated into Table Tags. This tells
AMOS where to insert the data in the HTML file. There are two ways to load data into the HTML file.
S Use the portal setting XML Configuration in combination with a template file specified in the
POF Template or RFQ Template portal settings. Or,
S Insert AMOS-- specific tags into the template file specified in POF Template or RFQ Template
with or without the use of the XML Configuration setting. To insert a tag with use of the XML
Configuration setting, be sure to define that portal setting, first. Note that AMOS is not case
sensitive regarding these tags, but due to HTML standards it is recommended to type
amostabledata and amoscolumnid in lower case.
amostabledata
This tag identifies the source of the data. Set it to either the same name as defined in the XML
Configuration file or, to an SQL select statement.
amoscolumnid
Within the SQL select statement there are one or more columns identified numerically - 1, 2, 3
etc.
The amoscolumnid tag identifies the column number of the SQL select statement already set in
the amostabledata tag. If that tag points to a name in the XML Configuration file, look for the SQL
select statement in that file. Otherwise, the amostabledata tag is the SQL select statement.
To insert a column in the HTML file, set the amoscolumnid tag to the numerical value of the
column in the SQL select statement.
Example: in the following SQL select statement, code is amoscolumnid=1 and name is
amoscolumnid=2.
SELECT code, name FROM address WHERE code LIKE j%
The order of the presented columns does not need to follow the numerical value of the column
ID.
The presentation of the HTML file and its data can be customised using the Portal Settings POF
Template and RFQ Template.
If your HTML file collects data from multiple sources - that is from several SQL select statements - all
the table tags must be contained within one main table tag.
199
25.7 System Parameters
A brief description of the system parameters which control the behaviour of AMOS e-- Business Direct
follows below.
The parameters are found at Tools > Configuration > Parameters > Options > General > Portal >
[Parameter Name].
Billing Address
The Billing Address parameter is where you define the code for the address where purchase invoices
should be sent. When you enter the Billing Address filter you will be presented with the Addresses
window from which you can chose the correct address. The chosen address will be shown as an eight
digit code.
Default value: Empty
Log Successful Portal Operations
Set to TRUE, the system will store successful portal operations in the portal log.
Default Setting: FALSE
Portal Line Item Reference Priority
If the value for this parameter is set to VendorRef, MakersRef the system writes the Vendor Reference
value into the XML file if both values are available. If only one of the two is available, that value is
written into the XML file. If this parameter is set to MakersRef, VendorRef the Makers Reference is
written to the XML file as the Identification value.
Default setting: MakersRef, VendorRef
Prevent Update of Quotation When One is Selected
When set to TRUE and a vendor is selected, the XML file will not be imported and will be renamed to
*.OnOrder. If set to TRUE and no vendor is selected, the XML file will be imported. Set to FALSE the
portal will import the XML file whether a vendor is selected or not.
Default setting: FALSE
Show Error Messages During Portal Export
This parameter, if set to FALSE, allows Portal Export to continue uninterrupted in the event of errors
occurring during export. Any errors encountered are written to the portal log and can be viewed later.
If the parameter is set to TRUE you will receive an error message each time an export error occurs and
further data export will be stopped until the error message is cleared by the user.
Default setting: TRUE
Show Error Messages During Portal Import
This parameter, if set to FALSE, allows Portal Import to continue uninterrupted in the event of errors
occurring during import. Any errors encountered are written to the portal log and can be viewed later.
If the parameter is set to TRUE you will receive an error message each time an import error occurs and
further data import will be stopped until the error message is cleared by the user.
Default setting: TRUE
Store Imported XML Document in Portal Log
This parameter, when set to TRUE, allows you to see the imported XML document associated with the
selected error message in the Portal Log, accessed via the Options menu. If set to FALSE, there will be
no Options menu available and no XML documents will be stored.
Default setting: FALSE
200
Chapter 26 Transaction Codes
Transaction Codes can connect expenses to a specific budget dimension, such as Responsible or Project.
The codes themselves are not directly connected to the budget.
To activate and use Transaction Codes:
1. Define the Transaction Code parameters, then
2. Open the Transaction Codes register to enter values for the defined codes.
These Transaction Codes and their set values will then become available for selection within the system.
3. Select a Level and use the lookups to assign a status, either globally or by installation/department.
There are three possibilities:
- Mandatory - every transaction must have a value for this code
- Optional - up to the user
- Not Used - this code is not in use
201
Figure 167 The Dialog Box for Transaction Codes
4. Next, select the Label parameter for the same Level. Enter a name to identify the transaction code
level by. Codes belonging to this level will be identified with the label you provide. For example,
Responsible or Project.
5. Save your work before exiting the window.
1. Select the transaction code label to enter values for from the drop-- down list.
2. Click the New button to get a blank line.
3. Enter a Code and Title for the transaction code. For example, select the label Responsible, and
enter the initials and names of the people assigned as responsible for various projects.
4. Create as many transaction codes for the selected label as required. These codes will have the
status defined for the label in the parameters window.
5. Save your work before exiting the window.
202
26.3 Applying Transaction Codes
Once parameters are set and the code values defined, the transaction codes become available for use
throughout the system.
For example, the Components window Options menu contains the item Transaction Codes. Selecting
a Component in the list and then choosing Options > Transaction Codes opens a new dialog showing
the Transaction Code Labels you defined in the Parameters window. Next to each one is a drop-- down
list, containing the Transaction Code values you defined for each label, in the Transaction Codes register.
The codes you select here will then apply by default to subsequent transactions involving this component
and the related expenses will be linked to the appropriate budget dimension. So, when a user opens the
In/Out of Stock window and takes a part in or out against this component which has default transaction
codes applied, those codes will appear in the In/Out of Stock window.
203
Chapter 27 Templates and Form Designer
Various documents used in AMOS Business Suite can require different layouts. Creating Templates
provides the ability to customise the presentation of the Details tabs/Full Description windows found
throughout AMOS Business Suite. When a template is selected in a particular window, the user will then
be presented with a form that may contain drop-- down lists, selection boxes, input fields and other
controls, upon opening the Details tab/Full Description window. Using a template, the Details tab/Full
Description window is given the appearance of a specialised input form (otherwise the tab is simply a
blank page for free-- entry text).
There are two types of templates: Basic and Enhanced. A basic template can be converted to an enhanced
one. While the two types of templates look the same and show the same data entry fields, enhanced
Templates create custom tables in the AMOS database upon conversion. Custom tables provide better
analysis and trending capabilities than the standard BLOBs which basic templates store all data in.
To make and use a new template, a user creates a form definition (in PowerBuilder terminology this is
called a DataWindow), and saves it in a PowerBuilder library file with the file extension *.pbl. The name
of the file and the name of the datawindow are optional, though a good practice would be to prefix the
object with d_ (for datawindow), for example d_mytemplate. Form definitions can be created using
PowerBuilder, or using the Form Designer in AMOS. The datawindow is imported into the Template
Register and connected to a Template Code and Description. It is then called a Template. Once a template
is imported into AMOS from the library file, the .pbl file is no longer required. However you may wish
to archive the file for future modifications etc.
Templates are usually attached to Details tabs/Full Description windows via Edit > Change Template.
However, a template can be attached automatically on creation of a new table entry, by setting a default
parameter.
204
Figure 169 The Templates Register
Note In the event that an existing template is out of use, check the Obsolete checkbox to remove it from
drop-- down lists in the system and prevent future selection and use of that template.
The window opens to a new blank form. To open and edit an existing form, go to Options > Open Form.
You can then select an existing PowerBuilder Library file (*.PBL) to read in an existing template and
modify.
Note Data registered with a standard template in AMOS is stored in a comma-- separated format in so-- called
BLOBs (Binary Large OBjects) in the database. This means that the data from the form is transferred
to the database in the defined field sequence. If the field sequence is changed, data will be displayed
incorrectly to the user. Therefore, once a form has been used to input data, do not change it.
Use the right side of the window to create and place objects on your template. Once you click on the right
side, the form is activated and more tabs are added. These tabs, the fields and the information displayed
in the left side of the window will vary depending on the object selected or inserted in the template. Read
about the types of objects you can insert in section 27.3.2.
The General tab contains information such as the Name of the object, the Tag, the visibility and the way
it is displayed: for example, background Colour and Height. Checking the Autosize Height box
automatically sizes the height of the window according to the fields you add.
The Position tab allows you to define the exact position where an object is to be placed in the template.
Keep in mind that if the Moveable and Resizeable boxes are checked, this gives any user the option to
move and resize the object in the form within the window where it is in use as a template.
205
The Font tab is for defining the properties with regards to the font.
The Format tab is for defining the mask of a column.
The Edit tab is for defining the input and display properties of a column object. For example, when
adding a free-- text field to a form, you can add a horizontal scroll bar by selecting the column and then
checking the Auto Horz and Horz Scroll Bar boxes.
When you finish working with a form, always save it. There are two ways to do this:
S Options > Save Form - saves the modifications to the template in the Library file it was
originally stored in (in the case of an existing form).
S Options > Save Form As - allows you either to choose another existing Library file or to create
one by defining the name of an non-- existing Library file. After either selecting an existing library
file, or defining the location and naming a new library file, you will be prompted to register a name
for the template with which it will be available in the Library file. Read more about Library files
in section 28.3 of this guide.
Select the Type, and enter the Length and Decimal value if required. To access this dialog later to change
the column definition, either double-- click the column, or select it and go to Options > Edit Column
Type.
Selecting Options > Tab Order displays a list of all the columns you have added to the template and
allows you to define the tabbing order for these columns: setting values here defines the order in which
users will access these fields, when pressing the Tab key.
One column is present in any form by default. Select it to see its properties on the left: its name is table_id.
Do not delete this field, as it is required. To prevent it appearing on the finished form select it and then
in the left side of the window, uncheck the Visible checkbox. Then adjust the tab order value for this field
to 0. This will hide it from the users view when the form appears in a Details tab.
206
S Text places a text label on the template.
S Picture opens a browse dialog allowing you to select an image to insert in the template.
S Group Box draws a group box.
S Line draws a line.
S Oval draws an oval.
S Rectangle draws a rectangle.
S Round Rectangle draws a rectangle with rounded corners.
S Column inserts an input field, as discussed in section 27.3.1. The following types are supported:
string
number
decimal
date
datetime
time
long
ulong
S Computed Field adds a computed field, or a field that performs calculations. After adding one,
place and size it on the form and then click the lookup button in the left side of the window next
to the Compute Expression field. This opens the Select Expression window. Add column names
and operators to retrieve a computed value. Click the Verify button to check the validity of the
expression.
207
6. Select the definition and click OK to import it.
Once the connection between the template and the form definition is established, the form is available
as a template and can be linked to Details tabs/Full Description windows throughout the system.
Use the fields in the lower part of the Convert Template dialog to enter the details that will be applied
to the new template. The Code will initially be the same as the existing template and so you must alter
it to preserve uniqueness. The Description is inherited from the existing template and can be re-- used
if required, this does not need to be unique.
Enhanced templates enable the creation of user defined table names used to store the values entered in
the form at a later date. This requires that you specify a Table name for database storage purposes. The
name can not include spaces, you will be prompted to accept underscores if you attempt to do so. Click
OK to continue with the conversion and a table will be created in the AMOS database with the Table
name provided.
During conversion you need to specify the Export DBMS to be used. This establishes the Database
Platform used at the receiving installation during export, ensuring that the correct syntax is provided
to create the table in that database.
On returning to the Template register, the Enhanced column value for this template will reflect the
conversion.
Note A check is performed during conversion to determine if the selected template is attached to a register.
If this is the case, a warning is displayed and the obsolete checkbox must be unchecked.
Note If AMOS Replication is installed you will be prompted to create a replication rule for all new user defined
tables associated with enhanced templates.
208
27.5.1 Access Rights --- Defining Sections
Once you have created an enhanced template, you can limit access to it so that only certain users can
fill out certain fields.
This is one of the defining points of enhanced templates. When a template is converted, the resulting form
can be divided into sections. Sections are defined by the keyword AMOS_SECTION=# (where # is the
section number) in the Tag property of each of the fields when designing the form. This defines the
section to which each field belongs. Each section can then be given read and edit access rights for any
registered group within AMOS. This feature adds a dynamism to the form that means certain users can
only edit data in predetermined areas whilst being able to read other areas. Other users may be prevented
from reading certain areas entirely. If access to a section is undefined, any group can edit it.
Start by editing the enhanced template to create access sections:
1. Open the Template register at File > Open Register > General > Templates. Inside the Template
register go to Options > Form Designer, and then in the Form Designer go to Options > Open
Form.
2. Select the form to open.
3. Select a column and then type a section definition for that column, into the Tag field. For example,
AMOS_SECTION=1.
4. Continue to group the columns into sections by defining the section number in the Tag field for
each column.
Now, assign access by user groups for each of the defined section numbers. See section 27.6 for more
about this step.
209
5. Add as many groups as necessary, and then continue to the next section.
6. When you are finished, Save your settings and close the window, to return to the Templates
register.
210
Figure 176 Changing/Adding a Template
A warning message appears telling you that if you change the template then any information
already in that Details tab will be displayed incorrectly.
3. Click OK to open the Select Template dialog and change the template or Cancel to close the
message box and halt the process.
4. Save the changes.
211
Chapter 28 Layouts and Reports
Several of the AMOS Business Suite registers contain a Details Tab or a details window called Full
Description (accessed via the Options menu). You can create layouts -- also called Templates -- to make it
easier for users to enter the correct data in such fields in a faster and more efficient way.
There are a number of pre--defined reports that present data about components, stock items jobs etc. You
can create new, user--defined reports for your organisation using PowerBuilder or InfoMaker from
PowerSoft.
212
28.3.1 Creating a Database Profile
The first time you use PowerBuilder it is necessary to define a database profile.
Note In PowerBuilder, always use the amos user.
To define a database profile:
If you receive an error message while you are trying to connect to the database, a ConnectString
must be defined:
1. In the Database Profile Setup shown above, click More>> to expand the dialog box.
2. In the field DBPARM, enter the following:
ConnectString=DSN=Amos
3. Click OK to connect to the database.
213
S In PowerBuilder, you can get an overview of the various .Pbl files for the application in a Library
window. This resembles the Explorer program in Windows 95. This option is not available in
InfoMaker.
In PowerBuilder, click the Library button to get a graphical representation of the .Pbl files in the
application:
214
Figure 179 The Create Library Dialog Box
28.4.1 Layouts
Below is a description of the steps involved in the process of creating a layout to be used in a Full
Description field:
1. Start PowerBuilder and double--click the Library icon for the library in which the layout is to
be stored.
2. Click the Datawindow button to open the Select DataWindow dialog box, and click New to
create a new data window.
215
Figure 180 The Select DataWindow Dialog Box
3. In the New DataWindow dialog box, select External in the Data Source area of the dialog box and
Freeform from the Presentation Style area.
216
Figure 182 The Result Set Description Dialog Box
7. When you have added the elements to be used in the layout, click OK to display the data window.
Note You can add new elements to the layout later, so it is not absolutely necessary to add all the layout elements
at this point.
8. Click Save to name the layout and save it in the currently open library file.
9. Use the available design tools to format and design the layout, and remember to save the layout at
regular intervals during the process.
A description of some of the design functions available is included in section 28.4.3.
10. Use AMOS to connect the created layout to a Template definition, as described in section 28.5.
217
28.4.2 Reports
Once the AMOS Business Suite has been set up and operating in your organisation, its database will contain
large amounts of useful data. A number of pre--defined reports have been created in order to present data
from the database.
It is also possible to tailor new reports to extract and display data from the AMOS database. Once a new
report has been created, you can add it to the report hierarchy, and use it the same way as the pre--defined
reports. The process of adding a user defined report to the report hierarchy is described in section 28.6.
Here is a description of how to create a new report:
1. Select the .Pbl file in which to store the report, and click the Data window button in PowerBuilder
or the Form button in InfoMaker.
Figure 185 The Data Window Button (Left) and the Form Button (Right)
The New Form dialog box in InfoMaker contains fewer options but the ones you need for your
reports are available.
3. Select SQL Select as Data Source and Freeform as the Presentation Style/Form Style.
4. Click OK.
The Select Tables dialog box is displayed.
218
Figure 187 The Select Tables Dialog Box
5. From the list of tables, select the one you want to use, and click Open.
You can select multiple tables and define necessary join relationships between them in order to
create complex reports. It is beyond the scope of this manual to describe such reports.
6. Select each column in the small table window in the middle.
As you do, the column names appear near the top of the window, below the title bar, as shown in
Figure 188.
7. Click the SQL button , which by now should be depressed, and it will appear to come back out
when you click it.
Finally, it is time to edit the actual report. The screen now looks something like this:
219
Figure 189 An Advanced DataWindow View
Note When you make a new report, AMOS Business Suite and PowerBuilder might be working on the same
library. Unfortunately, this can cause conflicts and you will not be notified about them before you try to
save your changes. Save the report at this point, before too much work has been put in it. See the next
section. Then start designing the report.
220
Figure 190 The Important Toolbar Buttons
Use standard Windows techniques to design the report/layout. For example, you can drag an object to a
different position and drop it there. Use the buttons in the toolbar shown above to select alignment, colour
and other object properties.
It is fairly simple to interpret the function of each individual icon and what effect it will have on the selected
objects. If in doubt, let the mouse pointer rest on a button for a short while. A tool tip will appear, informing
you about the function of that icon.
221
Figure 192 The Text Object Properties Window
Use the tabs to enter or edit properties for the selected object. In the example above, the Text field on the
General tab is for changing the actual text of the field. The Font tab is for setting font, size and other textual
properties, etc.
The properties window for Column Objects looks like this.
It is beyond the scope of this manual to describe all the possibilities InfoMaker and PowerBuilder offer:
refer to the relevant documentation or online help for more information. However, here are some tips about
the functions available on the different tabs:
The Edit Tab
222
Use the Edit tab to make different presentation styles, such as dropdown lists, check boxes and
radio--buttons. Edit masks force the user to type data in a special format (for example a telephone number
or a date, described in the next section).
The Validation Tab
Use the Validation tab to test the legality of the data the users type in. For example, you can make certain
that a number is always positive.
The Expression Tab
The Expression tab is the most complex: It makes it possible to change the colour of the text depending
on what is typed. For example, negative numbers can be displayed in red. Certain fields may be made
invisible.
If your main concern is with the appearance of a report/layout, it is probably sufficient to manipulate items
on the General and Font tabs. Use the Position tab to specify the exact position of an object. Other
properties require a deeper knowledge of PowerBuilder, InfoMaker and database applications, and such
topics fall beyond the scope of this reference manual.
223
To insert a picture, for example a company logo, click the Picture button and draw the location for the
picture. A dialog box to specify the file name of the picture opens.
Click Browse to find the picture file, locate the correct folder, select the file to use and click OK twice to
return to the report/layout.
Note For such a report/layout to work properly at the site, ensure that the picture file is available on the PC where
the report is to be used, and that it is located in the specified folder.
224
Figure 195 The Import Definition Window
To read more about working with Templates in AMOS, and about creating them in the AMOS Form
Designer window, see Chapter 27 in this guide.
225
28.6.1 Add the Report to the Hierarchy: the Reports Menu
To include a user--defined report in the Reports window hierarchy:
1. Select Tools > Configuration > Extension Features > Reports Menu.
The Reports Menu window for user--defined reports opens, with a hierarchy on the left side.
In the example above, the item My own reports has been added to the hierarchy. The item contains
the two sub--commands Label reports and Utility reports, and the former contains the actual report
called Tag stickers. The section below explains how this is added:
2. Click the New button on the left--hand side of the secondary toolbar to insert a new record. Use the
dialog box that opens to choose the type of object to create:
3. Select whether to create a Top--level menu, a Sub--level menu or a Report, and click OK. If you
select to add a menu item, a new folder appears in the tree structure where the cursor was located.
To change the name, click in the name field and type the name to use.
When you insert a Report in a menu or a sub--level menu, a report icon appears in the tree structure.
4. Name the report by clicking in the name and typing in the desired name. Use the tabs to the right
in the window to specify more information about the report.
5. Click the lookup button to the right of the Library Filename to locate the folder where the report
definition is stored. Use a library file with the file extension .Pbl or .Pbd. If you select a library file
stored in the Report directory (see section 15.4), only the file name is used in the field. If the file
is stored elsewhere, the full path name of the library file is used.
S If a library file of the type .Pbd is used, the functions in AMOS cannot list the contents of the file.
This means you must manually fill in the fields Window Name and Datawindow Name without
using the lookup buttons.
6. Name the window to display the report in the Window Name field. The field is optional.
7. The Datawindow Name field is for the name of the data window of the report, and must be filled
in. Click the lookup button to see a list of available windows in the selected library. Select one to
get access to the last field on the tab.
226
Modify Strings
You can set up the AMOS Business Suite to make modifications on a report when it is run.
S Use the Modify String field to specify editing and display masks. For example, specify that the
report should use the number mask defined in the system. This is done on the Auto--Numbering tab
described in section 15.2.
S These are the mask names and the corresponding modify strings that you can use:
Component Number Mask #CompNoFormat#
Form Number Mask #FormNoFormat
Function Number Mask #FuncNoFormat#
Stock Item Number Mask #PartNoFormat#
Transport Number Mask #TransDocNoFormat#
Work Order Number Mask #WONoFormat#
Note The Modify String text is case sensitive.
When you specify a mask, enter the name of the field in the data window where the modification
should be applied. The same applies to the property of the field that should be changed. For example,
a data window called d_test may contain a column field called formno. This shows the form number
associated to a Purchase Order. This makes it logical to display the number with the mask defined
in the system. Enter the following value in the Modify String field:
S formno.format=#FormNoFormat#
This tells AMOS that the field property of the formno field is the mask defined as the Form Number
Mask.
S Define an edit mask for query data windows for when the user enters numbers in a field. The
property is called editmask.mask. If you have a number field and want it to use the Form Number
Mask, use the following field value:
-- formno.editmask.mask=#<Xxxx/No>#
It is possible to define multiple text strings in the Modify String field by separating them with
spaces.
The Query Tab
The Query tab is for specifying an optional filter window. The tab contains the same fields as the
Report tab.
The Misc. Tab
The Misc. tab contains the two optional fields User Defined Fields and User Defined Table. Use
the field Printer Task to specify a printer task to be executed for the report. See section 28.6.4 about
Printer Tasks.
227
5. Click Save and close the Module Contents window to return to the Access Modules window.
6. Click Save in the Access Modules window and close the window.
It is necessary to grant the relevant user--groups access to the reports in the access module. This is done
in the Access Control window. See the next section.
5. Check the Execute checkbox beside the Custom Reports entry to allow the selected user group
access to the reports in the access module as listed in the Module Contents window.
6. Save before exiting the window. The user--defined report(s) will now be available to users with the
correct access, from the Tools > Reports window.
After you save, the selected group has the necessary access and will be able to see the report(s) listed in
the Reports Browser, as well as preview and print it.
228
Figure 200 The Reports Menu Window -- Misc. Tab
To create the tasks that will appear in the drop--down list in the Reports Menu window Printer Task field:
1. Select Tools > Configuration > Printer Tasks to open the corresponding window. Give each task
a name, and add a comment describing the task further:
2. Save the named Task. The Options menu becomes active. Go to Options > Printer Task
Configuration to open the Task Configuration dialog.
3. If no printer names appear when you open the drop--down list in the Identification field, select
Options > System Printers (in the Task Configuration window) for AMOS to add the printer
definitions available on your PC into its own database.
AMOS imports the necessary information in a few minutes. After the process is completed, you can
select the desired printer from the drop--down list.
S The Comments field is optional, you can use it to describe the selected printer.
S Use the Copies field to specify how many copies to print in the selected printer task.
S Click the lookup button next to the Paper Source field to get a window to select the paper source.
This window displays the defined paper sources in the selected printer.
4. Save the window and close it to return to the Printer Tasks dialog.
229
Chapter 29 Custom Logon
It is possible to customise the Logon and About screens to display pre-- defined bitmaps. Your licence
file needs to be adjusted to support this functionality and it is only activated on a case-- by-- case basis
under a special distribution agreement.
Custom Logon and About images can only be changed if the value for SystemType in the license file
is >=10.
Option A
The files should be stored in the folder defined as the InstallationDirectory in the parameters. The
filenames are logon##.TYP and about##.TYP, where ## is the SystemType as registered in the license
file (SystemInfo.SystemType), and TYP is either the extension gif, jpg or bmp (they will be scanned for
in that order).
Option B
As the Logon and About windows contain some controls such as username and password fields, ok and
cancel buttons, and text, there is an additional solution to define the logon image and the position of the
controls within the window.
The positions are relative to the left top hand corner of the Logon and About windows (coordinates 0,0)
and the positions of the controls are relative to each other and cannot be influenced.
Register the following in the AMOSW.INI file to use this solution:
[Customisation]
LoginControl_x=
LoginControl_y=
LoginPicture=
AboutControl_x=
AboutControl_y=
AboutPicture=
Where LoginControl_x, LoginControl_y, AboutControl_x and AboutControl_y define the coordinates
to place the controls in the respective windows. The LoginPicture and AboutPicture parameters allow
you to define the folder and name of the image for use in the Logon and About windows.
230
Index
A Component Classes, 38
Component transfer, 148
Access, reports, 228
Component Types, 70
Access Control, 112
Components, 37
Account Codes
Condition Based Maintenance, 182
categories, 76
Configuration
configuration, 76
cost centres, 75
Account Transactions, 32
depreciation levels, 62
Accounting, parameters, 122
stock grade categories, 62
Accounting module, 32
transaction codes, 201
Accumulators, 60
workflow, 151
Activity, 54
Contract Leave Days, 57
Addresses, 20
Copy, 20
options menu, 22
Copyright, ii
products tab, 21
Cost Centre Access, 111
Airport, 59
Cost Centres, 32
Alert Groups, 165
configuration, 75
Alerts Overview, 6
Counter Types, register, 28
Attachment, 48
Countries, register, 33
open in new window, 134
Country Regions, tab, 33
references, 49
Create Component Job, 37
sources, 48
Create Component Type Job, 37
Audit Trail Configuration, 78
Crew Effect Type, 59
Auto--numbering, 118
Crew Member Document, directory, 121
create new rules, 119
Criteria, 40
Currency Codes, register, 29
B
Currency Rates, 23
Bank Register, 60 register, 23
Bargain Agreement, 60 Currency Rounding Register, 60
Berth Type, 34 Custom Logon, 230
Best Practice Guidelines, 86 Customise toolbars, 8
Boundaries, 86
Budget, parameters, 122 D
Budget Codes, access, 111 Dashboard, 5
Dashboard Themes, 6
C Database, 18, 212
Calendar, 17 create a profile, 213
Cargo Attribute Type, 53 datawindow, 204
Cargo Group, 53 Day--Files, 185
Cargo Type, 53 Default, templates, 120
CBM Default Template, 210
directory, 121 Delay Activity, 53
references, 184 Delay Reason, 53
status definitions, 183 Deliveries
Change template, 120 locations, 47
Change Workflow Status, window, 157 terms, 46
Claims, 53 Depreciation Levels, configuration, 62
Classes, 41 Design, window, 220
Closing a Window, 10 Directories, 121
Column Ordering, 13 CMB, 121
Column Sorting, 13 crew member document, 121
Company, 54 graphics, 121
231
hand terminal, 121 register, 25
installation, 121 Global access, 109
personnel report, 121 Graphics, directory, 121
reports, 121
transfer, 122 H
Disability Grade, 57 Hand Terminal
Disciplines, register, 27 directory, 121
Disclaimer, ii, xi reader, 133
Document Templates, 51 Hand terminal, file extension, 129
Hand Terminal Interface
E application, 84
Edit and Options Menus, 15 business suite, 84
Edit Formula, 61 file format, 83
Editor, parameters, 127 file sample, 84
Element, adding new, 89 Hand Terminal Reader, read file, 84
Emergency Response System, 53 Hardware Components, 1
Employee, 22 How To
options menu, 23 Change the Template Used in a Tab,
Employee Address Type, 57 210
Employee Details, 59 Define the Default Template for a Tab,
Evaluation Criteria, 55 210
Evaluation Grade, 55
I
Event Type, 54
Exiting, 10 Import, 66, 67
Export, 66, 67 log, 73
log, 72 portal log, 73
portal log, 73 task server, 65
task server, 65 tasks, 64
tasks, 64 Import Log, 73
Export Log, 72 Infomaker, a brief introduction, 212
Extension Features Installation, directory, 121
access modules, 177 Institute, 57
modules menu, 176 Insurance Categories, 53
External viewers, 48
J
F Job Class Access, 111
Job Classes, register, 30, 36
Family Relation, 57 Job Description Revisions, 36
Fields Job Descriptions, 51
moving and aligning, 221 attachments, 37
properties, 221 components, 37
File create component job, 37
export, 66 create component type job, 37
print, 18 maintenance log, 37
printer setup, 18 move job references, 37
File Extensions, parameters, 129 options menu, 36
File Format, hand terminal interface, 83 permits to work, 37
Format Masks, 223 register, 35
Forms, inserting new objects, 223 Jobs, CBM, 182
Function Criticality, 38 JSON, 197
G K
General Key Performance Indicators (KPIs), 85
parameters, 124 KPI, adding new, 90
232
L Allow User Defined Impact on
Layouts, 212 Purchase Budget, 122
designing, 215 approval required for stock transfer,
making and using, 212 145
Leave Days, 55 ask user to confirm deletions, 132
Locations, 23 auto inheirit counters, 136
registers, 23 auto--calculate form estimate, 141
Lock Application, 10 auto--file completed CBM work order,
Lock/Unlock, 156 135
Log Tab, vessel details, 25 auto--file completed corrective action
Logon, 4 work order, 135
Look--up Filters, 12 auto--file completed periodic work
order, 135
M auto--file completed requisition work
Mailbox, access log, 105, 158 order, 135
Maintenance auto--file completed round work order,
condition based, 182 135
parameters, 135 auto--file controlled CBM work order,
register, 35 135
Maintenance Log, 37 auto--file controlled corrective action
Manning Agents, 55 work order, 135
Marital Status, 58 auto--file controlled periodic work
Menu Bar, 7 order, 136
Move Job References, 37 auto file controlled requisition work
order, 136
N auto--file controlled round work order,
Non Conformity, 51 136
cause, 52 auto--file fully received form, 141
severity, 52 auto--fill delivery details, 141
type, 51 auto--numbering, 118
NoScript, 198 auto--set budget date, 141
Notifications, 6 auto--update multi--vendor from line
item, 141
O auto--update stock details from line
Obsolete, 26, 205 items, 141
Options, 122 autofilter WO by discipline, 136
general tab, 98 automatically reschedule work orders,
views tab, 99 136
Options Menu, 15, 16 base currency code, 132
addresses, 22 billing address, 129
employees, 23 budget, 122
job descriptions, 36 budget at line item level, 122
Oracle, 70 budget code status, 125
Order Priority, 46 budget for component job, 125
calculate estimates for component jobs,
P 136
Parameters classic editor font, 127
account code type for maintenance, 122 clean up for component in stock
account lockout threshold, 131 wanted, 141
accounting, 122 close quotation after query select, 142
address format, 140 commodity purchase, 142
allow negative value of counters, 136 Compatible To Version, 125
allow removal of more items than in component search range in order lines,
stock, 145 142
233
component search range in stock > initial requisition work order status,
wanted, 146 126
create component archive on transfer initial round work order status, 126
in, 133 interface, 118
create log--in audit trail, 131 Interrupt Approval Warning Limit
create new form on form conversions, Adjustment, 123
142 Job Description Revision Control, 137
current installation, 133 leave days -- 30 days deduction, 140
default preference when reporting level of approval, 143
work, 137 Limit Global Search to Departmental
default status on component transfer, Access, 133
125 limit stock types selection on required
default templates, 120 parts on work orders, 134
Default Value Mark Work as list all transfer documents, 146
Completed, 125 locations for stock items, 126
default value quotation update stock lock ordered form fields, 143
item field, 125 lock approved purchase orders, 143
default wage type, 139 lock approved requisition forms, 143
delete component archive on transfer lock completed voyages, 147
out, 133 lock discharged cargoes, 147
depreciation level, 125 lock exported requisition forms, 143
directories, 121 lock planned port calls, 147
Edit Stock Item Currency and Price on lock planned voyages, 147
Required Parts, 133 lock sailed port calls, 147
editor, 127 log counters for non--counter based
employee number sequence max, 140 jobs, 137
employee number sequence min, 140 log job rescheduling, 137
enforce complex password, 131 log work with employee, 137
enforce password history, 132 maintenance cost account category, 126
file extension for export files, 129 maintenance, 135
file extension for hand terminal files, maintenance log modification warning,
129 137
file extension for import files, 129 max size (kB), 128
file extension for successfully imported maximum password age, 132
files, 129 minimum password length, 132
file extensions, 129 month--end close period (days), 123
financial year early start, 123 multiple departments in order forms,
form generic queue field, 142 144
form status after query select, 142 open attachments in new window, 134
form type, 126 options, 122
form type after query select, 142 output format for new job related to
general, 124 components, 126
hand terminal reader, 133 output format for new rounds, 127
hide inaccessible menu entries, 133 output format for work requisitions,
ID number series, 133 127
IMOS installed, 147 password backward compatability, 132
import cargo group, 147 payroll, 139
inheirit full description from parent, payroll calculation period, 139
146 payroll currency code, 139
initial CBM work order status, 126 payroll current period, 139
initial corrective action work order personnel, 140
status, 126 portal line item reference priority, 129
initial periodic work order status, 126
234
printer task to use when printing labels, track stock expenses, 123
134 track stock transactions, 122
priority for new job related to transaction codes, 148
components, 127 type common, 128
priority for new rounds, 127 type maintenance, 128
priority for work requisitions, 127 type personnel, 128
propose work order required parts, 146 type purchase, 128
purchase, 141 type quality, 128
record stock usage when reporting type voyage, 129
work, 146 unassigned cargo departments, 147
reload DDDW when opened, 134 use 9 digits for PK counters, 134
Remote Workflow, 130 Use Budget Control When Approving
report history by default, 138 Forms, 123
report resources by default, 138 use component types, 135
report stock usage by default, 138 Use External Budget Figures for
report work, show component parts, Budget Approval Warning Levels, 123
138 use latest delivery date of order lines,
require estimated cost for approval, 144 144
require reason for job rescheduling, 138 Use Maintenance Task, 139
reset purchase counter on financial use quotation discount given, 144
year, 144 use specification for purchase budget,
restrict original PO printing, 144 124
restrict replanning of started work use specification for stock budget, 124
orders, 138 use specifications for maintenance
restrict work flow assign to values, 134 budget, 124
seconds between each CBM check, 138 use stock class access, 147
set date automatically during receipt, use stock item depreciation, 147
144 use stock types, 135
sharing, 148 use vendors price, 144
show account number, 139 use voucher to update forms details,
show bargain agreement, 139 124
show company code, 140 use work flow, 139, 144
show currency code, 140 user defined fields, 149
show employee first name, 140 validate order form dates, 145
show employee surname, 140 view counter from functions
show error messages during portal perspective, 139
import, 130 voyage, 147
show from date, 140 work order tracking accuracy, 139
show rank code, 140 working day length, 135
show status codes, 140 Password, 106
show vessel code, 140 Payment Terms, 47
single window instance, 134 Payroll, parameters, 139
start date for financial year, 123 PBL, creating a file, 213
start in department, 134 pbl file, 204
status for new components, 127 Period Register, 59, 60
stock, 145 Permits to Work, 24, 37
stock price logged, 146 register, 24
stock reservation trigger, 138 Personnel, 54
store documents in the database, 140 activity, 54
Track Custom Clearance Expenses, 123 airport, 59
track maintenance expenses, 123 category, 57
track maintenance transactions, 122 company, 54
track purchase expenses, 123 contract leave days, 57
track purchase transactions, 122 disability grade, 57
235
employee address type, 57 Register
employee details, 59 account codes, 31
evaluation criteria, 55 addresses, 20
evaluation grade, 55 attachment, 48
family relation, 57 berth types, 34
institute, 57 causes, 42
leave days, 55 claims, 53
manning agents, 55 classes, 41
marital status, 58 component classes, 38
parameters, 140 counter types, 28
rank, 55 countries, 33
rank type, 55 Crew Effect Type, 59
sailing period, 58 currency codes, 29
ship category, 55 currency rates, 23
sickness, 58 delivery locations, 47
sickness nature, 58 delivery terms, 46
sickness type, 58 disciplines, 27
standard document, 58 document templates, 51
standard document type, 58 employees, 22
termination reason, 59 function criticality, 38
trade, 55 general, 25
trade union, 59 job classes, 30
vessel, 56 job description, 35
vessel characteristic type, 57 job descriptions, 51
vessel department, 57 job triggers, 30
Personnel Report, directory, 121 locations, 23
Portal Log, 73 maintenance, 35
Ports, register, 34 Non Conformity, 51
PowerBuilder, 26, 204, 212 order priority, 46
a brief introduction, 212 payment terms, 47
Predefined Fields, 100 permits to work, 24
Price Classes, 45 personnel, 54
Print, 18 ports, 34
Printer Setup, 18 product types, 28
Product Types, register, 28 purchase, 46
Products Tab, addresses, 21 QA grades, 31
Project Categories, 39 quality codes, 29
Purchase, 46 quality procedures, 51
parameters, 141 receipt status, 48
stock, 44
Q stock classes, 44
QA Grades, register, 31 stock grades, 31
Quality Codes, register, 29 templates, 26
Quality Procedures, 51 transfer reasons, 45
categories, 51 types, 41
document templates, 51 units, 29
job descriptions, 51 vessel details, 24
job triggers, 30 vessel types, 30
Voyage Management, 53
R world regions, 32
Rank, 55 Reports, 212
Rank Type, 55 directory, 121
Receipt Status, 48 granting access, 228
References, CBM, 184 saving, 220
236
working with, 212 Trademarks, ii
Reschdule Limits, 40 Transaction Codes, 201
Response, 53 parameters, 148
Revision Transfer of Mailbox Contents, 105, 158
self assessment, 85 Transfer Reasons, 45
self assessment parameters, 85 Transfer, directory, 122
Type, 51
S Types, 41
Sailing Period, 58
Saving Data, 10 U
Selection File Commands, 67 Units, register, 29
Self Assessment User Defined
continuing, 86 fields, 149
revision, 86 parameters, 149
Self Assessment Parameters
Elements, 88 V
KPIs, 88
Vessel, 56
Self Assessment Statistics, 87
Characteristic Type, 57
Severity, 52
Department, 57
Sharing, parameters, 148
Vessel Details, 24
Ship Category, 55
log tab, 25
Ship Store Type, 59
register, 24
Shortcut Keys, 9
Vessel Types, register, 30
Sickness, 58
View, PSR reports, 82
Sickness Nature, 58
Views, save, 99
Sickness Type, 58
Voucher, 48
Slopchest Departments and Locations, 59
Voucher Category, 48
Software Components, 1
Voyage, parameters, 147
Sorting, 13
Voyage Management, 53
Sources, 48
cargo attribute type, 53
Split Scrollbars, 14
cargo group, 53
Standard Document, 58
cargo type, 53
Standard Document Type, 58
delay activity, 53
Standard Toolbars, 8
delay reason, 53
Stock, 44
event type, 54
parameters, 145
Stock Classes, 44
W
Stock Grade Categories, configuration, 62
Stock Grades, register, 31 Wage Scale, 60
Sub--Element, adding new, 90 Wage Type Register, 60
What is a Filter?, 11
T Why do I Have to Logon?, 4
Tab Order, 224 Window Refresh, 10
Task Server, 65 Window Toolbar, 8
Templates, 15 Windows
default, 120 change workflow status, 157
register, 26 designing reports and layouts, 220
Termination Reason, 59 Workflow, configuration, 151
Text Object, 221 World Regions, register, 32
Tools Menu, view PSR reports, 82
Trade, 55 Z
Trade Union, 59 Zoom, toolbar button, 82
237
Notes
238
239