Generate Fee Values {FSAMR2-4}

This is the forth action in a series of options to removing a key field to the SD Fee Structure options {FSAM-29} and {FSAM-1}. In the this manual we discuss also the fifth (final) action. For more detail see information below.

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.

To change some of the key fields, only one field at a time can be changed, using the batch programs.
To remove a key field use {FSAMR2-1}, {FSAMR2-2}, {FSAMR2-3}, {FSAMR2-4}
or
To add a key field {FSAMR2-5}, {FSAMR2-6}, {FSAMR2-7}, {FSAMR2-8}.

This option add/create records in {FSAM-1b1} applying the following rules.
NB. Read the following before the user run this option:

This option and {FSAMR2-8} has the same program and has 2 functions, regardless of which option is used.

Function 1: The user add/delete a new key field.

Before running this option, option {FSAM-1b2} has no records for the year and event, the previous action deleted all the records for the year and event.
This program will add/create all records in option {FSAM-1b2} using option {FSAM-29} information from all the blocks for the year and the event.
The fifth and final action is to add records in option {FSAM-1b2} for transaction types that are no defined in option {FSAM-29}.

Example:

In option {FSAM-29} only the primary fee is defined.
In some of the combinations there is additional fees like NZQA/SAQA.
These records must be add by the user in option {FSAM-1b2}.

Function 2: The user did not add or remove a key field and need to run this option to add Valid Y records of {FSAM-29}, that does not exist, in {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 Y in {FSAM-29}, that does not exist, in option {FSAM-1} will be be added/created to option {FSAM-1}.

After the above run add records in option {FSAM-1b2} for transaction types that are no defined in option {FSAM-29}.

Example:

In option {FSAM-29} only the primary fee is defined.
In some of the combinations there is additional fees like NZQA/SAQA.
These records must be add by the user in option {FSAM-1b2}.

User Selection	Prompt Text ^{* an item between square brackets [ ] is the default answer}	Type & Length	Comments
	Year	N4
	Even to Generate Fee Records	A2

Sort Order	Per	Comments
	Key fields

System Select
	No special system selection

Example: Removing key field Post/Undergraduate from Event 01. The reason is post and undergraduate does pay the same fee for application and the Basis of Generation has changed.
The processing add/create records to option {FSAM-1}. Below is the before image of {FSAM-1} before this program has run.
Block 1.

No action has change anything on this block.

Block 2:

Note that Event 01 for year 2012 does not have any records in this block, they where all deleted by the previous option action.

This option user selection is to add/create fee values.

The report that was generated, using the above user selection.

Option {FSAM-1} after adding/creating the fee records.
Block 1
No action has change anything on this block

Block 2:

This program added/created all records in option {FSAM-1b2} using option {FSAM-29} information from all the blocks for the year and event.

The user must perform the fifth and final action is to add records in option {FSAM-1b2} for transaction types that are no defined in option {FSAM-29}, if required.

Processing Rules
	No special processing rules