Train Source Report
The Train Source report displays a summary of a selected shipment and unloading details of the trains assigned to the shipment.
The report is designed to work best with shipment despatches that have a single sales or purchase despatch order. The trains must be associated with the shipment (via the header fields in the Train screen). The despatch order is not assigned to the trains.
The report definition is stored in the TrainSource.xml file.
Parameters
The Train Source report contains the following default parameters:
|
Name |
Default Type |
Required |
Description |
|---|---|---|---|
|
Start Date |
Date/time picker |
Y |
Limits the report to shipments where the ETD or actual end loading => this value. |
|
End Date |
Date/time picker |
Y |
Limits the report to shipments where the ETD or actual end loading <= this value. |
|
Shipment |
Single-select list |
Y |
Limits the report to the selected shipment. The drop-down list displays only the shipments within the report's date range and that have the Loading Type set to Loading Only or Both. |
|
Despatch Order |
Single-select list |
Y |
Limits the report to trains associated with the selected shipment and despatch order combination. The drop-down list displays despatch orders on the selected shipment. |
Report View
The Train Source report has five sections:
- Logo
- Header Information
- Shipment Summary
- Train Unloading Details
- Footer
Logo
The logo is retrieved from the organisation or company specified as the Logo Organisation for the BTLogo data table in the report configuration.
If no Logo Organisation is selected, the logo is retrieved from the organisation or company with an Alias2 of 'SITE'. If no such organisation or company exists, or if the organisation or company with Alias2 of 'SITE' does not contain a logo, the Datamine logo displays on the report.
Header Information
The report header includes the report title and the name of the shipment.
Shipment Summary
The shipment summary section displays the following fields.
Data in the asterisked fields displays in bold if the data is actual rather than estimated or planned.
The date format is the short date format specified in the MineMarket user preferences.
|
Field |
Description |
|---|---|
|
Customer |
The name of the buyer of the sales contract or the seller of the purchase contract associated with the despatch order. |
|
Contract |
The name of the contract. |
|
Product Description |
The description (from the Product screen) of the contract product of the despatch order. |
|
Despatch Order Required Quantity |
The required quantity of the despatch order. |
|
Ship Loading Location |
The loading location in the shipment's route. |
|
Source Stockpile |
The source stockpile of the first loading transaction on the shipment. |
|
Arrival Time* |
The shipment's actual time of arrival (ATA) if available, or else the estimated time of arrival (ETA). |
|
Start Loading* |
The shipment's start loading date if available, or else the planned start loading date. |
|
End Loading* |
The shipment's end loading date if available, or else the planned end loading date. |
|
Shipment Quantity* |
The current quantity from the despatch order snapshot if available, or else the total mass of planned loading transactions on the shipment. |
Train Unloading Details
The train unloading details section displays the following columns.
|
Column |
Description |
|---|---|
|
End Unloading |
The train's end loading date if available, or else the planned end loading date. |
|
Train |
The name of the train. |
|
Unloaded Quantity |
The total mass of unloading transactions on the train. |
|
Destination Stockpile |
The destination stockpile of the first unloading transaction on the train. |
|
Status |
The status of the train. |
|
Contributors |
The quantities for the six largest contributors for the train unloading transactions. |
Footer
The footer displays on every page. The footer includes the report run date and time, the version, the page number, and the total number of pages.
