The bulk switch load program reads the input file and validates the records. Errors are written to the error log, and are displayed per member. Data is only written to the database once all errors have been fixed.
The following validations are performed:
Check that the file length of the file is correct
- type 01 (sell) - length 46
- type 02 (buy) - length 37
Sell portfolio validations – check that the
- sell percentage is greater than zero
- sell due date is valid
- sell percentage is within the minimum / maximum range of the portfolio detail
- sell portfolio for the member has a positive unit balance (i.e. has an investment position)
Buy portfolio validations – check that the
- buy percentage is greater than zero
- total buy percentage for the member adds up to 100%
- scheme code is valid
- membership is valid
- member's end date is null
- portfolio is valid for the scheme
- member belongs to an investment category
- buy portfolio for the investment category is valid
- override fee indicator is valid
- member does not exceed the maximum limit of the investment category
You can view the results of a successful bulk switch by selecting the appropriate member enquiry.
Click clients.
The Welcome screen will be displayed.
Select Members from the top menu. The JU3AO List of Members for a Scheme/Pay Centre screen will be displayed.
Select the required member as described under Finding Members under
Members
Members
From the JU3AO List of Members for a Scheme/Pay Centre screen, highlight the required member, then select Member Switching Enquiries from the menu.
For more information, refer to
Clients
Member Switching Enquiries
Access to perform this function is only allowed for the user group called SWITCH LOAD.
If the user is not in the appropriate user group, then they must be assigned to that user group in order to be able perform the switching load function.
Refer to Assign a User to a User Group and Propagate User Changes under
Security
Functional
Data Take On Process For Pensioners
Note:
- The records must be sequential, i.e. the buy transactions must follow the sell transactions for that specific reference number.
- The last line must read EOF.
Note:
If the file is being resubmitted after an error has occurred, then the file name must be different to the original file name.
Sell transaction
Field Name |
Field Size |
ATTR |
Format |
Value |
File mask code |
4 |
Char |
|
SWTH |
Tran code sell |
2 |
Num |
|
01 |
Scheme code |
7 |
Char |
Align left |
|
Reference number |
8 |
Char |
Align left |
|
Sell Portfolio code |
8 |
Char |
Align left |
|
Transfer percentage |
7 |
Num |
2 decimals |
|
Sell due date |
8 |
Num |
CCYYMMDD |
|
Override fee indicator (Y or N) |
1 |
Char |
|
Y or N |
Buy transaction for sell transaction
Field Name |
Field Size |
ATTR |
Format |
Value |
File mask code |
4 |
Char |
|
SWTH |
Tran code buy |
2 |
Num |
|
02 |
Scheme code |
7 |
Char |
Align left |
|
Reference number |
8 |
Char |
Align left |
|
Buy Portfolio code |
8 |
Char |
Align left |
|
Buy percentage |
7 |
Num |
2 decimals |
|
Note:
All optional text fields must be padded with trailing spaces.
All numeric fields must be padded with leading zeroes.