Feeders File
The feeders file should define feeders for job groups in all plans.
The table below lists possible fields for the feeders file. Field names in bold text are required fields for import. Data in the files can contain letters, numbers, or both unless specifically noted.
IMPORTANT: There is no field mapping for the feeders file. This means that the fields must be named exactly as listed below (not case-sensitive) in order to import properly.
| Field Name | Max Length | Req'd? | Description |
| Plan Name | 128 | N | The plan to which the job group belongs. If this field is left blank, this file will be considered a ”universal” file, and the information will be applied to every plan in the plan container. When a universal file format is used and the total feeder weight for a job group is less than 100%, the remaining weight will be automatically redistributed among the feeders in the job group. |
| Job Group Code | 50 | Y | The job group code to which the feeder will be applied. |
| Feeder Plan Name | 128 | N | The plan to which the feeder job group belongs. Feeders typically come from the same plan. If this field is left blank, it will default to the one provided in the Plan Name field. If the Plan Name field is also blank, this field will be ignored. |
| Feeder Type | 9 | N | Value indicating the type of feeder. Acceptable values are JOBGROUP or JOB. If this field is left blank, it will default to JOBGROUP. |
| Feeder Code | 50 | Y | The job group code (or job code, if feeder type is JOB) that feeds into the specified job group. |
| Feeder Weight | 7 | Y |
Weight assigned to the feeder.
NOTE: Feeder weights for one job group must total 100%. Weights should be entered as whole numbers with up to two decimal places (i.e., if the weight is 20.5%, enter 20.5).
|