265413 - Revision history

Middletong at 13:57, 19 April 2010

2010-04-19T13:57:15Z

← Older revision		Revision as of 15:57, 19 April 2010
Line 244:		Line 244:

	\|}		\|}

	~~Back to [[CONPRD Release - 24/02/2010]]~~

Middletong at 11:21, 29 March 2010

2010-03-29T11:21:03Z

← Older revision		Revision as of 13:21, 29 March 2010
Line 191:		Line 191:
	\|-		\|-
	\| <center>1</center>		\| <center>1</center>
	\| EST-~~259410 PA~~-~~7MKDYG CN Loading Schedule Report Changes~~ v1.doc		\| EST-265413 NW-7S7FHR Add Slot Flag & DB Job v1.0.doc
	\| <center>1</center>		\| <center>1.0</center>
	\| <center>06/01/09</center>		\| <center>04/06/09</center>

			\|-
			\| <center>2</center>
			\| EST-265413 NW-7S7FHR Add Slot Flag & DB Job v2.0.doc
			\| <center>2.0</center>
			\| <center>09/06/09</center>

	\|}		\|}

Line 207:		Line 214:

	\|-		\|-
	\| <center>1a</center>		\| <center>0.1</center>
	\| <center>12/01/09</center>		\| <center>06/07/09</center>
	\| <center>Draft</center>		\| <center>Draft</center>
	\| Initial version		\| Initial version
	\| <center>~~PDR~~</center>		\| <center>LAD</center>

	\|-		\|-
	\| <center>1</center>		\| <center>1.0</center>
	\| <center>12/01/09</center>		\| <center>12/01/09</center>
	\| <center>Issue</center>		\| <center>Issue</center>
	\| Reviewed and Issued		\| Reviewed and Issued
	\| <center>~~MJC~~</center>		\| <center>DJM</center>
	\|}		\|}

Line 232:		Line 239:

	\|-		\|-
	\| '''''~~Peter Greer~~'''''		\| '''''Suk Sandhu'''''
	\| TMSCC MTS Product Manager		\| TMSCC MTS Product Manager
	\|		\|

Middletong at 11:15, 29 March 2010

2010-03-29T11:15:06Z

@@ Line 51: / Line 51: @@
 '''N.B. it has been requested to not include the database job or functionality around setting additional slots to inactive.'''
 '''Ensuring new functionality remains Generic'''
@@ Line 59: / Line 60: @@
 ==Scope==
 ==Data==
 =FUNCTIONAL DESCRIPTION=
 =REFERENCES=

Middletong: /* Solution */

2010-03-29T11:05:56Z

Solution

← Older revision		Revision as of 13:05, 29 March 2010
Line 21:		Line 21:

	==Solution==		==Solution==
	#'''LOCATIONS Form Updates'''		'''LOCATIONS Form Updates'''

	2 new check boxes will be added to tab ‘Slots’ on the LOCATIONS form as this is where they are maintained. They will be displayed to the right of field ‘Carrier’ currently on this tab. Other items on the tab will need to be moved to make room for the 2 new check boxes. First checkbox will have header ‘Add.’ (for Additional as no room for entire word) and second checkbox will have header ‘Core’.		2 new check boxes will be added to tab ‘Slots’ on the LOCATIONS form as this is where they are maintained. They will be displayed to the right of field ‘Carrier’ currently on this tab. Other items on the tab will need to be moved to make room for the 2 new check boxes. First checkbox will have header ‘Add.’ (for Additional as no room for entire word) and second checkbox will have header ‘Core’.
