| User Selection |
Prompt Text
* an item between square brackets [ ] is the default
answer |
Type
&
Length |
Comments |
|
Supply the Subsystem Code or ALL |
A2 |
A file can be created for all
the transactions from a specific subsystem or all the subsystems for
which payments and receipts were generated. |
|
Supply the Cash-Book Code |
A5 |
All the transactions on one file must belong to the same cash book. |
|
Supply the ACB User Code |
N4 |
All the transactions on one tape must
belong to the same ACB user code. If different cash books and ACB users
are in use, separate files must be created for each. |
|
Supply First Action Date |
DD-MON-YYYY |
The earliest date on which payments or receipts may
be effectively transferred. All transactions with an action date before
this date will be updated with this date as the new action date. |
|
Supply
Last Action Date |
DD-MON-YYYY |
The latest date on which
transfers may be passed. Only transactions with action dates between
these dates will be transferred to the file. |
|
Supply Purge Date |
DD-MON-YYYY |
The date on which the ACB organisation may delete the
records from their database. |
|
Is this a Test Tape? (Y/N) |
A1 |
If the answer is (Y)es, the program will
insert the characters “TEST” as per the ACB instructions
into the ACB file listing and DCV (every user is allowed two test
files, which
will be validated by the Bureau free of charge). |
|
|
|
- If there are no incorrect data records, the system will
generate the UNIX file for ACB (called finacb.tape),
thereafter listing the file on the system printer. This printout
should accompany the file to the Bureau.
- A “Tape
Delivery Advice (TDA)” and “Data Control Voucher (DCV)” are also
produced in duplicate for submission to the Bureau.
- In
addition, the “ACB Item and Aggregate Limit Report” is produced in two
parts. The first part identifies individual transactions that exceed
the limit and the second part identifies when the 7 day limit is
exceeded. Arrangements must be made with the Bureau if these limits
must be exceeded.
- The “ACB Tape Detail Report” is
divided into three parts. The first part identifies all action dates
that were changed. The second part is the detail of all the records in
the file. The creditor number recorded in the file will either be “Our
Account Number” if this is recorded on {FPMM-2} or,
if this field is null, “Our Membership Number” as recorded on {FPMM-2}
or, if this field is null, “Creditor Code”, as defined on {FPMM-2}.
The third part is a breakdown of all the transactions per action date.
- The system checks for invalid account numbers and payment types, with
explicit error messages on the report listing. If any errors are
encountered, the User Generation Number and Installation Generation
Number in option {FCSC-5} will NOT be increased. Any fatal errors in
the data will result in an error report being produced. The report
will identify the detail of the incorrect record. A file will not
be created and the process stops.
|
