There are two primary reasons why customers will have a requirement to customize the Reporting Module. The first is that customers may want to include fields and entities in Reporting that are not included in the 'out of the box' functionality and the second is that they may have already extended the Core Data Model and they want to include the additional data in Reporting:
The folder structure provided with BIA Reporting consists of both a core folder and a custom folder. When a customer site wants to modify metadata such as an ETL or DDL they should copy the core file, place it in the custom folder and make modifications in this custom folder. Build scripts will then give precedence to the contents of the custom folder.
The core folder should never contain artifacts modified by the customer. This is necessary for future upgrades (see separate section below on Upgrades) of BIA Reporting.
The following steps give the modifiable artifacts delivered with Reporting together with the customization guidelines. Example scenarios in Appendix C detail typical customizations that customers will be faced with. The three examples provided detail the user report change required, the methodology used for determining the required changes, and finally a listing of the changes required.