iCompMan Manual

MyFootballClub registrations import - automated transfer

MyFootballClub registrations import - automated transfer

Previous topic Next topic  

MyFootballClub registrations import - automated transfer

Previous topic Next topic JavaScript is required for the print function  

This is a special routine created to import data from the Football Federation of Australia (FFA) online registration program My Football Club (MFC).


The registration data is provided by FFA once a day. The data transfer/import is done automatically by our Internet data server during the night and includes all new and modified registrations for the past 24 hours.


Note: Club registrars still have the option to transfer data from MFC manually using the “CSV” data export option. This may be necessary with “late” registrations.


Data Flow


- The iCompMan server requests data transfer from MFC daily (after midnight)

- A background process in iCompMan transfers the MFC data to the iCompMan data structure

- Club registrars will review data transferred from MFC before accepting the new/modified registrations. All the necessary information and tools are available on the page shown below.



1.Information on the last data import date/time
2.By default only newly received data will be shown. It is however possible to display all previously received registrations or to separate and view only deregistered members in the MFC system.
3.The “Accepted” column will show “Yes” for already accepted registrations when displaying “All” – option 2.
4.Members deregistered in the MFC system are marked with “X” in the list for easier identification.
5.You can preview records with potential data import errors
6.Data validation rules can be configured to suit your requirements
7.It is possible to modify the imported data before accepting it (before updating registrations in iCompMan).

It is also possible to remove unwanted registrations from the list before accepting the rest. In such cases use the “Delete” button.

8.Normally a registrar, after having reviewed the data obtained from MFC, will select all records using the “Select all” button and update registrations in iCompMan by using the “Accept selected records” button.


Note: When accepting the data transferred from MFC, the program still validates the received data and sends any conflicting records to the Data Import Errors table as before.


Example of the data update form:


Note: Modifying imported data before accepting it is optional.


 Data Validation Rules options




IMPORANTData Definitions


It is vitally important to ensure that common data definitions are the same between the two systems, MFC and iCompMan. Irrespective whether registrations are transferred from the MFC system manually or electronically, any discrepancies in the common data definitions may, and most likely will, cause unnecessary problems.


The data definitions to watch out for are:

-Age Group codes
-Division codes
-Team codes
-Team No/ID codes
-Registrations categories (player, coach, etc.) codes


Main pitfall – Age Groups


Traditionally this is the main source of issues with importing registrations from MFC into CompMan. Below is the explanation how the MFC system manages age groups. Our program applies this logic to the data being transferred. If you wish to deviate from this logic please email us with clear instructions how your association would like to handle Age Groups.


MFC system rules:


The Age Group is based on a number of factors.


a.If the club has placed player into a team, it is the Age Group of that team. Assuming the Association has setup the correct Age Group codes in MFC, this should be the same Age Group code that is defined by the Association in iCompMan.
b.If the club has not placed the player in the team, the Age Group will be taken from a mapping table that has been setup in MFC based on the Age Groups given to FFA by the Association. If the Association changes their Age Groups they need to tell FFA so this mapping table can be updated. The mapping is based on the players age at the end of that year.
c.If the club has not placed the player in a team, and the Association’s Age Groups do not exist in the mapping table, the AgeGroup is taken from the PackageAgeGroup, which is defined by the club.