...
The Report Import page allows users to import landing and production reports, one at a time. Reports are imported in the unsubmitted status. Once the report has been successfully imported, users must review it and submit it. Imported landing reports must be initially submitted, and finally submitted, just like reports created directly in eLandings. Production reports do not have a distinction between initial submit and final submit, they just need to be submitted after they are imported. As a consequence, the XML document for reports does not have to specify the status element. If the status element is specified, it must have the unsubmitted status value.
The Report Import page has some flexibility in the use and assignment of report identifiers. Both landing reports and production reports have a report ID, which uniquely identifies the report. Landing reports also have fish ticket numbers, which identify what parts of the harvest documented on the landing report are assigned to which CFEC permits. The report ID can be handled in one of two ways.
...
report id element should be omitted from the XML document. When the document is imported a new, unique, report ID will be generated and assigned to the report. When the report is displayed after importing the report ID can be read off of the web page. It can also be obtained by downloading the XML from eLandings, which can be done from the report display page that is displayed after a successful import.
The Report Import page has some flexibility in the use and assignment of fish ticket numbers on landing reports. The fish ticket numbers identify what parts of the harvest documented on the landing report are assigned to which CFEC permits. The fish ticket numbers can be handled in several ways.
- If the landing report has only one CFEC permit, the fish ticket number can be omitted from the report. The eLandings system will generate a new fish ticket number for the report, and will populate it on the permit worksheet and line items.
- If the landing report has more than one CFEC permit, but the line items are not allocated to the permits, then the fish ticket numbers can be omitted, and the eLandings system will fill them in on the permit worksheet. In this case, the user will need to use the Allocate Permits function on the eLandings web application to allocate the line items to permits.
- Place holder fish ticket numbers can be assigned to the CFEC permits, and line items if desired. In this case, the eLandings system will replace each unique placeholder fish ticket number with a new, generated fish ticket number. The placeholder fish ticket numbers should start with a letter other than "I".
- Importable fish ticket numbers can be obtained from the eLandings system prior to creating the report XML document. This allows the seafood processor's system to obtain the fish ticket number prior to the landing, and to use them as key data in their internal records. When importing the landing report, the eLandings system will recognize the fish ticket numbers as importable numbers, and will not replace them with newly generated ones. Importable fish ticket numbers always begin with the letter "I". Importable fish ticket numbers can be obtained using the Importable Numbers page. It is accessible from the Operation Information and User Maintenance page by clicking on the "Importable Fish Ticket Numbers" button.
Warning |
---|
Fish ticket numbers can be retrieved as importable numbers from Operation page, get importable numbers button.
...