Although we simplified DataTrak implementation as much as possible, implementation requires more than just installing the software. You will complete numerous steps as you implement DataTrak. Some implementation steps are quite simple and take only a few moments to complete, for example, checking your web browser's configuration settings. Other steps are more complex and require some planning on your part, such as creating profit center consolidation paths or user groups. Print or bookmark this help topic to serve as your guide during the implementation process.
DataTrak implementation will occur in 2 stages: Management Reports and Data Alerts.
The first implementation stage fully enables management reports. This stage is important because this is when you will:
Install and configure software.
Define profit center consolidation paths.
Create and configure user groups and accounts, including access and security.
After you complete the first implementation stage, you can then begin the second stage in DataTrak implementation: Data Alerts. During this implementation stage you will:
Define any necessary schedules
Schedule events
Schedule alerts for users (user's can also schedule their own alerts)
Management reports implementation steps fall into two categories: System Implementation and Technical Implementation.
System Implementation refers primarily to those steps you need to take in the ExecuTrak system to enable DataTrak to interface with the database and report data correctly. For example, creating profit center paths, general ledger accounts, and products. Click here to access DataTrak User Help.
Technical implementation refers to such things as software installation, creating user accounts, and performing other DataTrak maintenance for which only the DataTrak administrator has access.
The following list of implementation steps contains both technical and system installation steps. Items appearing in italics, are considered system implementation steps. Those appearing in regular type are considered technical implementation steps. Technical implementation steps are part of the DataTrak Admin Help system. You will need to complete the following implementation steps, in the listed order to set up DataTrak:
Install the ExecuTrak for Windows Service Pack and Interim Service Pack (Consult the Factor Documentation CD for instructions.)
Install the Interim Release on the RISC or SCO system. (Consult the Factor Documentation CD for instructions.)
Install Java Virtual Machine (JVM) on each client PC that will run DataTrak. To install, insert the CD into the PC’s CD ROM drive. Setup will begin automatically. Follow the on-screen prompts to complete installation. Reboot the client PC after installation.
Install the latest CommServer release. (Consult the Factor Documentation CD for instructions.)
Install the DataTrak software on the RISC or SCO system.
Login to the RISC or SCO system as “root”.
Insert DataTrak CD into the CD-ROM on the RISC or SCO.
Type
the following command at the prompt and then press Enter:
mount /cdrom
Type
the following command at the prompt and then press Enter:
cd /cdrom
Type
the following command at the prompt and then press Enter:
./install.pl
Installation is automated from this point forward.
After
installation is complete, type the following command at the prompt and
then press enter:
cd
Next,
type the following command and press enter:
umount /cdrom
You won’t be able to remove the CD if you omit this step.
Note: After installation, consult DataTrak’s on-line help for additional information on implementation and program operations. You can access this help by entering the following URL into your web browser: http://ether/portalhelp/admin/admin_help.htm. If your server is not named “ether” replace “ether” in the URL with the actual name of your server. User help can be accessed at http://ether/portalhelp/portal.htm.
Set the web browser on the client PC to check for newer versions of stored pages each time you visit a web page. (Open your web browser and select Tools >> Internet Options >> Settings >> Every Visit to the Page.)
In the Advanced Financial Module, create the profit center consolidation paths that will be used to define DataTrak’s drill-down paths. Consolidation paths are a hierarchical structure of profit centers used to establish profit center relationships for drill-down reporting. If you currently use the Advanced Financial module, you may have an existing path that DataTrak can utilize.
Set System Parameter 16000 to identify the profit center path to use for drill-down reporting. System parameters are set through ExecuTrak.
Set System Parameter 16001 to identify the number of periods to include the retail sales consolidation. System parameters are set through ExecuTrak.
Add inventory, sales, and cost GL accounts to the chart of accounts for dummy profit centers in the DataTrak consolidation path. See the Special Considerations for Dummy Profit Centers Help Topic.
Set up inventory master records for fuel products at dummy profit centers in the DataTrak consolidation path. See the Special Considerations for Dummy Profit Centers Help Topic.
Perform DataTrak maintenance to finish set up. These steps should be performed by the DataTrak administrator. Consult the DataTrak administrator help system for detailed instructions on each step.
Data alerts functionality should be implemented only after you have completed the necessary steps for DataTrak implementation. Use the following steps as a guideline for implementing data alerts:
In the ExecuTrak system, set the value of System Parameter 10 to the date that you implement data alerts.
Use Schedule File Maintenance to create any user-defined schedules. DataTrak does install with numerous pre-defined schedules that might meet your needs.
Use Offline Report Boundary File Maintenance to set the following boundaries:
The number of periods, prior to the current period, for which the Offline Fuel Inventory Pre-processor will generate Fuel Inventory Over/Short alerts.
The number of periods for which the Retail Fuel Profit Analysis Report should be generated.
The number of periods
for which the Retail Sales Profit Analysis Report should be generated.
Use Event File Maintenance to set schedules for the Stand Alone Pre-Processor and Offline Fuel Inventory Pre-Processor.
Perform Data Alert File Maintenance to specify which alerts a user will receive, including the tolerance and schedules for the alerts.