Liidese arendajatele: liideste kaudu pakutavate teenuste kirjeldus (inglise keeles)

Table of Contents:

1       Description

2       General concept of integration

2.1         External commercial systems

2.1.1          Primary protocol
2.1.2          XML message format
2.1.3          Securing queries
2.1.4          Authentication and authorization
2.1.5          Localization
2.1.6          Input and output
2.1.7          Modification of records
2.1.8          Locations (WSDL, XSD, STS)
2.1.9          Brief description of services
2.1.10        Other relevant information
2.1.11        Queries
2.1.12        Schema

2.2         State information systems (X-road)

2.2.1          Authentication and authorization

2.3         Web services over the X-road provided by ELVIS to state information systems

3       Queries offered to external commercial systems

3.1         Query of an assortment classifier: GetAssortmentTypes ()
3.2         Warehouse

3.2.1          Insert warehouse: InsertWarehouse ()
3.2.2          Deliver warehouse data: GetWarehouse ()
3.2.3          Search warehouse: SearchWarehouse ()
3.2.4          Delete warehouse: DeleteWarehouse ()

3.3         Transport order

3.3.1          Insert transport order: InsertTransportOrder ()
3.3.2          Get detailed data of a transport order: GetTransportOrder ()
3.3.3          Search transport order: SearchTransportOrders ()
3.3.4          Get transport order status: GetTransportOrderStatus ()
3.3.5          Change transport order status: SetTransportOrderStatus ()

3.4         Waybill

3.4.1          Insert a waybill: InsertWayBill ()
3.4.2          Get detailed data of a waybill: GetWayBill ()
3.4.3          Search a waybill: SearchWaybill ()
3.4.4          Get a waybill’s status: GetWaybillStatus ()
3.4.5          Change a waybill status: SetWaybillStatus ()
3.4.6          Changing of  waybill destination with „Confirmed“ status TO BE SPECIFIED
3.4.7          Insert received assortment: InsertReceptionAssortment ()
3.4.8          Delete received assortment: DeleteReceptionAssortment ()
3.4.9          Insert fine measurement data: InsertFinemeasurementAssortment ()
3.4.10        Delete fine measurement assortment: DeleteFinemeasurementAssortment ()
3.4.11        Insert a fine measurement file: InsertFinemeasurementFile ()
3.4.12        Delete a fine measurement file: DeleteFinemeasurementFile ()

3.5         Data types

Description

This document is intended as a manual for integrating external systems with the ELVIS e-waybill system. The document describes the content of services provided by ELVIS, including specifications for all validation rules, classifiers, etc.

If necessary, the system analyst of the integrating party can prepare a more detailed document for the developer.

Readers are required to have basic knowledge of HTTP Protocol, XML-Schema and SOAP technology.

The following references gives a more detailed technical overview of the functioning principles of web services:

  1. What’s a web service: http://en.wikipedia.org/wiki/Web_service
  2. How to read a description of a web service: http://en.wikipedia.org/wiki/Web_Services_Description_Language
  3. Overview of XML Schema: http://en.wikipedia.org/wiki/XML_schema
  4. How to exchange information with web services: http://en.wikipedia.org/wiki/SOAP

2 General concept of integration

2.1 External commercial systems

Commercial systems can integrate with ELVIS (to write and read data) by addressing web services directly. You can find exemplifying code of an integration written in C-sharp (including full WSDL description under \Service References\ElvisPublicService\ElvisPublicService.wsdl) in the following attachment:

ElvisTestAppGetWayBill.zip

2.1.1 Primary protocol

Messages are exchanged in SOAP-format - technically these are SSL-secured (HTTPS) HTTP POST-type queries. All queries use the UTF-8 encoding.

2.1.2 XML message format

Standard SOAP 1.2 XML messages in container format are supported. Content of a message is validated by XML Schema. SOAP 1.2 is recommended by W3C.

2.1.3 Securing queries

Queries are secured by a message level encryption.

2.1.4 Authentication and authorization

The Security Token Service (STS) is used for user authentication. Service location: http://www.veoseleht.ee/STS/Service.svc/IWSTrust13Public. User's personal ID code is sent to STS in the message header, i.e. "PersonCode" element with namespace "http://www.veoseleht.ee/" has been added to RequestSecurityToken element, and PersonCode element is valued with user’s ID-code (the exact structure is described in WSDL – please see the attachment under “2.1 General concept of integration”; the service and the STS-certificate are currently under the name "localhost".

STS will provide all necessary information about the user (user name, roles, companies, etc), which a certain service requires about the user, and the user’s access to the resources of this service system limited based on this information. ELVIS users’ role management takes place in AAR (Authentication and Authorization service). The function of STS is to identify the user and to provide the user with necessary verified claims for his/her authorization. STS gets claims about the roles from the AAR service. A user may use the web service only if the rights are granted. Additional information about authentication and user rights is described in the document about architecture.

