Attempts to save a production 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 three states. These report status types are:
¿ 1 = NOT SUBMITTED
¿ 8 = FINAL REPORT SUBMITTED
¿ 16 = REPORT DELETED
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.
The submitProductionReport() takes four arguments:
1. String Userid ¿ i.e ¿amarx¿
2. String password ¿ i.e. ¿A_marx¿
3. String schemaVersionNumber ¿ i.e. ¿2.1¿
4. String productionReportInXmlDataFormat ¿ 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. submitProductionReport(userid, password, schemaVersionNumber, productionReportInXmlDataFormat);
Or
<SAMPLE_CODE_CALL>
If the web service call was successful you might see a string containing the production report that you submitted. The report status should have changed to final report submitted 8 So you would see something like this:
<SAMPLE_CODE_SUCCESS>
If the web service call was unsuccessful you should receive a string containing XML for an empty production_report structure containing one or more messages documenting errors that were encountered when processing your request. For example if you tried to save a production report with three stat areas defined as such:
¿ Stat Area = 355401, Percent = 40
¿ Stat Area = 355430, Percent = 60
¿ Stat Area = -10, Percent = 30
Clearly a stat area of -10 doesn¿t exist and is illegal. Furthermore the total percentage should add up to 100 but it adds up to 130.
If called the web service with:
<SAMPLE_CODE_ERROR_CALL>
As a result, when we try to save this production report we might receive something like:
<SAMPLE_CODE_ERROR_RESULT>