Calidus HUB - User contributions [en-gb]

FS 293863 CDL EPOD Modifications

2012-10-08T10:18:10Z

Milesl: /* Export Functionality */

<div class="noprint">
{{#vardefine:Client|CDL}}
{{#vardefine:ClientName|Computer Disposals Limited}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|CDL EPOD Modifications}}
{{#vardefine:Version|1.1}}
{{#vardefine:Date|28th June 2012}}
{{#vardefine:Reference|293863}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==
Development is required to the ''CALIDUS'' ePOD system in order to provide the functionality required by CDL. The requirements have been set out by Matthew Turner from visits to the client as follows:

Computer Disposals collect used computer equipment from companies to recycle at their head office in Warrington.

They are currently implementing a back office solution to handle all job processing. The system will export basic job detail. We need to provide xml/csv schema detail so they can design an import function to pass job detail onto us. They will provide a example of their standard output in November, so we can tell them how to change it.

They have a 2 part delivery note that is largely based on a fixed template created in Word.

Coll Note Part 1 is attached.

Coll Note Part 2 is attached.

I have marked the detail that comes from the CDL back job office import on the 2 part form with a tick.
I have marked the detail that the driver needs to complete with an X.

In the current process, the driver does not generally know the exact quantity of goods he is collecting from a site. A general idea of the number of items to be collected is usually entered in the driver instructions part of the collection note. We refer to driver instructions in ePOD as ‘job instructions’.

On Product QTY Count, you will see that the driver does a manual count of equipment collected. He then does an estimation of weight based on multiplication of set weight per item. The result is entered on the QTY KG boxes on both parts on the collection note.

Example:
(qty count of product) x ( set weight per product ) = QTY (KG)

On Coll Note Part 1 the following rules apply:

In box CRT Monitor QTY (KG), the KG total number is based on:

(qty count of monitors) x ( set weight per monitor ) = QTY (KG)

In box Flat Screen Displays QTY KG, the KG total number is based on:

(qty count of TFT’s) x ( set weight per TFT) + (qty count of laptops) x ( set weight per laptops) = QTY (KG)

In box Waste Refrigerants QTY KG, the KG total number is based on:

(qty count of waste refrigerants) x ( set weight per waste refrigerants ) = QTY (KG)

On Coll Note Part 2 which is the 2nd part of the collection note, the following rules apply:

In box IT Equipment, the KG total number is based on:

Total QTY KG of all collected products except Monitors, TFT’s, Laptops, Waste Refrigerants

Set Weights Info
*1 x Monitor = 12 Kg
*1 x TFT = 8 Kg
*1 x Base = 8 Kg
*1 x General = 2 Kg
*1 x Printer = 5 Kg
*1 x Server = 12 Kg
*1 x Laptop = 8 Kg
*1 x Refrigeration Unit = 50 Kg

Anticipated Process On PDA:
#Driver opens collection job from manifest
#Driver accesses product confirmation
#Driver does QTY count of product
#Result of calculation for QTY KG does not necessarily have to be shown on PDA just electronic collection note back in system.
#Driver signs PDA.
#Customer (Consignor) signs PDA

General Info:

Consignor is ‘Customer‘.

Part E (Disposer of Waste) on both parts of the collection note needs to be replicated on the electronic collection note, but is not interacted with in any way by our system.
Automatic email POD is required on this contract.

General Questions:

Can date and time be automatically provided by the system on the electronic collection note?

Can driver print name and vehicle registration automatically be provided by the system on the electronic collection note?

CDL will be using HTC Touch 2.

== Solution Overview ==
The functionality required is:
*Bespoke Job Import function
*Bespoke Multi-part Proof of Collection
*Multiple Signatures at Delivery/Collection
*Ad Hoc Collection process
*Product Weights
*Automatic email of POD/POC
*Office Instructions
*Modifiable customer contact.

{{Note}} Slight changes to requirements were requested on 28/06/2012 regarding:
* Confirmation of T&Cs when signing for goods.
The format of the collection note has also been modified slightly to allow for the enhanced T&Cs.

The system will be modified to allow the PDA to confirm the T&Cs and allow check-box entry as required. Although this will be data-maintainable, this will not be configurable by the customer.

== Scope ==
*Modifications will be made to version 1.1 of ''CALIDUS'' ePOD system.



= Set-up =

== Pre-requisites ==
*For emailing POC/POD documents, Email must be configured on the ''CALIDUS'' ePOD server.

== Menu Structure ==
None

== Data ==
*The standard products must be created with standard weights.
*For emailing POC/POD documents, customers must be configured with email addresses.



= Functional Description =

==Configuration==
New Rules are required for the configuration of the system:
===Site/Job Group===
*Driver Signature Required Delivery
*Driver Signature Required Collection
*Ad Hoc Collection
*Automatic Email
===Site===
*Job Import Format
*Automatic Email

==Database Modifications==
The EPOD_JOB table will be modified to include a new EPL_OFFICE_INSTRUCTIONS field. This will be in the same format as the current Instructions field.

The EPOD_JOB table will be modified to include a new EPL_CUST_SIGNATORY field. This will be in the same format as the current EPOD_CUSTOMERS Contact field.

The EPOD_JOB table will be modified to include a new EPL_CUST_REF field. This will be a 30-character field. {{Note}} This is also being added under developments for another customer - see the Referenced documents for details.

The EPOD_PRODUCTS table will be modified to include a new Weight field. This will be a floating point field.

The EPOD_SERVICE_PRODUCT_MASTER table will be modified to include a new Weight field. This will be a floating point field.

The EPOD_JOB table will be modified to include a new EPL_TNCS field. This will be a max-character field.

The EPOD_JOB_GROUP table will be modified to include a new EPL_TNCS field. This will be a max-character field.


==Office Instructions==
A new field of office instruction will be added to the EPOD_JOB table. This field will need to be displayed within the Job Details screen. This will be a free text field, identical to the current instructions field.



==Bespoke Job Import Function==

The Import shall be performed via a XML file. The file format must conform to the following schema. The upload shall function so that if there is a single issue with the file, no data will be committed, "All or Nothing". The upload works for both adding and updating data. The upload is available via a manual upload or a web request.

===XML Schema===

A base for the XML import:

<?xml version="1.0" encoding="utf-16"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="EPOD_IMPORT">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_LOADS" maxOccurs="1" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_LOAD" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0" />
<xsd:element name="EPL_LOAD_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_END_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_END_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_USER_ID" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_JOBS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_JOB" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_OFFICE_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_CONTAINERS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CONTAINER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="true" minOccurs="0" />
<xsd:element name="EPL_CONTAINER_PACKAGE_CODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_PACKAGE_DESC" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1" >
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="I"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_REG_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_VIN_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SIM_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_JOBS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_JOB" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_OFFICE_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_CONTAINERS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CONTAINER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CONTAINER_PACKAGE_CODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_PACKAGE_DESC" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="I"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_REG_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_VIN_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SIM_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_CUSTOMERS" maxOccurs="1" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CUSTOMER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE_PRODUCT_MASTERS" nillable="false" maxOccurs="1" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_SERVICE_PRODUCT_MASTER" nillable="false" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_DESCRIPTION" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_STATUS" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="A"/>
<xsd:enumeration value="I"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_QUANTITY" type="xsd:int" />
<xsd:element name="EPL_PRODUCT_WEIGHT" type="xsd:decimal" nillable="true" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="EPL_SITE_ID">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="EPL_USER_ID">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="EPL_USER_PASSWORD">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:schema>



==Ad Hoc Collection Process==

The Ad Hoc collection process will allow users of the PDA to specify items collected, at point of collection. This will appears as a separate tab on the PDA within the Collections menu. Users will be able to select items that currently exists in the EPOD_SERVICE_PRODUCT_MASTER, from a drop down list and add or remove them from the collection. These products will be added to the Loose Products container 00000000.

Once completed the server will then create this container if it does not exist and products.

This will be configurable against the SITE and the JOB GROUP. If configured as off the Ad Hoc tab within the collections menu will be disabled. If this is enabled the tab will be displayed allowing a combination of pre-defined containers and products as well as Ad Hoc additions. The functionality provided by Containers without products means that in the scenario that there are no products/containers pre-defined the Containers and Products tabs will be disabled. If the Loose Product container is pre-defined, the Ad Hoc products will be placed onto this container.


==Multiple Signatures at Delivery/Collection==

When completing a Delivery/Collection, the flag against site for Driver Signature will be checked. If this option is enabled the user will be asked to sign (Driver) as in the service menu.
These details will be stored in the driver signature field within the Job table.

The flag will be configurable against Job Group and Site. As with other configuration, the job group will be checked if no record is present then the site record will be used.


==Modifiable Customer Contact==
When the PDA requests a customer signature, the Customer Contact Name is defaulted into the text box above the signature. The user is allowed to amend this name, to reflect the customer contact who actually signed for the work.

This customer name must be sent back to the Server.

The Server must save this to the new Job field created for this purpose (CUST_SIGNATORY).

This must be used on the POD/POC/Service reports created instead of the customer name.


==Customer Terms & Conditions ==
When the PDA requests a customer signature, the system should prompt for T&Cs first, if the system has been configured for this. In order to achieve this:
* The Job Group configuration sent to the PDA must now include the new EPL_TNCS field.
* When prompting for customer signature, the PDA must check the Job Group configuration of the Job being confirmed. If this has a TNC Configuration, this should call a new screen to require T&C confirmation. If not, the existing Customer Signature screen will be called instead.
* The new screen will extract the XML tags of the EPL_TNCS field as follows:
** TEXT - this is the text that is always present and fills a scrolling text box on the screen.
** CHECK - these are check boxes that will be displayed for the user to check under the text box. They will consist of the label to be displayed. There can be up to 3 only - any more will be ignored.
* The format used by the site will be as follows:
<TEXT>I certify that the information in A, B and C is correct, and that the carrier is registered.<br />
I confirm that I have fulfilled my duty to apply the waste hierarchy as required by Regulation 12 of the Waste (England and Wales) Regulations 2011. I also confirm that I am legally permitted to release the items from the company detailed in part A to CDL
</TEXT>
<CHECKS>
<INPUT type="checkbox">A) Secure Location</INPUT>
<INPUT type="checkbox">B) Non - Secure Location</INPUT>
<INPUT type="checkbox">C) Customer Not Present</INPUT>
</CHECKS>
* The new screen will have an OK button. At least one of the check boxes must be checked to continue.
* On clicking OK, the user will be taken to the existing Customer Signature screen.
* The Checks tab will be returned and stored in the database in the EPL_TNCS field on the Job record. If check boxes have been ticked, they will have a parameter added to them of "checked", as follows:
<CHECKS>
<INPUT type="checkbox">A) Secure Location</INPUT>
<INPUT type="checkbox" checked="checked">B) Non - Secure Location</INPUT>
<INPUT type="checkbox" checked="checked">C) Customer Not Present</INPUT>
</CHECKS>
* The new screen will have a layout similar to the following:
[[File:293863-PDA-1.PNG]]


==Product Weights==
===Admin===
The Service Product Maintenance screen (product_maintanance.aspx) will be modified to add a Weight column to the grid when data is found.

[[File:293863-ProdWeight-1.PNG|border|600px]]

This will come from the new field on EPOD_SERVICE_PRODUCTS_MASTER.

When adding a new product from this screen (pressing the '''New''' button), the screen will prompt for the Weight. This will be positioned under the Product Status field, in line with it.

[[File:293863-ProdWeight-2.PNG|border|600px]]

Clicking '''Create''' will save the new product with the weight. Weight (and quantity) are not required entries. Weight if entered will be validated as a floating point number.

When editing a product on the grid (by clicking '''Select''', the '''Edit'''), the screen will allow the user to edit the weight in position here, like the Status and Quantity.

[[File:293863-ProdWeight-3.PNG|border|600px]]

Clicking '''Update''' will save the product with any amendments. Weight (and quantity) are not required entries. Weight if entered will be validated as a floating point number.

===Server===
When a PDA client confirms a job as complete, the server will update the Job with the new products (see [[#Ad Hoc Collection Process|"Ad Hoc Collection Process"]]).

When creating these products, the server will get the Service Product record relating to the product line. If found, and the product has a weight against it, this will be multiplied by the product quantity and saved into the weight field against the Job Products record.


==Bespoke Multi-part Proof of Collection Document==
A new POC format will be created, labelled as "CDL". This will match as closely as possible the existing documents used by CDL, as can be seen in [[#Appendix A: POC Document Formats|Appendix A]].

The fields used on both pages are as follows:
*Collection Date: EPL_START_PLANNED_DATE of EPOD_JOB
*CDL Representative: EPL_USER_NAME of EPOD_USER
*Consignment Note Code: CUSTOMER_CODE + JOB_ID of EPOD_JOB
*Waste Remove From: Address information from EPOD_CUSTOMER
*Premises Code: CUSTOMER_CODE of EPOD_JOB
*Waste Taken To: Site Address (taken from the EPOD_CUSTOMER record for the SITE_ID
*CDL Internal Reference: EPL_JOB_ID of EPOD_JOB
*SIC: EPL_CUST_REF of EPOD_JOB
*Qty (Kg): Calculated based on EPL_PRODUCT_WEIGHT * EPL_PRODUCT_QTY_ACTUAL
*Carrier
**Vehicle Reg: EPL_VEHICLE_REG of EPOD_VEHICLE, from EPL_VEHICLE_ID of EPOD_LOAD
**Signature: EPL_ENG_SIGNATURE of EPOD_JOB
**Time: EPL_END_ACTUAL_TIME of EPOD_JOB
**Print Name: EPL_USER_NAME of EPOD_USER
**Date: EPL_END_ACTUAL_DATE of EPOD_JOB
*Consignor:
**Consignor Name: CUST_SIGNATORY
**Signature: EPL_JOB_SIGNATURE
**Date: EPL_END_ACTUAL_DATE of EPOD_JOB
**Time: EPL_END_ACTUAL_TIME of EPOD_JOB
**Consignor Name: EPL_CONTACT + EPL_TELEPHONE of EPOD_CUSTOMER
**Office Instruction: EPL_OFFICE_INSTRUCTION of EPOD_JOB
**Driver Instruction: EPL_INSTRUCTIONS of EPOD_JOB
All other details on the POD will be produced as-is on the pro-forma document.

All existing POD/POC formats include a section that allows the user to send the document via Email. This section in each existing format will be modified to be surrounded by two identical comments, similar to the below:
<pre></pre>

The Email section will be encased in a Division, specifically identified. CSS will be created to ensure that this section is removed when printing, using a CSS style specific for media printing.

For example:

<pre>
<style type="text/css" media="screen">
#emailSection {display: block;}
</style>
<style type="text/css" media="print">
#emailSection {display: none;}
</style>
<div id="emailSection">

.
.
.

</div>
</pre>

{{Note}} Multiple pages will be achieved when printing by using the CSS style '''page-break-before: always;''' set against the first element of the second page.

"PART D - Consignor's Certificate" will be populated based on the values configured in the EPOD_JOB_GROUP record for the job and the check-box input values specified on the EPOD_JOB record.

The text and the check boxes will be formatted on the EPOD format to line up as per the existing documents used by CDL.



==Automatic email of POD/POC==

When a PDA client confirms a job as complete, the server will update the Job to Complete status.

When this is complete, the process will check whether the new Configuration rule "Automatic Email" is set up for the Site of the completed job.

If this is enabled, the process will get the Customer record for the Job's Customer.

If the Email address of the Customer is set, the following actions will be taken:
*The process will render the POD or POC for the Job, in the correct format, according to the Site or Job Group of the completed Job.
*The process will take the rendered page and remove any code in between the new ''EMAIL SECTION'' comment tags
*This rendered page will then be sent to the customer's email address through the standard email mechanism.

==Export Functionality==
The CDL host system will require the ability to poll a webservice within ePOD either on demand or on a poller to retrieve current ePOD job information.
A webservice already exists for exporting data by Job/Load ID and Date. Another two will be added allowing loads and jobs to be exported that have been changed in a date and time range.
The services will require a From Date and Time and will accept a option To Date and Time, this will allow for poller services to simply retrieve all updates since the last poll using only the From Date and Time as well as queries to data in a particular date and time range. The data returned as part of this export will conform to the current standards documented in the current version of the ePOD XSD’s.
===Job Level===
The Job level webservice should be added that will accept the following structure:

<EPOD_EXPORT_JOB_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">
<DATE_TIME_FROM>2012-10-05T18:40:00</DATE_TIME_FROM>
<DATE_TIME_TO>2012-10-05T18:50:00</DATE_TIME_TO>
</EPOD_EXPORT_JOB_CHANGED>

The webservice will authenticate the user data and then process the message as follows:
IF DATE_TIME_FROM is NULL or Invalid
RETURN ERROR
IF DATE_TIME_TO is Invalid
RETURN ERROR
IF DATE_TIME_TO is NULL
RETURN XML of all jobs that have a last changed date and time greater than the DATE_TIME_FROM field
ELSE
RETURN XML of all jobs that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields

===Load Level===
The Load level webservice should be added that will accept the following structure:

<EPOD_EXPORT_LOAD_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">
<DATE_TIME_FROM>2012-10-05T18:40:00</DATE_TIME_FROM>
<DATE_TIME_TO>2012-10-05T18:50:00</DATE_TIME_TO>
</EPOD_EXPORT_LOAD_CHANGED>

The webservice will authenticate the user data and then process the message as follows:
IF DATE_TIME_FROM is NULL or Invalid
RETURN ERROR
IF DATE_TIME_TO is Invalid
RETURN ERROR
IF DATE_TIME_TO is NULL
RETURN XML of all jobs that have a last changed date and time greater than the DATE_TIME_FROM field
ELSE
RETURN XML of all loads that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields



= Appendix A: POC Document Formats =
[[File:293863-POC-1.JPG|600px]]


[[File:293863-POC-2.JPG|600px]]



= Appendix B: TEST PLAN =

{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=Full System Test for CDL's functionality
|MenuAccess=N/a
|Prerequisites=CDL Test Site configuration
|Objective=Fully test CDL's functionality
}}
{{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Admin
|Notes=Admin Changes
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Create a Ad Hoc collection with Office Instructions (collection with no containers or products)
|Result=
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Check the multi-part POC is produced correctly(printed as well), confirm the weights are calculated correctly.
|Result=
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=On job completion the POC should be emailed to the customers email address, automatically.
|Result=
|Remarks=
|PassFail=
}}{{TestPlan_CycleFooter}}

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=PDA Client
|Notes=PDA Client Changes
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Process a ad hoc collection
|Result=Only Ad Hoc collection tab and instruction tabs should be shown.
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Process a ad hoc collection using products configured in the service product master
|Result=Products should be added in the standard approach
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Check driver signature is prompted
|Result=Driver should sign as well as the customer
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Change the customers name when signing
|Result=This should process back to the admin system and be shown against the job.
|Remarks=
|PassFail=
}}
{{TestPlan_CycleFooter}}


{{Doc_Appendix
|Appendix=C
|Estimate=N
|Glossary=EPOD
|Ref1=[[FS 294229 Whiteline EPOD Modifications]]
|RefV1=0.1
|RefDate1=23/11/2011
|REQ=0
|EST=0
|FS=1.0
|TS=0
|DEV=18.0
|ST=5.0
|IMP=0
|Client={{#var:Client}}
|Year=2011
|FSEST=N
|Rev1=Steve McCartney
|Rev1Title=OBS Representative
|Rev2=Matthew Turner
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 293863 CDL EPOD Modifications

2012-10-08T10:06:04Z

Milesl: /* Export Functionality */

<div class="noprint">
{{#vardefine:Client|CDL}}
{{#vardefine:ClientName|Computer Disposals Limited}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|CDL EPOD Modifications}}
{{#vardefine:Version|1.1}}
{{#vardefine:Date|28th June 2012}}
{{#vardefine:Reference|293863}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==
Development is required to the ''CALIDUS'' ePOD system in order to provide the functionality required by CDL. The requirements have been set out by Matthew Turner from visits to the client as follows:

Computer Disposals collect used computer equipment from companies to recycle at their head office in Warrington.

They are currently implementing a back office solution to handle all job processing. The system will export basic job detail. We need to provide xml/csv schema detail so they can design an import function to pass job detail onto us. They will provide a example of their standard output in November, so we can tell them how to change it.

They have a 2 part delivery note that is largely based on a fixed template created in Word.

Coll Note Part 1 is attached.

Coll Note Part 2 is attached.

I have marked the detail that comes from the CDL back job office import on the 2 part form with a tick.
I have marked the detail that the driver needs to complete with an X.

In the current process, the driver does not generally know the exact quantity of goods he is collecting from a site. A general idea of the number of items to be collected is usually entered in the driver instructions part of the collection note. We refer to driver instructions in ePOD as ‘job instructions’.

On Product QTY Count, you will see that the driver does a manual count of equipment collected. He then does an estimation of weight based on multiplication of set weight per item. The result is entered on the QTY KG boxes on both parts on the collection note.

Example:
(qty count of product) x ( set weight per product ) = QTY (KG)

On Coll Note Part 1 the following rules apply:

In box CRT Monitor QTY (KG), the KG total number is based on:

(qty count of monitors) x ( set weight per monitor ) = QTY (KG)

In box Flat Screen Displays QTY KG, the KG total number is based on:

(qty count of TFT’s) x ( set weight per TFT) + (qty count of laptops) x ( set weight per laptops) = QTY (KG)

In box Waste Refrigerants QTY KG, the KG total number is based on:

(qty count of waste refrigerants) x ( set weight per waste refrigerants ) = QTY (KG)

On Coll Note Part 2 which is the 2nd part of the collection note, the following rules apply:

In box IT Equipment, the KG total number is based on:

Total QTY KG of all collected products except Monitors, TFT’s, Laptops, Waste Refrigerants

Set Weights Info
*1 x Monitor = 12 Kg
*1 x TFT = 8 Kg
*1 x Base = 8 Kg
*1 x General = 2 Kg
*1 x Printer = 5 Kg
*1 x Server = 12 Kg
*1 x Laptop = 8 Kg
*1 x Refrigeration Unit = 50 Kg

Anticipated Process On PDA:
#Driver opens collection job from manifest
#Driver accesses product confirmation
#Driver does QTY count of product
#Result of calculation for QTY KG does not necessarily have to be shown on PDA just electronic collection note back in system.
#Driver signs PDA.
#Customer (Consignor) signs PDA

General Info:

Consignor is ‘Customer‘.

Part E (Disposer of Waste) on both parts of the collection note needs to be replicated on the electronic collection note, but is not interacted with in any way by our system.
Automatic email POD is required on this contract.

General Questions:

Can date and time be automatically provided by the system on the electronic collection note?

Can driver print name and vehicle registration automatically be provided by the system on the electronic collection note?

CDL will be using HTC Touch 2.

== Solution Overview ==
The functionality required is:
*Bespoke Job Import function
*Bespoke Multi-part Proof of Collection
*Multiple Signatures at Delivery/Collection
*Ad Hoc Collection process
*Product Weights
*Automatic email of POD/POC
*Office Instructions
*Modifiable customer contact.

{{Note}} Slight changes to requirements were requested on 28/06/2012 regarding:
* Confirmation of T&Cs when signing for goods.
The format of the collection note has also been modified slightly to allow for the enhanced T&Cs.

The system will be modified to allow the PDA to confirm the T&Cs and allow check-box entry as required. Although this will be data-maintainable, this will not be configurable by the customer.

== Scope ==
*Modifications will be made to version 1.1 of ''CALIDUS'' ePOD system.



= Set-up =

== Pre-requisites ==
*For emailing POC/POD documents, Email must be configured on the ''CALIDUS'' ePOD server.

== Menu Structure ==
None

== Data ==
*The standard products must be created with standard weights.
*For emailing POC/POD documents, customers must be configured with email addresses.



= Functional Description =

==Configuration==
New Rules are required for the configuration of the system:
===Site/Job Group===
*Driver Signature Required Delivery
*Driver Signature Required Collection
*Ad Hoc Collection
*Automatic Email
===Site===
*Job Import Format
*Automatic Email

==Database Modifications==
The EPOD_JOB table will be modified to include a new EPL_OFFICE_INSTRUCTIONS field. This will be in the same format as the current Instructions field.

The EPOD_JOB table will be modified to include a new EPL_CUST_SIGNATORY field. This will be in the same format as the current EPOD_CUSTOMERS Contact field.

The EPOD_JOB table will be modified to include a new EPL_CUST_REF field. This will be a 30-character field. {{Note}} This is also being added under developments for another customer - see the Referenced documents for details.

The EPOD_PRODUCTS table will be modified to include a new Weight field. This will be a floating point field.

The EPOD_SERVICE_PRODUCT_MASTER table will be modified to include a new Weight field. This will be a floating point field.

The EPOD_JOB table will be modified to include a new EPL_TNCS field. This will be a max-character field.

The EPOD_JOB_GROUP table will be modified to include a new EPL_TNCS field. This will be a max-character field.


==Office Instructions==
A new field of office instruction will be added to the EPOD_JOB table. This field will need to be displayed within the Job Details screen. This will be a free text field, identical to the current instructions field.



==Bespoke Job Import Function==

The Import shall be performed via a XML file. The file format must conform to the following schema. The upload shall function so that if there is a single issue with the file, no data will be committed, "All or Nothing". The upload works for both adding and updating data. The upload is available via a manual upload or a web request.

===XML Schema===

A base for the XML import:

<?xml version="1.0" encoding="utf-16"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="EPOD_IMPORT">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_LOADS" maxOccurs="1" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_LOAD" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0" />
<xsd:element name="EPL_LOAD_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_END_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_END_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_USER_ID" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_JOBS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_JOB" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_OFFICE_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_CONTAINERS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CONTAINER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="true" minOccurs="0" />
<xsd:element name="EPL_CONTAINER_PACKAGE_CODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_PACKAGE_DESC" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1" >
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="I"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_REG_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_VIN_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SIM_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_JOBS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_JOB" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_OFFICE_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_CONTAINERS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CONTAINER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CONTAINER_PACKAGE_CODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_PACKAGE_DESC" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="I"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_REG_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_VIN_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SIM_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_CUSTOMERS" maxOccurs="1" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CUSTOMER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE_PRODUCT_MASTERS" nillable="false" maxOccurs="1" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_SERVICE_PRODUCT_MASTER" nillable="false" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_DESCRIPTION" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_STATUS" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="A"/>
<xsd:enumeration value="I"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_QUANTITY" type="xsd:int" />
<xsd:element name="EPL_PRODUCT_WEIGHT" type="xsd:decimal" nillable="true" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="EPL_SITE_ID">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="EPL_USER_ID">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="EPL_USER_PASSWORD">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:schema>



==Ad Hoc Collection Process==

The Ad Hoc collection process will allow users of the PDA to specify items collected, at point of collection. This will appears as a separate tab on the PDA within the Collections menu. Users will be able to select items that currently exists in the EPOD_SERVICE_PRODUCT_MASTER, from a drop down list and add or remove them from the collection. These products will be added to the Loose Products container 00000000.

Once completed the server will then create this container if it does not exist and products.

This will be configurable against the SITE and the JOB GROUP. If configured as off the Ad Hoc tab within the collections menu will be disabled. If this is enabled the tab will be displayed allowing a combination of pre-defined containers and products as well as Ad Hoc additions. The functionality provided by Containers without products means that in the scenario that there are no products/containers pre-defined the Containers and Products tabs will be disabled. If the Loose Product container is pre-defined, the Ad Hoc products will be placed onto this container.


==Multiple Signatures at Delivery/Collection==

When completing a Delivery/Collection, the flag against site for Driver Signature will be checked. If this option is enabled the user will be asked to sign (Driver) as in the service menu.
These details will be stored in the driver signature field within the Job table.

The flag will be configurable against Job Group and Site. As with other configuration, the job group will be checked if no record is present then the site record will be used.


==Modifiable Customer Contact==
When the PDA requests a customer signature, the Customer Contact Name is defaulted into the text box above the signature. The user is allowed to amend this name, to reflect the customer contact who actually signed for the work.

This customer name must be sent back to the Server.

The Server must save this to the new Job field created for this purpose (CUST_SIGNATORY).

This must be used on the POD/POC/Service reports created instead of the customer name.


==Customer Terms & Conditions ==
When the PDA requests a customer signature, the system should prompt for T&Cs first, if the system has been configured for this. In order to achieve this:
* The Job Group configuration sent to the PDA must now include the new EPL_TNCS field.
* When prompting for customer signature, the PDA must check the Job Group configuration of the Job being confirmed. If this has a TNC Configuration, this should call a new screen to require T&C confirmation. If not, the existing Customer Signature screen will be called instead.
* The new screen will extract the XML tags of the EPL_TNCS field as follows:
** TEXT - this is the text that is always present and fills a scrolling text box on the screen.
** CHECK - these are check boxes that will be displayed for the user to check under the text box. They will consist of the label to be displayed. There can be up to 3 only - any more will be ignored.
* The format used by the site will be as follows:
<TEXT>I certify that the information in A, B and C is correct, and that the carrier is registered.<br />
I confirm that I have fulfilled my duty to apply the waste hierarchy as required by Regulation 12 of the Waste (England and Wales) Regulations 2011. I also confirm that I am legally permitted to release the items from the company detailed in part A to CDL
</TEXT>
<CHECKS>
<INPUT type="checkbox">A) Secure Location</INPUT>
<INPUT type="checkbox">B) Non - Secure Location</INPUT>
<INPUT type="checkbox">C) Customer Not Present</INPUT>
</CHECKS>
* The new screen will have an OK button. At least one of the check boxes must be checked to continue.
* On clicking OK, the user will be taken to the existing Customer Signature screen.
* The Checks tab will be returned and stored in the database in the EPL_TNCS field on the Job record. If check boxes have been ticked, they will have a parameter added to them of "checked", as follows:
<CHECKS>
<INPUT type="checkbox">A) Secure Location</INPUT>
<INPUT type="checkbox" checked="checked">B) Non - Secure Location</INPUT>
<INPUT type="checkbox" checked="checked">C) Customer Not Present</INPUT>
</CHECKS>
* The new screen will have a layout similar to the following:
[[File:293863-PDA-1.PNG]]


==Product Weights==
===Admin===
The Service Product Maintenance screen (product_maintanance.aspx) will be modified to add a Weight column to the grid when data is found.

[[File:293863-ProdWeight-1.PNG|border|600px]]

This will come from the new field on EPOD_SERVICE_PRODUCTS_MASTER.

When adding a new product from this screen (pressing the '''New''' button), the screen will prompt for the Weight. This will be positioned under the Product Status field, in line with it.

[[File:293863-ProdWeight-2.PNG|border|600px]]

Clicking '''Create''' will save the new product with the weight. Weight (and quantity) are not required entries. Weight if entered will be validated as a floating point number.

When editing a product on the grid (by clicking '''Select''', the '''Edit'''), the screen will allow the user to edit the weight in position here, like the Status and Quantity.

[[File:293863-ProdWeight-3.PNG|border|600px]]

Clicking '''Update''' will save the product with any amendments. Weight (and quantity) are not required entries. Weight if entered will be validated as a floating point number.

===Server===
When a PDA client confirms a job as complete, the server will update the Job with the new products (see [[#Ad Hoc Collection Process|"Ad Hoc Collection Process"]]).

When creating these products, the server will get the Service Product record relating to the product line. If found, and the product has a weight against it, this will be multiplied by the product quantity and saved into the weight field against the Job Products record.


==Bespoke Multi-part Proof of Collection Document==
A new POC format will be created, labelled as "CDL". This will match as closely as possible the existing documents used by CDL, as can be seen in [[#Appendix A: POC Document Formats|Appendix A]].

The fields used on both pages are as follows:
*Collection Date: EPL_START_PLANNED_DATE of EPOD_JOB
*CDL Representative: EPL_USER_NAME of EPOD_USER
*Consignment Note Code: CUSTOMER_CODE + JOB_ID of EPOD_JOB
*Waste Remove From: Address information from EPOD_CUSTOMER
*Premises Code: CUSTOMER_CODE of EPOD_JOB
*Waste Taken To: Site Address (taken from the EPOD_CUSTOMER record for the SITE_ID
*CDL Internal Reference: EPL_JOB_ID of EPOD_JOB
*SIC: EPL_CUST_REF of EPOD_JOB
*Qty (Kg): Calculated based on EPL_PRODUCT_WEIGHT * EPL_PRODUCT_QTY_ACTUAL
*Carrier
**Vehicle Reg: EPL_VEHICLE_REG of EPOD_VEHICLE, from EPL_VEHICLE_ID of EPOD_LOAD
**Signature: EPL_ENG_SIGNATURE of EPOD_JOB
**Time: EPL_END_ACTUAL_TIME of EPOD_JOB
**Print Name: EPL_USER_NAME of EPOD_USER
**Date: EPL_END_ACTUAL_DATE of EPOD_JOB
*Consignor:
**Consignor Name: CUST_SIGNATORY
**Signature: EPL_JOB_SIGNATURE
**Date: EPL_END_ACTUAL_DATE of EPOD_JOB
**Time: EPL_END_ACTUAL_TIME of EPOD_JOB
**Consignor Name: EPL_CONTACT + EPL_TELEPHONE of EPOD_CUSTOMER
**Office Instruction: EPL_OFFICE_INSTRUCTION of EPOD_JOB
**Driver Instruction: EPL_INSTRUCTIONS of EPOD_JOB
All other details on the POD will be produced as-is on the pro-forma document.

All existing POD/POC formats include a section that allows the user to send the document via Email. This section in each existing format will be modified to be surrounded by two identical comments, similar to the below:
<pre></pre>

The Email section will be encased in a Division, specifically identified. CSS will be created to ensure that this section is removed when printing, using a CSS style specific for media printing.

For example:

<pre>
<style type="text/css" media="screen">
#emailSection {display: block;}
</style>
<style type="text/css" media="print">
#emailSection {display: none;}
</style>
<div id="emailSection">

.
.
.

</div>
</pre>

{{Note}} Multiple pages will be achieved when printing by using the CSS style '''page-break-before: always;''' set against the first element of the second page.

"PART D - Consignor's Certificate" will be populated based on the values configured in the EPOD_JOB_GROUP record for the job and the check-box input values specified on the EPOD_JOB record.

The text and the check boxes will be formatted on the EPOD format to line up as per the existing documents used by CDL.



==Automatic email of POD/POC==

When a PDA client confirms a job as complete, the server will update the Job to Complete status.

When this is complete, the process will check whether the new Configuration rule "Automatic Email" is set up for the Site of the completed job.

If this is enabled, the process will get the Customer record for the Job's Customer.

If the Email address of the Customer is set, the following actions will be taken:
*The process will render the POD or POC for the Job, in the correct format, according to the Site or Job Group of the completed Job.
*The process will take the rendered page and remove any code in between the new ''EMAIL SECTION'' comment tags
*This rendered page will then be sent to the customer's email address through the standard email mechanism.

==Export Functionality==
The CDL host system will require the ability to poll a webservice within ePOD either on demand or on a poller to retrieve current ePOD job information.
A webservice already exists for exporting data by Job/Load ID and Date. Another two will be added allowing loads and jobs to be exported that have been changed in a date and time range.
The services will require a From Date and Time and will accept a option To Date and Time, this will allow for poller services to simply retrieve all updates since the last poll using only the From Date and Time as well as queries to data in a particular date and time range.
===Job Level===
The Job level webservice should be added that will accept the following structure:

<EPOD_EXPORT_JOB_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">
<DATE_TIME_FROM>2012-10-05T18:40:00</DATE_TIME_FROM>
<DATE_TIME_TO>2012-10-05T18:50:00</DATE_TIME_TO>
</EPOD_EXPORT_JOB_CHANGED>

The webservice will authenticate the user data and then process the message as follows:
IF DATE_TIME_FROM is NULL or Invalid
RETURN ERROR
IF DATE_TIME_TO is Invalid
RETURN ERROR
IF DATE_TIME_TO is NULL
RETURN XML of all jobs that have a last changed date and time greater than the DATE_TIME_FROM field
ELSE
RETURN XML of all jobs that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields

===Load Level===
The Load level webservice should be added that will accept the following structure:

<EPOD_EXPORT_LOAD_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">
<DATE_TIME_FROM>2012-10-05T18:40:00</DATE_TIME_FROM>
<DATE_TIME_TO>2012-10-05T18:50:00</DATE_TIME_TO>
</EPOD_EXPORT_LOAD_CHANGED>

The webservice will authenticate the user data and then process the message as follows:
IF DATE_TIME_FROM is NULL or Invalid
RETURN ERROR
IF DATE_TIME_TO is Invalid
RETURN ERROR
IF DATE_TIME_TO is NULL
RETURN XML of all jobs that have a last changed date and time greater than the DATE_TIME_FROM field
ELSE
RETURN XML of all loads that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields



= Appendix A: POC Document Formats =
[[File:293863-POC-1.JPG|600px]]


[[File:293863-POC-2.JPG|600px]]



= Appendix B: TEST PLAN =

{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=Full System Test for CDL's functionality
|MenuAccess=N/a
|Prerequisites=CDL Test Site configuration
|Objective=Fully test CDL's functionality
}}
{{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Admin
|Notes=Admin Changes
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Create a Ad Hoc collection with Office Instructions (collection with no containers or products)
|Result=
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Check the multi-part POC is produced correctly(printed as well), confirm the weights are calculated correctly.
|Result=
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=On job completion the POC should be emailed to the customers email address, automatically.
|Result=
|Remarks=
|PassFail=
}}{{TestPlan_CycleFooter}}

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=PDA Client
|Notes=PDA Client Changes
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Process a ad hoc collection
|Result=Only Ad Hoc collection tab and instruction tabs should be shown.
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Process a ad hoc collection using products configured in the service product master
|Result=Products should be added in the standard approach
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Check driver signature is prompted
|Result=Driver should sign as well as the customer
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Change the customers name when signing
|Result=This should process back to the admin system and be shown against the job.
|Remarks=
|PassFail=
}}
{{TestPlan_CycleFooter}}


{{Doc_Appendix
|Appendix=C
|Estimate=N
|Glossary=EPOD
|Ref1=[[FS 294229 Whiteline EPOD Modifications]]
|RefV1=0.1
|RefDate1=23/11/2011
|REQ=0
|EST=0
|FS=1.0
|TS=0
|DEV=18.0
|ST=5.0
|IMP=0
|Client={{#var:Client}}
|Year=2011
|FSEST=N
|Rev1=Steve McCartney
|Rev1Title=OBS Representative
|Rev2=Matthew Turner
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 293863 CDL EPOD Modifications

2012-10-08T10:01:56Z

Milesl: /* Export Functionality */

<div class="noprint">
{{#vardefine:Client|CDL}}
{{#vardefine:ClientName|Computer Disposals Limited}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|CDL EPOD Modifications}}
{{#vardefine:Version|1.1}}
{{#vardefine:Date|28th June 2012}}
{{#vardefine:Reference|293863}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==
Development is required to the ''CALIDUS'' ePOD system in order to provide the functionality required by CDL. The requirements have been set out by Matthew Turner from visits to the client as follows:

Computer Disposals collect used computer equipment from companies to recycle at their head office in Warrington.

They are currently implementing a back office solution to handle all job processing. The system will export basic job detail. We need to provide xml/csv schema detail so they can design an import function to pass job detail onto us. They will provide a example of their standard output in November, so we can tell them how to change it.

They have a 2 part delivery note that is largely based on a fixed template created in Word.

Coll Note Part 1 is attached.

Coll Note Part 2 is attached.

I have marked the detail that comes from the CDL back job office import on the 2 part form with a tick.
I have marked the detail that the driver needs to complete with an X.

In the current process, the driver does not generally know the exact quantity of goods he is collecting from a site. A general idea of the number of items to be collected is usually entered in the driver instructions part of the collection note. We refer to driver instructions in ePOD as ‘job instructions’.

On Product QTY Count, you will see that the driver does a manual count of equipment collected. He then does an estimation of weight based on multiplication of set weight per item. The result is entered on the QTY KG boxes on both parts on the collection note.

Example:
(qty count of product) x ( set weight per product ) = QTY (KG)

On Coll Note Part 1 the following rules apply:

In box CRT Monitor QTY (KG), the KG total number is based on:

(qty count of monitors) x ( set weight per monitor ) = QTY (KG)

In box Flat Screen Displays QTY KG, the KG total number is based on:

(qty count of TFT’s) x ( set weight per TFT) + (qty count of laptops) x ( set weight per laptops) = QTY (KG)

In box Waste Refrigerants QTY KG, the KG total number is based on:

(qty count of waste refrigerants) x ( set weight per waste refrigerants ) = QTY (KG)

On Coll Note Part 2 which is the 2nd part of the collection note, the following rules apply:

In box IT Equipment, the KG total number is based on:

Total QTY KG of all collected products except Monitors, TFT’s, Laptops, Waste Refrigerants

Set Weights Info
*1 x Monitor = 12 Kg
*1 x TFT = 8 Kg
*1 x Base = 8 Kg
*1 x General = 2 Kg
*1 x Printer = 5 Kg
*1 x Server = 12 Kg
*1 x Laptop = 8 Kg
*1 x Refrigeration Unit = 50 Kg

Anticipated Process On PDA:
#Driver opens collection job from manifest
#Driver accesses product confirmation
#Driver does QTY count of product
#Result of calculation for QTY KG does not necessarily have to be shown on PDA just electronic collection note back in system.
#Driver signs PDA.
#Customer (Consignor) signs PDA

General Info:

Consignor is ‘Customer‘.

Part E (Disposer of Waste) on both parts of the collection note needs to be replicated on the electronic collection note, but is not interacted with in any way by our system.
Automatic email POD is required on this contract.

General Questions:

Can date and time be automatically provided by the system on the electronic collection note?

Can driver print name and vehicle registration automatically be provided by the system on the electronic collection note?

CDL will be using HTC Touch 2.

== Solution Overview ==
The functionality required is:
*Bespoke Job Import function
*Bespoke Multi-part Proof of Collection
*Multiple Signatures at Delivery/Collection
*Ad Hoc Collection process
*Product Weights
*Automatic email of POD/POC
*Office Instructions
*Modifiable customer contact.

{{Note}} Slight changes to requirements were requested on 28/06/2012 regarding:
* Confirmation of T&Cs when signing for goods.
The format of the collection note has also been modified slightly to allow for the enhanced T&Cs.

The system will be modified to allow the PDA to confirm the T&Cs and allow check-box entry as required. Although this will be data-maintainable, this will not be configurable by the customer.

== Scope ==
*Modifications will be made to version 1.1 of ''CALIDUS'' ePOD system.



= Set-up =

== Pre-requisites ==
*For emailing POC/POD documents, Email must be configured on the ''CALIDUS'' ePOD server.

== Menu Structure ==
None

== Data ==
*The standard products must be created with standard weights.
*For emailing POC/POD documents, customers must be configured with email addresses.



= Functional Description =

==Configuration==
New Rules are required for the configuration of the system:
===Site/Job Group===
*Driver Signature Required Delivery
*Driver Signature Required Collection
*Ad Hoc Collection
*Automatic Email
===Site===
*Job Import Format
*Automatic Email

==Database Modifications==
The EPOD_JOB table will be modified to include a new EPL_OFFICE_INSTRUCTIONS field. This will be in the same format as the current Instructions field.

The EPOD_JOB table will be modified to include a new EPL_CUST_SIGNATORY field. This will be in the same format as the current EPOD_CUSTOMERS Contact field.

The EPOD_JOB table will be modified to include a new EPL_CUST_REF field. This will be a 30-character field. {{Note}} This is also being added under developments for another customer - see the Referenced documents for details.

The EPOD_PRODUCTS table will be modified to include a new Weight field. This will be a floating point field.

The EPOD_SERVICE_PRODUCT_MASTER table will be modified to include a new Weight field. This will be a floating point field.

The EPOD_JOB table will be modified to include a new EPL_TNCS field. This will be a max-character field.

The EPOD_JOB_GROUP table will be modified to include a new EPL_TNCS field. This will be a max-character field.


==Office Instructions==
A new field of office instruction will be added to the EPOD_JOB table. This field will need to be displayed within the Job Details screen. This will be a free text field, identical to the current instructions field.



==Bespoke Job Import Function==

The Import shall be performed via a XML file. The file format must conform to the following schema. The upload shall function so that if there is a single issue with the file, no data will be committed, "All or Nothing". The upload works for both adding and updating data. The upload is available via a manual upload or a web request.

===XML Schema===

A base for the XML import:

<?xml version="1.0" encoding="utf-16"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="EPOD_IMPORT">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_LOADS" maxOccurs="1" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_LOAD" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0" />
<xsd:element name="EPL_LOAD_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_END_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_END_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_USER_ID" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_JOBS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_JOB" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_OFFICE_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_CONTAINERS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CONTAINER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="true" minOccurs="0" />
<xsd:element name="EPL_CONTAINER_PACKAGE_CODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_PACKAGE_DESC" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1" >
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="I"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_REG_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_VIN_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SIM_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_JOBS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_JOB" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_OFFICE_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_CONTAINERS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CONTAINER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CONTAINER_PACKAGE_CODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_PACKAGE_DESC" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="I"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_REG_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_VIN_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SIM_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_CUSTOMERS" maxOccurs="1" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CUSTOMER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE_PRODUCT_MASTERS" nillable="false" maxOccurs="1" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_SERVICE_PRODUCT_MASTER" nillable="false" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_DESCRIPTION" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_STATUS" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="A"/>
<xsd:enumeration value="I"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_QUANTITY" type="xsd:int" />
<xsd:element name="EPL_PRODUCT_WEIGHT" type="xsd:decimal" nillable="true" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="EPL_SITE_ID">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="EPL_USER_ID">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="EPL_USER_PASSWORD">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:schema>



==Ad Hoc Collection Process==

The Ad Hoc collection process will allow users of the PDA to specify items collected, at point of collection. This will appears as a separate tab on the PDA within the Collections menu. Users will be able to select items that currently exists in the EPOD_SERVICE_PRODUCT_MASTER, from a drop down list and add or remove them from the collection. These products will be added to the Loose Products container 00000000.

Once completed the server will then create this container if it does not exist and products.

This will be configurable against the SITE and the JOB GROUP. If configured as off the Ad Hoc tab within the collections menu will be disabled. If this is enabled the tab will be displayed allowing a combination of pre-defined containers and products as well as Ad Hoc additions. The functionality provided by Containers without products means that in the scenario that there are no products/containers pre-defined the Containers and Products tabs will be disabled. If the Loose Product container is pre-defined, the Ad Hoc products will be placed onto this container.


==Multiple Signatures at Delivery/Collection==

When completing a Delivery/Collection, the flag against site for Driver Signature will be checked. If this option is enabled the user will be asked to sign (Driver) as in the service menu.
These details will be stored in the driver signature field within the Job table.

The flag will be configurable against Job Group and Site. As with other configuration, the job group will be checked if no record is present then the site record will be used.


==Modifiable Customer Contact==
When the PDA requests a customer signature, the Customer Contact Name is defaulted into the text box above the signature. The user is allowed to amend this name, to reflect the customer contact who actually signed for the work.

This customer name must be sent back to the Server.

The Server must save this to the new Job field created for this purpose (CUST_SIGNATORY).

This must be used on the POD/POC/Service reports created instead of the customer name.


==Customer Terms & Conditions ==
When the PDA requests a customer signature, the system should prompt for T&Cs first, if the system has been configured for this. In order to achieve this:
* The Job Group configuration sent to the PDA must now include the new EPL_TNCS field.
* When prompting for customer signature, the PDA must check the Job Group configuration of the Job being confirmed. If this has a TNC Configuration, this should call a new screen to require T&C confirmation. If not, the existing Customer Signature screen will be called instead.
* The new screen will extract the XML tags of the EPL_TNCS field as follows:
** TEXT - this is the text that is always present and fills a scrolling text box on the screen.
** CHECK - these are check boxes that will be displayed for the user to check under the text box. They will consist of the label to be displayed. There can be up to 3 only - any more will be ignored.
* The format used by the site will be as follows:
<TEXT>I certify that the information in A, B and C is correct, and that the carrier is registered.<br />
I confirm that I have fulfilled my duty to apply the waste hierarchy as required by Regulation 12 of the Waste (England and Wales) Regulations 2011. I also confirm that I am legally permitted to release the items from the company detailed in part A to CDL
</TEXT>
<CHECKS>
<INPUT type="checkbox">A) Secure Location</INPUT>
<INPUT type="checkbox">B) Non - Secure Location</INPUT>
<INPUT type="checkbox">C) Customer Not Present</INPUT>
</CHECKS>
* The new screen will have an OK button. At least one of the check boxes must be checked to continue.
* On clicking OK, the user will be taken to the existing Customer Signature screen.
* The Checks tab will be returned and stored in the database in the EPL_TNCS field on the Job record. If check boxes have been ticked, they will have a parameter added to them of "checked", as follows:
<CHECKS>
<INPUT type="checkbox">A) Secure Location</INPUT>
<INPUT type="checkbox" checked="checked">B) Non - Secure Location</INPUT>
<INPUT type="checkbox" checked="checked">C) Customer Not Present</INPUT>
</CHECKS>
* The new screen will have a layout similar to the following:
[[File:293863-PDA-1.PNG]]


==Product Weights==
===Admin===
The Service Product Maintenance screen (product_maintanance.aspx) will be modified to add a Weight column to the grid when data is found.

[[File:293863-ProdWeight-1.PNG|border|600px]]

This will come from the new field on EPOD_SERVICE_PRODUCTS_MASTER.

When adding a new product from this screen (pressing the '''New''' button), the screen will prompt for the Weight. This will be positioned under the Product Status field, in line with it.

[[File:293863-ProdWeight-2.PNG|border|600px]]

Clicking '''Create''' will save the new product with the weight. Weight (and quantity) are not required entries. Weight if entered will be validated as a floating point number.

When editing a product on the grid (by clicking '''Select''', the '''Edit'''), the screen will allow the user to edit the weight in position here, like the Status and Quantity.

[[File:293863-ProdWeight-3.PNG|border|600px]]

Clicking '''Update''' will save the product with any amendments. Weight (and quantity) are not required entries. Weight if entered will be validated as a floating point number.

===Server===
When a PDA client confirms a job as complete, the server will update the Job with the new products (see [[#Ad Hoc Collection Process|"Ad Hoc Collection Process"]]).

When creating these products, the server will get the Service Product record relating to the product line. If found, and the product has a weight against it, this will be multiplied by the product quantity and saved into the weight field against the Job Products record.


==Bespoke Multi-part Proof of Collection Document==
A new POC format will be created, labelled as "CDL". This will match as closely as possible the existing documents used by CDL, as can be seen in [[#Appendix A: POC Document Formats|Appendix A]].

The fields used on both pages are as follows:
*Collection Date: EPL_START_PLANNED_DATE of EPOD_JOB
*CDL Representative: EPL_USER_NAME of EPOD_USER
*Consignment Note Code: CUSTOMER_CODE + JOB_ID of EPOD_JOB
*Waste Remove From: Address information from EPOD_CUSTOMER
*Premises Code: CUSTOMER_CODE of EPOD_JOB
*Waste Taken To: Site Address (taken from the EPOD_CUSTOMER record for the SITE_ID
*CDL Internal Reference: EPL_JOB_ID of EPOD_JOB
*SIC: EPL_CUST_REF of EPOD_JOB
*Qty (Kg): Calculated based on EPL_PRODUCT_WEIGHT * EPL_PRODUCT_QTY_ACTUAL
*Carrier
**Vehicle Reg: EPL_VEHICLE_REG of EPOD_VEHICLE, from EPL_VEHICLE_ID of EPOD_LOAD
**Signature: EPL_ENG_SIGNATURE of EPOD_JOB
**Time: EPL_END_ACTUAL_TIME of EPOD_JOB
**Print Name: EPL_USER_NAME of EPOD_USER
**Date: EPL_END_ACTUAL_DATE of EPOD_JOB
*Consignor:
**Consignor Name: CUST_SIGNATORY
**Signature: EPL_JOB_SIGNATURE
**Date: EPL_END_ACTUAL_DATE of EPOD_JOB
**Time: EPL_END_ACTUAL_TIME of EPOD_JOB
**Consignor Name: EPL_CONTACT + EPL_TELEPHONE of EPOD_CUSTOMER
**Office Instruction: EPL_OFFICE_INSTRUCTION of EPOD_JOB
**Driver Instruction: EPL_INSTRUCTIONS of EPOD_JOB
All other details on the POD will be produced as-is on the pro-forma document.

All existing POD/POC formats include a section that allows the user to send the document via Email. This section in each existing format will be modified to be surrounded by two identical comments, similar to the below:
<pre></pre>

The Email section will be encased in a Division, specifically identified. CSS will be created to ensure that this section is removed when printing, using a CSS style specific for media printing.

For example:

<pre>
<style type="text/css" media="screen">
#emailSection {display: block;}
</style>
<style type="text/css" media="print">
#emailSection {display: none;}
</style>
<div id="emailSection">

.
.
.

</div>
</pre>

{{Note}} Multiple pages will be achieved when printing by using the CSS style '''page-break-before: always;''' set against the first element of the second page.

"PART D - Consignor's Certificate" will be populated based on the values configured in the EPOD_JOB_GROUP record for the job and the check-box input values specified on the EPOD_JOB record.

The text and the check boxes will be formatted on the EPOD format to line up as per the existing documents used by CDL.



==Automatic email of POD/POC==

When a PDA client confirms a job as complete, the server will update the Job to Complete status.

When this is complete, the process will check whether the new Configuration rule "Automatic Email" is set up for the Site of the completed job.

If this is enabled, the process will get the Customer record for the Job's Customer.

If the Email address of the Customer is set, the following actions will be taken:
*The process will render the POD or POC for the Job, in the correct format, according to the Site or Job Group of the completed Job.
*The process will take the rendered page and remove any code in between the new ''EMAIL SECTION'' comment tags
*This rendered page will then be sent to the customer's email address through the standard email mechanism.

==Export Functionality==
The CDL host system will require the ability to poll a webservice within ePOD either on demand or on a poller to retrieve current ePOD job information.
A webservice already exists for exporting data by Job/Load ID and Date. Another two will be added allowing loads and jobs to be exported that have been changed in a date and time range.

===Job Level===
The Job level webservice should be added that will accept the following structure:

<EPOD_EXPORT_JOB_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">
<DATE_TIME_FROM>2012-10-05T18:40:00</DATE_TIME_FROM>
<DATE_TIME_TO>2012-10-05T18:50:00</DATE_TIME_TO>
</EPOD_EXPORT_JOB_CHANGED>

The webservice will authenticate the user data and then process the message as follows:
IF DATE_TIME_FROM is NULL or Invalid
RETURN ERROR
IF DATE_TIME_TO is Invalid
RETURN ERROR
IF DATE_TIME_TO is NULL
RETURN XML of all jobs that have a last changed date and time greater than the DATE_TIME_FROM field
ELSE
RETURN XML of all jobs that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields

===Load Level===
The Load level webservice should be added that will accept the following structure:

<EPOD_EXPORT_LOAD_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">
<DATE_TIME_FROM>2012-10-05T18:40:00</DATE_TIME_FROM>
<DATE_TIME_TO>2012-10-05T18:50:00</DATE_TIME_TO>
</EPOD_EXPORT_LOAD_CHANGED>

The webservice will authenticate the user data and then process the message as follows:
IF DATE_TIME_FROM is NULL or Invalid
RETURN ERROR
IF DATE_TIME_TO is Invalid
RETURN ERROR
IF DATE_TIME_TO is NULL
RETURN XML of all jobs that have a last changed date and time greater than the DATE_TIME_FROM field
ELSE
RETURN XML of all loads that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields



= Appendix A: POC Document Formats =
[[File:293863-POC-1.JPG|600px]]


[[File:293863-POC-2.JPG|600px]]



= Appendix B: TEST PLAN =

{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=Full System Test for CDL's functionality
|MenuAccess=N/a
|Prerequisites=CDL Test Site configuration
|Objective=Fully test CDL's functionality
}}
{{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Admin
|Notes=Admin Changes
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Create a Ad Hoc collection with Office Instructions (collection with no containers or products)
|Result=
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Check the multi-part POC is produced correctly(printed as well), confirm the weights are calculated correctly.
|Result=
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=On job completion the POC should be emailed to the customers email address, automatically.
|Result=
|Remarks=
|PassFail=
}}{{TestPlan_CycleFooter}}

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=PDA Client
|Notes=PDA Client Changes
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Process a ad hoc collection
|Result=Only Ad Hoc collection tab and instruction tabs should be shown.
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Process a ad hoc collection using products configured in the service product master
|Result=Products should be added in the standard approach
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Check driver signature is prompted
|Result=Driver should sign as well as the customer
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Change the customers name when signing
|Result=This should process back to the admin system and be shown against the job.
|Remarks=
|PassFail=
}}
{{TestPlan_CycleFooter}}


{{Doc_Appendix
|Appendix=C
|Estimate=N
|Glossary=EPOD
|Ref1=[[FS 294229 Whiteline EPOD Modifications]]
|RefV1=0.1
|RefDate1=23/11/2011
|REQ=0
|EST=0
|FS=1.0
|TS=0
|DEV=18.0
|ST=5.0
|IMP=0
|Client={{#var:Client}}
|Year=2011
|FSEST=N
|Rev1=Steve McCartney
|Rev1Title=OBS Representative
|Rev2=Matthew Turner
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 293863 CDL EPOD Modifications

2012-10-08T09:58:54Z

Milesl: /* Load Level */

<div class="noprint">
{{#vardefine:Client|CDL}}
{{#vardefine:ClientName|Computer Disposals Limited}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|CDL EPOD Modifications}}
{{#vardefine:Version|1.1}}
{{#vardefine:Date|28th June 2012}}
{{#vardefine:Reference|293863}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==
Development is required to the ''CALIDUS'' ePOD system in order to provide the functionality required by CDL. The requirements have been set out by Matthew Turner from visits to the client as follows:

Computer Disposals collect used computer equipment from companies to recycle at their head office in Warrington.

They are currently implementing a back office solution to handle all job processing. The system will export basic job detail. We need to provide xml/csv schema detail so they can design an import function to pass job detail onto us. They will provide a example of their standard output in November, so we can tell them how to change it.

They have a 2 part delivery note that is largely based on a fixed template created in Word.

Coll Note Part 1 is attached.

Coll Note Part 2 is attached.

I have marked the detail that comes from the CDL back job office import on the 2 part form with a tick.
I have marked the detail that the driver needs to complete with an X.

In the current process, the driver does not generally know the exact quantity of goods he is collecting from a site. A general idea of the number of items to be collected is usually entered in the driver instructions part of the collection note. We refer to driver instructions in ePOD as ‘job instructions’.

On Product QTY Count, you will see that the driver does a manual count of equipment collected. He then does an estimation of weight based on multiplication of set weight per item. The result is entered on the QTY KG boxes on both parts on the collection note.

Example:
(qty count of product) x ( set weight per product ) = QTY (KG)

On Coll Note Part 1 the following rules apply:

In box CRT Monitor QTY (KG), the KG total number is based on:

(qty count of monitors) x ( set weight per monitor ) = QTY (KG)

In box Flat Screen Displays QTY KG, the KG total number is based on:

(qty count of TFT’s) x ( set weight per TFT) + (qty count of laptops) x ( set weight per laptops) = QTY (KG)

In box Waste Refrigerants QTY KG, the KG total number is based on:

(qty count of waste refrigerants) x ( set weight per waste refrigerants ) = QTY (KG)

On Coll Note Part 2 which is the 2nd part of the collection note, the following rules apply:

In box IT Equipment, the KG total number is based on:

Total QTY KG of all collected products except Monitors, TFT’s, Laptops, Waste Refrigerants

Set Weights Info
*1 x Monitor = 12 Kg
*1 x TFT = 8 Kg
*1 x Base = 8 Kg
*1 x General = 2 Kg
*1 x Printer = 5 Kg
*1 x Server = 12 Kg
*1 x Laptop = 8 Kg
*1 x Refrigeration Unit = 50 Kg

Anticipated Process On PDA:
#Driver opens collection job from manifest
#Driver accesses product confirmation
#Driver does QTY count of product
#Result of calculation for QTY KG does not necessarily have to be shown on PDA just electronic collection note back in system.
#Driver signs PDA.
#Customer (Consignor) signs PDA

General Info:

Consignor is ‘Customer‘.

Part E (Disposer of Waste) on both parts of the collection note needs to be replicated on the electronic collection note, but is not interacted with in any way by our system.
Automatic email POD is required on this contract.

General Questions:

Can date and time be automatically provided by the system on the electronic collection note?

Can driver print name and vehicle registration automatically be provided by the system on the electronic collection note?

CDL will be using HTC Touch 2.

== Solution Overview ==
The functionality required is:
*Bespoke Job Import function
*Bespoke Multi-part Proof of Collection
*Multiple Signatures at Delivery/Collection
*Ad Hoc Collection process
*Product Weights
*Automatic email of POD/POC
*Office Instructions
*Modifiable customer contact.

{{Note}} Slight changes to requirements were requested on 28/06/2012 regarding:
* Confirmation of T&Cs when signing for goods.
The format of the collection note has also been modified slightly to allow for the enhanced T&Cs.

The system will be modified to allow the PDA to confirm the T&Cs and allow check-box entry as required. Although this will be data-maintainable, this will not be configurable by the customer.

== Scope ==
*Modifications will be made to version 1.1 of ''CALIDUS'' ePOD system.



= Set-up =

== Pre-requisites ==
*For emailing POC/POD documents, Email must be configured on the ''CALIDUS'' ePOD server.

== Menu Structure ==
None

== Data ==
*The standard products must be created with standard weights.
*For emailing POC/POD documents, customers must be configured with email addresses.



= Functional Description =

==Configuration==
New Rules are required for the configuration of the system:
===Site/Job Group===
*Driver Signature Required Delivery
*Driver Signature Required Collection
*Ad Hoc Collection
*Automatic Email
===Site===
*Job Import Format
*Automatic Email

==Database Modifications==
The EPOD_JOB table will be modified to include a new EPL_OFFICE_INSTRUCTIONS field. This will be in the same format as the current Instructions field.

The EPOD_JOB table will be modified to include a new EPL_CUST_SIGNATORY field. This will be in the same format as the current EPOD_CUSTOMERS Contact field.

The EPOD_JOB table will be modified to include a new EPL_CUST_REF field. This will be a 30-character field. {{Note}} This is also being added under developments for another customer - see the Referenced documents for details.

The EPOD_PRODUCTS table will be modified to include a new Weight field. This will be a floating point field.

The EPOD_SERVICE_PRODUCT_MASTER table will be modified to include a new Weight field. This will be a floating point field.

The EPOD_JOB table will be modified to include a new EPL_TNCS field. This will be a max-character field.

The EPOD_JOB_GROUP table will be modified to include a new EPL_TNCS field. This will be a max-character field.


==Office Instructions==
A new field of office instruction will be added to the EPOD_JOB table. This field will need to be displayed within the Job Details screen. This will be a free text field, identical to the current instructions field.



==Bespoke Job Import Function==

The Import shall be performed via a XML file. The file format must conform to the following schema. The upload shall function so that if there is a single issue with the file, no data will be committed, "All or Nothing". The upload works for both adding and updating data. The upload is available via a manual upload or a web request.

===XML Schema===

A base for the XML import:

<?xml version="1.0" encoding="utf-16"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="EPOD_IMPORT">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_LOADS" maxOccurs="1" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_LOAD" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0" />
<xsd:element name="EPL_LOAD_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_END_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_END_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_USER_ID" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_JOBS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_JOB" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_OFFICE_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_CONTAINERS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CONTAINER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="true" minOccurs="0" />
<xsd:element name="EPL_CONTAINER_PACKAGE_CODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_PACKAGE_DESC" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1" >
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="I"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_REG_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_VIN_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SIM_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_JOBS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_JOB" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_OFFICE_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_CONTAINERS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CONTAINER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CONTAINER_PACKAGE_CODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_PACKAGE_DESC" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="I"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_REG_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_VIN_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SIM_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_CUSTOMERS" maxOccurs="1" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CUSTOMER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE_PRODUCT_MASTERS" nillable="false" maxOccurs="1" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_SERVICE_PRODUCT_MASTER" nillable="false" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_DESCRIPTION" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_STATUS" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="A"/>
<xsd:enumeration value="I"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_QUANTITY" type="xsd:int" />
<xsd:element name="EPL_PRODUCT_WEIGHT" type="xsd:decimal" nillable="true" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="EPL_SITE_ID">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="EPL_USER_ID">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="EPL_USER_PASSWORD">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:schema>



==Ad Hoc Collection Process==

The Ad Hoc collection process will allow users of the PDA to specify items collected, at point of collection. This will appears as a separate tab on the PDA within the Collections menu. Users will be able to select items that currently exists in the EPOD_SERVICE_PRODUCT_MASTER, from a drop down list and add or remove them from the collection. These products will be added to the Loose Products container 00000000.

Once completed the server will then create this container if it does not exist and products.

This will be configurable against the SITE and the JOB GROUP. If configured as off the Ad Hoc tab within the collections menu will be disabled. If this is enabled the tab will be displayed allowing a combination of pre-defined containers and products as well as Ad Hoc additions. The functionality provided by Containers without products means that in the scenario that there are no products/containers pre-defined the Containers and Products tabs will be disabled. If the Loose Product container is pre-defined, the Ad Hoc products will be placed onto this container.


==Multiple Signatures at Delivery/Collection==

When completing a Delivery/Collection, the flag against site for Driver Signature will be checked. If this option is enabled the user will be asked to sign (Driver) as in the service menu.
These details will be stored in the driver signature field within the Job table.

The flag will be configurable against Job Group and Site. As with other configuration, the job group will be checked if no record is present then the site record will be used.


==Modifiable Customer Contact==
When the PDA requests a customer signature, the Customer Contact Name is defaulted into the text box above the signature. The user is allowed to amend this name, to reflect the customer contact who actually signed for the work.

This customer name must be sent back to the Server.

The Server must save this to the new Job field created for this purpose (CUST_SIGNATORY).

This must be used on the POD/POC/Service reports created instead of the customer name.


==Customer Terms & Conditions ==
When the PDA requests a customer signature, the system should prompt for T&Cs first, if the system has been configured for this. In order to achieve this:
* The Job Group configuration sent to the PDA must now include the new EPL_TNCS field.
* When prompting for customer signature, the PDA must check the Job Group configuration of the Job being confirmed. If this has a TNC Configuration, this should call a new screen to require T&C confirmation. If not, the existing Customer Signature screen will be called instead.
* The new screen will extract the XML tags of the EPL_TNCS field as follows:
** TEXT - this is the text that is always present and fills a scrolling text box on the screen.
** CHECK - these are check boxes that will be displayed for the user to check under the text box. They will consist of the label to be displayed. There can be up to 3 only - any more will be ignored.
* The format used by the site will be as follows:
<TEXT>I certify that the information in A, B and C is correct, and that the carrier is registered.<br />
I confirm that I have fulfilled my duty to apply the waste hierarchy as required by Regulation 12 of the Waste (England and Wales) Regulations 2011. I also confirm that I am legally permitted to release the items from the company detailed in part A to CDL
</TEXT>
<CHECKS>
<INPUT type="checkbox">A) Secure Location</INPUT>
<INPUT type="checkbox">B) Non - Secure Location</INPUT>
<INPUT type="checkbox">C) Customer Not Present</INPUT>
</CHECKS>
* The new screen will have an OK button. At least one of the check boxes must be checked to continue.
* On clicking OK, the user will be taken to the existing Customer Signature screen.
* The Checks tab will be returned and stored in the database in the EPL_TNCS field on the Job record. If check boxes have been ticked, they will have a parameter added to them of "checked", as follows:
<CHECKS>
<INPUT type="checkbox">A) Secure Location</INPUT>
<INPUT type="checkbox" checked="checked">B) Non - Secure Location</INPUT>
<INPUT type="checkbox" checked="checked">C) Customer Not Present</INPUT>
</CHECKS>
* The new screen will have a layout similar to the following:
[[File:293863-PDA-1.PNG]]


==Product Weights==
===Admin===
The Service Product Maintenance screen (product_maintanance.aspx) will be modified to add a Weight column to the grid when data is found.

[[File:293863-ProdWeight-1.PNG|border|600px]]

This will come from the new field on EPOD_SERVICE_PRODUCTS_MASTER.

When adding a new product from this screen (pressing the '''New''' button), the screen will prompt for the Weight. This will be positioned under the Product Status field, in line with it.

[[File:293863-ProdWeight-2.PNG|border|600px]]

Clicking '''Create''' will save the new product with the weight. Weight (and quantity) are not required entries. Weight if entered will be validated as a floating point number.

When editing a product on the grid (by clicking '''Select''', the '''Edit'''), the screen will allow the user to edit the weight in position here, like the Status and Quantity.

[[File:293863-ProdWeight-3.PNG|border|600px]]

Clicking '''Update''' will save the product with any amendments. Weight (and quantity) are not required entries. Weight if entered will be validated as a floating point number.

===Server===
When a PDA client confirms a job as complete, the server will update the Job with the new products (see [[#Ad Hoc Collection Process|"Ad Hoc Collection Process"]]).

When creating these products, the server will get the Service Product record relating to the product line. If found, and the product has a weight against it, this will be multiplied by the product quantity and saved into the weight field against the Job Products record.


==Bespoke Multi-part Proof of Collection Document==
A new POC format will be created, labelled as "CDL". This will match as closely as possible the existing documents used by CDL, as can be seen in [[#Appendix A: POC Document Formats|Appendix A]].

The fields used on both pages are as follows:
*Collection Date: EPL_START_PLANNED_DATE of EPOD_JOB
*CDL Representative: EPL_USER_NAME of EPOD_USER
*Consignment Note Code: CUSTOMER_CODE + JOB_ID of EPOD_JOB
*Waste Remove From: Address information from EPOD_CUSTOMER
*Premises Code: CUSTOMER_CODE of EPOD_JOB
*Waste Taken To: Site Address (taken from the EPOD_CUSTOMER record for the SITE_ID
*CDL Internal Reference: EPL_JOB_ID of EPOD_JOB
*SIC: EPL_CUST_REF of EPOD_JOB
*Qty (Kg): Calculated based on EPL_PRODUCT_WEIGHT * EPL_PRODUCT_QTY_ACTUAL
*Carrier
**Vehicle Reg: EPL_VEHICLE_REG of EPOD_VEHICLE, from EPL_VEHICLE_ID of EPOD_LOAD
**Signature: EPL_ENG_SIGNATURE of EPOD_JOB
**Time: EPL_END_ACTUAL_TIME of EPOD_JOB
**Print Name: EPL_USER_NAME of EPOD_USER
**Date: EPL_END_ACTUAL_DATE of EPOD_JOB
*Consignor:
**Consignor Name: CUST_SIGNATORY
**Signature: EPL_JOB_SIGNATURE
**Date: EPL_END_ACTUAL_DATE of EPOD_JOB
**Time: EPL_END_ACTUAL_TIME of EPOD_JOB
**Consignor Name: EPL_CONTACT + EPL_TELEPHONE of EPOD_CUSTOMER
**Office Instruction: EPL_OFFICE_INSTRUCTION of EPOD_JOB
**Driver Instruction: EPL_INSTRUCTIONS of EPOD_JOB
All other details on the POD will be produced as-is on the pro-forma document.

All existing POD/POC formats include a section that allows the user to send the document via Email. This section in each existing format will be modified to be surrounded by two identical comments, similar to the below:
<pre></pre>

The Email section will be encased in a Division, specifically identified. CSS will be created to ensure that this section is removed when printing, using a CSS style specific for media printing.

For example:

<pre>
<style type="text/css" media="screen">
#emailSection {display: block;}
</style>
<style type="text/css" media="print">
#emailSection {display: none;}
</style>
<div id="emailSection">

.
.
.

</div>
</pre>

{{Note}} Multiple pages will be achieved when printing by using the CSS style '''page-break-before: always;''' set against the first element of the second page.

"PART D - Consignor's Certificate" will be populated based on the values configured in the EPOD_JOB_GROUP record for the job and the check-box input values specified on the EPOD_JOB record.

The text and the check boxes will be formatted on the EPOD format to line up as per the existing documents used by CDL.



==Automatic email of POD/POC==

When a PDA client confirms a job as complete, the server will update the Job to Complete status.

When this is complete, the process will check whether the new Configuration rule "Automatic Email" is set up for the Site of the completed job.

If this is enabled, the process will get the Customer record for the Job's Customer.

If the Email address of the Customer is set, the following actions will be taken:
*The process will render the POD or POC for the Job, in the correct format, according to the Site or Job Group of the completed Job.
*The process will take the rendered page and remove any code in between the new ''EMAIL SECTION'' comment tags
*This rendered page will then be sent to the customer's email address through the standard email mechanism.

==Export Functionality==
The CDL host system will require the ability to poll a webservice within ePOD either on demand or on a poller to retrieve current ePOD job information.
A webservice already exists for exporting data by Job/Load ID and Date. Another two will be added allowing loads and jobs to be exported that have been changed in a date and time range.

===Job Level===
The Job level webservice should be added that will accept the following structure:

<EPOD_EXPORT_JOB_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">
<DATE_TIME_FROM></DATE_TIME_FROM>
<DATE_TIME_TO></DATE_TIME_TO>
</EPOD_EXPORT_JOB_CHANGED>

The webservice will authenticate the user data and then process the message as follows:
IF DATE_TIME_FROM is NULL or Invalid
RETURN ERROR
IF DATE_TIME_TO is Invalid
RETURN ERROR
IF DATE_TIME_TO is NULL
RETURN XML of all jobs that have a last changed date and time greater than the DATE_TIME_FROM field
ELSE
RETURN XML of all jobs that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields

===Load Level===
The Load level webservice should be added that will accept the following structure:

<EPOD_EXPORT_LOAD_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">
<DATE_TIME_FROM></DATE_TIME_FROM>
<DATE_TIME_TO></DATE_TIME_TO>
</EPOD_EXPORT_LOAD_CHANGED>

The webservice will authenticate the user data and then process the message as follows:
IF DATE_TIME_FROM is NULL or Invalid
RETURN ERROR
IF DATE_TIME_TO is Invalid
RETURN ERROR
IF DATE_TIME_TO is NULL
RETURN XML of all jobs that have a last changed date and time greater than the DATE_TIME_FROM field
ELSE
RETURN XML of all loads that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields



= Appendix A: POC Document Formats =
[[File:293863-POC-1.JPG|600px]]


[[File:293863-POC-2.JPG|600px]]



= Appendix B: TEST PLAN =

{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=Full System Test for CDL's functionality
|MenuAccess=N/a
|Prerequisites=CDL Test Site configuration
|Objective=Fully test CDL's functionality
}}
{{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Admin
|Notes=Admin Changes
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Create a Ad Hoc collection with Office Instructions (collection with no containers or products)
|Result=
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Check the multi-part POC is produced correctly(printed as well), confirm the weights are calculated correctly.
|Result=
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=On job completion the POC should be emailed to the customers email address, automatically.
|Result=
|Remarks=
|PassFail=
}}{{TestPlan_CycleFooter}}

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=PDA Client
|Notes=PDA Client Changes
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Process a ad hoc collection
|Result=Only Ad Hoc collection tab and instruction tabs should be shown.
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Process a ad hoc collection using products configured in the service product master
|Result=Products should be added in the standard approach
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Check driver signature is prompted
|Result=Driver should sign as well as the customer
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Change the customers name when signing
|Result=This should process back to the admin system and be shown against the job.
|Remarks=
|PassFail=
}}
{{TestPlan_CycleFooter}}


{{Doc_Appendix
|Appendix=C
|Estimate=N
|Glossary=EPOD
|Ref1=[[FS 294229 Whiteline EPOD Modifications]]
|RefV1=0.1
|RefDate1=23/11/2011
|REQ=0
|EST=0
|FS=1.0
|TS=0
|DEV=18.0
|ST=5.0
|IMP=0
|Client={{#var:Client}}
|Year=2011
|FSEST=N
|Rev1=Steve McCartney
|Rev1Title=OBS Representative
|Rev2=Matthew Turner
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 293863 CDL EPOD Modifications

2012-10-08T09:44:39Z

Milesl: /* Automatic email of POD/POC */

<div class="noprint">
{{#vardefine:Client|CDL}}
{{#vardefine:ClientName|Computer Disposals Limited}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|CDL EPOD Modifications}}
{{#vardefine:Version|1.1}}
{{#vardefine:Date|28th June 2012}}
{{#vardefine:Reference|293863}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==
Development is required to the ''CALIDUS'' ePOD system in order to provide the functionality required by CDL. The requirements have been set out by Matthew Turner from visits to the client as follows:

Computer Disposals collect used computer equipment from companies to recycle at their head office in Warrington.

They are currently implementing a back office solution to handle all job processing. The system will export basic job detail. We need to provide xml/csv schema detail so they can design an import function to pass job detail onto us. They will provide a example of their standard output in November, so we can tell them how to change it.

They have a 2 part delivery note that is largely based on a fixed template created in Word.

Coll Note Part 1 is attached.

Coll Note Part 2 is attached.

I have marked the detail that comes from the CDL back job office import on the 2 part form with a tick.
I have marked the detail that the driver needs to complete with an X.

In the current process, the driver does not generally know the exact quantity of goods he is collecting from a site. A general idea of the number of items to be collected is usually entered in the driver instructions part of the collection note. We refer to driver instructions in ePOD as ‘job instructions’.

On Product QTY Count, you will see that the driver does a manual count of equipment collected. He then does an estimation of weight based on multiplication of set weight per item. The result is entered on the QTY KG boxes on both parts on the collection note.

Example:
(qty count of product) x ( set weight per product ) = QTY (KG)

On Coll Note Part 1 the following rules apply:

In box CRT Monitor QTY (KG), the KG total number is based on:

(qty count of monitors) x ( set weight per monitor ) = QTY (KG)

In box Flat Screen Displays QTY KG, the KG total number is based on:

(qty count of TFT’s) x ( set weight per TFT) + (qty count of laptops) x ( set weight per laptops) = QTY (KG)

In box Waste Refrigerants QTY KG, the KG total number is based on:

(qty count of waste refrigerants) x ( set weight per waste refrigerants ) = QTY (KG)

On Coll Note Part 2 which is the 2nd part of the collection note, the following rules apply:

In box IT Equipment, the KG total number is based on:

Total QTY KG of all collected products except Monitors, TFT’s, Laptops, Waste Refrigerants

Set Weights Info
*1 x Monitor = 12 Kg
*1 x TFT = 8 Kg
*1 x Base = 8 Kg
*1 x General = 2 Kg
*1 x Printer = 5 Kg
*1 x Server = 12 Kg
*1 x Laptop = 8 Kg
*1 x Refrigeration Unit = 50 Kg

Anticipated Process On PDA:
#Driver opens collection job from manifest
#Driver accesses product confirmation
#Driver does QTY count of product
#Result of calculation for QTY KG does not necessarily have to be shown on PDA just electronic collection note back in system.
#Driver signs PDA.
#Customer (Consignor) signs PDA

General Info:

Consignor is ‘Customer‘.

Part E (Disposer of Waste) on both parts of the collection note needs to be replicated on the electronic collection note, but is not interacted with in any way by our system.
Automatic email POD is required on this contract.

General Questions:

Can date and time be automatically provided by the system on the electronic collection note?

Can driver print name and vehicle registration automatically be provided by the system on the electronic collection note?

CDL will be using HTC Touch 2.

== Solution Overview ==
The functionality required is:
*Bespoke Job Import function
*Bespoke Multi-part Proof of Collection
*Multiple Signatures at Delivery/Collection
*Ad Hoc Collection process
*Product Weights
*Automatic email of POD/POC
*Office Instructions
*Modifiable customer contact.

{{Note}} Slight changes to requirements were requested on 28/06/2012 regarding:
* Confirmation of T&Cs when signing for goods.
The format of the collection note has also been modified slightly to allow for the enhanced T&Cs.

The system will be modified to allow the PDA to confirm the T&Cs and allow check-box entry as required. Although this will be data-maintainable, this will not be configurable by the customer.

== Scope ==
*Modifications will be made to version 1.1 of ''CALIDUS'' ePOD system.



= Set-up =

== Pre-requisites ==
*For emailing POC/POD documents, Email must be configured on the ''CALIDUS'' ePOD server.

== Menu Structure ==
None

== Data ==
*The standard products must be created with standard weights.
*For emailing POC/POD documents, customers must be configured with email addresses.



= Functional Description =

==Configuration==
New Rules are required for the configuration of the system:
===Site/Job Group===
*Driver Signature Required Delivery
*Driver Signature Required Collection
*Ad Hoc Collection
*Automatic Email
===Site===
*Job Import Format
*Automatic Email

==Database Modifications==
The EPOD_JOB table will be modified to include a new EPL_OFFICE_INSTRUCTIONS field. This will be in the same format as the current Instructions field.

The EPOD_JOB table will be modified to include a new EPL_CUST_SIGNATORY field. This will be in the same format as the current EPOD_CUSTOMERS Contact field.

The EPOD_JOB table will be modified to include a new EPL_CUST_REF field. This will be a 30-character field. {{Note}} This is also being added under developments for another customer - see the Referenced documents for details.

The EPOD_PRODUCTS table will be modified to include a new Weight field. This will be a floating point field.

The EPOD_SERVICE_PRODUCT_MASTER table will be modified to include a new Weight field. This will be a floating point field.

The EPOD_JOB table will be modified to include a new EPL_TNCS field. This will be a max-character field.

The EPOD_JOB_GROUP table will be modified to include a new EPL_TNCS field. This will be a max-character field.


==Office Instructions==
A new field of office instruction will be added to the EPOD_JOB table. This field will need to be displayed within the Job Details screen. This will be a free text field, identical to the current instructions field.



==Bespoke Job Import Function==

The Import shall be performed via a XML file. The file format must conform to the following schema. The upload shall function so that if there is a single issue with the file, no data will be committed, "All or Nothing". The upload works for both adding and updating data. The upload is available via a manual upload or a web request.

===XML Schema===

A base for the XML import:

<?xml version="1.0" encoding="utf-16"?>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" version="1.0" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:element name="EPOD_IMPORT">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_LOADS" maxOccurs="1" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_LOAD" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0" />
<xsd:element name="EPL_LOAD_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_END_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_END_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_LOAD_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_USER_ID" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_JOBS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_JOB" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_OFFICE_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_CONTAINERS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CONTAINER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="true" minOccurs="0" />
<xsd:element name="EPL_CONTAINER_PACKAGE_CODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_PACKAGE_DESC" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1" >
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="I"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_REG_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_VIN_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SIM_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_JOBS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_JOB" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_LOAD_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="12" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="C"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="5" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_OFFICE_INSTRUCTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_START_PLANNED_DATE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_START_PLANNED_TIME" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_DISTANCE_PLANNED" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_CONTAINERS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CONTAINER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="true" minOccurs="0"/>
<xsd:element name="EPL_CONTAINER_PACKAGE_CODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="4" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_PACKAGE_DESC" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTAINER_ID" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_PRODUCTS" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_PRODUCT" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SEQUENCE" type="xsd:int" nillable="false"/>
<xsd:element name="EPL_DESCRIPTION" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_QTY_PLANNED" type="xsd:int" nillable="false"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE" nillable="true" minOccurs="0" maxOccurs="1">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_JOB_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SERVICE_TYPE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="D"/>
<xsd:enumeration value="I"/>
<xsd:enumeration value="S"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_REG_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="15" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_VIN_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_SIM_NUMBER" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_CUSTOMERS" maxOccurs="1" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_CUSTOMER" nillable="true" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="20" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CUSTOMER_NAME" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_1" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_2" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_3" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_ADDRESS_4" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_POSTCODE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:pattern value="^([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9]?[A-Za-z])))) {0,1}[0-9][A-Za-z]{2})$" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_CONTACT" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_TELEPHONE" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="50" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_EMAIL" nillable="true" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="255" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="EPOD_SERVICE_PRODUCT_MASTERS" nillable="false" maxOccurs="1" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPOD_SERVICE_PRODUCT_MASTER" nillable="false" minOccurs="0">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="EPL_SITE_ID" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_CODE" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_PRODUCT_GROUP" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_DESCRIPTION" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="40" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_STATUS" nillable="false">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="A"/>
<xsd:enumeration value="I"/>
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
<xsd:element name="EPL_QUANTITY" type="xsd:int" />
<xsd:element name="EPL_PRODUCT_WEIGHT" type="xsd:decimal" nillable="true" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
<xsd:attribute name="EPL_SITE_ID">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="EPL_USER_ID">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="10" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
<xsd:attribute name="EPL_USER_PASSWORD">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:maxLength value="100" />
</xsd:restriction>
</xsd:simpleType>
</xsd:attribute>
</xsd:complexType>
</xsd:element>
</xsd:schema>



==Ad Hoc Collection Process==

The Ad Hoc collection process will allow users of the PDA to specify items collected, at point of collection. This will appears as a separate tab on the PDA within the Collections menu. Users will be able to select items that currently exists in the EPOD_SERVICE_PRODUCT_MASTER, from a drop down list and add or remove them from the collection. These products will be added to the Loose Products container 00000000.

Once completed the server will then create this container if it does not exist and products.

This will be configurable against the SITE and the JOB GROUP. If configured as off the Ad Hoc tab within the collections menu will be disabled. If this is enabled the tab will be displayed allowing a combination of pre-defined containers and products as well as Ad Hoc additions. The functionality provided by Containers without products means that in the scenario that there are no products/containers pre-defined the Containers and Products tabs will be disabled. If the Loose Product container is pre-defined, the Ad Hoc products will be placed onto this container.


==Multiple Signatures at Delivery/Collection==

When completing a Delivery/Collection, the flag against site for Driver Signature will be checked. If this option is enabled the user will be asked to sign (Driver) as in the service menu.
These details will be stored in the driver signature field within the Job table.

The flag will be configurable against Job Group and Site. As with other configuration, the job group will be checked if no record is present then the site record will be used.


==Modifiable Customer Contact==
When the PDA requests a customer signature, the Customer Contact Name is defaulted into the text box above the signature. The user is allowed to amend this name, to reflect the customer contact who actually signed for the work.

This customer name must be sent back to the Server.

The Server must save this to the new Job field created for this purpose (CUST_SIGNATORY).

This must be used on the POD/POC/Service reports created instead of the customer name.


==Customer Terms & Conditions ==
When the PDA requests a customer signature, the system should prompt for T&Cs first, if the system has been configured for this. In order to achieve this:
* The Job Group configuration sent to the PDA must now include the new EPL_TNCS field.
* When prompting for customer signature, the PDA must check the Job Group configuration of the Job being confirmed. If this has a TNC Configuration, this should call a new screen to require T&C confirmation. If not, the existing Customer Signature screen will be called instead.
* The new screen will extract the XML tags of the EPL_TNCS field as follows:
** TEXT - this is the text that is always present and fills a scrolling text box on the screen.
** CHECK - these are check boxes that will be displayed for the user to check under the text box. They will consist of the label to be displayed. There can be up to 3 only - any more will be ignored.
* The format used by the site will be as follows:
<TEXT>I certify that the information in A, B and C is correct, and that the carrier is registered.<br />
I confirm that I have fulfilled my duty to apply the waste hierarchy as required by Regulation 12 of the Waste (England and Wales) Regulations 2011. I also confirm that I am legally permitted to release the items from the company detailed in part A to CDL
</TEXT>
<CHECKS>
<INPUT type="checkbox">A) Secure Location</INPUT>
<INPUT type="checkbox">B) Non - Secure Location</INPUT>
<INPUT type="checkbox">C) Customer Not Present</INPUT>
</CHECKS>
* The new screen will have an OK button. At least one of the check boxes must be checked to continue.
* On clicking OK, the user will be taken to the existing Customer Signature screen.
* The Checks tab will be returned and stored in the database in the EPL_TNCS field on the Job record. If check boxes have been ticked, they will have a parameter added to them of "checked", as follows:
<CHECKS>
<INPUT type="checkbox">A) Secure Location</INPUT>
<INPUT type="checkbox" checked="checked">B) Non - Secure Location</INPUT>
<INPUT type="checkbox" checked="checked">C) Customer Not Present</INPUT>
</CHECKS>
* The new screen will have a layout similar to the following:
[[File:293863-PDA-1.PNG]]


==Product Weights==
===Admin===
The Service Product Maintenance screen (product_maintanance.aspx) will be modified to add a Weight column to the grid when data is found.

[[File:293863-ProdWeight-1.PNG|border|600px]]

This will come from the new field on EPOD_SERVICE_PRODUCTS_MASTER.

When adding a new product from this screen (pressing the '''New''' button), the screen will prompt for the Weight. This will be positioned under the Product Status field, in line with it.

[[File:293863-ProdWeight-2.PNG|border|600px]]

Clicking '''Create''' will save the new product with the weight. Weight (and quantity) are not required entries. Weight if entered will be validated as a floating point number.

When editing a product on the grid (by clicking '''Select''', the '''Edit'''), the screen will allow the user to edit the weight in position here, like the Status and Quantity.

[[File:293863-ProdWeight-3.PNG|border|600px]]

Clicking '''Update''' will save the product with any amendments. Weight (and quantity) are not required entries. Weight if entered will be validated as a floating point number.

===Server===
When a PDA client confirms a job as complete, the server will update the Job with the new products (see [[#Ad Hoc Collection Process|"Ad Hoc Collection Process"]]).

When creating these products, the server will get the Service Product record relating to the product line. If found, and the product has a weight against it, this will be multiplied by the product quantity and saved into the weight field against the Job Products record.


==Bespoke Multi-part Proof of Collection Document==
A new POC format will be created, labelled as "CDL". This will match as closely as possible the existing documents used by CDL, as can be seen in [[#Appendix A: POC Document Formats|Appendix A]].

The fields used on both pages are as follows:
*Collection Date: EPL_START_PLANNED_DATE of EPOD_JOB
*CDL Representative: EPL_USER_NAME of EPOD_USER
*Consignment Note Code: CUSTOMER_CODE + JOB_ID of EPOD_JOB
*Waste Remove From: Address information from EPOD_CUSTOMER
*Premises Code: CUSTOMER_CODE of EPOD_JOB
*Waste Taken To: Site Address (taken from the EPOD_CUSTOMER record for the SITE_ID
*CDL Internal Reference: EPL_JOB_ID of EPOD_JOB
*SIC: EPL_CUST_REF of EPOD_JOB
*Qty (Kg): Calculated based on EPL_PRODUCT_WEIGHT * EPL_PRODUCT_QTY_ACTUAL
*Carrier
**Vehicle Reg: EPL_VEHICLE_REG of EPOD_VEHICLE, from EPL_VEHICLE_ID of EPOD_LOAD
**Signature: EPL_ENG_SIGNATURE of EPOD_JOB
**Time: EPL_END_ACTUAL_TIME of EPOD_JOB
**Print Name: EPL_USER_NAME of EPOD_USER
**Date: EPL_END_ACTUAL_DATE of EPOD_JOB
*Consignor:
**Consignor Name: CUST_SIGNATORY
**Signature: EPL_JOB_SIGNATURE
**Date: EPL_END_ACTUAL_DATE of EPOD_JOB
**Time: EPL_END_ACTUAL_TIME of EPOD_JOB
**Consignor Name: EPL_CONTACT + EPL_TELEPHONE of EPOD_CUSTOMER
**Office Instruction: EPL_OFFICE_INSTRUCTION of EPOD_JOB
**Driver Instruction: EPL_INSTRUCTIONS of EPOD_JOB
All other details on the POD will be produced as-is on the pro-forma document.

All existing POD/POC formats include a section that allows the user to send the document via Email. This section in each existing format will be modified to be surrounded by two identical comments, similar to the below:
<pre></pre>

The Email section will be encased in a Division, specifically identified. CSS will be created to ensure that this section is removed when printing, using a CSS style specific for media printing.

For example:

<pre>
<style type="text/css" media="screen">
#emailSection {display: block;}
</style>
<style type="text/css" media="print">
#emailSection {display: none;}
</style>
<div id="emailSection">

.
.
.

</div>
</pre>

{{Note}} Multiple pages will be achieved when printing by using the CSS style '''page-break-before: always;''' set against the first element of the second page.

"PART D - Consignor's Certificate" will be populated based on the values configured in the EPOD_JOB_GROUP record for the job and the check-box input values specified on the EPOD_JOB record.

The text and the check boxes will be formatted on the EPOD format to line up as per the existing documents used by CDL.



==Automatic email of POD/POC==

When a PDA client confirms a job as complete, the server will update the Job to Complete status.

When this is complete, the process will check whether the new Configuration rule "Automatic Email" is set up for the Site of the completed job.

If this is enabled, the process will get the Customer record for the Job's Customer.

If the Email address of the Customer is set, the following actions will be taken:
*The process will render the POD or POC for the Job, in the correct format, according to the Site or Job Group of the completed Job.
*The process will take the rendered page and remove any code in between the new ''EMAIL SECTION'' comment tags
*This rendered page will then be sent to the customer's email address through the standard email mechanism.

==Export Functionality==
The CDL host system will require the ability to poll a webservice within ePOD either on demand or on a poller to retrieve current ePOD job information.
A webservice already exists for exporting data by Job/Load ID and Date. Another two will be added allowing loads and jobs to be exported that have been changed in a date and time range.

===Job Level===
The Job level webservice should be added that will accept the following structure:

<EPOD_EXPORT_JOB_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">
<DATE_TIME_FROM></DATE_TIME_FROM>
<DATE_TIME_TO></DATE_TIME_TO>
</EPOD_EXPORT_JOB_CHANGED>

The webservice will authenticate the user data and then process the message as follows:
IF DATE_TIME_FROM is NULL or Invalid
RETURN ERROR
IF DATE_TIME_TO is Invalid
RETURN ERROR
IF DATE_TIME_TO is NULL
RETURN XML of all jobs that have a last changed date and time greater than the DATE_TIME_FROM field
ELSE
RETURN XML of all jobs that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields

===Load Level===
The Load level webservice should be added that will accept the following structure:

<EPOD_EXPORT_LOAD_CHANGED EPL_USER_ID="" EPL_USER_PASSWORD="" EPL_SITE_ID="">
<DATE_TIME_FROM></DATE_TIME_FROM>
<DATE_TIME_TO></DATE_TIME_TO>
</EPOD_EXPORT_LOAD_CHANGED>

The webservice will authenticate the user data and then process the message as follows:
IF DATE_TIME_FROM is NULL or Invalid
RETURN ERROR
IF DATE_TIME_TO is Invalid
RETURN ERROR
IF DATE_TIME_TO is NULL
RETURN XML of all jobs that have a last changed date and time greater than the DATE_TIME_FROM field
ELSE
RETURN XML of all jobs that have a last changed date and time between the DATE_TIME_FROM and DATE_TIME_TO fields



= Appendix A: POC Document Formats =
[[File:293863-POC-1.JPG|600px]]


[[File:293863-POC-2.JPG|600px]]



= Appendix B: TEST PLAN =

{{TestPlan_Header
|Title={{#var:Doc_Title}}
|Log={{#var:Reference}}
|Description=Full System Test for CDL's functionality
|MenuAccess=N/a
|Prerequisites=CDL Test Site configuration
|Objective=Fully test CDL's functionality
}}
{{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}
{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Admin
|Notes=Admin Changes
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Create a Ad Hoc collection with Office Instructions (collection with no containers or products)
|Result=
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Check the multi-part POC is produced correctly(printed as well), confirm the weights are calculated correctly.
|Result=
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=On job completion the POC should be emailed to the customers email address, automatically.
|Result=
|Remarks=
|PassFail=
}}{{TestPlan_CycleFooter}}

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=PDA Client
|Notes=PDA Client Changes
}}  {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Process a ad hoc collection
|Result=Only Ad Hoc collection tab and instruction tabs should be shown.
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Process a ad hoc collection using products configured in the service product master
|Result=Products should be added in the standard approach
|Remarks=
|PassFail=
}} {{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Check driver signature is prompted
|Result=Driver should sign as well as the customer
|Remarks=
|PassFail=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.1 }} }}
|Action=Change the customers name when signing
|Result=This should process back to the admin system and be shown against the job.
|Remarks=
|PassFail=
}}
{{TestPlan_CycleFooter}}


{{Doc_Appendix
|Appendix=C
|Estimate=N
|Glossary=EPOD
|Ref1=[[FS 294229 Whiteline EPOD Modifications]]
|RefV1=0.1
|RefDate1=23/11/2011
|REQ=0
|EST=0
|FS=1.0
|TS=0
|DEV=18.0
|ST=5.0
|IMP=0
|Client={{#var:Client}}
|Year=2011
|FSEST=N
|Rev1=Steve McCartney
|Rev1Title=OBS Representative
|Rev2=Matthew Turner
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 299880 EuLoS EPOD Modifications

2012-06-20T10:54:03Z

Milesl: /* PDA Changes */

<div class="noprint">
{{#vardefine:Client|EUL}}
{{#vardefine:ClientName|EuLoS}}
{{#vardefine:System|''CALIDUS'' EPOD}}
{{#vardefine:Doc_Title|EuLoS EPOD Modifications}}
{{#vardefine:Version|0.4}}
{{#vardefine:Date|11th June 2012}}
{{#vardefine:Reference|299880}}
{{#vardefine:Year|2012}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==
=== Admin Functionality ===
Jobs are created within the Admin screens or sent to the system through the standard Web Services (to be slightly modified to accept some new fields).

A method will be added to the Admin Job Creation screen to copy a collection to a delivery once created (if linked collections/deliveries are being used) – this will ease data creation for the Admin users.

The Admin User will enter the vehicles to be collected/delivered as containers against the job – user enters code as the vehicle registration, description is the make/model. The screen will be modified so that the labels are more descriptive of a Vehicle Delivery process (i.e. Vehicle Reg, Make/Model, etc)

Each vehicle and registration will be added as a separate line - if the operation is not aware of the car registration at the time of entering the job, the registration can be entered as a generic line (i.e. CAR1, CAR2, etc) or left blank.

The jobs will be assigned to loads, and the loads assigned to users through the Admin screens as per the existing functionality.

=== PDA Functionality ===
On the PDA, the User will log on with a provided User ID and Vehicle ID.

A vehicle labelled "CAR COLLECT" will be available for those drivers picking up a single car. All other vehicles are trailer plates and will be selectable by registration from the drop-down list provided. If the vehicle has not been checked that day, the PDA will force the user to perform the vehicle checks required. {{Note}} For "CAR COLLECT", these checks will be skipped by the user.

The user will then be provided the Load they have been allocated.

The Job List will display, showing the collection and delivery assigned to the load.

The User selects the Job from the list and is provided contact details and address information, as normal, along with the Job reference.

When the user starts the job, the PDA will display a list of vehicles to be collected. The user clicks a line (there should be one per vehicle registration). Note that the screen labels will be modified to show Vehicle/Reg, etc.

The User will be prompted to enter
* Model/Make (defaulted to that entered on the Job)
* Registration/Chassis (defaulted to that entered on the Job)
* Spare (check box entry)
* Radio (check box entry)
* The user will also be able to enter Defects, if any are found:
** The PDA will allow selection of the Location/Type/Severity required, through drop-down lists. A Button will be provided to add the defect to a list below. A Button will be provided to capture an image associated to the defect, if required.
** A Grid of all entered defects will be shown below, showing the coded entry (i.e. 37 CE-Punctured 1). – Click the grid line to edit the entry above and see the detail. If editing, there will be a button to remove the defect. OK to save again.
* When complete, the User clicks OK, and is returned to the container (vehicle) list.

Completion of collection or delivery is after all container (vehicle) items are confirmed collected or delivered.

There will be a facility for the User to enter notes against the collection or delivery.

The User is then prompted for the customer signature.

Assuming 1 collection and delivery on a load, the User is returned to the job list, with only the delivery portion remaining. The vehicles will have been copied to the Delivery, but not the defect codes.

Click the delivery, and the user will be shown the Delivery with the same job code but the delivery address.

The Delivery process works identically to the Collection process. Vehicle Details and Condition codes will not be pre-entered.

On completion of all jobs, all messages are sent back to the EPOD database. All Images are sent separately. Images will be sent after normal messages, but normal messages may be queued after an image already in the process of being sent. To prevent this, messages will be sent back in smaller chunks, rather than in one large piece.

=== Completion Reports ===

The Admin Products screen will be modified to show the labels of Vehicles/Condition in all places if the new configuration flag 'Vehicle Delivery System' is set. The Job Details screen will display the condition location/type/severity codes entered by the PDA user. Images taken by the PDA users can be seen from here.

The POD/POC reports will show the logo of the company to whom the job belongs (configured within the EPOD system). The POC will not display the data relating to the delivery.

The Terms and Conditions will be added to the second page of the POD/POC.

All POD and POC values can be emailed directly to the customer/client as required.

ERP systems (if any) can be updated at this time.

== Barcelona System ==
This system will be used here only to examine cars in the lot associated to the office.

Cars will be added onto a load and the load assigned to a user.

The users will use the PDA to inspect each car in turn, the device is being used as inspection data entry, and the system used to print off an inspection form (the POC document).

This operation will be under a different site and/or job group, so that it can have its own configuration.

The POC format produced will be different to the normal operation. It will be multi-page document, the second page showing all the defect codes.

== Scope ==
The developments will take place against the latest version of the EPOD system (1.31.X)


= Set-up =
== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server. Additionally, each customer must have an Email address assigned to them for automatic emails to be sent.

== Menu Structure ==
== Data ==
A Site will be generated. This will be agreed in advance, but is expected to be "EULOS". This is generated and maintained through the Site Admin screen.
* PDF Production will be enabled from this screen, by setting the "POD's PDF" check box.
* Notes will be enabled against the Job by setting the "User Notes" check box.
* Collections and Deliveries with the same reference (Job Code) will be linked for updating, by setting the "Link C & D on Job Code" check box.

Job Groups will be set up for the depots using the system, through the Job Group Admin screen. 2 will be set up for the base operation (GEFCO and EULOS). A third will be set up for the Barcelona operation (BARCA).
*The format for collections will be set to "EULOS POC" and deliveries set to "EULOS POD" against each Job Group, from the Job Groups screen. For Barcelona, the format for collections will be set to "EULOS POC 2"
* Collections and Deliveries with the same reference (Job Code) will be linked for updating, by setting the "Link C & D on Job Code" check box.

A Customer record will be set up for each of the Job Groups, with the same ID as the Job Groups. This address of these customer records will be used to identify the Depot Address on the documentation.

Reason Codes will be set up as agreed between any host system and ''CALIDUS'' EPOD. These are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system.

Reason Codes for the Vehicle Defect Location, Type and Severity will be set up as required by the operation.

{{Note}} Type codes that have multiple sub-values will be encoded separately i.e. CD-Cut and CD-Torn will be stored as two separate codes.

= Functional Description =
The following areas will require modification:
* Database Changes
* Import/Export
** Add new fields
** Add Generation of EPL_CONTAINER_ID to Import.
* Admin Changes
** Copy Collection to Delivery button
** Job/Job Details Screens Label Changes
** Job Products to translate Vehicle Damage Codes
** Reason Codes screen
*** Vehicle Damage Codes
*** MAX Length Description field
* PDA Changes
** Collection/Delivery Label Changes
** Vehicle Details Tab
** Copy Vehicle Details to Linked Delivery
** Sequence Image messages After All Normal Messages
* Server Image Changes
* POD/POC Formats

==Database Fields==
Table EPOD_CONTAINER will be modified as follows:
* Three new fields, EPL_CODE_1/2/3, will be added to the table, to allow for several new fields. These fields will be 20 character nvarchar fields.
* EPL_CONTAINER_PACKAGE_CODE will be modified to be up to 20 characters in length.

Table EPOD_SITE will be modified as follows:
* A new "System Type" flag will be added, called EPL_SYSTEM_TYPE, with options "Vehicle Delivery" and "Generic"

Table EPOD_REASON_CODES will be modified as follows:
* EPL_DESCRIPTION will be changed to a MAX length nvarchar field.
* EPL_REASON_CODE will be changed to allow up to 20 characters.

Table EPOD_PROTO will be modified as follows:
* EPL_COMPLETE will be added as a single-character field. It will default to "Y".

==Import/Export Data==
Import and Export of Jobs and Loads will be through the existing standard Web Services.

These will be modified to add the new fields and modify the existing fields as listed in the previous section.

Additionally, the Import processes will be modified to auto-generate the Container ID if it is not provided.

The export process will be modified to export the Containers with the new tags (EPL_CODE1/2/3). A new XSD will be produced as standard, for clients that wish to interface with this.

== Admin Changes ==
=== Job Screen ===
A new button (Copy Collection to Delivery) will be available if the Job Group or Site is configured for Linked Collections and Deliveries. Clicking this button will create a linked Collection or Delivery and copy all the data from the original job.

The user will be given a extra tab on the job screen popup. If a link is present the update function will copy any data below the job level to the linked job. The code to complete this will exist within the DAL.

=== Reason Codes Screen ===
This screen will be modified to allow the user to enter 3 additional different types of codes:
* VLOC - Vehicle Damage Location
* VTYPE - Vehicle Damage Type
* VSEV - Vehicle Damage Severity
These code types should be
* visible (with the human-readable text) within the grid when showing saved codes
* selectable (with the human-readable text) through the filter.
* able to be added against a new code
* able to be changed against an existing code being edited
A Drop-down List should be provided of all the types.

Additionally, this screen should be modified to allow the user to display and enter an unlimited number of characters in the description.

=== Job Details Screen ===
If the new System Type flag is set to "Vehicle Delivery", the function of this screen will change slightly.

* The "New Container" button will become New Vehicle.
* "Containers for Job" will become "Vehicles for Job"
* The "New Loose Product" button will be removed.
* The Containers grid will not display the "Container ID" field
* The "Products" button will become the "Damages" button.
* "Package Code" will become "Vehicle Reg"
* "Description" will become "Model/Make"
* "Products for Container" will become "Damages for Vehicle".
* The "New Product" button will become the "New Damages" button.
* The Products grid will be replaced with a Damages grid showing:
** Damage Code (comprising Location, Type and Severity)
** Damage Description (comprising the description looked up from each Location, Type and Severity in the Damage code above)

On pressing Select against a grid line (or adding a new Container/Vehicle), the following changes will be made to the pop-up:
* The pop-up will be titled "Vehicle Details"
* "Container ID" will be removed and automatically generated
* "Package Code" will become "Vehicle Reg"
* "Description" will become "Model/Make"
* "Long Description" will be removed.
* "Gross Weight" will be removed.
* Three new fields will be added (EPL_CODE_1, EPL_CODE_2 and EPL_CODE_3) only when this flag is set. The first two shall be labelled as Spare and Radio. Both will be Drop-down lists, allowing the values "Yes" and "No" only (actual values "Y" and "N" stored). The last shall be labelled CMR No.

In addition, any pop-up messages or validation messages will change to reflect the following:
* A "Container" is a "Vehicle"
* "Description" is "Model/Make"
* "Product" is "Damage"

When saving these details on a Collection job, if the system is set up for Linked Collections and Deliveries, changes to the Vehicles (additions and edits) should be reflected against any Delivery job with the same Load Number as the Collection (even if this is blank) with the same Job Code (non-blank) at a status that is not Complete or Cancelled. If multiples are found, only the first need be updated.

== PDA Changes ==
If the new "System Type" flag is set to "Vehicle Delivery", the function of the Collection and Delivery screens will change.
* The "Containers" tab will be labelled as "Vehicles".
* A new tab will be created, labelled as "Details".
* The scanned item will be EPL_CONTAINER_PACKAGE_CODE rather than EPL_CONTAINER_ID.

When a vehicle has been entered/scanned and marked as collected or delivered (through the appropriate button), the system will move on to the new Details tab.

The User will be prompted to enter:
* Model/Make (defaulted to EPL_CONTAINER_PACKAGE_DESC)
* Registration/Chassis (defaulted to EPL_CONTAINER_PACKAGE_CODE)
* CMR # (defaulted to EPL_CODE3)
* Spare (check box entry of EPL_CODE1)
* Radio (check box entry of EPL_CODE2)
* The user will also be able to enter Defects, if any are found, using the button provided:
** The PDA will allow selection of the Location/Type/Severity required, through a pop-up screen, selecting values from drop-down lists. A Button will be provided to add the defect to a list below. A Button will be provided to capture an image associated to the defect, if required.
** A Grid of all entered defects will be shown below, showing the coded entry (i.e. 37 CE-Punctured 1). The user will be able to long-hold against a grid-line to delete or edit the entry.

The suggested screen layouts are as follows:
* The Vehicle Details screen
[[file:299880-PDA-Details1.PNG]]
* The pop-up Damage Entry screen
[[file:299880-PDA-Details2.PNG]]
* The pop-up menu, from long-pressing the grid.
[[file:299880-PDA-Details3.PNG]]

Each defect will be stored as an entry against EPOD_PRODUCT, in the EPL_PRODUCT_CODE field.
Any images taken against a defect will be saved against the EPOD_PRODUCT record.

If no codes are entered when OK is pressed, a popup confirmation will be displayed ("No Damage?").

Completion of collection or delivery is after all container (vehicle) items are confirmed collected or delivered.

There will be a facility for the User to enter notes against the collection or delivery, through the standard Notes tab.

When complete, the User will click OK and is returned to the container (vehicle) list. The messages will be sent back to the EPOD server for confirmation.

If the Load has the same reference being delivered later, both the PDA and the Server will update the Delivery associated to the Collection with the Vehicle information (i.e. the Container records) but not the Damages information (i.e. the Products).

== Ad Hoc Vehicle (Container) Collection ==
As part of the collection a Ad Hoc collection at container level will be required. This will function in a similar way to existing product level ad hoc collection, with the PDA creating the records.
As part of the vehicle system configuration a addtional item on the context menu will be added to the containers grid labelled as new.
Clicking this will create a new container and enter the user in the vehicle damages screen, prompting to populate the Reg, desc, cmr. From here they can add any damages on this vehicle.

Clicking confirm will create the container. This will then be processed the same as all other containers.

=== Sequence Image messages After All Normal Messages ===
The PDA Sending process will be modified to ensure that all images are sequenced for sending after any other pending messages, via a sort order on the pending message. To achieve this, a Priority and auto-generating ID will be added to the index on the Pending table, sorting in Ascending sequence. All Image messages will be written with priority -1. All other messages will be written with priority 1.

When writing Images, the Image Size parameter will be checked. If the Image exceeds the Image Size parameter, the message will be broken down into multiple messages, each message payload being equal to the Image Size parameter, with the remainder of the image being sent in the final message.

The Image Size parameter will be a constant at this time, set to 50Kb.

The Image message packet will be modified to include both the Image Packet number and the total number of packets to be received as new tags, as follows:

<PHOTO_REQUEST ID="0" SITE="LSM" USER="ADM" PASSWORD="TEST">
<EPL_SITE_ID>LSM</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID></EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE></EPL_PRODUCT_CODE>
<EPL_SEQUENCE></EPL_SEQUENCE>
<EPL_PHOTO></EPL_PHOTO>
<EPL_DESCRIPTION></EPL_DESCRIPTION>
<EPL_PHOTO_TYPE>J|C|P</EPL_PHOTO_TYPE>
<EPL_PACKET></EPL_PACKET>
<EPL_PACKET_TOTAL></EPL_PACKETTOTAL>
</PHOTO_REQUEST>

== Server Image Changes ==
Image messages may now be received in multiple packets.

If the new Packet tags are not found, the message will be received as now.

If the new Packet attributes are found and are both set to "1", the message will be received as now.

In all other cases, the image data will be created with the first message as follows:
* An image will be found associated to the parameters on the message (Site, job, Container, Product, Sequence and Photo Type).
* If an image is found it will be retrieved. If an image record is not found, one will be created with place-holder tags for the data, based on the total number of packets. So, if there are 3 packets in total, the image record will be initially created as "<PACKET>1</PACKET><PACKET>2</PACKET><PACKET>3</PACKET>".
* The packet identified in the message will then be substituted with the image packet (i.e. EPL_PHOTO). So, if the first message is for packet 2, the image data will become "<PACKET>1</PACKET>lsdkl897jhdfgkl(87jkhsf98*(&(*&***<PACKET>3</PACKET>"
* If all packets have not yet been received (i.e. the message still includes <PACKET> tags), a new flag against the Photo (EPL_COMPLETE) will be set to "N" show that the Photo has not been completely received. If there are no packets awaiting receipt, this flag will be set to "Y".

The DAL for Photos will be modified to retrieve only Photos that are Complete. An overloaded version of this DAL method will be created to allow the retrieval of incomplete Photos (as used in the procedure above).

== POD/POC Formats ==

The POD/POC reports will show the logo of the company to whom the job belongs (configured within the EPOD system). The POC will not display the data relating to the delivery.

=== Format "EULOS POD" ===
* Collect From: Name and Address information from the Customer or Job Address associated to the Collection Job of that Job Code. The Date is the Date the Collection job was completed.
* Deliver To: Name and Address information from the Customer or Job Address associated to the Delivery Job of that Job Code. The Date is the Date the Delivery job was completed.
* Model/Make: EPL_CONTAINER_PACKAGE_DESC of EPOD_CONTAINER
* Registration/Chassis: EPL_CONTAINER_PACKAGE_CODE of EPOD_CONTAINER
* Spare: EPL_CODE1 of EPOD_CONTAINER
* Radio: EPL_CODE2 of EPOD_CONTAINER
* Collection Condition: This is the consolidated values of EPL_PRODUCT_CODE of EPOD_PRODUCT, comma delimited, from the Collection job of this Job Code.
* Delivery Condition: This is the consolidated values of EPL_PRODUCT_CODE of EPOD_PRODUCT, comma delimited, from the Delivery job of this Job Code.
* Driver Name: EPL_NAME of EPOD_USER, of the PDA User who completed the Delivery job (EPL_USER_ID of EPL_JOB)
* Truck Registration: EPL_VEHICLE_REG of EPOD_VEHICLE, of the Vehicle driven by the user who completed the Delivery job (EPL_VEHICLE_ID of EPOD_JOB).
* Reference Number: EPL_CUST_REF of the EPOD_JOB record for the Delivery Job.
* Collection Name: EPL_SIGNATORY of the EPOD_JOB record for the Collection Job.
* Collection Signature: EPL_SIGNATURE of the EPOD_JOB record for the Collection Job.
* Delivery Name: EPL_SIGNATORY of the EPOD_JOB record for the Delivery Job.
* Delivery Signature: EPL_SIGNATURE of the EPOD_JOB record for the Delivery Job.

A second page will be produced showing all the terms and conditions.

=== Format "EULOS POC" ===
This is the same as the POD document above, but with the following changes:
* The Deliver To box is not displayed.
* The Delivery Collection column is not displayed.
* The Delivery Name/Signature box is not displayed.
* Driver Name: EPL_NAME of EPOD_USER, of the PDA User who completed the Collectionjob (EPL_USER_ID of EPL_JOB)
* Truck Registration: EPL_VEHICLE_REG of EPOD_VEHICLE, of the Vehicle driven by the user who completed the Collection job (EPL_VEHICLE_ID of EPOD_JOB).
* Reference Number: EPL_CUST_REF of the EPOD_JOB record for the Collection Job.

=== Format "EULOS POC 2" ===
This format will print one page per container, rather than one page per job.

* Model: EPL_CONTAINER_PACKAGE_DESC of EPOD_CONTAINER
* Load No: EPL_JOB_CODE of EPOD_JOB
* REF No: EPL_CUST_REF of EPOD_JOB
* Chassis/Reg No: EPL_CONTAINER_PACKAGE_CODE of EPOD_CONTAINER
* CMR No: EPL_CODE3 of EPOD_CONTAINER
* Purchase Order No: EPL_SO_NUMBER of EPOD_JOB
* Collection Point Area, Damage and Severity Codes: This is the consolidated values of EPL_PRODUCT_CODE of EPOD_PRODUCT, comma delimited, from the Collection job of this Job Code.
* Truck No/Ship: EPL_VEHICLE_REG of EPOD_VEHICLE, of the Vehicle driven by the user who completed the Collection job (EPL_VEHICLE_ID of EPOD_JOB).
* Driver Name: EPL_NAME of EPOD_USER, of the PDA User who completed the Collection job (EPL_USER_ID of EPL_JOB)
* Driver Signature: EPL_SIGNATURE of the EPOD_JOB record for the Collection Job.
* Date: The Date is the Date the Collection job was completed (EPL_ACTUAL_END_DATE of EPOD_JOB).

{{note}} All other parts of the format not mentioned above will be printed but are not filled in with any data compiled from the job completion.

{{warning}} The diagram of the car will be supplied by the client.

A second page will be produced showing all the damage location, type and severity codes.


= Appendix A: POD Formats =
[[File:299880-DeliveryNote.jpg|700px|border]]

[[File:299880-BarcaNote.jpg|700px|border]]



= Appendix B: Test Plan =
{{TestPlan_Header
|Title=EuLoS EPOD Test Plan
|Log=299880
|Description=Test the functionality required by the EuLoS operation
|MenuAccess=Various
|Prerequisites=Ensure that site EULOS is created, with Users ADM and PDA pre-created.
|Objective=To ensure that the Import, Admin, PDA and Export functionality of the ''CALIDUS'' EPOD system operate as expected
}}{{ #vardefine: Cycle | 0 }}{{ #vardefine: SubCycle | 0 }}

{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Admin
|Notes=
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Log on as an admin user on Site EULOS
|Result=The system should start
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter the Site screen, edit the details and Upload a Site Image (JPG). Save.
|Result=The Site log should be uploaded.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Ensure that Delivery and Collection completion document formats can be set to Eulos POC, Eulos POC2 and Eulos POD and Save.
|Result=The option is available from the drop-down boxes. Data is saved as expected.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Ensure the system can be configured to "Vehicle Delivery" or "Generic". Set to "Vehicle Delivery" and Save.
|Result=The options are available a check boxes on the Admin tab.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter the Job Group screen and create "EULOS"
|Result=Job group created
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Edit job group and assign a logo and save.
|Result=Logo updated
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Ensure that Delivery and Collection completion document formats can be set to Eulos POC, Eulos POC2 and Eulos POD and Save.
|Result=The option is available from the drop-down boxes. Data is saved as expected.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Configure the remaining Job Groups (GEFCO and BARCA) are configured with the correct POC and POD notes and logos and save.
|Result=Configuration saved.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Choose Reason Codes from the menu. Search and check that the Reason Types can be set to "Vehicle Location", "Vehicle Type" and "Vehicle Severity" from the drop-down list.
|Result=As expected
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Select all of the above and check that the reasons exist.
|Result=All reasons required should be pre-created and available to find in this screen.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter a new reason code for all of the types listed above and save.
|Result=The new Reason Codes should be saved. They should be findable in the grid. The Reason Types should be translated to human-readable text (i.e. "Vehicle Location" rather than "VLOC").
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Edit the description of all the new Reason Codes
|Result=The pop-up should allow this. The Reason Types should be translated to human-readable text (i.e. "Vehicle Location" rather than "VLOC"). The changes should be saved.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Delete all the new reason codes.
|Result=The should all be deleted.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Create a new load, and drill-down to create a new Job. Create a Collection. Drill-down to Details. |Result=The Job Details screen should display the new Vehicles screen, showing all the label, grid and button changes as described in the specification.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Click 'New Vehicle'.
|Result=The popup should display, showing only the fields required, with the new labels as specified.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter the details of the vehicle required.
|Result=The popup should force entry on the Registration and Make/Model. All other fields are optional.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Save the new Vehicle
|Result=The grid should re-display, showing the vehicle entered.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Add multiple vehicles
|Result=The results should be displayed in the grid.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Exit back to the Job screen.
|Result=The Job screen should allow the user to create a linked Delivery, by pressing a new button.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter all required details and Save.
|Result=A new Delivery Job should be created.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Find the collection Job again, and delete a Vehicle, add a new Vehicle and change an existing one.
|Result=The Delivery associated should be updated with the new details.
}}
{{TestPlan_CycleFooter}}


{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Import
|Notes=A test XML file exists for the creation of jobs as specified below.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Import loads containing: a 12-vehicle linked collection and delivery for Job Group GEFCO; a 1-vehicle linked collection and delivery for Job Group EULOS; a 6-part collection for Job Group Barca. All should have the new import element EPL_CODE3, populated with a CMR number.
|Result=The Loads and Jobs should be created. The Customers should be created. All new required fields should be populated.
}}
{{TestPlan_CycleFooter}}


{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=PDA Functionality
|Notes=Ensure the following flags are enabled against the Site and/or Job Group:
* Linked Collections and Deliveries
* Auto-Email
* Container-only Delivery
Ensure the Site flag "System Type" is set to "Vehicle Delivery".
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Start a Load on the PDA and start a Collection Job.
|Result=The Collection should show "Vehicles" and "Details" tabs. A list of vehicles should be shown, along with a Registration entry button.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter/Scan or click a Registration or Chassis that does not exist, then click '''Collected'''.
|Result=The PDA should inform you that the Vehicle does not exist.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter/Scan or click a Registration or Chassis that exists, then click '''Collected'''.
|Result=The PDA should display the ''Details'' tab for that vehicle. The Registration, Make and CMR number should be pre-populated.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Click Apply
|Result=The PDA should issue a confirmation message saying "No Damage?". Cancelling this will return to the Details screen, whilst confirming will return you to the Vehicles list, with the vehicle just completed removed from the list.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Enter another valid Reg and click '''Collected'''. On the displayed ''Details'' tab, click the Damages button.
|Result=The Damages popup should be displayed.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Click '''Save'''
|Result=The popup should not allow saving without choosing at least a Location and Type entry.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Select some Location, Type and Severity codes and click '''Save'''.
|Result=The PDA should display the Details screen, with the Damage code entered shown on the grid.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Click the '''Damages''' button again and enter another (different) damages code and save. Do this at least 3 times.
|Result=The grid should scroll to show multiple damage codes.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Click the '''Damages''' button and enter another damages code. Click '''Image'''.
|Result=The Image dialogue should be shown to capture an image.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Capture an image, then save the damage code.
|Result=The PDA should display all damage codes.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Long-hold on any of the Damage codes in the grid (not the last).
|Result=A popup menu should show, showing options to ''Delete'' and ''Edit''.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Choose ''Delete''.
|Result=A confirmation dialogue should be displayed. If cancelled, the damage code should not be removed from the grid. If confirmed, the Damage code should be deleted and removed from the grid.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Long-hold any of the Damage codes except the last and choose ''Edit'' from the popup menu.
|Result=The Damages popup should be shown, with the Damage codes pre-set to those on the grid entry.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Change the damage code and click '''Save'''
|Result=The changed Damage code should be reflected in the Grid.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Long-hold any of the Damage codes not yet selected except the last and choose ''Edit'' from the popup menu. Click the '''Image''' button and capture an image for the line. Click '''Save'''.
|Result=The Damage code should be reflected in the Grid.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Click '''Apply'''
|Result=The PDA should return you to the Vehicles list, with the vehicle just completed removed from the list.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Complete all of the other vehicles.
|Result=The job is completed and the PDA displays the Job List.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Check the job on the server, using the Job screen.
|Result=The job should be updated to completed status, with all required information entered.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Check the Vehicles
|Result=All vehicles should be completed. Once vehicle should have changed registration, as entered on the PDA.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Check the vehicle details.
|Result=All reason codes should be saved. All images should be present.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Check the delivery job associated to the Job Code against the Collection on this load.
|Result=The Vehicles should match the collection job. No damage codes should be present.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Start the associated delivery on the PDA.
|Result=The Vehicles shown should be the vehicles entered on the PDA only.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Repeat tests 3-20 above for the delivery.
|Result=As expected.
}}
{{TestPlan_CycleFooter}}


{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Server (After Update)
|Notes=Ensure that the Auto-Export process is scheduled to run and that Auto-Email is enabled on the Site and/or Job Group.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Complete jobs on the PDA. Force-run the Auto-export process.
|Result=The Auto-export process should send PDF versions of the POD documents customers' Email addresses.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Cancel Jobs on the PDA. Force-run the Auto-export process.
|Result=No emails should be sent.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Check that the Correct format of POD and POC document is produced.
|Result=The correct format is produced, based on the Job Group and Job Type, with all the correct data in the correct place.
}}
{{TestPlan_CycleFooter}}


{{TestPlan_CycleHeader
|Cycle={{ #vardefineecho: Cycle | {{ #expr: {{ #var: Cycle }} + 1 }} }}{{ #vardefine: SubCycle | {{ #var: Cycle }} }}
|Title=Admin (Job Functionality)
|Notes=Ensure that several job types have been completed for each Job Group, with damage codes.
Ensure the Site flag "System Type" is set to "Vehicle Delivery".
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Find a completed Job, either through the Load or Jobs screens.
|Result=The vehicles are displayed.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Select a vehicle and choose to display the damages.
|Result=The damages should be displayed in a grid.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Select a vehicle.
|Result=A popup should show all the vehicle details. All fields should appear and be labelled as specified.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Select a Damage line
|Result=A popup should show all the damage details. All fields should appear and be labelled as specified.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=Show an image against a damage line.
|Result=The image should be displayed.
}}
{{TestPlan_Test
|Test={{ #vardefineecho: SubCycle | {{ #expr: {{ #var: SubCycle }} + 0.01 }} }}
|Action=From the Jobs screen, choose to display the completion report for the job for each type (Collection and Delivery), for each Job Group (GEFCO, EULOS and BARCA).
|Result=The correct report (POD or POC) should be displayed, depending on the Job type and the Job Group configuration.
}}
{{TestPlan_CycleFooter}}


{{Doc_Appendix
|Appendix=C
|Estimate=N
|Glossary=EPOD
|Ref1=UG 291094 EPOD Admin User Guide
|RefV1=2.0
|RefDate1=4/4/2012
|Ref2=UG 291097 EPOD Client User Guide
|RefV2=2.0
|RefDate2=4/4/2012
|REQ=0
|EST=0
|FS=2
|TS=0
|DEV=16
|ST=5
|IMP=0
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=N
|Rev1={{warning}} Client Rep
|Rev1Title=Client Representative
|Rev2=Matt Turner
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 291227 PROD Supimix Web Client

2012-04-18T14:27:38Z

Milesl: /* User Access */

<div class="noprint">
{{#vardefine:Client|PROD}}
{{#vardefine:ClientName|OBS}}
{{#vardefine:System|''CALIDUS'' Supimix}}
{{#vardefine:Doc_Title|Supimix Web Client}}
{{#vardefine:Version|0.1}}
{{#vardefine:Date|3rd Jan 2012}}
{{#vardefine:Reference|291227}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==
The Client (being potentially all OBS clients), DHL will need access to the Supimix system allowing for easy logging of TIDs and potentially other calls.

They will require access to view log activity only.

== Solution Overview ==
A ASP .NET solution has been developed. This has gone through several revisions, and now remains at v0.1.

== Scope ==



= Set-up =

== Pre-requisites ==
*IIS
*.NET Framework 4.0
*Informix SDK installer

== Menu Structure ==

== Data ==
This runs from the Informix database hosted on Steel.

== System Config ==

The host machine requires the following configurations:
* Installation of Informix Client SDK version 3.70 xC1
* Network access to steel
* Services adding for the Informix TCP/IP services

sqlexec 1528/tcp ---No Longer Needed
informix1 1529/tcp #Informix server

* IIS
* .NET 4



= Functional Description =

== System Functionality ==

The system provides the following functionality:
*User access restrictions
** OBS users can access everything and can log/update calls for all clients.
** Client users cannot update calls and can only view log relating to their client.
*Call logging
*View and update call details
*Attach files relating to the log
*Email based on events (status updated, details updated ect)

== User Access ==

The Web Client provides user access control, limiting users access to Supimix's content based on the users account settings.

The users account must exist both as a member of staff within supimix with a client flag set and a record within the Web Support table which holds their access details and level. Internal users will require this configuration as well.

Access will initially be given to Julie Scott, Julie Ann Taylor, Peter Greer and myself for testing purposes.

Once released to production, Peter Greer will specify the users to be given access.

Access from the application to the Steel machine and Database will be setup using a specified netowrk user account.

To add users to the system:
*Create a new staff record
*Run the following sql against the Steel DB, replacing all fields marked with *, with the relevant values.

"INSERT INTO websupport_users (wu_client, wu_project, wu_site, wu_product, wu_user, wu_pass, wu_name, wu_contact)
VALUES ('*client*','*project*','*site*','*product*','*user*','*password*','*name*','*contact')";

Note: Only the client field is used by the system at this time.

== Testing ==

Internal testing has been completed using the SEC client within supimix.

Testing for the Client aspects of the system will be compelted externally by Peter Greer, this will include UAC testing.

First Call testing for the purpose of internal use (helpdesk) will be preformed by Julie Ann Tayor.

== Test to Production ==

Once the current version of the system has been approved both internally (no bugs found during external texting) and externally (UAC), the system will need to be migrated from the testing environment to a production machine with external web access, ideally hosted under a OBS domain.

== Migration of Other Web Systems ==

Functionality provided in other web system will need to be identified and migrated. During this phase any additional functionality required will need to be assessed.

== Basic requirements for WEB Supimix for ease of logging for Firstcall (OBS Helpdesk) - JAT ==

Facility to;
*Add a new incident
*Update an incident
*View an incident

=== Ability to log ‘new incidents’ ===

*Populate default values where possible dependent on client code entered ie support queue and product code.
*Populate default values dependent on site code entered ie project, job codes.
*To provide drop down list for easy entry (using current supimix maintained tables).
*To have the facility to send automatic external emails for new call confirmations, with date/time stamped records written to supimix as proof. Using standard text template from current supimix version. Auto close any prompt windows on email delivery, ensure status text is also displayed in header section ‘Call confirmation has been sent’
*To have the facility to send automatic chase emails to the user id currently assigned the call, with date/time stamped records written to supimix as proof. Using standard text template from current supimix version. Auto close any prompt windows on email delivery, ensure status text is also displayed in header section ‘Chase has been sent’
*To have the facility to write records to supimix on ‘passing a call’ out of hours. Date/time stamped when the call was handed over to and accepted by the support analyst on call. Auto close any prompt windows on update, ensure status text is also displayed in header section ‘Passed to oncall’
*On completion of logging a new call, display summarised call information for ease of entry into forwarding email subject (for copy&paste) displayed as ‘client code:priority:site:log number:reference’ eg EXL:4:COV:294250:EARS00031823587
*New call Alert emails must be automatically sent to OBS support queue once logged triggered by default support queue in point 1 above.
*Audit History record is required for new call status Logged and Confirmed – the audit record written is to include date, time, who, type.
*Call details should be displayed in record date/time order showing call history from earliest entry (call logging) to latest entry (call closure).
*Ability to cancel a call half way through logging.
*Ensure all display text is correctly formatted and justified.
*Ensure OBS logo and OBS Helpdesk contact details are displayed in each of the screens.

===Ability to ‘update’ incidents===

*Update action should display the same screen familiar with during ‘new call entry’
*Record/Field updates should prompt for details (narrative) to be added by the user, thus providing a full history of the call.
*Updates of status, substatus, assigned, priority, call type must all have audit history records written along with ‘passed to oncall’ and ‘chase’ actions – this audit record should include date, time, who, type, old value, new value. NB: Important for month end statistical reporting.
*Also requires call confirmation, chase and passed to on call facility.

===Ability to ‘view’ incidents===

*Introduce a new ‘search’ screen to allow the user to search for an incident uniquely by OBS Log number, or via reference number (with wildcard search) or client/date range.
*On selection, a list of ‘matching’ records should be displayed to the user, allowing sort action on each field value displayed.
*OBS log number should be manually selected and user taken to ‘Update Calls’ screen allowing any updates if required.

===Important points to highlight===

*Check session inactivity period settings.
*Multiple logins should be enabled for the same user account.
*Emails should be sent from the email account of the user logged on
*Ensure search boxes are not case sensitive and allow the use of * as a wildcard value.
*Date and time values should be UK formatted DD/MM/YYYY, HH:MM:SS
*Any code values should also have full text displayed (eg status 0 means nothing without the text ‘LOGGED’).
*Ensure screens are ID’d to assist with any support assistance from OBS.

{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=WCS
|Ref1=Reference1
|RefV1=0.1
|RefDate1=01/03/2012
|REQ=0
|EST=0
|FS=0
|TS=0
|DEV=0
|ST=0
|IMP=0
|Client={{#var:Client}}
|Year=2012
|FSEST=Y
|Rev1=Julie Scott
|Rev1Title=Project Manager
}}</div>
[[Category:{{#var:Client}} FS]]

FS 291227 PROD Supimix Web Client

2012-04-18T14:27:27Z

Milesl: /* User Access */

<div class="noprint">
{{#vardefine:Client|PROD}}
{{#vardefine:ClientName|OBS}}
{{#vardefine:System|''CALIDUS'' Supimix}}
{{#vardefine:Doc_Title|Supimix Web Client}}
{{#vardefine:Version|0.1}}
{{#vardefine:Date|3rd Jan 2012}}
{{#vardefine:Reference|291227}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==
The Client (being potentially all OBS clients), DHL will need access to the Supimix system allowing for easy logging of TIDs and potentially other calls.

They will require access to view log activity only.

== Solution Overview ==
A ASP .NET solution has been developed. This has gone through several revisions, and now remains at v0.1.

== Scope ==



= Set-up =

== Pre-requisites ==
*IIS
*.NET Framework 4.0
*Informix SDK installer

== Menu Structure ==

== Data ==
This runs from the Informix database hosted on Steel.

== System Config ==

The host machine requires the following configurations:
* Installation of Informix Client SDK version 3.70 xC1
* Network access to steel
* Services adding for the Informix TCP/IP services

sqlexec 1528/tcp ---No Longer Needed
informix1 1529/tcp #Informix server

* IIS
* .NET 4



= Functional Description =

== System Functionality ==

The system provides the following functionality:
*User access restrictions
** OBS users can access everything and can log/update calls for all clients.
** Client users cannot update calls and can only view log relating to their client.
*Call logging
*View and update call details
*Attach files relating to the log
*Email based on events (status updated, details updated ect)

== User Access ==

The Web Client provides user access control, limiting users access to Supimix's content based on the users account settings.

The users account must exist both as a member of staff within supimix with a client flag set and a record within the Web Support table which holds their access details and level. Internal users will require this configuration as well.

Access will initially be given to Julie Scott, Julie Ann Taylor, Peter Greer and myself for testing purposes.

Once released to production, Peter Greer will specify the users to be given access.

Access from the application to the Steel machine and Database will be setup using a specified netowrk user account.

To add users to the system:
*Create a new staff record
*Run the following sql against the Steel DB, replacing all fields marked with *, with the relevant values.

"INSERT INTO websupport_users (wu_client, wu_project, wu_site, wu_product, wu_user, wu_pass, wu_name, wu_contact) " +
VALUES ('*client*','*project*','*site*','*product*','*user*','*password*','*name*','*contact')";

Note: Only the client field is used by the system at this time.

== Testing ==

Internal testing has been completed using the SEC client within supimix.

Testing for the Client aspects of the system will be compelted externally by Peter Greer, this will include UAC testing.

First Call testing for the purpose of internal use (helpdesk) will be preformed by Julie Ann Tayor.

== Test to Production ==

Once the current version of the system has been approved both internally (no bugs found during external texting) and externally (UAC), the system will need to be migrated from the testing environment to a production machine with external web access, ideally hosted under a OBS domain.

== Migration of Other Web Systems ==

Functionality provided in other web system will need to be identified and migrated. During this phase any additional functionality required will need to be assessed.

== Basic requirements for WEB Supimix for ease of logging for Firstcall (OBS Helpdesk) - JAT ==

Facility to;
*Add a new incident
*Update an incident
*View an incident

=== Ability to log ‘new incidents’ ===

*Populate default values where possible dependent on client code entered ie support queue and product code.
*Populate default values dependent on site code entered ie project, job codes.
*To provide drop down list for easy entry (using current supimix maintained tables).
*To have the facility to send automatic external emails for new call confirmations, with date/time stamped records written to supimix as proof. Using standard text template from current supimix version. Auto close any prompt windows on email delivery, ensure status text is also displayed in header section ‘Call confirmation has been sent’
*To have the facility to send automatic chase emails to the user id currently assigned the call, with date/time stamped records written to supimix as proof. Using standard text template from current supimix version. Auto close any prompt windows on email delivery, ensure status text is also displayed in header section ‘Chase has been sent’
*To have the facility to write records to supimix on ‘passing a call’ out of hours. Date/time stamped when the call was handed over to and accepted by the support analyst on call. Auto close any prompt windows on update, ensure status text is also displayed in header section ‘Passed to oncall’
*On completion of logging a new call, display summarised call information for ease of entry into forwarding email subject (for copy&paste) displayed as ‘client code:priority:site:log number:reference’ eg EXL:4:COV:294250:EARS00031823587
*New call Alert emails must be automatically sent to OBS support queue once logged triggered by default support queue in point 1 above.
*Audit History record is required for new call status Logged and Confirmed – the audit record written is to include date, time, who, type.
*Call details should be displayed in record date/time order showing call history from earliest entry (call logging) to latest entry (call closure).
*Ability to cancel a call half way through logging.
*Ensure all display text is correctly formatted and justified.
*Ensure OBS logo and OBS Helpdesk contact details are displayed in each of the screens.

===Ability to ‘update’ incidents===

*Update action should display the same screen familiar with during ‘new call entry’
*Record/Field updates should prompt for details (narrative) to be added by the user, thus providing a full history of the call.
*Updates of status, substatus, assigned, priority, call type must all have audit history records written along with ‘passed to oncall’ and ‘chase’ actions – this audit record should include date, time, who, type, old value, new value. NB: Important for month end statistical reporting.
*Also requires call confirmation, chase and passed to on call facility.

===Ability to ‘view’ incidents===

*Introduce a new ‘search’ screen to allow the user to search for an incident uniquely by OBS Log number, or via reference number (with wildcard search) or client/date range.
*On selection, a list of ‘matching’ records should be displayed to the user, allowing sort action on each field value displayed.
*OBS log number should be manually selected and user taken to ‘Update Calls’ screen allowing any updates if required.

===Important points to highlight===

*Check session inactivity period settings.
*Multiple logins should be enabled for the same user account.
*Emails should be sent from the email account of the user logged on
*Ensure search boxes are not case sensitive and allow the use of * as a wildcard value.
*Date and time values should be UK formatted DD/MM/YYYY, HH:MM:SS
*Any code values should also have full text displayed (eg status 0 means nothing without the text ‘LOGGED’).
*Ensure screens are ID’d to assist with any support assistance from OBS.

{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=WCS
|Ref1=Reference1
|RefV1=0.1
|RefDate1=01/03/2012
|REQ=0
|EST=0
|FS=0
|TS=0
|DEV=0
|ST=0
|IMP=0
|Client={{#var:Client}}
|Year=2012
|FSEST=Y
|Rev1=Julie Scott
|Rev1Title=Project Manager
}}</div>
[[Category:{{#var:Client}} FS]]

FS 297001 Prolog EPOD Modifications

2012-03-07T11:24:16Z

Milesl: v0.5 Version updated

<div class="noprint">
{{#vardefine:Client|PROL}}
{{#vardefine:ClientName|PROLOG}}
{{#vardefine:System|''CALIDUS'' EPOD}}
{{#vardefine:Doc_Title|Prolog EPOD Modifications}}
{{#vardefine:Version|0.5}}
{{#vardefine:Date|7st March 2012}}
{{#vardefine:Reference|297001}}
{{#vardefine:Year|2012}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}


<div class="noprint">
= Functional Overview =
There will be 35 PDA users and 5 Admin users hosted by the Prolog system.

There are expected to be 35 loads per day.

There are expected to be approximately 10 jobs per load.

There are expected to be up to 52 containers/products per load.

There will be 3 job groups, allocated to each Depot.

== Client Requirement ==
The client requires an implementation of the {{#var:System}} system, following the functionality as described below.

== Solution Overview ==
===Import Data===
Import and Export of Jobs and Loads will be through the existing standard Web Services.

The Job Group field will identify the depot from which the Job originates.

An Owner field added to the Job import, to allow the client system to specify Prolog's Client (e.g. Britvic).

The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).

Delivery jobs will be sent with one container record and multiple product records. The container record will be provided with a description of the required pallets and weight (for example, "2 Pallets / 174.0 Kg"). All products associated to the job will be added to this container, detailing the product code, description and quantity.

Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.

Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job.

The Load import includes the Driver assigned to the Load.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.

===PDA Log-on===
Each Driver will have a PDA with the ''CALIDUS'' EPOD system installed and configured on it. The user will log in with a User ID and password provided to them, and a Vehicle ID, chosen from a list.

===Vehicle Checks===
If the vehicle being used has not been checked recently, the unit will direct the user to complete the Vehicle Checks. The data entry and checks here are configurable within the Admin system. The checks required will be sent to OBS so that they can configure the checks required at this stage.

===Metrics===
Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point.

{{note}} The user will also be prompted to enter the mileage once all jobs on the load are complete.

The user will then be shown a list all the jobs on the load that has been assigned to the user. The jobs are displayed in the order in which they should be completed. However, the jobs can be completed in any sequence by clicking the line of the job required to to be completed first and then clicking the '''OK''' button. The user will then be taken to the Job Details page, which displays the full details of the job being undertaken.
The screen has several Tabs, each showing:
* The Job Type (Collection, Delivery, Service)
* The customer details (Customer Code, Name, Address and Postcode)
* The contact information (Contact name and number)
* The Instructions for the job
From these tabs, the user can:
* Call the customer by clicking on the '''Call''' button.
* Navigate to the customer's address by clicking on the '''Navigate''' button.

Again, here the user can choose which job to complete by using the supplied left and right buttons or start a job with the '''OK''' button, when either a Collection or Delivery process will begin.

{{Note}} The job can be cancelled at this stage by clicking the '''Cancel''' button. The unit will take to the user to an Exception screen and prompt them to enter a reason code explaining why this job was cancelled. See the Exception process for more information.

===Collection Process===
For collections, the user will be shown instructions for the job, with a list of all required products and quantities to collect.

If the collection is successful with no changes, the user will click the '''OK''' button to confirm this and be taken to the Confirmation process.

If nothing can be collected, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the collection, the user will click the '''Notes''' tab and enter details on the adjustment to the collection. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

===Delivery Process===
Deliveries (from Depots to Customers) will be configured to ensure that the PDA unit only requires the user to confirm containers rather than individual products, as follows:

The user will be shown a list of containers only. The description on here will display the number of pallets.

By long-clicking on the container, the user can view a list of all the products in this container.

If all has been delivered successfully, the user will click the '''Collected''' button and be taken to the Confirmation process.

If nothing can be delivered, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the delivery, the user will click the '''Notes''' tab and enter details on the adjustment to the delivery. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

Deliveries (from a supplier to a customer direct) will not follow this process, as no container or product details will have been provided on the job. The Notes information from the collection will have been automatically updated onto the associated delivery, so the user will be able to see what was collected. The user will be able to confirm the delivery with the '''OK''' button, cancel the delivery through the '''Cancel''' button and amend the notes as above.

===Exception Process===
This screen will be displayed if the user is cancelling an entire job, as described in the previous sections.

When cancelling a Job, the user is asked to enter a reason for the cancellation or shortage. These reasons are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system.

If necessary, the user can capture an image to support this reason, by clicking the '''Image''' button. The user can then use the device's camera to capture an image. When complete, the user will exit and will be allowed to view the captured image and add a note to the image to explain.

Once the exception is complete, the user will be returned to the job list, to complete the next job.

===Confirmation Process===
The expected configuration for both Collections and Deliveries will be that the user will be prompted to sign for the job, then the customer will be asked to sign for this also.

The Name defaults to the customer contact name (if present on the job) and allows the user to change this.

Once completed, The user will be returned to the Job Menu to pick up the next task.

The completed job will be transferred back to the main ''CALIDUS'' EPOD system with all the details, signatures and photos.

Once all jobs are completed on that load, the user will be prompted to enter the mileage of the vehicle when they have returned to base. This and the starting mileage will be sent back to the main ''CALIDUS'' EPOD system.

===Export Data===
When data is sent back to the server for jobs completed or cancelled, the server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All jobs completed in this manner will be forwarded on to a configured Web Service within the client host system, in the standard ''CALIDUS'' EPOD format.

When metric data is sent back for the Load, this will be stored in the ''CALIDUS'' EPOD database. The server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All loads completed in this manner will be forwarded on to a configured Web Service within the client host system, in the new format created for this purpose.

===Completion Documents (POD/POC)===
This automated process will also create the Completion documents in PDF format and email them to a central email address, configured against the site in ''CALIDUS'' EPOD.

A document will be generated for every collection and delivery completed (i.e. not cancelled).

The format for both collections and deliveries will be the same and will match the current documentation.

The data held within the bar code is a unique reference to the consignment matching the data in the host system. This data will be displayed instead of the barcode. The 'Consignment Number' will be passed to ePOD as the EPL_CUST_REF.

===Data Clear-down===
A data clear-down script will be written and scheduled to run on the host server. This will check the job and image data files and clear down any records older than a specific date.

{{Note}} If this is hosted at OBS, the responsibility of creating and running this script will be OBS'. If hosted by the client, this will be the responsibility of the client.

===Admin Screens===
The Admin Users will be provided log-ons - these will be manually created within the Admin system itself. Each log-on can be configured to see all Job Groups (Depots) or a selection of job groups only.

These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.

No changes need to be made within the Administration screen in the ''CALIDUS'' EPOD system, as both the entered Notes and advised Owner can be seen when viewing the completion document within the Admin system.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.

== Scope ==
The developments will take place against the latest version of the EPOD system (1.2.X)

The described process flow requires functionality currently being developed, as follows:
* Auto-Email
* PDF Completion Reports
* Auto-Export
* Site Email Address
* Container-only Delivery
* Change Job Identifier on PDA


= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
A Site will be generated. This will be agreed in advance, but is expected to be "PROLOG". This is generated and maintained through the Site Admin screen.
*Automatic Email of POD to a Site email address will be enabled from this screen, by entering a Site email address.
*PDF Production will be enabled from this screen.
*Automatic Export of data will be configured through the Transfer Configuration assigned to the Site record. The Transfer Configuration ID can be maintained through the Transfer Configuration screens. Configuration of both the Load and Job exports will be required.

A Job Group will be set up for each Depot, through the Job Group Admin screen.
*The format for both collections and deliveries will be set to "Prolog" against each Job Group, from the Job Groups screen.
*The expected configuration for both Collections and Deliveries will be that the user will be prompted to sign for the job, then the customer will be asked to sign for this also. This will be through the configuration flags EPL_DEL_DRIVER_SIGN and EPL_COL_DRIVER_SIGN against the EPOD_JOB_GROUP records. These can be configured through the Job Group Config screen, accessible from the Job Groups screen.
*The PDA will not prompt for confirmation of Products at delivery if it has them - this is controlled by setting the "Delivery without Products" flag against each Job Group, maintained in the Job Group screen.
*The PDA will be configured to display the Job Code on the Job Detail screen as the Job Reference, rather than the Job ID. If the system is generating IDs for the received jobs, this should be done. This can be completed through the Job Groups admin screen.
*Metrics entry of mileage information at the start and end of a Load will be enabled.
*Entry of Notes information at the end of a Job will be enabled.

A Customer record will be set up for each of the Job Groups, with the same ID as the Job Groups. This address of these customer records will be used to identify the Depot Address on the documentation.

Reason Codes will be set up as agreed between the host system and ''CALIDUS'' EPOD. These are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system

= Functional Description =
The following areas will require modification:
*Database fields
*Import
**Job
**Load
*Pass new configuration to PDA
*Job Assignation by Vehicle
*Metric Entry
*Load Update from PDA to Server
*Add Notes tab to Collection and Delivery
*Add Notes to Job Update
*Add Notes to Job Export data
*Add Load Auto-Export
*POD/POC Formats
*Data Cleardown

==Database Fields==
New fields will be added to the EPOD_JOB table:
*EPL_USER_NOTES - a Max length text field
*EPL_OWNER_NAME - a 30-character text field

New fields will be added to the EPOD_LOAD table
*EPL_MILEAGE_START - an integer field
*EPL_MILEAGE_END - an integer field
*EPL_XFER_FLAG - a Y/N flag to control whether the load has been exported yet.

New Configuration fields will be added to EPOD_JOB_GROUP and EPOD_SITE:
*EPL_METRIC_ENTRY - a Y/N flag to control entry of mileage information at the start and end of a Load.
*EPL_NOTES - a Y/N flag to control entry of Notes information at the end of a Job.

A new field will be added to EPOD_XF_CONFIG:
*EPL_XF_ID - a 20-character ID field.
The index will be modified to add this field.

Values in this field will be:
*JOB - A configuration set for JOB updates
*LOAD - A configuration set for LOAD updates

New Fields to both EPOD_CUSTOMER and EPOD_JOB_ADDRESS
*EPL_ADDRESS_5

==Import Data==
Import and Export of Jobs and Loads will be through the existing standard Web Services.

===Job===
An Owner field added to the Job import, to allow the client system to specify the Depot (e.g. Britvic).

The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).

Delivery jobs will be sent with one container record and multiple product records. The container record will be provided with a description of the required pallets and weight (for example, "2 Pallets / 174.0 Kg"). All products associated to the job will be added to this container, detailing the product code, description and quantity.

Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.

Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job.

<PRE>
<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>00067527</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>00067527</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_002</EPL_JOB_CODE>
<EPL_CUST_REF>00067523</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE></EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>2 Pallets / 174.0Kg</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>
</PRE>
Notes:
*EPL_SITE_ID will be mapped to the single company site ID - this is suggested to be "PROLOG"
*EPL_JOB_GROUP will be the originating Depot ID (e.g. "SHEFFIELD"). These will be pre-set and agreed in advance.
*EPL_JOB_ID (10 characters) is a unique reference for the individual job (collection or delivery). For linked collections and deliveries, each job should have a unique EPL_JOB_ID, but the same EPL_JOB_CODE. If left blank, this will be generated by the system. This will be mapped to the unique value of the currently used barcode.
*EPL_JOB_CODE (20 characters) will be any reference that ties linked jobs together.
*An additional reference can be mapped to EPL_CUST_REF (30 characters). This will map to the consignment number.
*The customer code, name, contact and address information will be mapped to the appropriate fields.
*EPL_CONTAINER_ID (15 characters) will be the Order Reference.
*EPL_CONTAINER_PACKAGE_DESC (40 characters) will contain the text showing the total pallets and weight.
*The product code, description and quantity will be mapped to the appropriate product tags

===Load===
Loads can be imported separately or the jobs can be included within the EPOD_JOBS tag.

The Load import includes the Driver and Vehicle assigned to the Load.

{{warning}} Currently the client system allocates jobs to a Vehicle, not a Driver, whilst ''CALIDUS'' EPOD assigns by the User ID (the Driver). In the requirements meeting, did we decide which will be changed, EPOD or Transport system?

<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPL_VEHICLE_ID>AB12XYZ</EPL_VEHICLE_ID>
<EPOD_JOBS>
...
</EPOD_JOBS>
</EPOD_LOAD>
<EPOD_LOAD>
...
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

==Pass new Configuration to PDA==
Each Driver will have a PDA with the ''CALIDUS'' EPOD system installed and configured on it. The user will log in with a User ID and password provided to them, and a Vehicle ID, chosen from a list.

The server responds with a Logon Response, passing all the configuration and standing data to the device. The configuration will be modified to include the new configuration elements against the Site and Job Group. The PDA will store this configuration.

==Metric Entry==
Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point. This will be though a form to enter the mileage in numeric form.

This form will be shown once all jobs are complete against a Load, to enter the mileage at end of the full trip. This will default to the first mileage entered. A prompt at this atge will say "Load Completed. Return to Base, then enter Mileage".

==Load Update from PDA to Server==
Both of the entry items will be sent back to the Server on a new Load Update message, showing that the load is now complete.

The Server will action this message and store the mileage values on the message onto the new fields in the database against the load.

{{Note}} The Actual Distance value against the load will be calculated and stored here as well, by taking the start mileage value from the end mileage. If the value results in a negative value, this will be saved as 0 miles, as the user has made an error inputting the mileage information.

If the Site has been configured for transmitting Load data back to the host system, the Load record's EPL_XFER_FLAG will be marked as "N", to indicate that the record has not yet been transmitted, otherwise this will be set to "".

==Add Notes tab to Collection and Delivery==
A new tab will be added to the Collection and Delivery process, if the system has been configured to do so through the new EPL_NOTES configuration element. The note field will allow free-text entry by the user.

The tab will be added as the last tab on each screen. The unit will function as follows:

===Collection Process===
For collections, the user will be shown instructions for the job, with a list of all required products and quantities to collect in the instructions field.

If the collection is successful with no changes, the user will click the '''OK''' button to confirm this and be taken to the Confirmation process.

If nothing can be collected, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the collection, the user will click the '''Notes''' tab and enter details on the adjustment to the collection. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

===Delivery Process===
Deliveries (from Depots to Customers) will be configured to ensure that the PDA unit only requires the user to confirm containers rather than individual products (through the existing configuration flag EPL_CONTAINER_ONLY), as follows:

The user will be shown a list of containers only. The description on here will display the number of pallets.

By long-clicking on the container, the user can view a list of all the products in this container.

If all has been delivered successfully, the user will click the '''Collected''' button and be taken to the Confirmation process.

If nothing can be delivered, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the delivery, the user will click the '''Notes''' tab and enter details on the adjustment to the delivery. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

Deliveries (from a supplier to a customer direct) will not follow this process, as no container or product details will have been provided on the job. The Notes information from the collection will have been automatically updated onto the associated delivery, so the user will be able to see what was collected. The user will be able to confirm the delivery with the '''OK''' button, cancel the delivery through the '''Cancel''' button and amend the notes as above.

==Add Notes to Job Update==
When a job is complete (confirmed or cancelled) the PDA sends the job update back to the server, which will complete the job as per normal processing.

The Job Update message must be modified to pass back the Notes data entered above.

{{Note}} If the job being updated is a collection and there are any deliveries with the same Job Code, the PDA unit will update the linked job on the device with the notes from the collection.

==Add Notes to Job Export data==
When data is sent back to the server for jobs completed or cancelled, the server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All jobs completed in this manner will be forwarded on to a configured Web Service within the client host system, in the standard ''CALIDUS'' EPOD format.

The format will be changed to include the Notes field, as in the example below:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE></EPL_JOB_CODE>
<EPL_CUST_REF>00067523</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPL_NOTES>Any user-entered notes here</EPL_NOTES>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

{{Note}} Other elements may be included but will contain no data - these may be ignored.

==Load Auto-Export==
The Load Export schema will be modified as in the following example:
<EPL_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL_LOAD_END_PLANNED_TIME>00000000</EPL_LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_MILEAGE_START>0</EPL_MILEAGE_START>
<EPL_MILEAGE_END>0</EPL_MILEAGE_END>
<EPL_USER_ID>MATT</EPL_USER_ID>
</EPL_LOAD>

The Auto-Export process will be modified to add Load export, if configured against the Site or Job Group's EPOD_XF_CONFIG.

The process will be similar to the Job Export - all Loads will be checked if they are required to be exported (through the new EPL_XFER_FLAG against the Load) and a configuration exists for that site or job group. If found, these Load Exports will be sent to the client via the required method (again on the Config table)

==Completion Documents (POD/POC)==
This automated process will also create the Completion documents in PDF format and email them to a central email address, configured against the site in ''CALIDUS'' EPOD.

A document will be generated for every collection and delivery completed (i.e. not cancelled).

The format for both collections and deliveries will be the same and will match the current documentation, shown in [[#Appendix A: POD Formats]]. The format will be created with a name of "Prolog" and this will be able to be chosen as an option from the Delivery and Collection Formats against the Job Group.

The data will be mapped as follows:
*'''From''': The Name will come from the new EPL_OWNER field on EPOD_JOB. The address information will come from the customer address with the same ID as EPL_JOB_GROUP of EPOD_JOB.
*'''Delivery Instructions''': EPL_JOB_INSTRUCTION of EPOD_JOB
*'''Customer''': The Code will be EPL_CUSTOMER_CODE of EPOD_JOB. The address will be taken from this customer's EPOD_CUSTOMER record.
*'''"2 Pallets / 162 Kg"''': EPL_CONTAINER_PACKAGE_DESC of EPOD_CONTAINER
*'''Order Reference''': EPL_CONTAINER_ID of EPOD_CONTAINER
*'''Order Processed''': EPL_START_ACTUAL_DATE of EPOD_JOB
*'''Reference''': EPL_PRODUCT_CODE of EPOD_PRODUCT
*'''Description''': EPL_DESCRIPTION of EPOD_PRODUCT
*'''Qty''': EPL_PRODUCT_QTY_ACTUAL of EPOD_PRODUCT
*'''Signature''': EPL_JOB_SIGNATURE of EPOD_JOB
*'''Block Print''': EPL_CUST_SIGNATORY of EPOD_JOB
*'''Date''': EPL_END_ACTUAL_DATE of EPOD_JOB
*'''Time''': EPL_END_ACTUAL_TIME of EPOD_JOB
*'''Notes''': EPL_NOTES of EPOD_JOB {{Note}} New Field
*'''Consignment Barcode''': {{Warning}} is this required? If so, from what data?
*'''"SM0425 00000 00113306"''': {{Warning}} is this required? If so, from what data?
{{warning}} The data contained in the barcode is not the number above - what is this?

==Data Clear-down==
A data clear-down script will be written and scheduled to run on the host server. This will check the job and image data files and clear down any records older than a specific date.

{{Note}} If this is hosted at OBS, the responsibility of creating and running this script will be OBS'. If hosted by the client, this will be the responsibility of the client.

The process should receive parameters specifying:
*The database connection.
*The Number of Days Transactional Data to keep.
*The Number of Days Image Data to keep.
*The Number of Days Signature Data to keep.

==Admin Screens==
The Admin Users will be provided log-ons - these will be manually created within the Admin system itself. Each log-on can be configured to see all Job Groups (Depots) or a selection of job groups only.

These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.

The Job Group screen will require modification, to add the new configuration flags (detailed in section [[#Database Fields|Database Fields]]

The Load screen will be modified to add a mouse-over tool-tip, displaying the start and end vehicle mileage.

The File Transfer Configuration screens will be modified to allow users to set up multiple configurations against a EPL_XF_CONFIG_ID, for each EPL_XF_ID.

No further changes need to be made within the Administration screen in the ''CALIDUS'' EPOD system, as both the entered Notes and advised Owner can be seen when viewing the completion document within the Admin system.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.



= Appendix A: POD Formats =
[[File:297001-DeliveryNote.jpg|700px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|Ref1=UG 291094 EPOD Admin User Guide
|RefV1=1.0
|RefDate1=6/10/2011
|Ref2=UG 291097 EPOD Client User Guide
|RefV2=1.0
|RefDate2=6/10/2011
|REQ=0
|EST=0
|FS=2
|TS=0
|DEV=16
|ST=5
|IMP=0
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=N
|Rev1=Tony Walker
|Rev1Title=Consultant
|Rev2=Matt Turner
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 297001 Prolog EPOD Modifications

2012-03-07T11:19:09Z

Milesl: Added Address line 5

<div class="noprint">
{{#vardefine:Client|PROL}}
{{#vardefine:ClientName|PROLOG}}
{{#vardefine:System|''CALIDUS'' EPOD}}
{{#vardefine:Doc_Title|Prolog EPOD Modifications}}
{{#vardefine:Version|0.4}}
{{#vardefine:Date|1st March 2012}}
{{#vardefine:Reference|297001}}
{{#vardefine:Year|2012}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}


<div class="noprint">
= Functional Overview =
There will be 35 PDA users and 5 Admin users hosted by the Prolog system.

There are expected to be 35 loads per day.

There are expected to be approximately 10 jobs per load.

There are expected to be up to 52 containers/products per load.

There will be 3 job groups, allocated to each Depot.

== Client Requirement ==
The client requires an implementation of the {{#var:System}} system, following the functionality as described below.

== Solution Overview ==
===Import Data===
Import and Export of Jobs and Loads will be through the existing standard Web Services.

The Job Group field will identify the depot from which the Job originates.

An Owner field added to the Job import, to allow the client system to specify Prolog's Client (e.g. Britvic).

The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).

Delivery jobs will be sent with one container record and multiple product records. The container record will be provided with a description of the required pallets and weight (for example, "2 Pallets / 174.0 Kg"). All products associated to the job will be added to this container, detailing the product code, description and quantity.

Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.

Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job.

The Load import includes the Driver assigned to the Load.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.

===PDA Log-on===
Each Driver will have a PDA with the ''CALIDUS'' EPOD system installed and configured on it. The user will log in with a User ID and password provided to them, and a Vehicle ID, chosen from a list.

===Vehicle Checks===
If the vehicle being used has not been checked recently, the unit will direct the user to complete the Vehicle Checks. The data entry and checks here are configurable within the Admin system. The checks required will be sent to OBS so that they can configure the checks required at this stage.

===Metrics===
Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point.

{{note}} The user will also be prompted to enter the mileage once all jobs on the load are complete.

The user will then be shown a list all the jobs on the load that has been assigned to the user. The jobs are displayed in the order in which they should be completed. However, the jobs can be completed in any sequence by clicking the line of the job required to to be completed first and then clicking the '''OK''' button. The user will then be taken to the Job Details page, which displays the full details of the job being undertaken.
The screen has several Tabs, each showing:
* The Job Type (Collection, Delivery, Service)
* The customer details (Customer Code, Name, Address and Postcode)
* The contact information (Contact name and number)
* The Instructions for the job
From these tabs, the user can:
* Call the customer by clicking on the '''Call''' button.
* Navigate to the customer's address by clicking on the '''Navigate''' button.

Again, here the user can choose which job to complete by using the supplied left and right buttons or start a job with the '''OK''' button, when either a Collection or Delivery process will begin.

{{Note}} The job can be cancelled at this stage by clicking the '''Cancel''' button. The unit will take to the user to an Exception screen and prompt them to enter a reason code explaining why this job was cancelled. See the Exception process for more information.

===Collection Process===
For collections, the user will be shown instructions for the job, with a list of all required products and quantities to collect.

If the collection is successful with no changes, the user will click the '''OK''' button to confirm this and be taken to the Confirmation process.

If nothing can be collected, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the collection, the user will click the '''Notes''' tab and enter details on the adjustment to the collection. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

===Delivery Process===
Deliveries (from Depots to Customers) will be configured to ensure that the PDA unit only requires the user to confirm containers rather than individual products, as follows:

The user will be shown a list of containers only. The description on here will display the number of pallets.

By long-clicking on the container, the user can view a list of all the products in this container.

If all has been delivered successfully, the user will click the '''Collected''' button and be taken to the Confirmation process.

If nothing can be delivered, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the delivery, the user will click the '''Notes''' tab and enter details on the adjustment to the delivery. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

Deliveries (from a supplier to a customer direct) will not follow this process, as no container or product details will have been provided on the job. The Notes information from the collection will have been automatically updated onto the associated delivery, so the user will be able to see what was collected. The user will be able to confirm the delivery with the '''OK''' button, cancel the delivery through the '''Cancel''' button and amend the notes as above.

===Exception Process===
This screen will be displayed if the user is cancelling an entire job, as described in the previous sections.

When cancelling a Job, the user is asked to enter a reason for the cancellation or shortage. These reasons are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system.

If necessary, the user can capture an image to support this reason, by clicking the '''Image''' button. The user can then use the device's camera to capture an image. When complete, the user will exit and will be allowed to view the captured image and add a note to the image to explain.

Once the exception is complete, the user will be returned to the job list, to complete the next job.

===Confirmation Process===
The expected configuration for both Collections and Deliveries will be that the user will be prompted to sign for the job, then the customer will be asked to sign for this also.

The Name defaults to the customer contact name (if present on the job) and allows the user to change this.

Once completed, The user will be returned to the Job Menu to pick up the next task.

The completed job will be transferred back to the main ''CALIDUS'' EPOD system with all the details, signatures and photos.

Once all jobs are completed on that load, the user will be prompted to enter the mileage of the vehicle when they have returned to base. This and the starting mileage will be sent back to the main ''CALIDUS'' EPOD system.

===Export Data===
When data is sent back to the server for jobs completed or cancelled, the server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All jobs completed in this manner will be forwarded on to a configured Web Service within the client host system, in the standard ''CALIDUS'' EPOD format.

When metric data is sent back for the Load, this will be stored in the ''CALIDUS'' EPOD database. The server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All loads completed in this manner will be forwarded on to a configured Web Service within the client host system, in the new format created for this purpose.

===Completion Documents (POD/POC)===
This automated process will also create the Completion documents in PDF format and email them to a central email address, configured against the site in ''CALIDUS'' EPOD.

A document will be generated for every collection and delivery completed (i.e. not cancelled).

The format for both collections and deliveries will be the same and will match the current documentation.

The data held within the bar code is a unique reference to the consignment matching the data in the host system. This data will be displayed instead of the barcode. The 'Consignment Number' will be passed to ePOD as the EPL_CUST_REF.

===Data Clear-down===
A data clear-down script will be written and scheduled to run on the host server. This will check the job and image data files and clear down any records older than a specific date.

{{Note}} If this is hosted at OBS, the responsibility of creating and running this script will be OBS'. If hosted by the client, this will be the responsibility of the client.

===Admin Screens===
The Admin Users will be provided log-ons - these will be manually created within the Admin system itself. Each log-on can be configured to see all Job Groups (Depots) or a selection of job groups only.

These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.

No changes need to be made within the Administration screen in the ''CALIDUS'' EPOD system, as both the entered Notes and advised Owner can be seen when viewing the completion document within the Admin system.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.

== Scope ==
The developments will take place against the latest version of the EPOD system (1.2.X)

The described process flow requires functionality currently being developed, as follows:
* Auto-Email
* PDF Completion Reports
* Auto-Export
* Site Email Address
* Container-only Delivery
* Change Job Identifier on PDA


= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
A Site will be generated. This will be agreed in advance, but is expected to be "PROLOG". This is generated and maintained through the Site Admin screen.
*Automatic Email of POD to a Site email address will be enabled from this screen, by entering a Site email address.
*PDF Production will be enabled from this screen.
*Automatic Export of data will be configured through the Transfer Configuration assigned to the Site record. The Transfer Configuration ID can be maintained through the Transfer Configuration screens. Configuration of both the Load and Job exports will be required.

A Job Group will be set up for each Depot, through the Job Group Admin screen.
*The format for both collections and deliveries will be set to "Prolog" against each Job Group, from the Job Groups screen.
*The expected configuration for both Collections and Deliveries will be that the user will be prompted to sign for the job, then the customer will be asked to sign for this also. This will be through the configuration flags EPL_DEL_DRIVER_SIGN and EPL_COL_DRIVER_SIGN against the EPOD_JOB_GROUP records. These can be configured through the Job Group Config screen, accessible from the Job Groups screen.
*The PDA will not prompt for confirmation of Products at delivery if it has them - this is controlled by setting the "Delivery without Products" flag against each Job Group, maintained in the Job Group screen.
*The PDA will be configured to display the Job Code on the Job Detail screen as the Job Reference, rather than the Job ID. If the system is generating IDs for the received jobs, this should be done. This can be completed through the Job Groups admin screen.
*Metrics entry of mileage information at the start and end of a Load will be enabled.
*Entry of Notes information at the end of a Job will be enabled.

A Customer record will be set up for each of the Job Groups, with the same ID as the Job Groups. This address of these customer records will be used to identify the Depot Address on the documentation.

Reason Codes will be set up as agreed between the host system and ''CALIDUS'' EPOD. These are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system

= Functional Description =
The following areas will require modification:
*Database fields
*Import
**Job
**Load
*Pass new configuration to PDA
*Job Assignation by Vehicle
*Metric Entry
*Load Update from PDA to Server
*Add Notes tab to Collection and Delivery
*Add Notes to Job Update
*Add Notes to Job Export data
*Add Load Auto-Export
*POD/POC Formats
*Data Cleardown

==Database Fields==
New fields will be added to the EPOD_JOB table:
*EPL_USER_NOTES - a Max length text field
*EPL_OWNER_NAME - a 30-character text field

New fields will be added to the EPOD_LOAD table
*EPL_MILEAGE_START - an integer field
*EPL_MILEAGE_END - an integer field
*EPL_XFER_FLAG - a Y/N flag to control whether the load has been exported yet.

New Configuration fields will be added to EPOD_JOB_GROUP and EPOD_SITE:
*EPL_METRIC_ENTRY - a Y/N flag to control entry of mileage information at the start and end of a Load.
*EPL_NOTES - a Y/N flag to control entry of Notes information at the end of a Job.

A new field will be added to EPOD_XF_CONFIG:
*EPL_XF_ID - a 20-character ID field.
The index will be modified to add this field.

Values in this field will be:
*JOB - A configuration set for JOB updates
*LOAD - A configuration set for LOAD updates

New Fields to both EPOD_CUSTOMER and EPOD_JOB_ADDRESS
*EPL_ADDRESS_5

==Import Data==
Import and Export of Jobs and Loads will be through the existing standard Web Services.

===Job===
An Owner field added to the Job import, to allow the client system to specify the Depot (e.g. Britvic).

The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).

Delivery jobs will be sent with one container record and multiple product records. The container record will be provided with a description of the required pallets and weight (for example, "2 Pallets / 174.0 Kg"). All products associated to the job will be added to this container, detailing the product code, description and quantity.

Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.

Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job.

<PRE>
<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>00067527</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>00067527</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_002</EPL_JOB_CODE>
<EPL_CUST_REF>00067523</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE></EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>2 Pallets / 174.0Kg</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>
</PRE>
Notes:
*EPL_SITE_ID will be mapped to the single company site ID - this is suggested to be "PROLOG"
*EPL_JOB_GROUP will be the originating Depot ID (e.g. "SHEFFIELD"). These will be pre-set and agreed in advance.
*EPL_JOB_ID (10 characters) is a unique reference for the individual job (collection or delivery). For linked collections and deliveries, each job should have a unique EPL_JOB_ID, but the same EPL_JOB_CODE. If left blank, this will be generated by the system. This will be mapped to the unique value of the currently used barcode.
*EPL_JOB_CODE (20 characters) will be any reference that ties linked jobs together.
*An additional reference can be mapped to EPL_CUST_REF (30 characters). This will map to the consignment number.
*The customer code, name, contact and address information will be mapped to the appropriate fields.
*EPL_CONTAINER_ID (15 characters) will be the Order Reference.
*EPL_CONTAINER_PACKAGE_DESC (40 characters) will contain the text showing the total pallets and weight.
*The product code, description and quantity will be mapped to the appropriate product tags

===Load===
Loads can be imported separately or the jobs can be included within the EPOD_JOBS tag.

The Load import includes the Driver and Vehicle assigned to the Load.

{{warning}} Currently the client system allocates jobs to a Vehicle, not a Driver, whilst ''CALIDUS'' EPOD assigns by the User ID (the Driver). In the requirements meeting, did we decide which will be changed, EPOD or Transport system?

<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPL_VEHICLE_ID>AB12XYZ</EPL_VEHICLE_ID>
<EPOD_JOBS>
...
</EPOD_JOBS>
</EPOD_LOAD>
<EPOD_LOAD>
...
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

==Pass new Configuration to PDA==
Each Driver will have a PDA with the ''CALIDUS'' EPOD system installed and configured on it. The user will log in with a User ID and password provided to them, and a Vehicle ID, chosen from a list.

The server responds with a Logon Response, passing all the configuration and standing data to the device. The configuration will be modified to include the new configuration elements against the Site and Job Group. The PDA will store this configuration.

==Metric Entry==
Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point. This will be though a form to enter the mileage in numeric form.

This form will be shown once all jobs are complete against a Load, to enter the mileage at end of the full trip. This will default to the first mileage entered. A prompt at this atge will say "Load Completed. Return to Base, then enter Mileage".

==Load Update from PDA to Server==
Both of the entry items will be sent back to the Server on a new Load Update message, showing that the load is now complete.

The Server will action this message and store the mileage values on the message onto the new fields in the database against the load.

{{Note}} The Actual Distance value against the load will be calculated and stored here as well, by taking the start mileage value from the end mileage. If the value results in a negative value, this will be saved as 0 miles, as the user has made an error inputting the mileage information.

If the Site has been configured for transmitting Load data back to the host system, the Load record's EPL_XFER_FLAG will be marked as "N", to indicate that the record has not yet been transmitted, otherwise this will be set to "".

==Add Notes tab to Collection and Delivery==
A new tab will be added to the Collection and Delivery process, if the system has been configured to do so through the new EPL_NOTES configuration element. The note field will allow free-text entry by the user.

The tab will be added as the last tab on each screen. The unit will function as follows:

===Collection Process===
For collections, the user will be shown instructions for the job, with a list of all required products and quantities to collect in the instructions field.

If the collection is successful with no changes, the user will click the '''OK''' button to confirm this and be taken to the Confirmation process.

If nothing can be collected, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the collection, the user will click the '''Notes''' tab and enter details on the adjustment to the collection. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

===Delivery Process===
Deliveries (from Depots to Customers) will be configured to ensure that the PDA unit only requires the user to confirm containers rather than individual products (through the existing configuration flag EPL_CONTAINER_ONLY), as follows:

The user will be shown a list of containers only. The description on here will display the number of pallets.

By long-clicking on the container, the user can view a list of all the products in this container.

If all has been delivered successfully, the user will click the '''Collected''' button and be taken to the Confirmation process.

If nothing can be delivered, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the delivery, the user will click the '''Notes''' tab and enter details on the adjustment to the delivery. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

Deliveries (from a supplier to a customer direct) will not follow this process, as no container or product details will have been provided on the job. The Notes information from the collection will have been automatically updated onto the associated delivery, so the user will be able to see what was collected. The user will be able to confirm the delivery with the '''OK''' button, cancel the delivery through the '''Cancel''' button and amend the notes as above.

==Add Notes to Job Update==
When a job is complete (confirmed or cancelled) the PDA sends the job update back to the server, which will complete the job as per normal processing.

The Job Update message must be modified to pass back the Notes data entered above.

{{Note}} If the job being updated is a collection and there are any deliveries with the same Job Code, the PDA unit will update the linked job on the device with the notes from the collection.

==Add Notes to Job Export data==
When data is sent back to the server for jobs completed or cancelled, the server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All jobs completed in this manner will be forwarded on to a configured Web Service within the client host system, in the standard ''CALIDUS'' EPOD format.

The format will be changed to include the Notes field, as in the example below:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE></EPL_JOB_CODE>
<EPL_CUST_REF>00067523</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPL_NOTES>Any user-entered notes here</EPL_NOTES>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

{{Note}} Other elements may be included but will contain no data - these may be ignored.

==Load Auto-Export==
The Load Export schema will be modified as in the following example:
<EPL_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL_LOAD_END_PLANNED_TIME>00000000</EPL_LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_MILEAGE_START>0</EPL_MILEAGE_START>
<EPL_MILEAGE_END>0</EPL_MILEAGE_END>
<EPL_USER_ID>MATT</EPL_USER_ID>
</EPL_LOAD>

The Auto-Export process will be modified to add Load export, if configured against the Site or Job Group's EPOD_XF_CONFIG.

The process will be similar to the Job Export - all Loads will be checked if they are required to be exported (through the new EPL_XFER_FLAG against the Load) and a configuration exists for that site or job group. If found, these Load Exports will be sent to the client via the required method (again on the Config table)

==Completion Documents (POD/POC)==
This automated process will also create the Completion documents in PDF format and email them to a central email address, configured against the site in ''CALIDUS'' EPOD.

A document will be generated for every collection and delivery completed (i.e. not cancelled).

The format for both collections and deliveries will be the same and will match the current documentation, shown in [[#Appendix A: POD Formats]]. The format will be created with a name of "Prolog" and this will be able to be chosen as an option from the Delivery and Collection Formats against the Job Group.

The data will be mapped as follows:
*'''From''': The Name will come from the new EPL_OWNER field on EPOD_JOB. The address information will come from the customer address with the same ID as EPL_JOB_GROUP of EPOD_JOB.
*'''Delivery Instructions''': EPL_JOB_INSTRUCTION of EPOD_JOB
*'''Customer''': The Code will be EPL_CUSTOMER_CODE of EPOD_JOB. The address will be taken from this customer's EPOD_CUSTOMER record.
*'''"2 Pallets / 162 Kg"''': EPL_CONTAINER_PACKAGE_DESC of EPOD_CONTAINER
*'''Order Reference''': EPL_CONTAINER_ID of EPOD_CONTAINER
*'''Order Processed''': EPL_START_ACTUAL_DATE of EPOD_JOB
*'''Reference''': EPL_PRODUCT_CODE of EPOD_PRODUCT
*'''Description''': EPL_DESCRIPTION of EPOD_PRODUCT
*'''Qty''': EPL_PRODUCT_QTY_ACTUAL of EPOD_PRODUCT
*'''Signature''': EPL_JOB_SIGNATURE of EPOD_JOB
*'''Block Print''': EPL_CUST_SIGNATORY of EPOD_JOB
*'''Date''': EPL_END_ACTUAL_DATE of EPOD_JOB
*'''Time''': EPL_END_ACTUAL_TIME of EPOD_JOB
*'''Notes''': EPL_NOTES of EPOD_JOB {{Note}} New Field
*'''Consignment Barcode''': {{Warning}} is this required? If so, from what data?
*'''"SM0425 00000 00113306"''': {{Warning}} is this required? If so, from what data?
{{warning}} The data contained in the barcode is not the number above - what is this?

==Data Clear-down==
A data clear-down script will be written and scheduled to run on the host server. This will check the job and image data files and clear down any records older than a specific date.

{{Note}} If this is hosted at OBS, the responsibility of creating and running this script will be OBS'. If hosted by the client, this will be the responsibility of the client.

The process should receive parameters specifying:
*The database connection.
*The Number of Days Transactional Data to keep.
*The Number of Days Image Data to keep.
*The Number of Days Signature Data to keep.

==Admin Screens==
The Admin Users will be provided log-ons - these will be manually created within the Admin system itself. Each log-on can be configured to see all Job Groups (Depots) or a selection of job groups only.

These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.

The Job Group screen will require modification, to add the new configuration flags (detailed in section [[#Database Fields|Database Fields]]

The Load screen will be modified to add a mouse-over tool-tip, displaying the start and end vehicle mileage.

The File Transfer Configuration screens will be modified to allow users to set up multiple configurations against a EPL_XF_CONFIG_ID, for each EPL_XF_ID.

No further changes need to be made within the Administration screen in the ''CALIDUS'' EPOD system, as both the entered Notes and advised Owner can be seen when viewing the completion document within the Admin system.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.



= Appendix A: POD Formats =
[[File:297001-DeliveryNote.jpg|700px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|Ref1=UG 291094 EPOD Admin User Guide
|RefV1=1.0
|RefDate1=6/10/2011
|Ref2=UG 291097 EPOD Client User Guide
|RefV2=1.0
|RefDate2=6/10/2011
|REQ=0
|EST=0
|FS=2
|TS=0
|DEV=16
|ST=5
|IMP=0
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=N
|Rev1=Tony Walker
|Rev1Title=Consultant
|Rev2=Matt Turner
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 294838 Proctor ePOD Modifications

2012-03-07T11:09:32Z

Milesl: /* EPOD_JOB */

<div class="noprint">
{{#vardefine:Client|PROC}}
{{#vardefine:ClientName|Proctors}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Proctors ePOD Modifications}}
{{#vardefine:Version|1.1}}
{{#vardefine:Date|01st March 2012}}
{{#vardefine:Reference|294838}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==

== Solution Overview ==

The ERP system will be able to interface Customer data to the ''CALIDUS'' EPOD system, to identify the customer address, contact and email information.

{{Note}} Customers can also be created through the standard Job interface - if this is the case, then the Job address provided with the first job for this customer will become the customer address.

Jobs will be received for Collection and Delivery from the following main customer types:
*Suppliers
*Customers
*Proctors-operated Warehouses
*3rd Party Warehouses

The jobs will be updated into the ''CALIDUS'' EPOD system through the standard WebService interface.

This job upload will create 2 tasks:
*A Collection Job
*A Delivery Job

Every Collection and Delivery will be specified separately within the interface, with the Product and Quantity specified for all jobs. Linked collections and deliveries will have the same Job Code, but will be distinguished by the Job Type (i.e. Collection or Delivery).

The Upload system will also identify the Loads onto which jobs are planned, as all planning is completed through the Proctors' ERP system.

In phase 1, the initial uploads will be sent to the EPOD system with either no load information, or with the load ID set to a default value.

In phase 2, the initial uploads will be sent tot he EPOD system with either no load information, or with the correct load identified against them. It will then be possible to subsequently update the Load for a job through another update of the Job alone.

There are two types of job:
* Customer/Supplier jobs - jobs that begin or end with a Customer or Supplier.
* Inter-warehouse Transfer - jobs that begin and end from Warehouses

All jobs will be categorised by the ''CALIDUS'' EPOD Job Group into one of the two categories - this will define the paperwork produced by the system when the job is completed. The Job Group will be agreed and sent to the system in the upload files.

Once jobs from Proctors-controlled warehouses are picked and marshalled, updated Jobs will be sent to the EPOD system, detailing the actual containers (pallets) and product quantities on each.

{{Note}} If this data is not available at the time of collecting or delivering the associated jobs, the system will check periodically through a regularly-scheduled automatic process.

Collection jobs from a Proctors-operated warehouse should then have containers and product quantities specified against them. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.

{{Warning}} In this circumstance, where pallet information has not been received, the automatic update of the job when complete will identify on product and quantity information, not pallet information.

The process for a Collection of this type will be:
* Confirm arrival to warehouse.
* Scan/Enter/Select Pallets to be collected.
* Once completed, confirm collection through depot signature.
The user will also be able to long-press against any container to show the details of any products contained within it.

Collection jobs from a Customer, Supplier or 3rd party warehouse (i.e. non-Proctors) will have the Product and Quantity created against them (i.e. no containers/pallets). The process will be:
* Confirm arrival to customer/supplier/warehouse.
* Scan/Enter/Select Products to be collected.
* Confirm total quantity of the products.
* Once completed, confirm collection through customer/supplier signature.

A Delivery of a non-Proctors job will have only product and quantity details. The process will be:
* Confirm arrival to customer.
* Scan/Enter/Select Products to be delivered.
* Confirm total quantity of the products.
* Once completed, confirm delivery through customer signature.

A Delivery of Proctors job should have container (pallet), product and quantities. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.
The process will be:
* Confirm arrival to customer/depot.
* Scan/Enter/Select pallets being delivered
* Once completed, confirm delivery through customer/depot signature.

{{Note}} The system will be configurable to allow the PDA unit to display Job Code rather than Job ID on the Job Detail screen.

Two new POD document formats will be created:
* A Delivery format, configured for use on Customer/Supplier jobs.
* A Transfer format, configured for use on Inter-warehouse Transfers.
These formats will be defined against the Job group provided on the upload.
In order for these to be created to match the current formats as closely as possible, the ''CALIDUS'' EPOD Job Import will be extended to add new fields, identified in detail later in the document.

''CALIDUS'' EPOD will be set up to allow certain customers to be automatically emailed upon completion of jobs to and from them. When enabled, the format associated to the Job Group will be sent to the Customer's associated email address, if there is one. This will also be sent to an email address against the site, if there is one, ensuring that the ERP system is provided copies of the produced PDF files.

{{Note}} Email notification of the POD or POC will be attempted if this feature is turned on and if the customer has an email address. If depots or suppliers do not require notification of collections or deliveries, it must be ensured that the customers created do not have an email address.

Confirmation or cancellation of any job will trigger an automatic update of the ERP system. This will be configurable but is expected to be through an email of the standard EPOD XML job update message. This update will be a scheduled process that will regularly check and attempt to update when possible. It will be scheduled to run as often as required by the client, up to once per minute.

== Scope ==



= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
The two new fixed Job Groups will be set up for Proctors-controlled warehouses and 3rd-party. The former will be configured with the Stock Transfer POD format, whilst the latter will be configured with the other format.


= Functional Description =
The total changes required are:
* Database
* Job Import/Export
* Customers Import
* Auto-Export
* Auto-Email
* Admin
* PDA Client
** Delivery/Collection Without Products
* New POD formats
* PDF Production

== Database Changes ==

=== EPOD_SITE ===
A new flag will be added for the Site Email Address for auto-email, called EPL_EMAIL

=== EPOD_JOB ===
New Fields:
*EPL_SIGNED_UNCHECKED
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number
*EPL_ORDER_DATE
*EPL_SALES_CONTACT - PPB Contact
*EPL_XFER_FLAG - default to ""
*EPL_EMAIL_FLAG - default to ""
*EPL_JOB_CODE - size increased to 15

Changes:
*Indexing applied to EPL_JOB_CODE, EPL_JOB_TYPE. This will be a repeating index.
*Indexing applied to EPL_XFER_FLAG. This will be a repeating index.
*Indexing applied to EPL_EMAIL_FLAG. This will be a repeating index.

=== EPOD_CONTAINER ===

*EPL_GROSS_WEIGHT - a floating point number.
*EPL_COMMENT - a maximum length text field.

=== EPOD_PRODUCT ===

*EPL_UNIT_TYPE
*EPL_DESCRIPTION_LONG
*EPL_PRODUCT_QTY_ORDERED

=== EPOD_JOB_GROUP ===

*EPL_CONTAINER_ONLY - Controls container-only delivery
*EPL_JOB_DISPLAY - controls whether Job ID or Job Code is displayed on the PDA.

=== XF_CONFIG ===

EPOD_JOB will require a new field of two characters EPL_XFER_FLAG, this will be defaulted to "".
EPOD_SITE and EPOD_JOB_GROUP will require a new field EPL_XF_CONFIG which will link to the EPL_XF_CONFIG_ID. If no export is required this will be blank.

A new table EPOD_XF_CONFIG will be created consisting of:
*EPL_XF_CONFIG_ID: A ten character unique field
*EPL_DESCRIPTION
*EPL_XF_TYPE: A ten character field identifying the type of export (SOAP, File, Email)
*EPL_XF_DESTINATION: A 255 character field identifying the destination of the export
*EPL_XF_PARM: Additional parameters for example subject for email

A new table EPOD_XF_AUDIT_HEADER will be created consisting of:
*EPL_HEADER_ID: A unique auto-increment Id
*EPL_SITE_ID: Indexed
*EPL_JOB_GROUP: Indexed
*EPL_REQUEST_DATA: A maximum length free-text field
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)

A new table EPOD_XF_AUDIT_DETAIL will be created consisting of:
*EPL_HEADER_ID: Foreign key to EPOD_XF_AUDIT_HEADER
*EPL_DETAIL_ID: A unique auto-increment Id
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)
{{Note}} This table is for future development and will not be used at this time.

=== JOB_ADDRESS ===
A new table EPOD_JOB_ADDRESS will be created consisting of:
*EPL_SITE_ID: Foreign key to EPOD_SITE
*EPL_JOB_ID: Foreign key to EPOD_JOB
*EPL_ADDRESS_LINE_1
*EPL_ADDRESS_LINE_2
*EPL_ADDRESS_LINE_3
*EPL_ADDRESS_LINE_4
*EPL_POST_CODE
*EPL_CONTACT
*EPL_TELEPHONE
*EPL_EMAIL
*EPL_LAST_CHANGE_DATE
*EPL_LAST_CHANGE_TIME
The table will be indexed on EPL_SITE_ID and EPL_JOB_ID.

== XML Interface ==

=== Job Import ===

The system shall use the EPL_JOB_CODE field as a reference linking the delivery and collection, the index used shall be EPL_JOB_CODE and EPL_JOB_TYPE. The field EPL_JOB_ID will always be unique, this will be auto-generated by our system if not passed in.

The import can include an optional EPOD_CUSTOMER tag. This is used in preference to the CUSTOMER_NAME and CUSTOMER_CODE tags to update Customer address information. The supplied information against the job is then used exclusively for the Job Address, if different. So for Proctor both the standard adress section with the job message will be completed, mapping to the delivery address (EPOD_JOB_ADDRESS) and the EPOD_CUSTOMER tag will be populated updating the customer address.

The Import XML structure will have a attribute of ID. This will not be stored within the system, instead this will be stamped on the responding message from the web service. Within the responce the EPL_JOB_CODE field will be added to any job records returned in the import confirmation.

Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST" ID="XXXXX">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

The following XML would have the same outcome as above without the generation of container records:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

Both the collection and delivery must share the same EPL_JOB_CODE reference.

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>.
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>

==== Job Update ====

To update the jobs with the Container details, Proctors' ERP must follow the same standard structure as the import.
All Job, Container and Product tags that are populated and present will update the relevant details in the ''CALIDUS'' EPOD system.

{{Note}}
* If the EPL_JOB_ID is blank (as expected for the Proctors interface, as the Collection and Deliveries will be linked via EPL_JOB_CODE), the system will check to see whether a job exists for this EPL_JOB_CODE and EPL_JOB_TYPE. If so, the record will be updated. If not, a new record (with a generated EPL_JOB_ID) will be created.
* If the EPL_JOB_ID is not blank, the system will check to see whether a job exists for this EPL_JOB_ID. If so, the record will be updated. If not, a new record will be created with this EPL_JOB_ID.
* If the EPL_LOAD_ID is left blank, the system will not update the Load ID of the Job.
* If the EPOD_CONTAINERS tag is not populated, the system will not update any container information. If it is present, the system will delete any existing container information and replace it with the information in the containers tag.
* If the EPOD_PRODUCTS tag is not populated, the system will not update any product information. If it is present, the system will delete any existing product information and replace it with the information in the product tag.
* The import can include an optional EPOD_CUSTOMER tag. This is used in preference to the CUSTOMER_NAME and CUSTOMER_CODE tags to update Customer address information. The supplied information against the job is then used exclusively for the Job Address, if different.

Changes will be made to the Customer Address import to ensure that a customer and a job can have defined addresses, as follows:
* If the EPOD_CUSTOMER tag exists in the message
** Pass the contents of the tag to the Customer Import, to update the Customer details
** Use the address information in the message to update the Job Address.
* Else
**If the Customer Code exists in the message
*** the system will check that the record exists within the database with that code.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created with that code.
** If not, and the Customer Name exists
*** the system will check that the record exists within the database with that name.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created and a code generated for it.
** If neither Code nor Name exist, the system will store the address information against the Job.

=== Job Export ===

At the point of job status changed the system will export the Jobs structure using the standard XML and send this to a predefined email address, for interfacing with the ERP system. This will be configured using the XF_CONFIG section of the system.

The required email functionality will need to be added to the existing export process.

The following XML is produced by the export, this example shows the export with multiple Jobs:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PHOTO_ID/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/> <EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575903</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

The following XML is produced by the export, this example shows the export with a single Job:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

==== Auto-Export Process ====

Whenever a job is updated to Cancelled or Complete (i.e. when the jobs are updated by the PDA client, or when jobs are updated via the Admin system), after committing the changes to the database, the Auto Export flag will be checked against the Job Group and Site. If this flag is present the EPL_JOB record will have the EPL_XFER_FLAG set to N, to indicate that the record requires interfacing but has not yet been sent.

{{Note}} These changes will be committed into the Data Access Layer, so that the same code will be called whether running this through the Admin or PDA server functions.

A timed process will be running to send any Jobs with the Xfer flag of N.
The process will:
*Retrieve all jobs on the EPL_JOBS table with the Xfer flag set to N, sorted by Site and Job Group.
*For each record found in distinct Site and Job Group:
**Load the details of this Job ID,
**Generate the XML export as per the standard for currently existing exports
**Once all jobs for the Site/Job Group are exported:
***Get the configuration of the Job Group. If the configuration for the Job Group does not exist, get the configuration for the Site.
***Attempt to transfer this to the destination specified in the configuration.

If this process if successful then the Xfer flag on the Job record will be set to Y, and a success audit record written.
If this fails the flag on the job will be set to N and a record will be written to a audit table with details of the failure.
If the file is send successfully but a message is received from the destination advising of this problem then an audit record will be written and the flag will be set to N.

This timed process will be scheduled on the system. The frequency of the process will be defined by the schedule and can be no more frequent that one per minute. If the process is already running, the process will wait for the next cycle before starting.

The status of the audit records based on the result are:
* S for success;
* SF for success send but error at the receivers, and;
* F for failure to send.
These records will be cleared down once they are older than 7 days.

===Customer Import===
Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_CUSTOMERS>
<EPOD_CUSTOMER>
<EPL_SITE_ID>Dave Jones</EPL_SITE_ID>
<EPL_CUSTOMER_CODE>CUST01</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
</EPOD_CUSTOMERS>

Similarly to the Job import:
* If the Customer Code exists in the message
** the system will check that the record exists within the database with that code.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created.
* If not, and the Customer Name exists
** the system will check that the record exists within the database with that name.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created and a code generated for it.
* If neither exist, the system will not import the customer.

== Admin System ==

Within Phase one the Admin interface will be used to plan Jobs onto loads, all required functionality has been implemented. Within phase two this will not be required as Proctors will interface pre-planned loads.
The following changes will need to be made to the admin system to reflect the database changes:

===Jobs Screen===

*EPL_SIGNED_UNCHECKED - Visible on the POD only, this field is not searchable
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number - Entry only
*EPL_ORDER_DATE - Entry only
*EPL_SALES_CONTACT - PPB Contact - Entry only
*EPOD_JOB_ADDRESS.

In order to accommodate the new fields and allow them to be displayed and entered, the Job screen must be extensively modified.

The Entry panel will be modified to allow entry of the following fields, in two adjacent panels, as below:
<table border="solid black 1px">
<tr><td colspan="2"> '''[Edit buttons]''' </td></tr>
<tr><td width="50%">
Job Type

Job Code

Job Group

Cust Ref

'''Dnote No'''

Planned Date/Time

'''Order Date/Time'''

Sales Contact

Job/Office Instructions

</td><td width="50%">
Customer Code

Use Customer Address as Delivery Address?

'''New Customer Code'''

'''New Customer Name'''

''Address 1''

''Address 2''

''Address 3''

''Address 4''

''Postcode''

''Contact''

''Email''

''Telephone''
</td></tr>
<tr><td colspan="2"> '''[Save] [Cancel]'''</td></tr>
</table>

All fields in '''Bold''' are new fields. All fields in ''Italics'' are new functionality.

The ''Edit'' buttons will not be shown in entry mode.

The left side of the screen will show all the Job-related fields for entry, including the new fields.

The right side of the screen will be the area to identify the customer and address.

The Instructions entry will be through a tabbed entry box. The first tab will contain the Job Instructions and will be displayed. The second tab can be clicked on to edit the Office Instructions.

The Customer drop-down will allow you to select:
* ''No Customer''
** All entry fields (bar Customer Code and Name) below will be enabled.
** The check-box will be disabled.
* ''Create a New Customer'':
** All entry fields below will be enabled.
** Customer Code and Name must be entered
** The check-box will be disabled.
* Select an Existing Customer from the list.
** All fields below will be populated from the Customer's address information.
** The check-box will be enabled, indicating that you are using the Customer's address as the delivery address.
** Only the check-box will be an enabled field - all others will be disabled.

Un-checking the check box will enable all the entry fields, which will remain populated with the default values from the customer address.

Clicking '''Save''' will create the Job. If a new customer is being created, the address entered will be assigned to the customer. If a delivery address has been chosen that is different to the selected existing customer (or no customer has been selected), the address will be saved to the Job address.

The following columns will be removed from the grid:
* Site ID
* Job Instructions
* Office Instructions
* Reason Code
* Configure
* Details
* Report

The Status field will be modified to show the Reason Code and Description entered for a cancelled job in a tool-tip (activated by hovering the mouse pointer over the Status).

The grid will be modified to not allow direct entry. Instead, the grid will use the Entry panel. This will be activated by clicking once on the line, which will display the Entry panel, populated with the details of the line selected.

The functionality will differ to the Entry functionality, in that the Action buttons will be populated as follows:
* Details - Display any Container, Product or Service details associated to the job
* Report - Display the POD/POC/Service report (only enabled if the Job is at status Complete
* Cancel Job - Move a Job to Cancelled status.
* Image - Display any Image associated to the Job.

===Containers Screen===
*EPL_GROSS_WEIGHT - Visible against the container record and available for entry.
*EPL_COMMENT - Visible against the container record and available for entry.

===Job Products Screen===

*EPL_UNIT_TYPE - Visible against the product record and available for entry
*EPL_DESCRIPTION_LONG - Visible against the product record and available for entry
*EPL_PRODUCT_QTY_ORDERED - Visible against the product record and available for entry

===Site Maintenance Screen===
*EPL_EMAIL - Visible and editable.

===Job Group Maintenance Screen===

*EPL_CONTAINER_ONLY - Controls container only delivery - Visible and Editable
*EPL_JOB_DISPLAY - controls which element is displayed on the PDA device on the Job Detail screen as the Job Reference. The two options are Job Code or Job ID, defaulting to the latter.

===Transfer Configuration Screen===

A new audit and maintenance screen will be required.

This will allow users to search the EPOD_XF_AUDIT_HEADER table by EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_JOB_GROUP. With a later implementation allowing to search for EPL_JOB_ID, or EPL_LOAD_ID.

This screen will display the header records details, EPL_JOB_GROUP, EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_STATUS_DESCRIPTION, and EPL_REQUEST_DATA.
{{note|This would be best displayed within a popup of some kind. For future implementation, the editing and resending of this data may be needed. Doing so a link would need to be made to each job.
}}

== PDA Server ==

The message sent to the PDA client from the server will be modified so that the Job Address (if present) will be used in preference to the Customer address. The Container Weight field (EPL_GROSS_WEIGHT) must also be passed.

The Standing Data Configuration must be changed to pass the new control flags to the device (e.g. EPL_JOB_DISPLAY).

== PDA Client ==

The DB changes will need to be reflected on the PDA.

The PDA will need to be implemented with the functionality to transfer collection details to the delivery job, based on matching Job Codes. This includes altering the planned delivery quantity to the actual collection quantity specified in the collection.

The PDA will need to display Job Code rather than Job ID on the Job Detail screen, depending on the value of the new configuration flag.

The PDA will need to select the appropriate delivery or collection process based on the jobs attributes:
*Collections
**Proctors-Controlled Warehouse - Collection of Containers without Products
**Non-Proctors Location - Collection of Products without Containers
*Deliveries
**Proctors Collection - Delivery of Containers without Products.
**Non-Proctors Collection - Delivery of Products without Containers

When starting a collection or delivery from a Proctors-Controlled Warehouse a update check must be forced (this is currently handled under the standard process) if no container records are received, then an alert is given to the user advising that the data may not be up to date.

====Standard Collection====
The user will be able to long-press any container in the grid. This will provide a popup menu, allowing the user to see the details of the selected container. The PDA will display a screen displaying:
*ID
*Package Code and Description
*Weight

====Collection of Containers without Products====
This will check a parameter on the Job Group - if Container-only Collection is enabled and there are no loose products, the collection will continue as Container only, otherwise the standard (Products Without Containers) collection process will be used.

The user is presented with a list of Containers for collection. The user selects a container either through text entry or scanning. Users have the ability to short-deliver by container only and use the exception process to document any non-delivered containers. When all Containers are accounted for, the user is prompted to complete the job, with a customer signature.

Long-pressing on a container will display a pop-up menu with a Products option shown. If this is clicked, the PDA client will display a list of all products against the container. {{note}} This option should be available only if this is unit is configured for containers without products.

====Collection of Products without Containers====
The user is presented with a list of products for collection. The user confirms collection of each product as in the standard approach. When all Products are accounted for the user is prompted to complete the job, with a customer signature.

====Delivery of Products without Containers====
The process is the same as Collection of Products without Containers.

====Delivery of Containers without Products====
The process is the same as Collection of Containers without Products.

=== Photos ===
Photos will be captured using the standard exception process. User's must be aware that quality of the images will affect GPRS usage, higher quality equals longer more date to transfer. This can only be controlled on the PDA itself and must be set in the PDA's camera settings.

== New POD formats ==
New POD formats will be created for the operation.

The POD or POC format produced will be dependant on the Job Group associated to the Job.

All images captured relating to the Job will be displayed on a second page of the POD/POC document, with the associated detail information (Job ID, Container ID, Product Code, Image description). Again image quality is dependant on device settings, which affects the image size.

Fields on the Delivery Note document will be sourced from the following database fields:
* Delivery Note: EPL_JOB_CODE
* Customer Address: Address information from the Job's Customer
* Delivery Address: Address information from the Job's Address (if present) or the Customer's.
* Customer Tel No: From the Job's Address (if present) or the Customer.
* Cust No/Contact: From the Job's Address (if present) or the Customer.
* Our Order No: EPL_SO_NUMBER (New field)
* Order Date: EPL_ORDER_DATE (New Field)
* Customer Order No: EPL_CUST_REF
* PPB Contact: EPL_SALES_CONTACT (New Field)
* Product Reference: EPL_PRODUCT_CODE
* Product Description: EPL_DESCRIPTION and EPL_DESCRIPTION_LONG
* Due Date: EPL_START_PLANNED_DATE/TIME {{Note}} This is the same for all lines.
* Unit: EPL_UNIT_TYPE (New Field)
* Quantity: EPL_PRODUCT_QTY_ORDERED (New Field)
* Quantity Despatched: EPL_PRODUCT_QTY_PLANNED
* Quantity Delivered: EPL_PRODUCT_QTY_ACTUAL
* No Of Parcels: EPL_COMMENT of EPOD_CONTAINER (New field)
* Pallet ID: EPL_CONTAINER_ID
* Special Instructions: EPL_JOB_INSTRUCTION
* Total Weight: See below
* Delivered By: PDA User Name
* Print Name: EPL_CUST_SIGNATORY (entered by PDA user)
* Date: Job Completion Date
* Signed Unchecked: EPL_SIGNED_UNCHECKED (New Field)

Total Weight will be calculated at the container level. The weight must be passed through as part of the interfaced container record. If no containers have been interfaced, this field will be omitted.

{{Warning}}The following elements have been excluded from the design:
* Barcode
* Vat No
* Picked
* Converted

Fields on the Transfer Note document will be sourced from the following database fields (where different from the Delivery Note):
* Stock Transfer Note: EPL_JOB_CODE
* Transfer Stock From: From the Collection's Customer information
* Transfer Stock To: From the Delivery's Customer information
* Xfer Ref No: EPL_SO_NUMBER (New Field)
* Input By: EPL_SALES_CONTACT (New Field)
* Part Number: EPL_PRODUCT_ID
* Product Description: EPL_DESCRIPTION

{{Warning}}The following elements have been excluded from the design:
* Location
* Location Qty

{{Note}} The existing generic POD/POC format must be modified to check for the Job address before using the Customer's address.

{{Note}} There could be many pallets and stock codes on a collection or delivery. This will run into multiple pages regardless of which note is produced. In the case where multiple pages of information are displayed, the header, up to and including the ''Customer Tel No'' table, will be shown on every page, whereas the Signature footer table will be shown only on the first page, being omitted from all subsequent pages.

==PDF Production==
A new rule will be added at a Site level to control whether emails to customers will be HTML-Embedded or PDF attachment style.

The system will check this rule when:
# The "Email To" button is pressed on the "View POD" page
# auto-emailed documents are being produced.

If this rule is not enabled, the system will send emails as now (embedded HTML emails).

If this rule is enabled, the system will:
*Export and save the page to a temporary directory, with all images rendered.
*Run the saved page through a conversion routine to convert the HTML to a PDF page (saved in the same directory).
*Attach this generated PDF to the email and send
*Delete the temporary folder.

The conversion routine will use the WkHtmlToPDF program with default parameters - this must be installed on the server.

==Auto-Email==
The Auto-email code will be moved into the new batch Auto-Export Process.

The update of a job to complete or cancelled will result in the new field EPL_EMAIL_FLAG being set to "N". The batch process will retrieve all job records where this flag is "N" and the Job Group or Site associated to the job requires auto-email.

The process will iterate through these records and retrieve the email addresses that the job should be emailed to from the Site, Job and Customer records.

If no emails have been specified, EPL_EMAIL_FLAG will set to "X".

If an email address has been specified, the email will be built as per the current process and sent to the defined email address. EPL_EMAIL_FLAG will set to "Y".



= Appendix A: POD Formats =
[[File:Delivery Note.jpg|600px|border]]

[[File:Stock Transfer Note.jpg|600px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|REQ=0
|EST=0
|FS=5.0
|TS=0
|DEV=36
|ST=5.00
|IMP=2.0
|Client={{#var:Client}}
|Year=2012
|FSEST=N
|Rev1=Matt Turner
|Rev1Title=OBS Representative
|Rev2=Stephen McCartney
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 297001 Prolog EPOD Modifications

2012-03-01T14:36:27Z

Milesl: v0.4 Version updated

<div class="noprint">
{{#vardefine:Client|PROL}}
{{#vardefine:ClientName|PROLOG}}
{{#vardefine:System|''CALIDUS'' EPOD}}
{{#vardefine:Doc_Title|Prolog EPOD Modifications}}
{{#vardefine:Version|0.4}}
{{#vardefine:Date|1st March 2012}}
{{#vardefine:Reference|297001}}
{{#vardefine:Year|2012}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}


<div class="noprint">
= Functional Overview =
There will be 35 PDA users and 5 Admin users hosted by the Prolog system.

There are expected to be 35 loads per day.

There are expected to be approximately 10 jobs per load.

There are expected to be up to 52 containers/products per load.

There will be 3 job groups, allocated to each Depot.

== Client Requirement ==
The client requires an implementation of the {{#var:System}} system, following the functionality as described below.

== Solution Overview ==
===Import Data===
Import and Export of Jobs and Loads will be through the existing standard Web Services.

The Job Group field will identify the depot from which the Job originates.

An Owner field added to the Job import, to allow the client system to specify Prolog's Client (e.g. Britvic).

The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).

Delivery jobs will be sent with one container record and multiple product records. The container record will be provided with a description of the required pallets and weight (for example, "2 Pallets / 174.0 Kg"). All products associated to the job will be added to this container, detailing the product code, description and quantity.

Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.

Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job.

The Load import includes the Driver assigned to the Load.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.

===PDA Log-on===
Each Driver will have a PDA with the ''CALIDUS'' EPOD system installed and configured on it. The user will log in with a User ID and password provided to them, and a Vehicle ID, chosen from a list.

===Vehicle Checks===
If the vehicle being used has not been checked recently, the unit will direct the user to complete the Vehicle Checks. The data entry and checks here are configurable within the Admin system. The checks required will be sent to OBS so that they can configure the checks required at this stage.

===Metrics===
Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point.

{{note}} The user will also be prompted to enter the mileage once all jobs on the load are complete.

The user will then be shown a list all the jobs on the load that has been assigned to the user. The jobs are displayed in the order in which they should be completed. However, the jobs can be completed in any sequence by clicking the line of the job required to to be completed first and then clicking the '''OK''' button. The user will then be taken to the Job Details page, which displays the full details of the job being undertaken.
The screen has several Tabs, each showing:
* The Job Type (Collection, Delivery, Service)
* The customer details (Customer Code, Name, Address and Postcode)
* The contact information (Contact name and number)
* The Instructions for the job
From these tabs, the user can:
* Call the customer by clicking on the '''Call''' button.
* Navigate to the customer's address by clicking on the '''Navigate''' button.

Again, here the user can choose which job to complete by using the supplied left and right buttons or start a job with the '''OK''' button, when either a Collection or Delivery process will begin.

{{Note}} The job can be cancelled at this stage by clicking the '''Cancel''' button. The unit will take to the user to an Exception screen and prompt them to enter a reason code explaining why this job was cancelled. See the Exception process for more information.

===Collection Process===
For collections, the user will be shown instructions for the job, with a list of all required products and quantities to collect.

If the collection is successful with no changes, the user will click the '''OK''' button to confirm this and be taken to the Confirmation process.

If nothing can be collected, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the collection, the user will click the '''Notes''' tab and enter details on the adjustment to the collection. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

===Delivery Process===
Deliveries (from Depots to Customers) will be configured to ensure that the PDA unit only requires the user to confirm containers rather than individual products, as follows:

The user will be shown a list of containers only. The description on here will display the number of pallets.

By long-clicking on the container, the user can view a list of all the products in this container.

If all has been delivered successfully, the user will click the '''Collected''' button and be taken to the Confirmation process.

If nothing can be delivered, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the delivery, the user will click the '''Notes''' tab and enter details on the adjustment to the delivery. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

Deliveries (from a supplier to a customer direct) will not follow this process, as no container or product details will have been provided on the job. The Notes information from the collection will have been automatically updated onto the associated delivery, so the user will be able to see what was collected. The user will be able to confirm the delivery with the '''OK''' button, cancel the delivery through the '''Cancel''' button and amend the notes as above.

===Exception Process===
This screen will be displayed if the user is cancelling an entire job, as described in the previous sections.

When cancelling a Job, the user is asked to enter a reason for the cancellation or shortage. These reasons are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system.

If necessary, the user can capture an image to support this reason, by clicking the '''Image''' button. The user can then use the device's camera to capture an image. When complete, the user will exit and will be allowed to view the captured image and add a note to the image to explain.

Once the exception is complete, the user will be returned to the job list, to complete the next job.

===Confirmation Process===
The expected configuration for both Collections and Deliveries will be that the user will be prompted to sign for the job, then the customer will be asked to sign for this also.

The Name defaults to the customer contact name (if present on the job) and allows the user to change this.

Once completed, The user will be returned to the Job Menu to pick up the next task.

The completed job will be transferred back to the main ''CALIDUS'' EPOD system with all the details, signatures and photos.

Once all jobs are completed on that load, the user will be prompted to enter the mileage of the vehicle when they have returned to base. This and the starting mileage will be sent back to the main ''CALIDUS'' EPOD system.

===Export Data===
When data is sent back to the server for jobs completed or cancelled, the server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All jobs completed in this manner will be forwarded on to a configured Web Service within the client host system, in the standard ''CALIDUS'' EPOD format.

When metric data is sent back for the Load, this will be stored in the ''CALIDUS'' EPOD database. The server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All loads completed in this manner will be forwarded on to a configured Web Service within the client host system, in the new format created for this purpose.

===Completion Documents (POD/POC)===
This automated process will also create the Completion documents in PDF format and email them to a central email address, configured against the site in ''CALIDUS'' EPOD.

A document will be generated for every collection and delivery completed (i.e. not cancelled).

The format for both collections and deliveries will be the same and will match the current documentation.

The data held within the bar code is a unique reference to the consignment matching the data in the host system. This data will be displayed instead of the barcode. The 'Consignment Number' will be passed to ePOD as the EPL_CUST_REF.

===Data Clear-down===
A data clear-down script will be written and scheduled to run on the host server. This will check the job and image data files and clear down any records older than a specific date.

{{Note}} If this is hosted at OBS, the responsibility of creating and running this script will be OBS'. If hosted by the client, this will be the responsibility of the client.

===Admin Screens===
The Admin Users will be provided log-ons - these will be manually created within the Admin system itself. Each log-on can be configured to see all Job Groups (Depots) or a selection of job groups only.

These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.

No changes need to be made within the Administration screen in the ''CALIDUS'' EPOD system, as both the entered Notes and advised Owner can be seen when viewing the completion document within the Admin system.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.

== Scope ==
The developments will take place against the latest version of the EPOD system (1.2.X)

The described process flow requires functionality currently being developed, as follows:
* Auto-Email
* PDF Completion Reports
* Auto-Export
* Site Email Address
* Container-only Delivery
* Change Job Identifier on PDA


= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
A Site will be generated. This will be agreed in advance, but is expected to be "PROLOG". This is generated and maintained through the Site Admin screen.
*Automatic Email of POD to a Site email address will be enabled from this screen, by entering a Site email address.
*PDF Production will be enabled from this screen.
*Automatic Export of data will be configured through the Transfer Configuration assigned to the Site record. The Transfer Configuration ID can be maintained through the Transfer Configuration screens. Configuration of both the Load and Job exports will be required.

A Job Group will be set up for each Depot, through the Job Group Admin screen.
*The format for both collections and deliveries will be set to "Prolog" against each Job Group, from the Job Groups screen.
*The expected configuration for both Collections and Deliveries will be that the user will be prompted to sign for the job, then the customer will be asked to sign for this also. This will be through the configuration flags EPL_DEL_DRIVER_SIGN and EPL_COL_DRIVER_SIGN against the EPOD_JOB_GROUP records. These can be configured through the Job Group Config screen, accessible from the Job Groups screen.
*The PDA will not prompt for confirmation of Products at delivery if it has them - this is controlled by setting the "Delivery without Products" flag against each Job Group, maintained in the Job Group screen.
*The PDA will be configured to display the Job Code on the Job Detail screen as the Job Reference, rather than the Job ID. If the system is generating IDs for the received jobs, this should be done. This can be completed through the Job Groups admin screen.
*Metrics entry of mileage information at the start and end of a Load will be enabled.
*Entry of Notes information at the end of a Job will be enabled.

A Customer record will be set up for each of the Job Groups, with the same ID as the Job Groups. This address of these customer records will be used to identify the Depot Address on the documentation.

Reason Codes will be set up as agreed between the host system and ''CALIDUS'' EPOD. These are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system

= Functional Description =
The following areas will require modification:
*Database fields
*Import
**Job
**Load
*Pass new configuration to PDA
*Job Assignation by Vehicle
*Metric Entry
*Load Update from PDA to Server
*Add Notes tab to Collection and Delivery
*Add Notes to Job Update
*Add Notes to Job Export data
*Add Load Auto-Export
*POD/POC Formats
*Data Cleardown

==Database Fields==
New fields will be added to the EPOD_JOB table:
*EPL_USER_NOTES - a Max length text field
*EPL_OWNER_NAME - a 30-character text field

New fields will be added to the EPOD_LOAD table
*EPL_MILEAGE_START - an integer field
*EPL_MILEAGE_END - an integer field
*EPL_XFER_FLAG - a Y/N flag to control whether the load has been exported yet.

New Configuration fields will be added to EPOD_JOB_GROUP and EPOD_SITE:
*EPL_METRIC_ENTRY - a Y/N flag to control entry of mileage information at the start and end of a Load.
*EPL_NOTES - a Y/N flag to control entry of Notes information at the end of a Job.

A new field will be added to EPOD_XF_CONFIG:
*EPL_XF_ID - a 20-character ID field.
The index will be modified to add this field.

Values in this field will be:
*JOB - A configuration set for JOB updates
*LOAD - A configuration set for LOAD updates

==Import Data==
Import and Export of Jobs and Loads will be through the existing standard Web Services.

===Job===
An Owner field added to the Job import, to allow the client system to specify the Depot (e.g. Britvic).

The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).

Delivery jobs will be sent with one container record and multiple product records. The container record will be provided with a description of the required pallets and weight (for example, "2 Pallets / 174.0 Kg"). All products associated to the job will be added to this container, detailing the product code, description and quantity.

Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.

Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job.

<PRE>
<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>00067527</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>00067527</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_002</EPL_JOB_CODE>
<EPL_CUST_REF>00067523</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE></EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>2 Pallets / 174.0Kg</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>
</PRE>
Notes:
*EPL_SITE_ID will be mapped to the single company site ID - this is suggested to be "PROLOG"
*EPL_JOB_GROUP will be the originating Depot ID (e.g. "SHEFFIELD"). These will be pre-set and agreed in advance.
*EPL_JOB_ID (10 characters) is a unique reference for the individual job (collection or delivery). For linked collections and deliveries, each job should have a unique EPL_JOB_ID, but the same EPL_JOB_CODE. If left blank, this will be generated by the system. This will be mapped to the unique value of the currently used barcode.
*EPL_JOB_CODE (20 characters) will be any reference that ties linked jobs together.
*An additional reference can be mapped to EPL_CUST_REF (30 characters). This will map to the consignment number.
*The customer code, name, contact and address information will be mapped to the appropriate fields.
*EPL_CONTAINER_ID (15 characters) will be the Order Reference.
*EPL_CONTAINER_PACKAGE_DESC (40 characters) will contain the text showing the total pallets and weight.
*The product code, description and quantity will be mapped to the appropriate product tags

===Load===
Loads can be imported separately or the jobs can be included within the EPOD_JOBS tag.

The Load import includes the Driver and Vehicle assigned to the Load.

{{warning}} Currently the client system allocates jobs to a Vehicle, not a Driver, whilst ''CALIDUS'' EPOD assigns by the User ID (the Driver). In the requirements meeting, did we decide which will be changed, EPOD or Transport system?

<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPL_VEHICLE_ID>AB12XYZ</EPL_VEHICLE_ID>
<EPOD_JOBS>
...
</EPOD_JOBS>
</EPOD_LOAD>
<EPOD_LOAD>
...
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

==Pass new Configuration to PDA==
Each Driver will have a PDA with the ''CALIDUS'' EPOD system installed and configured on it. The user will log in with a User ID and password provided to them, and a Vehicle ID, chosen from a list.

The server responds with a Logon Response, passing all the configuration and standing data to the device. The configuration will be modified to include the new configuration elements against the Site and Job Group. The PDA will store this configuration.

==Metric Entry==
Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point. This will be though a form to enter the mileage in numeric form.

This form will be shown once all jobs are complete against a Load, to enter the mileage at end of the full trip. This will default to the first mileage entered. A prompt at this atge will say "Load Completed. Return to Base, then enter Mileage".

==Load Update from PDA to Server==
Both of the entry items will be sent back to the Server on a new Load Update message, showing that the load is now complete.

The Server will action this message and store the mileage values on the message onto the new fields in the database against the load.

{{Note}} The Actual Distance value against the load will be calculated and stored here as well, by taking the start mileage value from the end mileage. If the value results in a negative value, this will be saved as 0 miles, as the user has made an error inputting the mileage information.

If the Site has been configured for transmitting Load data back to the host system, the Load record's EPL_XFER_FLAG will be marked as "N", to indicate that the record has not yet been transmitted, otherwise this will be set to "".

==Add Notes tab to Collection and Delivery==
A new tab will be added to the Collection and Delivery process, if the system has been configured to do so through the new EPL_NOTES configuration element. The note field will allow free-text entry by the user.

The tab will be added as the last tab on each screen. The unit will function as follows:

===Collection Process===
For collections, the user will be shown instructions for the job, with a list of all required products and quantities to collect in the instructions field.

If the collection is successful with no changes, the user will click the '''OK''' button to confirm this and be taken to the Confirmation process.

If nothing can be collected, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the collection, the user will click the '''Notes''' tab and enter details on the adjustment to the collection. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

===Delivery Process===
Deliveries (from Depots to Customers) will be configured to ensure that the PDA unit only requires the user to confirm containers rather than individual products (through the existing configuration flag EPL_CONTAINER_ONLY), as follows:

The user will be shown a list of containers only. The description on here will display the number of pallets.

By long-clicking on the container, the user can view a list of all the products in this container.

If all has been delivered successfully, the user will click the '''Collected''' button and be taken to the Confirmation process.

If nothing can be delivered, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the delivery, the user will click the '''Notes''' tab and enter details on the adjustment to the delivery. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

Deliveries (from a supplier to a customer direct) will not follow this process, as no container or product details will have been provided on the job. The Notes information from the collection will have been automatically updated onto the associated delivery, so the user will be able to see what was collected. The user will be able to confirm the delivery with the '''OK''' button, cancel the delivery through the '''Cancel''' button and amend the notes as above.

==Add Notes to Job Update==
When a job is complete (confirmed or cancelled) the PDA sends the job update back to the server, which will complete the job as per normal processing.

The Job Update message must be modified to pass back the Notes data entered above.

{{Note}} If the job being updated is a collection and there are any deliveries with the same Job Code, the PDA unit will update the linked job on the device with the notes from the collection.

==Add Notes to Job Export data==
When data is sent back to the server for jobs completed or cancelled, the server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All jobs completed in this manner will be forwarded on to a configured Web Service within the client host system, in the standard ''CALIDUS'' EPOD format.

The format will be changed to include the Notes field, as in the example below:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE></EPL_JOB_CODE>
<EPL_CUST_REF>00067523</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPL_NOTES>Any user-entered notes here</EPL_NOTES>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

{{Note}} Other elements may be included but will contain no data - these may be ignored.

==Load Auto-Export==
The Load Export schema will be modified as in the following example:
<EPL_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL_LOAD_END_PLANNED_TIME>00000000</EPL_LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_MILEAGE_START>0</EPL_MILEAGE_START>
<EPL_MILEAGE_END>0</EPL_MILEAGE_END>
<EPL_USER_ID>MATT</EPL_USER_ID>
</EPL_LOAD>

The Auto-Export process will be modified to add Load export, if configured against the Site or Job Group's EPOD_XF_CONFIG.

The process will be similar to the Job Export - all Loads will be checked if they are required to be exported (through the new EPL_XFER_FLAG against the Load) and a configuration exists for that site or job group. If found, these Load Exports will be sent to the client via the required method (again on the Config table)

==Completion Documents (POD/POC)==
This automated process will also create the Completion documents in PDF format and email them to a central email address, configured against the site in ''CALIDUS'' EPOD.

A document will be generated for every collection and delivery completed (i.e. not cancelled).

The format for both collections and deliveries will be the same and will match the current documentation, shown in [[#Appendix A: POD Formats]]. The format will be created with a name of "Prolog" and this will be able to be chosen as an option from the Delivery and Collection Formats against the Job Group.

The data will be mapped as follows:
*'''From''': The Name will come from the new EPL_OWNER field on EPOD_JOB. The address information will come from the customer address with the same ID as EPL_JOB_GROUP of EPOD_JOB.
*'''Delivery Instructions''': EPL_JOB_INSTRUCTION of EPOD_JOB
*'''Customer''': The Code will be EPL_CUSTOMER_CODE of EPOD_JOB. The address will be taken from this customer's EPOD_CUSTOMER record.
*'''"2 Pallets / 162 Kg"''': EPL_CONTAINER_PACKAGE_DESC of EPOD_CONTAINER
*'''Order Reference''': EPL_CONTAINER_ID of EPOD_CONTAINER
*'''Order Processed''': EPL_START_ACTUAL_DATE of EPOD_JOB
*'''Reference''': EPL_PRODUCT_CODE of EPOD_PRODUCT
*'''Description''': EPL_DESCRIPTION of EPOD_PRODUCT
*'''Qty''': EPL_PRODUCT_QTY_ACTUAL of EPOD_PRODUCT
*'''Signature''': EPL_JOB_SIGNATURE of EPOD_JOB
*'''Block Print''': EPL_CUST_SIGNATORY of EPOD_JOB
*'''Date''': EPL_END_ACTUAL_DATE of EPOD_JOB
*'''Time''': EPL_END_ACTUAL_TIME of EPOD_JOB
*'''Notes''': EPL_NOTES of EPOD_JOB {{Note}} New Field
*'''Consignment Barcode''': {{Warning}} is this required? If so, from what data?
*'''"SM0425 00000 00113306"''': {{Warning}} is this required? If so, from what data?
{{warning}} The data contained in the barcode is not the number above - what is this?

==Data Clear-down==
A data clear-down script will be written and scheduled to run on the host server. This will check the job and image data files and clear down any records older than a specific date.

{{Note}} If this is hosted at OBS, the responsibility of creating and running this script will be OBS'. If hosted by the client, this will be the responsibility of the client.

The process should receive parameters specifying:
*The database connection.
*The Number of Days Transactional Data to keep.
*The Number of Days Image Data to keep.
*The Number of Days Signature Data to keep.

==Admin Screens==
The Admin Users will be provided log-ons - these will be manually created within the Admin system itself. Each log-on can be configured to see all Job Groups (Depots) or a selection of job groups only.

These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.

The Job Group screen will require modification, to add the new configuration flags (detailed in section [[#Database Fields|Database Fields]]

The Load screen will be modified to add a mouse-over tool-tip, displaying the start and end vehicle mileage.

The File Transfer Configuration screens will be modified to allow users to set up multiple configurations against a EPL_XF_CONFIG_ID, for each EPL_XF_ID.

No further changes need to be made within the Administration screen in the ''CALIDUS'' EPOD system, as both the entered Notes and advised Owner can be seen when viewing the completion document within the Admin system.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.



= Appendix A: POD Formats =
[[File:297001-DeliveryNote.jpg|700px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|Ref1=UG 291094 EPOD Admin User Guide
|RefV1=1.0
|RefDate1=6/10/2011
|Ref2=UG 291097 EPOD Client User Guide
|RefV2=1.0
|RefDate2=6/10/2011
|REQ=0
|EST=0
|FS=2
|TS=0
|DEV=16
|ST=5
|IMP=0
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=N
|Rev1=Tony Walker
|Rev1Title=Consultant
|Rev2=Matt Turner
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 297001 Prolog EPOD Modifications

2012-03-01T14:35:55Z

Milesl: Removed Job assignment by vehicle

<div class="noprint">
{{#vardefine:Client|PROL}}
{{#vardefine:ClientName|PROLOG}}
{{#vardefine:System|''CALIDUS'' EPOD}}
{{#vardefine:Doc_Title|Prolog EPOD Modifications}}
{{#vardefine:Version|0.3}}
{{#vardefine:Date|1st March 2012}}
{{#vardefine:Reference|297001}}
{{#vardefine:Year|2012}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}


<div class="noprint">
= Functional Overview =
There will be 35 PDA users and 5 Admin users hosted by the Prolog system.

There are expected to be 35 loads per day.

There are expected to be approximately 10 jobs per load.

There are expected to be up to 52 containers/products per load.

There will be 3 job groups, allocated to each Depot.

== Client Requirement ==
The client requires an implementation of the {{#var:System}} system, following the functionality as described below.

== Solution Overview ==
===Import Data===
Import and Export of Jobs and Loads will be through the existing standard Web Services.

The Job Group field will identify the depot from which the Job originates.

An Owner field added to the Job import, to allow the client system to specify Prolog's Client (e.g. Britvic).

The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).

Delivery jobs will be sent with one container record and multiple product records. The container record will be provided with a description of the required pallets and weight (for example, "2 Pallets / 174.0 Kg"). All products associated to the job will be added to this container, detailing the product code, description and quantity.

Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.

Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job.

The Load import includes the Driver assigned to the Load.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.

===PDA Log-on===
Each Driver will have a PDA with the ''CALIDUS'' EPOD system installed and configured on it. The user will log in with a User ID and password provided to them, and a Vehicle ID, chosen from a list.

===Vehicle Checks===
If the vehicle being used has not been checked recently, the unit will direct the user to complete the Vehicle Checks. The data entry and checks here are configurable within the Admin system. The checks required will be sent to OBS so that they can configure the checks required at this stage.

===Metrics===
Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point.

{{note}} The user will also be prompted to enter the mileage once all jobs on the load are complete.

The user will then be shown a list all the jobs on the load that has been assigned to the user. The jobs are displayed in the order in which they should be completed. However, the jobs can be completed in any sequence by clicking the line of the job required to to be completed first and then clicking the '''OK''' button. The user will then be taken to the Job Details page, which displays the full details of the job being undertaken.
The screen has several Tabs, each showing:
* The Job Type (Collection, Delivery, Service)
* The customer details (Customer Code, Name, Address and Postcode)
* The contact information (Contact name and number)
* The Instructions for the job
From these tabs, the user can:
* Call the customer by clicking on the '''Call''' button.
* Navigate to the customer's address by clicking on the '''Navigate''' button.

Again, here the user can choose which job to complete by using the supplied left and right buttons or start a job with the '''OK''' button, when either a Collection or Delivery process will begin.

{{Note}} The job can be cancelled at this stage by clicking the '''Cancel''' button. The unit will take to the user to an Exception screen and prompt them to enter a reason code explaining why this job was cancelled. See the Exception process for more information.

===Collection Process===
For collections, the user will be shown instructions for the job, with a list of all required products and quantities to collect.

If the collection is successful with no changes, the user will click the '''OK''' button to confirm this and be taken to the Confirmation process.

If nothing can be collected, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the collection, the user will click the '''Notes''' tab and enter details on the adjustment to the collection. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

===Delivery Process===
Deliveries (from Depots to Customers) will be configured to ensure that the PDA unit only requires the user to confirm containers rather than individual products, as follows:

The user will be shown a list of containers only. The description on here will display the number of pallets.

By long-clicking on the container, the user can view a list of all the products in this container.

If all has been delivered successfully, the user will click the '''Collected''' button and be taken to the Confirmation process.

If nothing can be delivered, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the delivery, the user will click the '''Notes''' tab and enter details on the adjustment to the delivery. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

Deliveries (from a supplier to a customer direct) will not follow this process, as no container or product details will have been provided on the job. The Notes information from the collection will have been automatically updated onto the associated delivery, so the user will be able to see what was collected. The user will be able to confirm the delivery with the '''OK''' button, cancel the delivery through the '''Cancel''' button and amend the notes as above.

===Exception Process===
This screen will be displayed if the user is cancelling an entire job, as described in the previous sections.

When cancelling a Job, the user is asked to enter a reason for the cancellation or shortage. These reasons are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system.

If necessary, the user can capture an image to support this reason, by clicking the '''Image''' button. The user can then use the device's camera to capture an image. When complete, the user will exit and will be allowed to view the captured image and add a note to the image to explain.

Once the exception is complete, the user will be returned to the job list, to complete the next job.

===Confirmation Process===
The expected configuration for both Collections and Deliveries will be that the user will be prompted to sign for the job, then the customer will be asked to sign for this also.

The Name defaults to the customer contact name (if present on the job) and allows the user to change this.

Once completed, The user will be returned to the Job Menu to pick up the next task.

The completed job will be transferred back to the main ''CALIDUS'' EPOD system with all the details, signatures and photos.

Once all jobs are completed on that load, the user will be prompted to enter the mileage of the vehicle when they have returned to base. This and the starting mileage will be sent back to the main ''CALIDUS'' EPOD system.

===Export Data===
When data is sent back to the server for jobs completed or cancelled, the server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All jobs completed in this manner will be forwarded on to a configured Web Service within the client host system, in the standard ''CALIDUS'' EPOD format.

When metric data is sent back for the Load, this will be stored in the ''CALIDUS'' EPOD database. The server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All loads completed in this manner will be forwarded on to a configured Web Service within the client host system, in the new format created for this purpose.

===Completion Documents (POD/POC)===
This automated process will also create the Completion documents in PDF format and email them to a central email address, configured against the site in ''CALIDUS'' EPOD.

A document will be generated for every collection and delivery completed (i.e. not cancelled).

The format for both collections and deliveries will be the same and will match the current documentation.

The data held within the bar code is a unique reference to the consignment matching the data in the host system. This data will be displayed instead of the barcode. The 'Consignment Number' will be passed to ePOD as the EPL_CUST_REF.

===Data Clear-down===
A data clear-down script will be written and scheduled to run on the host server. This will check the job and image data files and clear down any records older than a specific date.

{{Note}} If this is hosted at OBS, the responsibility of creating and running this script will be OBS'. If hosted by the client, this will be the responsibility of the client.

===Admin Screens===
The Admin Users will be provided log-ons - these will be manually created within the Admin system itself. Each log-on can be configured to see all Job Groups (Depots) or a selection of job groups only.

These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.

No changes need to be made within the Administration screen in the ''CALIDUS'' EPOD system, as both the entered Notes and advised Owner can be seen when viewing the completion document within the Admin system.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.

== Scope ==
The developments will take place against the latest version of the EPOD system (1.2.X)

The described process flow requires functionality currently being developed, as follows:
* Auto-Email
* PDF Completion Reports
* Auto-Export
* Site Email Address
* Container-only Delivery
* Change Job Identifier on PDA


= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
A Site will be generated. This will be agreed in advance, but is expected to be "PROLOG". This is generated and maintained through the Site Admin screen.
*Automatic Email of POD to a Site email address will be enabled from this screen, by entering a Site email address.
*PDF Production will be enabled from this screen.
*Automatic Export of data will be configured through the Transfer Configuration assigned to the Site record. The Transfer Configuration ID can be maintained through the Transfer Configuration screens. Configuration of both the Load and Job exports will be required.

A Job Group will be set up for each Depot, through the Job Group Admin screen.
*The format for both collections and deliveries will be set to "Prolog" against each Job Group, from the Job Groups screen.
*The expected configuration for both Collections and Deliveries will be that the user will be prompted to sign for the job, then the customer will be asked to sign for this also. This will be through the configuration flags EPL_DEL_DRIVER_SIGN and EPL_COL_DRIVER_SIGN against the EPOD_JOB_GROUP records. These can be configured through the Job Group Config screen, accessible from the Job Groups screen.
*The PDA will not prompt for confirmation of Products at delivery if it has them - this is controlled by setting the "Delivery without Products" flag against each Job Group, maintained in the Job Group screen.
*The PDA will be configured to display the Job Code on the Job Detail screen as the Job Reference, rather than the Job ID. If the system is generating IDs for the received jobs, this should be done. This can be completed through the Job Groups admin screen.
*Metrics entry of mileage information at the start and end of a Load will be enabled.
*Entry of Notes information at the end of a Job will be enabled.

A Customer record will be set up for each of the Job Groups, with the same ID as the Job Groups. This address of these customer records will be used to identify the Depot Address on the documentation.

Reason Codes will be set up as agreed between the host system and ''CALIDUS'' EPOD. These are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system

= Functional Description =
The following areas will require modification:
*Database fields
*Import
**Job
**Load
*Pass new configuration to PDA
*Job Assignation by Vehicle
*Metric Entry
*Load Update from PDA to Server
*Add Notes tab to Collection and Delivery
*Add Notes to Job Update
*Add Notes to Job Export data
*Add Load Auto-Export
*POD/POC Formats
*Data Cleardown

==Database Fields==
New fields will be added to the EPOD_JOB table:
*EPL_USER_NOTES - a Max length text field
*EPL_OWNER_NAME - a 30-character text field

New fields will be added to the EPOD_LOAD table
*EPL_MILEAGE_START - an integer field
*EPL_MILEAGE_END - an integer field
*EPL_XFER_FLAG - a Y/N flag to control whether the load has been exported yet.

New Configuration fields will be added to EPOD_JOB_GROUP and EPOD_SITE:
*EPL_METRIC_ENTRY - a Y/N flag to control entry of mileage information at the start and end of a Load.
*EPL_NOTES - a Y/N flag to control entry of Notes information at the end of a Job.

A new field will be added to EPOD_XF_CONFIG:
*EPL_XF_ID - a 20-character ID field.
The index will be modified to add this field.

Values in this field will be:
*JOB - A configuration set for JOB updates
*LOAD - A configuration set for LOAD updates

==Import Data==
Import and Export of Jobs and Loads will be through the existing standard Web Services.

===Job===
An Owner field added to the Job import, to allow the client system to specify the Depot (e.g. Britvic).

The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).

Delivery jobs will be sent with one container record and multiple product records. The container record will be provided with a description of the required pallets and weight (for example, "2 Pallets / 174.0 Kg"). All products associated to the job will be added to this container, detailing the product code, description and quantity.

Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.

Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job.

<PRE>
<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>00067527</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>00067527</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_002</EPL_JOB_CODE>
<EPL_CUST_REF>00067523</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE></EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>2 Pallets / 174.0Kg</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>
</PRE>
Notes:
*EPL_SITE_ID will be mapped to the single company site ID - this is suggested to be "PROLOG"
*EPL_JOB_GROUP will be the originating Depot ID (e.g. "SHEFFIELD"). These will be pre-set and agreed in advance.
*EPL_JOB_ID (10 characters) is a unique reference for the individual job (collection or delivery). For linked collections and deliveries, each job should have a unique EPL_JOB_ID, but the same EPL_JOB_CODE. If left blank, this will be generated by the system. This will be mapped to the unique value of the currently used barcode.
*EPL_JOB_CODE (20 characters) will be any reference that ties linked jobs together.
*An additional reference can be mapped to EPL_CUST_REF (30 characters). This will map to the consignment number.
*The customer code, name, contact and address information will be mapped to the appropriate fields.
*EPL_CONTAINER_ID (15 characters) will be the Order Reference.
*EPL_CONTAINER_PACKAGE_DESC (40 characters) will contain the text showing the total pallets and weight.
*The product code, description and quantity will be mapped to the appropriate product tags

===Load===
Loads can be imported separately or the jobs can be included within the EPOD_JOBS tag.

The Load import includes the Driver and Vehicle assigned to the Load.

{{warning}} Currently the client system allocates jobs to a Vehicle, not a Driver, whilst ''CALIDUS'' EPOD assigns by the User ID (the Driver). In the requirements meeting, did we decide which will be changed, EPOD or Transport system?

<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPL_VEHICLE_ID>AB12XYZ</EPL_VEHICLE_ID>
<EPOD_JOBS>
...
</EPOD_JOBS>
</EPOD_LOAD>
<EPOD_LOAD>
...
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

==Pass new Configuration to PDA==
Each Driver will have a PDA with the ''CALIDUS'' EPOD system installed and configured on it. The user will log in with a User ID and password provided to them, and a Vehicle ID, chosen from a list.

The server responds with a Logon Response, passing all the configuration and standing data to the device. The configuration will be modified to include the new configuration elements against the Site and Job Group. The PDA will store this configuration.

==Metric Entry==
Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point. This will be though a form to enter the mileage in numeric form.

This form will be shown once all jobs are complete against a Load, to enter the mileage at end of the full trip. This will default to the first mileage entered. A prompt at this atge will say "Load Completed. Return to Base, then enter Mileage".

==Load Update from PDA to Server==
Both of the entry items will be sent back to the Server on a new Load Update message, showing that the load is now complete.

The Server will action this message and store the mileage values on the message onto the new fields in the database against the load.

{{Note}} The Actual Distance value against the load will be calculated and stored here as well, by taking the start mileage value from the end mileage. If the value results in a negative value, this will be saved as 0 miles, as the user has made an error inputting the mileage information.

If the Site has been configured for transmitting Load data back to the host system, the Load record's EPL_XFER_FLAG will be marked as "N", to indicate that the record has not yet been transmitted, otherwise this will be set to "".

==Add Notes tab to Collection and Delivery==
A new tab will be added to the Collection and Delivery process, if the system has been configured to do so through the new EPL_NOTES configuration element. The note field will allow free-text entry by the user.

The tab will be added as the last tab on each screen. The unit will function as follows:

===Collection Process===
For collections, the user will be shown instructions for the job, with a list of all required products and quantities to collect in the instructions field.

If the collection is successful with no changes, the user will click the '''OK''' button to confirm this and be taken to the Confirmation process.

If nothing can be collected, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the collection, the user will click the '''Notes''' tab and enter details on the adjustment to the collection. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

===Delivery Process===
Deliveries (from Depots to Customers) will be configured to ensure that the PDA unit only requires the user to confirm containers rather than individual products (through the existing configuration flag EPL_CONTAINER_ONLY), as follows:

The user will be shown a list of containers only. The description on here will display the number of pallets.

By long-clicking on the container, the user can view a list of all the products in this container.

If all has been delivered successfully, the user will click the '''Collected''' button and be taken to the Confirmation process.

If nothing can be delivered, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the delivery, the user will click the '''Notes''' tab and enter details on the adjustment to the delivery. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

Deliveries (from a supplier to a customer direct) will not follow this process, as no container or product details will have been provided on the job. The Notes information from the collection will have been automatically updated onto the associated delivery, so the user will be able to see what was collected. The user will be able to confirm the delivery with the '''OK''' button, cancel the delivery through the '''Cancel''' button and amend the notes as above.

==Add Notes to Job Update==
When a job is complete (confirmed or cancelled) the PDA sends the job update back to the server, which will complete the job as per normal processing.

The Job Update message must be modified to pass back the Notes data entered above.

{{Note}} If the job being updated is a collection and there are any deliveries with the same Job Code, the PDA unit will update the linked job on the device with the notes from the collection.

==Add Notes to Job Export data==
When data is sent back to the server for jobs completed or cancelled, the server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All jobs completed in this manner will be forwarded on to a configured Web Service within the client host system, in the standard ''CALIDUS'' EPOD format.

The format will be changed to include the Notes field, as in the example below:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE></EPL_JOB_CODE>
<EPL_CUST_REF>00067523</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPL_NOTES>Any user-entered notes here</EPL_NOTES>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

{{Note}} Other elements may be included but will contain no data - these may be ignored.

==Load Auto-Export==
The Load Export schema will be modified as in the following example:
<EPL_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL_LOAD_END_PLANNED_TIME>00000000</EPL_LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_MILEAGE_START>0</EPL_MILEAGE_START>
<EPL_MILEAGE_END>0</EPL_MILEAGE_END>
<EPL_USER_ID>MATT</EPL_USER_ID>
</EPL_LOAD>

The Auto-Export process will be modified to add Load export, if configured against the Site or Job Group's EPOD_XF_CONFIG.

The process will be similar to the Job Export - all Loads will be checked if they are required to be exported (through the new EPL_XFER_FLAG against the Load) and a configuration exists for that site or job group. If found, these Load Exports will be sent to the client via the required method (again on the Config table)

==Completion Documents (POD/POC)==
This automated process will also create the Completion documents in PDF format and email them to a central email address, configured against the site in ''CALIDUS'' EPOD.

A document will be generated for every collection and delivery completed (i.e. not cancelled).

The format for both collections and deliveries will be the same and will match the current documentation, shown in [[#Appendix A: POD Formats]]. The format will be created with a name of "Prolog" and this will be able to be chosen as an option from the Delivery and Collection Formats against the Job Group.

The data will be mapped as follows:
*'''From''': The Name will come from the new EPL_OWNER field on EPOD_JOB. The address information will come from the customer address with the same ID as EPL_JOB_GROUP of EPOD_JOB.
*'''Delivery Instructions''': EPL_JOB_INSTRUCTION of EPOD_JOB
*'''Customer''': The Code will be EPL_CUSTOMER_CODE of EPOD_JOB. The address will be taken from this customer's EPOD_CUSTOMER record.
*'''"2 Pallets / 162 Kg"''': EPL_CONTAINER_PACKAGE_DESC of EPOD_CONTAINER
*'''Order Reference''': EPL_CONTAINER_ID of EPOD_CONTAINER
*'''Order Processed''': EPL_START_ACTUAL_DATE of EPOD_JOB
*'''Reference''': EPL_PRODUCT_CODE of EPOD_PRODUCT
*'''Description''': EPL_DESCRIPTION of EPOD_PRODUCT
*'''Qty''': EPL_PRODUCT_QTY_ACTUAL of EPOD_PRODUCT
*'''Signature''': EPL_JOB_SIGNATURE of EPOD_JOB
*'''Block Print''': EPL_CUST_SIGNATORY of EPOD_JOB
*'''Date''': EPL_END_ACTUAL_DATE of EPOD_JOB
*'''Time''': EPL_END_ACTUAL_TIME of EPOD_JOB
*'''Notes''': EPL_NOTES of EPOD_JOB {{Note}} New Field
*'''Consignment Barcode''': {{Warning}} is this required? If so, from what data?
*'''"SM0425 00000 00113306"''': {{Warning}} is this required? If so, from what data?
{{warning}} The data contained in the barcode is not the number above - what is this?

==Data Clear-down==
A data clear-down script will be written and scheduled to run on the host server. This will check the job and image data files and clear down any records older than a specific date.

{{Note}} If this is hosted at OBS, the responsibility of creating and running this script will be OBS'. If hosted by the client, this will be the responsibility of the client.

The process should receive parameters specifying:
*The database connection.
*The Number of Days Transactional Data to keep.
*The Number of Days Image Data to keep.
*The Number of Days Signature Data to keep.

==Admin Screens==
The Admin Users will be provided log-ons - these will be manually created within the Admin system itself. Each log-on can be configured to see all Job Groups (Depots) or a selection of job groups only.

These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.

The Job Group screen will require modification, to add the new configuration flags (detailed in section [[#Database Fields|Database Fields]]

The Load screen will be modified to add a mouse-over tool-tip, displaying the start and end vehicle mileage.

The File Transfer Configuration screens will be modified to allow users to set up multiple configurations against a EPL_XF_CONFIG_ID, for each EPL_XF_ID.

No further changes need to be made within the Administration screen in the ''CALIDUS'' EPOD system, as both the entered Notes and advised Owner can be seen when viewing the completion document within the Admin system.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.



= Appendix A: POD Formats =
[[File:297001-DeliveryNote.jpg|700px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|Ref1=UG 291094 EPOD Admin User Guide
|RefV1=1.0
|RefDate1=6/10/2011
|Ref2=UG 291097 EPOD Client User Guide
|RefV2=1.0
|RefDate2=6/10/2011
|REQ=0
|EST=0
|FS=2
|TS=0
|DEV=16
|ST=5
|IMP=0
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=N
|Rev1=Tony Walker
|Rev1Title=Consultant
|Rev2=Matt Turner
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 297001 Prolog EPOD Modifications

2012-03-01T14:35:01Z

Milesl: Updated Mapping

<div class="noprint">
{{#vardefine:Client|PROL}}
{{#vardefine:ClientName|PROLOG}}
{{#vardefine:System|''CALIDUS'' EPOD}}
{{#vardefine:Doc_Title|Prolog EPOD Modifications}}
{{#vardefine:Version|0.3}}
{{#vardefine:Date|1st March 2012}}
{{#vardefine:Reference|297001}}
{{#vardefine:Year|2012}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}


<div class="noprint">
= Functional Overview =
There will be 35 PDA users and 5 Admin users hosted by the Prolog system.

There are expected to be 35 loads per day.

There are expected to be approximately 10 jobs per load.

There are expected to be up to 52 containers/products per load.

There will be 3 job groups, allocated to each Depot.

== Client Requirement ==
The client requires an implementation of the {{#var:System}} system, following the functionality as described below.

== Solution Overview ==
===Import Data===
Import and Export of Jobs and Loads will be through the existing standard Web Services.

The Job Group field will identify the depot from which the Job originates.

An Owner field added to the Job import, to allow the client system to specify Prolog's Client (e.g. Britvic).

The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).

Delivery jobs will be sent with one container record and multiple product records. The container record will be provided with a description of the required pallets and weight (for example, "2 Pallets / 174.0 Kg"). All products associated to the job will be added to this container, detailing the product code, description and quantity.

Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.

Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job.

The Load import includes the Driver assigned to the Load.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.

===PDA Log-on===
Each Driver will have a PDA with the ''CALIDUS'' EPOD system installed and configured on it. The user will log in with a User ID and password provided to them, and a Vehicle ID, chosen from a list.

===Vehicle Checks===
If the vehicle being used has not been checked recently, the unit will direct the user to complete the Vehicle Checks. The data entry and checks here are configurable within the Admin system. The checks required will be sent to OBS so that they can configure the checks required at this stage.

===Metrics===
Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point.

{{note}} The user will also be prompted to enter the mileage once all jobs on the load are complete.

The user will then be shown a list all the jobs on the load that has been assigned to the user. The jobs are displayed in the order in which they should be completed. However, the jobs can be completed in any sequence by clicking the line of the job required to to be completed first and then clicking the '''OK''' button. The user will then be taken to the Job Details page, which displays the full details of the job being undertaken.
The screen has several Tabs, each showing:
* The Job Type (Collection, Delivery, Service)
* The customer details (Customer Code, Name, Address and Postcode)
* The contact information (Contact name and number)
* The Instructions for the job
From these tabs, the user can:
* Call the customer by clicking on the '''Call''' button.
* Navigate to the customer's address by clicking on the '''Navigate''' button.

Again, here the user can choose which job to complete by using the supplied left and right buttons or start a job with the '''OK''' button, when either a Collection or Delivery process will begin.

{{Note}} The job can be cancelled at this stage by clicking the '''Cancel''' button. The unit will take to the user to an Exception screen and prompt them to enter a reason code explaining why this job was cancelled. See the Exception process for more information.

===Collection Process===
For collections, the user will be shown instructions for the job, with a list of all required products and quantities to collect.

If the collection is successful with no changes, the user will click the '''OK''' button to confirm this and be taken to the Confirmation process.

If nothing can be collected, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the collection, the user will click the '''Notes''' tab and enter details on the adjustment to the collection. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

===Delivery Process===
Deliveries (from Depots to Customers) will be configured to ensure that the PDA unit only requires the user to confirm containers rather than individual products, as follows:

The user will be shown a list of containers only. The description on here will display the number of pallets.

By long-clicking on the container, the user can view a list of all the products in this container.

If all has been delivered successfully, the user will click the '''Collected''' button and be taken to the Confirmation process.

If nothing can be delivered, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the delivery, the user will click the '''Notes''' tab and enter details on the adjustment to the delivery. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

Deliveries (from a supplier to a customer direct) will not follow this process, as no container or product details will have been provided on the job. The Notes information from the collection will have been automatically updated onto the associated delivery, so the user will be able to see what was collected. The user will be able to confirm the delivery with the '''OK''' button, cancel the delivery through the '''Cancel''' button and amend the notes as above.

===Exception Process===
This screen will be displayed if the user is cancelling an entire job, as described in the previous sections.

When cancelling a Job, the user is asked to enter a reason for the cancellation or shortage. These reasons are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system.

If necessary, the user can capture an image to support this reason, by clicking the '''Image''' button. The user can then use the device's camera to capture an image. When complete, the user will exit and will be allowed to view the captured image and add a note to the image to explain.

Once the exception is complete, the user will be returned to the job list, to complete the next job.

===Confirmation Process===
The expected configuration for both Collections and Deliveries will be that the user will be prompted to sign for the job, then the customer will be asked to sign for this also.

The Name defaults to the customer contact name (if present on the job) and allows the user to change this.

Once completed, The user will be returned to the Job Menu to pick up the next task.

The completed job will be transferred back to the main ''CALIDUS'' EPOD system with all the details, signatures and photos.

Once all jobs are completed on that load, the user will be prompted to enter the mileage of the vehicle when they have returned to base. This and the starting mileage will be sent back to the main ''CALIDUS'' EPOD system.

===Export Data===
When data is sent back to the server for jobs completed or cancelled, the server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All jobs completed in this manner will be forwarded on to a configured Web Service within the client host system, in the standard ''CALIDUS'' EPOD format.

When metric data is sent back for the Load, this will be stored in the ''CALIDUS'' EPOD database. The server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All loads completed in this manner will be forwarded on to a configured Web Service within the client host system, in the new format created for this purpose.

===Completion Documents (POD/POC)===
This automated process will also create the Completion documents in PDF format and email them to a central email address, configured against the site in ''CALIDUS'' EPOD.

A document will be generated for every collection and delivery completed (i.e. not cancelled).

The format for both collections and deliveries will be the same and will match the current documentation.

The data held within the bar code is a unique reference to the consignment matching the data in the host system. This data will be displayed instead of the barcode. The 'Consignment Number' will be passed to ePOD as the EPL_CUST_REF.

===Data Clear-down===
A data clear-down script will be written and scheduled to run on the host server. This will check the job and image data files and clear down any records older than a specific date.

{{Note}} If this is hosted at OBS, the responsibility of creating and running this script will be OBS'. If hosted by the client, this will be the responsibility of the client.

===Admin Screens===
The Admin Users will be provided log-ons - these will be manually created within the Admin system itself. Each log-on can be configured to see all Job Groups (Depots) or a selection of job groups only.

These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.

No changes need to be made within the Administration screen in the ''CALIDUS'' EPOD system, as both the entered Notes and advised Owner can be seen when viewing the completion document within the Admin system.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.

== Scope ==
The developments will take place against the latest version of the EPOD system (1.2.X)

The described process flow requires functionality currently being developed, as follows:
* Auto-Email
* PDF Completion Reports
* Auto-Export
* Site Email Address
* Container-only Delivery
* Change Job Identifier on PDA


= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
A Site will be generated. This will be agreed in advance, but is expected to be "PROLOG". This is generated and maintained through the Site Admin screen.
*Automatic Email of POD to a Site email address will be enabled from this screen, by entering a Site email address.
*PDF Production will be enabled from this screen.
*Automatic Export of data will be configured through the Transfer Configuration assigned to the Site record. The Transfer Configuration ID can be maintained through the Transfer Configuration screens. Configuration of both the Load and Job exports will be required.

A Job Group will be set up for each Depot, through the Job Group Admin screen.
*The format for both collections and deliveries will be set to "Prolog" against each Job Group, from the Job Groups screen.
*The expected configuration for both Collections and Deliveries will be that the user will be prompted to sign for the job, then the customer will be asked to sign for this also. This will be through the configuration flags EPL_DEL_DRIVER_SIGN and EPL_COL_DRIVER_SIGN against the EPOD_JOB_GROUP records. These can be configured through the Job Group Config screen, accessible from the Job Groups screen.
*The PDA will not prompt for confirmation of Products at delivery if it has them - this is controlled by setting the "Delivery without Products" flag against each Job Group, maintained in the Job Group screen.
*The PDA will be configured to display the Job Code on the Job Detail screen as the Job Reference, rather than the Job ID. If the system is generating IDs for the received jobs, this should be done. This can be completed through the Job Groups admin screen.
*Metrics entry of mileage information at the start and end of a Load will be enabled.
*Entry of Notes information at the end of a Job will be enabled.

A Customer record will be set up for each of the Job Groups, with the same ID as the Job Groups. This address of these customer records will be used to identify the Depot Address on the documentation.

Reason Codes will be set up as agreed between the host system and ''CALIDUS'' EPOD. These are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system

= Functional Description =
The following areas will require modification:
*Database fields
*Import
**Job
**Load
*Pass new configuration to PDA
*Job Assignation by Vehicle
*Metric Entry
*Load Update from PDA to Server
*Add Notes tab to Collection and Delivery
*Add Notes to Job Update
*Add Notes to Job Export data
*Add Load Auto-Export
*POD/POC Formats
*Data Cleardown

==Database Fields==
New fields will be added to the EPOD_JOB table:
*EPL_USER_NOTES - a Max length text field
*EPL_OWNER_NAME - a 30-character text field

New fields will be added to the EPOD_LOAD table
*EPL_MILEAGE_START - an integer field
*EPL_MILEAGE_END - an integer field
*EPL_XFER_FLAG - a Y/N flag to control whether the load has been exported yet.

New Configuration fields will be added to EPOD_JOB_GROUP and EPOD_SITE:
*EPL_METRIC_ENTRY - a Y/N flag to control entry of mileage information at the start and end of a Load.
*EPL_NOTES - a Y/N flag to control entry of Notes information at the end of a Job.

A new field will be added to EPOD_XF_CONFIG:
*EPL_XF_ID - a 20-character ID field.
The index will be modified to add this field.

Values in this field will be:
*JOB - A configuration set for JOB updates
*LOAD - A configuration set for LOAD updates

==Import Data==
Import and Export of Jobs and Loads will be through the existing standard Web Services.

===Job===
An Owner field added to the Job import, to allow the client system to specify the Depot (e.g. Britvic).

The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).

Delivery jobs will be sent with one container record and multiple product records. The container record will be provided with a description of the required pallets and weight (for example, "2 Pallets / 174.0 Kg"). All products associated to the job will be added to this container, detailing the product code, description and quantity.

Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.

Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job.

<PRE>
<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>00067527</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>00067527</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_002</EPL_JOB_CODE>
<EPL_CUST_REF>00067523</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE></EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>2 Pallets / 174.0Kg</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>
</PRE>
Notes:
*EPL_SITE_ID will be mapped to the single company site ID - this is suggested to be "PROLOG"
*EPL_JOB_GROUP will be the originating Depot ID (e.g. "SHEFFIELD"). These will be pre-set and agreed in advance.
*EPL_JOB_ID (10 characters) is a unique reference for the individual job (collection or delivery). For linked collections and deliveries, each job should have a unique EPL_JOB_ID, but the same EPL_JOB_CODE. If left blank, this will be generated by the system. This will be mapped to the unique value of the currently used barcode.
*EPL_JOB_CODE (20 characters) will be any reference that ties linked jobs together.
*An additional reference can be mapped to EPL_CUST_REF (30 characters). This will map to the consignment number.
*The customer code, name, contact and address information will be mapped to the appropriate fields.
*EPL_CONTAINER_ID (15 characters) will be the Order Reference.
*EPL_CONTAINER_PACKAGE_DESC (40 characters) will contain the text showing the total pallets and weight.
*The product code, description and quantity will be mapped to the appropriate product tags

===Load===
Loads can be imported separately or the jobs can be included within the EPOD_JOBS tag.

The Load import includes the Driver and Vehicle assigned to the Load.

{{warning}} Currently the client system allocates jobs to a Vehicle, not a Driver, whilst ''CALIDUS'' EPOD assigns by the User ID (the Driver). In the requirements meeting, did we decide which will be changed, EPOD or Transport system?

<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPL_VEHICLE_ID>AB12XYZ</EPL_VEHICLE_ID>
<EPOD_JOBS>
...
</EPOD_JOBS>
</EPOD_LOAD>
<EPOD_LOAD>
...
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

==Pass new Configuration to PDA==
Each Driver will have a PDA with the ''CALIDUS'' EPOD system installed and configured on it. The user will log in with a User ID and password provided to them, and a Vehicle ID, chosen from a list.

The server responds with a Logon Response, passing all the configuration and standing data to the device. The configuration will be modified to include the new configuration elements against the Site and Job Group. The PDA will store this configuration.

==Job Assignation by Vehicle==

The EPOD server will first attempt to find any incomplete loads assigned to that user. In the event that this does not return a load, the server will be modified to check for any incomplete loads assigned to that vehicle. If found, the Load will be assigned to that user and sent to the device as is does now for loads assigned to users.

==Metric Entry==
Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point. This will be though a form to enter the mileage in numeric form.

This form will be shown once all jobs are complete against a Load, to enter the mileage at end of the full trip. This will default to the first mileage entered. A prompt at this atge will say "Load Completed. Return to Base, then enter Mileage".

==Load Update from PDA to Server==
Both of the entry items will be sent back to the Server on a new Load Update message, showing that the load is now complete.

The Server will action this message and store the mileage values on the message onto the new fields in the database against the load.

{{Note}} The Actual Distance value against the load will be calculated and stored here as well, by taking the start mileage value from the end mileage. If the value results in a negative value, this will be saved as 0 miles, as the user has made an error inputting the mileage information.

If the Site has been configured for transmitting Load data back to the host system, the Load record's EPL_XFER_FLAG will be marked as "N", to indicate that the record has not yet been transmitted, otherwise this will be set to "".

==Add Notes tab to Collection and Delivery==
A new tab will be added to the Collection and Delivery process, if the system has been configured to do so through the new EPL_NOTES configuration element. The note field will allow free-text entry by the user.

The tab will be added as the last tab on each screen. The unit will function as follows:

===Collection Process===
For collections, the user will be shown instructions for the job, with a list of all required products and quantities to collect in the instructions field.

If the collection is successful with no changes, the user will click the '''OK''' button to confirm this and be taken to the Confirmation process.

If nothing can be collected, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the collection, the user will click the '''Notes''' tab and enter details on the adjustment to the collection. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

===Delivery Process===
Deliveries (from Depots to Customers) will be configured to ensure that the PDA unit only requires the user to confirm containers rather than individual products (through the existing configuration flag EPL_CONTAINER_ONLY), as follows:

The user will be shown a list of containers only. The description on here will display the number of pallets.

By long-clicking on the container, the user can view a list of all the products in this container.

If all has been delivered successfully, the user will click the '''Collected''' button and be taken to the Confirmation process.

If nothing can be delivered, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the delivery, the user will click the '''Notes''' tab and enter details on the adjustment to the delivery. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

Deliveries (from a supplier to a customer direct) will not follow this process, as no container or product details will have been provided on the job. The Notes information from the collection will have been automatically updated onto the associated delivery, so the user will be able to see what was collected. The user will be able to confirm the delivery with the '''OK''' button, cancel the delivery through the '''Cancel''' button and amend the notes as above.

==Add Notes to Job Update==
When a job is complete (confirmed or cancelled) the PDA sends the job update back to the server, which will complete the job as per normal processing.

The Job Update message must be modified to pass back the Notes data entered above.

{{Note}} If the job being updated is a collection and there are any deliveries with the same Job Code, the PDA unit will update the linked job on the device with the notes from the collection.

==Add Notes to Job Export data==
When data is sent back to the server for jobs completed or cancelled, the server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All jobs completed in this manner will be forwarded on to a configured Web Service within the client host system, in the standard ''CALIDUS'' EPOD format.

The format will be changed to include the Notes field, as in the example below:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE></EPL_JOB_CODE>
<EPL_CUST_REF>00067523</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPL_NOTES>Any user-entered notes here</EPL_NOTES>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

{{Note}} Other elements may be included but will contain no data - these may be ignored.

==Load Auto-Export==
The Load Export schema will be modified as in the following example:
<EPL_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL_LOAD_END_PLANNED_TIME>00000000</EPL_LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_MILEAGE_START>0</EPL_MILEAGE_START>
<EPL_MILEAGE_END>0</EPL_MILEAGE_END>
<EPL_USER_ID>MATT</EPL_USER_ID>
</EPL_LOAD>

The Auto-Export process will be modified to add Load export, if configured against the Site or Job Group's EPOD_XF_CONFIG.

The process will be similar to the Job Export - all Loads will be checked if they are required to be exported (through the new EPL_XFER_FLAG against the Load) and a configuration exists for that site or job group. If found, these Load Exports will be sent to the client via the required method (again on the Config table)

==Completion Documents (POD/POC)==
This automated process will also create the Completion documents in PDF format and email them to a central email address, configured against the site in ''CALIDUS'' EPOD.

A document will be generated for every collection and delivery completed (i.e. not cancelled).

The format for both collections and deliveries will be the same and will match the current documentation, shown in [[#Appendix A: POD Formats]]. The format will be created with a name of "Prolog" and this will be able to be chosen as an option from the Delivery and Collection Formats against the Job Group.

The data will be mapped as follows:
*'''From''': The Name will come from the new EPL_OWNER field on EPOD_JOB. The address information will come from the customer address with the same ID as EPL_JOB_GROUP of EPOD_JOB.
*'''Delivery Instructions''': EPL_JOB_INSTRUCTION of EPOD_JOB
*'''Customer''': The Code will be EPL_CUSTOMER_CODE of EPOD_JOB. The address will be taken from this customer's EPOD_CUSTOMER record.
*'''"2 Pallets / 162 Kg"''': EPL_CONTAINER_PACKAGE_DESC of EPOD_CONTAINER
*'''Order Reference''': EPL_CONTAINER_ID of EPOD_CONTAINER
*'''Order Processed''': EPL_START_ACTUAL_DATE of EPOD_JOB
*'''Reference''': EPL_PRODUCT_CODE of EPOD_PRODUCT
*'''Description''': EPL_DESCRIPTION of EPOD_PRODUCT
*'''Qty''': EPL_PRODUCT_QTY_ACTUAL of EPOD_PRODUCT
*'''Signature''': EPL_JOB_SIGNATURE of EPOD_JOB
*'''Block Print''': EPL_CUST_SIGNATORY of EPOD_JOB
*'''Date''': EPL_END_ACTUAL_DATE of EPOD_JOB
*'''Time''': EPL_END_ACTUAL_TIME of EPOD_JOB
*'''Notes''': EPL_NOTES of EPOD_JOB {{Note}} New Field
*'''Consignment Barcode''': {{Warning}} is this required? If so, from what data?
*'''"SM0425 00000 00113306"''': {{Warning}} is this required? If so, from what data?
{{warning}} The data contained in the barcode is not the number above - what is this?

==Data Clear-down==
A data clear-down script will be written and scheduled to run on the host server. This will check the job and image data files and clear down any records older than a specific date.

{{Note}} If this is hosted at OBS, the responsibility of creating and running this script will be OBS'. If hosted by the client, this will be the responsibility of the client.

The process should receive parameters specifying:
*The database connection.
*The Number of Days Transactional Data to keep.
*The Number of Days Image Data to keep.
*The Number of Days Signature Data to keep.

==Admin Screens==
The Admin Users will be provided log-ons - these will be manually created within the Admin system itself. Each log-on can be configured to see all Job Groups (Depots) or a selection of job groups only.

These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.

The Job Group screen will require modification, to add the new configuration flags (detailed in section [[#Database Fields|Database Fields]]

The Load screen will be modified to add a mouse-over tool-tip, displaying the start and end vehicle mileage.

The File Transfer Configuration screens will be modified to allow users to set up multiple configurations against a EPL_XF_CONFIG_ID, for each EPL_XF_ID.

No further changes need to be made within the Administration screen in the ''CALIDUS'' EPOD system, as both the entered Notes and advised Owner can be seen when viewing the completion document within the Admin system.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.



= Appendix A: POD Formats =
[[File:297001-DeliveryNote.jpg|700px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|Ref1=UG 291094 EPOD Admin User Guide
|RefV1=1.0
|RefDate1=6/10/2011
|Ref2=UG 291097 EPOD Client User Guide
|RefV2=1.0
|RefDate2=6/10/2011
|REQ=0
|EST=0
|FS=2
|TS=0
|DEV=16
|ST=5
|IMP=0
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=N
|Rev1=Tony Walker
|Rev1Title=Consultant
|Rev2=Matt Turner
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 297001 Prolog EPOD Modifications

2012-03-01T14:32:31Z

Milesl: Updated in responce to comms

<div class="noprint">
{{#vardefine:Client|PROL}}
{{#vardefine:ClientName|PROLOG}}
{{#vardefine:System|''CALIDUS'' EPOD}}
{{#vardefine:Doc_Title|Prolog EPOD Modifications}}
{{#vardefine:Version|0.3}}
{{#vardefine:Date|1st March 2012}}
{{#vardefine:Reference|297001}}
{{#vardefine:Year|2012}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}


<div class="noprint">
= Functional Overview =
There will be 35 PDA users and 5 Admin users hosted by the Prolog system.

There are expected to be 35 loads per day.

There are expected to be approximately 10 jobs per load.

There are expected to be up to 52 containers/products per load.

There will be 3 job groups, allocated to each Depot.

== Client Requirement ==
The client requires an implementation of the {{#var:System}} system, following the functionality as described below.

== Solution Overview ==
===Import Data===
Import and Export of Jobs and Loads will be through the existing standard Web Services.

The Job Group field will identify the depot from which the Job originates.

An Owner field added to the Job import, to allow the client system to specify Prolog's Client (e.g. Britvic).

The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).

Delivery jobs will be sent with one container record and multiple product records. The container record will be provided with a description of the required pallets and weight (for example, "2 Pallets / 174.0 Kg"). All products associated to the job will be added to this container, detailing the product code, description and quantity.

Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.

Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job.

The Load import includes the Driver assigned to the Load.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.

===PDA Log-on===
Each Driver will have a PDA with the ''CALIDUS'' EPOD system installed and configured on it. The user will log in with a User ID and password provided to them, and a Vehicle ID, chosen from a list.

===Vehicle Checks===
If the vehicle being used has not been checked recently, the unit will direct the user to complete the Vehicle Checks. The data entry and checks here are configurable within the Admin system. The checks required will be sent to OBS so that they can configure the checks required at this stage.

===Metrics===
Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point.

{{note}} The user will also be prompted to enter the mileage once all jobs on the load are complete.

The user will then be shown a list all the jobs on the load that has been assigned to the user. The jobs are displayed in the order in which they should be completed. However, the jobs can be completed in any sequence by clicking the line of the job required to to be completed first and then clicking the '''OK''' button. The user will then be taken to the Job Details page, which displays the full details of the job being undertaken.
The screen has several Tabs, each showing:
* The Job Type (Collection, Delivery, Service)
* The customer details (Customer Code, Name, Address and Postcode)
* The contact information (Contact name and number)
* The Instructions for the job
From these tabs, the user can:
* Call the customer by clicking on the '''Call''' button.
* Navigate to the customer's address by clicking on the '''Navigate''' button.

Again, here the user can choose which job to complete by using the supplied left and right buttons or start a job with the '''OK''' button, when either a Collection or Delivery process will begin.

{{Note}} The job can be cancelled at this stage by clicking the '''Cancel''' button. The unit will take to the user to an Exception screen and prompt them to enter a reason code explaining why this job was cancelled. See the Exception process for more information.

===Collection Process===
For collections, the user will be shown instructions for the job, with a list of all required products and quantities to collect.

If the collection is successful with no changes, the user will click the '''OK''' button to confirm this and be taken to the Confirmation process.

If nothing can be collected, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the collection, the user will click the '''Notes''' tab and enter details on the adjustment to the collection. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

===Delivery Process===
Deliveries (from Depots to Customers) will be configured to ensure that the PDA unit only requires the user to confirm containers rather than individual products, as follows:

The user will be shown a list of containers only. The description on here will display the number of pallets.

By long-clicking on the container, the user can view a list of all the products in this container.

If all has been delivered successfully, the user will click the '''Collected''' button and be taken to the Confirmation process.

If nothing can be delivered, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the delivery, the user will click the '''Notes''' tab and enter details on the adjustment to the delivery. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

Deliveries (from a supplier to a customer direct) will not follow this process, as no container or product details will have been provided on the job. The Notes information from the collection will have been automatically updated onto the associated delivery, so the user will be able to see what was collected. The user will be able to confirm the delivery with the '''OK''' button, cancel the delivery through the '''Cancel''' button and amend the notes as above.

===Exception Process===
This screen will be displayed if the user is cancelling an entire job, as described in the previous sections.

When cancelling a Job, the user is asked to enter a reason for the cancellation or shortage. These reasons are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system.

If necessary, the user can capture an image to support this reason, by clicking the '''Image''' button. The user can then use the device's camera to capture an image. When complete, the user will exit and will be allowed to view the captured image and add a note to the image to explain.

Once the exception is complete, the user will be returned to the job list, to complete the next job.

===Confirmation Process===
The expected configuration for both Collections and Deliveries will be that the user will be prompted to sign for the job, then the customer will be asked to sign for this also.

The Name defaults to the customer contact name (if present on the job) and allows the user to change this.

Once completed, The user will be returned to the Job Menu to pick up the next task.

The completed job will be transferred back to the main ''CALIDUS'' EPOD system with all the details, signatures and photos.

Once all jobs are completed on that load, the user will be prompted to enter the mileage of the vehicle when they have returned to base. This and the starting mileage will be sent back to the main ''CALIDUS'' EPOD system.

===Export Data===
When data is sent back to the server for jobs completed or cancelled, the server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All jobs completed in this manner will be forwarded on to a configured Web Service within the client host system, in the standard ''CALIDUS'' EPOD format.

When metric data is sent back for the Load, this will be stored in the ''CALIDUS'' EPOD database. The server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All loads completed in this manner will be forwarded on to a configured Web Service within the client host system, in the new format created for this purpose.

===Completion Documents (POD/POC)===
This automated process will also create the Completion documents in PDF format and email them to a central email address, configured against the site in ''CALIDUS'' EPOD.

A document will be generated for every collection and delivery completed (i.e. not cancelled).

The format for both collections and deliveries will be the same and will match the current documentation.

The data held within the bar code is a unique reference to the consignment matching the data in the host system. This data will be displayed instead of the barcode. The 'Consignment Number' will be passed to ePOD as the EPL_CUST_REF.

===Data Clear-down===
A data clear-down script will be written and scheduled to run on the host server. This will check the job and image data files and clear down any records older than a specific date.

{{Note}} If this is hosted at OBS, the responsibility of creating and running this script will be OBS'. If hosted by the client, this will be the responsibility of the client.

===Admin Screens===
The Admin Users will be provided log-ons - these will be manually created within the Admin system itself. Each log-on can be configured to see all Job Groups (Depots) or a selection of job groups only.

These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.

No changes need to be made within the Administration screen in the ''CALIDUS'' EPOD system, as both the entered Notes and advised Owner can be seen when viewing the completion document within the Admin system.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.

== Scope ==
The developments will take place against the latest version of the EPOD system (1.2.X)

The described process flow requires functionality currently being developed, as follows:
* Auto-Email
* PDF Completion Reports
* Auto-Export
* Site Email Address
* Container-only Delivery
* Change Job Identifier on PDA


= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
A Site will be generated. This will be agreed in advance, but is expected to be "PROLOG". This is generated and maintained through the Site Admin screen.
*Automatic Email of POD to a Site email address will be enabled from this screen, by entering a Site email address.
*PDF Production will be enabled from this screen.
*Automatic Export of data will be configured through the Transfer Configuration assigned to the Site record. The Transfer Configuration ID can be maintained through the Transfer Configuration screens. Configuration of both the Load and Job exports will be required.

A Job Group will be set up for each Depot, through the Job Group Admin screen.
*The format for both collections and deliveries will be set to "Prolog" against each Job Group, from the Job Groups screen.
*The expected configuration for both Collections and Deliveries will be that the user will be prompted to sign for the job, then the customer will be asked to sign for this also. This will be through the configuration flags EPL_DEL_DRIVER_SIGN and EPL_COL_DRIVER_SIGN against the EPOD_JOB_GROUP records. These can be configured through the Job Group Config screen, accessible from the Job Groups screen.
*The PDA will not prompt for confirmation of Products at delivery if it has them - this is controlled by setting the "Delivery without Products" flag against each Job Group, maintained in the Job Group screen.
*The PDA will be configured to display the Job Code on the Job Detail screen as the Job Reference, rather than the Job ID. If the system is generating IDs for the received jobs, this should be done. This can be completed through the Job Groups admin screen.
*Metrics entry of mileage information at the start and end of a Load will be enabled.
*Entry of Notes information at the end of a Job will be enabled.

A Customer record will be set up for each of the Job Groups, with the same ID as the Job Groups. This address of these customer records will be used to identify the Depot Address on the documentation.

Reason Codes will be set up as agreed between the host system and ''CALIDUS'' EPOD. These are configurable within the administrative system. These will be generic reasons agreed and mapped to the client host system

= Functional Description =
The following areas will require modification:
*Database fields
*Import
**Job
**Load
*Pass new configuration to PDA
*Job Assignation by Vehicle
*Metric Entry
*Load Update from PDA to Server
*Add Notes tab to Collection and Delivery
*Add Notes to Job Update
*Add Notes to Job Export data
*Add Load Auto-Export
*POD/POC Formats
*Data Cleardown

==Database Fields==
New fields will be added to the EPOD_JOB table:
*EPL_USER_NOTES - a Max length text field
*EPL_OWNER_NAME - a 30-character text field

New fields will be added to the EPOD_LOAD table
*EPL_MILEAGE_START - an integer field
*EPL_MILEAGE_END - an integer field
*EPL_XFER_FLAG - a Y/N flag to control whether the load has been exported yet.

New Configuration fields will be added to EPOD_JOB_GROUP and EPOD_SITE:
*EPL_METRIC_ENTRY - a Y/N flag to control entry of mileage information at the start and end of a Load.
*EPL_NOTES - a Y/N flag to control entry of Notes information at the end of a Job.

A new field will be added to EPOD_XF_CONFIG:
*EPL_XF_ID - a 20-character ID field.
The index will be modified to add this field.

Values in this field will be:
*JOB - A configuration set for JOB updates
*LOAD - A configuration set for LOAD updates

==Import Data==
Import and Export of Jobs and Loads will be through the existing standard Web Services.

===Job===
An Owner field added to the Job import, to allow the client system to specify the Depot (e.g. Britvic).

The Customer information (i.e. customer code, name address and contact details) will be sent as part of Job, so that this information can be placed on the resulting completion document (POD or POC).

Delivery jobs will be sent with one container record and multiple product records. The container record will be provided with a description of the required pallets and weight (for example, "2 Pallets / 174.0 Kg"). All products associated to the job will be added to this container, detailing the product code, description and quantity.

Collection jobs will have no product or container details, just job instructions detailing the products and quantities to be collected.

Linked Collections and Deliveries (i.e. collecting from a supplier and delivering directly to a customer on the same trip) will be required. In this instance, the jobs will be linked by having the same Job Code on each job.

<PRE>
<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>00067527</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>00067527</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_002</EPL_JOB_CODE>
<EPL_CUST_REF>00067523</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@CUST1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE></EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>2 Pallets / 174.0Kg</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID></EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>
</PRE>
Notes:
*EPL_SITE_ID will be mapped to the single company site ID - this is suggested to be "PROLOG"
*EPL_JOB_GROUP will be the originating Depot ID (e.g. "SHEFFIELD"). These will be pre-set and agreed in advance.
*EPL_JOB_ID (10 characters) is a unique reference for the individual job (collection or delivery). For linked collections and deliveries, each job should have a unique EPL_JOB_ID, but the same EPL_JOB_CODE. If left blank, this will be generated by the system. {{warning}} is the barcode content a unique ID?
*EPL_JOB_CODE (20 characters) will be any reference that ties linked jobs together.
*An additional reference can be mapped to EPL_CUST_REF (30 characters). {{Warning}} The number under the barcode?
*The customer code, name, contact and address information will be mapped to the appropriate fields.
*EPL_CONTAINER_ID (15 characters) will be the Order Reference.
*EPL_CONTAINER_PACKAGE_DESC (40 characters) will contain the text showing the total pallets and weight.
*The product code, description and quantity will be mapped to the appropriate product tags

===Load===
Loads can be imported separately or the jobs can be included within the EPOD_JOBS tag.

The Load import includes the Driver and Vehicle assigned to the Load.

{{warning}} Currently the client system allocates jobs to a Vehicle, not a Driver, whilst ''CALIDUS'' EPOD assigns by the User ID (the Driver). In the requirements meeting, did we decide which will be changed, EPOD or Transport system?

<EPOD_IMPORT EPL_SITE_ID="PROLOG" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPL_VEHICLE_ID>AB12XYZ</EPL_VEHICLE_ID>
<EPOD_JOBS>
...
</EPOD_JOBS>
</EPOD_LOAD>
<EPOD_LOAD>
...
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

==Pass new Configuration to PDA==
Each Driver will have a PDA with the ''CALIDUS'' EPOD system installed and configured on it. The user will log in with a User ID and password provided to them, and a Vehicle ID, chosen from a list.

The server responds with a Logon Response, passing all the configuration and standing data to the device. The configuration will be modified to include the new configuration elements against the Site and Job Group. The PDA will store this configuration.

==Job Assignation by Vehicle==

The EPOD server will first attempt to find any incomplete loads assigned to that user. In the event that this does not return a load, the server will be modified to check for any incomplete loads assigned to that vehicle. If found, the Load will be assigned to that user and sent to the device as is does now for loads assigned to users.

==Metric Entry==
Once a load has been downloaded, the unit will check whether the system requires Current Mileage entry against the load. If so, the unit will request the user to enter the mileage at this point. This will be though a form to enter the mileage in numeric form.

This form will be shown once all jobs are complete against a Load, to enter the mileage at end of the full trip. This will default to the first mileage entered. A prompt at this atge will say "Load Completed. Return to Base, then enter Mileage".

==Load Update from PDA to Server==
Both of the entry items will be sent back to the Server on a new Load Update message, showing that the load is now complete.

The Server will action this message and store the mileage values on the message onto the new fields in the database against the load.

{{Note}} The Actual Distance value against the load will be calculated and stored here as well, by taking the start mileage value from the end mileage. If the value results in a negative value, this will be saved as 0 miles, as the user has made an error inputting the mileage information.

If the Site has been configured for transmitting Load data back to the host system, the Load record's EPL_XFER_FLAG will be marked as "N", to indicate that the record has not yet been transmitted, otherwise this will be set to "".

==Add Notes tab to Collection and Delivery==
A new tab will be added to the Collection and Delivery process, if the system has been configured to do so through the new EPL_NOTES configuration element. The note field will allow free-text entry by the user.

The tab will be added as the last tab on each screen. The unit will function as follows:

===Collection Process===
For collections, the user will be shown instructions for the job, with a list of all required products and quantities to collect in the instructions field.

If the collection is successful with no changes, the user will click the '''OK''' button to confirm this and be taken to the Confirmation process.

If nothing can be collected, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the collection, the user will click the '''Notes''' tab and enter details on the adjustment to the collection. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

===Delivery Process===
Deliveries (from Depots to Customers) will be configured to ensure that the PDA unit only requires the user to confirm containers rather than individual products (through the existing configuration flag EPL_CONTAINER_ONLY), as follows:

The user will be shown a list of containers only. The description on here will display the number of pallets.

By long-clicking on the container, the user can view a list of all the products in this container.

If all has been delivered successfully, the user will click the '''Collected''' button and be taken to the Confirmation process.

If nothing can be delivered, the user can press the '''Cancel''' button here and will be directed to the Exception process.

If there has been a problem with the delivery, the user will click the '''Notes''' tab and enter details on the adjustment to the delivery. Once complete, the user will then press the '''OK''' button and be taken to the Confirmation process.

Deliveries (from a supplier to a customer direct) will not follow this process, as no container or product details will have been provided on the job. The Notes information from the collection will have been automatically updated onto the associated delivery, so the user will be able to see what was collected. The user will be able to confirm the delivery with the '''OK''' button, cancel the delivery through the '''Cancel''' button and amend the notes as above.

==Add Notes to Job Update==
When a job is complete (confirmed or cancelled) the PDA sends the job update back to the server, which will complete the job as per normal processing.

The Job Update message must be modified to pass back the Notes data entered above.

{{Note}} If the job being updated is a collection and there are any deliveries with the same Job Code, the PDA unit will update the linked job on the device with the notes from the collection.

==Add Notes to Job Export data==
When data is sent back to the server for jobs completed or cancelled, the server will mark this data to be sent automatically on to the client host system. This will be through a regularly scheduled process (i.e. every few minutes). All jobs completed in this manner will be forwarded on to a configured Web Service within the client host system, in the standard ''CALIDUS'' EPOD format.

The format will be changed to include the Notes field, as in the example below:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>DEPOT1</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>CUSTCODE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_OWNER>Britvic</EPL_OWNER>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE></EPL_JOB_CODE>
<EPL_CUST_REF>00067523</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPL_NOTES>Any user-entered notes here</EPL_NOTES>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>PROLOG</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>00067523</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

{{Note}} Other elements may be included but will contain no data - these may be ignored.

==Load Auto-Export==
The Load Export schema will be modified as in the following example:
<EPL_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL_LOAD_END_PLANNED_TIME>00000000</EPL_LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_MILEAGE_START>0</EPL_MILEAGE_START>
<EPL_MILEAGE_END>0</EPL_MILEAGE_END>
<EPL_USER_ID>MATT</EPL_USER_ID>
</EPL_LOAD>

The Auto-Export process will be modified to add Load export, if configured against the Site or Job Group's EPOD_XF_CONFIG.

The process will be similar to the Job Export - all Loads will be checked if they are required to be exported (through the new EPL_XFER_FLAG against the Load) and a configuration exists for that site or job group. If found, these Load Exports will be sent to the client via the required method (again on the Config table)

==Completion Documents (POD/POC)==
This automated process will also create the Completion documents in PDF format and email them to a central email address, configured against the site in ''CALIDUS'' EPOD.

A document will be generated for every collection and delivery completed (i.e. not cancelled).

The format for both collections and deliveries will be the same and will match the current documentation, shown in [[#Appendix A: POD Formats]]. The format will be created with a name of "Prolog" and this will be able to be chosen as an option from the Delivery and Collection Formats against the Job Group.

The data will be mapped as follows:
*'''From''': The Name will come from the new EPL_OWNER field on EPOD_JOB. The address information will come from the customer address with the same ID as EPL_JOB_GROUP of EPOD_JOB.
*'''Delivery Instructions''': EPL_JOB_INSTRUCTION of EPOD_JOB
*'''Customer''': The Code will be EPL_CUSTOMER_CODE of EPOD_JOB. The address will be taken from this customer's EPOD_CUSTOMER record.
*'''"2 Pallets / 162 Kg"''': EPL_CONTAINER_PACKAGE_DESC of EPOD_CONTAINER
*'''Order Reference''': EPL_CONTAINER_ID of EPOD_CONTAINER
*'''Order Processed''': EPL_START_ACTUAL_DATE of EPOD_JOB
*'''Reference''': EPL_PRODUCT_CODE of EPOD_PRODUCT
*'''Description''': EPL_DESCRIPTION of EPOD_PRODUCT
*'''Qty''': EPL_PRODUCT_QTY_ACTUAL of EPOD_PRODUCT
*'''Signature''': EPL_JOB_SIGNATURE of EPOD_JOB
*'''Block Print''': EPL_CUST_SIGNATORY of EPOD_JOB
*'''Date''': EPL_END_ACTUAL_DATE of EPOD_JOB
*'''Time''': EPL_END_ACTUAL_TIME of EPOD_JOB
*'''Notes''': EPL_NOTES of EPOD_JOB {{Note}} New Field
*'''Consignment Barcode''': {{Warning}} is this required? If so, from what data?
*'''"SM0425 00000 00113306"''': {{Warning}} is this required? If so, from what data?
{{warning}} The data contained in the barcode is not the number above - what is this?

==Data Clear-down==
A data clear-down script will be written and scheduled to run on the host server. This will check the job and image data files and clear down any records older than a specific date.

{{Note}} If this is hosted at OBS, the responsibility of creating and running this script will be OBS'. If hosted by the client, this will be the responsibility of the client.

The process should receive parameters specifying:
*The database connection.
*The Number of Days Transactional Data to keep.
*The Number of Days Image Data to keep.
*The Number of Days Signature Data to keep.

==Admin Screens==
The Admin Users will be provided log-ons - these will be manually created within the Admin system itself. Each log-on can be configured to see all Job Groups (Depots) or a selection of job groups only.

These users will be able to view (and create) loads and jobs within the system, as well as view the completion documents for completed jobs, or view images of exceptions on cancelled jobs.

The Job Group screen will require modification, to add the new configuration flags (detailed in section [[#Database Fields|Database Fields]]

The Load screen will be modified to add a mouse-over tool-tip, displaying the start and end vehicle mileage.

The File Transfer Configuration screens will be modified to allow users to set up multiple configurations against a EPL_XF_CONFIG_ID, for each EPL_XF_ID.

No further changes need to be made within the Administration screen in the ''CALIDUS'' EPOD system, as both the entered Notes and advised Owner can be seen when viewing the completion document within the Admin system.

{{Note}} Inter-warehouse Transfers are not expected to be included in the initial running of the system, as these are currently handled manually. In a future phase (i.e. after go-live of the initial phase), these may be added into the client host system for processing or, alternatively, they will be created manually within ''CALIDUS'' EPOD and attached to existing loads.



= Appendix A: POD Formats =
[[File:297001-DeliveryNote.jpg|700px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|Ref1=UG 291094 EPOD Admin User Guide
|RefV1=1.0
|RefDate1=6/10/2011
|Ref2=UG 291097 EPOD Client User Guide
|RefV2=1.0
|RefDate2=6/10/2011
|REQ=0
|EST=0
|FS=2
|TS=0
|DEV=16
|ST=5
|IMP=0
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=N
|Rev1=Tony Walker
|Rev1Title=Consultant
|Rev2=Matt Turner
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 294838 Proctor ePOD Modifications

2012-03-01T12:03:29Z

Milesl:

<div class="noprint">
{{#vardefine:Client|PROC}}
{{#vardefine:ClientName|Proctors}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Proctors ePOD Modifications}}
{{#vardefine:Version|1.1}}
{{#vardefine:Date|01st March 2012}}
{{#vardefine:Reference|294838}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==

== Solution Overview ==

The ERP system will be able to interface Customer data to the ''CALIDUS'' EPOD system, to identify the customer address, contact and email information.

{{Note}} Customers can also be created through the standard Job interface - if this is the case, then the Job address provided with the first job for this customer will become the customer address.

Jobs will be received for Collection and Delivery from the following main customer types:
*Suppliers
*Customers
*Proctors-operated Warehouses
*3rd Party Warehouses

The jobs will be updated into the ''CALIDUS'' EPOD system through the standard WebService interface.

This job upload will create 2 tasks:
*A Collection Job
*A Delivery Job

Every Collection and Delivery will be specified separately within the interface, with the Product and Quantity specified for all jobs. Linked collections and deliveries will have the same Job Code, but will be distinguished by the Job Type (i.e. Collection or Delivery).

The Upload system will also identify the Loads onto which jobs are planned, as all planning is completed through the Proctors' ERP system.

In phase 1, the initial uploads will be sent to the EPOD system with either no load information, or with the load ID set to a default value.

In phase 2, the initial uploads will be sent tot he EPOD system with either no load information, or with the correct load identified against them. It will then be possible to subsequently update the Load for a job through another update of the Job alone.

There are two types of job:
* Customer/Supplier jobs - jobs that begin or end with a Customer or Supplier.
* Inter-warehouse Transfer - jobs that begin and end from Warehouses

All jobs will be categorised by the ''CALIDUS'' EPOD Job Group into one of the two categories - this will define the paperwork produced by the system when the job is completed. The Job Group will be agreed and sent to the system in the upload files.

Once jobs from Proctors-controlled warehouses are picked and marshalled, updated Jobs will be sent to the EPOD system, detailing the actual containers (pallets) and product quantities on each.

{{Note}} If this data is not available at the time of collecting or delivering the associated jobs, the system will check periodically through a regularly-scheduled automatic process.

Collection jobs from a Proctors-operated warehouse should then have containers and product quantities specified against them. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.

{{Warning}} In this circumstance, where pallet information has not been received, the automatic update of the job when complete will identify on product and quantity information, not pallet information.

The process for a Collection of this type will be:
* Confirm arrival to warehouse.
* Scan/Enter/Select Pallets to be collected.
* Once completed, confirm collection through depot signature.
The user will also be able to long-press against any container to show the details of any products contained within it.

Collection jobs from a Customer, Supplier or 3rd party warehouse (i.e. non-Proctors) will have the Product and Quantity created against them (i.e. no containers/pallets). The process will be:
* Confirm arrival to customer/supplier/warehouse.
* Scan/Enter/Select Products to be collected.
* Confirm total quantity of the products.
* Once completed, confirm collection through customer/supplier signature.

A Delivery of a non-Proctors job will have only product and quantity details. The process will be:
* Confirm arrival to customer.
* Scan/Enter/Select Products to be delivered.
* Confirm total quantity of the products.
* Once completed, confirm delivery through customer signature.

A Delivery of Proctors job should have container (pallet), product and quantities. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.
The process will be:
* Confirm arrival to customer/depot.
* Scan/Enter/Select pallets being delivered
* Once completed, confirm delivery through customer/depot signature.

{{Note}} The system will be configurable to allow the PDA unit to display Job Code rather than Job ID on the Job Detail screen.

Two new POD document formats will be created:
* A Delivery format, configured for use on Customer/Supplier jobs.
* A Transfer format, configured for use on Inter-warehouse Transfers.
These formats will be defined against the Job group provided on the upload.
In order for these to be created to match the current formats as closely as possible, the ''CALIDUS'' EPOD Job Import will be extended to add new fields, identified in detail later in the document.

''CALIDUS'' EPOD will be set up to allow certain customers to be automatically emailed upon completion of jobs to and from them. When enabled, the format associated to the Job Group will be sent to the Customer's associated email address, if there is one. This will also be sent to an email address against the site, if there is one, ensuring that the ERP system is provided copies of the produced PDF files.

{{Note}} Email notification of the POD or POC will be attempted if this feature is turned on and if the customer has an email address. If depots or suppliers do not require notification of collections or deliveries, it must be ensured that the customers created do not have an email address.

Confirmation or cancellation of any job will trigger an automatic update of the ERP system. This will be configurable but is expected to be through an email of the standard EPOD XML job update message. This update will be a scheduled process that will regularly check and attempt to update when possible. It will be scheduled to run as often as required by the client, up to once per minute.

== Scope ==



= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
The two new fixed Job Groups will be set up for Proctors-controlled warehouses and 3rd-party. The former will be configured with the Stock Transfer POD format, whilst the latter will be configured with the other format.


= Functional Description =
The total changes required are:
* Database
* Job Import/Export
* Customers Import
* Auto-Export
* Auto-Email
* Admin
* PDA Client
** Delivery/Collection Without Products
* New POD formats
* PDF Production

== Database Changes ==

=== EPOD_SITE ===
A new flag will be added for the Site Email Address for auto-email, called EPL_EMAIL

=== EPOD_JOB ===
New Fields:
*EPL_SIGNED_UNCHECKED
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number
*EPL_ORDER_DATE
*EPL_SALES_CONTACT - PPB Contact
*EPL_XFER_FLAG - default to ""
*EPL_EMAIL_FLAG - default to ""

Changes:
*Indexing applied to EPL_JOB_CODE, EPL_JOB_TYPE. This will be a repeating index.
*Indexing applied to EPL_XFER_FLAG. This will be a repeating index.
*Indexing applied to EPL_EMAIL_FLAG. This will be a repeating index.

=== EPOD_CONTAINER ===

*EPL_GROSS_WEIGHT - a floating point number.
*EPL_COMMENT - a maximum length text field.

=== EPOD_PRODUCT ===

*EPL_UNIT_TYPE
*EPL_DESCRIPTION_LONG
*EPL_PRODUCT_QTY_ORDERED

=== EPOD_JOB_GROUP ===

*EPL_CONTAINER_ONLY - Controls container-only delivery
*EPL_JOB_DISPLAY - controls whether Job ID or Job Code is displayed on the PDA.

=== XF_CONFIG ===

EPOD_JOB will require a new field of two characters EPL_XFER_FLAG, this will be defaulted to "".
EPOD_SITE and EPOD_JOB_GROUP will require a new field EPL_XF_CONFIG which will link to the EPL_XF_CONFIG_ID. If no export is required this will be blank.

A new table EPOD_XF_CONFIG will be created consisting of:
*EPL_XF_CONFIG_ID: A ten character unique field
*EPL_DESCRIPTION
*EPL_XF_TYPE: A ten character field identifying the type of export (SOAP, File, Email)
*EPL_XF_DESTINATION: A 255 character field identifying the destination of the export
*EPL_XF_PARM: Additional parameters for example subject for email

A new table EPOD_XF_AUDIT_HEADER will be created consisting of:
*EPL_HEADER_ID: A unique auto-increment Id
*EPL_SITE_ID: Indexed
*EPL_JOB_GROUP: Indexed
*EPL_REQUEST_DATA: A maximum length free-text field
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)

A new table EPOD_XF_AUDIT_DETAIL will be created consisting of:
*EPL_HEADER_ID: Foreign key to EPOD_XF_AUDIT_HEADER
*EPL_DETAIL_ID: A unique auto-increment Id
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)
{{Note}} This table is for future development and will not be used at this time.

=== JOB_ADDRESS ===
A new table EPOD_JOB_ADDRESS will be created consisting of:
*EPL_SITE_ID: Foreign key to EPOD_SITE
*EPL_JOB_ID: Foreign key to EPOD_JOB
*EPL_ADDRESS_LINE_1
*EPL_ADDRESS_LINE_2
*EPL_ADDRESS_LINE_3
*EPL_ADDRESS_LINE_4
*EPL_POST_CODE
*EPL_CONTACT
*EPL_TELEPHONE
*EPL_EMAIL
*EPL_LAST_CHANGE_DATE
*EPL_LAST_CHANGE_TIME
The table will be indexed on EPL_SITE_ID and EPL_JOB_ID.

== XML Interface ==

=== Job Import ===

The system shall use the EPL_JOB_CODE field as a reference linking the delivery and collection, the index used shall be EPL_JOB_CODE and EPL_JOB_TYPE. The field EPL_JOB_ID will always be unique, this will be auto-generated by our system if not passed in.

The import can include an optional EPOD_CUSTOMER tag. This is used in preference to the CUSTOMER_NAME and CUSTOMER_CODE tags to update Customer address information. The supplied information against the job is then used exclusively for the Job Address, if different. So for Proctor both the standard adress section with the job message will be completed, mapping to the delivery address (EPOD_JOB_ADDRESS) and the EPOD_CUSTOMER tag will be populated updating the customer address.

The Import XML structure will have a attribute of ID. This will not be stored within the system, instead this will be stamped on the responding message from the web service. Within the responce the EPL_JOB_CODE field will be added to any job records returned in the import confirmation.

Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST" ID="XXXXX">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

The following XML would have the same outcome as above without the generation of container records:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

Both the collection and delivery must share the same EPL_JOB_CODE reference.

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>.
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>

==== Job Update ====

To update the jobs with the Container details, Proctors' ERP must follow the same standard structure as the import.
All Job, Container and Product tags that are populated and present will update the relevant details in the ''CALIDUS'' EPOD system.

{{Note}}
* If the EPL_JOB_ID is blank (as expected for the Proctors interface, as the Collection and Deliveries will be linked via EPL_JOB_CODE), the system will check to see whether a job exists for this EPL_JOB_CODE and EPL_JOB_TYPE. If so, the record will be updated. If not, a new record (with a generated EPL_JOB_ID) will be created.
* If the EPL_JOB_ID is not blank, the system will check to see whether a job exists for this EPL_JOB_ID. If so, the record will be updated. If not, a new record will be created with this EPL_JOB_ID.
* If the EPL_LOAD_ID is left blank, the system will not update the Load ID of the Job.
* If the EPOD_CONTAINERS tag is not populated, the system will not update any container information. If it is present, the system will delete any existing container information and replace it with the information in the containers tag.
* If the EPOD_PRODUCTS tag is not populated, the system will not update any product information. If it is present, the system will delete any existing product information and replace it with the information in the product tag.
* The import can include an optional EPOD_CUSTOMER tag. This is used in preference to the CUSTOMER_NAME and CUSTOMER_CODE tags to update Customer address information. The supplied information against the job is then used exclusively for the Job Address, if different.

Changes will be made to the Customer Address import to ensure that a customer and a job can have defined addresses, as follows:
* If the EPOD_CUSTOMER tag exists in the message
** Pass the contents of the tag to the Customer Import, to update the Customer details
** Use the address information in the message to update the Job Address.
* Else
**If the Customer Code exists in the message
*** the system will check that the record exists within the database with that code.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created with that code.
** If not, and the Customer Name exists
*** the system will check that the record exists within the database with that name.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created and a code generated for it.
** If neither Code nor Name exist, the system will store the address information against the Job.

=== Job Export ===

At the point of job status changed the system will export the Jobs structure using the standard XML and send this to a predefined email address, for interfacing with the ERP system. This will be configured using the XF_CONFIG section of the system.

The required email functionality will need to be added to the existing export process.

The following XML is produced by the export, this example shows the export with multiple Jobs:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PHOTO_ID/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/> <EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575903</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

The following XML is produced by the export, this example shows the export with a single Job:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

==== Auto-Export Process ====

Whenever a job is updated to Cancelled or Complete (i.e. when the jobs are updated by the PDA client, or when jobs are updated via the Admin system), after committing the changes to the database, the Auto Export flag will be checked against the Job Group and Site. If this flag is present the EPL_JOB record will have the EPL_XFER_FLAG set to N, to indicate that the record requires interfacing but has not yet been sent.

{{Note}} These changes will be committed into the Data Access Layer, so that the same code will be called whether running this through the Admin or PDA server functions.

A timed process will be running to send any Jobs with the Xfer flag of N.
The process will:
*Retrieve all jobs on the EPL_JOBS table with the Xfer flag set to N, sorted by Site and Job Group.
*For each record found in distinct Site and Job Group:
**Load the details of this Job ID,
**Generate the XML export as per the standard for currently existing exports
**Once all jobs for the Site/Job Group are exported:
***Get the configuration of the Job Group. If the configuration for the Job Group does not exist, get the configuration for the Site.
***Attempt to transfer this to the destination specified in the configuration.

If this process if successful then the Xfer flag on the Job record will be set to Y, and a success audit record written.
If this fails the flag on the job will be set to N and a record will be written to a audit table with details of the failure.
If the file is send successfully but a message is received from the destination advising of this problem then an audit record will be written and the flag will be set to N.

This timed process will be scheduled on the system. The frequency of the process will be defined by the schedule and can be no more frequent that one per minute. If the process is already running, the process will wait for the next cycle before starting.

The status of the audit records based on the result are:
* S for success;
* SF for success send but error at the receivers, and;
* F for failure to send.
These records will be cleared down once they are older than 7 days.

===Customer Import===
Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_CUSTOMERS>
<EPOD_CUSTOMER>
<EPL_SITE_ID>Dave Jones</EPL_SITE_ID>
<EPL_CUSTOMER_CODE>CUST01</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
</EPOD_CUSTOMERS>

Similarly to the Job import:
* If the Customer Code exists in the message
** the system will check that the record exists within the database with that code.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created.
* If not, and the Customer Name exists
** the system will check that the record exists within the database with that name.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created and a code generated for it.
* If neither exist, the system will not import the customer.

== Admin System ==

Within Phase one the Admin interface will be used to plan Jobs onto loads, all required functionality has been implemented. Within phase two this will not be required as Proctors will interface pre-planned loads.
The following changes will need to be made to the admin system to reflect the database changes:

===Jobs Screen===

*EPL_SIGNED_UNCHECKED - Visible on the POD only, this field is not searchable
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number - Entry only
*EPL_ORDER_DATE - Entry only
*EPL_SALES_CONTACT - PPB Contact - Entry only
*EPOD_JOB_ADDRESS.

In order to accommodate the new fields and allow them to be displayed and entered, the Job screen must be extensively modified.

The Entry panel will be modified to allow entry of the following fields, in two adjacent panels, as below:
<table border="solid black 1px">
<tr><td colspan="2"> '''[Edit buttons]''' </td></tr>
<tr><td width="50%">
Job Type

Job Code

Job Group

Cust Ref

'''Dnote No'''

Planned Date/Time

'''Order Date/Time'''

Sales Contact

Job/Office Instructions

</td><td width="50%">
Customer Code

Use Customer Address as Delivery Address?

'''New Customer Code'''

'''New Customer Name'''

''Address 1''

''Address 2''

''Address 3''

''Address 4''

''Postcode''

''Contact''

''Email''

''Telephone''
</td></tr>
<tr><td colspan="2"> '''[Save] [Cancel]'''</td></tr>
</table>

All fields in '''Bold''' are new fields. All fields in ''Italics'' are new functionality.

The ''Edit'' buttons will not be shown in entry mode.

The left side of the screen will show all the Job-related fields for entry, including the new fields.

The right side of the screen will be the area to identify the customer and address.

The Instructions entry will be through a tabbed entry box. The first tab will contain the Job Instructions and will be displayed. The second tab can be clicked on to edit the Office Instructions.

The Customer drop-down will allow you to select:
* ''No Customer''
** All entry fields (bar Customer Code and Name) below will be enabled.
** The check-box will be disabled.
* ''Create a New Customer'':
** All entry fields below will be enabled.
** Customer Code and Name must be entered
** The check-box will be disabled.
* Select an Existing Customer from the list.
** All fields below will be populated from the Customer's address information.
** The check-box will be enabled, indicating that you are using the Customer's address as the delivery address.
** Only the check-box will be an enabled field - all others will be disabled.

Un-checking the check box will enable all the entry fields, which will remain populated with the default values from the customer address.

Clicking '''Save''' will create the Job. If a new customer is being created, the address entered will be assigned to the customer. If a delivery address has been chosen that is different to the selected existing customer (or no customer has been selected), the address will be saved to the Job address.

The following columns will be removed from the grid:
* Site ID
* Job Instructions
* Office Instructions
* Reason Code
* Configure
* Details
* Report

The Status field will be modified to show the Reason Code and Description entered for a cancelled job in a tool-tip (activated by hovering the mouse pointer over the Status).

The grid will be modified to not allow direct entry. Instead, the grid will use the Entry panel. This will be activated by clicking once on the line, which will display the Entry panel, populated with the details of the line selected.

The functionality will differ to the Entry functionality, in that the Action buttons will be populated as follows:
* Details - Display any Container, Product or Service details associated to the job
* Report - Display the POD/POC/Service report (only enabled if the Job is at status Complete
* Cancel Job - Move a Job to Cancelled status.
* Image - Display any Image associated to the Job.

===Containers Screen===
*EPL_GROSS_WEIGHT - Visible against the container record and available for entry.
*EPL_COMMENT - Visible against the container record and available for entry.

===Job Products Screen===

*EPL_UNIT_TYPE - Visible against the product record and available for entry
*EPL_DESCRIPTION_LONG - Visible against the product record and available for entry
*EPL_PRODUCT_QTY_ORDERED - Visible against the product record and available for entry

===Site Maintenance Screen===
*EPL_EMAIL - Visible and editable.

===Job Group Maintenance Screen===

*EPL_CONTAINER_ONLY - Controls container only delivery - Visible and Editable
*EPL_JOB_DISPLAY - controls which element is displayed on the PDA device on the Job Detail screen as the Job Reference. The two options are Job Code or Job ID, defaulting to the latter.

===Transfer Configuration Screen===

A new audit and maintenance screen will be required.

This will allow users to search the EPOD_XF_AUDIT_HEADER table by EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_JOB_GROUP. With a later implementation allowing to search for EPL_JOB_ID, or EPL_LOAD_ID.

This screen will display the header records details, EPL_JOB_GROUP, EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_STATUS_DESCRIPTION, and EPL_REQUEST_DATA.
{{note|This would be best displayed within a popup of some kind. For future implementation, the editing and resending of this data may be needed. Doing so a link would need to be made to each job.
}}

== PDA Server ==

The message sent to the PDA client from the server will be modified so that the Job Address (if present) will be used in preference to the Customer address. The Container Weight field (EPL_GROSS_WEIGHT) must also be passed.

The Standing Data Configuration must be changed to pass the new control flags to the device (e.g. EPL_JOB_DISPLAY).

== PDA Client ==

The DB changes will need to be reflected on the PDA.

The PDA will need to be implemented with the functionality to transfer collection details to the delivery job, based on matching Job Codes. This includes altering the planned delivery quantity to the actual collection quantity specified in the collection.

The PDA will need to display Job Code rather than Job ID on the Job Detail screen, depending on the value of the new configuration flag.

The PDA will need to select the appropriate delivery or collection process based on the jobs attributes:
*Collections
**Proctors-Controlled Warehouse - Collection of Containers without Products
**Non-Proctors Location - Collection of Products without Containers
*Deliveries
**Proctors Collection - Delivery of Containers without Products.
**Non-Proctors Collection - Delivery of Products without Containers

When starting a collection or delivery from a Proctors-Controlled Warehouse a update check must be forced (this is currently handled under the standard process) if no container records are received, then an alert is given to the user advising that the data may not be up to date.

====Standard Collection====
The user will be able to long-press any container in the grid. This will provide a popup menu, allowing the user to see the details of the selected container. The PDA will display a screen displaying:
*ID
*Package Code and Description
*Weight

====Collection of Containers without Products====
This will check a parameter on the Job Group - if Container-only Collection is enabled and there are no loose products, the collection will continue as Container only, otherwise the standard (Products Without Containers) collection process will be used.

The user is presented with a list of Containers for collection. The user selects a container either through text entry or scanning. Users have the ability to short-deliver by container only and use the exception process to document any non-delivered containers. When all Containers are accounted for, the user is prompted to complete the job, with a customer signature.

Long-pressing on a container will display a pop-up menu with a Products option shown. If this is clicked, the PDA client will display a list of all products against the container. {{note}} This option should be available only if this is unit is configured for containers without products.

====Collection of Products without Containers====
The user is presented with a list of products for collection. The user confirms collection of each product as in the standard approach. When all Products are accounted for the user is prompted to complete the job, with a customer signature.

====Delivery of Products without Containers====
The process is the same as Collection of Products without Containers.

====Delivery of Containers without Products====
The process is the same as Collection of Containers without Products.

=== Photos ===
Photos will be captured using the standard exception process. User's must be aware that quality of the images will affect GPRS usage, higher quality equals longer more date to transfer. This can only be controlled on the PDA itself and must be set in the PDA's camera settings.

== New POD formats ==
New POD formats will be created for the operation.

The POD or POC format produced will be dependant on the Job Group associated to the Job.

All images captured relating to the Job will be displayed on a second page of the POD/POC document, with the associated detail information (Job ID, Container ID, Product Code, Image description). Again image quality is dependant on device settings, which affects the image size.

Fields on the Delivery Note document will be sourced from the following database fields:
* Delivery Note: EPL_JOB_CODE
* Customer Address: Address information from the Job's Customer
* Delivery Address: Address information from the Job's Address (if present) or the Customer's.
* Customer Tel No: From the Job's Address (if present) or the Customer.
* Cust No/Contact: From the Job's Address (if present) or the Customer.
* Our Order No: EPL_SO_NUMBER (New field)
* Order Date: EPL_ORDER_DATE (New Field)
* Customer Order No: EPL_CUST_REF
* PPB Contact: EPL_SALES_CONTACT (New Field)
* Product Reference: EPL_PRODUCT_CODE
* Product Description: EPL_DESCRIPTION and EPL_DESCRIPTION_LONG
* Due Date: EPL_START_PLANNED_DATE/TIME {{Note}} This is the same for all lines.
* Unit: EPL_UNIT_TYPE (New Field)
* Quantity: EPL_PRODUCT_QTY_ORDERED (New Field)
* Quantity Despatched: EPL_PRODUCT_QTY_PLANNED
* Quantity Delivered: EPL_PRODUCT_QTY_ACTUAL
* No Of Parcels: EPL_COMMENT of EPOD_CONTAINER (New field)
* Pallet ID: EPL_CONTAINER_ID
* Special Instructions: EPL_JOB_INSTRUCTION
* Total Weight: See below
* Delivered By: PDA User Name
* Print Name: EPL_CUST_SIGNATORY (entered by PDA user)
* Date: Job Completion Date
* Signed Unchecked: EPL_SIGNED_UNCHECKED (New Field)

Total Weight will be calculated at the container level. The weight must be passed through as part of the interfaced container record. If no containers have been interfaced, this field will be omitted.

{{Warning}}The following elements have been excluded from the design:
* Barcode
* Vat No
* Picked
* Converted

Fields on the Transfer Note document will be sourced from the following database fields (where different from the Delivery Note):
* Stock Transfer Note: EPL_JOB_CODE
* Transfer Stock From: From the Collection's Customer information
* Transfer Stock To: From the Delivery's Customer information
* Xfer Ref No: EPL_SO_NUMBER (New Field)
* Input By: EPL_SALES_CONTACT (New Field)
* Part Number: EPL_PRODUCT_ID
* Product Description: EPL_DESCRIPTION

{{Warning}}The following elements have been excluded from the design:
* Location
* Location Qty

{{Note}} The existing generic POD/POC format must be modified to check for the Job address before using the Customer's address.

{{Note}} There could be many pallets and stock codes on a collection or delivery. This will run into multiple pages regardless of which note is produced. In the case where multiple pages of information are displayed, the header, up to and including the ''Customer Tel No'' table, will be shown on every page, whereas the Signature footer table will be shown only on the first page, being omitted from all subsequent pages.

==PDF Production==
A new rule will be added at a Site level to control whether emails to customers will be HTML-Embedded or PDF attachment style.

The system will check this rule when:
# The "Email To" button is pressed on the "View POD" page
# auto-emailed documents are being produced.

If this rule is not enabled, the system will send emails as now (embedded HTML emails).

If this rule is enabled, the system will:
*Export and save the page to a temporary directory, with all images rendered.
*Run the saved page through a conversion routine to convert the HTML to a PDF page (saved in the same directory).
*Attach this generated PDF to the email and send
*Delete the temporary folder.

The conversion routine will use the WkHtmlToPDF program with default parameters - this must be installed on the server.

==Auto-Email==
The Auto-email code will be moved into the new batch Auto-Export Process.

The update of a job to complete or cancelled will result in the new field EPL_EMAIL_FLAG being set to "N". The batch process will retrieve all job records where this flag is "N" and the Job Group or Site associated to the job requires auto-email.

The process will iterate through these records and retrieve the email addresses that the job should be emailed to from the Site, Job and Customer records.

If no emails have been specified, EPL_EMAIL_FLAG will set to "X".

If an email address has been specified, the email will be built as per the current process and sent to the defined email address. EPL_EMAIL_FLAG will set to "Y".



= Appendix A: POD Formats =
[[File:Delivery Note.jpg|600px|border]]

[[File:Stock Transfer Note.jpg|600px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|REQ=0
|EST=0
|FS=5.0
|TS=0
|DEV=36
|ST=5.00
|IMP=2.0
|Client={{#var:Client}}
|Year=2012
|FSEST=N
|Rev1=Matt Turner
|Rev1Title=OBS Representative
|Rev2=Stephen McCartney
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 294838 Proctor ePOD Modifications

2012-03-01T12:01:45Z

Milesl: v1.1 - Including changes from feedback from the client

<div class="noprint">
{{#vardefine:Client|PROC}}
{{#vardefine:ClientName|Proctors}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Proctors ePOD Modifications}}
{{#vardefine:Version|1.1}}
{{#vardefine:Date|22nd February 2012}}
{{#vardefine:Reference|294838}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==

== Solution Overview ==

The ERP system will be able to interface Customer data to the ''CALIDUS'' EPOD system, to identify the customer address, contact and email information.

{{Note}} Customers can also be created through the standard Job interface - if this is the case, then the Job address provided with the first job for this customer will become the customer address.

Jobs will be received for Collection and Delivery from the following main customer types:
*Suppliers
*Customers
*Proctors-operated Warehouses
*3rd Party Warehouses

The jobs will be updated into the ''CALIDUS'' EPOD system through the standard WebService interface.

This job upload will create 2 tasks:
*A Collection Job
*A Delivery Job

Every Collection and Delivery will be specified separately within the interface, with the Product and Quantity specified for all jobs. Linked collections and deliveries will have the same Job Code, but will be distinguished by the Job Type (i.e. Collection or Delivery).

The Upload system will also identify the Loads onto which jobs are planned, as all planning is completed through the Proctors' ERP system.

In phase 1, the initial uploads will be sent to the EPOD system with either no load information, or with the load ID set to a default value.

In phase 2, the initial uploads will be sent tot he EPOD system with either no load information, or with the correct load identified against them. It will then be possible to subsequently update the Load for a job through another update of the Job alone.

There are two types of job:
* Customer/Supplier jobs - jobs that begin or end with a Customer or Supplier.
* Inter-warehouse Transfer - jobs that begin and end from Warehouses

All jobs will be categorised by the ''CALIDUS'' EPOD Job Group into one of the two categories - this will define the paperwork produced by the system when the job is completed. The Job Group will be agreed and sent to the system in the upload files.

Once jobs from Proctors-controlled warehouses are picked and marshalled, updated Jobs will be sent to the EPOD system, detailing the actual containers (pallets) and product quantities on each.

{{Note}} If this data is not available at the time of collecting or delivering the associated jobs, the system will check periodically through a regularly-scheduled automatic process.

Collection jobs from a Proctors-operated warehouse should then have containers and product quantities specified against them. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.

{{Warning}} In this circumstance, where pallet information has not been received, the automatic update of the job when complete will identify on product and quantity information, not pallet information.

The process for a Collection of this type will be:
* Confirm arrival to warehouse.
* Scan/Enter/Select Pallets to be collected.
* Once completed, confirm collection through depot signature.
The user will also be able to long-press against any container to show the details of any products contained within it.

Collection jobs from a Customer, Supplier or 3rd party warehouse (i.e. non-Proctors) will have the Product and Quantity created against them (i.e. no containers/pallets). The process will be:
* Confirm arrival to customer/supplier/warehouse.
* Scan/Enter/Select Products to be collected.
* Confirm total quantity of the products.
* Once completed, confirm collection through customer/supplier signature.

A Delivery of a non-Proctors job will have only product and quantity details. The process will be:
* Confirm arrival to customer.
* Scan/Enter/Select Products to be delivered.
* Confirm total quantity of the products.
* Once completed, confirm delivery through customer signature.

A Delivery of Proctors job should have container (pallet), product and quantities. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.
The process will be:
* Confirm arrival to customer/depot.
* Scan/Enter/Select pallets being delivered
* Once completed, confirm delivery through customer/depot signature.

{{Note}} The system will be configurable to allow the PDA unit to display Job Code rather than Job ID on the Job Detail screen.

Two new POD document formats will be created:
* A Delivery format, configured for use on Customer/Supplier jobs.
* A Transfer format, configured for use on Inter-warehouse Transfers.
These formats will be defined against the Job group provided on the upload.
In order for these to be created to match the current formats as closely as possible, the ''CALIDUS'' EPOD Job Import will be extended to add new fields, identified in detail later in the document.

''CALIDUS'' EPOD will be set up to allow certain customers to be automatically emailed upon completion of jobs to and from them. When enabled, the format associated to the Job Group will be sent to the Customer's associated email address, if there is one. This will also be sent to an email address against the site, if there is one, ensuring that the ERP system is provided copies of the produced PDF files.

{{Note}} Email notification of the POD or POC will be attempted if this feature is turned on and if the customer has an email address. If depots or suppliers do not require notification of collections or deliveries, it must be ensured that the customers created do not have an email address.

Confirmation or cancellation of any job will trigger an automatic update of the ERP system. This will be configurable but is expected to be through an email of the standard EPOD XML job update message. This update will be a scheduled process that will regularly check and attempt to update when possible. It will be scheduled to run as often as required by the client, up to once per minute.

== Scope ==



= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
The two new fixed Job Groups will be set up for Proctors-controlled warehouses and 3rd-party. The former will be configured with the Stock Transfer POD format, whilst the latter will be configured with the other format.


= Functional Description =
The total changes required are:
* Database
* Job Import/Export
* Customers Import
* Auto-Export
* Auto-Email
* Admin
* PDA Client
** Delivery/Collection Without Products
* New POD formats
* PDF Production

== Database Changes ==

=== EPOD_SITE ===
A new flag will be added for the Site Email Address for auto-email, called EPL_EMAIL

=== EPOD_JOB ===
New Fields:
*EPL_SIGNED_UNCHECKED
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number
*EPL_ORDER_DATE
*EPL_SALES_CONTACT - PPB Contact
*EPL_XFER_FLAG - default to ""
*EPL_EMAIL_FLAG - default to ""

Changes:
*Indexing applied to EPL_JOB_CODE, EPL_JOB_TYPE. This will be a repeating index.
*Indexing applied to EPL_XFER_FLAG. This will be a repeating index.
*Indexing applied to EPL_EMAIL_FLAG. This will be a repeating index.

=== EPOD_CONTAINER ===

*EPL_GROSS_WEIGHT - a floating point number.
*EPL_COMMENT - a maximum length text field.

=== EPOD_PRODUCT ===

*EPL_UNIT_TYPE
*EPL_DESCRIPTION_LONG
*EPL_PRODUCT_QTY_ORDERED

=== EPOD_JOB_GROUP ===

*EPL_CONTAINER_ONLY - Controls container-only delivery
*EPL_JOB_DISPLAY - controls whether Job ID or Job Code is displayed on the PDA.

=== XF_CONFIG ===

EPOD_JOB will require a new field of two characters EPL_XFER_FLAG, this will be defaulted to "".
EPOD_SITE and EPOD_JOB_GROUP will require a new field EPL_XF_CONFIG which will link to the EPL_XF_CONFIG_ID. If no export is required this will be blank.

A new table EPOD_XF_CONFIG will be created consisting of:
*EPL_XF_CONFIG_ID: A ten character unique field
*EPL_DESCRIPTION
*EPL_XF_TYPE: A ten character field identifying the type of export (SOAP, File, Email)
*EPL_XF_DESTINATION: A 255 character field identifying the destination of the export
*EPL_XF_PARM: Additional parameters for example subject for email

A new table EPOD_XF_AUDIT_HEADER will be created consisting of:
*EPL_HEADER_ID: A unique auto-increment Id
*EPL_SITE_ID: Indexed
*EPL_JOB_GROUP: Indexed
*EPL_REQUEST_DATA: A maximum length free-text field
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)

A new table EPOD_XF_AUDIT_DETAIL will be created consisting of:
*EPL_HEADER_ID: Foreign key to EPOD_XF_AUDIT_HEADER
*EPL_DETAIL_ID: A unique auto-increment Id
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)
{{Note}} This table is for future development and will not be used at this time.

=== JOB_ADDRESS ===
A new table EPOD_JOB_ADDRESS will be created consisting of:
*EPL_SITE_ID: Foreign key to EPOD_SITE
*EPL_JOB_ID: Foreign key to EPOD_JOB
*EPL_ADDRESS_LINE_1
*EPL_ADDRESS_LINE_2
*EPL_ADDRESS_LINE_3
*EPL_ADDRESS_LINE_4
*EPL_POST_CODE
*EPL_CONTACT
*EPL_TELEPHONE
*EPL_EMAIL
*EPL_LAST_CHANGE_DATE
*EPL_LAST_CHANGE_TIME
The table will be indexed on EPL_SITE_ID and EPL_JOB_ID.

== XML Interface ==

=== Job Import ===

The system shall use the EPL_JOB_CODE field as a reference linking the delivery and collection, the index used shall be EPL_JOB_CODE and EPL_JOB_TYPE. The field EPL_JOB_ID will always be unique, this will be auto-generated by our system if not passed in.

The import can include an optional EPOD_CUSTOMER tag. This is used in preference to the CUSTOMER_NAME and CUSTOMER_CODE tags to update Customer address information. The supplied information against the job is then used exclusively for the Job Address, if different. So for Proctor both the standard adress section with the job message will be completed, mapping to the delivery address (EPOD_JOB_ADDRESS) and the EPOD_CUSTOMER tag will be populated updating the customer address.

The Import XML structure will have a attribute of ID. This will not be stored within the system, instead this will be stamped on the responding message from the web service. Within the responce the EPL_JOB_CODE field will be added to any job records returned in the import confirmation.

Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST" ID="XXXXX">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

The following XML would have the same outcome as above without the generation of container records:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

Both the collection and delivery must share the same EPL_JOB_CODE reference.

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>.
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>

==== Job Update ====

To update the jobs with the Container details, Proctors' ERP must follow the same standard structure as the import.
All Job, Container and Product tags that are populated and present will update the relevant details in the ''CALIDUS'' EPOD system.

{{Note}}
* If the EPL_JOB_ID is blank (as expected for the Proctors interface, as the Collection and Deliveries will be linked via EPL_JOB_CODE), the system will check to see whether a job exists for this EPL_JOB_CODE and EPL_JOB_TYPE. If so, the record will be updated. If not, a new record (with a generated EPL_JOB_ID) will be created.
* If the EPL_JOB_ID is not blank, the system will check to see whether a job exists for this EPL_JOB_ID. If so, the record will be updated. If not, a new record will be created with this EPL_JOB_ID.
* If the EPL_LOAD_ID is left blank, the system will not update the Load ID of the Job.
* If the EPOD_CONTAINERS tag is not populated, the system will not update any container information. If it is present, the system will delete any existing container information and replace it with the information in the containers tag.
* If the EPOD_PRODUCTS tag is not populated, the system will not update any product information. If it is present, the system will delete any existing product information and replace it with the information in the product tag.
* The import can include an optional EPOD_CUSTOMER tag. This is used in preference to the CUSTOMER_NAME and CUSTOMER_CODE tags to update Customer address information. The supplied information against the job is then used exclusively for the Job Address, if different.

Changes will be made to the Customer Address import to ensure that a customer and a job can have defined addresses, as follows:
* If the EPOD_CUSTOMER tag exists in the message
** Pass the contents of the tag to the Customer Import, to update the Customer details
** Use the address information in the message to update the Job Address.
* Else
**If the Customer Code exists in the message
*** the system will check that the record exists within the database with that code.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created with that code.
** If not, and the Customer Name exists
*** the system will check that the record exists within the database with that name.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created and a code generated for it.
** If neither Code nor Name exist, the system will store the address information against the Job.

=== Job Export ===

At the point of job status changed the system will export the Jobs structure using the standard XML and send this to a predefined email address, for interfacing with the ERP system. This will be configured using the XF_CONFIG section of the system.

The required email functionality will need to be added to the existing export process.

The following XML is produced by the export, this example shows the export with multiple Jobs:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PHOTO_ID/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/> <EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575903</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

The following XML is produced by the export, this example shows the export with a single Job:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

==== Auto-Export Process ====

Whenever a job is updated to Cancelled or Complete (i.e. when the jobs are updated by the PDA client, or when jobs are updated via the Admin system), after committing the changes to the database, the Auto Export flag will be checked against the Job Group and Site. If this flag is present the EPL_JOB record will have the EPL_XFER_FLAG set to N, to indicate that the record requires interfacing but has not yet been sent.

{{Note}} These changes will be committed into the Data Access Layer, so that the same code will be called whether running this through the Admin or PDA server functions.

A timed process will be running to send any Jobs with the Xfer flag of N.
The process will:
*Retrieve all jobs on the EPL_JOBS table with the Xfer flag set to N, sorted by Site and Job Group.
*For each record found in distinct Site and Job Group:
**Load the details of this Job ID,
**Generate the XML export as per the standard for currently existing exports
**Once all jobs for the Site/Job Group are exported:
***Get the configuration of the Job Group. If the configuration for the Job Group does not exist, get the configuration for the Site.
***Attempt to transfer this to the destination specified in the configuration.

If this process if successful then the Xfer flag on the Job record will be set to Y, and a success audit record written.
If this fails the flag on the job will be set to N and a record will be written to a audit table with details of the failure.
If the file is send successfully but a message is received from the destination advising of this problem then an audit record will be written and the flag will be set to N.

This timed process will be scheduled on the system. The frequency of the process will be defined by the schedule and can be no more frequent that one per minute. If the process is already running, the process will wait for the next cycle before starting.

The status of the audit records based on the result are:
* S for success;
* SF for success send but error at the receivers, and;
* F for failure to send.
These records will be cleared down once they are older than 7 days.

===Customer Import===
Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_CUSTOMERS>
<EPOD_CUSTOMER>
<EPL_SITE_ID>Dave Jones</EPL_SITE_ID>
<EPL_CUSTOMER_CODE>CUST01</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
</EPOD_CUSTOMERS>

Similarly to the Job import:
* If the Customer Code exists in the message
** the system will check that the record exists within the database with that code.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created.
* If not, and the Customer Name exists
** the system will check that the record exists within the database with that name.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created and a code generated for it.
* If neither exist, the system will not import the customer.

== Admin System ==

Within Phase one the Admin interface will be used to plan Jobs onto loads, all required functionality has been implemented. Within phase two this will not be required as Proctors will interface pre-planned loads.
The following changes will need to be made to the admin system to reflect the database changes:

===Jobs Screen===

*EPL_SIGNED_UNCHECKED - Visible on the POD only, this field is not searchable
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number - Entry only
*EPL_ORDER_DATE - Entry only
*EPL_SALES_CONTACT - PPB Contact - Entry only
*EPOD_JOB_ADDRESS.

In order to accommodate the new fields and allow them to be displayed and entered, the Job screen must be extensively modified.

The Entry panel will be modified to allow entry of the following fields, in two adjacent panels, as below:
<table border="solid black 1px">
<tr><td colspan="2"> '''[Edit buttons]''' </td></tr>
<tr><td width="50%">
Job Type

Job Code

Job Group

Cust Ref

'''Dnote No'''

Planned Date/Time

'''Order Date/Time'''

Sales Contact

Job/Office Instructions

</td><td width="50%">
Customer Code

Use Customer Address as Delivery Address?

'''New Customer Code'''

'''New Customer Name'''

''Address 1''

''Address 2''

''Address 3''

''Address 4''

''Postcode''

''Contact''

''Email''

''Telephone''
</td></tr>
<tr><td colspan="2"> '''[Save] [Cancel]'''</td></tr>
</table>

All fields in '''Bold''' are new fields. All fields in ''Italics'' are new functionality.

The ''Edit'' buttons will not be shown in entry mode.

The left side of the screen will show all the Job-related fields for entry, including the new fields.

The right side of the screen will be the area to identify the customer and address.

The Instructions entry will be through a tabbed entry box. The first tab will contain the Job Instructions and will be displayed. The second tab can be clicked on to edit the Office Instructions.

The Customer drop-down will allow you to select:
* ''No Customer''
** All entry fields (bar Customer Code and Name) below will be enabled.
** The check-box will be disabled.
* ''Create a New Customer'':
** All entry fields below will be enabled.
** Customer Code and Name must be entered
** The check-box will be disabled.
* Select an Existing Customer from the list.
** All fields below will be populated from the Customer's address information.
** The check-box will be enabled, indicating that you are using the Customer's address as the delivery address.
** Only the check-box will be an enabled field - all others will be disabled.

Un-checking the check box will enable all the entry fields, which will remain populated with the default values from the customer address.

Clicking '''Save''' will create the Job. If a new customer is being created, the address entered will be assigned to the customer. If a delivery address has been chosen that is different to the selected existing customer (or no customer has been selected), the address will be saved to the Job address.

The following columns will be removed from the grid:
* Site ID
* Job Instructions
* Office Instructions
* Reason Code
* Configure
* Details
* Report

The Status field will be modified to show the Reason Code and Description entered for a cancelled job in a tool-tip (activated by hovering the mouse pointer over the Status).

The grid will be modified to not allow direct entry. Instead, the grid will use the Entry panel. This will be activated by clicking once on the line, which will display the Entry panel, populated with the details of the line selected.

The functionality will differ to the Entry functionality, in that the Action buttons will be populated as follows:
* Details - Display any Container, Product or Service details associated to the job
* Report - Display the POD/POC/Service report (only enabled if the Job is at status Complete
* Cancel Job - Move a Job to Cancelled status.
* Image - Display any Image associated to the Job.

===Containers Screen===
*EPL_GROSS_WEIGHT - Visible against the container record and available for entry.
*EPL_COMMENT - Visible against the container record and available for entry.

===Job Products Screen===

*EPL_UNIT_TYPE - Visible against the product record and available for entry
*EPL_DESCRIPTION_LONG - Visible against the product record and available for entry
*EPL_PRODUCT_QTY_ORDERED - Visible against the product record and available for entry

===Site Maintenance Screen===
*EPL_EMAIL - Visible and editable.

===Job Group Maintenance Screen===

*EPL_CONTAINER_ONLY - Controls container only delivery - Visible and Editable
*EPL_JOB_DISPLAY - controls which element is displayed on the PDA device on the Job Detail screen as the Job Reference. The two options are Job Code or Job ID, defaulting to the latter.

===Transfer Configuration Screen===

A new audit and maintenance screen will be required.

This will allow users to search the EPOD_XF_AUDIT_HEADER table by EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_JOB_GROUP. With a later implementation allowing to search for EPL_JOB_ID, or EPL_LOAD_ID.

This screen will display the header records details, EPL_JOB_GROUP, EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_STATUS_DESCRIPTION, and EPL_REQUEST_DATA.
{{note|This would be best displayed within a popup of some kind. For future implementation, the editing and resending of this data may be needed. Doing so a link would need to be made to each job.
}}

== PDA Server ==

The message sent to the PDA client from the server will be modified so that the Job Address (if present) will be used in preference to the Customer address. The Container Weight field (EPL_GROSS_WEIGHT) must also be passed.

The Standing Data Configuration must be changed to pass the new control flags to the device (e.g. EPL_JOB_DISPLAY).

== PDA Client ==

The DB changes will need to be reflected on the PDA.

The PDA will need to be implemented with the functionality to transfer collection details to the delivery job, based on matching Job Codes. This includes altering the planned delivery quantity to the actual collection quantity specified in the collection.

The PDA will need to display Job Code rather than Job ID on the Job Detail screen, depending on the value of the new configuration flag.

The PDA will need to select the appropriate delivery or collection process based on the jobs attributes:
*Collections
**Proctors-Controlled Warehouse - Collection of Containers without Products
**Non-Proctors Location - Collection of Products without Containers
*Deliveries
**Proctors Collection - Delivery of Containers without Products.
**Non-Proctors Collection - Delivery of Products without Containers

When starting a collection or delivery from a Proctors-Controlled Warehouse a update check must be forced (this is currently handled under the standard process) if no container records are received, then an alert is given to the user advising that the data may not be up to date.

====Standard Collection====
The user will be able to long-press any container in the grid. This will provide a popup menu, allowing the user to see the details of the selected container. The PDA will display a screen displaying:
*ID
*Package Code and Description
*Weight

====Collection of Containers without Products====
This will check a parameter on the Job Group - if Container-only Collection is enabled and there are no loose products, the collection will continue as Container only, otherwise the standard (Products Without Containers) collection process will be used.

The user is presented with a list of Containers for collection. The user selects a container either through text entry or scanning. Users have the ability to short-deliver by container only and use the exception process to document any non-delivered containers. When all Containers are accounted for, the user is prompted to complete the job, with a customer signature.

Long-pressing on a container will display a pop-up menu with a Products option shown. If this is clicked, the PDA client will display a list of all products against the container. {{note}} This option should be available only if this is unit is configured for containers without products.

====Collection of Products without Containers====
The user is presented with a list of products for collection. The user confirms collection of each product as in the standard approach. When all Products are accounted for the user is prompted to complete the job, with a customer signature.

====Delivery of Products without Containers====
The process is the same as Collection of Products without Containers.

====Delivery of Containers without Products====
The process is the same as Collection of Containers without Products.

=== Photos ===
Photos will be captured using the standard exception process. User's must be aware that quality of the images will affect GPRS usage, higher quality equals longer more date to transfer. This can only be controlled on the PDA itself and must be set in the PDA's camera settings.

== New POD formats ==
New POD formats will be created for the operation.

The POD or POC format produced will be dependant on the Job Group associated to the Job.

All images captured relating to the Job will be displayed on a second page of the POD/POC document, with the associated detail information (Job ID, Container ID, Product Code, Image description). Again image quality is dependant on device settings, which affects the image size.

Fields on the Delivery Note document will be sourced from the following database fields:
* Delivery Note: EPL_JOB_CODE
* Customer Address: Address information from the Job's Customer
* Delivery Address: Address information from the Job's Address (if present) or the Customer's.
* Customer Tel No: From the Job's Address (if present) or the Customer.
* Cust No/Contact: From the Job's Address (if present) or the Customer.
* Our Order No: EPL_SO_NUMBER (New field)
* Order Date: EPL_ORDER_DATE (New Field)
* Customer Order No: EPL_CUST_REF
* PPB Contact: EPL_SALES_CONTACT (New Field)
* Product Reference: EPL_PRODUCT_CODE
* Product Description: EPL_DESCRIPTION and EPL_DESCRIPTION_LONG
* Due Date: EPL_START_PLANNED_DATE/TIME {{Note}} This is the same for all lines.
* Unit: EPL_UNIT_TYPE (New Field)
* Quantity: EPL_PRODUCT_QTY_ORDERED (New Field)
* Quantity Despatched: EPL_PRODUCT_QTY_PLANNED
* Quantity Delivered: EPL_PRODUCT_QTY_ACTUAL
* No Of Parcels: EPL_COMMENT of EPOD_CONTAINER (New field)
* Pallet ID: EPL_CONTAINER_ID
* Special Instructions: EPL_JOB_INSTRUCTION
* Total Weight: See below
* Delivered By: PDA User Name
* Print Name: EPL_CUST_SIGNATORY (entered by PDA user)
* Date: Job Completion Date
* Signed Unchecked: EPL_SIGNED_UNCHECKED (New Field)

Total Weight will be calculated at the container level. The weight must be passed through as part of the interfaced container record. If no containers have been interfaced, this field will be omitted.

{{Warning}}The following elements have been excluded from the design:
* Barcode
* Vat No
* Picked
* Converted

Fields on the Transfer Note document will be sourced from the following database fields (where different from the Delivery Note):
* Stock Transfer Note: EPL_JOB_CODE
* Transfer Stock From: From the Collection's Customer information
* Transfer Stock To: From the Delivery's Customer information
* Xfer Ref No: EPL_SO_NUMBER (New Field)
* Input By: EPL_SALES_CONTACT (New Field)
* Part Number: EPL_PRODUCT_ID
* Product Description: EPL_DESCRIPTION

{{Warning}}The following elements have been excluded from the design:
* Location
* Location Qty

{{Note}} The existing generic POD/POC format must be modified to check for the Job address before using the Customer's address.

{{Note}} There could be many pallets and stock codes on a collection or delivery. This will run into multiple pages regardless of which note is produced. In the case where multiple pages of information are displayed, the header, up to and including the ''Customer Tel No'' table, will be shown on every page, whereas the Signature footer table will be shown only on the first page, being omitted from all subsequent pages.

==PDF Production==
A new rule will be added at a Site level to control whether emails to customers will be HTML-Embedded or PDF attachment style.

The system will check this rule when:
# The "Email To" button is pressed on the "View POD" page
# auto-emailed documents are being produced.

If this rule is not enabled, the system will send emails as now (embedded HTML emails).

If this rule is enabled, the system will:
*Export and save the page to a temporary directory, with all images rendered.
*Run the saved page through a conversion routine to convert the HTML to a PDF page (saved in the same directory).
*Attach this generated PDF to the email and send
*Delete the temporary folder.

The conversion routine will use the WkHtmlToPDF program with default parameters - this must be installed on the server.

==Auto-Email==
The Auto-email code will be moved into the new batch Auto-Export Process.

The update of a job to complete or cancelled will result in the new field EPL_EMAIL_FLAG being set to "N". The batch process will retrieve all job records where this flag is "N" and the Job Group or Site associated to the job requires auto-email.

The process will iterate through these records and retrieve the email addresses that the job should be emailed to from the Site, Job and Customer records.

If no emails have been specified, EPL_EMAIL_FLAG will set to "X".

If an email address has been specified, the email will be built as per the current process and sent to the defined email address. EPL_EMAIL_FLAG will set to "Y".



= Appendix A: POD Formats =
[[File:Delivery Note.jpg|600px|border]]

[[File:Stock Transfer Note.jpg|600px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|REQ=0
|EST=0
|FS=5.0
|TS=0
|DEV=36
|ST=5.00
|IMP=2.0
|Client={{#var:Client}}
|Year=2012
|FSEST=N
|Rev1=Matt Turner
|Rev1Title=OBS Representative
|Rev2=Stephen McCartney
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 294838 Proctor ePOD Modifications

2012-03-01T12:01:09Z

Milesl: Changes made to Import Responce

<div class="noprint">
{{#vardefine:Client|PROC}}
{{#vardefine:ClientName|Proctors}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Proctors ePOD Modifications}}
{{#vardefine:Version|1.0}}
{{#vardefine:Date|22nd February 2012}}
{{#vardefine:Reference|294838}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==

== Solution Overview ==

The ERP system will be able to interface Customer data to the ''CALIDUS'' EPOD system, to identify the customer address, contact and email information.

{{Note}} Customers can also be created through the standard Job interface - if this is the case, then the Job address provided with the first job for this customer will become the customer address.

Jobs will be received for Collection and Delivery from the following main customer types:
*Suppliers
*Customers
*Proctors-operated Warehouses
*3rd Party Warehouses

The jobs will be updated into the ''CALIDUS'' EPOD system through the standard WebService interface.

This job upload will create 2 tasks:
*A Collection Job
*A Delivery Job

Every Collection and Delivery will be specified separately within the interface, with the Product and Quantity specified for all jobs. Linked collections and deliveries will have the same Job Code, but will be distinguished by the Job Type (i.e. Collection or Delivery).

The Upload system will also identify the Loads onto which jobs are planned, as all planning is completed through the Proctors' ERP system.

In phase 1, the initial uploads will be sent to the EPOD system with either no load information, or with the load ID set to a default value.

In phase 2, the initial uploads will be sent tot he EPOD system with either no load information, or with the correct load identified against them. It will then be possible to subsequently update the Load for a job through another update of the Job alone.

There are two types of job:
* Customer/Supplier jobs - jobs that begin or end with a Customer or Supplier.
* Inter-warehouse Transfer - jobs that begin and end from Warehouses

All jobs will be categorised by the ''CALIDUS'' EPOD Job Group into one of the two categories - this will define the paperwork produced by the system when the job is completed. The Job Group will be agreed and sent to the system in the upload files.

Once jobs from Proctors-controlled warehouses are picked and marshalled, updated Jobs will be sent to the EPOD system, detailing the actual containers (pallets) and product quantities on each.

{{Note}} If this data is not available at the time of collecting or delivering the associated jobs, the system will check periodically through a regularly-scheduled automatic process.

Collection jobs from a Proctors-operated warehouse should then have containers and product quantities specified against them. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.

{{Warning}} In this circumstance, where pallet information has not been received, the automatic update of the job when complete will identify on product and quantity information, not pallet information.

The process for a Collection of this type will be:
* Confirm arrival to warehouse.
* Scan/Enter/Select Pallets to be collected.
* Once completed, confirm collection through depot signature.
The user will also be able to long-press against any container to show the details of any products contained within it.

Collection jobs from a Customer, Supplier or 3rd party warehouse (i.e. non-Proctors) will have the Product and Quantity created against them (i.e. no containers/pallets). The process will be:
* Confirm arrival to customer/supplier/warehouse.
* Scan/Enter/Select Products to be collected.
* Confirm total quantity of the products.
* Once completed, confirm collection through customer/supplier signature.

A Delivery of a non-Proctors job will have only product and quantity details. The process will be:
* Confirm arrival to customer.
* Scan/Enter/Select Products to be delivered.
* Confirm total quantity of the products.
* Once completed, confirm delivery through customer signature.

A Delivery of Proctors job should have container (pallet), product and quantities. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.
The process will be:
* Confirm arrival to customer/depot.
* Scan/Enter/Select pallets being delivered
* Once completed, confirm delivery through customer/depot signature.

{{Note}} The system will be configurable to allow the PDA unit to display Job Code rather than Job ID on the Job Detail screen.

Two new POD document formats will be created:
* A Delivery format, configured for use on Customer/Supplier jobs.
* A Transfer format, configured for use on Inter-warehouse Transfers.
These formats will be defined against the Job group provided on the upload.
In order for these to be created to match the current formats as closely as possible, the ''CALIDUS'' EPOD Job Import will be extended to add new fields, identified in detail later in the document.

''CALIDUS'' EPOD will be set up to allow certain customers to be automatically emailed upon completion of jobs to and from them. When enabled, the format associated to the Job Group will be sent to the Customer's associated email address, if there is one. This will also be sent to an email address against the site, if there is one, ensuring that the ERP system is provided copies of the produced PDF files.

{{Note}} Email notification of the POD or POC will be attempted if this feature is turned on and if the customer has an email address. If depots or suppliers do not require notification of collections or deliveries, it must be ensured that the customers created do not have an email address.

Confirmation or cancellation of any job will trigger an automatic update of the ERP system. This will be configurable but is expected to be through an email of the standard EPOD XML job update message. This update will be a scheduled process that will regularly check and attempt to update when possible. It will be scheduled to run as often as required by the client, up to once per minute.

== Scope ==



= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
The two new fixed Job Groups will be set up for Proctors-controlled warehouses and 3rd-party. The former will be configured with the Stock Transfer POD format, whilst the latter will be configured with the other format.


= Functional Description =
The total changes required are:
* Database
* Job Import/Export
* Customers Import
* Auto-Export
* Auto-Email
* Admin
* PDA Client
** Delivery/Collection Without Products
* New POD formats
* PDF Production

== Database Changes ==

=== EPOD_SITE ===
A new flag will be added for the Site Email Address for auto-email, called EPL_EMAIL

=== EPOD_JOB ===
New Fields:
*EPL_SIGNED_UNCHECKED
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number
*EPL_ORDER_DATE
*EPL_SALES_CONTACT - PPB Contact
*EPL_XFER_FLAG - default to ""
*EPL_EMAIL_FLAG - default to ""

Changes:
*Indexing applied to EPL_JOB_CODE, EPL_JOB_TYPE. This will be a repeating index.
*Indexing applied to EPL_XFER_FLAG. This will be a repeating index.
*Indexing applied to EPL_EMAIL_FLAG. This will be a repeating index.

=== EPOD_CONTAINER ===

*EPL_GROSS_WEIGHT - a floating point number.
*EPL_COMMENT - a maximum length text field.

=== EPOD_PRODUCT ===

*EPL_UNIT_TYPE
*EPL_DESCRIPTION_LONG
*EPL_PRODUCT_QTY_ORDERED

=== EPOD_JOB_GROUP ===

*EPL_CONTAINER_ONLY - Controls container-only delivery
*EPL_JOB_DISPLAY - controls whether Job ID or Job Code is displayed on the PDA.

=== XF_CONFIG ===

EPOD_JOB will require a new field of two characters EPL_XFER_FLAG, this will be defaulted to "".
EPOD_SITE and EPOD_JOB_GROUP will require a new field EPL_XF_CONFIG which will link to the EPL_XF_CONFIG_ID. If no export is required this will be blank.

A new table EPOD_XF_CONFIG will be created consisting of:
*EPL_XF_CONFIG_ID: A ten character unique field
*EPL_DESCRIPTION
*EPL_XF_TYPE: A ten character field identifying the type of export (SOAP, File, Email)
*EPL_XF_DESTINATION: A 255 character field identifying the destination of the export
*EPL_XF_PARM: Additional parameters for example subject for email

A new table EPOD_XF_AUDIT_HEADER will be created consisting of:
*EPL_HEADER_ID: A unique auto-increment Id
*EPL_SITE_ID: Indexed
*EPL_JOB_GROUP: Indexed
*EPL_REQUEST_DATA: A maximum length free-text field
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)

A new table EPOD_XF_AUDIT_DETAIL will be created consisting of:
*EPL_HEADER_ID: Foreign key to EPOD_XF_AUDIT_HEADER
*EPL_DETAIL_ID: A unique auto-increment Id
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)
{{Note}} This table is for future development and will not be used at this time.

=== JOB_ADDRESS ===
A new table EPOD_JOB_ADDRESS will be created consisting of:
*EPL_SITE_ID: Foreign key to EPOD_SITE
*EPL_JOB_ID: Foreign key to EPOD_JOB
*EPL_ADDRESS_LINE_1
*EPL_ADDRESS_LINE_2
*EPL_ADDRESS_LINE_3
*EPL_ADDRESS_LINE_4
*EPL_POST_CODE
*EPL_CONTACT
*EPL_TELEPHONE
*EPL_EMAIL
*EPL_LAST_CHANGE_DATE
*EPL_LAST_CHANGE_TIME
The table will be indexed on EPL_SITE_ID and EPL_JOB_ID.

== XML Interface ==

=== Job Import ===

The system shall use the EPL_JOB_CODE field as a reference linking the delivery and collection, the index used shall be EPL_JOB_CODE and EPL_JOB_TYPE. The field EPL_JOB_ID will always be unique, this will be auto-generated by our system if not passed in.

The import can include an optional EPOD_CUSTOMER tag. This is used in preference to the CUSTOMER_NAME and CUSTOMER_CODE tags to update Customer address information. The supplied information against the job is then used exclusively for the Job Address, if different. So for Proctor both the standard adress section with the job message will be completed, mapping to the delivery address (EPOD_JOB_ADDRESS) and the EPOD_CUSTOMER tag will be populated updating the customer address.

The Import XML structure will have a attribute of ID. This will not be stored within the system, instead this will be stamped on the responding message from the web service. Within the responce the EPL_JOB_CODE field will be added to any job records returned in the import confirmation.

Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST" ID="XXXXX">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

The following XML would have the same outcome as above without the generation of container records:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

Both the collection and delivery must share the same EPL_JOB_CODE reference.

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>.
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>

==== Job Update ====

To update the jobs with the Container details, Proctors' ERP must follow the same standard structure as the import.
All Job, Container and Product tags that are populated and present will update the relevant details in the ''CALIDUS'' EPOD system.

{{Note}}
* If the EPL_JOB_ID is blank (as expected for the Proctors interface, as the Collection and Deliveries will be linked via EPL_JOB_CODE), the system will check to see whether a job exists for this EPL_JOB_CODE and EPL_JOB_TYPE. If so, the record will be updated. If not, a new record (with a generated EPL_JOB_ID) will be created.
* If the EPL_JOB_ID is not blank, the system will check to see whether a job exists for this EPL_JOB_ID. If so, the record will be updated. If not, a new record will be created with this EPL_JOB_ID.
* If the EPL_LOAD_ID is left blank, the system will not update the Load ID of the Job.
* If the EPOD_CONTAINERS tag is not populated, the system will not update any container information. If it is present, the system will delete any existing container information and replace it with the information in the containers tag.
* If the EPOD_PRODUCTS tag is not populated, the system will not update any product information. If it is present, the system will delete any existing product information and replace it with the information in the product tag.
* The import can include an optional EPOD_CUSTOMER tag. This is used in preference to the CUSTOMER_NAME and CUSTOMER_CODE tags to update Customer address information. The supplied information against the job is then used exclusively for the Job Address, if different.

Changes will be made to the Customer Address import to ensure that a customer and a job can have defined addresses, as follows:
* If the EPOD_CUSTOMER tag exists in the message
** Pass the contents of the tag to the Customer Import, to update the Customer details
** Use the address information in the message to update the Job Address.
* Else
**If the Customer Code exists in the message
*** the system will check that the record exists within the database with that code.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created with that code.
** If not, and the Customer Name exists
*** the system will check that the record exists within the database with that name.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created and a code generated for it.
** If neither Code nor Name exist, the system will store the address information against the Job.

=== Job Export ===

At the point of job status changed the system will export the Jobs structure using the standard XML and send this to a predefined email address, for interfacing with the ERP system. This will be configured using the XF_CONFIG section of the system.

The required email functionality will need to be added to the existing export process.

The following XML is produced by the export, this example shows the export with multiple Jobs:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PHOTO_ID/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/> <EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575903</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

The following XML is produced by the export, this example shows the export with a single Job:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

==== Auto-Export Process ====

Whenever a job is updated to Cancelled or Complete (i.e. when the jobs are updated by the PDA client, or when jobs are updated via the Admin system), after committing the changes to the database, the Auto Export flag will be checked against the Job Group and Site. If this flag is present the EPL_JOB record will have the EPL_XFER_FLAG set to N, to indicate that the record requires interfacing but has not yet been sent.

{{Note}} These changes will be committed into the Data Access Layer, so that the same code will be called whether running this through the Admin or PDA server functions.

A timed process will be running to send any Jobs with the Xfer flag of N.
The process will:
*Retrieve all jobs on the EPL_JOBS table with the Xfer flag set to N, sorted by Site and Job Group.
*For each record found in distinct Site and Job Group:
**Load the details of this Job ID,
**Generate the XML export as per the standard for currently existing exports
**Once all jobs for the Site/Job Group are exported:
***Get the configuration of the Job Group. If the configuration for the Job Group does not exist, get the configuration for the Site.
***Attempt to transfer this to the destination specified in the configuration.

If this process if successful then the Xfer flag on the Job record will be set to Y, and a success audit record written.
If this fails the flag on the job will be set to N and a record will be written to a audit table with details of the failure.
If the file is send successfully but a message is received from the destination advising of this problem then an audit record will be written and the flag will be set to N.

This timed process will be scheduled on the system. The frequency of the process will be defined by the schedule and can be no more frequent that one per minute. If the process is already running, the process will wait for the next cycle before starting.

The status of the audit records based on the result are:
* S for success;
* SF for success send but error at the receivers, and;
* F for failure to send.
These records will be cleared down once they are older than 7 days.

===Customer Import===
Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_CUSTOMERS>
<EPOD_CUSTOMER>
<EPL_SITE_ID>Dave Jones</EPL_SITE_ID>
<EPL_CUSTOMER_CODE>CUST01</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
</EPOD_CUSTOMERS>

Similarly to the Job import:
* If the Customer Code exists in the message
** the system will check that the record exists within the database with that code.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created.
* If not, and the Customer Name exists
** the system will check that the record exists within the database with that name.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created and a code generated for it.
* If neither exist, the system will not import the customer.

== Admin System ==

Within Phase one the Admin interface will be used to plan Jobs onto loads, all required functionality has been implemented. Within phase two this will not be required as Proctors will interface pre-planned loads.
The following changes will need to be made to the admin system to reflect the database changes:

===Jobs Screen===

*EPL_SIGNED_UNCHECKED - Visible on the POD only, this field is not searchable
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number - Entry only
*EPL_ORDER_DATE - Entry only
*EPL_SALES_CONTACT - PPB Contact - Entry only
*EPOD_JOB_ADDRESS.

In order to accommodate the new fields and allow them to be displayed and entered, the Job screen must be extensively modified.

The Entry panel will be modified to allow entry of the following fields, in two adjacent panels, as below:
<table border="solid black 1px">
<tr><td colspan="2"> '''[Edit buttons]''' </td></tr>
<tr><td width="50%">
Job Type

Job Code

Job Group

Cust Ref

'''Dnote No'''

Planned Date/Time

'''Order Date/Time'''

Sales Contact

Job/Office Instructions

</td><td width="50%">
Customer Code

Use Customer Address as Delivery Address?

'''New Customer Code'''

'''New Customer Name'''

''Address 1''

''Address 2''

''Address 3''

''Address 4''

''Postcode''

''Contact''

''Email''

''Telephone''
</td></tr>
<tr><td colspan="2"> '''[Save] [Cancel]'''</td></tr>
</table>

All fields in '''Bold''' are new fields. All fields in ''Italics'' are new functionality.

The ''Edit'' buttons will not be shown in entry mode.

The left side of the screen will show all the Job-related fields for entry, including the new fields.

The right side of the screen will be the area to identify the customer and address.

The Instructions entry will be through a tabbed entry box. The first tab will contain the Job Instructions and will be displayed. The second tab can be clicked on to edit the Office Instructions.

The Customer drop-down will allow you to select:
* ''No Customer''
** All entry fields (bar Customer Code and Name) below will be enabled.
** The check-box will be disabled.
* ''Create a New Customer'':
** All entry fields below will be enabled.
** Customer Code and Name must be entered
** The check-box will be disabled.
* Select an Existing Customer from the list.
** All fields below will be populated from the Customer's address information.
** The check-box will be enabled, indicating that you are using the Customer's address as the delivery address.
** Only the check-box will be an enabled field - all others will be disabled.

Un-checking the check box will enable all the entry fields, which will remain populated with the default values from the customer address.

Clicking '''Save''' will create the Job. If a new customer is being created, the address entered will be assigned to the customer. If a delivery address has been chosen that is different to the selected existing customer (or no customer has been selected), the address will be saved to the Job address.

The following columns will be removed from the grid:
* Site ID
* Job Instructions
* Office Instructions
* Reason Code
* Configure
* Details
* Report

The Status field will be modified to show the Reason Code and Description entered for a cancelled job in a tool-tip (activated by hovering the mouse pointer over the Status).

The grid will be modified to not allow direct entry. Instead, the grid will use the Entry panel. This will be activated by clicking once on the line, which will display the Entry panel, populated with the details of the line selected.

The functionality will differ to the Entry functionality, in that the Action buttons will be populated as follows:
* Details - Display any Container, Product or Service details associated to the job
* Report - Display the POD/POC/Service report (only enabled if the Job is at status Complete
* Cancel Job - Move a Job to Cancelled status.
* Image - Display any Image associated to the Job.

===Containers Screen===
*EPL_GROSS_WEIGHT - Visible against the container record and available for entry.
*EPL_COMMENT - Visible against the container record and available for entry.

===Job Products Screen===

*EPL_UNIT_TYPE - Visible against the product record and available for entry
*EPL_DESCRIPTION_LONG - Visible against the product record and available for entry
*EPL_PRODUCT_QTY_ORDERED - Visible against the product record and available for entry

===Site Maintenance Screen===
*EPL_EMAIL - Visible and editable.

===Job Group Maintenance Screen===

*EPL_CONTAINER_ONLY - Controls container only delivery - Visible and Editable
*EPL_JOB_DISPLAY - controls which element is displayed on the PDA device on the Job Detail screen as the Job Reference. The two options are Job Code or Job ID, defaulting to the latter.

===Transfer Configuration Screen===

A new audit and maintenance screen will be required.

This will allow users to search the EPOD_XF_AUDIT_HEADER table by EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_JOB_GROUP. With a later implementation allowing to search for EPL_JOB_ID, or EPL_LOAD_ID.

This screen will display the header records details, EPL_JOB_GROUP, EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_STATUS_DESCRIPTION, and EPL_REQUEST_DATA.
{{note|This would be best displayed within a popup of some kind. For future implementation, the editing and resending of this data may be needed. Doing so a link would need to be made to each job.
}}

== PDA Server ==

The message sent to the PDA client from the server will be modified so that the Job Address (if present) will be used in preference to the Customer address. The Container Weight field (EPL_GROSS_WEIGHT) must also be passed.

The Standing Data Configuration must be changed to pass the new control flags to the device (e.g. EPL_JOB_DISPLAY).

== PDA Client ==

The DB changes will need to be reflected on the PDA.

The PDA will need to be implemented with the functionality to transfer collection details to the delivery job, based on matching Job Codes. This includes altering the planned delivery quantity to the actual collection quantity specified in the collection.

The PDA will need to display Job Code rather than Job ID on the Job Detail screen, depending on the value of the new configuration flag.

The PDA will need to select the appropriate delivery or collection process based on the jobs attributes:
*Collections
**Proctors-Controlled Warehouse - Collection of Containers without Products
**Non-Proctors Location - Collection of Products without Containers
*Deliveries
**Proctors Collection - Delivery of Containers without Products.
**Non-Proctors Collection - Delivery of Products without Containers

When starting a collection or delivery from a Proctors-Controlled Warehouse a update check must be forced (this is currently handled under the standard process) if no container records are received, then an alert is given to the user advising that the data may not be up to date.

====Standard Collection====
The user will be able to long-press any container in the grid. This will provide a popup menu, allowing the user to see the details of the selected container. The PDA will display a screen displaying:
*ID
*Package Code and Description
*Weight

====Collection of Containers without Products====
This will check a parameter on the Job Group - if Container-only Collection is enabled and there are no loose products, the collection will continue as Container only, otherwise the standard (Products Without Containers) collection process will be used.

The user is presented with a list of Containers for collection. The user selects a container either through text entry or scanning. Users have the ability to short-deliver by container only and use the exception process to document any non-delivered containers. When all Containers are accounted for, the user is prompted to complete the job, with a customer signature.

Long-pressing on a container will display a pop-up menu with a Products option shown. If this is clicked, the PDA client will display a list of all products against the container. {{note}} This option should be available only if this is unit is configured for containers without products.

====Collection of Products without Containers====
The user is presented with a list of products for collection. The user confirms collection of each product as in the standard approach. When all Products are accounted for the user is prompted to complete the job, with a customer signature.

====Delivery of Products without Containers====
The process is the same as Collection of Products without Containers.

====Delivery of Containers without Products====
The process is the same as Collection of Containers without Products.

=== Photos ===
Photos will be captured using the standard exception process. User's must be aware that quality of the images will affect GPRS usage, higher quality equals longer more date to transfer. This can only be controlled on the PDA itself and must be set in the PDA's camera settings.

== New POD formats ==
New POD formats will be created for the operation.

The POD or POC format produced will be dependant on the Job Group associated to the Job.

All images captured relating to the Job will be displayed on a second page of the POD/POC document, with the associated detail information (Job ID, Container ID, Product Code, Image description). Again image quality is dependant on device settings, which affects the image size.

Fields on the Delivery Note document will be sourced from the following database fields:
* Delivery Note: EPL_JOB_CODE
* Customer Address: Address information from the Job's Customer
* Delivery Address: Address information from the Job's Address (if present) or the Customer's.
* Customer Tel No: From the Job's Address (if present) or the Customer.
* Cust No/Contact: From the Job's Address (if present) or the Customer.
* Our Order No: EPL_SO_NUMBER (New field)
* Order Date: EPL_ORDER_DATE (New Field)
* Customer Order No: EPL_CUST_REF
* PPB Contact: EPL_SALES_CONTACT (New Field)
* Product Reference: EPL_PRODUCT_CODE
* Product Description: EPL_DESCRIPTION and EPL_DESCRIPTION_LONG
* Due Date: EPL_START_PLANNED_DATE/TIME {{Note}} This is the same for all lines.
* Unit: EPL_UNIT_TYPE (New Field)
* Quantity: EPL_PRODUCT_QTY_ORDERED (New Field)
* Quantity Despatched: EPL_PRODUCT_QTY_PLANNED
* Quantity Delivered: EPL_PRODUCT_QTY_ACTUAL
* No Of Parcels: EPL_COMMENT of EPOD_CONTAINER (New field)
* Pallet ID: EPL_CONTAINER_ID
* Special Instructions: EPL_JOB_INSTRUCTION
* Total Weight: See below
* Delivered By: PDA User Name
* Print Name: EPL_CUST_SIGNATORY (entered by PDA user)
* Date: Job Completion Date
* Signed Unchecked: EPL_SIGNED_UNCHECKED (New Field)

Total Weight will be calculated at the container level. The weight must be passed through as part of the interfaced container record. If no containers have been interfaced, this field will be omitted.

{{Warning}}The following elements have been excluded from the design:
* Barcode
* Vat No
* Picked
* Converted

Fields on the Transfer Note document will be sourced from the following database fields (where different from the Delivery Note):
* Stock Transfer Note: EPL_JOB_CODE
* Transfer Stock From: From the Collection's Customer information
* Transfer Stock To: From the Delivery's Customer information
* Xfer Ref No: EPL_SO_NUMBER (New Field)
* Input By: EPL_SALES_CONTACT (New Field)
* Part Number: EPL_PRODUCT_ID
* Product Description: EPL_DESCRIPTION

{{Warning}}The following elements have been excluded from the design:
* Location
* Location Qty

{{Note}} The existing generic POD/POC format must be modified to check for the Job address before using the Customer's address.

{{Note}} There could be many pallets and stock codes on a collection or delivery. This will run into multiple pages regardless of which note is produced. In the case where multiple pages of information are displayed, the header, up to and including the ''Customer Tel No'' table, will be shown on every page, whereas the Signature footer table will be shown only on the first page, being omitted from all subsequent pages.

==PDF Production==
A new rule will be added at a Site level to control whether emails to customers will be HTML-Embedded or PDF attachment style.

The system will check this rule when:
# The "Email To" button is pressed on the "View POD" page
# auto-emailed documents are being produced.

If this rule is not enabled, the system will send emails as now (embedded HTML emails).

If this rule is enabled, the system will:
*Export and save the page to a temporary directory, with all images rendered.
*Run the saved page through a conversion routine to convert the HTML to a PDF page (saved in the same directory).
*Attach this generated PDF to the email and send
*Delete the temporary folder.

The conversion routine will use the WkHtmlToPDF program with default parameters - this must be installed on the server.

==Auto-Email==
The Auto-email code will be moved into the new batch Auto-Export Process.

The update of a job to complete or cancelled will result in the new field EPL_EMAIL_FLAG being set to "N". The batch process will retrieve all job records where this flag is "N" and the Job Group or Site associated to the job requires auto-email.

The process will iterate through these records and retrieve the email addresses that the job should be emailed to from the Site, Job and Customer records.

If no emails have been specified, EPL_EMAIL_FLAG will set to "X".

If an email address has been specified, the email will be built as per the current process and sent to the defined email address. EPL_EMAIL_FLAG will set to "Y".



= Appendix A: POD Formats =
[[File:Delivery Note.jpg|600px|border]]

[[File:Stock Transfer Note.jpg|600px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|REQ=0
|EST=0
|FS=5.0
|TS=0
|DEV=36
|ST=5.00
|IMP=2.0
|Client={{#var:Client}}
|Year=2012
|FSEST=N
|Rev1=Matt Turner
|Rev1Title=OBS Representative
|Rev2=Stephen McCartney
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 294838 Proctor ePOD Modifications

2012-03-01T11:58:57Z

Milesl: /* Job Import */

<div class="noprint">
{{#vardefine:Client|PROC}}
{{#vardefine:ClientName|Proctors}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Proctors ePOD Modifications}}
{{#vardefine:Version|1.0}}
{{#vardefine:Date|22nd February 2012}}
{{#vardefine:Reference|294838}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==

== Solution Overview ==

The ERP system will be able to interface Customer data to the ''CALIDUS'' EPOD system, to identify the customer address, contact and email information.

{{Note}} Customers can also be created through the standard Job interface - if this is the case, then the Job address provided with the first job for this customer will become the customer address.

Jobs will be received for Collection and Delivery from the following main customer types:
*Suppliers
*Customers
*Proctors-operated Warehouses
*3rd Party Warehouses

The jobs will be updated into the ''CALIDUS'' EPOD system through the standard WebService interface.

This job upload will create 2 tasks:
*A Collection Job
*A Delivery Job

Every Collection and Delivery will be specified separately within the interface, with the Product and Quantity specified for all jobs. Linked collections and deliveries will have the same Job Code, but will be distinguished by the Job Type (i.e. Collection or Delivery).

The Upload system will also identify the Loads onto which jobs are planned, as all planning is completed through the Proctors' ERP system.

In phase 1, the initial uploads will be sent to the EPOD system with either no load information, or with the load ID set to a default value.

In phase 2, the initial uploads will be sent tot he EPOD system with either no load information, or with the correct load identified against them. It will then be possible to subsequently update the Load for a job through another update of the Job alone.

There are two types of job:
* Customer/Supplier jobs - jobs that begin or end with a Customer or Supplier.
* Inter-warehouse Transfer - jobs that begin and end from Warehouses

All jobs will be categorised by the ''CALIDUS'' EPOD Job Group into one of the two categories - this will define the paperwork produced by the system when the job is completed. The Job Group will be agreed and sent to the system in the upload files.

Once jobs from Proctors-controlled warehouses are picked and marshalled, updated Jobs will be sent to the EPOD system, detailing the actual containers (pallets) and product quantities on each.

{{Note}} If this data is not available at the time of collecting or delivering the associated jobs, the system will check periodically through a regularly-scheduled automatic process.

Collection jobs from a Proctors-operated warehouse should then have containers and product quantities specified against them. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.

{{Warning}} In this circumstance, where pallet information has not been received, the automatic update of the job when complete will identify on product and quantity information, not pallet information.

The process for a Collection of this type will be:
* Confirm arrival to warehouse.
* Scan/Enter/Select Pallets to be collected.
* Once completed, confirm collection through depot signature.
The user will also be able to long-press against any container to show the details of any products contained within it.

Collection jobs from a Customer, Supplier or 3rd party warehouse (i.e. non-Proctors) will have the Product and Quantity created against them (i.e. no containers/pallets). The process will be:
* Confirm arrival to customer/supplier/warehouse.
* Scan/Enter/Select Products to be collected.
* Confirm total quantity of the products.
* Once completed, confirm collection through customer/supplier signature.

A Delivery of a non-Proctors job will have only product and quantity details. The process will be:
* Confirm arrival to customer.
* Scan/Enter/Select Products to be delivered.
* Confirm total quantity of the products.
* Once completed, confirm delivery through customer signature.

A Delivery of Proctors job should have container (pallet), product and quantities. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.
The process will be:
* Confirm arrival to customer/depot.
* Scan/Enter/Select pallets being delivered
* Once completed, confirm delivery through customer/depot signature.

{{Note}} The system will be configurable to allow the PDA unit to display Job Code rather than Job ID on the Job Detail screen.

Two new POD document formats will be created:
* A Delivery format, configured for use on Customer/Supplier jobs.
* A Transfer format, configured for use on Inter-warehouse Transfers.
These formats will be defined against the Job group provided on the upload.
In order for these to be created to match the current formats as closely as possible, the ''CALIDUS'' EPOD Job Import will be extended to add new fields, identified in detail later in the document.

''CALIDUS'' EPOD will be set up to allow certain customers to be automatically emailed upon completion of jobs to and from them. When enabled, the format associated to the Job Group will be sent to the Customer's associated email address, if there is one. This will also be sent to an email address against the site, if there is one, ensuring that the ERP system is provided copies of the produced PDF files.

{{Note}} Email notification of the POD or POC will be attempted if this feature is turned on and if the customer has an email address. If depots or suppliers do not require notification of collections or deliveries, it must be ensured that the customers created do not have an email address.

Confirmation or cancellation of any job will trigger an automatic update of the ERP system. This will be configurable but is expected to be through an email of the standard EPOD XML job update message. This update will be a scheduled process that will regularly check and attempt to update when possible. It will be scheduled to run as often as required by the client, up to once per minute.

== Scope ==



= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
The two new fixed Job Groups will be set up for Proctors-controlled warehouses and 3rd-party. The former will be configured with the Stock Transfer POD format, whilst the latter will be configured with the other format.


= Functional Description =
The total changes required are:
* Database
* Job Import/Export
* Customers Import
* Auto-Export
* Auto-Email
* Admin
* PDA Client
** Delivery/Collection Without Products
* New POD formats
* PDF Production

== Database Changes ==

=== EPOD_SITE ===
A new flag will be added for the Site Email Address for auto-email, called EPL_EMAIL

=== EPOD_JOB ===
New Fields:
*EPL_SIGNED_UNCHECKED
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number
*EPL_ORDER_DATE
*EPL_SALES_CONTACT - PPB Contact
*EPL_XFER_FLAG - default to ""
*EPL_EMAIL_FLAG - default to ""

Changes:
*Indexing applied to EPL_JOB_CODE, EPL_JOB_TYPE. This will be a repeating index.
*Indexing applied to EPL_XFER_FLAG. This will be a repeating index.
*Indexing applied to EPL_EMAIL_FLAG. This will be a repeating index.

=== EPOD_CONTAINER ===

*EPL_GROSS_WEIGHT - a floating point number.
*EPL_COMMENT - a maximum length text field.

=== EPOD_PRODUCT ===

*EPL_UNIT_TYPE
*EPL_DESCRIPTION_LONG
*EPL_PRODUCT_QTY_ORDERED

=== EPOD_JOB_GROUP ===

*EPL_CONTAINER_ONLY - Controls container-only delivery
*EPL_JOB_DISPLAY - controls whether Job ID or Job Code is displayed on the PDA.

=== XF_CONFIG ===

EPOD_JOB will require a new field of two characters EPL_XFER_FLAG, this will be defaulted to "".
EPOD_SITE and EPOD_JOB_GROUP will require a new field EPL_XF_CONFIG which will link to the EPL_XF_CONFIG_ID. If no export is required this will be blank.

A new table EPOD_XF_CONFIG will be created consisting of:
*EPL_XF_CONFIG_ID: A ten character unique field
*EPL_DESCRIPTION
*EPL_XF_TYPE: A ten character field identifying the type of export (SOAP, File, Email)
*EPL_XF_DESTINATION: A 255 character field identifying the destination of the export
*EPL_XF_PARM: Additional parameters for example subject for email

A new table EPOD_XF_AUDIT_HEADER will be created consisting of:
*EPL_HEADER_ID: A unique auto-increment Id
*EPL_SITE_ID: Indexed
*EPL_JOB_GROUP: Indexed
*EPL_REQUEST_DATA: A maximum length free-text field
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)

A new table EPOD_XF_AUDIT_DETAIL will be created consisting of:
*EPL_HEADER_ID: Foreign key to EPOD_XF_AUDIT_HEADER
*EPL_DETAIL_ID: A unique auto-increment Id
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)
{{Note}} This table is for future development and will not be used at this time.

=== JOB_ADDRESS ===
A new table EPOD_JOB_ADDRESS will be created consisting of:
*EPL_SITE_ID: Foreign key to EPOD_SITE
*EPL_JOB_ID: Foreign key to EPOD_JOB
*EPL_ADDRESS_LINE_1
*EPL_ADDRESS_LINE_2
*EPL_ADDRESS_LINE_3
*EPL_ADDRESS_LINE_4
*EPL_POST_CODE
*EPL_CONTACT
*EPL_TELEPHONE
*EPL_EMAIL
*EPL_LAST_CHANGE_DATE
*EPL_LAST_CHANGE_TIME
The table will be indexed on EPL_SITE_ID and EPL_JOB_ID.

== XML Interface ==

=== Job Import ===

The system shall use the EPL_JOB_CODE field as a reference linking the delivery and collection, the index used shall be EPL_JOB_CODE and EPL_JOB_TYPE. The field EPL_JOB_ID will always be unique, this will be auto-generated by our system if not passed in.

The import can include an optional EPOD_CUSTOMER tag. This is used in preference to the CUSTOMER_NAME and CUSTOMER_CODE tags to update Customer address information. The supplied information against the job is then used exclusively for the Job Address, if different. So for Proctor both the standard adress section with the job message will be completed, mapping to the delivery address (EPOD_JOB_ADDRESS) and the EPOD_CUSTOMER tag will be populated updating the customer address.

Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

The following XML would have the same outcome as above without the generation of container records:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

Both the collection and delivery must share the same EPL_JOB_CODE reference.

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>.
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>

==== Job Update ====

To update the jobs with the Container details, Proctors' ERP must follow the same standard structure as the import.
All Job, Container and Product tags that are populated and present will update the relevant details in the ''CALIDUS'' EPOD system.

{{Note}}
* If the EPL_JOB_ID is blank (as expected for the Proctors interface, as the Collection and Deliveries will be linked via EPL_JOB_CODE), the system will check to see whether a job exists for this EPL_JOB_CODE and EPL_JOB_TYPE. If so, the record will be updated. If not, a new record (with a generated EPL_JOB_ID) will be created.
* If the EPL_JOB_ID is not blank, the system will check to see whether a job exists for this EPL_JOB_ID. If so, the record will be updated. If not, a new record will be created with this EPL_JOB_ID.
* If the EPL_LOAD_ID is left blank, the system will not update the Load ID of the Job.
* If the EPOD_CONTAINERS tag is not populated, the system will not update any container information. If it is present, the system will delete any existing container information and replace it with the information in the containers tag.
* If the EPOD_PRODUCTS tag is not populated, the system will not update any product information. If it is present, the system will delete any existing product information and replace it with the information in the product tag.
* The import can include an optional EPOD_CUSTOMER tag. This is used in preference to the CUSTOMER_NAME and CUSTOMER_CODE tags to update Customer address information. The supplied information against the job is then used exclusively for the Job Address, if different.

Changes will be made to the Customer Address import to ensure that a customer and a job can have defined addresses, as follows:
* If the EPOD_CUSTOMER tag exists in the message
** Pass the contents of the tag to the Customer Import, to update the Customer details
** Use the address information in the message to update the Job Address.
* Else
**If the Customer Code exists in the message
*** the system will check that the record exists within the database with that code.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created with that code.
** If not, and the Customer Name exists
*** the system will check that the record exists within the database with that name.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created and a code generated for it.
** If neither Code nor Name exist, the system will store the address information against the Job.

=== Job Export ===

At the point of job status changed the system will export the Jobs structure using the standard XML and send this to a predefined email address, for interfacing with the ERP system. This will be configured using the XF_CONFIG section of the system.

The required email functionality will need to be added to the existing export process.

The following XML is produced by the export, this example shows the export with multiple Jobs:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PHOTO_ID/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/> <EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575903</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

The following XML is produced by the export, this example shows the export with a single Job:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

==== Auto-Export Process ====

Whenever a job is updated to Cancelled or Complete (i.e. when the jobs are updated by the PDA client, or when jobs are updated via the Admin system), after committing the changes to the database, the Auto Export flag will be checked against the Job Group and Site. If this flag is present the EPL_JOB record will have the EPL_XFER_FLAG set to N, to indicate that the record requires interfacing but has not yet been sent.

{{Note}} These changes will be committed into the Data Access Layer, so that the same code will be called whether running this through the Admin or PDA server functions.

A timed process will be running to send any Jobs with the Xfer flag of N.
The process will:
*Retrieve all jobs on the EPL_JOBS table with the Xfer flag set to N, sorted by Site and Job Group.
*For each record found in distinct Site and Job Group:
**Load the details of this Job ID,
**Generate the XML export as per the standard for currently existing exports
**Once all jobs for the Site/Job Group are exported:
***Get the configuration of the Job Group. If the configuration for the Job Group does not exist, get the configuration for the Site.
***Attempt to transfer this to the destination specified in the configuration.

If this process if successful then the Xfer flag on the Job record will be set to Y, and a success audit record written.
If this fails the flag on the job will be set to N and a record will be written to a audit table with details of the failure.
If the file is send successfully but a message is received from the destination advising of this problem then an audit record will be written and the flag will be set to N.

This timed process will be scheduled on the system. The frequency of the process will be defined by the schedule and can be no more frequent that one per minute. If the process is already running, the process will wait for the next cycle before starting.

The status of the audit records based on the result are:
* S for success;
* SF for success send but error at the receivers, and;
* F for failure to send.
These records will be cleared down once they are older than 7 days.

===Customer Import===
Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_CUSTOMERS>
<EPOD_CUSTOMER>
<EPL_SITE_ID>Dave Jones</EPL_SITE_ID>
<EPL_CUSTOMER_CODE>CUST01</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
</EPOD_CUSTOMERS>

Similarly to the Job import:
* If the Customer Code exists in the message
** the system will check that the record exists within the database with that code.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created.
* If not, and the Customer Name exists
** the system will check that the record exists within the database with that name.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created and a code generated for it.
* If neither exist, the system will not import the customer.

== Admin System ==

Within Phase one the Admin interface will be used to plan Jobs onto loads, all required functionality has been implemented. Within phase two this will not be required as Proctors will interface pre-planned loads.
The following changes will need to be made to the admin system to reflect the database changes:

===Jobs Screen===

*EPL_SIGNED_UNCHECKED - Visible on the POD only, this field is not searchable
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number - Entry only
*EPL_ORDER_DATE - Entry only
*EPL_SALES_CONTACT - PPB Contact - Entry only
*EPOD_JOB_ADDRESS.

In order to accommodate the new fields and allow them to be displayed and entered, the Job screen must be extensively modified.

The Entry panel will be modified to allow entry of the following fields, in two adjacent panels, as below:
<table border="solid black 1px">
<tr><td colspan="2"> '''[Edit buttons]''' </td></tr>
<tr><td width="50%">
Job Type

Job Code

Job Group

Cust Ref

'''Dnote No'''

Planned Date/Time

'''Order Date/Time'''

Sales Contact

Job/Office Instructions

</td><td width="50%">
Customer Code

Use Customer Address as Delivery Address?

'''New Customer Code'''

'''New Customer Name'''

''Address 1''

''Address 2''

''Address 3''

''Address 4''

''Postcode''

''Contact''

''Email''

''Telephone''
</td></tr>
<tr><td colspan="2"> '''[Save] [Cancel]'''</td></tr>
</table>

All fields in '''Bold''' are new fields. All fields in ''Italics'' are new functionality.

The ''Edit'' buttons will not be shown in entry mode.

The left side of the screen will show all the Job-related fields for entry, including the new fields.

The right side of the screen will be the area to identify the customer and address.

The Instructions entry will be through a tabbed entry box. The first tab will contain the Job Instructions and will be displayed. The second tab can be clicked on to edit the Office Instructions.

The Customer drop-down will allow you to select:
* ''No Customer''
** All entry fields (bar Customer Code and Name) below will be enabled.
** The check-box will be disabled.
* ''Create a New Customer'':
** All entry fields below will be enabled.
** Customer Code and Name must be entered
** The check-box will be disabled.
* Select an Existing Customer from the list.
** All fields below will be populated from the Customer's address information.
** The check-box will be enabled, indicating that you are using the Customer's address as the delivery address.
** Only the check-box will be an enabled field - all others will be disabled.

Un-checking the check box will enable all the entry fields, which will remain populated with the default values from the customer address.

Clicking '''Save''' will create the Job. If a new customer is being created, the address entered will be assigned to the customer. If a delivery address has been chosen that is different to the selected existing customer (or no customer has been selected), the address will be saved to the Job address.

The following columns will be removed from the grid:
* Site ID
* Job Instructions
* Office Instructions
* Reason Code
* Configure
* Details
* Report

The Status field will be modified to show the Reason Code and Description entered for a cancelled job in a tool-tip (activated by hovering the mouse pointer over the Status).

The grid will be modified to not allow direct entry. Instead, the grid will use the Entry panel. This will be activated by clicking once on the line, which will display the Entry panel, populated with the details of the line selected.

The functionality will differ to the Entry functionality, in that the Action buttons will be populated as follows:
* Details - Display any Container, Product or Service details associated to the job
* Report - Display the POD/POC/Service report (only enabled if the Job is at status Complete
* Cancel Job - Move a Job to Cancelled status.
* Image - Display any Image associated to the Job.

===Containers Screen===
*EPL_GROSS_WEIGHT - Visible against the container record and available for entry.
*EPL_COMMENT - Visible against the container record and available for entry.

===Job Products Screen===

*EPL_UNIT_TYPE - Visible against the product record and available for entry
*EPL_DESCRIPTION_LONG - Visible against the product record and available for entry
*EPL_PRODUCT_QTY_ORDERED - Visible against the product record and available for entry

===Site Maintenance Screen===
*EPL_EMAIL - Visible and editable.

===Job Group Maintenance Screen===

*EPL_CONTAINER_ONLY - Controls container only delivery - Visible and Editable
*EPL_JOB_DISPLAY - controls which element is displayed on the PDA device on the Job Detail screen as the Job Reference. The two options are Job Code or Job ID, defaulting to the latter.

===Transfer Configuration Screen===

A new audit and maintenance screen will be required.

This will allow users to search the EPOD_XF_AUDIT_HEADER table by EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_JOB_GROUP. With a later implementation allowing to search for EPL_JOB_ID, or EPL_LOAD_ID.

This screen will display the header records details, EPL_JOB_GROUP, EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_STATUS_DESCRIPTION, and EPL_REQUEST_DATA.
{{note|This would be best displayed within a popup of some kind. For future implementation, the editing and resending of this data may be needed. Doing so a link would need to be made to each job.
}}

== PDA Server ==

The message sent to the PDA client from the server will be modified so that the Job Address (if present) will be used in preference to the Customer address. The Container Weight field (EPL_GROSS_WEIGHT) must also be passed.

The Standing Data Configuration must be changed to pass the new control flags to the device (e.g. EPL_JOB_DISPLAY).

== PDA Client ==

The DB changes will need to be reflected on the PDA.

The PDA will need to be implemented with the functionality to transfer collection details to the delivery job, based on matching Job Codes. This includes altering the planned delivery quantity to the actual collection quantity specified in the collection.

The PDA will need to display Job Code rather than Job ID on the Job Detail screen, depending on the value of the new configuration flag.

The PDA will need to select the appropriate delivery or collection process based on the jobs attributes:
*Collections
**Proctors-Controlled Warehouse - Collection of Containers without Products
**Non-Proctors Location - Collection of Products without Containers
*Deliveries
**Proctors Collection - Delivery of Containers without Products.
**Non-Proctors Collection - Delivery of Products without Containers

When starting a collection or delivery from a Proctors-Controlled Warehouse a update check must be forced (this is currently handled under the standard process) if no container records are received, then an alert is given to the user advising that the data may not be up to date.

====Standard Collection====
The user will be able to long-press any container in the grid. This will provide a popup menu, allowing the user to see the details of the selected container. The PDA will display a screen displaying:
*ID
*Package Code and Description
*Weight

====Collection of Containers without Products====
This will check a parameter on the Job Group - if Container-only Collection is enabled and there are no loose products, the collection will continue as Container only, otherwise the standard (Products Without Containers) collection process will be used.

The user is presented with a list of Containers for collection. The user selects a container either through text entry or scanning. Users have the ability to short-deliver by container only and use the exception process to document any non-delivered containers. When all Containers are accounted for, the user is prompted to complete the job, with a customer signature.

Long-pressing on a container will display a pop-up menu with a Products option shown. If this is clicked, the PDA client will display a list of all products against the container. {{note}} This option should be available only if this is unit is configured for containers without products.

====Collection of Products without Containers====
The user is presented with a list of products for collection. The user confirms collection of each product as in the standard approach. When all Products are accounted for the user is prompted to complete the job, with a customer signature.

====Delivery of Products without Containers====
The process is the same as Collection of Products without Containers.

====Delivery of Containers without Products====
The process is the same as Collection of Containers without Products.

=== Photos ===
Photos will be captured using the standard exception process. User's must be aware that quality of the images will affect GPRS usage, higher quality equals longer more date to transfer. This can only be controlled on the PDA itself and must be set in the PDA's camera settings.

== New POD formats ==
New POD formats will be created for the operation.

The POD or POC format produced will be dependant on the Job Group associated to the Job.

All images captured relating to the Job will be displayed on a second page of the POD/POC document, with the associated detail information (Job ID, Container ID, Product Code, Image description). Again image quality is dependant on device settings, which affects the image size.

Fields on the Delivery Note document will be sourced from the following database fields:
* Delivery Note: EPL_JOB_CODE
* Customer Address: Address information from the Job's Customer
* Delivery Address: Address information from the Job's Address (if present) or the Customer's.
* Customer Tel No: From the Job's Address (if present) or the Customer.
* Cust No/Contact: From the Job's Address (if present) or the Customer.
* Our Order No: EPL_SO_NUMBER (New field)
* Order Date: EPL_ORDER_DATE (New Field)
* Customer Order No: EPL_CUST_REF
* PPB Contact: EPL_SALES_CONTACT (New Field)
* Product Reference: EPL_PRODUCT_CODE
* Product Description: EPL_DESCRIPTION and EPL_DESCRIPTION_LONG
* Due Date: EPL_START_PLANNED_DATE/TIME {{Note}} This is the same for all lines.
* Unit: EPL_UNIT_TYPE (New Field)
* Quantity: EPL_PRODUCT_QTY_ORDERED (New Field)
* Quantity Despatched: EPL_PRODUCT_QTY_PLANNED
* Quantity Delivered: EPL_PRODUCT_QTY_ACTUAL
* No Of Parcels: EPL_COMMENT of EPOD_CONTAINER (New field)
* Pallet ID: EPL_CONTAINER_ID
* Special Instructions: EPL_JOB_INSTRUCTION
* Total Weight: See below
* Delivered By: PDA User Name
* Print Name: EPL_CUST_SIGNATORY (entered by PDA user)
* Date: Job Completion Date
* Signed Unchecked: EPL_SIGNED_UNCHECKED (New Field)

Total Weight will be calculated at the container level. The weight must be passed through as part of the interfaced container record. If no containers have been interfaced, this field will be omitted.

{{Warning}}The following elements have been excluded from the design:
* Barcode
* Vat No
* Picked
* Converted

Fields on the Transfer Note document will be sourced from the following database fields (where different from the Delivery Note):
* Stock Transfer Note: EPL_JOB_CODE
* Transfer Stock From: From the Collection's Customer information
* Transfer Stock To: From the Delivery's Customer information
* Xfer Ref No: EPL_SO_NUMBER (New Field)
* Input By: EPL_SALES_CONTACT (New Field)
* Part Number: EPL_PRODUCT_ID
* Product Description: EPL_DESCRIPTION

{{Warning}}The following elements have been excluded from the design:
* Location
* Location Qty

{{Note}} The existing generic POD/POC format must be modified to check for the Job address before using the Customer's address.

{{Note}} There could be many pallets and stock codes on a collection or delivery. This will run into multiple pages regardless of which note is produced. In the case where multiple pages of information are displayed, the header, up to and including the ''Customer Tel No'' table, will be shown on every page, whereas the Signature footer table will be shown only on the first page, being omitted from all subsequent pages.

==PDF Production==
A new rule will be added at a Site level to control whether emails to customers will be HTML-Embedded or PDF attachment style.

The system will check this rule when:
# The "Email To" button is pressed on the "View POD" page
# auto-emailed documents are being produced.

If this rule is not enabled, the system will send emails as now (embedded HTML emails).

If this rule is enabled, the system will:
*Export and save the page to a temporary directory, with all images rendered.
*Run the saved page through a conversion routine to convert the HTML to a PDF page (saved in the same directory).
*Attach this generated PDF to the email and send
*Delete the temporary folder.

The conversion routine will use the WkHtmlToPDF program with default parameters - this must be installed on the server.

==Auto-Email==
The Auto-email code will be moved into the new batch Auto-Export Process.

The update of a job to complete or cancelled will result in the new field EPL_EMAIL_FLAG being set to "N". The batch process will retrieve all job records where this flag is "N" and the Job Group or Site associated to the job requires auto-email.

The process will iterate through these records and retrieve the email addresses that the job should be emailed to from the Site, Job and Customer records.

If no emails have been specified, EPL_EMAIL_FLAG will set to "X".

If an email address has been specified, the email will be built as per the current process and sent to the defined email address. EPL_EMAIL_FLAG will set to "Y".



= Appendix A: POD Formats =
[[File:Delivery Note.jpg|600px|border]]

[[File:Stock Transfer Note.jpg|600px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|REQ=0
|EST=0
|FS=5.0
|TS=0
|DEV=36
|ST=5.00
|IMP=2.0
|Client={{#var:Client}}
|Year=2012
|FSEST=N
|Rev1=Matt Turner
|Rev1Title=OBS Representative
|Rev2=Stephen McCartney
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 294838 Proctor ePOD Modifications

2012-02-23T14:01:24Z

Milesl: Updates including XML change to include EPOD_CUSTOMER

<div class="noprint">
{{#vardefine:Client|PROC}}
{{#vardefine:ClientName|Proctors}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Proctors ePOD Modifications}}
{{#vardefine:Version|1.0}}
{{#vardefine:Date|22nd February 2012}}
{{#vardefine:Reference|294838}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==

== Solution Overview ==

The ERP system will be able to interface Customer data to the ''CALIDUS'' EPOD system, to identify the customer address, contact and email information.

{{Note}} Customers can also be created through the standard Job interface - if this is the case, then the Job address provided with the first job for this customer will become the customer address.

Jobs will be received for Collection and Delivery from the following main customer types:
*Suppliers
*Customers
*Proctors-operated Warehouses
*3rd Party Warehouses

The jobs will be updated into the ''CALIDUS'' EPOD system through the standard WebService interface.

This job upload will create 2 tasks:
*A Collection Job
*A Delivery Job

Every Collection and Delivery will be specified separately within the interface, with the Product and Quantity specified for all jobs. Linked collections and deliveries will have the same Job Code, but will be distinguished by the Job Type (i.e. Collection or Delivery).

The Upload system will also identify the Loads onto which jobs are planned, as all planning is completed through the Proctors' ERP system.

In phase 1, the initial uploads will be sent to the EPOD system with either no load information, or with the load ID set to a default value.

In phase 2, the initial uploads will be sent tot he EPOD system with either no load information, or with the correct load identified against them. It will then be possible to subsequently update the Load for a job through another update of the Job alone.

There are two types of job:
* Customer/Supplier jobs - jobs that begin or end with a Customer or Supplier.
* Inter-warehouse Transfer - jobs that begin and end from Warehouses

All jobs will be categorised by the ''CALIDUS'' EPOD Job Group into one of the two categories - this will define the paperwork produced by the system when the job is completed. The Job Group will be agreed and sent to the system in the upload files.

Once jobs from Proctors-controlled warehouses are picked and marshalled, updated Jobs will be sent to the EPOD system, detailing the actual containers (pallets) and product quantities on each.

{{Note}} If this data is not available at the time of collecting or delivering the associated jobs, the system will check periodically through a regularly-scheduled automatic process.

Collection jobs from a Proctors-operated warehouse should then have containers and product quantities specified against them. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.

{{Warning}} In this circumstance, where pallet information has not been received, the automatic update of the job when complete will identify on product and quantity information, not pallet information.

The process for a Collection of this type will be:
* Confirm arrival to warehouse.
* Scan/Enter/Select Pallets to be collected.
* Once completed, confirm collection through depot signature.
The user will also be able to long-press against any container to show the details of any products contained within it.

Collection jobs from a Customer, Supplier or 3rd party warehouse (i.e. non-Proctors) will have the Product and Quantity created against them (i.e. no containers/pallets). The process will be:
* Confirm arrival to customer/supplier/warehouse.
* Scan/Enter/Select Products to be collected.
* Confirm total quantity of the products.
* Once completed, confirm collection through customer/supplier signature.

A Delivery of a non-Proctors job will have only product and quantity details. The process will be:
* Confirm arrival to customer.
* Scan/Enter/Select Products to be delivered.
* Confirm total quantity of the products.
* Once completed, confirm delivery through customer signature.

A Delivery of Proctors job should have container (pallet), product and quantities. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.
The process will be:
* Confirm arrival to customer/depot.
* Scan/Enter/Select pallets being delivered
* Once completed, confirm delivery through customer/depot signature.

{{Note}} The system will be configurable to allow the PDA unit to display Job Code rather than Job ID on the Job Detail screen.

Two new POD document formats will be created:
* A Delivery format, configured for use on Customer/Supplier jobs.
* A Transfer format, configured for use on Inter-warehouse Transfers.
These formats will be defined against the Job group provided on the upload.
In order for these to be created to match the current formats as closely as possible, the ''CALIDUS'' EPOD Job Import will be extended to add new fields, identified in detail later in the document.

''CALIDUS'' EPOD will be set up to allow certain customers to be automatically emailed upon completion of jobs to and from them. When enabled, the format associated to the Job Group will be sent to the Customer's associated email address, if there is one. This will also be sent to an email address against the site, if there is one, ensuring that the ERP system is provided copies of the produced PDF files.

{{Note}} Email notification of the POD or POC will be attempted if this feature is turned on and if the customer has an email address. If depots or suppliers do not require notification of collections or deliveries, it must be ensured that the customers created do not have an email address.

Confirmation or cancellation of any job will trigger an automatic update of the ERP system. This will be configurable but is expected to be through an email of the standard EPOD XML job update message. This update will be a scheduled process that will regularly check and attempt to update when possible. It will be scheduled to run as often as required by the client, up to once per minute.

== Scope ==



= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
The two new fixed Job Groups will be set up for Proctors-controlled warehouses and 3rd-party. The former will be configured with the Stock Transfer POD format, whilst the latter will be configured with the other format.


= Functional Description =
The total changes required are:
* Database
* Job Import/Export
* Customers Import
* Auto-Export
* Auto-Email
* Admin
* PDA Client
** Delivery/Collection Without Products
* New POD formats
* PDF Production

== Database Changes ==

=== EPOD_SITE ===
A new flag will be added for the Site Email Address for auto-email, called EPL_EMAIL

=== EPOD_JOB ===
New Fields:
*EPL_SIGNED_UNCHECKED
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number
*EPL_ORDER_DATE
*EPL_SALES_CONTACT - PPB Contact
*EPL_XFER_FLAG - default to ""
*EPL_EMAIL_FLAG - default to ""

Changes:
*Indexing applied to EPL_JOB_CODE, EPL_JOB_TYPE. This will be a repeating index.
*Indexing applied to EPL_XFER_FLAG. This will be a repeating index.
*Indexing applied to EPL_EMAIL_FLAG. This will be a repeating index.

=== EPOD_CONTAINER ===

*EPL_GROSS_WEIGHT - a floating point number.
*EPL_COMMENT - a maximum length text field.

=== EPOD_PRODUCT ===

*EPL_UNIT_TYPE
*EPL_DESCRIPTION_LONG
*EPL_PRODUCT_QTY_ORDERED

=== EPOD_JOB_GROUP ===

*EPL_CONTAINER_ONLY - Controls container-only delivery
*EPL_JOB_DISPLAY - controls whether Job ID or Job Code is displayed on the PDA.

=== XF_CONFIG ===

EPOD_JOB will require a new field of two characters EPL_XFER_FLAG, this will be defaulted to "".
EPOD_SITE and EPOD_JOB_GROUP will require a new field EPL_XF_CONFIG which will link to the EPL_XF_CONFIG_ID. If no export is required this will be blank.

A new table EPOD_XF_CONFIG will be created consisting of:
*EPL_XF_CONFIG_ID: A ten character unique field
*EPL_DESCRIPTION
*EPL_XF_TYPE: A ten character field identifying the type of export (SOAP, File, Email)
*EPL_XF_DESTINATION: A 255 character field identifying the destination of the export
*EPL_XF_PARM: Additional parameters for example subject for email

A new table EPOD_XF_AUDIT_HEADER will be created consisting of:
*EPL_HEADER_ID: A unique auto-increment Id
*EPL_SITE_ID: Indexed
*EPL_JOB_GROUP: Indexed
*EPL_REQUEST_DATA: A maximum length free-text field
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)

A new table EPOD_XF_AUDIT_DETAIL will be created consisting of:
*EPL_HEADER_ID: Foreign key to EPOD_XF_AUDIT_HEADER
*EPL_DETAIL_ID: A unique auto-increment Id
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)
{{Note}} This table is for future development and will not be used at this time.

=== JOB_ADDRESS ===
A new table EPOD_JOB_ADDRESS will be created consisting of:
*EPL_SITE_ID: Foreign key to EPOD_SITE
*EPL_JOB_ID: Foreign key to EPOD_JOB
*EPL_ADDRESS_LINE_1
*EPL_ADDRESS_LINE_2
*EPL_ADDRESS_LINE_3
*EPL_ADDRESS_LINE_4
*EPL_POST_CODE
*EPL_CONTACT
*EPL_TELEPHONE
*EPL_EMAIL
*EPL_LAST_CHANGE_DATE
*EPL_LAST_CHANGE_TIME
The table will be indexed on EPL_SITE_ID and EPL_JOB_ID.

== XML Interface ==

=== Job Import ===

The system shall use the EPL_JOB_CODE field as a reference linking the delivery and collection, the index used shall be EPL_JOB_CODE and EPL_JOB_TYPE. The field EPL_JOB_ID will always be unique, this will be auto-generated by our system if not passed in.

The import can include an optional EPOD_CUSTOMER tag. This is used in preference to the CUSTOMER_NAME and CUSTOMER_CODE tags to update Customer address information. The supplied information against the job is then used exclusively for the Job Address, if different. So for Proctor both the standard adress section with the job message will be completed, mapping to the delivery address (EPOD_JOB_ADDRESS) and the EPOD_CUSTOMER tag will be populated updating the customer address.

Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

The following XML would have the same outcome as above without the generation of container records:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

Both the collection and delivery must share the same EPL_JOB_CODE reference.

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>.
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>

==== Job Update ====

To update the jobs with the Container details, Proctors' ERP must follow the same standard structure as the import.
All Job, Container and Product tags that are populated and present will update the relevant details in the ''CALIDUS'' EPOD system.

{{Note}}
* If the EPL_JOB_ID is blank (as expected for the Proctors interface, as the Collection and Deliveries will be linked via EPL_JOB_CODE), the system will check to see whether a job exists for this EPL_JOB_CODE and EPL_JOB_TYPE. If so, the record will be updated. If not, a new record (with a generated EPL_JOB_ID) will be created.
* If the EPL_JOB_ID is not blank, the system will check to see whether a job exists for this EPL_JOB_ID. If so, the record will be updated. If not, a new record will be created with this EPL_JOB_ID.
* If the EPL_LOAD_ID is left blank, the system will not update the Load ID of the Job.
* If the EPOD_CONTAINERS tag is not populated, the system will not update any container information. If it is present, the system will delete any existing container information and replace it with the information in the containers tag.
* If the EPOD_PRODUCTS tag is not populated, the system will not update any product information. If it is present, the system will delete any existing product information and replace it with the information in the product tag.
* The import can include an optional EPOD_CUSTOMER tag. This is used in preference to the CUSTOMER_NAME and CUSTOMER_CODE tags to update Customer address information. The supplied information against the job is then used exclusively for the Job Address, if different.

Changes will be made to the Customer Address import to ensure that a customer and a job can have defined addresses, as follows:
* If the EPOD_CUSTOMER tag exists in the message
** Pass the contents of the tag to the Customer Import, to update the Customer details
** Use the address information in the message to update the Job Address.
* Else
**If the Customer Code exists in the message
*** the system will check that the record exists within the database with that code.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created with that code.
** If not, and the Customer Name exists
*** the system will check that the record exists within the database with that name.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created and a code generated for it.
** If neither Code nor Name exist, the system will store the address information against the Job.

=== Job Export ===

At the point of job status changed the system will export the Jobs structure using the standard XML and send this to a predefined email address, for interfacing with the ERP system. This will be configured using the XF_CONFIG section of the system.

The required email functionality will need to be added to the existing export process.

The following XML is produced by the export, this example shows the export with multiple Jobs:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PHOTO_ID/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/> <EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575903</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

The following XML is produced by the export, this example shows the export with a single Job:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

==== Auto-Export Process ====

Whenever a job is updated to Cancelled or Complete (i.e. when the jobs are updated by the PDA client, or when jobs are updated via the Admin system), after committing the changes to the database, the Auto Export flag will be checked against the Job Group and Site. If this flag is present the EPL_JOB record will have the EPL_XFER_FLAG set to N, to indicate that the record requires interfacing but has not yet been sent.

{{Note}} These changes will be committed into the Data Access Layer, so that the same code will be called whether running this through the Admin or PDA server functions.

A timed process will be running to send any Jobs with the Xfer flag of N.
The process will:
*Retrieve all jobs on the EPL_JOBS table with the Xfer flag set to N, sorted by Site and Job Group.
*For each record found in distinct Site and Job Group:
**Load the details of this Job ID,
**Generate the XML export as per the standard for currently existing exports
**Once all jobs for the Site/Job Group are exported:
***Get the configuration of the Job Group. If the configuration for the Job Group does not exist, get the configuration for the Site.
***Attempt to transfer this to the destination specified in the configuration.

If this process if successful then the Xfer flag on the Job record will be set to Y, and a success audit record written.
If this fails the flag on the job will be set to N and a record will be written to a audit table with details of the failure.
If the file is send successfully but a message is received from the destination advising of this problem then an audit record will be written and the flag will be set to N.

This timed process will be scheduled on the system. The frequency of the process will be defined by the schedule and can be no more frequent that one per minute. If the process is already running, the process will wait for the next cycle before starting.

The status of the audit records based on the result are:
* S for success;
* SF for success send but error at the receivers, and;
* F for failure to send.
These records will be cleared down once they are older than 7 days.

===Customer Import===
Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_CUSTOMERS>
<EPOD_CUSTOMER>
<EPL_SITE_ID>Dave Jones</EPL_SITE_ID>
<EPL_CUSTOMER_CODE>CUST01</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
</EPOD_CUSTOMERS>

Similarly to the Job import:
* If the Customer Code exists in the message
** the system will check that the record exists within the database with that code.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created.
* If not, and the Customer Name exists
** the system will check that the record exists within the database with that name.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created and a code generated for it.
* If neither exist, the system will not import the customer.

== Admin System ==

Within Phase one the Admin interface will be used to plan Jobs onto loads, all required functionality has been implemented. Within phase two this will not be required as Proctors will interface pre-planned loads.
The following changes will need to be made to the admin system to reflect the database changes:

===Jobs Screen===

*EPL_SIGNED_UNCHECKED - Visible on the POD only, this field is not searchable
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number - Entry only
*EPL_ORDER_DATE - Entry only
*EPL_SALES_CONTACT - PPB Contact - Entry only
*EPOD_JOB_ADDRESS.

In order to accommodate the new fields and allow them to be displayed and entered, the Job screen must be extensively modified.

The Entry panel will be modified to allow entry of the following fields, in two adjacent panels, as below:
<table border="solid black 1px">
<tr><td colspan="2"> '''[Edit buttons]''' </td></tr>
<tr><td width="50%">
Job Type

Job Code

Job Group

Cust Ref

'''Dnote No'''

Planned Date/Time

'''Order Date/Time'''

Sales Contact

Job/Office Instructions

</td><td width="50%">
Customer Code

Use Customer Address as Delivery Address?

'''New Customer Code'''

'''New Customer Name'''

''Address 1''

''Address 2''

''Address 3''

''Address 4''

''Postcode''

''Contact''

''Email''

''Telephone''
</td></tr>
<tr><td colspan="2"> '''[Save] [Cancel]'''</td></tr>
</table>

All fields in '''Bold''' are new fields. All fields in ''Italics'' are new functionality.

The ''Edit'' buttons will not be shown in entry mode.

The left side of the screen will show all the Job-related fields for entry, including the new fields.

The right side of the screen will be the area to identify the customer and address.

The Instructions entry will be through a tabbed entry box. The first tab will contain the Job Instructions and will be displayed. The second tab can be clicked on to edit the Office Instructions.

The Customer drop-down will allow you to select:
* ''No Customer''
** All entry fields (bar Customer Code and Name) below will be enabled.
** The check-box will be disabled.
* ''Create a New Customer'':
** All entry fields below will be enabled.
** Customer Code and Name must be entered
** The check-box will be disabled.
* Select an Existing Customer from the list.
** All fields below will be populated from the Customer's address information.
** The check-box will be enabled, indicating that you are using the Customer's address as the delivery address.
** Only the check-box will be an enabled field - all others will be disabled.

Un-checking the check box will enable all the entry fields, which will remain populated with the default values from the customer address.

Clicking '''Save''' will create the Job. If a new customer is being created, the address entered will be assigned to the customer. If a delivery address has been chosen that is different to the selected existing customer (or no customer has been selected), the address will be saved to the Job address.

The following columns will be removed from the grid:
* Site ID
* Job Instructions
* Office Instructions
* Reason Code
* Configure
* Details
* Report

The Status field will be modified to show the Reason Code and Description entered for a cancelled job in a tool-tip (activated by hovering the mouse pointer over the Status).

The grid will be modified to not allow direct entry. Instead, the grid will use the Entry panel. This will be activated by clicking once on the line, which will display the Entry panel, populated with the details of the line selected.

The functionality will differ to the Entry functionality, in that the Action buttons will be populated as follows:
* Details - Display any Container, Product or Service details associated to the job
* Report - Display the POD/POC/Service report (only enabled if the Job is at status Complete
* Cancel Job - Move a Job to Cancelled status.
* Image - Display any Image associated to the Job.

===Containers Screen===
*EPL_GROSS_WEIGHT - Visible against the container record and available for entry.
*EPL_COMMENT - Visible against the container record and available for entry.

===Job Products Screen===

*EPL_UNIT_TYPE - Visible against the product record and available for entry
*EPL_DESCRIPTION_LONG - Visible against the product record and available for entry
*EPL_PRODUCT_QTY_ORDERED - Visible against the product record and available for entry

===Site Maintenance Screen===
*EPL_EMAIL - Visible and editable.

===Job Group Maintenance Screen===

*EPL_CONTAINER_ONLY - Controls container only delivery - Visible and Editable
*EPL_JOB_DISPLAY - controls which element is displayed on the PDA device on the Job Detail screen as the Job Reference. The two options are Job Code or Job ID, defaulting to the latter.

===Transfer Configuration Screen===

A new audit and maintenance screen will be required.

This will allow users to search the EPOD_XF_AUDIT_HEADER table by EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_JOB_GROUP. With a later implementation allowing to search for EPL_JOB_ID, or EPL_LOAD_ID.

This screen will display the header records details, EPL_JOB_GROUP, EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_STATUS_DESCRIPTION, and EPL_REQUEST_DATA.
{{note|This would be best displayed within a popup of some kind. For future implementation, the editing and resending of this data may be needed. Doing so a link would need to be made to each job.
}}

== PDA Server ==

The message sent to the PDA client from the server will be modified so that the Job Address (if present) will be used in preference to the Customer address. The Container Weight field (EPL_GROSS_WEIGHT) must also be passed.

The Standing Data Configuration must be changed to pass the new control flags to the device (e.g. EPL_JOB_DISPLAY).

== PDA Client ==

The DB changes will need to be reflected on the PDA.

The PDA will need to be implemented with the functionality to transfer collection details to the delivery job, based on matching Job Codes. This includes altering the planned delivery quantity to the actual collection quantity specified in the collection.

The PDA will need to display Job Code rather than Job ID on the Job Detail screen, depending on the value of the new configuration flag.

The PDA will need to select the appropriate delivery or collection process based on the jobs attributes:
*Collections
**Proctors-Controlled Warehouse - Collection of Containers without Products
**Non-Proctors Location - Collection of Products without Containers
*Deliveries
**Proctors Collection - Delivery of Containers without Products.
**Non-Proctors Collection - Delivery of Products without Containers

When starting a collection or delivery from a Proctors-Controlled Warehouse a update check must be forced (this is currently handled under the standard process) if no container records are received, then an alert is given to the user advising that the data may not be up to date.

====Standard Collection====
The user will be able to long-press any container in the grid. This will provide a popup menu, allowing the user to see the details of the selected container. The PDA will display a screen displaying:
*ID
*Package Code and Description
*Weight

====Collection of Containers without Products====
This will check a parameter on the Job Group - if Container-only Collection is enabled and there are no loose products, the collection will continue as Container only, otherwise the standard (Products Without Containers) collection process will be used.

The user is presented with a list of Containers for collection. The user selects a container either through text entry or scanning. Users have the ability to short-deliver by container only and use the exception process to document any non-delivered containers. When all Containers are accounted for, the user is prompted to complete the job, with a customer signature.

Long-pressing on a container will display a pop-up menu with a Products option shown. If this is clicked, the PDA client will display a list of all products against the container. {{note}} This option should be available only if this is unit is configured for containers without products.

====Collection of Products without Containers====
The user is presented with a list of products for collection. The user confirms collection of each product as in the standard approach. When all Products are accounted for the user is prompted to complete the job, with a customer signature.

====Delivery of Products without Containers====
The process is the same as Collection of Products without Containers.

====Delivery of Containers without Products====
The process is the same as Collection of Containers without Products.

=== Photos ===
Photos will be captured using the standard exception process. User's must be aware that quality of the images will affect GPRS usage, higher quality equals longer more date to transfer. This can only be controlled on the PDA itself and must be set in the PDA's camera settings.

== New POD formats ==
New POD formats will be created for the operation.

The POD or POC format produced will be dependant on the Job Group associated to the Job.

All images captured relating to the Job will be displayed on a second page of the POD/POC document, with the associated detail information (Job ID, Container ID, Product Code, Image description). Again image quality is dependant on device settings, which affects the image size.

Fields on the Delivery Note document will be sourced from the following database fields:
* Delivery Note: EPL_JOB_CODE
* Customer Address: Address information from the Job's Customer
* Delivery Address: Address information from the Job's Address (if present) or the Customer's.
* Customer Tel No: From the Job's Address (if present) or the Customer.
* Cust No/Contact: From the Job's Address (if present) or the Customer.
* Our Order No: EPL_SO_NUMBER (New field)
* Order Date: EPL_ORDER_DATE (New Field)
* Customer Order No: EPL_CUST_REF
* PPB Contact: EPL_SALES_CONTACT (New Field)
* Product Reference: EPL_PRODUCT_CODE
* Product Description: EPL_DESCRIPTION and EPL_DESCRIPTION_LONG
* Due Date: EPL_START_PLANNED_DATE/TIME {{Note}} This is the same for all lines.
* Unit: EPL_UNIT_TYPE (New Field)
* Quantity: EPL_PRODUCT_QTY_ORDERED (New Field)
* Quantity Despatched: EPL_PRODUCT_QTY_PLANNED
* Quantity Delivered: EPL_PRODUCT_QTY_ACTUAL
* No Of Parcels: EPL_COMMENT of EPOD_CONTAINER (New field)
* Pallet ID: EPL_CONTAINER_ID
* Special Instructions: EPL_JOB_INSTRUCTION
* Total Weight: See below
* Delivered By: PDA User Name
* Print Name: EPL_CUST_SIGNATORY (entered by PDA user)
* Date: Job Completion Date
* Signed Unchecked: EPL_SIGNED_UNCHECKED (New Field)

Total Weight will be calculated at the container level. The weight must be passed through as part of the interfaced container record. If no containers have been interfaced, this field will be omitted.

{{Warning}}The following elements have been excluded from the design:
* Barcode
* Vat No
* Picked
* Converted

Fields on the Transfer Note document will be sourced from the following database fields (where different from the Delivery Note):
* Stock Transfer Note: EPL_JOB_CODE
* Transfer Stock From: From the Collection's Customer information
* Transfer Stock To: From the Delivery's Customer information
* Xfer Ref No: EPL_SO_NUMBER (New Field)
* Input By: EPL_SALES_CONTACT (New Field)
* Part Number: EPL_PRODUCT_ID
* Product Description: EPL_DESCRIPTION

{{Warning}}The following elements have been excluded from the design:
* Location
* Location Qty

{{Note}} The existing generic POD/POC format must be modified to check for the Job address before using the Customer's address.

{{Note}} There could be many pallets and stock codes on a collection or delivery. This will run into multiple pages regardless of which note is produced. In the case where multiple pages of information are displayed, the header, up to and including the ''Customer Tel No'' table, will be shown on every page, whereas the Signature footer table will be shown only on the first page, being omitted from all subsequent pages.

==PDF Production==
A new rule will be added at a Site level to control whether emails to customers will be HTML-Embedded or PDF attachment style.

The system will check this rule when:
# The "Email To" button is pressed on the "View POD" page
# auto-emailed documents are being produced.

If this rule is not enabled, the system will send emails as now (embedded HTML emails).

If this rule is enabled, the system will:
*Export and save the page to a temporary directory, with all images rendered.
*Run the saved page through a conversion routine to convert the HTML to a PDF page (saved in the same directory).
*Attach this generated PDF to the email and send
*Delete the temporary folder.

The conversion routine will use the WkHtmlToPDF program with default parameters - this must be installed on the server.

==Auto-Email==
The Auto-email code will be moved into the new batch Auto-Export Process.

The update of a job to complete or cancelled will result in the new field EPL_EMAIL_FLAG being set to "N". The batch process will retrieve all job records where this flag is "N" and the Job Group or Site associated to the job requires auto-email.

The process will iterate through these records and retrieve the email addresses that the job should be emailed to from the Site, Job and Customer records.

If no emails have been specified, EPL_EMAIL_FLAG will set to "X".

If an email address has been specified, the email will be built as per the current process and sent to the defined email address. EPL_EMAIL_FLAG will set to "Y".



= Appendix A: POD Formats =
[[File:Delivery Note.jpg|600px|border]]

[[File:Stock Transfer Note.jpg|600px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|REQ=0
|EST=0
|FS=5.0
|TS=0
|DEV=36
|ST=5.00
|IMP=2.0
|Client={{#var:Client}}
|Year=2012
|FSEST=N
|Rev1=Matt Turner
|Rev1Title=OBS Representative
|Rev2=Stephen McCartney
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 294838 Proctor ePOD Modifications

2012-02-23T13:56:56Z

Milesl:

<div class="noprint">
{{#vardefine:Client|PROC}}
{{#vardefine:ClientName|Proctors}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Proctors ePOD Modifications}}
{{#vardefine:Version|1.0}}
{{#vardefine:Date|22nd February 2012}}
{{#vardefine:Reference|294838}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==

== Solution Overview ==

The ERP system will be able to interface Customer data to the ''CALIDUS'' EPOD system, to identify the customer address, contact and email information.

{{Note}} Customers can also be created through the standard Job interface - if this is the case, then the Job address provided with the first job for this customer will become the customer address.

Jobs will be received for Collection and Delivery from the following main customer types:
*Suppliers
*Customers
*Proctors-operated Warehouses
*3rd Party Warehouses

The jobs will be updated into the ''CALIDUS'' EPOD system through the standard WebService interface.

This job upload will create 2 tasks:
*A Collection Job
*A Delivery Job

Every Collection and Delivery will be specified separately within the interface, with the Product and Quantity specified for all jobs. Linked collections and deliveries will have the same Job Code, but will be distinguished by the Job Type (i.e. Collection or Delivery).

The Upload system will also identify the Loads onto which jobs are planned, as all planning is completed through the Proctors' ERP system.

In phase 1, the initial uploads will be sent to the EPOD system with either no load information, or with the load ID set to a default value.

In phase 2, the initial uploads will be sent tot he EPOD system with either no load information, or with the correct load identified against them. It will then be possible to subsequently update the Load for a job through another update of the Job alone.

There are two types of job:
* Customer/Supplier jobs - jobs that begin or end with a Customer or Supplier.
* Inter-warehouse Transfer - jobs that begin and end from Warehouses

All jobs will be categorised by the ''CALIDUS'' EPOD Job Group into one of the two categories - this will define the paperwork produced by the system when the job is completed. The Job Group will be agreed and sent to the system in the upload files.

Once jobs from Proctors-controlled warehouses are picked and marshalled, updated Jobs will be sent to the EPOD system, detailing the actual containers (pallets) and product quantities on each.

{{Note}} If this data is not available at the time of collecting or delivering the associated jobs, the system will check periodically through a regularly-scheduled automatic process.

Collection jobs from a Proctors-operated warehouse should then have containers and product quantities specified against them. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.

{{Warning}} In this circumstance, where pallet information has not been received, the automatic update of the job when complete will identify on product and quantity information, not pallet information.

The process for a Collection of this type will be:
* Confirm arrival to warehouse.
* Scan/Enter/Select Pallets to be collected.
* Once completed, confirm collection through depot signature.
The user will also be able to long-press against any container to show the details of any products contained within it.

Collection jobs from a Customer, Supplier or 3rd party warehouse (i.e. non-Proctors) will have the Product and Quantity created against them (i.e. no containers/pallets). The process will be:
* Confirm arrival to customer/supplier/warehouse.
* Scan/Enter/Select Products to be collected.
* Confirm total quantity of the products.
* Once completed, confirm collection through customer/supplier signature.

A Delivery of a non-Proctors job will have only product and quantity details. The process will be:
* Confirm arrival to customer.
* Scan/Enter/Select Products to be delivered.
* Confirm total quantity of the products.
* Once completed, confirm delivery through customer signature.

A Delivery of Proctors job should have container (pallet), product and quantities. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.
The process will be:
* Confirm arrival to customer/depot.
* Scan/Enter/Select pallets being delivered
* Once completed, confirm delivery through customer/depot signature.

{{Note}} The system will be configurable to allow the PDA unit to display Job Code rather than Job ID on the Job Detail screen.

Two new POD document formats will be created:
* A Delivery format, configured for use on Customer/Supplier jobs.
* A Transfer format, configured for use on Inter-warehouse Transfers.
These formats will be defined against the Job group provided on the upload.
In order for these to be created to match the current formats as closely as possible, the ''CALIDUS'' EPOD Job Import will be extended to add new fields, identified in detail later in the document.

''CALIDUS'' EPOD will be set up to allow certain customers to be automatically emailed upon completion of jobs to and from them. When enabled, the format associated to the Job Group will be sent to the Customer's associated email address, if there is one. This will also be sent to an email address against the site, if there is one, ensuring that the ERP system is provided copies of the produced PDF files.

{{Note}} Email notification of the POD or POC will be attempted if this feature is turned on and if the customer has an email address. If depots or suppliers do not require notification of collections or deliveries, it must be ensured that the customers created do not have an email address.

Confirmation or cancellation of any job will trigger an automatic update of the ERP system. This will be configurable but is expected to be through an email of the standard EPOD XML job update message. This update will be a scheduled process that will regularly check and attempt to update when possible. It will be scheduled to run as often as required by the client, up to once per minute.

== Scope ==



= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
The two new fixed Job Groups will be set up for Proctors-controlled warehouses and 3rd-party. The former will be configured with the Stock Transfer POD format, whilst the latter will be configured with the other format.


= Functional Description =
The total changes required are:
* Database
* Job Import/Export
* Customers Import
* Auto-Export
* Auto-Email
* Admin
* PDA Client
** Delivery/Collection Without Products
* New POD formats
* PDF Production

== Database Changes ==

=== EPOD_SITE ===
A new flag will be added for the Site Email Address for auto-email, called EPL_EMAIL

=== EPOD_JOB ===
New Fields:
*EPL_SIGNED_UNCHECKED
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number
*EPL_ORDER_DATE
*EPL_SALES_CONTACT - PPB Contact
*EPL_XFER_FLAG - default to ""
*EPL_EMAIL_FLAG - default to ""

Changes:
*Indexing applied to EPL_JOB_CODE, EPL_JOB_TYPE. This will be a repeating index.
*Indexing applied to EPL_XFER_FLAG. This will be a repeating index.
*Indexing applied to EPL_EMAIL_FLAG. This will be a repeating index.

=== EPOD_CONTAINER ===

*EPL_GROSS_WEIGHT - a floating point number.
*EPL_COMMENT - a maximum length text field.

=== EPOD_PRODUCT ===

*EPL_UNIT_TYPE
*EPL_DESCRIPTION_LONG
*EPL_PRODUCT_QTY_ORDERED

=== EPOD_JOB_GROUP ===

*EPL_CONTAINER_ONLY - Controls container-only delivery
*EPL_JOB_DISPLAY - controls whether Job ID or Job Code is displayed on the PDA.

=== XF_CONFIG ===

EPOD_JOB will require a new field of two characters EPL_XFER_FLAG, this will be defaulted to "".
EPOD_SITE and EPOD_JOB_GROUP will require a new field EPL_XF_CONFIG which will link to the EPL_XF_CONFIG_ID. If no export is required this will be blank.

A new table EPOD_XF_CONFIG will be created consisting of:
*EPL_XF_CONFIG_ID: A ten character unique field
*EPL_DESCRIPTION
*EPL_XF_TYPE: A ten character field identifying the type of export (SOAP, File, Email)
*EPL_XF_DESTINATION: A 255 character field identifying the destination of the export
*EPL_XF_PARM: Additional parameters for example subject for email

A new table EPOD_XF_AUDIT_HEADER will be created consisting of:
*EPL_HEADER_ID: A unique auto-increment Id
*EPL_SITE_ID: Indexed
*EPL_JOB_GROUP: Indexed
*EPL_REQUEST_DATA: A maximum length free-text field
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)

A new table EPOD_XF_AUDIT_DETAIL will be created consisting of:
*EPL_HEADER_ID: Foreign key to EPOD_XF_AUDIT_HEADER
*EPL_DETAIL_ID: A unique auto-increment Id
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)
{{Note}} This table is for future development and will not be used at this time.

=== JOB_ADDRESS ===
A new table EPOD_JOB_ADDRESS will be created consisting of:
*EPL_SITE_ID: Foreign key to EPOD_SITE
*EPL_JOB_ID: Foreign key to EPOD_JOB
*EPL_ADDRESS_LINE_1
*EPL_ADDRESS_LINE_2
*EPL_ADDRESS_LINE_3
*EPL_ADDRESS_LINE_4
*EPL_POST_CODE
*EPL_CONTACT
*EPL_TELEPHONE
*EPL_EMAIL
*EPL_LAST_CHANGE_DATE
*EPL_LAST_CHANGE_TIME
The table will be indexed on EPL_SITE_ID and EPL_JOB_ID.

== XML Interface ==

=== Job Import ===

The system shall use the EPL_JOB_CODE field as a reference linking the delivery and collection, the index used shall be EPL_JOB_CODE and EPL_JOB_TYPE. The field EPL_JOB_ID will always be unique, this will be auto-generated by our system if not passed in.

Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

The following XML would have the same outcome as above without the generation of container records:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

Both the collection and delivery must share the same EPL_JOB_CODE reference.

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>.
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>

==== Job Update ====

To update the jobs with the Container details, Proctors' ERP must follow the same standard structure as the import.
All Job, Container and Product tags that are populated and present will update the relevant details in the ''CALIDUS'' EPOD system.

{{Note}}
* If the EPL_JOB_ID is blank (as expected for the Proctors interface, as the Collection and Deliveries will be linked via EPL_JOB_CODE), the system will check to see whether a job exists for this EPL_JOB_CODE and EPL_JOB_TYPE. If so, the record will be updated. If not, a new record (with a generated EPL_JOB_ID) will be created.
* If the EPL_JOB_ID is not blank, the system will check to see whether a job exists for this EPL_JOB_ID. If so, the record will be updated. If not, a new record will be created with this EPL_JOB_ID.
* If the EPL_LOAD_ID is left blank, the system will not update the Load ID of the Job.
* If the EPOD_CONTAINERS tag is not populated, the system will not update any container information. If it is present, the system will delete any existing container information and replace it with the information in the containers tag.
* If the EPOD_PRODUCTS tag is not populated, the system will not update any product information. If it is present, the system will delete any existing product information and replace it with the information in the product tag.
* The import can include an optional EPOD_CUSTOMER tag. This is used in preference to the CUSTOMER_NAME and CUSTOMER_CODE tags to update Customer address information. The supplied information against the job is then used exclusively for the Job Address, if different.

Changes will be made to the Customer Address import to ensure that a customer and a job can have defined addresses, as follows:
* If the EPOD_CUSTOMER tag exists in the message
** Pass the contents of the tag to the Customer Import, to update the Customer details
** Use the address information in the message to update the Job Address.
* Else
**If the Customer Code exists in the message
*** the system will check that the record exists within the database with that code.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created with that code.
** If not, and the Customer Name exists
*** the system will check that the record exists within the database with that name.
*** If the record exists,
**** The system will check the address information provided on the job against the address information against the customer.
**** If this information is the different, the address information will be added to the Job, defaulting all non-present fields from the customer.
*** If not, the record will be created and a code generated for it.
** If neither Code nor Name exist, the system will store the address information against the Job.

=== Job Export ===

At the point of job status changed the system will export the Jobs structure using the standard XML and send this to a predefined email address, for interfacing with the ERP system. This will be configured using the XF_CONFIG section of the system.

The required email functionality will need to be added to the existing export process.

The following XML is produced by the export, this example shows the export with multiple Jobs:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PHOTO_ID/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/> <EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575903</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

The following XML is produced by the export, this example shows the export with a single Job:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_SO_NUMBER></EPL_SO_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_GROSS_WEIGHT>100.14</EPL_GROSS_WEIGHT>
<EPL_COMMENT>1 PLT 800</EPL_COMMENT>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

==== Auto-Export Process ====

Whenever a job is updated to Cancelled or Complete (i.e. when the jobs are updated by the PDA client, or when jobs are updated via the Admin system), after committing the changes to the database, the Auto Export flag will be checked against the Job Group and Site. If this flag is present the EPL_JOB record will have the EPL_XFER_FLAG set to N, to indicate that the record requires interfacing but has not yet been sent.

{{Note}} These changes will be committed into the Data Access Layer, so that the same code will be called whether running this through the Admin or PDA server functions.

A timed process will be running to send any Jobs with the Xfer flag of N.
The process will:
*Retrieve all jobs on the EPL_JOBS table with the Xfer flag set to N, sorted by Site and Job Group.
*For each record found in distinct Site and Job Group:
**Load the details of this Job ID,
**Generate the XML export as per the standard for currently existing exports
**Once all jobs for the Site/Job Group are exported:
***Get the configuration of the Job Group. If the configuration for the Job Group does not exist, get the configuration for the Site.
***Attempt to transfer this to the destination specified in the configuration.

If this process if successful then the Xfer flag on the Job record will be set to Y, and a success audit record written.
If this fails the flag on the job will be set to N and a record will be written to a audit table with details of the failure.
If the file is send successfully but a message is received from the destination advising of this problem then an audit record will be written and the flag will be set to N.

This timed process will be scheduled on the system. The frequency of the process will be defined by the schedule and can be no more frequent that one per minute. If the process is already running, the process will wait for the next cycle before starting.

The status of the audit records based on the result are:
* S for success;
* SF for success send but error at the receivers, and;
* F for failure to send.
These records will be cleared down once they are older than 7 days.

===Customer Import===
Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_CUSTOMERS>
<EPOD_CUSTOMER>
<EPL_SITE_ID>Dave Jones</EPL_SITE_ID>
<EPL_CUSTOMER_CODE>CUST01</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
</EPOD_CUSTOMER>
</EPOD_CUSTOMERS>

Similarly to the Job import:
* If the Customer Code exists in the message
** the system will check that the record exists within the database with that code.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created.
* If not, and the Customer Name exists
** the system will check that the record exists within the database with that name.
*** If the record exists, it will be updated with the populated values in the message.
*** If not, the record will be created and a code generated for it.
* If neither exist, the system will not import the customer.

== Admin System ==

Within Phase one the Admin interface will be used to plan Jobs onto loads, all required functionality has been implemented. Within phase two this will not be required as Proctors will interface pre-planned loads.
The following changes will need to be made to the admin system to reflect the database changes:

===Jobs Screen===

*EPL_SIGNED_UNCHECKED - Visible on the POD only, this field is not searchable
*EPL_SO_NUMBER - Our Order Number / Xfer Ref Number - Entry only
*EPL_ORDER_DATE - Entry only
*EPL_SALES_CONTACT - PPB Contact - Entry only
*EPOD_JOB_ADDRESS.

In order to accommodate the new fields and allow them to be displayed and entered, the Job screen must be extensively modified.

The Entry panel will be modified to allow entry of the following fields, in two adjacent panels, as below:
<table border="solid black 1px">
<tr><td colspan="2"> '''[Edit buttons]''' </td></tr>
<tr><td width="50%">
Job Type

Job Code

Job Group

Cust Ref

'''Dnote No'''

Planned Date/Time

'''Order Date/Time'''

Sales Contact

Job/Office Instructions

</td><td width="50%">
Customer Code

Use Customer Address as Delivery Address?

'''New Customer Code'''

'''New Customer Name'''

''Address 1''

''Address 2''

''Address 3''

''Address 4''

''Postcode''

''Contact''

''Email''

''Telephone''
</td></tr>
<tr><td colspan="2"> '''[Save] [Cancel]'''</td></tr>
</table>

All fields in '''Bold''' are new fields. All fields in ''Italics'' are new functionality.

The ''Edit'' buttons will not be shown in entry mode.

The left side of the screen will show all the Job-related fields for entry, including the new fields.

The right side of the screen will be the area to identify the customer and address.

The Instructions entry will be through a tabbed entry box. The first tab will contain the Job Instructions and will be displayed. The second tab can be clicked on to edit the Office Instructions.

The Customer drop-down will allow you to select:
* ''No Customer''
** All entry fields (bar Customer Code and Name) below will be enabled.
** The check-box will be disabled.
* ''Create a New Customer'':
** All entry fields below will be enabled.
** Customer Code and Name must be entered
** The check-box will be disabled.
* Select an Existing Customer from the list.
** All fields below will be populated from the Customer's address information.
** The check-box will be enabled, indicating that you are using the Customer's address as the delivery address.
** Only the check-box will be an enabled field - all others will be disabled.

Un-checking the check box will enable all the entry fields, which will remain populated with the default values from the customer address.

Clicking '''Save''' will create the Job. If a new customer is being created, the address entered will be assigned to the customer. If a delivery address has been chosen that is different to the selected existing customer (or no customer has been selected), the address will be saved to the Job address.

The following columns will be removed from the grid:
* Site ID
* Job Instructions
* Office Instructions
* Reason Code
* Configure
* Details
* Report

The Status field will be modified to show the Reason Code and Description entered for a cancelled job in a tool-tip (activated by hovering the mouse pointer over the Status).

The grid will be modified to not allow direct entry. Instead, the grid will use the Entry panel. This will be activated by clicking once on the line, which will display the Entry panel, populated with the details of the line selected.

The functionality will differ to the Entry functionality, in that the Action buttons will be populated as follows:
* Details - Display any Container, Product or Service details associated to the job
* Report - Display the POD/POC/Service report (only enabled if the Job is at status Complete
* Cancel Job - Move a Job to Cancelled status.
* Image - Display any Image associated to the Job.

===Containers Screen===
*EPL_GROSS_WEIGHT - Visible against the container record and available for entry.
*EPL_COMMENT - Visible against the container record and available for entry.

===Job Products Screen===

*EPL_UNIT_TYPE - Visible against the product record and available for entry
*EPL_DESCRIPTION_LONG - Visible against the product record and available for entry
*EPL_PRODUCT_QTY_ORDERED - Visible against the product record and available for entry

===Site Maintenance Screen===
*EPL_EMAIL - Visible and editable.

===Job Group Maintenance Screen===

*EPL_CONTAINER_ONLY - Controls container only delivery - Visible and Editable
*EPL_JOB_DISPLAY - controls which element is displayed on the PDA device on the Job Detail screen as the Job Reference. The two options are Job Code or Job ID, defaulting to the latter.

===Transfer Configuration Screen===

A new audit and maintenance screen will be required.

This will allow users to search the EPOD_XF_AUDIT_HEADER table by EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_JOB_GROUP. With a later implementation allowing to search for EPL_JOB_ID, or EPL_LOAD_ID.

This screen will display the header records details, EPL_JOB_GROUP, EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_STATUS_DESCRIPTION, and EPL_REQUEST_DATA.
{{note|This would be best displayed within a popup of some kind. For future implementation, the editing and resending of this data may be needed. Doing so a link would need to be made to each job.
}}

== PDA Server ==

The message sent to the PDA client from the server will be modified so that the Job Address (if present) will be used in preference to the Customer address. The Container Weight field (EPL_GROSS_WEIGHT) must also be passed.

The Standing Data Configuration must be changed to pass the new control flags to the device (e.g. EPL_JOB_DISPLAY).

== PDA Client ==

The DB changes will need to be reflected on the PDA.

The PDA will need to be implemented with the functionality to transfer collection details to the delivery job, based on matching Job Codes. This includes altering the planned delivery quantity to the actual collection quantity specified in the collection.

The PDA will need to display Job Code rather than Job ID on the Job Detail screen, depending on the value of the new configuration flag.

The PDA will need to select the appropriate delivery or collection process based on the jobs attributes:
*Collections
**Proctors-Controlled Warehouse - Collection of Containers without Products
**Non-Proctors Location - Collection of Products without Containers
*Deliveries
**Proctors Collection - Delivery of Containers without Products.
**Non-Proctors Collection - Delivery of Products without Containers

When starting a collection or delivery from a Proctors-Controlled Warehouse a update check must be forced (this is currently handled under the standard process) if no container records are received, then an alert is given to the user advising that the data may not be up to date.

====Standard Collection====
The user will be able to long-press any container in the grid. This will provide a popup menu, allowing the user to see the details of the selected container. The PDA will display a screen displaying:
*ID
*Package Code and Description
*Weight

====Collection of Containers without Products====
This will check a parameter on the Job Group - if Container-only Collection is enabled and there are no loose products, the collection will continue as Container only, otherwise the standard (Products Without Containers) collection process will be used.

The user is presented with a list of Containers for collection. The user selects a container either through text entry or scanning. Users have the ability to short-deliver by container only and use the exception process to document any non-delivered containers. When all Containers are accounted for, the user is prompted to complete the job, with a customer signature.

Long-pressing on a container will display a pop-up menu with a Products option shown. If this is clicked, the PDA client will display a list of all products against the container. {{note}} This option should be available only if this is unit is configured for containers without products.

====Collection of Products without Containers====
The user is presented with a list of products for collection. The user confirms collection of each product as in the standard approach. When all Products are accounted for the user is prompted to complete the job, with a customer signature.

====Delivery of Products without Containers====
The process is the same as Collection of Products without Containers.

====Delivery of Containers without Products====
The process is the same as Collection of Containers without Products.

=== Photos ===
Photos will be captured using the standard exception process. User's must be aware that quality of the images will affect GPRS usage, higher quality equals longer more date to transfer. This can only be controlled on the PDA itself and must be set in the PDA's camera settings.

== New POD formats ==
New POD formats will be created for the operation.

The POD or POC format produced will be dependant on the Job Group associated to the Job.

All images captured relating to the Job will be displayed on a second page of the POD/POC document, with the associated detail information (Job ID, Container ID, Product Code, Image description). Again image quality is dependant on device settings, which affects the image size.

Fields on the Delivery Note document will be sourced from the following database fields:
* Delivery Note: EPL_JOB_CODE
* Customer Address: Address information from the Job's Customer
* Delivery Address: Address information from the Job's Address (if present) or the Customer's.
* Customer Tel No: From the Job's Address (if present) or the Customer.
* Cust No/Contact: From the Job's Address (if present) or the Customer.
* Our Order No: EPL_SO_NUMBER (New field)
* Order Date: EPL_ORDER_DATE (New Field)
* Customer Order No: EPL_CUST_REF
* PPB Contact: EPL_SALES_CONTACT (New Field)
* Product Reference: EPL_PRODUCT_CODE
* Product Description: EPL_DESCRIPTION and EPL_DESCRIPTION_LONG
* Due Date: EPL_START_PLANNED_DATE/TIME {{Note}} This is the same for all lines.
* Unit: EPL_UNIT_TYPE (New Field)
* Quantity: EPL_PRODUCT_QTY_ORDERED (New Field)
* Quantity Despatched: EPL_PRODUCT_QTY_PLANNED
* Quantity Delivered: EPL_PRODUCT_QTY_ACTUAL
* No Of Parcels: EPL_COMMENT of EPOD_CONTAINER (New field)
* Pallet ID: EPL_CONTAINER_ID
* Special Instructions: EPL_JOB_INSTRUCTION
* Total Weight: See below
* Delivered By: PDA User Name
* Print Name: EPL_CUST_SIGNATORY (entered by PDA user)
* Date: Job Completion Date
* Signed Unchecked: EPL_SIGNED_UNCHECKED (New Field)

Total Weight will be calculated at the container level. The weight must be passed through as part of the interfaced container record. If no containers have been interfaced, this field will be omitted.

{{Warning}}The following elements have been excluded from the design:
* Barcode
* Vat No
* Picked
* Converted

Fields on the Transfer Note document will be sourced from the following database fields (where different from the Delivery Note):
* Stock Transfer Note: EPL_JOB_CODE
* Transfer Stock From: From the Collection's Customer information
* Transfer Stock To: From the Delivery's Customer information
* Xfer Ref No: EPL_SO_NUMBER (New Field)
* Input By: EPL_SALES_CONTACT (New Field)
* Part Number: EPL_PRODUCT_ID
* Product Description: EPL_DESCRIPTION

{{Warning}}The following elements have been excluded from the design:
* Location
* Location Qty

{{Note}} The existing generic POD/POC format must be modified to check for the Job address before using the Customer's address.

{{Note}} There could be many pallets and stock codes on a collection or delivery. This will run into multiple pages regardless of which note is produced. In the case where multiple pages of information are displayed, the header, up to and including the ''Customer Tel No'' table, will be shown on every page, whereas the Signature footer table will be shown only on the first page, being omitted from all subsequent pages.

==PDF Production==
A new rule will be added at a Site level to control whether emails to customers will be HTML-Embedded or PDF attachment style.

The system will check this rule when:
# The "Email To" button is pressed on the "View POD" page
# auto-emailed documents are being produced.

If this rule is not enabled, the system will send emails as now (embedded HTML emails).

If this rule is enabled, the system will:
*Export and save the page to a temporary directory, with all images rendered.
*Run the saved page through a conversion routine to convert the HTML to a PDF page (saved in the same directory).
*Attach this generated PDF to the email and send
*Delete the temporary folder.

The conversion routine will use the WkHtmlToPDF program with default parameters - this must be installed on the server.

==Auto-Email==
The Auto-email code will be moved into the new batch Auto-Export Process.

The update of a job to complete or cancelled will result in the new field EPL_EMAIL_FLAG being set to "N". The batch process will retrieve all job records where this flag is "N" and the Job Group or Site associated to the job requires auto-email.

The process will iterate through these records and retrieve the email addresses that the job should be emailed to from the Site, Job and Customer records.

If no emails have been specified, EPL_EMAIL_FLAG will set to "X".

If an email address has been specified, the email will be built as per the current process and sent to the defined email address. EPL_EMAIL_FLAG will set to "Y".



= Appendix A: POD Formats =
[[File:Delivery Note.jpg|600px|border]]

[[File:Stock Transfer Note.jpg|600px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|REQ=0
|EST=0
|FS=5.0
|TS=0
|DEV=36
|ST=5.00
|IMP=2.0
|Client={{#var:Client}}
|Year=2012
|FSEST=N
|Rev1=Matt Turner
|Rev1Title=OBS Representative
|Rev2=Stephen McCartney
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 292887 EPOD Automatic Updater

2012-02-22T13:17:45Z

Milesl: Update to build procedures

<div class="noprint">
{{#vardefine:Client|PROD}}
{{#vardefine:ClientName|OBS}}
{{#vardefine:System|''CALIDUS'' EPOD}}
{{#vardefine:Doc_Title|EPOD Automatic Updater}}
{{#vardefine:Version|0.1}}
{{#vardefine:Date|22nd Feb 2012}}
{{#vardefine:Reference|292887}}
{{#vardefine:Year|2012}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
|Year={{#var:Year}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==
The intention of this process is to allow the EPOD PDA client to be updated in a much more automated way than is currently the case.

Additionally, the process must be accessible so that it can be used to reinstall the application from scratch if required.

The process may also include functionality to support:
*Optional updates
*Database updates preserving the data content

== Solution Overview ==
A separate Updater application will be written that allows updates of the application to be remotely installed.

== Scope ==



= Set-up =

== Pre-requisites ==

== Menu Structure ==

== Data ==



= Functional Description =

== EPOD PDA Client/Server ==
The Server file structure will be modified to include a ''PDAUpdates'' folder under the ''Webservice/Calidus_EPOD'' folder. This is where any updated PDA Client and Updater CAB files will be held.

== Update CAB file building ==
The Update (CAB) file built will be modified to automatically include the full version information from the EPOD Client app contained within it. It will also create a subdirectory of the install directory called Updater.

The build process will change for the PDA Client.

The following build projects will need to be constructed:
*A Build for fresh install on a device containing both EPOD_CLIENT and EPOD_UPDATER (both installed)
*A Build for EPOD_CLIENT only
*A Build for EPOD_UPDATER only

== EPOD PDA Client/Server ==
The Client app will be modified to check the default Updater subdirectory for any file with AppName "EpodUpdater". If one is found, a message box will be displayed showing that "an essential system update is required - when complete please press 'OK'". Once cleared, the EPOD client app will run the CAB file to update the Updater app.

When complete and control is returned to the EPOD client, the client will continue with the logon request.

The Client app will be modified to send out the current versions of the Client and Updater application within the logon request.

The Server will check the available Client CAB files within the server file structure for the latest version of the CAB files for the Updater and the EPOD Client.
For each program found, if the latest found is greater than the version passed in on the logon request message, the server will add tags to the outbound logon response message:
*EPOD_VERS - CAB version number of the EPOD client
*EPOD_FILE_NAME - Filename of the EPOD Client CAB file
*REQUIRED - at this time this will be set to "Y" only
*UPD_VERS - CAB version number of the Updater client
*UPD_FILE_NAME - Filename of the EPOD Updater CAB file

After processing the content of the standing data and configuration within the logon message, the client will check the latest version of the CAB file from the logon response message.

If the new tags are present, the client will check the REQUIRED tag. If this is set to "N", the Client app will pop up a message to the user, informing them than an update is available and whether it should be installed. If the user enters '''No''', the Client app will continue with its normal processing.

If the user responds '''Yes''' or the "REQUIRED" tag is set to "Y", the Client app will run the Updater app, passing a number of parameters:
*WEBSERVICE - the WebService URL.
*EPOD_VERS - CAB version number of the EPOD client
*EPOD_FILE_NAME - Filename of the EPOD Client CAB file
*UPD_VERS - CAB version number of the Updater client
*UPD_FILE_NAME - Filename of the EPOD Updater CAB file

Once the Updater app is started, the EPOD Client app will exit.

== Update App ==
A separate Updater application will be written that allows updates of the application to be remotely installed.

If no command-line parameters have been specified (or the ''WEBSERVICE'' parameter is blank) then app will open the EPOD Client database and extract the WebService URL. The database will be disposed of at this stage.

The app will modify the WebService URL to keep all domain and sub-domain information, discard the service name and add ''PDAUpdates/'' to the end. For example URL ''<nowiki>http://www.x.com:9091/y/WebService/Calidus_EPOD/Calidus_EPOD.asmx</nowiki>'' becomes ''<nowiki>http://www.x.com:9091/y/WebService/Calidus_EPOD/PDAUpdates/</nowiki>''.

A single form will be displayed showing:
*the Version and File Name of files being downloaded (i.e. both the PDA Client and Updater if there is one) with a read-only check-box showing whether the files have been downloaded.
*a progress bar to show the progress of downloading
*a read-only Install check-box, showing whether the files have been successfully installed
*A Re-start check-box, pre-checked, to indicate whether the EPOD client should be re-started on completion of the update.

The app will check whether the files have already been downloaded, by checking the versions of any downloaded CAB files within the ''Updater'' folder. If all files have not been downloaded, a dialogue will ask whether the files should be downloaded at this time. If the user answers '''No''' then the app will display a popup box showing that the Update was not applied and exit the app.

If the user answers ''Yes'', the application will start the download of the files, showing the progress through a progress bar on the form.

If the files have been downloaded successfully, a dialogue will ask whether the update is to be installed. If the user answers '''No''' then the app will display a popup box showing that the Update was not applied and exit the app.

If the user answers ''Yes'', the application will start the install of the EPOD Client CAB file only.

Once this installation is complete, the form will display 'Update complete - click OK to exit' on the back form.

If an Updater CAB file has been downloaded, the form will also display 'This Updater app will be updated when EPOD is next started'.

When the user clicks ''OK'', the app will check the 'Restart' check-box - if checked, this will re-start the EPOD Client app. Regardless, the Updater app will then exit.


{{Doc_Appendix
|Appendix=A
|Estimate=N
|Glossary=EPOD
|Ref1= 
|RefV1= 
|RefDate1= 
|REQ=0
|EST=0
|FS=0
|TS=0
|DEV=0
|ST=0
|IMP=0
|Client={{#var:Client}}
|Year={{#var:Year}}
|FSEST=Y
|Rev1=Tony Walker
|Rev1Title=Consultant
}}
[[Category:{{#var:Client}} FS]]

FS 294838 Proctor ePOD Modifications

2012-01-31T16:49:30Z

Milesl: /* Admin System */

<div class="noprint">
{{#vardefine:Client|PROC}}
{{#vardefine:ClientName|Proctors}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Proctors ePOD Modifications}}
{{#vardefine:Version|0.5}}
{{#vardefine:Date|26th January 2012}}
{{#vardefine:Reference|294838}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==

== Solution Overview ==

Jobs will be received for Collection and Delivery from the following main customer types:
*Suppliers
*Customers
*Proctors-operated Warehouses
*3rd Party Warehouses

The jobs will be updated into the ''CALIDUS'' EPOD system through the standard WebService interface.

This job upload will create 2 tasks:
*A Collection Job
*A Delivery Job

Every Collection and Delivery will be specified separately within the interface, with the Product and Quantity specified for all jobs. Linked collections and deliveries will have the same Job Code, but will be distinguished by the Job Type (i.e. Collection or Delivery).

The Upload system will also identify the Loads onto which jobs are planned, as all planning is completed through the Proctors' ERP system.

In phase 1, the initial uploads will be sent to the EPOD system with either no load information, or with the load ID set to a default value.

In phase 2, the initial uploads will be sent tot he EPOD system with either no load information, or with the correct load identified against them. It will then be possible to subsequently update the Load for a job through another update of the Job alone.

There are two types of job:
* Customer/Supplier jobs - jobs that begin or end with a Customer or Supplier.
* Inter-warehouse Transfer - jobs that begin and end from Warehouses

All jobs will be categorised by the ''CALIDUS'' EPOD Job Group into one of the two categories - this will define the paperwork produced by the system when the job is completed. The Job Group will be agreed and sent to the system in the upload files.

Once jobs from Proctors-controlled warehouses are picked and marshalled, updated Jobs will be sent to the EPOD system, detailing the actual containers (pallets) and product quantities on each.

{{Note}} If this data is not available at the time of collecting or delivering the associated jobs, the system will check periodically through a regularly-scheduled automatic process.

Collection jobs from a Proctors-operated warehouse should then have containers and product quantities specified against them. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.

{{Warning}} In this circumstance, where pallet information has not been received, the automatic update of the job when complete will identify on product and quantity information, not pallet information.

The process for a Collection of this type will be:
* Confirm arrival to warehouse.
* Scan/Enter/Select Pallets to be collected.
* Once completed, confirm collection through depot signature.

Collection jobs from a Customer, Supplier or 3rd party warehouse (i.e. non-Proctors) will have the Product and Quantity created against them (i.e. no containers/pallets). The process will be:
* Confirm arrival to customer/supplier/warehouse.
* Scan/Enter/Select Products to be collected.
* Confirm total quantity of the products.
* Once completed, confirm collection through customer/supplier signature.

A Delivery of a non-Proctors job will have only product and quantity details. The process will be:
* Confirm arrival to customer.
* Scan/Enter/Select Products to be delivered.
* Confirm total quantity of the products.
* Once completed, confirm delivery through customer signature.

A Delivery of Proctors job should have container (pallet), product and quantities. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.
The process will be:
* Confirm arrival to customer/depot.
* Scan/Enter/Select pallets being delivered
* Once completed, confirm delivery through customer/depot signature.

Two new POD document formats will be created:
* A Delivery format, configured for use on Customer/Supplier jobs.
* A Transfer format, configured for use on Inter-warehouse Transfers.
These formats will be defined against the Job group provided on the upload.
In order for these to be created to match the current formats as closely as possible, the ''CALIDUS'' EPOD Job Import will be extended to add new fields, identified in detail later in the document.

''CALIDUS'' EPOD will be set up to allow certain customers to be automatically emailed upon completion of jobs to and from them. When enabled, the format associated to the Job Group will be sent to the Customer's associated email address, if there is one.

{{Note}} Email notification of the POD or POC will be attempted if this feature is turned on and if the customer has an email address. If depots or suppliers do not require notification of collections or deliveries, it must be ensured that the customers created do not have an email address.

Confirmation or cancellation of the final job on a particular reference (i.e. the final delivery of a job) will trigger an automatic update of the ERP system. This will be configurable but is expected to be through an email of the standard EPOD XML job update message. This update will be a scheduled process that will regularly check and attempt to update when possible. It will be scheduled to run as often as required by the client, up to once per minute.

== Scope ==



= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
The two new fixed Job Groups will be set up for Proctors-controlled warehouses and 3rd-party. The former will be configured with the Stock Transfer POD format, whilst the latter will be configured with the other format.


= Functional Description =
The total changes required are:
* Database
* XML Import/Export
* Auto-Export
* Admin
* PDA Client
** Delivery/Collection Without Products
* New POD formats
* PDF Production

== Database Changes ==

=== EPOD_JOB ===
New Fields:
*EPL_SIGNED_UNCHECKED
*EPL_DNOTE_NUMBER - Delivery Note Number / Stock Transfer Number
*EPL_ORDER_DATE
*EPL_SALES_CONTACT - PPB Contact
{{Warning}}
*EPL_PICKER - Picked By
*EPL_CONVERTED
Changes:
*Indexing applied to EPL_JOB_CODE, EPL_JOB_TYPE. This will be a repeating index.
*Indexing applied to EPL_XFER_FLAG. This will be a repeating index.

=== EPOD_PRODUCT ===

*EPL_UNIT_TYPE
*EPL_DESCRIPTION_LONG
*EPL_PRODUCT_QTY_ORDERED
{{Warning}}
*EPL_LOCATION
*EPL_LOCATION_QUANTITY

=== EPOD_JOB_GROUP ===

*EPL_CONTAINER_ONLY - Controls container only delivery

=== XF_CONFIG ===

EPOD_JOB will require a new field of two characters EPL_XFER_FLAG, this will be defaulted to "".
EPOD_SITE and EPOD_JOB_GROUP will require a new field EPL_XF_CONFIG which will link to the EPL_XF_CONFIG_ID. If no export is required this will be blank.

A new table EPOD_XF_CONFIG will be created consisting of:
*EPL_XF_CONFIG_ID: A ten character unique field
*EPL_DESCRIPTION
*EPL_XF_TYPE: A ten character field identifying the type of export (SOAP, File, Email)
*EPL_XF_DESTINATION: A 255 character field identifying the destination of the export
*EPL_XF_PARM: Additional parameters for example subject for email

A new table EPOD_XF_AUDIT_HEADER will be created consisting of:
*EPL_HEADER_ID: A unique auto-increment Id
*EPL_SITE_ID: Indexed
*EPL_JOB_GROUP: Indexed
*EPL_REQUEST_DATA: A maximum length free-text field
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)

A new table EPOD_XF_AUDIT_DETAIL will be created consisting of:
*EPL_HEADER_ID: Foreign key to EPOD_XF_AUDIT_HEADER
*EPL_DETAIL_ID: A unique auto-increment Id
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)
{{Note}} This table is for future development and will not be used at this time.

== XML Interface ==

=== Import ===

The system shall use the EPL_JOB_CODE field as a reference linking the delivery and collection, the index used shall be EPL_JOB_CODE and EPL_JOB_TYPE. The field EPL_JOB_ID will always be unique, this will be auto-generated by our system if not passed in.

Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

The following XML would have the same outcome as above without the generation of container records:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

Both the collection and delivery must share the same EPL_JOB_CODE reference.

Within Phase One it is suggested that the following XML structure is used, importing only jobs and using the ePOD Admin System to plan these directly onto loads, as apposed to unplanning and re-planning.

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>.
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>

==== Update ====

To update the jobs with the Container details, Proctors' ERP must follow the same standard structure as the import.
All Job, Container and Product tags that are populated and present will update the relevant details in the ''CALIDUS'' EPOD system.

{{Note}}
* If the EPL_JOB_ID is blank (as expected for the Proctors interface, as the Collection and Deliveries will be linked via EPL_JOB_CODE), the system will check to see whether a job exists for this EPL_JOB_CODE and EPL_JOB_TYPE. If so, the record will be updated. If not, a new record (with a generated EPL_JOB_ID) will be created.
* If the EPL_JOB_ID is not blank, the system will check to see whether a job exists for this EPL_JOB_ID. If so, the record will be updated. If not, a new record will be created with this EPL_JOB_ID.
* If the EPL_LOAD_ID is left blank, the system will not update the Load ID of the Job.
* If the EPOD_CONTAINERS tag is not populated, the system will not update any container information. If it is present, the system will delete any existing container information and replace it with the information in the containers tag.
* If the EPOD_PRODUCTS tag is not populated, the system will not update any product information. If it is present, the system will delete any existing product information and replace it with the information in the product tag.

=== Export ===

At the point of job status changed the system will export the Jobs structure using the standard XML and send this to a predefined email address, for interfacing with the ERP system. This will be configured using the XF_CONFIG section of the system.

The required email functionality will need to be added to the existing export process.

The following XML is produced by the export, this example shows the export with multiple Jobs:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PHOTO_ID/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/> <EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575903</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

The following XML is produced by the export, this example shows the export with a single Job:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

==== Process ====

Whenever a job is updated to Cancelled or Complete (i.e. when the jobs are updated by the PDA client, or when jobs are updated via the Admin system), after committing the changes to the database, the Auto Export flag will be checked against the Job Group and Site. If this flag is present the EPL_JOB record will have the EPL_XFER_FLAG set to N, to indicate that the record requires interfacing but has not yet been sent.

{{Note}} These changes will be committed into the Data Access Layer, so that the same code will be called whether running this through the Admin or PDA server functions.

A timed process will be running to send any Jobs with the Xfer flag of N.
The process will:
*Retrieve all jobs on the EPL_JOBS table with the Xfer flag set to N, sorted by Site and Job Group.
*For each record found in distinct Site and Job Group:
**Load the details of this Job ID,
**Generate the XML export as per the standard for currently existing exports
**Once all jobs for the Site/Job Group are exported:
***Get the configuration of the Job Group. If the configuration for the Job Group does not exist, get the configuration for the Site.
***Attempt to transfer this to the destination specified in the configuration.

If this process if successful then the Xfer flag on the Job record will be set to Y, and a success audit record written.
If this fails the flag on the job will be set to N and a record will be written to a audit table with details of the failure.
If the file is send successfully but a message is received from the destination advising of this problem then an audit record will be written and the flag will be set to N.

This timed process will be scheduled on the system. The frequency of the process will be defined by the schedule and can be no more frequent that one per minute. If the process is already running, the process will wait for the next cycle before starting.

The status of the audit records based on the result are:
* S for success;
* SF for success send but error at the receivers, and;
* F for failure to send.
These records will be cleared down once they are older than 7 days.

== Admin System ==

Within Phase one the Admin interface will be used to plan Jobs onto loads, all required functionality has been implemented. Within phase two this will not be required as Proctors will interface pre-planned loads.
The following changes will need to be made to the admin system to reflect the database changes:

===EPOD_JOB===

*EPL_SIGNED_UNCHECKED - Visible on the POD only, this field is not searchable
*EPL_DNOTE_NUMBER - Delivery Note Number / Stock Transfer Number - Entry only
*EPL_ORDER_DATE - Entry only
*EPL_SALES_CONTACT - PPB Contact - Entry only

===EPOD_PRODUCT===

*EPL_UNIT_TYPE - Visible against the product record and available for entry
*EPL_DESCRIPTION_LONG - Visible against the product record and available for entry
*EPL_PRODUCT_QTY_ORDERED - Visible against the product record and available for entry

===EPOD_JOB_GROUP===

*EPL_CONTAINER_ONLY - Controls container only delivery - Visible and Editable

===XF_CONFIG===

A audit and maintenance screen will be required.

This will allow users to search the EPOD_XF_AUDIT_HEADER table by EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_JOB_GROUP. With a later implementation allowing to search for EPL_JOB_ID, or EPL_LOAD_ID.

This screen will display the header records details, EPL_JOB_GROUP, EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_STATUS_DESCRIPTION, and EPL_REQUEST_DATA.
{{note|This would be best displayed within a popup of some kind. For future implementation, the editing and resending of this data may be needed. Doing so a link would need to be made to each job.
}}

== PDA Client ==

The DB changes will need to be reflected on the PDA.

The PDA will need to be implemented with the functionality to transfer collection details to the delivery job, based on matching Job Codes. This includes altering the planned delivery quantity to the actual collection quantity specified in the collection.

The PDA will need to select the appropriate delivery or collection process based on the jobs attributes:
*Collections
**Proctors-Controlled Warehouse - Collection of Containers without Products
**Non-Proctors Location - Collection of Products without Containers
*Deliveries
**Proctors Collection - Delivery of Containers without Products.
**Non-Proctors Collection - Delivery of Products without Containers

When starting a collection or delivery from a Proctors-Controlled Warehouse a update check must be forced (this is currently handled under the standard process) if no container records are received, then an alert is given to the user advising that the data may not be up to date.

====Standard Collection====

====Collection of Containers without Products====
This will check a parameter on the Job Group - if Container-only Collection is enabled and there are no loose products, the collection will continue as Container only, otherwise the standard (Products Without Containers) collection process will be used.

The user is presented with a list of Containers for collection. The user selects a container either through text entry or scanning. Users have the ability to short-deliver by container only and use the exception process to document any non-delivered containers. When all Containers are accounted for, the user is prompted to complete the job, with a customer signature.

====Collection of Products without Containers====
The user is presented with a list of products for collection. The user confirms collection of each product as in the standard approach. When all Products are accounted for the user is prompted to complete the job, with a customer signature.

====Delivery of Products without Containers====
The process is the same as Collection of Products without Containers.

====Delivery of Containers without Products====
The process is the same as Collection of Containers without Products.

=== Photos ===
Photos will be captured using the standard exception process. User's must be aware that quality of the images will affect GPRS usage, higher quality equals longer more date to transfer. This can only be controlled on the PDA itself and must be set in the PDA's camera settings.

== New POD formats ==
New POD formats will be created for the operation.

The POD or POC format produced will be dependant of the Job Group associated to the Job.

All images captured relating to the Job will be displayed on a second page of the POD/POC document, with the associated detail information (Job ID, Container ID, Product Code, Image description). Again image quality is dependant on device settings, which affects the image size.

Fields on the Delivery Note document will be sourced from the following database fields:
* Delivery Note: EPL_DNOTE_NUMBER (New field)
* Customer Address: {{Warning}} From where?
* Delivery Address: Address information from the Job's Customer.
* Customer Tel No: From the Job's Customer.
* Cust No/Contact: From the Job's Customer.
* Our Order No: EPL_JOB_CODE
* Order Date: EPL_ORDER_DATE (New Field)
* Customer Order No: EPL_CUST_REF
* PPB Contact: EPL_SALES_CONTACT (New Field)
* Product Reference: EPL_PRODUCT_CODE
* Product Description: EPL_DESCRIPTION and EPL_DESCRIPTION_LONG
* Due Date: EPL_START_PLANNED_DATE/TIME {{Warning}} Is this the same for all lines?
* Unit: EPL_UNIT_TYPE (New Field)
* Quantity: EPL_PRODUCT_QTY_ORDERED (New Field)
* Quantity Despatched: EPL_PRODUCT_QTY_PLANNED
* Quantity Delivered: EPL_PRODUCT_QTY_ACTUAL
* No Of Parcels: {{Warning}} No longer relevant to either Containerised or product-only deliveries
* Pallet ID: EPL_CONTAINER_ID
* Special Instructions: EPL_JOB_INSTRUCTION
* Total Weight: See below
* Delivered By: PDA User Name
* Print Name: EPL_CUST_SIGNATORY (entered by PDA user)
* Date: Job Completion Date
* Signed Unchecked: EPL_SIGNED_UNCHECKED (New Field)

Weights will be calculated at product level. The weight must be passed through as part of the interfaced product record in the EPL_PRODUCT_WEIGHT. This must be weight per unit and will be calculated excluding tare weight.

{{Warning}}The following elements have been excluded from the design:
* Barcode
* Vat No
* Picked
* Converted

Fields on the Transfer Note document will be sourced from the following database fields (where different from the Delivery Note):
* Stock Transfer Note: EPL_DNOTE_NUMBER (New Field)
* Transfer Stock From: From the Collection's Customer information
* Transfer Stock To: From the Delivery's Customer information
* Xfer Ref No: EPL_JOB_CODE
* Input By: EPL_SALES_CONTACT (New Field)
* Part Number: EPL_PRODUCT_ID
* Product Description: EPL_DESCRIPTION

{{Warning}}The following elements have been excluded from the design:
* Location
* Location Qty

==PDF Production==
A new rule will be added at a Site level to control whether emails to customers will be HTML-Embedded or PDF attachment style.

The system will check this rule when:
# The "Email To" button is pressed on the "View POD" page
# auto-emailed documents are being produced.

If this rule is not enabled, the system will send emails as now (embedded HTML emails).

If this rule is enabled, the system will:
*Export and save the page to a temporary directory, with all images rendered.
*Run the saved page through a conversion routine to convert the HTML to a PDF page (saved in the same directory).
*Attach this generated PDF to the email and send
*Delete the temporary folder.

The conversion routine will use the WkHtmlToPDF program with default parameters - this must be installed on the server.



= Appendix A: POD Formats =
[[File:Delivery Note.jpg|600px|border]]

[[File:Stock Transfer Note.jpg|600px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|Ref1=
|RefV1=
|RefDate1=
|REQ=0
|EST=0
|FS=5.0
|TS=0
|DEV=36
|ST=5.00
|IMP=2.0
|Client={{#var:Client}}
|Year=2012
|FSEST=N
|Rev1=Matt Turner
|Rev1Title=OBS Representative
|Rev2=Stephen McCartney
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 294838 Proctor ePOD Modifications

2012-01-31T16:43:42Z

Milesl: /* Admin System */

<div class="noprint">
{{#vardefine:Client|PROC}}
{{#vardefine:ClientName|Proctors}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Proctors ePOD Modifications}}
{{#vardefine:Version|0.5}}
{{#vardefine:Date|26th January 2012}}
{{#vardefine:Reference|294838}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==

== Solution Overview ==

Jobs will be received for Collection and Delivery from the following main customer types:
*Suppliers
*Customers
*Proctors-operated Warehouses
*3rd Party Warehouses

The jobs will be updated into the ''CALIDUS'' EPOD system through the standard WebService interface.

This job upload will create 2 tasks:
*A Collection Job
*A Delivery Job

Every Collection and Delivery will be specified separately within the interface, with the Product and Quantity specified for all jobs. Linked collections and deliveries will have the same Job Code, but will be distinguished by the Job Type (i.e. Collection or Delivery).

The Upload system will also identify the Loads onto which jobs are planned, as all planning is completed through the Proctors' ERP system.

In phase 1, the initial uploads will be sent to the EPOD system with either no load information, or with the load ID set to a default value.

In phase 2, the initial uploads will be sent tot he EPOD system with either no load information, or with the correct load identified against them. It will then be possible to subsequently update the Load for a job through another update of the Job alone.

There are two types of job:
* Customer/Supplier jobs - jobs that begin or end with a Customer or Supplier.
* Inter-warehouse Transfer - jobs that begin and end from Warehouses

All jobs will be categorised by the ''CALIDUS'' EPOD Job Group into one of the two categories - this will define the paperwork produced by the system when the job is completed. The Job Group will be agreed and sent to the system in the upload files.

Once jobs from Proctors-controlled warehouses are picked and marshalled, updated Jobs will be sent to the EPOD system, detailing the actual containers (pallets) and product quantities on each.

{{Note}} If this data is not available at the time of collecting or delivering the associated jobs, the system will check periodically through a regularly-scheduled automatic process.

Collection jobs from a Proctors-operated warehouse should then have containers and product quantities specified against them. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.

{{Warning}} In this circumstance, where pallet information has not been received, the automatic update of the job when complete will identify on product and quantity information, not pallet information.

The process for a Collection of this type will be:
* Confirm arrival to warehouse.
* Scan/Enter/Select Pallets to be collected.
* Once completed, confirm collection through depot signature.

Collection jobs from a Customer, Supplier or 3rd party warehouse (i.e. non-Proctors) will have the Product and Quantity created against them (i.e. no containers/pallets). The process will be:
* Confirm arrival to customer/supplier/warehouse.
* Scan/Enter/Select Products to be collected.
* Confirm total quantity of the products.
* Once completed, confirm collection through customer/supplier signature.

A Delivery of a non-Proctors job will have only product and quantity details. The process will be:
* Confirm arrival to customer.
* Scan/Enter/Select Products to be delivered.
* Confirm total quantity of the products.
* Once completed, confirm delivery through customer signature.

A Delivery of Proctors job should have container (pallet), product and quantities. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.
The process will be:
* Confirm arrival to customer/depot.
* Scan/Enter/Select pallets being delivered
* Once completed, confirm delivery through customer/depot signature.

Two new POD document formats will be created:
* A Delivery format, configured for use on Customer/Supplier jobs.
* A Transfer format, configured for use on Inter-warehouse Transfers.
These formats will be defined against the Job group provided on the upload.
In order for these to be created to match the current formats as closely as possible, the ''CALIDUS'' EPOD Job Import will be extended to add new fields, identified in detail later in the document.

''CALIDUS'' EPOD will be set up to allow certain customers to be automatically emailed upon completion of jobs to and from them. When enabled, the format associated to the Job Group will be sent to the Customer's associated email address, if there is one.

{{Note}} Email notification of the POD or POC will be attempted if this feature is turned on and if the customer has an email address. If depots or suppliers do not require notification of collections or deliveries, it must be ensured that the customers created do not have an email address.

Confirmation or cancellation of the final job on a particular reference (i.e. the final delivery of a job) will trigger an automatic update of the ERP system. This will be configurable but is expected to be through an email of the standard EPOD XML job update message. This update will be a scheduled process that will regularly check and attempt to update when possible. It will be scheduled to run as often as required by the client, up to once per minute.

== Scope ==



= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
The two new fixed Job Groups will be set up for Proctors-controlled warehouses and 3rd-party. The former will be configured with the Stock Transfer POD format, whilst the latter will be configured with the other format.


= Functional Description =
The total changes required are:
* Database
* XML Import/Export
* Auto-Export
* Admin
* PDA Client
** Delivery/Collection Without Products
* New POD formats
* PDF Production

== Database Changes ==

=== EPOD_JOB ===
New Fields:
*EPL_SIGNED_UNCHECKED
*EPL_DNOTE_NUMBER - Delivery Note Number / Stock Transfer Number
*EPL_ORDER_DATE
*EPL_SALES_CONTACT - PPB Contact
{{Warning}}
*EPL_PICKER - Picked By
*EPL_CONVERTED
Changes:
*Indexing applied to EPL_JOB_CODE, EPL_JOB_TYPE. This will be a repeating index.
*Indexing applied to EPL_XFER_FLAG. This will be a repeating index.

=== EPOD_PRODUCT ===

*EPL_UNIT_TYPE
*EPL_DESCRIPTION_LONG
*EPL_PRODUCT_QTY_ORDERED
{{Warning}}
*EPL_LOCATION
*EPL_LOCATION_QUANTITY

=== EPOD_JOB_GROUP ===

*EPL_CONTAINER_ONLY - Controls container only delivery

=== XF_CONFIG ===

EPOD_JOB will require a new field of two characters EPL_XFER_FLAG, this will be defaulted to "".
EPOD_SITE and EPOD_JOB_GROUP will require a new field EPL_XF_CONFIG which will link to the EPL_XF_CONFIG_ID. If no export is required this will be blank.

A new table EPOD_XF_CONFIG will be created consisting of:
*EPL_XF_CONFIG_ID: A ten character unique field
*EPL_DESCRIPTION
*EPL_XF_TYPE: A ten character field identifying the type of export (SOAP, File, Email)
*EPL_XF_DESTINATION: A 255 character field identifying the destination of the export
*EPL_XF_PARM: Additional parameters for example subject for email

A new table EPOD_XF_AUDIT_HEADER will be created consisting of:
*EPL_HEADER_ID: A unique auto-increment Id
*EPL_SITE_ID: Indexed
*EPL_JOB_GROUP: Indexed
*EPL_REQUEST_DATA: A maximum length free-text field
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)

A new table EPOD_XF_AUDIT_DETAIL will be created consisting of:
*EPL_HEADER_ID: Foreign key to EPOD_XF_AUDIT_HEADER
*EPL_DETAIL_ID: A unique auto-increment Id
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)
{{Note}} This table is for future development and will not be used at this time.

== XML Interface ==

=== Import ===

The system shall use the EPL_JOB_CODE field as a reference linking the delivery and collection, the index used shall be EPL_JOB_CODE and EPL_JOB_TYPE. The field EPL_JOB_ID will always be unique, this will be auto-generated by our system if not passed in.

Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

The following XML would have the same outcome as above without the generation of container records:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

Both the collection and delivery must share the same EPL_JOB_CODE reference.

Within Phase One it is suggested that the following XML structure is used, importing only jobs and using the ePOD Admin System to plan these directly onto loads, as apposed to unplanning and re-planning.

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>.
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>

==== Update ====

To update the jobs with the Container details, Proctors' ERP must follow the same standard structure as the import.
All Job, Container and Product tags that are populated and present will update the relevant details in the ''CALIDUS'' EPOD system.

{{Note}}
* If the EPL_JOB_ID is blank (as expected for the Proctors interface, as the Collection and Deliveries will be linked via EPL_JOB_CODE), the system will check to see whether a job exists for this EPL_JOB_CODE and EPL_JOB_TYPE. If so, the record will be updated. If not, a new record (with a generated EPL_JOB_ID) will be created.
* If the EPL_JOB_ID is not blank, the system will check to see whether a job exists for this EPL_JOB_ID. If so, the record will be updated. If not, a new record will be created with this EPL_JOB_ID.
* If the EPL_LOAD_ID is left blank, the system will not update the Load ID of the Job.
* If the EPOD_CONTAINERS tag is not populated, the system will not update any container information. If it is present, the system will delete any existing container information and replace it with the information in the containers tag.
* If the EPOD_PRODUCTS tag is not populated, the system will not update any product information. If it is present, the system will delete any existing product information and replace it with the information in the product tag.

=== Export ===

At the point of job status changed the system will export the Jobs structure using the standard XML and send this to a predefined email address, for interfacing with the ERP system. This will be configured using the XF_CONFIG section of the system.

The required email functionality will need to be added to the existing export process.

The following XML is produced by the export, this example shows the export with multiple Jobs:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PHOTO_ID/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/> <EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575903</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

The following XML is produced by the export, this example shows the export with a single Job:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

==== Process ====

Whenever a job is updated to Cancelled or Complete (i.e. when the jobs are updated by the PDA client, or when jobs are updated via the Admin system), after committing the changes to the database, the Auto Export flag will be checked against the Job Group and Site. If this flag is present the EPL_JOB record will have the EPL_XFER_FLAG set to N, to indicate that the record requires interfacing but has not yet been sent.

{{Note}} These changes will be committed into the Data Access Layer, so that the same code will be called whether running this through the Admin or PDA server functions.

A timed process will be running to send any Jobs with the Xfer flag of N.
The process will:
*Retrieve all jobs on the EPL_JOBS table with the Xfer flag set to N, sorted by Site and Job Group.
*For each record found in distinct Site and Job Group:
**Load the details of this Job ID,
**Generate the XML export as per the standard for currently existing exports
**Once all jobs for the Site/Job Group are exported:
***Get the configuration of the Job Group. If the configuration for the Job Group does not exist, get the configuration for the Site.
***Attempt to transfer this to the destination specified in the configuration.

If this process if successful then the Xfer flag on the Job record will be set to Y, and a success audit record written.
If this fails the flag on the job will be set to N and a record will be written to a audit table with details of the failure.
If the file is send successfully but a message is received from the destination advising of this problem then an audit record will be written and the flag will be set to N.

This timed process will be scheduled on the system. The frequency of the process will be defined by the schedule and can be no more frequent that one per minute. If the process is already running, the process will wait for the next cycle before starting.

The status of the audit records based on the result are:
* S for success;
* SF for success send but error at the receivers, and;
* F for failure to send.
These records will be cleared down once they are older than 7 days.

== Admin System ==

Within Phase one the Admin interface will be used to plan Jobs onto loads, all required functionality has been implemented. Within phase two this will not be required as Proctors will interface pre-planned loads.
The following changes will need to be made to the admin system to reflect the database changes:

===EPOD_JOB===

*EPL_SIGNED_UNCHECKED - Visible on the POD only, this field is not searchable
*EPL_DNOTE_NUMBER - Delivery Note Number / Stock Transfer Number - Entry only
*EPL_ORDER_DATE - Entry only
*EPL_SALES_CONTACT - PPB Contact - Entry only

===EPOD_PRODUCT===

*EPL_UNIT_TYPE - Visible against the product record and available for entry
*EPL_DESCRIPTION_LONG - Visible against the product record and available for entry
*EPL_PRODUCT_QTY_ORDERED - Visible against the product record and available for entry

===EPOD_JOB_GROUP===

*EPL_CONTAINER_ONLY - Controls container only delivery - Visible and Editable

===XF_CONFIG===

A audit and maintenance screen will be required.

This will allow users to search the EPOD_XF_AUDIT_HEADER table by EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_JOB_GROUP. With a later implementation allowing to search for EPL_JOB_ID, or EPL_LOAD_ID.

This screen will display the header records details, EPL_JOB_GROUP, EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_STATUS_DESCRIPTION, and EPL_REQUEST_DATA.
{{comment|text=This would be best displayed within a popup of some kind.
|sign=[[User:Milesl]]|date=31/01/2012 16:27:56}}

{{comment|text=For future implementation, the editing and resending of this data may be needed. Doing so a link would need to be made to each job.
|sign=[[User:Milesl]]|date=31/01/2012 16:27:56}}

== PDA Client ==

The DB changes will need to be reflected on the PDA.

The PDA will need to be implemented with the functionality to transfer collection details to the delivery job, based on matching Job Codes. This includes altering the planned delivery quantity to the actual collection quantity specified in the collection.

The PDA will need to select the appropriate delivery or collection process based on the jobs attributes:
*Collections
**Proctors-Controlled Warehouse - Collection of Containers without Products
**Non-Proctors Location - Collection of Products without Containers
*Deliveries
**Proctors Collection - Delivery of Containers without Products.
**Non-Proctors Collection - Delivery of Products without Containers

When starting a collection or delivery from a Proctors-Controlled Warehouse a update check must be forced (this is currently handled under the standard process) if no container records are received, then an alert is given to the user advising that the data may not be up to date.

====Standard Collection====

====Collection of Containers without Products====
This will check a parameter on the Job Group - if Container-only Collection is enabled and there are no loose products, the collection will continue as Container only, otherwise the standard (Products Without Containers) collection process will be used.

The user is presented with a list of Containers for collection. The user selects a container either through text entry or scanning. Users have the ability to short-deliver by container only and use the exception process to document any non-delivered containers. When all Containers are accounted for, the user is prompted to complete the job, with a customer signature.

====Collection of Products without Containers====
The user is presented with a list of products for collection. The user confirms collection of each product as in the standard approach. When all Products are accounted for the user is prompted to complete the job, with a customer signature.

====Delivery of Products without Containers====
The process is the same as Collection of Products without Containers.

====Delivery of Containers without Products====
The process is the same as Collection of Containers without Products.

=== Photos ===
Photos will be captured using the standard exception process. User's must be aware that quality of the images will affect GPRS usage, higher quality equals longer more date to transfer. This can only be controlled on the PDA itself and must be set in the PDA's camera settings.

== New POD formats ==
New POD formats will be created for the operation.

The POD or POC format produced will be dependant of the Job Group associated to the Job.

All images captured relating to the Job will be displayed on a second page of the POD/POC document, with the associated detail information (Job ID, Container ID, Product Code, Image description). Again image quality is dependant on device settings, which affects the image size.

Fields on the Delivery Note document will be sourced from the following database fields:
* Delivery Note: EPL_DNOTE_NUMBER (New field)
* Customer Address: {{Warning}} From where?
* Delivery Address: Address information from the Job's Customer.
* Customer Tel No: From the Job's Customer.
* Cust No/Contact: From the Job's Customer.
* Our Order No: EPL_JOB_CODE
* Order Date: EPL_ORDER_DATE (New Field)
* Customer Order No: EPL_CUST_REF
* PPB Contact: EPL_SALES_CONTACT (New Field)
* Product Reference: EPL_PRODUCT_CODE
* Product Description: EPL_DESCRIPTION and EPL_DESCRIPTION_LONG
* Due Date: EPL_START_PLANNED_DATE/TIME {{Warning}} Is this the same for all lines?
* Unit: EPL_UNIT_TYPE (New Field)
* Quantity: EPL_PRODUCT_QTY_ORDERED (New Field)
* Quantity Despatched: EPL_PRODUCT_QTY_PLANNED
* Quantity Delivered: EPL_PRODUCT_QTY_ACTUAL
* No Of Parcels: {{Warning}} No longer relevant to either Containerised or product-only deliveries
* Pallet ID: EPL_CONTAINER_ID
* Special Instructions: EPL_JOB_INSTRUCTION
* Total Weight: See below
* Delivered By: PDA User Name
* Print Name: EPL_CUST_SIGNATORY (entered by PDA user)
* Date: Job Completion Date
* Signed Unchecked: EPL_SIGNED_UNCHECKED (New Field)

Weights will be calculated at product level. The weight must be passed through as part of the interfaced product record in the EPL_PRODUCT_WEIGHT. This must be weight per unit and will be calculated excluding tare weight.

{{Warning}}The following elements have been excluded from the design:
* Barcode
* Vat No
* Picked
* Converted

Fields on the Transfer Note document will be sourced from the following database fields (where different from the Delivery Note):
* Stock Transfer Note: EPL_DNOTE_NUMBER (New Field)
* Transfer Stock From: From the Collection's Customer information
* Transfer Stock To: From the Delivery's Customer information
* Xfer Ref No: EPL_JOB_CODE
* Input By: EPL_SALES_CONTACT (New Field)
* Part Number: EPL_PRODUCT_ID
* Product Description: EPL_DESCRIPTION

{{Warning}}The following elements have been excluded from the design:
* Location
* Location Qty

==PDF Production==
A new rule will be added at a Site level to control whether emails to customers will be HTML-Embedded or PDF attachment style.

The system will check this rule when:
# The "Email To" button is pressed on the "View POD" page
# auto-emailed documents are being produced.

If this rule is not enabled, the system will send emails as now (embedded HTML emails).

If this rule is enabled, the system will:
*Export and save the page to a temporary directory, with all images rendered.
*Run the saved page through a conversion routine to convert the HTML to a PDF page (saved in the same directory).
*Attach this generated PDF to the email and send
*Delete the temporary folder.

The conversion routine will use the WkHtmlToPDF program with default parameters - this must be installed on the server.



= Appendix A: POD Formats =
[[File:Delivery Note.jpg|600px|border]]

[[File:Stock Transfer Note.jpg|600px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|Ref1=
|RefV1=
|RefDate1=
|REQ=0
|EST=0
|FS=5.0
|TS=0
|DEV=36
|ST=5.00
|IMP=2.0
|Client={{#var:Client}}
|Year=2012
|FSEST=N
|Rev1=Matt Turner
|Rev1Title=OBS Representative
|Rev2=Stephen McCartney
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 294838 Proctor ePOD Modifications

2012-01-31T16:42:31Z

Milesl: /* Admin System */

<div class="noprint">
{{#vardefine:Client|PROC}}
{{#vardefine:ClientName|Proctors}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Proctors ePOD Modifications}}
{{#vardefine:Version|0.5}}
{{#vardefine:Date|26th January 2012}}
{{#vardefine:Reference|294838}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==

== Solution Overview ==

Jobs will be received for Collection and Delivery from the following main customer types:
*Suppliers
*Customers
*Proctors-operated Warehouses
*3rd Party Warehouses

The jobs will be updated into the ''CALIDUS'' EPOD system through the standard WebService interface.

This job upload will create 2 tasks:
*A Collection Job
*A Delivery Job

Every Collection and Delivery will be specified separately within the interface, with the Product and Quantity specified for all jobs. Linked collections and deliveries will have the same Job Code, but will be distinguished by the Job Type (i.e. Collection or Delivery).

The Upload system will also identify the Loads onto which jobs are planned, as all planning is completed through the Proctors' ERP system.

In phase 1, the initial uploads will be sent to the EPOD system with either no load information, or with the load ID set to a default value.

In phase 2, the initial uploads will be sent tot he EPOD system with either no load information, or with the correct load identified against them. It will then be possible to subsequently update the Load for a job through another update of the Job alone.

There are two types of job:
* Customer/Supplier jobs - jobs that begin or end with a Customer or Supplier.
* Inter-warehouse Transfer - jobs that begin and end from Warehouses

All jobs will be categorised by the ''CALIDUS'' EPOD Job Group into one of the two categories - this will define the paperwork produced by the system when the job is completed. The Job Group will be agreed and sent to the system in the upload files.

Once jobs from Proctors-controlled warehouses are picked and marshalled, updated Jobs will be sent to the EPOD system, detailing the actual containers (pallets) and product quantities on each.

{{Note}} If this data is not available at the time of collecting or delivering the associated jobs, the system will check periodically through a regularly-scheduled automatic process.

Collection jobs from a Proctors-operated warehouse should then have containers and product quantities specified against them. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.

{{Warning}} In this circumstance, where pallet information has not been received, the automatic update of the job when complete will identify on product and quantity information, not pallet information.

The process for a Collection of this type will be:
* Confirm arrival to warehouse.
* Scan/Enter/Select Pallets to be collected.
* Once completed, confirm collection through depot signature.

Collection jobs from a Customer, Supplier or 3rd party warehouse (i.e. non-Proctors) will have the Product and Quantity created against them (i.e. no containers/pallets). The process will be:
* Confirm arrival to customer/supplier/warehouse.
* Scan/Enter/Select Products to be collected.
* Confirm total quantity of the products.
* Once completed, confirm collection through customer/supplier signature.

A Delivery of a non-Proctors job will have only product and quantity details. The process will be:
* Confirm arrival to customer.
* Scan/Enter/Select Products to be delivered.
* Confirm total quantity of the products.
* Once completed, confirm delivery through customer signature.

A Delivery of Proctors job should have container (pallet), product and quantities. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.
The process will be:
* Confirm arrival to customer/depot.
* Scan/Enter/Select pallets being delivered
* Once completed, confirm delivery through customer/depot signature.

Two new POD document formats will be created:
* A Delivery format, configured for use on Customer/Supplier jobs.
* A Transfer format, configured for use on Inter-warehouse Transfers.
These formats will be defined against the Job group provided on the upload.
In order for these to be created to match the current formats as closely as possible, the ''CALIDUS'' EPOD Job Import will be extended to add new fields, identified in detail later in the document.

''CALIDUS'' EPOD will be set up to allow certain customers to be automatically emailed upon completion of jobs to and from them. When enabled, the format associated to the Job Group will be sent to the Customer's associated email address, if there is one.

{{Note}} Email notification of the POD or POC will be attempted if this feature is turned on and if the customer has an email address. If depots or suppliers do not require notification of collections or deliveries, it must be ensured that the customers created do not have an email address.

Confirmation or cancellation of the final job on a particular reference (i.e. the final delivery of a job) will trigger an automatic update of the ERP system. This will be configurable but is expected to be through an email of the standard EPOD XML job update message. This update will be a scheduled process that will regularly check and attempt to update when possible. It will be scheduled to run as often as required by the client, up to once per minute.

== Scope ==



= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
The two new fixed Job Groups will be set up for Proctors-controlled warehouses and 3rd-party. The former will be configured with the Stock Transfer POD format, whilst the latter will be configured with the other format.


= Functional Description =
The total changes required are:
* Database
* XML Import/Export
* Auto-Export
* Admin
* PDA Client
** Delivery/Collection Without Products
* New POD formats
* PDF Production

== Database Changes ==

=== EPOD_JOB ===
New Fields:
*EPL_SIGNED_UNCHECKED
*EPL_DNOTE_NUMBER - Delivery Note Number / Stock Transfer Number
*EPL_ORDER_DATE
*EPL_SALES_CONTACT - PPB Contact
{{Warning}}
*EPL_PICKER - Picked By
*EPL_CONVERTED
Changes:
*Indexing applied to EPL_JOB_CODE, EPL_JOB_TYPE. This will be a repeating index.
*Indexing applied to EPL_XFER_FLAG. This will be a repeating index.

=== EPOD_PRODUCT ===

*EPL_UNIT_TYPE
*EPL_DESCRIPTION_LONG
*EPL_PRODUCT_QTY_ORDERED
{{Warning}}
*EPL_LOCATION
*EPL_LOCATION_QUANTITY

=== EPOD_JOB_GROUP ===

*EPL_CONTAINER_ONLY - Controls container only delivery

=== XF_CONFIG ===

EPOD_JOB will require a new field of two characters EPL_XFER_FLAG, this will be defaulted to "".
EPOD_SITE and EPOD_JOB_GROUP will require a new field EPL_XF_CONFIG which will link to the EPL_XF_CONFIG_ID. If no export is required this will be blank.

A new table EPOD_XF_CONFIG will be created consisting of:
*EPL_XF_CONFIG_ID: A ten character unique field
*EPL_DESCRIPTION
*EPL_XF_TYPE: A ten character field identifying the type of export (SOAP, File, Email)
*EPL_XF_DESTINATION: A 255 character field identifying the destination of the export
*EPL_XF_PARM: Additional parameters for example subject for email

A new table EPOD_XF_AUDIT_HEADER will be created consisting of:
*EPL_HEADER_ID: A unique auto-increment Id
*EPL_SITE_ID: Indexed
*EPL_JOB_GROUP: Indexed
*EPL_REQUEST_DATA: A maximum length free-text field
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)

A new table EPOD_XF_AUDIT_DETAIL will be created consisting of:
*EPL_HEADER_ID: Foreign key to EPOD_XF_AUDIT_HEADER
*EPL_DETAIL_ID: A unique auto-increment Id
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)
{{Note}} This table is for future development and will not be used at this time.

== XML Interface ==

=== Import ===

The system shall use the EPL_JOB_CODE field as a reference linking the delivery and collection, the index used shall be EPL_JOB_CODE and EPL_JOB_TYPE. The field EPL_JOB_ID will always be unique, this will be auto-generated by our system if not passed in.

Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

The following XML would have the same outcome as above without the generation of container records:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

Both the collection and delivery must share the same EPL_JOB_CODE reference.

Within Phase One it is suggested that the following XML structure is used, importing only jobs and using the ePOD Admin System to plan these directly onto loads, as apposed to unplanning and re-planning.

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>.
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>

==== Update ====

To update the jobs with the Container details, Proctors' ERP must follow the same standard structure as the import.
All Job, Container and Product tags that are populated and present will update the relevant details in the ''CALIDUS'' EPOD system.

{{Note}}
* If the EPL_JOB_ID is blank (as expected for the Proctors interface, as the Collection and Deliveries will be linked via EPL_JOB_CODE), the system will check to see whether a job exists for this EPL_JOB_CODE and EPL_JOB_TYPE. If so, the record will be updated. If not, a new record (with a generated EPL_JOB_ID) will be created.
* If the EPL_JOB_ID is not blank, the system will check to see whether a job exists for this EPL_JOB_ID. If so, the record will be updated. If not, a new record will be created with this EPL_JOB_ID.
* If the EPL_LOAD_ID is left blank, the system will not update the Load ID of the Job.
* If the EPOD_CONTAINERS tag is not populated, the system will not update any container information. If it is present, the system will delete any existing container information and replace it with the information in the containers tag.
* If the EPOD_PRODUCTS tag is not populated, the system will not update any product information. If it is present, the system will delete any existing product information and replace it with the information in the product tag.

=== Export ===

At the point of job status changed the system will export the Jobs structure using the standard XML and send this to a predefined email address, for interfacing with the ERP system. This will be configured using the XF_CONFIG section of the system.

The required email functionality will need to be added to the existing export process.

The following XML is produced by the export, this example shows the export with multiple Jobs:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PHOTO_ID/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/> <EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575903</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

The following XML is produced by the export, this example shows the export with a single Job:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

==== Process ====

Whenever a job is updated to Cancelled or Complete (i.e. when the jobs are updated by the PDA client, or when jobs are updated via the Admin system), after committing the changes to the database, the Auto Export flag will be checked against the Job Group and Site. If this flag is present the EPL_JOB record will have the EPL_XFER_FLAG set to N, to indicate that the record requires interfacing but has not yet been sent.

{{Note}} These changes will be committed into the Data Access Layer, so that the same code will be called whether running this through the Admin or PDA server functions.

A timed process will be running to send any Jobs with the Xfer flag of N.
The process will:
*Retrieve all jobs on the EPL_JOBS table with the Xfer flag set to N, sorted by Site and Job Group.
*For each record found in distinct Site and Job Group:
**Load the details of this Job ID,
**Generate the XML export as per the standard for currently existing exports
**Once all jobs for the Site/Job Group are exported:
***Get the configuration of the Job Group. If the configuration for the Job Group does not exist, get the configuration for the Site.
***Attempt to transfer this to the destination specified in the configuration.

If this process if successful then the Xfer flag on the Job record will be set to Y, and a success audit record written.
If this fails the flag on the job will be set to N and a record will be written to a audit table with details of the failure.
If the file is send successfully but a message is received from the destination advising of this problem then an audit record will be written and the flag will be set to N.

This timed process will be scheduled on the system. The frequency of the process will be defined by the schedule and can be no more frequent that one per minute. If the process is already running, the process will wait for the next cycle before starting.

The status of the audit records based on the result are:
* S for success;
* SF for success send but error at the receivers, and;
* F for failure to send.
These records will be cleared down once they are older than 7 days.

== Admin System ==

Within Phase one the Admin interface will be used to plan Jobs onto loads, all required functionality has been implemented. Within phase two this will not be required as Proctors will interface pre-planned loads.
The following changes will need to be made to the admin system to reflect the database changes:

===EPOD_JOB===

EPL_SIGNED_UNCHECKED - Visible on the POD only, this field is not searchable
EPL_DNOTE_NUMBER - Delivery Note Number / Stock Transfer Number - Entry only
EPL_ORDER_DATE - Entry only
EPL_SALES_CONTACT - PPB Contact - Entry only

===EPOD_PRODUCT===

EPL_UNIT_TYPE - Visible against the product record and available for entry
EPL_DESCRIPTION_LONG - Visible against the product record and available for entry
EPL_PRODUCT_QTY_ORDERED - Visible against the product record and available for entry

===EPOD_JOB_GROUP===

EPL_CONTAINER_ONLY - Controls container only delivery - Visible and Editable

===XF_CONFIG===

A audit and maintenance screen will be required.

This will allow users to search the EPOD_XF_AUDIT_HEADER table by EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_JOB_GROUP. With a later implementation allowing to search for EPL_JOB_ID, or EPL_LOAD_ID.

This screen will display the header records details, EPL_JOB_GROUP, EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_STATUS_DESCRIPTION, and EPL_REQUEST_DATA.
{{comment|text=This would be best displayed within a popup of some kind.
|sign=[[User:Milesl]]|date=31/01/2012 16:27:56}}

{{comment|text=For future implementation, the editing and resending of this data may be needed. Doing so a link would need to be made to each job.
|sign=[[User:Milesl]]|date=31/01/2012 16:27:56}}

== PDA Client ==

The DB changes will need to be reflected on the PDA.

The PDA will need to be implemented with the functionality to transfer collection details to the delivery job, based on matching Job Codes. This includes altering the planned delivery quantity to the actual collection quantity specified in the collection.

The PDA will need to select the appropriate delivery or collection process based on the jobs attributes:
*Collections
**Proctors-Controlled Warehouse - Collection of Containers without Products
**Non-Proctors Location - Collection of Products without Containers
*Deliveries
**Proctors Collection - Delivery of Containers without Products.
**Non-Proctors Collection - Delivery of Products without Containers

When starting a collection or delivery from a Proctors-Controlled Warehouse a update check must be forced (this is currently handled under the standard process) if no container records are received, then an alert is given to the user advising that the data may not be up to date.

====Standard Collection====

====Collection of Containers without Products====
This will check a parameter on the Job Group - if Container-only Collection is enabled and there are no loose products, the collection will continue as Container only, otherwise the standard (Products Without Containers) collection process will be used.

The user is presented with a list of Containers for collection. The user selects a container either through text entry or scanning. Users have the ability to short-deliver by container only and use the exception process to document any non-delivered containers. When all Containers are accounted for, the user is prompted to complete the job, with a customer signature.

====Collection of Products without Containers====
The user is presented with a list of products for collection. The user confirms collection of each product as in the standard approach. When all Products are accounted for the user is prompted to complete the job, with a customer signature.

====Delivery of Products without Containers====
The process is the same as Collection of Products without Containers.

====Delivery of Containers without Products====
The process is the same as Collection of Containers without Products.

=== Photos ===
Photos will be captured using the standard exception process. User's must be aware that quality of the images will affect GPRS usage, higher quality equals longer more date to transfer. This can only be controlled on the PDA itself and must be set in the PDA's camera settings.

== New POD formats ==
New POD formats will be created for the operation.

The POD or POC format produced will be dependant of the Job Group associated to the Job.

All images captured relating to the Job will be displayed on a second page of the POD/POC document, with the associated detail information (Job ID, Container ID, Product Code, Image description). Again image quality is dependant on device settings, which affects the image size.

Fields on the Delivery Note document will be sourced from the following database fields:
* Delivery Note: EPL_DNOTE_NUMBER (New field)
* Customer Address: {{Warning}} From where?
* Delivery Address: Address information from the Job's Customer.
* Customer Tel No: From the Job's Customer.
* Cust No/Contact: From the Job's Customer.
* Our Order No: EPL_JOB_CODE
* Order Date: EPL_ORDER_DATE (New Field)
* Customer Order No: EPL_CUST_REF
* PPB Contact: EPL_SALES_CONTACT (New Field)
* Product Reference: EPL_PRODUCT_CODE
* Product Description: EPL_DESCRIPTION and EPL_DESCRIPTION_LONG
* Due Date: EPL_START_PLANNED_DATE/TIME {{Warning}} Is this the same for all lines?
* Unit: EPL_UNIT_TYPE (New Field)
* Quantity: EPL_PRODUCT_QTY_ORDERED (New Field)
* Quantity Despatched: EPL_PRODUCT_QTY_PLANNED
* Quantity Delivered: EPL_PRODUCT_QTY_ACTUAL
* No Of Parcels: {{Warning}} No longer relevant to either Containerised or product-only deliveries
* Pallet ID: EPL_CONTAINER_ID
* Special Instructions: EPL_JOB_INSTRUCTION
* Total Weight: See below
* Delivered By: PDA User Name
* Print Name: EPL_CUST_SIGNATORY (entered by PDA user)
* Date: Job Completion Date
* Signed Unchecked: EPL_SIGNED_UNCHECKED (New Field)

Weights will be calculated at product level. The weight must be passed through as part of the interfaced product record in the EPL_PRODUCT_WEIGHT. This must be weight per unit and will be calculated excluding tare weight.

{{Warning}}The following elements have been excluded from the design:
* Barcode
* Vat No
* Picked
* Converted

Fields on the Transfer Note document will be sourced from the following database fields (where different from the Delivery Note):
* Stock Transfer Note: EPL_DNOTE_NUMBER (New Field)
* Transfer Stock From: From the Collection's Customer information
* Transfer Stock To: From the Delivery's Customer information
* Xfer Ref No: EPL_JOB_CODE
* Input By: EPL_SALES_CONTACT (New Field)
* Part Number: EPL_PRODUCT_ID
* Product Description: EPL_DESCRIPTION

{{Warning}}The following elements have been excluded from the design:
* Location
* Location Qty

==PDF Production==
A new rule will be added at a Site level to control whether emails to customers will be HTML-Embedded or PDF attachment style.

The system will check this rule when:
# The "Email To" button is pressed on the "View POD" page
# auto-emailed documents are being produced.

If this rule is not enabled, the system will send emails as now (embedded HTML emails).

If this rule is enabled, the system will:
*Export and save the page to a temporary directory, with all images rendered.
*Run the saved page through a conversion routine to convert the HTML to a PDF page (saved in the same directory).
*Attach this generated PDF to the email and send
*Delete the temporary folder.

The conversion routine will use the WkHtmlToPDF program with default parameters - this must be installed on the server.



= Appendix A: POD Formats =
[[File:Delivery Note.jpg|600px|border]]

[[File:Stock Transfer Note.jpg|600px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|Ref1=
|RefV1=
|RefDate1=
|REQ=0
|EST=0
|FS=5.0
|TS=0
|DEV=36
|ST=5.00
|IMP=2.0
|Client={{#var:Client}}
|Year=2012
|FSEST=N
|Rev1=Matt Turner
|Rev1Title=OBS Representative
|Rev2=Stephen McCartney
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 294838 Proctor ePOD Modifications

2012-01-31T16:41:29Z

Milesl: /* Admin System */

<div class="noprint">
{{#vardefine:Client|PROC}}
{{#vardefine:ClientName|Proctors}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Proctors ePOD Modifications}}
{{#vardefine:Version|0.5}}
{{#vardefine:Date|26th January 2012}}
{{#vardefine:Reference|294838}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==

== Solution Overview ==

Jobs will be received for Collection and Delivery from the following main customer types:
*Suppliers
*Customers
*Proctors-operated Warehouses
*3rd Party Warehouses

The jobs will be updated into the ''CALIDUS'' EPOD system through the standard WebService interface.

This job upload will create 2 tasks:
*A Collection Job
*A Delivery Job

Every Collection and Delivery will be specified separately within the interface, with the Product and Quantity specified for all jobs. Linked collections and deliveries will have the same Job Code, but will be distinguished by the Job Type (i.e. Collection or Delivery).

The Upload system will also identify the Loads onto which jobs are planned, as all planning is completed through the Proctors' ERP system.

In phase 1, the initial uploads will be sent to the EPOD system with either no load information, or with the load ID set to a default value.

In phase 2, the initial uploads will be sent tot he EPOD system with either no load information, or with the correct load identified against them. It will then be possible to subsequently update the Load for a job through another update of the Job alone.

There are two types of job:
* Customer/Supplier jobs - jobs that begin or end with a Customer or Supplier.
* Inter-warehouse Transfer - jobs that begin and end from Warehouses

All jobs will be categorised by the ''CALIDUS'' EPOD Job Group into one of the two categories - this will define the paperwork produced by the system when the job is completed. The Job Group will be agreed and sent to the system in the upload files.

Once jobs from Proctors-controlled warehouses are picked and marshalled, updated Jobs will be sent to the EPOD system, detailing the actual containers (pallets) and product quantities on each.

{{Note}} If this data is not available at the time of collecting or delivering the associated jobs, the system will check periodically through a regularly-scheduled automatic process.

Collection jobs from a Proctors-operated warehouse should then have containers and product quantities specified against them. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.

{{Warning}} In this circumstance, where pallet information has not been received, the automatic update of the job when complete will identify on product and quantity information, not pallet information.

The process for a Collection of this type will be:
* Confirm arrival to warehouse.
* Scan/Enter/Select Pallets to be collected.
* Once completed, confirm collection through depot signature.

Collection jobs from a Customer, Supplier or 3rd party warehouse (i.e. non-Proctors) will have the Product and Quantity created against them (i.e. no containers/pallets). The process will be:
* Confirm arrival to customer/supplier/warehouse.
* Scan/Enter/Select Products to be collected.
* Confirm total quantity of the products.
* Once completed, confirm collection through customer/supplier signature.

A Delivery of a non-Proctors job will have only product and quantity details. The process will be:
* Confirm arrival to customer.
* Scan/Enter/Select Products to be delivered.
* Confirm total quantity of the products.
* Once completed, confirm delivery through customer signature.

A Delivery of Proctors job should have container (pallet), product and quantities. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.
The process will be:
* Confirm arrival to customer/depot.
* Scan/Enter/Select pallets being delivered
* Once completed, confirm delivery through customer/depot signature.

Two new POD document formats will be created:
* A Delivery format, configured for use on Customer/Supplier jobs.
* A Transfer format, configured for use on Inter-warehouse Transfers.
These formats will be defined against the Job group provided on the upload.
In order for these to be created to match the current formats as closely as possible, the ''CALIDUS'' EPOD Job Import will be extended to add new fields, identified in detail later in the document.

''CALIDUS'' EPOD will be set up to allow certain customers to be automatically emailed upon completion of jobs to and from them. When enabled, the format associated to the Job Group will be sent to the Customer's associated email address, if there is one.

{{Note}} Email notification of the POD or POC will be attempted if this feature is turned on and if the customer has an email address. If depots or suppliers do not require notification of collections or deliveries, it must be ensured that the customers created do not have an email address.

Confirmation or cancellation of the final job on a particular reference (i.e. the final delivery of a job) will trigger an automatic update of the ERP system. This will be configurable but is expected to be through an email of the standard EPOD XML job update message. This update will be a scheduled process that will regularly check and attempt to update when possible. It will be scheduled to run as often as required by the client, up to once per minute.

== Scope ==



= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
The two new fixed Job Groups will be set up for Proctors-controlled warehouses and 3rd-party. The former will be configured with the Stock Transfer POD format, whilst the latter will be configured with the other format.


= Functional Description =
The total changes required are:
* Database
* XML Import/Export
* Auto-Export
* Admin
* PDA Client
** Delivery/Collection Without Products
* New POD formats
* PDF Production

== Database Changes ==

=== EPOD_JOB ===
New Fields:
*EPL_SIGNED_UNCHECKED
*EPL_DNOTE_NUMBER - Delivery Note Number / Stock Transfer Number
*EPL_ORDER_DATE
*EPL_SALES_CONTACT - PPB Contact
{{Warning}}
*EPL_PICKER - Picked By
*EPL_CONVERTED
Changes:
*Indexing applied to EPL_JOB_CODE, EPL_JOB_TYPE. This will be a repeating index.
*Indexing applied to EPL_XFER_FLAG. This will be a repeating index.

=== EPOD_PRODUCT ===

*EPL_UNIT_TYPE
*EPL_DESCRIPTION_LONG
*EPL_PRODUCT_QTY_ORDERED
{{Warning}}
*EPL_LOCATION
*EPL_LOCATION_QUANTITY

=== EPOD_JOB_GROUP ===

*EPL_CONTAINER_ONLY - Controls container only delivery

=== XF_CONFIG ===

EPOD_JOB will require a new field of two characters EPL_XFER_FLAG, this will be defaulted to "".
EPOD_SITE and EPOD_JOB_GROUP will require a new field EPL_XF_CONFIG which will link to the EPL_XF_CONFIG_ID. If no export is required this will be blank.

A new table EPOD_XF_CONFIG will be created consisting of:
*EPL_XF_CONFIG_ID: A ten character unique field
*EPL_DESCRIPTION
*EPL_XF_TYPE: A ten character field identifying the type of export (SOAP, File, Email)
*EPL_XF_DESTINATION: A 255 character field identifying the destination of the export
*EPL_XF_PARM: Additional parameters for example subject for email

A new table EPOD_XF_AUDIT_HEADER will be created consisting of:
*EPL_HEADER_ID: A unique auto-increment Id
*EPL_SITE_ID: Indexed
*EPL_JOB_GROUP: Indexed
*EPL_REQUEST_DATA: A maximum length free-text field
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)

A new table EPOD_XF_AUDIT_DETAIL will be created consisting of:
*EPL_HEADER_ID: Foreign key to EPOD_XF_AUDIT_HEADER
*EPL_DETAIL_ID: A unique auto-increment Id
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)
{{Note}} This table is for future development and will not be used at this time.

== XML Interface ==

=== Import ===

The system shall use the EPL_JOB_CODE field as a reference linking the delivery and collection, the index used shall be EPL_JOB_CODE and EPL_JOB_TYPE. The field EPL_JOB_ID will always be unique, this will be auto-generated by our system if not passed in.

Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

The following XML would have the same outcome as above without the generation of container records:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

Both the collection and delivery must share the same EPL_JOB_CODE reference.

Within Phase One it is suggested that the following XML structure is used, importing only jobs and using the ePOD Admin System to plan these directly onto loads, as apposed to unplanning and re-planning.

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>.
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>

==== Update ====

To update the jobs with the Container details, Proctors' ERP must follow the same standard structure as the import.
All Job, Container and Product tags that are populated and present will update the relevant details in the ''CALIDUS'' EPOD system.

{{Note}}
* If the EPL_JOB_ID is blank (as expected for the Proctors interface, as the Collection and Deliveries will be linked via EPL_JOB_CODE), the system will check to see whether a job exists for this EPL_JOB_CODE and EPL_JOB_TYPE. If so, the record will be updated. If not, a new record (with a generated EPL_JOB_ID) will be created.
* If the EPL_JOB_ID is not blank, the system will check to see whether a job exists for this EPL_JOB_ID. If so, the record will be updated. If not, a new record will be created with this EPL_JOB_ID.
* If the EPL_LOAD_ID is left blank, the system will not update the Load ID of the Job.
* If the EPOD_CONTAINERS tag is not populated, the system will not update any container information. If it is present, the system will delete any existing container information and replace it with the information in the containers tag.
* If the EPOD_PRODUCTS tag is not populated, the system will not update any product information. If it is present, the system will delete any existing product information and replace it with the information in the product tag.

=== Export ===

At the point of job status changed the system will export the Jobs structure using the standard XML and send this to a predefined email address, for interfacing with the ERP system. This will be configured using the XF_CONFIG section of the system.

The required email functionality will need to be added to the existing export process.

The following XML is produced by the export, this example shows the export with multiple Jobs:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PHOTO_ID/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/> <EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575903</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

The following XML is produced by the export, this example shows the export with a single Job:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

==== Process ====

Whenever a job is updated to Cancelled or Complete (i.e. when the jobs are updated by the PDA client, or when jobs are updated via the Admin system), after committing the changes to the database, the Auto Export flag will be checked against the Job Group and Site. If this flag is present the EPL_JOB record will have the EPL_XFER_FLAG set to N, to indicate that the record requires interfacing but has not yet been sent.

{{Note}} These changes will be committed into the Data Access Layer, so that the same code will be called whether running this through the Admin or PDA server functions.

A timed process will be running to send any Jobs with the Xfer flag of N.
The process will:
*Retrieve all jobs on the EPL_JOBS table with the Xfer flag set to N, sorted by Site and Job Group.
*For each record found in distinct Site and Job Group:
**Load the details of this Job ID,
**Generate the XML export as per the standard for currently existing exports
**Once all jobs for the Site/Job Group are exported:
***Get the configuration of the Job Group. If the configuration for the Job Group does not exist, get the configuration for the Site.
***Attempt to transfer this to the destination specified in the configuration.

If this process if successful then the Xfer flag on the Job record will be set to Y, and a success audit record written.
If this fails the flag on the job will be set to N and a record will be written to a audit table with details of the failure.
If the file is send successfully but a message is received from the destination advising of this problem then an audit record will be written and the flag will be set to N.

This timed process will be scheduled on the system. The frequency of the process will be defined by the schedule and can be no more frequent that one per minute. If the process is already running, the process will wait for the next cycle before starting.

The status of the audit records based on the result are:
* S for success;
* SF for success send but error at the receivers, and;
* F for failure to send.
These records will be cleared down once they are older than 7 days.

== Admin System ==

Within Phase one the Admin interface will be used to plan Jobs onto loads, all required functionality has been implemented. Within phase two this will not be required as Proctors will interface pre-planned loads.
The following changes will need to be made to the admin system to reflect the database changes:

EPOD_JOB

New Fields:

EPL_SIGNED_UNCHECKED - Visible on the POD only, this field is not searchable
EPL_DNOTE_NUMBER - Delivery Note Number / Stock Transfer Number - Entry only
EPL_ORDER_DATE - Entry only
EPL_SALES_CONTACT - PPB Contact - Entry only

EPOD_PRODUCT

EPL_UNIT_TYPE - Visible against the product record and available for entry
EPL_DESCRIPTION_LONG - Visible against the product record and available for entry
EPL_PRODUCT_QTY_ORDERED - Visible against the product record and available for entry

EPOD_JOB_GROUP

EPL_CONTAINER_ONLY - Controls container only delivery - Visible and Editable

XF_CONFIG

A audit and maintenance screen will be required.

This will allow users to search the EPOD_XF_AUDIT_HEADER table by EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_JOB_GROUP. With a later implementation allowing to search for EPL_JOB_ID, or EPL_LOAD_ID.

This screen will display the header records details, EPL_JOB_GROUP, EPL_REQUEST_DATE, EPL_REQUEST_TIME, EPL_STATUS, EPL_STATUS_DESCRIPTION, and EPL_REQUEST_DATA.
{{comment|text=This would be best displayed within a popup of some kind.
|sign=[[User:Milesl]]|date=31/01/2012 16:27:56}}

{{comment|text=For future implementation, the editing and resending of this data may be needed. Doing so a link would need to be made to each job.
|sign=[[User:Milesl]]|date=31/01/2012 16:27:56}}

== PDA Client ==

The DB changes will need to be reflected on the PDA.

The PDA will need to be implemented with the functionality to transfer collection details to the delivery job, based on matching Job Codes. This includes altering the planned delivery quantity to the actual collection quantity specified in the collection.

The PDA will need to select the appropriate delivery or collection process based on the jobs attributes:
*Collections
**Proctors-Controlled Warehouse - Collection of Containers without Products
**Non-Proctors Location - Collection of Products without Containers
*Deliveries
**Proctors Collection - Delivery of Containers without Products.
**Non-Proctors Collection - Delivery of Products without Containers

When starting a collection or delivery from a Proctors-Controlled Warehouse a update check must be forced (this is currently handled under the standard process) if no container records are received, then an alert is given to the user advising that the data may not be up to date.

====Standard Collection====

====Collection of Containers without Products====
This will check a parameter on the Job Group - if Container-only Collection is enabled and there are no loose products, the collection will continue as Container only, otherwise the standard (Products Without Containers) collection process will be used.

The user is presented with a list of Containers for collection. The user selects a container either through text entry or scanning. Users have the ability to short-deliver by container only and use the exception process to document any non-delivered containers. When all Containers are accounted for, the user is prompted to complete the job, with a customer signature.

====Collection of Products without Containers====
The user is presented with a list of products for collection. The user confirms collection of each product as in the standard approach. When all Products are accounted for the user is prompted to complete the job, with a customer signature.

====Delivery of Products without Containers====
The process is the same as Collection of Products without Containers.

====Delivery of Containers without Products====
The process is the same as Collection of Containers without Products.

=== Photos ===
Photos will be captured using the standard exception process. User's must be aware that quality of the images will affect GPRS usage, higher quality equals longer more date to transfer. This can only be controlled on the PDA itself and must be set in the PDA's camera settings.

== New POD formats ==
New POD formats will be created for the operation.

The POD or POC format produced will be dependant of the Job Group associated to the Job.

All images captured relating to the Job will be displayed on a second page of the POD/POC document, with the associated detail information (Job ID, Container ID, Product Code, Image description). Again image quality is dependant on device settings, which affects the image size.

Fields on the Delivery Note document will be sourced from the following database fields:
* Delivery Note: EPL_DNOTE_NUMBER (New field)
* Customer Address: {{Warning}} From where?
* Delivery Address: Address information from the Job's Customer.
* Customer Tel No: From the Job's Customer.
* Cust No/Contact: From the Job's Customer.
* Our Order No: EPL_JOB_CODE
* Order Date: EPL_ORDER_DATE (New Field)
* Customer Order No: EPL_CUST_REF
* PPB Contact: EPL_SALES_CONTACT (New Field)
* Product Reference: EPL_PRODUCT_CODE
* Product Description: EPL_DESCRIPTION and EPL_DESCRIPTION_LONG
* Due Date: EPL_START_PLANNED_DATE/TIME {{Warning}} Is this the same for all lines?
* Unit: EPL_UNIT_TYPE (New Field)
* Quantity: EPL_PRODUCT_QTY_ORDERED (New Field)
* Quantity Despatched: EPL_PRODUCT_QTY_PLANNED
* Quantity Delivered: EPL_PRODUCT_QTY_ACTUAL
* No Of Parcels: {{Warning}} No longer relevant to either Containerised or product-only deliveries
* Pallet ID: EPL_CONTAINER_ID
* Special Instructions: EPL_JOB_INSTRUCTION
* Total Weight: See below
* Delivered By: PDA User Name
* Print Name: EPL_CUST_SIGNATORY (entered by PDA user)
* Date: Job Completion Date
* Signed Unchecked: EPL_SIGNED_UNCHECKED (New Field)

Weights will be calculated at product level. The weight must be passed through as part of the interfaced product record in the EPL_PRODUCT_WEIGHT. This must be weight per unit and will be calculated excluding tare weight.

{{Warning}}The following elements have been excluded from the design:
* Barcode
* Vat No
* Picked
* Converted

Fields on the Transfer Note document will be sourced from the following database fields (where different from the Delivery Note):
* Stock Transfer Note: EPL_DNOTE_NUMBER (New Field)
* Transfer Stock From: From the Collection's Customer information
* Transfer Stock To: From the Delivery's Customer information
* Xfer Ref No: EPL_JOB_CODE
* Input By: EPL_SALES_CONTACT (New Field)
* Part Number: EPL_PRODUCT_ID
* Product Description: EPL_DESCRIPTION

{{Warning}}The following elements have been excluded from the design:
* Location
* Location Qty

==PDF Production==
A new rule will be added at a Site level to control whether emails to customers will be HTML-Embedded or PDF attachment style.

The system will check this rule when:
# The "Email To" button is pressed on the "View POD" page
# auto-emailed documents are being produced.

If this rule is not enabled, the system will send emails as now (embedded HTML emails).

If this rule is enabled, the system will:
*Export and save the page to a temporary directory, with all images rendered.
*Run the saved page through a conversion routine to convert the HTML to a PDF page (saved in the same directory).
*Attach this generated PDF to the email and send
*Delete the temporary folder.

The conversion routine will use the WkHtmlToPDF program with default parameters - this must be installed on the server.



= Appendix A: POD Formats =
[[File:Delivery Note.jpg|600px|border]]

[[File:Stock Transfer Note.jpg|600px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|Ref1=
|RefV1=
|RefDate1=
|REQ=0
|EST=0
|FS=5.0
|TS=0
|DEV=36
|ST=5.00
|IMP=2.0
|Client={{#var:Client}}
|Year=2012
|FSEST=N
|Rev1=Matt Turner
|Rev1Title=OBS Representative
|Rev2=Stephen McCartney
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 294838 Proctor ePOD Modifications

2012-01-31T16:26:49Z

Milesl: /* Admin System */

<div class="noprint">
{{#vardefine:Client|PROC}}
{{#vardefine:ClientName|Proctors}}
{{#vardefine:System|''CALIDUS'' ePOD}}
{{#vardefine:Doc_Title|Proctors ePOD Modifications}}
{{#vardefine:Version|0.5}}
{{#vardefine:Date|26th January 2012}}
{{#vardefine:Reference|294838}}
</div>
{{Doc_Title
|Client={{#var:ClientName}}
|System={{#var:System}}
|Title={{#var:Doc_Title}}
|Reference=FS {{#var:Reference}}
|Version={{#var:Version}}
|Date={{#var:Date}}
}}


<div class="noprint">
= Functional Overview =

== Client Requirement ==

== Solution Overview ==

Jobs will be received for Collection and Delivery from the following main customer types:
*Suppliers
*Customers
*Proctors-operated Warehouses
*3rd Party Warehouses

The jobs will be updated into the ''CALIDUS'' EPOD system through the standard WebService interface.

This job upload will create 2 tasks:
*A Collection Job
*A Delivery Job

Every Collection and Delivery will be specified separately within the interface, with the Product and Quantity specified for all jobs. Linked collections and deliveries will have the same Job Code, but will be distinguished by the Job Type (i.e. Collection or Delivery).

The Upload system will also identify the Loads onto which jobs are planned, as all planning is completed through the Proctors' ERP system.

In phase 1, the initial uploads will be sent to the EPOD system with either no load information, or with the load ID set to a default value.

In phase 2, the initial uploads will be sent tot he EPOD system with either no load information, or with the correct load identified against them. It will then be possible to subsequently update the Load for a job through another update of the Job alone.

There are two types of job:
* Customer/Supplier jobs - jobs that begin or end with a Customer or Supplier.
* Inter-warehouse Transfer - jobs that begin and end from Warehouses

All jobs will be categorised by the ''CALIDUS'' EPOD Job Group into one of the two categories - this will define the paperwork produced by the system when the job is completed. The Job Group will be agreed and sent to the system in the upload files.

Once jobs from Proctors-controlled warehouses are picked and marshalled, updated Jobs will be sent to the EPOD system, detailing the actual containers (pallets) and product quantities on each.

{{Note}} If this data is not available at the time of collecting or delivering the associated jobs, the system will check periodically through a regularly-scheduled automatic process.

Collection jobs from a Proctors-operated warehouse should then have containers and product quantities specified against them. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.

{{Warning}} In this circumstance, where pallet information has not been received, the automatic update of the job when complete will identify on product and quantity information, not pallet information.

The process for a Collection of this type will be:
* Confirm arrival to warehouse.
* Scan/Enter/Select Pallets to be collected.
* Once completed, confirm collection through depot signature.

Collection jobs from a Customer, Supplier or 3rd party warehouse (i.e. non-Proctors) will have the Product and Quantity created against them (i.e. no containers/pallets). The process will be:
* Confirm arrival to customer/supplier/warehouse.
* Scan/Enter/Select Products to be collected.
* Confirm total quantity of the products.
* Once completed, confirm collection through customer/supplier signature.

A Delivery of a non-Proctors job will have only product and quantity details. The process will be:
* Confirm arrival to customer.
* Scan/Enter/Select Products to be delivered.
* Confirm total quantity of the products.
* Once completed, confirm delivery through customer signature.

A Delivery of Proctors job should have container (pallet), product and quantities. If this is not the case, the PDA client will force a check of these details at the point that the job is started. If these details are still not available (either that the PDA cannot connect to retrieve this or the data is unavailable from the ERP system), the PDA client will allow the user to continue loading the job, using only the product and quantity details.
The process will be:
* Confirm arrival to customer/depot.
* Scan/Enter/Select pallets being delivered
* Once completed, confirm delivery through customer/depot signature.

Two new POD document formats will be created:
* A Delivery format, configured for use on Customer/Supplier jobs.
* A Transfer format, configured for use on Inter-warehouse Transfers.
These formats will be defined against the Job group provided on the upload.
In order for these to be created to match the current formats as closely as possible, the ''CALIDUS'' EPOD Job Import will be extended to add new fields, identified in detail later in the document.

''CALIDUS'' EPOD will be set up to allow certain customers to be automatically emailed upon completion of jobs to and from them. When enabled, the format associated to the Job Group will be sent to the Customer's associated email address, if there is one.

{{Note}} Email notification of the POD or POC will be attempted if this feature is turned on and if the customer has an email address. If depots or suppliers do not require notification of collections or deliveries, it must be ensured that the customers created do not have an email address.

Confirmation or cancellation of the final job on a particular reference (i.e. the final delivery of a job) will trigger an automatic update of the ERP system. This will be configurable but is expected to be through an email of the standard EPOD XML job update message. This update will be a scheduled process that will regularly check and attempt to update when possible. It will be scheduled to run as often as required by the client, up to once per minute.

== Scope ==



= Set-up =

== Pre-requisites ==
For automatic updates through email and automatic emailing of POD/POC documents, the EPOD server must be configured with access to the customer's Email server.

== Menu Structure ==

== Data ==
The two new fixed Job Groups will be set up for Proctors-controlled warehouses and 3rd-party. The former will be configured with the Stock Transfer POD format, whilst the latter will be configured with the other format.


= Functional Description =
The total changes required are:
* Database
* XML Import/Export
* Auto-Export
* Admin
* PDA Client
** Delivery/Collection Without Products
* New POD formats
* PDF Production

== Database Changes ==

=== EPOD_JOB ===
New Fields:
*EPL_SIGNED_UNCHECKED
*EPL_DNOTE_NUMBER - Delivery Note Number / Stock Transfer Number
*EPL_ORDER_DATE
*EPL_SALES_CONTACT - PPB Contact
{{Warning}}
*EPL_PICKER - Picked By
*EPL_CONVERTED
Changes:
*Indexing applied to EPL_JOB_CODE, EPL_JOB_TYPE. This will be a repeating index.
*Indexing applied to EPL_XFER_FLAG. This will be a repeating index.

=== EPOD_PRODUCT ===

*EPL_UNIT_TYPE
*EPL_DESCRIPTION_LONG
*EPL_PRODUCT_QTY_ORDERED
{{Warning}}
*EPL_LOCATION
*EPL_LOCATION_QUANTITY

=== EPOD_JOB_GROUP ===

*EPL_CONTAINER_ONLY - Controls container only delivery

=== XF_CONFIG ===

EPOD_JOB will require a new field of two characters EPL_XFER_FLAG, this will be defaulted to "".
EPOD_SITE and EPOD_JOB_GROUP will require a new field EPL_XF_CONFIG which will link to the EPL_XF_CONFIG_ID. If no export is required this will be blank.

A new table EPOD_XF_CONFIG will be created consisting of:
*EPL_XF_CONFIG_ID: A ten character unique field
*EPL_DESCRIPTION
*EPL_XF_TYPE: A ten character field identifying the type of export (SOAP, File, Email)
*EPL_XF_DESTINATION: A 255 character field identifying the destination of the export
*EPL_XF_PARM: Additional parameters for example subject for email

A new table EPOD_XF_AUDIT_HEADER will be created consisting of:
*EPL_HEADER_ID: A unique auto-increment Id
*EPL_SITE_ID: Indexed
*EPL_JOB_GROUP: Indexed
*EPL_REQUEST_DATA: A maximum length free-text field
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)

A new table EPOD_XF_AUDIT_DETAIL will be created consisting of:
*EPL_HEADER_ID: Foreign key to EPOD_XF_AUDIT_HEADER
*EPL_DETAIL_ID: A unique auto-increment Id
*EPL_REQUEST_DATE
*EPL_REQUEST_TIME
*EPL_STATUS: Two character status field
*EPL_STATUS_DESCRIPTION: Returned Status Description (A maximum length free-text field)
{{Note}} This table is for future development and will not be used at this time.

== XML Interface ==

=== Import ===

The system shall use the EPL_JOB_CODE field as a reference linking the delivery and collection, the index used shall be EPL_JOB_CODE and EPL_JOB_TYPE. The field EPL_JOB_ID will always be unique, this will be auto-generated by our system if not passed in.

Proctors ERP system will provide the ePOD web service with the XML structure of the following example:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

The following XML would have the same outcome as above without the generation of container records:

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_LOADS>
<EPOD_LOAD>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_LOAD_START_PLANNED_DATE>20111129</EPL_LOAD_START_PLANNED_DATE>
<EPL_LOAD_START_PLANNED_TIME>00000000</EPL_LOAD_START_PLANNED_TIME>
<EPL_LOAD_END_PLANNED_DATE>20111129</EPL_LOAD_END_PLANNED_DATE>
<EPL__LOAD_END_PLANNED_TIME>00000000</EPL__LOAD_END_PLANNED_TIME>
<EPL_LOAD_DISTANCE_PLANNED>0</EPL_LOAD_DISTANCE_PLANNED>
<EPL_USER_ID>MATT</EPL_USER_ID>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
<EPL_PRODUCT_WEIGHT></EPL_PRODUCT_WEIGHT>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_LOAD>
</EPOD_LOADS>
</EPOD_IMPORT>

Both the collection and delivery must share the same EPL_JOB_CODE reference.

Within Phase One it is suggested that the following XML structure is used, importing only jobs and using the ePOD Admin System to plan these directly onto loads, as apposed to unplanning and re-planning.

<EPOD_IMPORT EPL_SITE_ID="TEST" EPL_USER_ID="ADM" EPL_USER_PASSWORD="TEST">
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_LOAD_ID></EPL_LOAD_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>00000000</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>20111129</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>00000000</EPL_END_PLANNED_TIME>
<EPL_JOB_CODE>JOB_CODE_001</EPL_JOB_CODE>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_OFFICE_INSTRUCTION>Free Text Instructions Admin Only</EPL_OFFICE_INSTRUCTION>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>.
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRIPTION_LONG></EPL_DESCRIPTION_LONG>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_IMPORT>

==== Update ====

To update the jobs with the Container details, Proctors' ERP must follow the same standard structure as the import.
All Job, Container and Product tags that are populated and present will update the relevant details in the ''CALIDUS'' EPOD system.

{{Note}}
* If the EPL_JOB_ID is blank (as expected for the Proctors interface, as the Collection and Deliveries will be linked via EPL_JOB_CODE), the system will check to see whether a job exists for this EPL_JOB_CODE and EPL_JOB_TYPE. If so, the record will be updated. If not, a new record (with a generated EPL_JOB_ID) will be created.
* If the EPL_JOB_ID is not blank, the system will check to see whether a job exists for this EPL_JOB_ID. If so, the record will be updated. If not, a new record will be created with this EPL_JOB_ID.
* If the EPL_LOAD_ID is left blank, the system will not update the Load ID of the Job.
* If the EPOD_CONTAINERS tag is not populated, the system will not update any container information. If it is present, the system will delete any existing container information and replace it with the information in the containers tag.
* If the EPOD_PRODUCTS tag is not populated, the system will not update any product information. If it is present, the system will delete any existing product information and replace it with the information in the product tag.

=== Export ===

At the point of job status changed the system will export the Jobs structure using the standard XML and send this to a predefined email address, for interfacing with the ERP system. This will be configured using the XF_CONFIG section of the system.

The required email functionality will need to be added to the existing export process.

The following XML is produced by the export, this example shows the export with multiple Jobs:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL></EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PHOTO_ID/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS/>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>D</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/> <EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>JohnSmithLtd</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>John Smith</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>19 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>john.smith@JohnSmithLtd.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575902</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_D</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575903</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

The following XML is produced by the export, this example shows the export with a single Job:

<?xml version="1.0"?>
<EPOD_EXPORT_JOB>
<EPOD_JOBS>
<EPOD_JOB>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_LOAD_ID>TIPIMPORT</EPL_LOAD_ID>
<EPL_JOB_TYPE>C</EPL_JOB_TYPE>
<EPL_JOB_GROUP>JG01</EPL_JOB_GROUP>
<EPL_JOB_INSTRUCTION>Free Text Instructions</EPL_JOB_INSTRUCTION>
<EPL_JOB_SIGNATURE/>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_CUSTOMER_CODE>WAREHOUSE1</EPL_CUSTOMER_CODE>
<EPL_PHOTO_ID/>
<EPL_ENG_SIGNATURE/>
<EPL_SEQUENCE/>
<EPL_START_PLANNED_DATE>20111129</EPL_START_PLANNED_DATE>
<EPL_START_PLANNED_TIME>0</EPL_START_PLANNED_TIME>
<EPL_END_PLANNED_DATE>0</EPL_END_PLANNED_DATE>
<EPL_END_PLANNED_TIME>0</EPL_END_PLANNED_TIME>
<EPL_START_ACTUAL_DATE>0</EPL_START_ACTUAL_DATE>
<EPL_START_ACTUAL_TIME>0</EPL_START_ACTUAL_TIME>
<EPL_END_ACTUAL_DATE>0</EPL_END_ACTUAL_DATE>
<EPL_END_ACTUAL_TIME>0</EPL_END_ACTUAL_TIME>
<EPL_DISTANCE_PLANNED>0</EPL_DISTANCE_PLANNED>
<EPL_DISTANCE_ACTUAL>0</EPL_DISTANCE_ACTUAL>
<EPL_DRIVING_TIME>0</EPL_DRIVING_TIME>
<EPL_DNOTE_NUMBER></EPL_DNOTE_NUMBER>
<EPL_ORDER_DATE></EPL_ORDER_DATE>
<EPL_SALES_CONTACT></EPL_SALES_CONTACT>
<EPL_PICKER></EPL_PICKER>
<EPL_CONVERTED></EPL_CONVERTED>
<EPL_CUSTOMER_NAME>Dave Jones</EPL_CUSTOMER_NAME>
<EPL_ADDRESS_1>16 Sutton Drive</EPL_ADDRESS_1>
<EPL_ADDRESS_2>Bebington</EPL_ADDRESS_2>
<EPL_ADDRESS_3>Wirral</EPL_ADDRESS_3>
<EPL_ADDRESS_4>Merseyside</EPL_ADDRESS_4>
<EPL_POSTCODE>CH62 9GR</EPL_POSTCODE>
<EPL_CONTACT>Dave Jones</EPL_CONTACT>
<EPL_TELEPHONE>08458795846</EPL_TELEPHONE>
<EPL_EMAIL>dave.jones@WAREHOUSE1.com</EPL_EMAIL>
<EPL_INVOICED/>
<EPL_CUST_SIGNATORY/>
<EPL_JOB_CODE/>
<EPL_CUST_REF>WAREHOUSE1_ORD0011</EPL_CUST_REF>
<EPL_OFFICE_INSTRUCTION/>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_CONTAINERS>
<EPOD_CONTAINER>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_CONTAINER_PACKAGE_CODE>XX00</EPL_CONTAINER_PACKAGE_CODE>
<EPL_CONTAINER_PACKAGE_DESC>Test Container</EPL_CONTAINER_PACKAGE_DESC>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
<EPOD_PRODUCTS>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD1</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
<EPOD_PRODUCT>
<EPL_SITE_ID>TEST</EPL_SITE_ID>
<EPL_JOB_ID>JOB_001_C</EPL_JOB_ID>
<EPL_CONTAINER_ID>0000000000001</EPL_CONTAINER_ID>
<EPL_PRODUCT_CODE>TESTPROD2</EPL_PRODUCT_CODE>
<EPL_SEQUENCE>0001</EPL_SEQUENCE>
<EPL_DESCRIPTION>TEST ITEM</EPL_DESCRIPTION>
<EPL_PRODUCT_QTY_PLANNED>1</EPL_PRODUCT_QTY_PLANNED>
<EPL_PRODUCT_QTY_ACTUAL>0</EPL_PRODUCT_QTY_ACTUAL>
<EPL_PRODUCT_QTY_CASE>0</EPL_PRODUCT_QTY_CASE>
<EPL_REASON_CODE/>
<EPL_STATUS>P</EPL_STATUS>
<EPL_PRODUCT_WEIGHT>0</EPL_PRODUCT_WEIGHT>
<EPL_CUST_REF/>
<EPL_ITEM_TYPE/>
<EPL_UNIT_TYPE></EPL_UNIT_TYPE>
<EPL_LOCATION></EPL_LOCATION>
<EPL_LOCATION_QUANTITY></EPL_LOCATION_QUANTITY>
<EPL_DESCRITPION_LONG></EPL_DESCRITPION_LONG>
<EPL_LAST_CHANGED_DATE>20120118</EPL_LAST_CHANGED_DATE>
<EPL_LAST_CHANGED_TIME>11575901</EPL_LAST_CHANGED_TIME>
</EPOD_PRODUCT>
</EPOD_PRODUCTS>
</EPOD_CONTAINER>
</EPOD_CONTAINERS>
<EPOD_SERVICES/>
</EPOD_JOB>
</EPOD_JOBS>
</EPOD_EXPORT_JOB>

==== Process ====

Whenever a job is updated to Cancelled or Complete (i.e. when the jobs are updated by the PDA client, or when jobs are updated via the Admin system), after committing the changes to the database, the Auto Export flag will be checked against the Job Group and Site. If this flag is present the EPL_JOB record will have the EPL_XFER_FLAG set to N, to indicate that the record requires interfacing but has not yet been sent.

{{Note}} These changes will be committed into the Data Access Layer, so that the same code will be called whether running this through the Admin or PDA server functions.

A timed process will be running to send any Jobs with the Xfer flag of N.
The process will:
*Retrieve all jobs on the EPL_JOBS table with the Xfer flag set to N, sorted by Site and Job Group.
*For each record found in distinct Site and Job Group:
**Load the details of this Job ID,
**Generate the XML export as per the standard for currently existing exports
**Once all jobs for the Site/Job Group are exported:
***Get the configuration of the Job Group. If the configuration for the Job Group does not exist, get the configuration for the Site.
***Attempt to transfer this to the destination specified in the configuration.

If this process if successful then the Xfer flag on the Job record will be set to Y, and a success audit record written.
If this fails the flag on the job will be set to N and a record will be written to a audit table with details of the failure.
If the file is send successfully but a message is received from the destination advising of this problem then an audit record will be written and the flag will be set to N.

This timed process will be scheduled on the system. The frequency of the process will be defined by the schedule and can be no more frequent that one per minute. If the process is already running, the process will wait for the next cycle before starting.

The status of the audit records based on the result are:
* S for success;
* SF for success send but error at the receivers, and;
* F for failure to send.
These records will be cleared down once they are older than 7 days.

== Admin System ==

Within Phase one the Admin interface will be used to plan Jobs onto loads, all required functionality has been implemented. Within phase two this will not be required as Proctors will interface pre-planned loads.
The following changes will need to be made to the admin system to reflect the database changes:
*

== PDA Client ==

The DB changes will need to be reflected on the PDA.

The PDA will need to be implemented with the functionality to transfer collection details to the delivery job, based on matching Job Codes. This includes altering the planned delivery quantity to the actual collection quantity specified in the collection.

The PDA will need to select the appropriate delivery or collection process based on the jobs attributes:
*Collections
**Proctors-Controlled Warehouse - Collection of Containers without Products
**Non-Proctors Location - Collection of Products without Containers
*Deliveries
**Proctors Collection - Delivery of Containers without Products.
**Non-Proctors Collection - Delivery of Products without Containers

When starting a collection or delivery from a Proctors-Controlled Warehouse a update check must be forced (this is currently handled under the standard process) if no container records are received, then an alert is given to the user advising that the data may not be up to date.

====Standard Collection====

====Collection of Containers without Products====
This will check a parameter on the Job Group - if Container-only Collection is enabled and there are no loose products, the collection will continue as Container only, otherwise the standard (Products Without Containers) collection process will be used.

The user is presented with a list of Containers for collection. The user selects a container either through text entry or scanning. Users have the ability to short-deliver by container only and use the exception process to document any non-delivered containers. When all Containers are accounted for, the user is prompted to complete the job, with a customer signature.

====Collection of Products without Containers====
The user is presented with a list of products for collection. The user confirms collection of each product as in the standard approach. When all Products are accounted for the user is prompted to complete the job, with a customer signature.

====Delivery of Products without Containers====
The process is the same as Collection of Products without Containers.

====Delivery of Containers without Products====
The process is the same as Collection of Containers without Products.

=== Photos ===
Photos will be captured using the standard exception process. User's must be aware that quality of the images will affect GPRS usage, higher quality equals longer more date to transfer. This can only be controlled on the PDA itself and must be set in the PDA's camera settings.

== New POD formats ==
New POD formats will be created for the operation.

The POD or POC format produced will be dependant of the Job Group associated to the Job.

All images captured relating to the Job will be displayed on a second page of the POD/POC document, with the associated detail information (Job ID, Container ID, Product Code, Image description). Again image quality is dependant on device settings, which affects the image size.

Fields on the Delivery Note document will be sourced from the following database fields:
* Delivery Note: EPL_DNOTE_NUMBER (New field)
* Customer Address: {{Warning}} From where?
* Delivery Address: Address information from the Job's Customer.
* Customer Tel No: From the Job's Customer.
* Cust No/Contact: From the Job's Customer.
* Our Order No: EPL_JOB_CODE
* Order Date: EPL_ORDER_DATE (New Field)
* Customer Order No: EPL_CUST_REF
* PPB Contact: EPL_SALES_CONTACT (New Field)
* Product Reference: EPL_PRODUCT_CODE
* Product Description: EPL_DESCRIPTION and EPL_DESCRIPTION_LONG
* Due Date: EPL_START_PLANNED_DATE/TIME {{Warning}} Is this the same for all lines?
* Unit: EPL_UNIT_TYPE (New Field)
* Quantity: EPL_PRODUCT_QTY_ORDERED (New Field)
* Quantity Despatched: EPL_PRODUCT_QTY_PLANNED
* Quantity Delivered: EPL_PRODUCT_QTY_ACTUAL
* No Of Parcels: {{Warning}} No longer relevant to either Containerised or product-only deliveries
* Pallet ID: EPL_CONTAINER_ID
* Special Instructions: EPL_JOB_INSTRUCTION
* Total Weight: See below
* Delivered By: PDA User Name
* Print Name: EPL_CUST_SIGNATORY (entered by PDA user)
* Date: Job Completion Date
* Signed Unchecked: EPL_SIGNED_UNCHECKED (New Field)

Weights will be calculated at product level. The weight must be passed through as part of the interfaced product record in the EPL_PRODUCT_WEIGHT. This must be weight per unit and will be calculated excluding tare weight.

{{Warning}}The following elements have been excluded from the design:
* Barcode
* Vat No
* Picked
* Converted

Fields on the Transfer Note document will be sourced from the following database fields (where different from the Delivery Note):
* Stock Transfer Note: EPL_DNOTE_NUMBER (New Field)
* Transfer Stock From: From the Collection's Customer information
* Transfer Stock To: From the Delivery's Customer information
* Xfer Ref No: EPL_JOB_CODE
* Input By: EPL_SALES_CONTACT (New Field)
* Part Number: EPL_PRODUCT_ID
* Product Description: EPL_DESCRIPTION

{{Warning}}The following elements have been excluded from the design:
* Location
* Location Qty

==PDF Production==
A new rule will be added at a Site level to control whether emails to customers will be HTML-Embedded or PDF attachment style.

The system will check this rule when:
# The "Email To" button is pressed on the "View POD" page
# auto-emailed documents are being produced.

If this rule is not enabled, the system will send emails as now (embedded HTML emails).

If this rule is enabled, the system will:
*Export and save the page to a temporary directory, with all images rendered.
*Run the saved page through a conversion routine to convert the HTML to a PDF page (saved in the same directory).
*Attach this generated PDF to the email and send
*Delete the temporary folder.

The conversion routine will use the WkHtmlToPDF program with default parameters - this must be installed on the server.



= Appendix A: POD Formats =
[[File:Delivery Note.jpg|600px|border]]

[[File:Stock Transfer Note.jpg|600px|border]]


{{Doc_Appendix
|Appendix=B
|Estimate=N
|Glossary=EPOD
|Ref1=
|RefV1=
|RefDate1=
|REQ=0
|EST=0
|FS=5.0
|TS=0
|DEV=36
|ST=5.00
|IMP=2.0
|Client={{#var:Client}}
|Year=2012
|FSEST=N
|Rev1=Matt Turner
|Rev1Title=OBS Representative
|Rev2=Stephen McCartney
|Rev2Title=OBS Representative
}}</div>
[[Category:{{#var:Client}} FS]]

FS 294838 Proctor ePOD Modifications

2012-01-24T15:04:20Z

Milesl: /* EPOD_JOB_GROUP */

FS 294838 Proctor ePOD Modifications

2012-01-24T14:19:24Z

Milesl: /* PDA Client */

FS 294838 Proctor ePOD Modifications

2012-01-24T14:16:34Z

Milesl: /* Delivery without Products */