Attempts to save a landing report in the database. Report Status is changed from un-submitted or initial submitted to final submitted, if it has not already been changed. The report is validated according to the rules associated with the final submit report status.

eLandings allows users to save a landing report in one of four states. These report status types are:

1 = NOT SUBMITTED
4 = INITIAL REPORT SUBMITTED
8 = FINAL REPORT SUBMITTED
16 = REPORT DELETED -- NOTE: Reports are marked as deleted but retained in the database for a historic record. Some users refer to this as "voiding" the report.

If a landing report is saved with a ReportStatus = 1 (Not Submitted), the data is stored in a clob in the database. This allows users to save unsubmitted reports in an incomplete or incorrect state. All other report status will trigger the report to be saved in the traditional report tables and columns.
When the submitFinalLandingReport() is called, the landing report is validated against final submission business rules. If the report was previously saved in the Not Submitted status as a clob, that data is now deleted. The landing report status is changed to ReportStatus = 8 (FINAL REPORT SUBMITTED). Finally the data is stored in the database tables.

The submitFinalLandingReport() takes four arguments:

String Userid – i.e "amarx"
String password – i.e. "A_marx"
String schemaVersionNumber – i.e. "2.1"
String landingReportInXmlDataFormat – see below for example of long string

In the web service client we might auto generate a data structure by providing the web service url. In eLandings we use Java – JAX-WS and generated a structure called ReportManager.
ReportManagement ws;
...
...
String xml = ws. submitFinalLandingReport (userid, password, schemaVersionNumber, landingReportInXmlDataFormat);
Or

submitFinalLandingReport_method_call_example.txt

If the web service call was successful you might see a string containing the landing report that you submitted. The Report Status should be changed to 8. So you would see something like this:

submitFinalLandingReport_results_on_success.txt

If the web service call was unsuccessful you should receive a string containing XML for an empty landing_report structure containing one or more messages documenting errors that were encountered when processing your request. For example you might receive something like:

submitFinalLandingReport_results_on_failure.txt

For the list of potential elandings messages see the elandings codes page and click on Message Codes

Browser not supported