This method returns a full production report record as a string in XML format as defined by the XSD definition for Production_Report object in productionreport.xsd.
The getProductionReport() 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 productionReportID - i.e. ¿3408¿
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.getProductionReport(userid, password, schemaVersionNumber, productionReportID);
For example: In eLandings, if you were to click on the link for Production report 3408:
eLandings would call the web service using:
String xml = ws.getLandingReport(¿amarx¿, ¿A_marx¿, ¿2.1¿, ¿3408¿);
If the web service call was successful you might see a string containing a production_report xml object:
getLandingReport_results_on_success.txt
This string can then be parsed using the productionreport.xsd definition for a production_report object into a data object that Java, C#, Visual Basic, etc. can work with in memory.
The eLandings web pages display this data as:
Alternatively, if an error was encountered in the web service while processing your request, you should get a string containing XML for a production_report containing one or more messages elements. These messages will define what error or errors were encountered in the web services.
For example, if your request was for productionReportId=1000 and if that id did not exist in the database, you might receive the following response string from the web service call:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<production_report>
<messages>
<message severity_desc="ERROR" severity_code="E" msgid="1472">Production Report 1000 not found</message>
</messages>
<schema_version>2.1</schema_version>
</production_report>
eLandings would display this error as:
