AMOS User's Guide
Code Transfer
Administration / Database Access
24.6
Swiss Aviation Software Ltd.
Code Transfer
Copyright Notice
Copyright © by Swiss AviationSoftware Ltd.
All rights reserved
The software contains proprietary information of Swiss AviationSoftware Ltd.; it is provided under a
licence agreement containing restrictions on use and disclosure and is also protected by copyright law.
Reverse engineering of the software is prohibited.
Due to continued product development this information may change without notice. The information
and intellectual property contained herein is confidential between Swiss AviationSoftware Ltd. and the
client and remains the exclusive property of Swiss AviationSoftware Ltd. If you find any problems in
the documentation, please report them to us in writing. Swiss AviationSoftware Ltd. does not warrant
that this document is error-free.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form
or by any means, electronic, mechanical, photocopying, recording or otherwise, without the prior
written permission of Swiss AviationSoftware Ltd.
Swiss AviationSoftware Ltd.
P.O. Box
4002 Basel
Switzerland
Tel.: +41 (61) 582 4020
Website: www.swiss-as.com
Page 2 of 13
Code Transfer
Contents
Copyright Notice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Code Transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
User anonymisation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Buttons. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Search, Workspace and Display sections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Disclaimer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Code Transfer related licences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Change user sign codes licence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Change station code licence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Change vendor code licence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Change AC-registration code licence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Change part number licence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Change aircraft type licence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Change currency code licence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Change project number licence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Administration related licences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Client memory configuration licence. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Global licences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
FAQs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Is it possible to guarantee that the reference to a user sign is fully and irreversibly anonymised in
AMOS?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Page 3 of 13
Code Transfer
Code Transfer
Path: Applications/Administration/Database Access/Code Transfer
APN: 254
Overview
Note: In order to preserve the structural integrity of the affected database when using Code Transfer, the
following preconditions should ALWAYS be observed:
• Only one user logged in!
• No scheduler jobs running!
To ensure that the updates are processed properly, you should set the database option Truncate Log
on Checkpoint to true before starting the transfer and set it back to false afterwards. This must be
done outside of AMOS with a dedicated database software. A full database backup must be run after
completion.
WARNING: If you are planning to run a DATABASE LEVEL MASS OPERATION.
1. YOU MUST have a full backup available.
2. The procedure should be tested in a playground environment first.
Code Transfer can ONLY be used to RENAME records, not to merge records.
The old Code Transfer application uses plain SQL to look up affected tables and to perform the update
itself. The new Code Transfer application will collect affected tables/columns by their MimeType.
The Part Number Change function will be moved from Part Administration to Code Transfer. Since both
functions work similarly, this centralisation has positive effects on maintainability and further
development.
Code Transfer can be used to quickly and easily change certain codes in all affected tables in the
database for example a vendor code has changed and needs to be replaced everywhere in AMOS.
The following codes can be replaced:
▪ Vendor Code
▪ Aircraft Registration
▪ Aircraft Type
▪ Station
▪ Currency Code
▪ Project Number
▪ Part Number
▪ User Sign
User anonymisation
In Code Transfer you also have the possibility to anonymise any information relating to a person by
changing the User Sign in the records to a generic User Sign. For User Signs it is possible to exclude
tables from the migration by checking the entries in the Exclusion column. Entries marked will not be
migrated.
The migration for User Signs is different from other Transfer Items. Entries for columns marked with
the icon will not be migrated but DELETED.These tables contain master data for which the User
Sign is the primary key. Therefore it is not possible to migrate them to another value.
All other entries are migrated to the ERASED User Sign. In the two key tables "sign" and
"menu_user", this User Sign will be created by Basic-Data Administration.
The changes which are performed on User Signs cannot be undone.
Page 4 of 13
Code Transfer
Note: Therefore test the change carefully in a non-productive environment before applying them to
production.
How to use it
1. Select the item USER SIGN from the drop down list Item and select the user you want to erase in
the field Original Value.
Double click in the field to open a book of available AMOS Users.
Optionally, select the Include all table option to ensure you search for all tables storing the user
sign, notably in the created_by or mutator columns.
2. Click Search to check how many entries there are per table. You can check the tables you want to
exclude from this operation by selecting them in the Exclusion column.
3. Start the process by clicking the Update button.
Buttons
The following buttons are in Code Transfer.
Button Description
Search Use to search for selected data.
Show Entries Use to display the available entries for the selected Table and Column.
Update Use to update/replace the selected data. Original Values will be replaced by new
values.
Exit Use to exit the program.
The following icons are in Code Transfer.
Icon Description
Entries for columns displayed with this icon will not be migrated but DELETED. These tables
contain master data for which the User Sign is the primary key. Therefore it is not possible to
migrate them to another value.
Search, Workspace and Display sections
Search section
Field Description
Item drop- ▪ Vendor Code
down list ▪ Aircraft Registration
▪ Aircraft Type
If Aircraft Type is selected, the option Include FAT is available. This option will
update all database columns which use the MimeType for a financial aircraft type.
▪ Station
▪ Currency Code
▪ Project Number
▪ Part Number
▪ User Sign
If User Sign is selected, the option Include all tables is available. This option
guarantees that the reference to a user sign is fully and irreversibly anonymized in
AMOS.
Page 5 of 13
Code Transfer
Original Double-click in this field to open a window with a table of existing values depending
Value on your selection in the Item drop-down list.
Result table
Column Description
Table Displays the name of the table.
Column These are Table columns matching the selected Transfer Action.
Entries Displays the occurrences of the Original Value in this column.
Exclusion Displays if the selected table column is excluded. If excluded, the table row is highlighted
in red and the check box is selected.
Note: Lines highlighted in red cannot be selected, changed or altered.
Options
Option Description
Number of Entries Displays the sum of all occurrences of Original Value in the database.
New Value In this field you can define a new value. This value should not exist in AMOS.
This new value that you define will replace the original value.
Do not update By default this check box is not selected. If the user wants to exclude the tables
tables containing containing history, this check box must be selected. If you select this box, all
"hist" tables will be excluded which contain the string "hist". Always use with caution.
Depending on each case, the history tables must be updated or not. It is the
responsibility of the person who makes the change to decide whether to do so.
Display section
Column Description
Code The current available entries for the selected Table and Column are displayed here after
clicking Show Entries .
WARNING: The excluded database field "partno" will be altered at the very end after a history has
been written that a part number change has been performed by AMOS.
1. Select a Transfer Action
2. Double-click on the Original Value field and a window of the defined entries for the selected
Transfer Action appears. Select the entry you want to replace.
3. The Search button becomes active. Click on it and you will launch a Database Query to determine
the number of occurrences per Table/Column.
4. AMOS will inform you how many entries are in the Database. Now the Update button becomes
active.
5. Enter a New Value which will replace the old one and click Update . Only values which are not
known to AMOS can be entered into this field. If a value already exists in AMOS you will be
informed.
6. When you are ready to update the chosen value click Update and the Run Updates window
appears. Click OK or click Cancel to stop the action.
GDPR Requirements
AMOS fulfils the following GDPR requirements:
Page 6 of 13
Code Transfer
Art 5.1. c) data minimization
Art 5.7. e) storage limitation
Art 17. Right to erasure (right to be forgotten)
Disclaimer
WARNING: In order to preserve the structural integrity of the affected database when using Code
Transfer, the following preconditions should ALWAYS be observed:
▪ Test the intended update in a testing environment first!
▪ Have a full-backup available!
▪ Request a possible downtime to restore the database!
▪ Only one user logged in!
▪ No scheduler jobs running!
▪ To ensure the proper processing of the updates, you should set the database option "truncate log
on checkpoint" to true before starting the transfer and set it back to false afterwards. This must be
done outside of AMOS with a dedicated database software. A full database backup must be run
after completion!
Page 7 of 13
Code Transfer
Code Transfer related licences
Listed below are the licences associated with this program/module and which can be set by the AMOS
System Administrator. All licences are listed in Admin Programs.
Change user sign codes licence
Licence Function
Change user sign codes Licence to change User Sign Codes.
Change station code licence
Licence Function
Change station code Allows you to change station codes and workorder numbers in Code Transfer.
Change vendor code licence
Licence Function
Change vendor code Allows you to change vendor codes in Code Transfer.
Change AC-registration code licence
Licence Function
Change aircraft registration code Allows you to change the aircraft registration codes in Code
Transfer.
Change part number licence
Licence Function
Change part number Allows you to change a part number.
Change aircraft type licence
Licence Function
Change aircraft type Licence to change Aircraft Types.
Change currency code licence
Licence Function
Change currency code Licence to change Currency Codes.
Page 8 of 13
Code Transfer
Change project number licence
Licence Function
Change project number Licence to change Project Numbers.
Page 9 of 13
Code Transfer
Administration related licences
Listed below are the licences associated with this program/module and which can be set by the AMOS
System Administrator. All licences are listed in Admin Programs.
Client memory configuration licence
Licence Function
Client memory configuration Allows the user to change the memory configuration of the
AMOSclient.
Page 10 of 13
Code Transfer
Global licences
Global licences are used in every AMOS program and are listed in Admin Programs and Admin Roles.
Refer to Admin Roles > Global Licences list
Page 11 of 13
Code Transfer
FAQs
Is it possible to guarantee that the reference to a user sign
is fully and irreversibly anonymised in AMOS?
Yes, in Code Transfer (APN 254), be sure to choose the Include all tables option before updating the
corresponding USER SIGN to ERASED.
Note: Be aware that selecting this option may result in a longer update process as it impacts nearly all
tables in the database.
If you decide to exclude a particular table from the operation, and if this table serves as a foreign key
to another table that is not excluded, AMOS will halt the operation until the entry is either included or
the linked column is also excluded.
Page 12 of 13
Code Transfer
Index
A
• Administration related licences. . . . . 10
B
• Buttons. . . . . . . . . . . . . . . . . . . . . . . . 5
C
• Change AC-registration code licence. 8
• Change aircraft type licence. . . . . . . . 8
• Change currency code licence. . . . . . 8
• Change part number licence. . . . . . . . 8
• Change project number licence. . . . . . 9
• Change station code licence. . . . . . . . 8
• Change user sign codes licence. . . . . 8
• Change vendor code licence. . . . . . . . 8
• Client memory configuration licence. 10
• Code Transfer. . . . . . . . . . . . . . . . . . . 4
• Code Transfer related licences. . . . . . 8
• Copyright Notice. . . . . . . . . . . . . . . . . 2
D
• Disclaimer. . . . . . . . . . . . . . . . . . . . . . 7
F
• FAQs. . . . . . . . . . . . . . . . . . . . . . . . . 12
G
• Global licences. . . . . . . . . . . . . . . . . 11
I
• Is it possible to guarantee that the
reference to a user sign is fully and
irreversibly anonymised in AMOS?. . 12
O
• Overview. . . . . . . . . . . . . . . . . . . . . . . 4
S
• Search, Workspace and Display
sections. . . . . . . . . . . . . . . . . . . . . . . . 5
U
• User anonymisation. . . . . . . . . . . . . . . 4
Page 13 of 13