Line 30:		Line 30:

	These checkboxes will reference 1 new field that will be created on table GEO_SLOT called ADD_CORE. If a ‘Save’ is actioned in the ‘Slots’ tab and ‘Add.’ is checked at the time of save then GEO_SLOT.ADD_CORE will be set to ADDITIONAL for the corresponding Slot record. If ‘Core’ is checked at the time a ‘Save’ is actioned in the ‘Slots’ tab then GEO_SLOT.ADD_CORE will be set to CORE for the corresponding Slot record.		These checkboxes will reference 1 new field that will be created on table GEO_SLOT called ADD_CORE. If a ‘Save’ is actioned in the ‘Slots’ tab and ‘Add.’ is checked at the time of save then GEO_SLOT.ADD_CORE will be set to ADDITIONAL for the corresponding Slot record. If ‘Core’ is checked at the time a ‘Save’ is actioned in the ‘Slots’ tab then GEO_SLOT.ADD_CORE will be set to CORE for the corresponding Slot record.
	#'''SLOT_USAGE Form Updates'''
			'''SLOT_USAGE Form Updates'''

	The Slot Usage Form will be updated to display the data held in the new field GEO_SLOT.ADD_CORE. This will be displayed under ‘Unused Slots’ next to the ‘Slot Status’ field as 2 check boxes similar to those that will be displayed in the LOCATIONS form, whereby only 1 box can be checked at any time. Currently it looks like these fields under ‘Unused Slots’ can be edited/updated, so the checkboxes will also be editable.		The Slot Usage Form will be updated to display the data held in the new field GEO_SLOT.ADD_CORE. This will be displayed under ‘Unused Slots’ next to the ‘Slot Status’ field as 2 check boxes similar to those that will be displayed in the LOCATIONS form, whereby only 1 box can be checked at any time. Currently it looks like these fields under ‘Unused Slots’ can be edited/updated, so the checkboxes will also be editable.

	When this functionality is released to MSPF and then MSLV, as there are already slots set up, all current slots will have field ADD_CORE set to ‘CORE’ initially by an update script on table GEO_SLOT.		When this functionality is released to MSPF and then MSLV, as there are already slots set up, all current slots will have field ADD_CORE set to ‘CORE’ initially by an update script on table GEO_SLOT.
	#'''Slot Import Functionality Update'''
			'''Slot Import Functionality Update'''

	In the IMPORT_MAINT screen (MSPF), Import type of SLOT currently details 24 fields. This config will be updated to import new field ADD_CORE in position 25. This will require users to append this new field to the end of the current Slot file format they use for importing.		In the IMPORT_MAINT screen (MSPF), Import type of SLOT currently details 24 fields. This config will be updated to import new field ADD_CORE in position 25. This will require users to append this new field to the end of the current Slot file format they use for importing.
Line 42:		Line 44:

	During the processing of lines in the Slot Import, field values are temporarily held in a Record of Type Slot_Type in Package SLOT.sql. Therefore, to temporarily hold the new field value of ADD_CORE, this record type of Slot_Type will have to be updated in this package.		During the processing of lines in the Slot Import, field values are temporarily held in a Record of Type Slot_Type in Package SLOT.sql. Therefore, to temporarily hold the new field value of ADD_CORE, this record type of Slot_Type will have to be updated in this package.
	#'''Ability to set Additional Slots to Inactive'''
			'''Ability to set Additional Slots to Inactive'''

	A new procedure called Inactivate_Additional_Slots in package SLOT.sql will be created. The purpose of this new procedure will be to select ALL records from table GEO_SLOT that have new field ADD_CORE set to ADDITIONAL and have a SLOT_STATUS of ACTIVE. All retrieved records will be updated to have a SLOT_STATUS of INACTIVE. This procedure will be run daily via a database job at 23:00.		A new procedure called Inactivate_Additional_Slots in package SLOT.sql will be created. The purpose of this new procedure will be to select ALL records from table GEO_SLOT that have new field ADD_CORE set to ADDITIONAL and have a SLOT_STATUS of ACTIVE. All retrieved records will be updated to have a SLOT_STATUS of INACTIVE. This procedure will be run daily via a database job at 23:00.
