261543 - Revision history

Middletong: /* Document History */

2009-09-10T15:25:58Z

Document History

← Older revision		Revision as of 17:25, 10 September 2009
Line 159:		Line 159:

	\|}		\|}
	~~'''~~Authorised ~~By'''~~

			= Authorised by =

Middletong: /* References */

2009-09-10T15:20:03Z

References

← Older revision		Revision as of 17:20, 10 September 2009
Line 120:		Line 120:
	== References ==		== References ==

	{\| ~~class~~="~~prettytable~~"		{\| Border="1"
	\| <center>'''Ref No'''</center>		\| <center>'''Ref No'''</center>
	\| <center>'''Document Title & ID'''</center>		\| <center>'''Document Title & ID'''</center>

Middletong: /* Data */

2009-09-10T15:19:13Z

Data

← Older revision		Revision as of 17:19, 10 September 2009
Line 91:		Line 91:


	{\| ~~class~~="~~prettytable~~"		{\| Border="1"
	\| '''PARAM_NAME'''		\| '''PARAM_NAME'''
	\| '''VALUE'''		\| '''VALUE'''
Line 111:		Line 111:
	\|}		\|}
	SQL script required to set up new parameter:		SQL script required to set up new parameter:


	= Functional Description =		= Functional Description =

Middletong: /* Solution */

2009-09-10T15:18:51Z

Solution

← Older revision		Revision as of 17:18, 10 September 2009
Line 39:		Line 39:
	Trip MAN-000123456 has:		Trip MAN-000123456 has:

	{\| ~~class~~="~~prettytable~~"		{\| Border="1"
	\| '''Order'''		\| '''Order'''
	\| '''RPE'''		\| '''RPE'''

Middletong at 15:18, 10 September 2009

2009-09-10T15:18:05Z

← Older revision		Revision as of 17:18, 10 September 2009
Line 8:		Line 8:

	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		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 ==		== Client Requirement ==
Line 79:		Line 82:
	The Total Weight that will be written to the EFX file will be 44318. No decimal places will be shown as they are not included in the current EFX file.		The Total Weight that will be written to the EFX file will be 44318. No decimal places will be shown as they are not included in the current EFX file.

	= Set-up =		== Set-up ==
	== Pre-requisites ==		== Pre-requisites ==
	Carrier of EFX set up in system.		Carrier of EFX set up in system.
Line 132:		Line 135:
	\|}		\|}

	== Document History ==		= Document History =


	{\| ~~class~~="~~prettytable~~"		{\| Border="1"
	\| <center>'''Version'''</center>		\| <center>'''Version'''</center>
	\| <center>'''Date'''</center>		\| <center>'''Date'''</center>
Line 161:		Line 164:


	{\| ~~class~~="~~prettytable~~"		{\| Border="1"
	\| '''''Matt Crisford'''''		\| '''''Matt Crisford'''''
	\| Development Manager		\| Development Manager

Crisfordm: /* EFX Export Layout */

2009-07-02T10:37:16Z

EFX Export Layout

← Older revision		Revision as of 12:37, 2 July 2009
Line 114:		Line 114:
	The EFX Export file will not change in format and will remain the same as in the sample below:		The EFX Export file will not change in format and will remain the same as in the sample below:

	~~(Note data has been moved onto more than 1 line for visual purposes)~~		The calculation used to obtain the trips total weight will change if the entered weight is 0 or no weight is entered by users.

	~~<center>[[Image:261543_1.png]]</center>~~

	The calculation used to obtain the trips total weight will change ~~and~~ is ~~detailed in section 3.2 Code Amendments~~.

	== References ==		== References ==

2009-07-02T10:35:02Z

New page

==261543 PA-7N5KQW Add weight to EFX Export==

{| class="prettytable"
| <div align="right">'''Version :'''</div>
| <center>'''1.0'''</center>
|}
'''Copyright OBS Logistics © 2009'''

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

== Client Requirement ==
Add a default Weight value to the EFX export data if no Weight is attached to the Order in MTS. To ensure that this is not understated I suggest that the default should be 1000kgs multiplied by the Pallet quantity. Alternative is to add a free-text box to the EFX pop-up window which will allow the user to add in a weight at the time of setting the deadline and Rate - Invoke an error window if no weight is added - Value always in KG's

EFX requires an entry in the weight field to process the posting.

== Solution ==
After investigation, the total weight in the EFX export data is currently calculated by summing the weight (SCH_ORDER_LINE.WEIGHT) of all orders on the Trip in the EFX file, at the time the file is created. This may result in nothing being reported in the weight field position of the EFX file, if all orders on the trip do not have a weight entered.

Investigations show that capturing the weight within the EFX Pop-Up, by the user, is not feasible as there is no data element to hold the weight a user entered until the export is created.

Therefore, the total weight that appears in the EFX export data will be calculated at the time the file is created – in the following way:

* All orders loaded on the Trip that appears in the EFX file will be selected
* The weight (SCH_ORDER_LINE.WEIGHT) and RPE (SCH_ORDER_LINE.RPE_QTY) of each order will be checked.
* If the order line has a weight entered then this will be added to a global variable holding the total weight of the trip, to be displayed in the exported data
* If the order line has a weight that is 0.00 or NULL, then a default weight for that particular order will be calculated. This will be calculated by taking the RPE for that order and multiplying it by 1000kgs (To be held in a new system parameter EFX_ DEF_WEIGHT). Therefore if the order is for 3 RPE, then the default weight for that order will be 3000kgs. This weight will then be added to the global variable holding the total weight of the trip
* Once all orders on the trip have been queried, then the global variable holding the total weight of the trip will be output to the EFX file

This calculation will ensure an entry is displayed in the weight field position in the EFX file.

This will require an update to procedure PROCESS_EFX_TRIP_DTL within package INT_MSG.

Below is an example of a Trip with 5 orders loaded on it. 1 of which does not have the weight field entered and 1 that has a weight of 0.00. A breakdown of how the total weight of the trip will be calculated is shown:

Trip MAN-000123456 has:

{| class="prettytable"
| '''Order'''
| '''RPE'''
| '''Weight'''
| '''Calculation'''
| '''Weight for adding to Total Weight of Trip variable'''
|-
| <div align="right">1</div>
| <div align="right">20</div>
| <div align="right">20000.00</div>
| N/A
| <div align="right">20000.00</div>
|-
| <div align="right">2</div>
| <div align="right">3</div>
| <div align="right"> 0.00</div>
| 3 X 1000.00
| <div align="right">3000.00</div>
|-
| <div align="right">3</div>
| <div align="right">1</div>
| <div align="right">318.00</div>
| N/A
| <div align="right">318.00</div>
|-
| <div align="right">4</div>
| <div align="right">12</div>
| <div align="right">12000.00</div>
| N/A
| <div align="right">12000.00</div>
|-
| <div align="right">5</div>
| <div align="right">9</div>
|  
| 9 X 1000.00
| <div align="right">9000.00</div>
|-
| colspan="4" |  
| '''Total Weight of trip to be displayed in EFX file = 44318.00'''
|}

The Total Weight that will be written to the EFX file will be 44318. No decimal places will be shown as they are not included in the current EFX file.

= Set-up =
== Pre-requisites ==
Carrier of EFX set up in system.

== Data ==
All orders in the EFX export, that do not have a weight, will have one automatically calculated at the time of the EFX file creation. This will be calculated by multiplying the RPE for that order by a kg value held in parameter EFX_DEF_WEIGHT. This will originally get set to 1000 but will be editable via the System Parameters form. Table ADM_SYSTEM_PARAM will be updated to include the following parameter:

{| class="prettytable"
| '''PARAM_NAME'''
| '''VALUE'''
| '''DATA_TYPE'''
| '''MAX_LENGTH'''
| '''DISPLAYED'''
| '''USER_MODIFIABLE'''
| '''DESCRIPTION'''

|-
| EFX_DEF_WEIGHT
| 1000
| S
| <div align="right">256</div>
| Y
| Y
| Default EFX weight per RPE, used in calculation of trip weight for EFX export

|}
SQL script required to set up new parameter:

= Functional Description =
== EFX Export Layout ==
The EFX Export file will not change in format and will remain the same as in the sample below:

(Note data has been moved onto more than 1 line for visual purposes)

<center>[[Image:261543_1.png]]</center>

The calculation used to obtain the trips total weight will change and is detailed in section 3.2 Code Amendments.

== References ==

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

|-
|
| EST-261543 PA-7N5KQW Add weight to EFX Export v1.doc
| <center>1</center>
| <center>26/02/09</center>

|}

== Document History ==

{| class="prettytable"
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>0.1</center>
| <center>18/03/09</center>
| <center>Draft</center>
| Initial version
| <center>LAD</center>

|-
| <center>1.0</center>
| <center>19/03/09</center>
| <center>Issue</center>
| Reviewed and Issued
| <center>MJC</center>

|}
'''Authorised By'''

{| class="prettytable"
| '''''Matt Crisford'''''
| Development Manager
|

|-
| '''''Suk Sandhu'''''
| TMSCC MTS Product Manager
|

|}