FS 304709 Partnerlink POD Format
PartnerLink
Partnerlink POD Format
CALIDUS ePOD
27th August 2013 - 0.2
Reference: FS 304709
Contents
Functional Overview
Client Requirement
Produce a POD format that is based closely on the following format. Ensure that the pallets delivered are shown on the report.
Solution Overview
A POD report format will be produced.
This format will be configurable against the Partners.
Scope
- These changes will be made in the latest version of the CALIDUS ePOD system.
- It is noted that this change will be split into two phases.
- Phase 1 will include all except the Consignee address and Collection Date.
- Phase 2 will complete the delivery.
Set-up
Pre-requisites
Menu Structure
None
Data
Functional Description
Database Changes
As a phase 2 development, the following files should be changed:
EPOD_JOB:
- Add EPL_COL_DATE (numeric).
Existing packages will be modified to allow the creating, editing and selecting of the new field, including but not limited to:
- EPOD_JOB_INSERT
- EPOD_JOB_SEARCH
- EPOD_JOB_SELECT
- EPOD_JOB_SELECT_DATE_RANGE
- EPOD_JOB_UPDATE
The existing EPOD_JOB DAL object will be changed to:
- Export the new field in XML requests
- Read the new field
Note: It is not necessary to add this flag as a searchable item. However, if allowing this keeps the packages and DAL objects standard in design, then this can also be done, within the DAL and the packages.
EPOD_JOB_ADDRESS: Existing packages will be modified to allow the creating, editing and selecting of the new field, including but not limited to:
- Add EPL_JOB_TYPE (nvarchar(1)) to the table and to the primary key.
- EPOD_JOB_ADDRESS_INSERT
- EPOD_JOB_ADDRESS_DELETE
- EPOD_JOB_ADDRESS_SELECT
- EPOD_JOB_ADDRESS_UPDATE
The existing EPOD_JOB DAL object will be changed to:
- Allow creation of EPOD_JOB_ADDRESS objects using EPL_JOB_TYPE
- Allow deletion of specific EPOD_JOB_ADDRESS objects, or all for an EPL_JOB_ID.
Partnerlink File Import Changes
The following fields will be populated from the incoming file:
- EPL_TRAILER_ID of EPOD_JOB - column 59 Trailer Number
- EPL_SERVICE of EPOD_JOB - column 38 Service
As a phase 2 development, the following fields will be populated:
- EPL_COL_DATE of EPOD_JOB - column 16 Col Date
- EPOD_JOB_ADDRESS - Collection and Delivery addresses will be populated, regardless of job type, identifying the job type in the new field EPL_JOB_TYPE of EPOD_JOB_ADDRESSES.
Note: All associated EPOD_JOB_ADDRESS functionality must change to identify that this new field EPL_JOB_TYPE is required at all times. This includes but is not limited to the existing Admin Job screen - developers should check the source code for any reference of EPOD_JOB_ADDRESSES and ensure that it is changed to require the Job Type.
POD Report Format
Fields on the POD report:
- Partnerlink Logo - removed if this is a Palletforce job (EPL_JOB_GROUP = "PALLET")
- Customer - EPL_CUSTOMER_CODE
- Consignment Details - EPL_JOB_CODE
- Consignor - the address of the consignor (collection address). For Phase 1, this will be labelled as "By" and will show the Site address (operating partner).
- Company - EPL_CUSTOMER_NAME of EPL_CUSTOMER
- Address - EPL_ADDRESS_LINE_1/2/3/4/5 of EPL_CUSTOMER
- Postcode - EPL_POST_CODE of EPL_CUSTOMER
- Phone - EPL_PHONE_NO of EPL_CUSTOMER
- Deliver To - the delivery address.
- Company - EPL_CUSTOMER_NAME of EPL_CUSTOMER
- Address - EPL_ADDRESS_LINE_1/2/3/4/5 of EPL_JOB_ADDRESS (or EPL_CUSTOMER if this does not exist)
- Postcode - EPL_POST_CODE of EPL_JOB_ADDRESS (or EPL_CUSTOMER if this does not exist)
- Phone - EPL_PHONE_NO of EPL_JOB_ADDRESS (or EPL_CUSTOMER if this does not exist)
- Driver - EPL_DRIVER_NAME of EPOD_DRIVER
- Vehicle - EPL_VEHICLE_REG of EPOD_VEHICLE
- Track Num - EPL_EXT_REF
- Trailer Number - EPL_TRAILER_ID
- Col Date - New field - excluded in phase 1
- Manifest Title - removed
- Manifest Number - EPL_LOAD_ID
- Del Date - EPL_START_PLANNED_DATE
- Service - EPL_SERVICE
- Del Time - EPL_START_PLANNED_TIME
- Conditions - Hard-coded
- Customer Ref - EPL_CUST_REF
- Customer Ref2 - EPL_SO_REF
- Barcode - removed
- Consignment Instructions - EPL_JOB_INSTRUCTION
- Total Packs - Calculated from number of the job's container records (not including loose products)
- Total Weight - subtotalled from EPL_GROSS_WEIGHT of the job's container records (not including loose products)
- Cubic - removed
- Consignee Signature - EPL_SIGNATURE
- Printed Name - EPL_SIGNATORY
- Date - EPL_END_ACTUAL_DATE
- Arrival Time - EPL_ARRIVAL_TIME
- Departure Time - EPL_END_ACTUAL_TIME
Note: All fields are from EPOD_JOB unless otherwise specified.
The customer also required that the status of the pallets delivered should be shown on the note. Due to this, and the slight changes to the content of the note shown above, the note has been redesigned as a A4 document, where the existing format (slightly modified for space) is the header of the document, followed by a list of pallets, their status and and descriptive text associated to them, as in the prototype shown.
- Item - EPL_CONTAINER_ID
- Status - EPL_STATUS (translated)
- Notes - EPL_USER_NOTES (if claused) else EPL_REASON_CODE and EPL_DESCRIPTION of EPOD_REASON_CODE
Note: All fields are from EPOD_CONTAINER unless otherwise specified.
Developer Notes:
- As there is a possibility that the number of containers will exceed that allowable on a page, the format should be written as a paginated document. The style of this should be copied from previous examples (e.g. ALS.aspx.cs).
- 30 lines should be allowed per page.
- The Container list should be recognised as the Detail portion of the document, the rest seen as the header.
- The header should be shown on each page, ensuring that the signature is shown at all times.
Note: Sample code exists for the new format, so please chech with the designer for details. Sample code of how multi-page reports work (for example the standard Container-based POD report) - please use this for code reference.
Appendix A: Document References
A.1 References
| Ref No | Document Title & ID | Version | Date |
| 1 |
A.2 Glossary
| Term | Definition |
|---|---|
| EPOD | Electronic Proof of Delivery. The OBS EPOD system is CALIDUS ePOD. |
| CALIDUS eSERV | The OBS mobile system to complete Service functionality in the field. This is part of the CALIDUS ePOD system. |
| PDA | The mobile device on which the C-ePOD system will run in the field. This can be a Phone, EDA or industrial PDA, running Android. |
| DAL | Data Access Layer. A mechanism for accessing data by the system that is removed from the application, allowing for simplified access and providing protection to the data, as only approved DAL methods can be used to modify it. |
| GPS | Global Positioning System. A mechanism of retrieving accurate positioning information in the form of Latitude and Longitude (Lat-Long) co-ordinates from a device. |
| GPRS, 3G, HSDPA, Data Service | All terms referring to mobile device network connectivity, and the speed at which the device connects to the internet. |
A.3 Authorised By
Andrew Allison | Client Representative | _____________________________ |