Line 48:		Line 51:

	'''N.B. it has been requested to not include the database job or functionality around setting additional slots to inactive.'''		'''N.B. it has been requested to not include the database job or functionality around setting additional slots to inactive.'''
	#'''Ensuring new functionality remains Generic'''
			'''Ensuring new functionality remains Generic'''

	This functionality has been requested by M&S, therefore we will have to make it generic so that it does not affect other clients using Slots. To do this the checkboxes on the ‘Slots’ tab of LOCATIONS and on the ‘New Slot’ pop-up will be system parameter based. If new parameter SLOT_INC_ADD_CORE_TYPES is set to ‘Y’ then the checkboxes will be shown, but if this parameter is set to ‘N’ or does not exist in a database then the checkboxes will not be shown, although there will be a space where they should appear on the ‘Slots’ tab.		This functionality has been requested by M&S, therefore we will have to make it generic so that it does not affect other clients using Slots. To do this the checkboxes on the ‘Slots’ tab of LOCATIONS and on the ‘New Slot’ pop-up will be system parameter based. If new parameter SLOT_INC_ADD_CORE_TYPES is set to ‘Y’ then the checkboxes will be shown, but if this parameter is set to ‘N’ or does not exist in a database then the checkboxes will not be shown, although there will be a space where they should appear on the ‘Slots’ tab.

Middletong: New page: =265413 - NW-7S7FHR / Add Slot Flag= Copyright OBS Logistics © 2010 The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omi...

2010-03-29T11:05:15Z

New page

=265413 - NW-7S7FHR / Add Slot Flag=

Copyright OBS Logistics © 2010

The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied

=FUNCTIONAL OVERVIEW=

==Client Requirement==
Add an additional flag to Slots and create a new DB job

Slots need to be recognised as either being Core or Additional for M&S, therefore two checkboxes should be added to the Slots form denoting either Core or Additional. Only one of these should be able to be checked at any one time and one should always be populated i.e. the Slot must be either Core or Additional. As part of this RIO this flag should also be added to the Slot Import format.

A new database job is also required to run overnight to set all Additional Slots that are Active to Inactive. The time that this job is run should be able to be changed via a P5 EARS call if required.

Project requirement for MTS as part of the re-deployment to M&S.

'''N.B. it has been requested to not include the database job or functionality around setting additional slots to inactive.'''

==Solution==
#'''LOCATIONS Form Updates'''

2 new check boxes will be added to tab ‘Slots’ on the LOCATIONS form as this is where they are maintained. They will be displayed to the right of field ‘Carrier’ currently on this tab. Other items on the tab will need to be moved to make room for the 2 new check boxes. First checkbox will have header ‘Add.’ (for Additional as no room for entire word) and second checkbox will have header ‘Core’.

When ‘New’ button is clicked for Slots, a pop-up is displayed for the user to create a new slot. This pop-up will also have 2 checkboxes to denote whether the slot is ‘Core’ or ‘Additional’. The default value will be ‘Core’ therefore when the ‘New’ button is clicked ‘Core’ will initially be set as checked.

These check boxes will be coded in such a way that only 1 of them can be checked at any time for a single slot. E.g. a trigger will be attached to both check boxes that will uncheck ‘Add.’ if ‘Core’ is checked and vice versa.

These checkboxes will reference 1 new field that will be created on table GEO_SLOT called ADD_CORE. If a ‘Save’ is actioned in the ‘Slots’ tab and ‘Add.’ is checked at the time of save then GEO_SLOT.ADD_CORE will be set to ADDITIONAL for the corresponding Slot record. If ‘Core’ is checked at the time a ‘Save’ is actioned in the ‘Slots’ tab then GEO_SLOT.ADD_CORE will be set to CORE for the corresponding Slot record.
#'''SLOT_USAGE Form Updates'''

