Clients
is strongly advice to do this series of adding or deleting key field
first on the Test Environment and if the result is satisfactory do your
Production Environment.
These key fields, per event, can only be
changed at the beginning of a new
academic year and structure – that is when a fee structure is
created for a new
academic year BEFORE A APPLICATION AND/OR REGISTRATION, WAS PROCESSED,
FOR THE NEW ACADEMIC YEAR. If any application and/or registration
was done for a academic year then no maintenance is allowed on the key
fields. Maintenance is allowed on the second block of options {FSAM-29} and {FSAM-1} during
the academic year.
This option and {
FSAMR2-7}
has the same program and has 3 functions, regardless of which option is
used. The definition of the function will determent what function will
be done when the program run..
Function 1: The user add a new key field.
In first action of adding, the user has add a new key field.
This action has the result that option {
FSAM-1b2}, for the year and event, has a new key field that is null.
This program will DELETE/REMOVE all records from {
FSAM-1b2} where a key field is null. In this case this program will delete/remove all records for the year and event.
Function 2: The user remove a new key field.
In first action of deleting, the user has remove a key field.
This action has the result that option {
FSAM-1b2},
for the year and event, has a key field with values that is not defined
as a key for a year and event. This key field is not displayed to
the user on option {
FSAM-1b2}.
This
program will DELETE/REMOVE all records from {
FSAM-1b2}
that has a key field with values that is not defined as a key for a
year and event. In this case this program will delete/remove all
records for
the year and event.
Function 3: The user did not add or remove a key field and need to run
this option to cleanup/remove Valid N records of {
FSAM-29} from {
FSAM-1}.
This function does not form part of the adding or remove of key fields action.
This function will do the following, for the year and event, when run:
There is not a key field that was add or removed.
Key field that is set to Valid N in {
FSAM-29} that have records in option {
FSAM-1} will be deleted/removed from option {
FSAM-1}.
Any keys in option {
FSAM-1} that does not have a record in {
FSAM-29} will be deleted/removed from option {
FSAM-1}.
DO NOT USE THIS FUNCTION IF THE CLIENT HAS RECORDS WITH TRANSACTION IN OPTION {
FSAM-1b2} AND THE KEY AND TRANSACTION TYPE DOES NOT EXIST IN {FSAM-29b2}. THIS PROGRAM WILL DELETE/REMOVE THE RECORDS FROM {
FSAM-1b2}
The reason for these records are:
Some keys required additional fee/s over and above the fee as define in {
FSAM-29} and they are normally add on an ad hoc bases .
Do not add these records to option {
FSAM-29}, if add it will solve the problem for now, but it will increase your maintenance on future new records in {
FSAM-1b2}, because the key will have record that is not applicable.
If still troubled consult ITS before running this program.
Note that Event 01 for year 2012 does
not have any records in this block, they where all deleted by this
options action. the user must now move to action 4 of adding the new records.
