276280
276280 - AS-84PEAN/ Dunelm Rating and Invoicing
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
Rating & Invoicing to support supplier billing.Suzanne York/Milton Keynes/UK/Exel Tariff and rate calculation to work for multiple delivery transit units within a consignment. Charging to be made at Consignment DU level and suppliers to be billed weeklyConsolidate charges and format invoice. Oracle integration enhancements. Priority development item to meet Dunelm contingency request. Required to support supplier billing for carriage charges.
Solution
The current contracting module allows the business to charge customers/ suppliers by the number of DU’s. This will be amended to allow users to charge based on individual DU types – eg PALLET, CARTON, ROLL, BAG.
An order (consignment) may include several different du type, this will require multiple calls to the contracts module to find the relevant tariff. After each contract call, the individual charge will be stored and totalled at the end to create an overall charge for the order (consignment).
Additional charges based on Ireland and Aberdeen will be handled by specific Tariffs for the du types at these locations. For example, three tariffs for Pallets will be created, Pallets, Pallets Ireland and Pallets Aberdeen. Each tariff will be assigned the relevant journeys . The journey of the order (consignment) will determine which tariff is selected.
A minimum charge per consignment will be held as a system parameter. If the total charges for an order (consignment) is less than the minimum charge, a payment record for the minimum charge will be created and stored against the order, rather than a payment record for the amount generated from contracts.
A system parameter will control the minimum collection amount. When a trip is set to Accepted, a query will run which totals the consignment charges per customer. If this total is less than the minimum collection charge, a new payment record will be created based on the Schedule/ Trip / customer with a payment type of MIN_COLLECT. The amount of this payment will be the difference between the total charges for the consignments at the stop and the Minimum collection charge.
Eg
Minimum Collection Charge = 30.00
Stop 1 there are 3 consignments for supplier LOV01 1 – 8.00
2 – 7.50
3 – 9:00
TOTAL= 25.50
A MIN_COLLECT payment will be generated when the trip is set to accepted , for 4.50, this will be held with an event ref based on the schedule, trip and supplier LOV01. At each stop, the sum of consignments will be compared with the Minium collection charge, and trips may have several MIN_COLLECT payments generated for different customers/ suppliers.
MIN_COLLECT payments will only be generated for the collection trip, where the load location of the stop matches the from location of the consignment.
A new button will be displayed on the Finance tab call Collection Charges , when this is selected the user will be able to see any payments of Type MIN_COLLECT , created for the trip. A new field will also be displayed on the Finance tab. The field called Total Collection Charges will display the sum of MIN_COLLECT charges for the trip.
The sum of consignments per stop (collections) and any MIN_COLLECT charges will be re validated at the following events
Unschedule an order from a trip Unschedule an order from a stop Add an order to the trip Add an order to the stop.
If a trip is deleted any MIN_COLLECT payments generated for the trip will also be deleted.
The charges generated will be used as the basis for invoicing the suppliers, using Oracle reports or an extract to interface with Oracle Financials.
Scope
This change will be applied to system version 10.6.0 on DUNTST and once approved DUNPRD.
FUNCTIONAL DESCRIPTION
Contracts are currently created with a tier type of DU, when costing an order the total DU of the order is calculated and passed to the contract to calculate the order revenue.
For Dunelm orders, each order line will be costed. The system will identify a DUNELM order which will be costed by order line by looking at the value if ORDER_LINE_CONTRACT on the customer table. If this has been ticked for the customer, any orders created for the customer will be costed using the order lines and not the order totals.
The du types will be used to determine the cost , contracts will be created with tariffs based on specific Du types eg PALLET, CTN etc. The DU TYPES have also been added to the Contracts import.
As each order line is costed, the value is stored in a temp field and after all order lines have been processed, the totals for each du type will be totalled to create the order revenue.
A minimum consignment charge has been added to the Invoice requirements table, if the total revenue for the order is less than the min_consignment_charge (for the specified cost centre and customer), the payment record will be created with the total set to the minimum consignment charge.
Once the orders have been created, they assigned to trips. Serveral orders loaded at the same stop are known as a collection. There is a system parameter created called MIN_COLLECTION_CHARGE and this is set to a numeric value. If the sum of revenue from stop is less than the MIN_COLLECTION_CHARGE, an extra payment record will be created for the amount of the difference.
If there are two orders loaded at a stop, each with a revenue of 12.00 and 15.00 and the MIN_COLLCTION_CHARGE is set to 29.00, an additional payment record will be created for a value of 2.00. The payment record will have the schedule name, trip id and customer is in the event reference and will be available to view from the Trip screen in the Finance tab. The payment record will have a payment type of MIN_COLLECT.
Selecting the Coll Uplift button will display the additional MIN_COLLECT payment created. This button is only visible in systems where the MINIMUM_COLLECTION parameter has been set to Y.
REFERENCES
| EST-276280 AS-84PEAN Dunelm Rating and Invoicing |
DOCUMENT HISTORY
| Initial version | ||||
| Submitted into RIO |
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