The Slot Usage Form will be updated to display the data held in the new field GEO_SLOT.ADD_CORE. This will be displayed under ‘Unused Slots’ next to the ‘Slot Status’ field as 2 check boxes similar to those that will be displayed in the LOCATIONS form, whereby only 1 box can be checked at any time. Currently it looks like these fields under ‘Unused Slots’ can be edited/updated, so the checkboxes will also be editable.

When this functionality is released to MSPF and then MSLV, as there are already slots set up, all current slots will have field ADD_CORE set to ‘CORE’ initially by an update script on table GEO_SLOT.
#'''Slot Import Functionality Update'''

In the IMPORT_MAINT screen (MSPF), Import type of SLOT currently details 24 fields. This config will be updated to import new field ADD_CORE in position 25. This will require users to append this new field to the end of the current Slot file format they use for importing.

Package IMP.sql will have function Process_Slot updated to pick up this new field during Slot Importing. A check will be done on this field to ensure it is either set to ADDITIONAL or CORE. These are the only 2 acceptable values. Users involved in importing Slots will have to be informed that new field ADD_CORE will be added into the Slot Import and can only be set to ADDITIONAL or CORE. If this field is left blank during the Import or is not a recognisable value, the default value will be CORE.

During the processing of lines in the Slot Import, field values are temporarily held in a Record of Type Slot_Type in Package SLOT.sql. Therefore, to temporarily hold the new field value of ADD_CORE, this record type of Slot_Type will have to be updated in this package.
#'''Ability to set Additional Slots to Inactive'''

A new procedure called Inactivate_Additional_Slots in package SLOT.sql will be created. The purpose of this new procedure will be to select ALL records from table GEO_SLOT that have new field ADD_CORE set to ADDITIONAL and have a SLOT_STATUS of ACTIVE. All retrieved records will be updated to have a SLOT_STATUS of INACTIVE. This procedure will be run daily via a database job at 23:00.
Note: It is currently assumed that this db job will run at 23:00 and may change during Development for testing purposes, however after release to the PRD system, any changes to the time the db jobs runs at will require a chargeable EARS call to be raised.

'''N.B. it has been requested to not include the database job or functionality around setting additional slots to inactive.'''
#'''Ensuring new functionality remains Generic'''

This functionality has been requested by M&S, therefore we will have to make it generic so that it does not affect other clients using Slots. To do this the checkboxes on the ‘Slots’ tab of LOCATIONS and on the ‘New Slot’ pop-up will be system parameter based. If new parameter SLOT_INC_ADD_CORE_TYPES is set to ‘Y’ then the checkboxes will be shown, but if this parameter is set to ‘N’ or does not exist in a database then the checkboxes will not be shown, although there will be a space where they should appear on the ‘Slots’ tab.

Amendments to packages SLOT.sql and IMP.sql to pick up the new field ADD_CORE in the Imported file should not have any affect on the other clients if released, as they will not have their IMPORT_MAINT form configured to pick up this new field in import type SLOT.

==Scope==

==Data==

=FUNCTIONAL DESCRIPTION=

=REFERENCES=

{| Border="1"
| <center>'''Ref No'''</center>
| <center>'''Document Title & ID'''</center>
| <center>'''Version'''</center>
| <center>'''Date'''</center>

|-
| <center>1</center>
| EST-259410 PA-7MKDYG CN Loading Schedule Report Changes v1.doc
| <center>1</center>
| <center>06/01/09</center>
|}

=DOCUMENT HISTORY=

{| Border="1"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>1a</center>
| <center>12/01/09</center>
| <center>Draft</center>
| Initial version
| <center>PDR</center>

|-
| <center>1</center>
| <center>12/01/09</center>
| <center>Issue</center>
| Reviewed and Issued
| <center>MJC</center>
|}

=AUTHORISED BY=

{| Border="1"
| '''''Matt Crisford'''''
| Development Manager
|

|-
| '''''Peter Greer'''''
| TMSCC MTS Product Manager
|

|}

Back to [[CONPRD Release - 24/02/2010]]