Embedded Files
This document describes the process to run the WSX RAPTOR docket export and its output (Note: DB Setting SQL_Raptor_Export must be set to 1)
For dockets to be written to the RAPTOR export file, the following criteria must first be met,
Docket LogOrg in RNZ_Export_LogOrgList setting (check with TFL Support if unsure)
Delivery date within the selected range (date range selected when export is run)
Docket LogOrg in the selected list (Log Orgs selected when export is run)
Docket Not Yet Sent
Net weight > 0
If 'Include Export Customers?' is checked then JAS and Pieces must be present for Export Customers
Must have M-Check (E-Check not required)
Cannot have E-Error or M-Error
Running an Export
Running an Export
To run the docket export, access the function from the menu: Dockets > Raptor > Create XML. From the Select Export Options screen that presents, make the following selections,
Start Date - Select the first date from which you want to include dockets
End Date - Select the final date up to which you want to include dockets
Include Export Customers? - Includes dockets for customers marked as ‘Export Customer’ in the database.
Send Un-Validated? - If selected this will export all dockets that are not set as ‘Error’. CAUTION: ticking this option will include non-validated docket data in the export.
Additional PSLog File - When selected, this will generate an additional docket export file in the PSLog format (see below for additonal details)
Select Log Orgs - Select the Log Org(s) for which you want to export docket data
Additional PSLog File - Notes
Selecting this option will activate the Customer selection area in the select screen, from which the customers for which an additional PSLog file is to be generated can be selected.
These files are generated into a folder specific to your operation - if you are unsure of the location of the files please contact Trimble Forestry support.
Sending of such files to the intended recipient needs to be done through normal channels - these files will not be sent via the automated FTP process as with the standard Matariki/Rayonier files.
Data Exported to XML
Data Exported to XML
Shown to the right is an example of the data exported to the XML file for each docket, with the table below describing this data.
The XML files are written to the location specified in the DB Setting LogOrgXMLOPathPath, with a file naming convention of ‘LogOrgDD_MM_HHMMSS.AST’. Once written to this folder they will be automatically picked up and FTP’d to Matariki, with the FTP process running every 15 minutes.
Note: A DB Setting exists in the database (RestrictedLogOrgList), which controls the data written to the RAPTOR export for the Log Orgs specified within it. For Log Orgs specified in this setting, the following fields are left blank when the export is created,
Logger, Crew, Cartage, Truck, Trailer, Operation
At present the Log Orgs associated to this setting are the AWG (AWGBOP, AWGNTH) log orgs, as they are processed differently by Rayonier. Additional log orgs can be added to this list if required, but such a request will be initiated by Rayonier.
A further DB Setting also exists in the database (RNZOnTruckCustomer_LogOrg), which controls the data written to the RAPTOR export for the Customers specified within it (where the Log Org in the setting is not included in those listed against the RestrictedLogOrgList setting). For dockets associated to customers specified in this setting, the following fields are left blank when the export is created,
Cartage, Truck, Trailer, Backload, LoadRate
Key to the data in the table below,
Field = Describes data in field
Origin = WSX or External Data Record
Data Source Field = Describes the source of data from within WSX
Translation = Translation available with associated Translation Entity Type
Required for Export? = Data must be present in these fields for docket to be written to FLITS export file. Note those marked as 'System' will always be present.
Field Origin Data Source Field Translation Required for Export?
DocketCode --- Docket Number if Paper Dockets (UseMorph = Off) --- No
DocketDate WSX Delivery Date --- System
Forest WSX Forest Code (full code incl Supplier/Short Code) FOREST System
SaleArea WSX Compartment Code --- System
Setting WSX Setting Code --- System
Species WSX Species (from Sold As WoodGroup) --- System
LogType WSX MasterGrade (from Sold As WoodGroup) --- System
Grade WSX MajorGrade (from Sold As WoodGroup) --- System
CutAs WSX MajorGrade (from Cut As WoodGroup) --- System
LogLen WSX Length or Export Length (for Customers set as Export) --- System
Note: Not populated where the Length Type field against
the WoodType is set as 'Random'. In these cases the length
is added to the <Random>field
Random WSX Length (from Sold As WoodGroup) --- System
Note: Only populated where the length type against the
Log Grade is Random. Where length type is 'fixed' this field
left blank and the 'LogLen' filed is populated.
Count WSX Pieces --- Export Customers Only
Operation WSX Operation associated to source Gang Location --- System
PickUp WSX N/A --- ---
Destination WSX Customer Destination Code CUSTOMER Yes
Note: Additional Translation may exist within the Additional
Customer Codes translation table - see below for details.
Quantity1 WSX Net Weight --- Yes
UOM1 WSX Always set as 'TON' (hardcoded) --- System
Quantity2 WSX JAS (Volume) --- Export Customers Only
UOM2 WSX Always set as 'JAS' (hardcoded) where value present --- System
Logger WSX Logging Contractor Code (associated to Gang) LOGGER System
Crew WSX Gang Code (Not Gang No.) CREW System
Customer WSX Customer Code + 1st letter of Supplier Code, e.g. A for AWG CUSTOMER System
or M for MFT. Possible addition also of a Customer Region
Code - see below
Cartage WSX Trucking Contractor Code TRUCKCON System
Truck WSX Truck Code TRUCK Yes (if Truck or Full Load)
Trailer WSX Trailer Code TRAILER Yes (if Trailer or Full Load)
Backload WSX Backload - Populated with a ‘Y’ if Internal or External --- System
backload. All other times it is populated with a ‘N'
LoadRate WSX If the journey is set as a Backload and the Customer is not --- System
listed in the RNZOnTruckCustomer_LogOrg DB Setting, the
LoadRate field is populated with 'Backload', otherwise it is
left blank.
Full WSX N/A --- ---
PDA WSX N/A --- ---
ExtDocket WSX Purchase Docket --- No
Comments WSX N/A --- ---
EDocket WSX 'Y' if Electronic Dockets, 'N' if not (based on UseMorph setting) --- System
DocketType WSX Populated with 'BushDocket' with the exception where if --- System
the crew tagged as Logyard it s set as 'Intermediate Docket'
EDocketNumber WSX Docket Number (if an ED) --- Yes (if E-Dockets)
Alternative Customer Destination Codes
Deliveries to specific customers from certain sources also require the ‘Destination’ on the RAPTOR docket export to be translated outside of the standard WSX Translations function. These translations should only be established when requested from Matariki/Rayonier.
To add or edit Alternative Customer Destination Codes, from the Dockets menu select Raptor > Alternative Customer Destinations (screen shown to the right), and enter records as described below.
Customer Code: Select the customer for which the translation is to apply.
Gang Location: Select the source (Gang Location) from which the translation is to apply.
Alternate Code: Enter the alternative code that will be used in place of the standard destination code for the customer, when loads are delivered from this source.
(Replace with updated screenshot)
Customer Region Codes
Some customers supplied by Matariki/Rayonier from more than one region require the addition of a ‘Customer Region Code’ to the customer code in the RAPTOR docket export data. These such codes are established in the Customer Region Codes scree, but should only be established based on a request from Matariki/Rayonier.
To add or edit Customer Region Codes, from the Dockets menu select Raptor > Customer Region Codes (screen shown to the right), and enter records as described below.
Customer Code: Select the WSX Customer
Log Org: Select the WSX Log Org
Region Code: Enter the Region Code (BOP = B, Northland = N)
Page updated
Report abuse