Steps for using the service:
Required steps for compiling queries and services for the use of services are described in the article "Authentication and authorization." Find below the necessary steps for using ELVIS services.

  1. User installs the certificate into „CurrentUser/Personal/Certificates“(Windows computer) or into some other location, where it is available for the application, which is using the service. Without a certificate it is not possible to make a query to the security token service.

    The credentials of authentication for the test-environment:

 

  1. User application makes a query to the security token service for receiving a security token. As a result the security token is issued for the user. Personal ID-code is added to the query message (more detailed description can be found in article "Authentication and Authorization).
    Description of security token service: http://www.veoseleht.ee/STS/Service.svc?wsdl (for full description please see the attachment under “2.1 General concept of integration”)
  2. User sends queries to ELVIS services using for authorization the security token, which is issued to him beforehand. Description of ELVIS service: http://www.veoseleht.ee/STS/Service.svc?wsdl.

2.1.5 Localization

Localization information is provided in the SOAP message header in the culture-attribute. For Estonia the default value is: ’et-EST’. Namespace is missing.

2.1.6 Input and output

All services are initiated by external systems. The input data are all data, which are provided to ELVIS by the external systems. The output data are all data returned by ELVIS to the external systems. The input and output of each service is described at the description of the service.

Responses to some queries may contain a very large number of records, which in turn have a very complex data structure. In such a case the returned records are divided into pages / paginated. In case of pagination, it is determined on how many pages the results are divided, as well as the maximum number of results per one page; additionally the total number of detected records is returned. The user may determine by input data, which results should be presented on each page.

2.1.7 Modification of records

When an object is going to be modified in ELVIS, the external system must provide the version number of the record, which is going to be modified. For that purpose the external system must first inquire from ELVIS information about that object. For example, for inserting a note about inspection of a waybill, first the data of the waybill must be inquired (these data are returned with the waybill version number). When inserting the inspection note, the waybill version number is provided, where the inspection note is going to be marked. It is necessary for the management of ConcurrencyFaults.

If the modification or deletion of the record fails, the fault parameter is returned to the output. In case the modification and deletion are successful, nothing is returned to the output.

In ELVIS the value of each classifier has its unique value code. The value of each classifier belongs to a certain classifier group. The external systems must know the predetermined codes of classifiers’ values. Classifiers for a service are partly provided as enumerations (See http://www.w3.org/TR/2001/WD-soap12-20010709/#_Toc478383516).

 

Example:

Figure1_-_Example_of_numeration_-_w3_org.jpg

 

Below a list of classifiers, which are not presented as Enumerations (as the setup might get updated in live/production environment, then please request the updated list from the service provider)

Classifiers’ group

Classifier’s ID

Classifier’s value

Supply Chain Certificates

2001

SupplyChainCertificate1

 

2002

SupplyChainCertificates2

Timber Management Certificates

3001

TimberManagementCertificate1

 

3002

TimberManagementCertificate2

Warehouse Types Group

5001

Forest edge warehouse / roadside warehouse

 

5002

Interim warehouse

 

5003

End warehouse

Basis for holding

6001

Forest Act § 41 (14)

 

6002

Forest notification

 

6003

Transfer of the cutting right

 

6004

Transfer of timber

 

6005

Inventory

 

6006

Summary report

Forest districts

8001

Forest district 1

 

8002

Forest district 2

Insert types

25001

Vessel

 

25002

Train

 

25003

Transport contract

 

25004

Delivery contract

 

25005

Freighter

 

25006

Reception

 

25007

Landowner

 

25008

Other

Measurement unit

14001

Cubic meter

 

In case an error occurs when using the service, the error information is returned within a SOAP element. Most common errors, which can occur in ELVIS context, are:

 

ConcurrencyFault

Structure:
ConcurrencyFault.png

Description: the error message is returned in case of a conflict of simultaneous processes.

 

KeyViolationFault

Structure:
KeyViolationFault.png

Description: systemic error.

 

SqlFault

Structure:

SqlFault.png

Description: systemic error.

 

ValidationFault

Structure:

ValidationFault.png

Description: error information is returned in case of a failure of validation of service parameters

 

Service

Structure:

 Service.png

 Service.jpg

Namespace

All services are located in namespace „http://www.veoseleht.ee/Service/“.

2.1.8 Locations (WSDL, XSD, STS)

Service location:

  1. http://www.veoseleht.ee/Service/ElvisPublicService.svc

WSDL location:

  1. http://www.veoseleht.ee/Service/ElvisPublicService.svc?wsdl (for full description please see the attachment under “1 General concept of integration”)

XSD locations:

  1. http://www.veoseleht.ee/Service/ElvisPublicService.svc?xsd=xsd0
  2. http://www.veoseleht.ee/Service/ElvisPublicService.svc?xsd=xsd1
  3. http://www.veoseleht.ee/Service/ElvisPublicService.svc?xsd=xsd2
  4. http://www.veoseleht.ee/Service/ElvisPublicService.svc?xsd=xsd3
  5. http://www.veoseleht.ee/Service/ElvisPublicService.svc?xsd=xsd4
  6. http://www.veoseleht.ee/Service/ElvisPublicService.svc?xsd=xsd5
  7. http://www.veoseleht.ee/Service/ElvisPublicService.svc?xsd=xsd6
  8. http://www.veoseleht.ee/Service/ElvisPublicService.svc?xsd=xsd7
  9. http://www.veoseleht.ee/Service/ElvisPublicService.svc?xsd=xsd8
  10. http://www.veoseleht.ee/Service/ElvisPublicService.svc?xsd=xsd9
  11. http://www.veoseleht.ee/Service/ElvisPublicService.svc?xsd=xsd10

STS location:

  1. http://www.veoseleht.ee/STS/Service.svc/IWSTrust13Public

 

2.1.9 Brief description of services

  1. GetAssortmentTypes (): the service returns the array of assortment classifiers
  2. InsertWarehouse (): the service creates a warehouse, returns the identifier
  3. GetWarehouse (): the service queries a warehouse, which is correspondent to a predetermined identifier
  4. SearchWarehouse (): the service returns an array of warehouse identifiers corresponding to predetermined parameters
  5. DeleteWarehouse (): the service deletes a warehouse
  6. InsertTransportOrder (): the service creates a transport order, returns the number of transport order
  7. GetTransportOrder (): the service queries detailed data of a transport order corresponding to predetermined identifiers
  8. SearchTransportOrders (): the service returns an array of transport orders identifiers corresponding to predetermined parameters
  9. GetTransportOrderStatus (): the service returns a transport order status corresponding to a predetermined transport order number
  10. SetTransportOrderStatus (): the service changes status of a transport order corresponding to a predetermined transport order number
  11. InsertWaybill (): the service creates a waybill, returns the number of the waybill
  12. GetWaybill (): the service queries detailed data of a waybill corresponding to a predetermined waybill number
  13. SearchWaybills (): the service returns an array of waybills’ identifiers corresponding to predetermined parameters
  14. GetWaybillStatus (): the service requests a waybill status corresponding to a predetermined waybill number
  15. SetWaybillStatus (): the service changes the status of a waybill corresponding to a predetermined waybill number
  16. InsertReceptionAssortment (): the service creates an assortment of received products on the waybill, returns with an inserted assortment identifier
  17. DeleteReceptionAssortment (): the service deletes the received assortment
  18. InsertFinemeasurementAssortment (): the service creates a fine measured assortment on the waybill, returns with an inserted fine measured assortment identifier
  19. DeleteFinemeasurementAssortment (): the service deletes a fine measurement assortment from the waybill
  20. InsertFinemeasurementFile (): the service creates a fine measurement file on a waybill, returns with an inserted file identifier
  21. DeleteFinemeasurementFile (): the service deletes a fine measurement file from the waybill

2.1.10 Other relevant information

  1. Input arrays must always be initialized. Array elements may be missing.

2.1.11 Queries

Encoding

The encoding system for queries is UTF-8

Structure

The structure of all SOAP messages is determined by the XML Schema of the corresponding service. Input and output validation are also measured against it.

2.1.12 Schema

Schema.png

2.2 State information systems (X-road)

State information systems (primarily those inspection bodies that need to have unrestricted access to data according to law – like the Police and Border Guard Board, Tax Board) can make queries (only read data, not insert/update/delete) over the X-road.

2.2.1 Authentication and authorization

No separate authentication is required for state information services that are using the X-road Data Exchange Layer for exchanging data; the authorization takes place via STS Service. In such a case additional information about authorization is not required for integration.

2.3      Web services over the X-road provided by ELVIS to state information systems

1.1          Query of simple data from Police Department

1.2          Query of detailed data from Police Department

1.3          Tax Board

3 Queries offered to external commercial systems

3.1 Query of an assortment classifier: GetAssortmentTypes ()

Description: assortment classifiers are queried, the array of basic classifiers / company's specific classifiers is returned.

Stream:

  1. The external system turns to ELVIS querying assortment classifiers
  2. ELVIS returns assortment classifiers (depending on input information also basic / specific classifiers)
    1. Alternative: information about failure is returned

Typical usage scenario: the elements of the array of classifiers are used for describing timber in documents.

 Input
When the entry is Enum („Elvis“), all basic classifiers are returned, when the entry is Enum („Company“), only the specific classifiers of a respective company are returned.

 Structure

GetAssortmentTypes_Input.jpg

Description

Name

Tag

Mandatory

Type

Validation

Type

Type

YES

AssortmentTypeType

Enum („Elvis“)
Enum („Company“)

 Text string

<xs:element name="GetAssortmentTypes">
    <xs:complexType>
      <xs:sequence>
        <xs:element minOccurs="0" name="type" type="q20:AssortmentTypeType"
          xmlns:q20="http://schemas.datacontract.org/2004/07/EMTL.Elvis.DTO.AssortmentType"
        />
      </xs:sequence>
    </xs:complexType>
  </xs:element>

 Output
Structure

GetAssortmentTypes_Output.jpg

Description

Name

Tag

Mandatory

Type

Validation

Result

GetAssortmentTypesResult

NO

ArrayOfAssortmentType

 

 Text string

<xs:element name="GetAssortmentTypesResponse">
    <xs:complexType>
      <xs:sequence>
        <xs:element minOccurs="0" name="GetAssortmentTypesResult" nillable="true"
          type="q21:ArrayOfAssortmentType"
          xmlns:q21="http://schemas.datacontract.org/2004/07/EMTL.Elvis.DTO.ElvisPublicService"
        />
      </xs:sequence>
    </xs:complexType>
  </xs:element>

 Business rules:

  1. The array of basic classifiers is returned to all parties
  2. The array of company's specific classifiers is returned to its owner only

3.2 Warehouse

3.2.1 Insert warehouse: InsertWarehouse ()

Description: Basic warehouse information is prepared in an external system and sent to ELVIS. As a result a new warehouse record is created in ELVIS containing basic data.

 Input

Description

Name

Tag

Mandatory

Type

Validation

Warehouse

Warehouse

NO

Shipment

 

Output

Description

Name

Tag

Mandatory

Type

Validation

Result

InsertWarehouseResult

NO

String

 

 Business rules

  1. Holding data don't have to be linked to the warehouse
  2. Assortment doesn't have to be linked to the holding data
  3. The amount of described assortment has to be greater than 0

3.2.2 Deliver warehouse data: GetWarehouse ()

Description: Detailed data of a queried transport order are returned on basis of predetermined identifier. The result is an array of detailed data of warehouses 0…1

Input

Description

Name

Tag

Mandatory

Type

Validation

Warehouse ID

Number

NO

String

 

Output

Description

Name

Tag

Mandatory

Type

Validation

Result

GetWarehouseResult

NO

Warehouse

 

 

Business rules

  1. Unnecessary warehouse is returned only to the owner (control on basis of a CompanyRegistrationNumber)

3.2.3 Search warehouse: SearchWarehouse ()

Description: An array of warehouses' identifiers is queried on basis of predetermined parameters

Input

Description

Name

Tag

Mandatory

Type

Validation

Context

RoleContext

YES

WarehouseRoleContext

 

Search Criteria

RestrictionItems

NO

ArrayOfWarehouseRestrictionItem

 

Sorting

SortItems

NO

ArrayOfWarehouseSortItem

 

Sample start position

Skip

YES

Integer

 

Amount

Take

YES

Integer

 

Returning the value of total amount

GetCount

YES

Boolean

 

 Output

Description

Name

Tag

Mandatory

Type

Validation

Result

SearcWarehouseResponse

YES

WarehouseListPage

 

 Business rules

  1. Unnecessary warehouse is returned only to the owner (control on basis of a Warehouse.CompanyRegistrationNumber)

3.2.4 Delete warehouse: DeleteWarehouse ()

Description: the service deletes a warehouse record on basis of a warehouse identifier, which is predetermined by an external system. The result is a logical deletion of a warehouse

Input

Description

Name

Tag

Mandatory

Type

Validation

Id

Id

YES

Integer

 

 Output

  1. In case of a failure there is an error message. If there is no failure, nothing is returned.

 Business rules

  1. Only warehouse belonging to the user can be deleted (control based on a CompanyRegistrationNumber)

 

3.3 Transport order

3.3.1 Insert transport order: InsertTransportOrder ()

Description: the service inserts a prepared transport order into ELVIS.

Subscriber of the transport prepares a full transport order in an external system and sends the data to ELVIS. One transport order at a time may be inserted. In case of a successful transfer, the transport order number is returned; in case of a failure an error message is returned. Prerequisite: transport order is previously fully prepared.

Input

Structure

InsertTransportOrder_Input.jpg

Description

Name

Tag

Mandatory

Type

Validation

Transport order

Order

NO

TransportOrder

 

Text string

<xs:element name="InsertTransportOrder">
    <xs:complexType>
      <xs:sequence>
        <xs:element minOccurs="0" name="order" nillable="true" type="q12:TransportOrder"
          xmlns:q12="http://schemas.datacontract.org/2004/07/EMTL.Elvis.DTO.ElvisPublicService"
        />
      </xs:sequence>
    </xs:complexType>
  </xs:element>

Output

Structure

InsertTransportOrder_Output.jpg

Description

Name

Tag

Mandatory

Type

Validation

Result

InsertTransportOrderResult

NO

String

 

 

Text string

<xs:element name="InsertTransportOrderResponse">
    <xs:complexType>
      <xs:sequence>
        <xs:element minOccurs="0" name="InsertTransportOrderResult" nillable="true"
          type="xs:string"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>

 

Business rules

  1. A transport order can be inserted only by a person described on the transport order as an owner of timber.

 3.3.2 Get detailed data of a transport order: GetTransportOrder ()

Description: Detailed data of a transport order are returned based on a predetermined transport order number. The result is an array of detailed data of transport orders 0…1                           

 Input

Structure

GetTransportOrder_Input.jpg

Name

Tag

Mandatory

Type

Validation

Transport order number

Number

NO

String

 

Description

Output
Structure

GetTransportOrder_Output.jpg

Description

Name

Tag

Mandatory

Type

Validation

Result

GetTransportOrderResult

NO

TransportOrder

 

 

Business rules

  1. Transport order is returned only to an involved party (owner of timber, transporter and receiver)

 

3.3.3 Search transport order: SearchTransportOrders ()

Description: query of an array of transport orders' identifiers based on predetermined parameters. In case of successful query an array of transport orders is returned (element including essential information, see detailed description of output), in case of failure, error message is returned.

Input

Structure

SearchTransportOrders_Input.jpg

Description

Name

Tag

Mandatory

Type

Validation

Context

RoleContext

YES

TransportOrderRoleContext

Enum („Owner“)
Enum („Reciever“)
Enum („Transporter“)

Search Criteria

RestrictionItems

NO

ArrayOfTransportOrderRestrictionItem

 

Sorting

SortItems

NO

ArrayOfTransportOrderSortItem

 

Sample start position

Skip

YES

Integer

 

Amount

Take

YES

Integer

 

Returning the value of total amount

GetCount

YES

Boolean

 

Text string

<xs:element name="SearchTransportOrders">
    <xs:complexType>
      <xs:sequence>
        <xs:element minOccurs="0" name="roleContext" type="q16:TransportOrderRoleContext"
          xmlns:q16="http://schemas.datacontract.org/2004/07/EMTL.Elvis.DTO.TransportOrder"/>
        <xs:element minOccurs="0" name="restrictionItems" nillable="true"
          type="q17:ArrayOfTransportOrderRestrictionItem"
          xmlns:q17="http://schemas.datacontract.org/2004/07/EMTL.Elvis.DTO.ElvisPublicService"/>
        <xs:element minOccurs="0" name="sortItems" nillable="true"
          type="q18:ArrayOfTransportOrderSortItem"
          xmlns:q18="http://schemas.datacontract.org/2004/07/EMTL.Elvis.DTO.ElvisPublicService"/>
        <xs:element minOccurs="0" name="skip" type="xs:int"/>
        <xs:element minOccurs="0" name="take" type="xs:int"/>
        <xs:element minOccurs="0" name="getCount" type="xs:boolean"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>

Output

Structure

SearchTransportOrders_Output.jpg

Description

Name

Tag

Mandatory

Type

Validation

Result

SearchTransportOrdersResult

NO

TransportOrderListPage

 

Text string

 <xs:element name="SearchTransportOrdersResponse">
    <xs:complexType>
      <xs:sequence>
        <xs:element minOccurs="0" name="SearchTransportOrdersResult" nillable="true"
          type="q19:TransportOrderListPage"
          xmlns:q19="http://schemas.datacontract.org/2004/07/EMTL.Elvis.DTO.ElvisPublicService"
        />
      </xs:sequence>
    </xs:complexType>
  </xs:element>

Business rules

  1. Transport order is returned only to an involved party (owner of timber, transporter and receiver)

3.3.4 Get transport order status: GetTransportOrderStatus ()

Description: transport order status and version are returned on base of a predetermined transport order number, in case of failure an error message is returned showing the failure information.

Stream:

  1. An external system turns to ELVIS with a query about status of a transport order
  2. ELVIS returns data of the transport order to be changed
    1. Alternative: information about failure is returned

Typical usage scenario: Status information has to be queried before changing the status information

There are following statuses of transport order existent in ELVIS:

Id

Status

Description

4001

Composing

Transport order is not confirmed by the owner of the timber or  owner's representative

4002

Submitted

Transport order is confirmed by the owner of the timber or owner's representative and is visible to the transporter

4003

Accepted

Transport order is accepted by the transporter of the timber, the transport has not been started

4004

Declined

Transport order is not accepted by the transporter of the timber

4005

Finalized

Transport order is executed by the transporter of the timber, the transport is finished

4006

Cancelled

Transport order is cancelled by the transporter of the timber. There are no waybills linked to the transport order (status either "Approved", "Transportation finished", "Received", "Measured", "Measurement approved“ or "Finished")

Input

Structure

GetTransportOrderStatus_Input.jpg

Description

Name

Tag

Mandatory

Type

Validation

Transport order number

Number

NO

String

 

Output

Structure

GetTransportOrderStatus_Output.jpg

Description

Name

Tag

Mandatory

Type

Validation

Result

GetTransportOrderStatusResult

NO

TransportOrderStatusInfo

 

Business rules

  1. The transport order is returned only to an involved party (owner of timber, transporter and receiver)
  2. The Receiver sees the transport order with a finalized set of terms: StatusId = = “Composing“ && TransportOrder.IsVisible = = „TRUE“

3.3.5 Change transport order status: SetTransportOrderStatus ()

Description: Changing the status of a transport order existent in ELVIS:

The following status changes are available:

  1. „Submitted“ -> „Accepted“
  2. „Submitted“ -> „Declined“
  3. „Submitted“ -> „Cancelled“
  4. „Accepted“ -> „Finalized“
  5. „Accepted“ -> „Cancelled“

Stream:

  1. An external system queries ELVIS for the data, which is going to be changed (using service GetTransportOrder () or GetTransportOrderlStatus ())
  2. ELVIS returns data of the transport order, which is going to be changed
    1. Alternative: information about failure is returned
  3. An external system turns to ELVIS with a request to change a transport order status
  4. The transport order status is changed in ELVIS
    1. Alternative: information about failure is returned

Status change is also used, when the transport order data needs to be changed. In such a case an active transport order is cancelled and a new one is created using respective method.

When changing a status, the business logic rules of ELVIS have to be taken into account. In case of failure, ELVIS issues a respective failure message.

Transport order statuses:

Id

Status

Description

4001

Composing

Transport order is not confirmed by the owner of the timber or owner's representative Not actual status for an external system

4002

Submitted

Transport order is confirmed by the owner of the timber or owner's representative and is visible to the transporter

4003

Accepted

Transport order is accepted by the transporter, the transport has not been started

4004

Declined

Transport order is not accepted by the transporter

4005

Finalized

Transport order is executed by the transporter of the timber, the transport is finished

4006

Cancelled

Transport order is cancelled by the transporter of the timber. There are no waybills related to the transport order (status either "Approved", "Transportation finished", "Received", "Measured", "Measurement approved“ or "Finished")

The status of a transport order can be changed as follows:
Transport_order_statuses_and_changing.jpg

Input

Structure

SetTransportOrderStatus_Input.jpg

Description

Name

Tag

Mandatory

Type

 

Transport order number

TransportOrderNumber

NO

String

 

Status

Status

YES

TransportOrderStatus

 

Feedback

Feedback

NO

String

 

Version

Version

NO

Base64Binary

 

Output

Structure

SetTransportOrderStatus_Output.jpg

  1. Missing
    1. Alternative: in case of failure information about a waybill error

Business rules

  • „Submitted“ -> „Accepted“
    • Status is "Submitted"
    • Transport order contains at least 1 starting point
    • Starting point contains at least 1 holding data
    • Holding data contain at least 1 assortment
    • The amount of assortment is greater than 0
    • Transport order contains a receiver
    • Transport order contains a destination
    • Transport order contains a transporter
    • There is at least 1 transport executer
    • The description of an executer contains at least a vehicle and a driver.
    • Partially allowed operations, determined in company's settings CompanyData.IsPartialOperationsAllowed, according to which the operations for the group's transport orders are held partially/ wholly
    • A group consists of transport orders of one company
    • Group's transport orders are submitted to one transporter
    • Actor is a transporter
  • „Submitted“ -> „Declined“
    • Status is "Submitted"
    • Transport order contains at least 1 starting point
    • Starting point contains at least 1 holding data
    • Holding data contain at least 1 assortment
    • The amount of assortment is greater than 0
    • Transport order contains a receiver
    • Transport order contains a destination
    • Transport order contains a transporter
    • Submitting feedback is mandatory
    • Partially allowed operations, determined in company's settings CompanyData.IsPartialOperationsAllowed, according to which the operations for the group's transport orders are held partially/ wholly
    • Group consists of transport orders of one company
    • Group's transport orders are submitted to one transporter
    • Actor is a transporter
  • „Submitted“ -> „Cancelled“
    • Status is "Submitted"
    • Submitting feedback is mandatory
    • Transport order contains at least 1 starting point
    • Starting point contains at least 1 holding data
    • Holding data contain at least 1 assortment
    • The amount of assortment is greater than 0
    • Transport order contains a receiver
    • Transport order contains a destination
    • Transport order contains a transporter
    • Transport order doesn't contain waybills
    • Partially allowed operations, determined in company's settings CompanyData.IsPartialOperationsAllowed, according to which the operations for the group's transport orders are held partially/ wholly
    • Group consists of transport orders of one company
    • Group's transport orders are submitted to one transporter
    • Actor is timber's owner or transporter
  • „Accepted“ -> „Finalized“
    • Status is "Accepted"
    • Transport order contains at least 1 starting point
    • Starting point contains at least 1 holding data
    • Holding data contain at least 1 assortment
    • The amount of assortment is greater than 0
    • Transport order contains a receiver
    • Transport order contains a destination
    • Transport order contains a transporter
    • There is at least 1 transport executer
    • The transport executer has at least one mandatory driver and a vehicle
    • Actor is a transporter
  • „Accepted“ -> „Cancelled“
    • Status is "Accepted"
    • Submitting feedback is mandatory
    • Transport order contains at least 1 starting point
    • Starting point contains at least 1 holding data
    • Holding data contain at least one assortment
    • The amount of assortment is greater than 0
    • Transport order contains a receiver
    • Transport order contains a destination
    • Transport order contains a transporter
    • There is at least 1 transport executer
    • Transport executer has at least a mandatory driver and a vehicle
    • Partially allowed operations, determined in company's settings CompanyData.IsPartialOperationsAllowed, according to which the operation for the group's transport orders is held partially/ wholly
    • A group consists of transport orders of one company
    • A group's transport orders are submitted to one transporter
    • Actor is a transporter

3.4 Waybill

3.4.1 Insert a waybill: InsertWayBill ()

Description: ELVIS waybill is created on the basis of predetermined data. In case of success, a waybill number is returned; in case of failure an error message is returned. Prerequisite: waybill is previously fully prepared.

Input

Structure

InsertWayBill_Input.jpg

Description

Name

Tag

Mandatory

Type

Validation

Waybill

Waybill

NO

Waybill

 

Output

Structure

InsertWayBill_Output.jpg

Description

Name

Tag

Mandatory

Type

Validation

Result

InsertWaybillResult

NO

String

 

Business rules

  • Composed waybill must include:
    • Timber owner
    • Person authorized by the timber owner
  • Approved waybill must include in addition to the validation rules of the composed waybill:
    • At least 1 starting point
    • Starting point must be related to at least 1 holding data
    • Holding data must contain at least 1 assortment
      • The amount of assortment has to be greater than 0
    • Destination
    • Receiver
    • Transporter
  • The amount of assortment has to be greater than 0
  • Transport order can be inserted only by a person described on a waybill either as an owner of timber or as a transporter.

3.4.2 Get detailed data of a waybill: GetWayBill ()

Description: Detailed data of a waybill are returned based on a predetermined waybill number. The result is an array of detailed data of waybills 0…1

Input

Structure

GetWayBill_Input.jpg

Name

Tag

Mandatory

Type

Validation

Waybill number

Number

NO

String

 

Description

Example (without message header):

<SOAP-ENV:Envelope xmlns:SOAP-ENV“"http://www.w3.org/2003/05/soap-envelop“" xmlns:SOAP-ENC“"http://www.w3.org/2003/05/soap-encodin“" xmlns:xsi“"http://www.w3.org/2001/XMLSchema-instanc“" xmlns:xsd“"http://www.w3.org/2001/XMLSchem“">

                <SOAP-ENV:Body>

                               <m:GetWaybill xmlns:m“"http://tempuri.org“">

                                               <m:Number>0</m:Number>

                               </m:GetWaybill>

                </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Output

Structure

GetWayBill_Output.jpg

Description

Name

Tag

Mandatory

Type

Validation

Result

GetWayBillResult

NO

Waybill

 

Notes

The service doesn't guarantee operation with the following Destination elements:

  1. Appropriation
  2. ForestDistrictId
  3. Longitude
  4. Latitude
  5. LambertEstX
  6. LambertEstY
  7. Quarter

 

Business rules

  1. Waybill is returned only to an involved party (owner of timber, transporter and receiver)

3.4.3 Search a waybill: SearchWaybill ()

Description: query of an array of waybills' identificators based on predetermined parameters

Input

Structure

SearchWaybill_Input.jpg

Description

Name

Tag

Mandatory

Type

Validation

Context

RoleContext

YES

WaybillRoleContext

 

Search Criteria

RestrictionItems

NO

ArrayOfWaybillRestrictionItem

 

Sorting

SortItems

NO

ArrayOfWaybillSortItem

 

Sample start position

Skip

YES

Integer

 

Amount

Take

YES

Integer

 

Returning the value of total amount

GetCount

YES

Boolean

 

Output

Structure

SearchWaybill_Output.jpg

Description

Name

Tag

Mandatory

Type

Validation

Result

SearchWaybillsResult

NO

WaybillListPage

 

Business rules

  1. Waybill is returned only to an involved party (owner of timber, transporter and receiver)

3.4.4 Get a waybill’s status: GetWaybillStatus ()

Description: waybill status and version are queried on basis of a waybill number.

Stream:

  1. An external system addresses ELVIS with a query of a waybill status
  2. ELVIS returns the data of a waybill to be changed
    1. Alternative: information about failure is returned

Typical use case: information about status is to be queried before changing of the status.

There are following statuses of waybill in ELVIS:

Id

Status

Description

7001

Composing

Waybill is saved, waybill is not confirmed by the driver

7002

Confirmed

Waybill is confirmed by the driver, timber is loaded on a truck, and transport is taking place.

7003

Transport finished/ unloaded

Driver has marked, that the load has reached the destination, timber is unloaded.

7004

Received

Timber is received, the drivers responsibility for the load has ended

7005

Measured

Timber is fine measured

7006

Measurement confirmed

Measurement has been confirmed by the receiver

7007

Finalized

Waybill is finalized/ closed, basic functions can't be performed. Waybill may be copied

7008

Cancelled

Waybill has been cancelled

Input

Structure

GetWaybillStatus_Input.jpg

Description

Name

Tag

Mandatory

Type

Validation

Waybill number

Number

NO

String

 

Text string

<xs:element name="GetWaybillStatus">
    <xs:complexType>
      <xs:sequence>
        <xs:element minOccurs="0" name="number" nillable="true" type="xs:string"/>
      </xs:sequence>
    </xs:complexType>
  </xs:element>

Output

Structure

GetWaybillStatus_Output.jpg

Description

Name

Tag

Mandatory

Type

Validation

Result

WayBillStatusResult

NO

WaybillStatusInfo

 

Text string

<xs:element name="GetWaybillStatusResponse">
    <xs:complexType>
      <xs:sequence>
        <xs:element minOccurs="0" name="GetWaybillStatusResult" nillable="true"
          type="q4:WaybillStatusInfo"
          xmlns:q4="http://schemas.datacontract.org/2004/07/EMTL.Elvis.DTO.ElvisPublicService"
        />
      </xs:sequence>
    </xs:complexType>
  </xs:element>

Business rules

  1. Data are returned only to a waybill party (owner of timber, transporter and receiver)

3.4.5 Change a waybill status: SetWaybillStatus ()

Description: Changing status of a waybill existent in ELVIS:

Stream:

  1. An external system addresses ELVIS querying data to be changed (using a service GetWayBill () or GetWaybillStatus ())
  2. ELVIS returns data of the waybill to be changed
    1. Alternative: information about failure is returned
  3. An external system addresses ELVIS with a request to change a waybill status
  4. The waybill status in ELVIS is changed
    1. Alternative: information about failure is returned

Status change is used also when the data on a transport order need to be changed. In such a case the active waybill is cancelled and a new one is created using respective method.

When changing status, the business logic rules of ELVIS have to be taken into account. In case of a failure, ELVIS issues a respective failure message.

There are following statuses of a waybill status present in ELVIS:

Id

Status

Description

7001

Composing

Waybill is saved, waybill is not confirmed by the driver

7002

Confirmed

Waybill is confirmed by the driver, timber is loaded on a truck, and transport is taking place.

7003

Transport finished/ unloaded

Driver has marked, that the load has reached the destination, timber is unloaded.

7004

Received

Timber is received, the drivers responsibility for the load has ended

7005

Measured

Timber is fine measured

7006

Measurement confirmed

Measurement has been confirmed by the receiver

7007

Finalized

Waybill is finalized/ closed, basic functions can't be performed. Waybill may be copied

7008

Cancelled

Waybill has been cancelled

Waybill status can be changed as follows:

Waybill_statuses_and_change_of_statuses.jpg

Input

Structure

SetWaybillStatus_Input.jpg

Description

Name

Tag

Mandatory

Type

 

Waybill number

WaybillNumber

NO

String

 

Status

Status

YES

WayBillStatus

 

Feedback

Feedback

NO

String

 

Pre journey length

PreJourneyLength

NO

Decimal

 

Total journey length

TotalJourneyLength

NO

Decimal

 

Measurement act number

MeasurementActNr

NO

String

 

Version

Version

NO

Base64Binary

 

Output

Structure

SetWaybillStatus_Output.jpg

  1. Missing
    1. Alternative: in case of failure information about waybill error

Business rules

  • Composing ->confirmed
    • There is a timber owner
    • There is a starting point
    • Starting point is related to at least 1 holding data
    • Holding data are related to at least one assortment
    • The amount of assortment is greater than 0
    • There is a destination
    • There is a receiver
    • There is a transporter
    • There is a transport executer (driver + vehicle)
    • Actor is a timber transporter
  • Confirmed -> unloaded in destination
    • Actor is a timber transporter
  • Confirmed -> Cancelled
    • Feedback is mandatory
    • Actor is a timber transporter
  • In destination, unloaded -> Received
    • Existence of holdingdata@received material
    • Existence of assortment@received material
    • The amount of received assortment is greater than 0
    • Actor is a timber transporter or a receiver
  • Received -> Measured
    • The amount of fine measured assortment is greater than 0, or there is a file related to fine measurement
    • Actor is a timber or a receiver
  • Received -> Finalized
    • Existence of at least 1 holdingdata@received material
    • Existence of 1 assortment@received material
    • The amount of assortment is greater than 0
    • Actor is a timber transporter or a receiver
  • Measured -> Measurement data confirmed
    • The amount of fine measured assortment is greater than 0, or there is a file related to fine measurement
    • Actor is a timber receiver
  • Measured -> Finalized
    • Existence of at least 1 holdingdata@received material
    • Existence of 1 assortment@received material
    • The amount of assortment is greater than 0
    • Actor is a timber receiver
  • Measurement data confirmed -> Finalized
    • Existence of holdingdata@received assortment
    • Existence of assortment@received assortment
    • The amount of received assortment is greater than 0
    • Actor is a timber receiver

3.4.6 Changing of  waybill destination with „Confirmed“ status TO BE SPECIFIED

Description: In the system there is a waybill with a destination, having status  "Confirmed". Destination on the waybill is going to be changed.

Input

  1. Waybill ID
  2. Waybill version number
  3. Destination ID

Output

In case of failure error message

3.4.7 Insert received assortment: InsertReceptionAssortment ()

Description: a record of received assortment is created. In case of successful insertion, a received assortment identifier is returned; in case of failure a failure message is returned.

Input

Structure

InsertReceptionAssortment_Input.jpg

Description

Name

Tag

Mandatory

Type

Validation

Possession data ID

TimberBatchId

YES

Integer

 

Forest Notice

TimberBatch.ForestNotice

NO

Varchar

 

Assortment:

Assortment:

NO

TimberAssortment

 

Output

Structure

InsertReceptionAssortment_Output.jpg

Description

Name

Tag

Mandatory

Type

Validation

Result

InsertReceptionAssortmentResult

YES

Integer

 

Business rules

  • The waybill status is ’in the Destination, unloaded’ [Enum,Unloaded’]
  • The use case performer is described on a waybill as a transporter or a receiver
  • The amount of assortment is greater than 0

3.4.8 Delete received assortment: DeleteReceptionAssortment ()

Description: the service deletes a received assortment record from ELVIS on basis of an identifier predetermined by an external system. The received assortment's deletion is logical. In case of successful deletion the output is missing, in case of failure there will be an error message.

Input

Structure

DeleteReceptionAssortment_Input.jpg

Description

Name

Tag

Mandatory

Type

Validation

Id

Id

YES

Integer

 

 

Output

Structure

DeleteReceptionAssortment_Output.jpg

  1. In case of failure there is a failure message. If there is no failure, nothing is returned

Business rules

  • The waybill status is ’in the Destination, unloaded’ [Enum,Unloaded’]
  • User case performer is described on a waybill as a transporter or a receiver

3.4.9 Insert fine measurement data: InsertFinemeasurementAssortment ()

Description: the service creates a record of fine measured assortment. In case of a successful creation, the fine measured assortment identifier is returned, in case of a failure a failure message is returned.

Input

Structure

InsertFinemeasurementAssortment_Input.jpg

Description

Name

Tag

Mandatory

Type

Validation

Waybill number

WaybillNumber

NO

String

 

Assortment:

Assortment:

NO

TimberAssortment

 

Output

Structure

InsertFinemeasurementAssortment_Output.jpg

Description

Name

Tag

Mandatory

Type

Validation

Result

InsertFinemeasurementAssortmentResult

YES

Integer

 

Business rules

  • Waybill status is ’Received’ [Enum,Received’]
  • User case performer is described on a waybill as a receiver
  • The amount of assortment is greater than 0

Output

  1. Successful or not. In case of failure error message.

3.4.10 Delete fine measurement assortment: DeleteFinemeasurementAssortment ()

Description: the service deletes a fine measurement assortment. In case of a successful deletion, the output is missing, in case of failure there will be an error message.

Input

Structure

DeleteFinemeasurementAssortment_Input.jpg

Description

Name

Tag

Mandatory

Type

Validation

Id

Id

YES

Integer

 

Output

Structure

DeleteFinemeasurementAssortment_Output.jpg

  1. In case of failure a failure message is sent. If there is no failure, nothing is returned

Business rules

  • The waybill status is ’Received’ [Enum,Received’]
  • User case performer is described on a waybill as a receiver 

3.4.11 Insert a fine measurement file: InsertFinemeasurementFile ()

Description: the service creates a file of a fine measured assortment. In case of a successful insertion the output is missing, in case of a failure there will be an error message.

Input

Structure

InsertFinemeasurementFile_Input.jpg

Description

Name

Tag

Mandatory

Type

Validation

Waybill number

WaybillNumber

NO

String

 

File

File

NO

FineMeasurementFile

 

Output

Structure

InsertFinemeasurementFile_Output.jpg

Description

Name

Tag

Mandatory

Type

Validation

Result

InsertFineMeasurementFileResult

YES

Integer

 

Business rules

  • The waybill status is ’Received’ [Enum,Received’]
  • Use case performer is described on a waybill as a receiver

3.4.12 Delete a fine measurement file: DeleteFinemeasurementFile ()

Description: the service creates a file of a fine measured assortment. In case of a successful deletion the output is missing, in case of a failure there will be a respective error message.

Input

Structure

DeleteFinemeasurementFile_Input.jpg

Description

Name

Tag

Mandatory

Type

Validation

Id

Id

YES

Integer

 

Output

  1. In case of a failure there is an error message. If there is no failure, nothing is returned

Business rules

  • The waybill status is ’Received’ [Enum,Received’]
  • Use case performer is described on a waybill as a receiver

3.5 Data types

Additional information:

  1. Procedures related to waybill load packs are not developed
  2. Contact persons
  3. Dispute

 

Type: Address

Structure

Address.jpg

Description

Name

Tag

Mandatory

Type

Validation

Additional information:

AddressAdditionalInformation

NO

String

Max. length == 2000

City/ municipality

CityBorough

NO

String

Max. length == 50

County

County

NO

String

Max. length == 50

EHAK

EHAK

NO

String

Max. length == 50

Near address

NearAddress

NO

String

Max. length == 50

Rural district

RuralDistrict

NO

String

Max. length == 50

 

Type: ArrayOfAssortmentType

Structure

ArrayOfAssortmentType.jpg

Description

Name

Tag

Mandatory

Type

Validation

Assortment:

AssortmentType

NO

AssortmentType

 

 

Type: ArrayOfCertificate

Structure

ArrayOfCertificate.jpg

Description

Name

Tag

Mandatory

Type

Validation

Certificate

Certificate

NO

Certificate

 

 

Type: ArrayOfPacks

Description

Name

Tag

Mandatory

Type

Validation

Load packs

Pack

NO

Pack

 

 

Type: ArrayOfShipment

Structure

ArrayOfShipment.jpg

Description

Name

Tag

Mandatory

Type

Validation

Shipment

Shipment

NO

Shipment

 

 

Type: ArrayOfTimberAssortment

Structure

ArrayOfTimberAssortment.jpg

Description

Name

Tag

Mandatory

Type

Validation

Assortment:

TimberAssortment

NO

TimberAssortment

 

 

Type: ArrayOfTimberBatch

Structure

ArrayOfTimberBatch.jpg

Description

Name

Tag

Mandatory

Type

Validation

Batch

TimberBatch

NO

TimberBatch

 

 

Type: ArrayOfTransport

Structure

ArrayOfTransport.jpg

Description

Name

Tag

Mandatory

Type

Validation

Transport

Transport

NO

Transport

 

 

Type: ArrayOfTransportOrderListItem

Structure

ArrayOfTransportOrderListItem.jpg

Description

Name

Tag

Mandatory

Type

Validation

List element

ArrayOfTransportOrderListItem

NO

TransportOrderListItem

 

 

Type: ArrayOfTransportOrderRestrictionItem

Structure

ArrayOfTransportOrderRestrictionItem.jpg

Description

Name

Tag

Mandatory

Type

Validation

List element

ArrayOfTransportOrderRestrictionItem

NO

TransportOrderRestrictionItem

 

 

Type: ArrayOfTransportOrderSortItem

Structure

ArrayOfTransportOrderSortItem.jpg

Description

Name

Tag

Mandatory

Type

Validation

List element

ArrayOfTransportOrderSortItem

NO

TransportOrderSortItem

 

 

Type: ArrayOfTransportOrderStatusChangeLog

Structure

ArrayOfTransportOrderStatusChangeLog.jpg

Description

Name

Tag

Mandatory

Type

Validation

Status changes

ArrayOfTransportOrderStatusChangeLog

NO

TransportOrderStatusChangeLog

 

 

Type: ArrayOfWaybillListItem

Structure

ArrayOfWaybillListItem.jpg

Description

Name

Tag

Mandatory

Type

Validation

List element

ArrayOfWaybillListItem

NO

WaybillListItem

 

 

Type: ArrayOfWaybillRestrictionItem

Structure

ArrayOfWaybillRestrictionItem.jpg

Description

Name

Tag

Mandatory

Type

Validation

List element

ArrayOfWaybillRestrictionItem

NO

WaybillRestrictionItem

 

 

Type: ArrayOfWaybillSortItem

Structure

ArrayOfWaybillSortItem.jpg

Description

Name

Tag

Mandatory

Type

Validation

List element

ArrayOfWayBillSortItem

NO

WaybillSortItem

 

 

Type: ArrayOfTransportOrderStatusChangeLog

Structure

ArrayOfTransportOrderStatusChangeLog.jpg

Description

Name

Tag

Mandatory

Type

Validation

List element

ArrayOfTransportOrderStatusChangeLog

NO

TransportOrderStatusChangeLog

 

 

Type: AssortmentType

Structure

AssortmentType.jpg

Description

Name

Tag

Mandatory

Type

Validation

Basic classifier

BaseId

NO

Integer

 

Code

Code

NO

String

 

Id

Id

YES

Integer

 

Name

Name

NO

String

 

Unit of measure

UnitId

YES

Integer

 

Unit name

UnitName

NO

String

 

 

Type: AssortmentTypeType

Structure

AssortmentTypeType.jpg

Description

Name

Tag

Mandatory

Type

Validation

Type

AssortmentTypeType

NO

AssortmentTypeType

Enum („Elvis“)
Enum („Company“)

 

Type: AuthorizedPerson, extends the complex data type Person

Structure

AuthorizedPerson.jpg

Description

Name

Tag

Mandatory

Type

Validation

Address

Address

NO

Address

 

Base of authorization

AuthorizationBase

NO

String

Max. length == 100

 

Type: Certificate

Structure

Certificate.jpg

Description

Name

Tag

Mandatory

Type

Validation

Number

CertificateNumber

NO

String

Max. length == 50

Type

TypeId

YES

Integer

CLASSIFIER GROUP TO BE SPECIFIED

 

Type: File

Structure

File.jpg

Description

Name

Tag

Mandatory

Type

Validation

Type

ContentType

NO

String

 

Data

Data

NO

Base64Binary

 

Name

FileName

NO

String

 

 

Type: FineMeasurements

Description

Name

Tag

Mandatory

Type

Validation

Fine measurements

FineMeasurements

NO

ArrayOfTimberAssortment

 

           

 

Type: FineMeasurementFile, extension of the complex data type File

Structure

FineMeasurementFile.jpg

Description

Name

Tag

Mandatory

Type

Validation

Description

Description

NO

String

 

 

Type: Pack

Description

Name

Tag

Mandatory

Type

Validation

Transport

VehicleType

YES

Int

Interval from 9001 to 9999

Pack

PackNumber

YES

Int

Interval from 1 to 3

Length

Length

YES

Decimal

Thousandth accuracy
interval 0,000 - 50,000

Width

Width

YES

Decimal

Thousandth accuracy
interval 0,000 - 50,000

Height

Height

YES

Decimal

Thousandth accuracy
interval 0,000 - 50,000

Factor

Factor

YES

Decimal

Thousandth accuracy
interval 0,000 - 50,000

 Business rules

  1. Load packs are used to describe the amount of assortment in case when the assortment unit is a cubic meter.
  2. Load pack amount is a multiplication of length, width, height and factor
  3. The amount of assortment is the sum of load packs related to assortment

 

Type: Party

Structure

Party.jpg

Description

Name

Tag

Mandatory

Type

Validation

Code

Code

NO

String

Max. length == 11

E-mail

Email

NO

String

Max. length == 50

Name

Name

NO

String

Max. length == 100

Phone

Phone

NO

String

Max. length == 25

 

Type: Person

Structure

Person.jpg

Description

Name

Tag

Mandatory

Type

Validation

E-mail

Email

NO

String

Max. length == 50

First name

Firstname

NO

String

Max. length == 50

Last name

Lastname

NO

String

Max. length == 50

Personal identification code

PersonCode

NO

String

Max. length == 11

Phone

Phone

NO

String

Max. length == 25

 

Type: Priority

Structure

Priority.jpg

Description

Name

Tag

Mandatory

Type

Validation

Priority

Priority

NO

Priority

Enum („Low“)
Enum („Normal“)

Enum („High“)

 

Type: Shipment

Structure

Shipment.jpg

Description

Name

Tag

Mandatory

Type

Validation

Batch

TimberBatches

NO

ArrayOfTimberBatch

 

Starting point

Warehouse

NO

Warehouse

 

 

Type: StatusChangeLogOfTransportOrderStatus

Structure

StatusChangeLogOfTransportOrderStatus.jpg

Description

Name

Tag

Mandatory

Type

Validation

Modifier

ChangedBy

YES

String

Max. length == 50

Changing time

ChangedOn

NO

DateTime

 

Status

TransportOrderStatus

NO

TransportOrderStatus

 

 

Type: StatusChangeLogOfWaybillStatus

Structure

StatusChangeLogOfWaybillStatus.jpg

Description

Name

Tag

Mandatory

Type

Validation

Modifier

ChangedBy

YES

String

Max. length == 50

Changing time

ChangedOn

NO

DateTime

 

Status

WayBillOrderStatus

NO

WayBillStatus

 

 

Type: TimberAssortment

Description

Name

Tag

Mandatory

Type

Validation

Amount

Amount

YES

Decimal

Greater than 0
Thousandth accuracy

Description

Description

NO

String

Max. length == 2000

Id

Id

NO

Integer

 

Load packs

Packs

NO

ArrayOfPack

 

Assortment:

TimberAssortmentTypeId

YES

Integer

Base classifier / company's specific classifier?

Business rules

  1. Validation of the assortment classifier's scope (base classifier / company's specific classifier)
  2. No packs, when defining the amount (waybill)
  3. Validation of a measurement unit (unit of measurement is described in base classifier)
  4. The amount of assortment is greater than 0

 

Type: TimberBatch

Structure

TimberBatch.jpg

Description

Name

Tag

Mandatory

Type

Validation

Appropriation

Appropriation

NO

String

Max. length == 25

Assortments

Assortment:

NO

ArrayOfTimberAssortment

 

Cadastral Number

CadastralNumber

NO

String

Max. length == 25

Certificates

Certificate

NO

ArrayOfCertificate

 

Description

Description

NO

String

Max. length == 2000

Document date

DocDate

YES

DateTime

 

Document no.

DocNumber

NO

String

Max. length == 50

Base of holding

HoldingBaseId

YES

Integer

Interval: from 6001 to 6999

Id

Id

NO

Integer

 

Address of the previous owner

PreviousOwnerAddress

NO

String

Max. length == 100

Code of the previous owner

PreviousOwnerCode

NO

String

Max. length == 25

Name of the previous owner

PreviousOwnerName

NO

String

Max. length == 50

Quarter

Quarter

NO

String

Max. length == 25

Registered immovable number

RegistredImmovableNumber

NO

String

Max. length == 50

Text string

<xs:complexType name="TimberBatch">
    <xs:sequence>
      <xs:element minOccurs="0" name="Appropriation" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="Assortments" nillable="true"
        type="tns:ArrayOfTimberAssortment"/>
      <xs:element minOccurs="0" name="CadastralNumber" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="Certificates" nillable="true"
        type="tns:ArrayOfCertificate"/>
      <xs:element minOccurs="0" name="Description" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="DocDate" type="xs:dateTime"/>
      <xs:element minOccurs="0" name="DocNumber" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="HoldingBaseId" type="xs:int"/>
      <xs:element minOccurs="0" name="Id" nillable="true" type="xs:int"/>
      <xs:element minOccurs="0" name="PreviousOwnerAddress" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="PreviousOwnerCode" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="PreviousOwnerName" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="Quarter" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="RegisteredImmovableNumber" nillable="true"
        type="xs:string"/>
    </xs:sequence>
  </xs:complexType>

Business rules

  1. The previous owner is mandatory if TimberBatch.HoldingBaseId = = „Agreement on Transfer of the Cutting Right“ [ClassificatorId == 6003], or „Agreement on Transfer of Timber" [ClassificatorId == 6004], otherwise not
  2. The previous owner's code is mandatory if TimberBatch.HoldingBaseId = = „Agreement on Transfer of the Cutting Right“ [ClassificatorId == 6003], or „Agreement on Transfer of Timber" [ClassificatorId == 6004], otherwise not.
  3. Previous owner's address is mandatory if TimberBatch.HoldingBaseId = = „Agreement on Transfer of the Cutting Right“ [ClassificatorId == 6003], or „Agreement on Transfer of Timber" [ClassificatorId == 6004], otherwise not

 

Type: TimberOwner, extending a complex data type Party

Structure

TimberOwner.jpg

Description

Name

Tag

Mandatory

Type

Validation

Address

Address

NO

Address

 

Authorized Person

AuthorizedPerson

NO

AuthorizedPerson

 

 

Type: TimberReceiver, extending a complex data type Party

Structure

TimberReceiver.jpg

Description

Name

Tag

Mandatory

Type

Validation

Address

Address

NO

Address

 

Contact person's first name

ContactFirstName

NO

String

Max. length == 50

Contact person's last name

ContactLastName

NO

String

Max. length == 50

Contact person's phone number

ContactPhone

NO

String

Max. length == 25

Contact person's e-mail

ContactEmail

NO

String

Max. length == 50

 

Type: TimberRecieverDestination

Structure

TimberRecieverDestination.jpg

Description:

Name

Tag

Mandatory

Type

Validation

Destination

Destination

NO

Warehouse

 

Receiver

Receiver

NO

TimberReciever

 

 

Type: Transport

Structure

Transport.jpg

Description

Name

Tag

Mandatory

Type

Validation

Driver

Driver

NO

Person

 

Trailer

Trailer

NO

Vehicle

 

Vehicle

Van

NO

Vehicle

 

Business rules:

  1. The transporter must be described in ELVIS as a transporter, a company correspondent to the registration number is existent among Company's records and there is a respective remark in the company’s record, i.e. IsTransporter == 1
  2. The vehicle must be described at the transporter (waybill), i.e. the vehicle registration number exists in Vehicle records and is related to the carrier via company's registration code
  3. The driver must be described at the transporter (waybill), i.e. the driver's identification code exists in Driver records and is related to the transporter via company's registration code
  4. Trailer is not mandatory (waybill)
  5. The trailer must be described at the transporter (waybill), i.e. the trailer registration number exists at Vehicle records and is related to the carrier via company's registration code.

 

Type: TransportOrder

Structure

TransportOrder.jpg

Description

Name

Tag

Mandatory

Type/List

Validation

Alternative number

AltNumber

NO

String

Max. length == 50

Deadline

Deadline

NO

DateTime

 

General notes

Description

NO

String

Max. length == 4000

Group ID

GroupId

NO

String

 

Partial operations

IsPartialOperationsAllowed

YES

Bit

 

Visible for the receiver

IsvisibleToReciever

YES

Bit

 

Transport order number

Number

NO

String

Max. length == 15

Priority

Priority

YES

Priority

 

Timber information

Shipments

NO

ArrayOfShipment

 

Status

Status

YES

TransPortOrderStatus

 

Status changes

StatusChangeLogs

NO

ArrayOfStatusChangeLogOfTransportOrderStatus

 

Timber owner

TimberOwner

NO

TimberOwner

 

Receiver and destination

TimberRecieverDestination

NO

TimberRecieverDestination

 

Transport contract number

TransportContractNumber

NO

String

Max. length == 15

Transporter

Transporter

NO

TransportOrderTransporter

 

Version

Version

NO

Base64Binary

 

 

Type: TransportOrderListItem

Structure

TransportOrderListItem.jpg

Description

Name

Tag

Mandatory

Type

Validation

Alternative number

AltNumber

NO

String

Max. length == 50

Deadline

Deadline

NO

DateTime

 

Group ID

GroupId

NO

String

 

Transport order number

Number

NO

String

Max. length == 15

Owner’s code

OwnerCode

NO

String

 

Owner's name

OwnerName

NO

String

 

Priority

Priority

YES

Priority

 

Receiver's code

RecieverCode

NO

String

 

Receiver’s name

ReceiverName

NO

String

 

Status

Status

YES

TransportOrderStatus

 

Timber owner

TimberOwner

NO

TimberOwner

 

Transporter's code

TransporterCode

NO

String

 

Transporter's name

TransporterName

NO

String

 

Version

Version

NO

Base64Binary

 

 

Type: TransportOrderListItemSearchField

Structure

TransportOrderListItemSearchField.jpg

Description

Name

Tag

Mandatory

Type

Validation

Field

WaybillListItemSearchField

NO

WaybillListItemSearchField

Enum („GroupId“)
Enum („OwnerCode“)
Enum („RecieverCode“)
Enum („TransporterCode“)
Enum („DeadlineFrom“)
Enum („DeadlineTo“)
Enum („TransportOrderNumber“)
Enum („TransportOrderNumberAlternate“)
Enum („OwnerCompanyCode“)
Enum („SourceWarehouseName“)
Enum („DestinationWarehouseName“)
Enum („IsDeleted“)
Enum („StatusId“)

Enum („IsArchived“)

Enum („SubmittedDateFrom“)

Enum („SubmittedDateTo“)

Enum („RecieverName“)

Enum („CreatedOnEnd“)

Enum („SourceWarehouseNameOrCode“)

Enum („DestinationwarehouseNameOrCode“)

Enum („AssortmentName“)

Enum („HoldingbaseId“)

Enum („TimberBatchContractNumber“)

Enum („TimberBatchDocumentDate“)

Enum („DriverName“)

Enum („VanRegistrationNumber“)

Enum („DriverPersonCode“)

 

Type: TransportOrderListItemSortField

Structure

TransportOrderListItemSortField.jpg

Description

Name

Tag

Mandatory

Type

Validation

Field

WaybillListItemSortField

NO

WaybillListItemSortField

Enum („Deadline“)

Enum („CreatedOn“)
Enum („OwnerName“)
Enum („SourceWarehouseName“)
Enum („DestinationWarehouseName“)

Enum („TransporterName“)

 

Type: TransportOrderListPage

Structure

TransportOrderListPage.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Page

TransportOrderListPage

NO

PagedListcontainerOfTransportOrderListItem

 

 

Type: TransportOrderRestrictionItem

Structure

TransportOrderRestrictionItem.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Element

TransportOrderRestrictionItem

NO

RestrictionItemOfTransportOrderListItemSearchField

 

 

Type: TransportOrderSortItem

Structure

TransportOrderSortItem.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Element

TransportOrderSortItem

NO

SortItemOfTransportOrderListItemSortFild

 

 

Type: TransportOrderStatusChangeLog, extension of complex data type  StatusChangeLogOfTransportOrderStatus

Structure

TransportOrderStatusChangeLog.jpg

Description: missing

 

Type: TransportOrderStatus

Structure

TransportOrderStatus.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Status

Status

NO

TransportOrderStatus

Enum („Composing“)
Enum („Submitted“)
Enum („Accepted“)

Enum („Declined“)

Enum („Finalized“)

Enum („Cancelled“)

Text string

<xs:simpleType name="TransportOrderStatus">
    <xs:restriction base="xs:string">
      <xs:enumeration value="Composing">
        <xs:annotation>
          <xs:appinfo><EnumerationValue
              xmlns="http://schemas.microsoft.com/2003/10/Serialization/"
              >4001</EnumerationValue></xs:appinfo>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="Submitted">
        <xs:annotation>
          <xs:appinfo><EnumerationValue
              xmlns="http://schemas.microsoft.com/2003/10/Serialization/"
              >4002</EnumerationValue></xs:appinfo>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="Accepted">
        <xs:annotation>
          <xs:appinfo><EnumerationValue
              xmlns="http://schemas.microsoft.com/2003/10/Serialization/"
              >4003</EnumerationValue></xs:appinfo>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="Declined">
        <xs:annotation>
          <xs:appinfo><EnumerationValue
              xmlns="http://schemas.microsoft.com/2003/10/Serialization/"
              >4004</EnumerationValue></xs:appinfo>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="Finalized">
        <xs:annotation>
          <xs:appinfo><EnumerationValue
              xmlns="http://schemas.microsoft.com/2003/10/Serialization/"
              >4005</EnumerationValue></xs:appinfo>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="Cancelled">
        <xs:annotation>
          <xs:appinfo><EnumerationValue
              xmlns="http://schemas.microsoft.com/2003/10/Serialization/"
              >4006</EnumerationValue></xs:appinfo>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
  </xs:simpleType>

 

Type: TransportOrderStatusInfo

Structure

TransportOrderStatusInfo.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Number

Number

NO

String

 

Status

Status

YES

TransportOrderStatus

 

Version

Version

NO

Version

 

 

Type: TransportOrderTransporter

Structure

TransportOrderTransporter.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Company

CompanyRegistrationNumber

NO

String

 

Contact person’s first Name

ContactFirstName

NO

String

Max. length == 50

Contact person’s last Name

ContactLastName

NO

String

Max. length == 50

Contact person’s E-mail

ContactEmail

NO

String

Max. length == 50

Contact person’s phone

ContactPhone

NO

String

Max. length == 25

Transport executors

Transports

NO

ArrayOfTransport

 

 

Type: Vehicle

Structure

Vehicle.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Model

Model

NO

String

Max. length == 50

Registration number

RegistrationNumber

NO

String

Max. length == 50

 

Type: Warehouse

Structure

Warehouse.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Address

Address

NO

Address

 

Appropriation

Appropriation

NO

String

Max. length == 25

Code

Code

NO

String

Max. length == 25

Contact person’s first Name

ContactFirstName

NO

String

Max. length == 50

Contact person’s last Name

ContactLastName

NO

String

Max. length == 50

Contact person’s phone

ContactPhone

NO

String

Max. length == 25

Contact person’s e-mail

ContactEmail

NO

String

Max. length == 50

Description

Description

NO

String

Max. length == 4000

Forest District

ForestDistrictId

NO

Int

Interval from 8001 to  8999

Id

Id

NO

Int

 

Active

IsActive

NO

Bit

 

Dry

IsDry

NO

Bit

 

Parallel loading

IsParallelLoading

NO

Bit

 

Public

IsPublic

NO

Bit

 

Longitude

Longitude

NO

Double

 

Latitude

Latitude

NO

Double

 

LambertEstX

LambertEstX

NO

Double

 

LambertEstY

LambertEstY

NO

Double

 

Name

Name

NO

String

Max. length == 100

Quarter

Quarter

NO

String

Max. length == 25

Type

Type

NO

Integer

 

 

Type: WarehouseListItem

Description

Name

Tag

 Mandatory

Type

Validation

Code

Code

NO

String

Max. length == 25

Public

IsPublic

YES

Boolean

 

Active

IsActive

YES

Boolean

 

Type

TypeId

YES

Integer

 

Version

Version

NO

Base64Binary

 

 

Type: WarehouseListItemSortField

Description

Name

Tag

 Mandatory

Type

Validation

Field

WarehouseListItemSortField

NO

WarehouseListItemSortField

Enum („CreatedOn“)
Enum („Code“)

Enum („Name“)

 

Type: WarehouseListItemSearchField

Description

Name

Tag

 Mandatory

Type

Validation

Field

WarehouseListItemSearchField

NO

WarehouseListItemSearchField

Enum („Code“)
Enum („Name“)
Enum („IsPublic“)
Enum („IsActive“)

Enum („CreatedOnStart“)

Enum („CreatedOnEnd“)

Enum („AssortmentName“)

Enum („HoldingbaseId“)

Enum („TimberBatchContractNumber“)

Enum („TimberBatchDocumentDate“)

           

 

Type: WarehouseListPage

Description

Name

Tag

 Mandatory

Type

Validation

Page

WarehouseListPage

NO

PagedListContainerOfWarehouseListItem

 

 

Type: WarehouseRestrictionItem

Description

Name

Tag

 Mandatory

Type

Validation

Element

WarehouseRestrictionItem

NO

RestrictionItemOfWarehouseListItemSearchField

 

 

Type: WarehouseSortItem

Description

Name

Tag

 Mandatory

Type

Validation

Element

WarehouseSortItem

NO

SortItemOfWarehouseListItemSortFeild

 

 

Type: WayBill

Structure

WayBill.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Alternative number

AltNumber

NO

String

Max. length == 50

General notes

Description

NO

String

Max. length == 4000

Fine measurements

FineMeasurements

NO

ArrayOfTimberAssortment

 

 

 

 

 

 

Disputing

IsDisputed

YES

Boolean

 

Waybill number

Number

NO

String

Max. length == 50

Pre journey length

PreJourneyLength

NO

Decimal

Greater than 0

Received assortments

RecivedAssortments

NO

ArrayOfTimberBatch

 

Shipped assortments

Shipments

NO

ArrayOfShipment

 

Status log

StatusChangeLogs

NO

ArrayOfStatusChangeLogOfWayBillStatus

 

Status

Status

YES

Integer

Interval: 7001 -  7999

Timber owner

TimberOwner

NO

TimberOwner

 

Receiver and destination

TimberRecieverDestination

NO

TimberRecieverDestination

 

Total journey length

TotalJourneyLength

NO

Decimal

Greater than 0

Transport order

TransportOrderNumber

NO

String

Max. length == 50

Transporter

Transporter

NO

WaybillTransporter

 

Version

Version

NO

Base64Binary

 

Text string

<xs:complexType name="Waybill">
    <xs:sequence>
      <xs:element minOccurs="0" name="AltNumber" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="Description" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="FineMeasurements" nillable="true"
        type="tns:ArrayOfTimberAssortment"/>
      <xs:element minOccurs="0" name="IsDisputed" type="xs:boolean"/>
      <xs:element minOccurs="0" name="Number" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="PreJourneyLength" nillable="true" type="xs:decimal"/>
      <xs:element minOccurs="0" name="ReceivedAssortments" nillable="true"
        type="tns:ArrayOfTimberBatch"/>
      <xs:element minOccurs="0" name="Shipments" nillable="true" type="tns:ArrayOfShipment"/>
      <xs:element minOccurs="0" name="Status" type="q1:WaybillStatus"
        xmlns:q1="http://schemas.datacontract.org/2004/07/EMTL.Elvis.DTO.Waybill"/>
      <xs:element minOccurs="0" name="StatusChangeLogs" nillable="true"
        type="tns:ArrayOfWaybillStatusChangeLog"/>
      <xs:element minOccurs="0" name="TimberOwner" nillable="true" type="tns:TimberOwner"/>
      <xs:element minOccurs="0" name="TimberReceiverDestination" nillable="true"
        type="tns:TimberReceiverDestination"/>
      <xs:element minOccurs="0" name="TotalJourneyLength" nillable="true" type="xs:decimal"/>
      <xs:element minOccurs="0" name="TransportOrderNumber" nillable="true" type="xs:string"/>
      <xs:element minOccurs="0" name="Transporter" nillable="true"
        type="tns:WaybillTransporter"/>
      <xs:element minOccurs="0" name="Version" nillable="true" type="xs:base64Binary"/>
    </xs:sequence>
  </xs:complexType>

 

Type: WaybillListItem

Structure

WaybillListItem.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Alternative number

AltNumber

NO

String

Max. length == 50

Waybill number

Number

NO

String

Max. length == 15

Owner’s code

OwnerCode

NO

String

 

Owner’s name

OwnerName

NO

String

 

Receiver’s code

RecieverCode

NO

String

 

Receiver’s name

ReceiverName

NO

String

 

Status

Status

NO

TransportOrderStatus

 

Transport order number

TransportOrderNumber

NO

String

 

Timber owner

TimberOwner

NO

TimberOwner

 

Transporter’s code

TransporterCode

NO

String

 

Transporter’s name

TransporterName

NO

String

 

Version

Version

NO

Base64Binary

 

 

Type: WaybillListItemSortField

Structure

WaybillListItemSortField.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Field

WaybillListItemSortField

NO

WaybillListItemSortField

Enum („CreatedOn“)
Enum („OwnerName“)
Enum („SourceWarehouseName“)
Enum („DestinationWarehouseName“)

Enum („TransporterName“)

 

Type: WaybillListItemSearchField

Structure

WaybillListItemSearchField.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Field

WaybillListItemSearchField

NO

WaybillListItemSearchField

Enum („OwnerCode“)
Enum („RecieverCode“)
Enum („RecieverName“)
Enum („TransporterCode“)
Enum („WaybillNumber“)
Enum („WaybillNumberAlternate“)
Enum („OwnerCompanyName“)
Enum („TransporterCompanyName“)
Enum („SourceWarehouseName“)
Enum („SourceWarehouseNameOrCode“)
Enum („DestinationWarehouseName“)
Enum („DestinationWarehouseNameOrCode“)
Enum („IsDeleted“)
Enum („StatusId“)

Enum („IsArchived“)

Enum („ConfirmationDateFrom“)

Enum („ConfirmationDateTo“)

Enum („CreatedOnStart“)

Enum („CreatedOnEnd“)

Enum („TransportOrderNumber“)

Enum („TransportOrderNumberAlternate“)

Enum („AssortmentName“)

Enum („HoldingbaseId“)

Enum („TimberBatchContractNumber“)

Enum („TimberBatchDocumentDate“)

Enum („DriverName“)

Enum („VanRegistrationNumber“)

Enum („TrailerRegistrationNumber“)

Enum („IsDisputed“)

Enum („DriverPersonCode“)

 

Type: WaybillListPage

Structure

WaybillListPage.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Page

WaybillListPage

NO

PagedListcontainerOfWaybillListItem

 

 

Type: WaybillRestrictionItem

Structure

WaybillRestrictionItem.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Element

WaybillRestrictionItem

NO

RestrictionItemOfWaybillListItemSearchField

 

 

Type: WaybillRoleContext

Structure

WaybillRoleContext.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Context

WaybillRoleContext

NO

WaybillroleContext

Enum („Owner“)
Enum („Receiver“)
Enum („Transporter“)

 

Type: WaybillSortItem

Structure

WaybillSortItem.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Element

WaybillSortItem

NO

SortItemOfWaybillListItemSortFeild

 

 

Type: WaybillStatusChangeLog, extension of complex data type  StatusChangeLogOfWaybillStatus

Structure

WaybillStatusChangeLog.jpg

Description: missing

 

Type: WaybillStatus

Structure

WaybillStatus.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Status

WaybillStatus

NO

WaybillStatus

Enum („Composing“)
Enum („Confirmed“)
Enum („Unloaded“)

Enum („Received“)

Enum („Measured“)
Enum („MeasurementConfirmed“)

Enum („Cancelled“)

 

Type: WaybillStatusInfo

Structure

WaybillStatusInfo.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Number

Number

NO

String

 

Status

Status

YES

TransportOrderStatus

 

Version

Version

NO

Version

 

 

Type: WaybillTransporter

Structure

WaybillTransporter.jpg

Description

Name

Tag

 Mandatory

Type

Validation

Company’s registration number

CompanyRegistrationNumber

NO

String

 

Transport

Transport

NO

Transport

 

 

 

 

 

 

 

 

Kas see artikkel oli abiks?
0 kasutajale 0st oli see abiks
Print, PDF