...
- 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. However, the web service will not save xml objects that cannot be parsed into a landing report object. This is the minimum standard of a save event in an unsubmitted state. All other report status' will trigger the report to be saved in the traditional report tables and columns.
...
- 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. saveLandingReport (userid, password, schemaVersionNumber, landingReportInXmlDataFormat);
Or
saveLandingReport_method_call_example.txt
...
saveLandingReport_results_on_error.txt
For the list of potential elandings messages see the elandings codes page and click on Message Codes