262096
262096 - PA-7PCSJV / Develop Cross Dock Functionality
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
When an Order is 'Applied by Cross-Dock' a second exact copy of the order is created - the only change being the status change to SCHED-COLL. If this second order could incorporate 3 changes to the detail, including a Suffix to the OMS reference, it would become a viable auto-rateable order within the Cross-dock location. Fields to Transpose - Original Customer to become the Group name of the originating depot on the new order. The Group name of the new order to become the Group name of the Cross-dock location, and the From location to become the Cross Dock location also. This would replace the manual process being used currently. The original revenue would remain with the original order, and the revenue on the second order would become the Order/Trip Cost for the original order. RIO to evaluate this process or alternative
Solution
The OBS Solution will amend the existing Internal Charging process for calculating Trunk and Radial costs from being between COST CENTRES to between GROUP NAMES.
The procedure RATE.CALC_ORDER_COSTS is used to determine the following:
- Are order costs applicable?
- Which type of orders costs are applicable (Trunk or Radial)?
- Who are the local and counter party values to be passed to the CONTRACT package?
Based on a comparison of the To and From Locations on the order with the Load Stop, Unload stop and Hub location the local and counter parties are set to cost centres based on to, from or hub location.
To replace cost centres with GROUP NAMES, we must be able to link the TO, FROM, HUB locations with a GROUP NAME (where applicable)
A new tab will be available In the STATIC DATA screen for assigning GROUP NAMES to Locations. A new field GROUP NAME will also be available to view on the LOCATIONS screen. Only LOCATIONS which are relevant for internal charging should be assigned a GROUP NAME. A new table will created to store this information and will be directly linked to the GEO_LOCATION table. Many locations can be assigned to a GROUP NAME.
Assigning a LOCATION to a GROUP NAME via the new tab screen will be equivalent to setting the INTERNAL_REVENUE flag for COST CENTRES.
When calculating ORDER COSTS, the GROUP NAME on the order will not be referenced, only the GROUP NAMES associated with the relevant LOCATIONS.
Cost and revenue will still be held at the order level. Revenue will be created against a COST CENTRE and CUSTOMER and charges will be created between GROUP NAMES.
Scope
This change will be applied to system version 10.6.0 on CONTST and once approved CONPRD.
Data
A new table will be created to store the location and Group name link. The table will be made up of two columns , LOCATION_ID and GROUP_NAME. LOCATION_ID will be the primary key to ensure that each location may only be assigned to one GROUP_NAME.
create table GEO_LOC_GROUP_NAME
(LOCATION_ID varchar2(12) not null,
GROUP_NAME varchar2(12) not null,
Primary Key (location_id),
Foreign Key (LOCATION_ID) references GEO_LOCATION(LOCATION_ID),
Foreign Key (GROUP_NAME) references OMS_SCHED_GROUP(GROUP_NAME);
CREATE PUBLIC SYNONYM GEO_LOC_GROUP_NAME FOR GEO_LOC_GROUP_NAME;
GRANT INSERT, DELETE, DEBUG, FLASHBACK, ON COMMIT REFRESH, QUERY REWRITE, SELECT, UPDATE ON GEO_LOC_GROUP_NAME TO MTS_USER;
GRANT SELECT ON GEO_LOC_GROUP_NAME TO MTS_USER_READ_ONLY;
All existing contracts between Cost Centres for internal charges will be redundant. The copy contract function can be used to change the local and counter parties and retain the tariffs which have been created.
FUNCTIONAL DESCRIPTION
A new table will be created to store GROUP_NAME at location level. This table will be populated via a new tab on the STATIC DATA screen. A location may only be assigned to one GROUP NAME but each GROUP NAME may be assigned many locations.
Look up values will be available for each field based on existing data. To select a group name, the group must have been added to the GROUP_NAME maintenance screen
The Location id must exist as a valid Location. Only locations which are relevant to internal charging should be assigned a GROUP NAME.
On the locations screen, the GROUP NAME field will be available as display only.
Once the group name has been associated with the relevant locations, we must amend the CONTRACT code to use the GROUP NAME instead of the COST CENTRE when calculating internal Charges.
The RATE package determines the parameters which are passed to the CONTRACT package to check for a relevant contract. RATE.CALC_ORDER_COSTS is the specific procedure used to gather the parameters for internal order charging.
Based on a comparison of the to and from locations on the order with the Load and Unload locations on the TRIPS, the procedure determines which type of Contract is relevant and sets the local and counter party parameters based on the contract type.
The code will be amended to set the local and counter party parameters to equal the GROUP NAME for the relevant locations. The GROUP NAME will be extracted as part of the select statement for the C_TRIP_ORDERS cursor.
No other procedures will be changed; all other revenue and charges will be calculated using the existing code.
REFERENCES
| 262096 PA-7PCSJV Develop Cross Dock Functionality v1.0.doc |
DOCUMENT HISTORY
| Initial version | ||||
| Reviewed and Issued |
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
