286732: Difference between revisions

From CTMS
(New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Organisation and Resource|Reference=FS 286732 DK-8EMEGM |Version=1.0|Date=|Sysver=10.6|Client=DHL C-TMS}} == Client Requirement == '''Ch...)
 
 
Line 76: Line 76:




[[Image:]]
[[Image:286732_4.png]]





Latest revision as of 12:39, 30 August 2011

Aptean Logo.png







DHL C-TMS

Organisation and Resource


FUNCTIONAL SPECIFICATION - 10.6

- 1.0


Reference: FS 286732 DK-8EMEGM













































Client Requirement

Change Request Summary:


Organisation and Resource.


Change Request Details:

Location contact details (up to 4 contacts)Term Hire Carriers

Benefits identified as a result of the change:

Enable the planners to be able to utilise functionality to enhance the day to day job.


Solution

Location Contact Details:

Functionality exists in C-TMS already. To maintain the ease of use and the ability to retrieve information quickly, it is requested that up to four location contact details can be displayed on the manifest (To be covered in separate reporting RIO) and come through at order and location level and preferably be displayed in order of preference according to the user. These contact details are to appear on paperwork and also on screen.


The contacts will be uploaded into C-TMS, and thus displayed, in the sequence provided in the XML file. Up to ten sets of location contact details may be uploaded as required although only four sets will be visible in the manifest.

A new tab page called ‘Address Refs’ will be added to the ‘Locations’ screen in the ‘LOCATION’ form to display the extra address references available from the new ‘GEO_LOCATION_REFERENCES’ table.

Access to the new tab page will be restricted to user groups as required.

The items currently identified are listed below (subject to confirmation of their sequence):

  1. Assurance Number
  2. Assurance Scheme
  3. Assurance Status

The ‘Comments’ block in the ‘Special’ tab page will also be displayed in the ‘Address Refs’ tab page.

The address references will be displayed with the decoded values so that reference type and value is displayed in a table with two columns. The user will have the ability to add or delete references using the appropriate buttons marked with a ‘+’ or a ‘-‘ sign. Only one reference type may exist at a time as all of the address references are expected to be updated via the XML file. A list of values based on the decoded values will be available for when new references are added.


Each of these items will be mapped to a sub-reference identifier and a decode value setup for name ‘GOLD_LOCS’ and type ‘LOCATION’.

The decode values may be setup in the ‘Decodes’ tab page of the ‘Import Maintenance’ screen in the ‘IMPORTS_MAINT’ form.

Fields are passed from GOLD via ESI interface and received into C-TMS. The references are made available on reporting against the trip and order level. The XML interface is described in RIO 286642 PM-8ELM6Z Integration Orders.


Term Hire Carriers:

Functionality exists in C-TMS already. Carrier Types can be used to determine a Term Hire Carrier v Spot Rate Carrier for example.

Scope

This change will be applied to system version 10.6.0 on INDTST and once approved INDPRD.

Set-up

Pre-requisites

The new ‘Address Refs’ tab page will need to be authorised for use for specific user groups.

Menu Structure

‘Unchanged’

Data

  • The new tab page will need to be created using the scripts in Appendix A.
  • Decoded values will need to be setup for the locations.

Functional Description

Data Setup

Decoded Values

Decoded values will need to be setup for the locations so that the


The decode values may be setup in the ‘Decodes’ tab page of the ‘Import Maintenance’ screen in the ‘IMPORTS_MAINT’ form.


286732 4.png


The ‘Decode Name’ will be ‘GOLD_LOCS’ and the ‘Decode Type’ will be ‘LOCATION’; there will then be records to map the ‘Source Value’ (e.g. ‘1’) to the ‘Target Value’ (e.g. ‘Assurance Number’) and the ‘Customer Id’ will be blank.

The items currently identified are listed below (subject to confirmation of their sequence):

SUB_REF_NAME SUB_REF_VALUE Decoded Value
1 VARCHAR2(200) Assurance Number
2 VARCHAR2(200) Assurance Scheme
3 VARCHAR2(200) Assurance Status


Fields are passed from GOLD via ESI interface and received into C-TMS. The references are made available on reporting against the trip and order level. The XML interface is described in RIO 286642 PM-8ELM6Z Integration Orders.

Location Contact Details

To maintain the ease of use and the ability to retrieve information quickly, it is requested that up to four location contact details can be displayed on the manifest (To be covered in separate reporting RIO) and come through at order and location level and preferably be displayed in order of preference according to the user. These contact details are to appear on paperwork and also on screen.


The contacts will be uploaded into C-TMS, and thus displayed, in the sequence provided in the XML file. Up to ten sets of location contact details may be uploaded as required although only four sets will be visible in the manifest.


286732 3.png


A new tab page called ‘Address Refs’ will be added to the ‘Locations’ screen in the ‘LOCATION’ form to display the extra address references available from the new ‘GEO_LOCATION_REFERENCES’ table.

Access to this tab page will be granted to the appropriate user groups as authorised in the ‘Access Groups’ screen:


286732 2.png

The ‘Comments’ block in the ‘Special’ tab page will also be displayed in the ‘Address Refs’ tab page.


286732 1.png

The address references will be displayed with the decoded values so that reference type and value is displayed in a table with two columns. The user will have the ability to add or delete references using the appropriate buttons marked with a ‘+’ or a ‘-‘ sign. Only one reference type may exist at a time as all of the address references are expected to be updated via the XML file. A list of values based on the decoded values will be available for when new references are added.

The ‘Comments’ section will be displayed at the top of the tab page with the address references displayed beneath with a vertical scrollbar available.

The address references will be stored on the new ‘GEO_LOCATION_REFERENCES’ table as created for RIO ‘286642 PM-8ELM6Z Integration Orders’.

The items currently identified are listed below (subject to confirmation of their sequence):

  1. Assurance Number
  2. Assurance Scheme
  3. Assurance Status
Additional Reference Value
IMP_DECODE_ENTRY.TARGET_VALUE REFERENCE_VALUE


Each of these items will be mapped to a sub-reference identifier and a decode value setup for name ‘GOLD_LOCS’ and type ‘LOCATION’.


The ‘Address Refs’ tab page will obtain the data for the location using column ‘GEO_LOCATION_REFERENCES.LOCATION_ID’, two columns will then be displayed for the data on the table:


Reference Name Reference Value
REFERENCE_NAME REFERENCE_VALUE


For example,


Assurance Number Number 1
Assurance Scheme Scheme 1
Assurance Status Status 1


Table Updates Required

The following script may be run to add the new ‘Address Refs’ tab page:

Update table insert into adm_form_tab (form_name, tab_name, description) values ('LOCATION','ADDRESS_REFS','Address Refs')


References

Ref No
Document Title & ID
Version
Date
1
EST-286732 DK-8EMEGM Organisation and Resource v2.0.doc
2.0
29/03/11


Glossary

Term or Acronym
Meaning
C-TMS Calidus TMS


Document History

Version
Date
Status
Reason
Initials
0.1
01/04/11
Draft
Initial version
PDR
1.0
04/04/11
Issued
Reviewed & Issued
MJC


AUTHORISED BY

Matt Crisford Development Manager
Peter Greer TMSCC MTS Product Manager