280015

From CTMS

280015 - PA-886AW8/ Enhance Order Visibility

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

Allow users (parameter controlled) to have visibility of orders in the order well with a 'Current Location' of their Profile SCHED GROUP location, in addition to the orders they would normally see for that location.


Solution

Currently , when an order is cross docked at an RDC, business users at the cross dock RDC are able to view the order and trip the delivery leg but they are not able to edit the order. This is because editing an order is controlled by the SCHED GROUP the user has access to. Users are only able to edit orders where the GROUP NAME on the order matches the users SCHED GROUP access.

Cross docked orders retain the GROUP NAME of the originating RDC which causes users in cross dock locations access problems.

To resolve this issue we intend to edit the function F_CHECK_ORD_ACCESS which currently controls edit access to orders based on user parameters.

Currently edits are allowed when:

  • GROUP NAME of the order matches one of the users SCHED_GROUP parameter values.

This will be amended, so edits are allowed when :

  • GROUP NAME of the order matches one of the users SCHED_GROUP parameter values.(gn)

OR

  • Current Location of the order matches a users BASED_AT parameter (cl)

OR

  • Any Load location of the order matched a users BASED_AT parameter. (ll)

Example

Order 123 is created for EXELBAWT. (edit access – EXELBAWT gn) The order is cross docked at EXELBELL ( edit accedd – EXELBAWT gn, EXELBEL cl) The order is again cross docked at EXELBANB (edit access – EXELBAWT gn, EXELBEL ll, EXELBANB cl) Order is delivered by EXELBANB (edit access – EXELBAWT gn, EXELBELL ll, EXELBANB ll)

Scope

This change will be applied to system version 10.6.0 on CONTST and once approved CONPRD.


FUNCTIONAL DESCRIPTION

When a user selects an order to edit on the main trip screens , the function F_CHECK_ORD_ACCESS will be called to determine if the user can edit the order.

A number of checks will be carried out and if any of the checks are met the function will return TRUE and allow the user to edit the order.

Check 1

The existing check based on the GROUP NAME of the order and the SCHED GROUPs the user has access to.

Check 2

A new check based on the current location of the order. When an order has been cross docked , so has a status of SCHED_COL, and is waiting in the order well of the cross docked location to be tripped, the CURRENT_LOCATION of the order will be populated with the cross docl location.

Check 2 will allow users to edit an order if the current location matches the users BASED_AT parameter.

Check 3

A new check based on the load locations that an order has visited. If any one of the load locations matches the users BASED AT parameter then the user will be allowed to edit the order.

A user parameter ‘CROSS_DOCKER’ will be available to add to a users profile. If this is set to Y then the third check will be run. If this is set to N, the third check is never run. The parameter will be assigned to a users profile using the ACCESS CONTROL functionality.

A new cursor will be created, if the order fails check 1 and 2, then the new cursor will run. This new cursor will select all the load locations of the order, based on the Haulage activity. Each location will be compared with the BASED_AT parameter of the user. If a match is found, the user will be allowed to edit the order. To allow the where clause to be built dynamically, the cursor and the running of the cursor will be built dynamically using the DBMS_SQL built in Oracle package

ADM.get_user_param will be used to identify the BASED_AT parameter values for each user.

This solution will not require users to have any additional access granted to other SCHED GROUPS. The change will allow users to EDIT orders that they are able to see listed in Haulage activity

280015 1.png


REFERENCES

Ref No
Document Title & ID
Version
Date
1
EST280015 PA - 886AW8 Enhance Order Visibitilty v1.0
1
13/08/10


DOCUMENT HISTORY

Version
Date
Status
Reason
Initials
0.1
13/08/10
Draft
Initial Version
SW


AUTHORISED BY

Matt Crisford Development Manager
Peter Greer TMSCC MTS Product Manager