286985

DHL MTS

Dunelm Supplier Revenue

- 10.6

- 1.1

Reference: FS 286985 OB-8EYKW2

Dunelm Supplier Revenue (New) Extract The business require a change to the existing extract. Currently the report is based on the In-store Date (ORDER_SCHED), of each consignment within a given date range (parameter). The report needs to be based on consignments that are being collected within a given date range (parameter), regardless of the in-store date. The report should then be more inline with invoicing. Dunelm Supplier DU Extract The business requires a change to the existing extract. As with the Revenue extract, this report needs to be changed to report on planned consignment quantity collected on trips within a specific date range (parameter) regardless of the in-store dates on the consignments. This should then bring this report more inline with invoicing

Benefits identified as a result of the change:

Better, more accurate production of Quicks and finance reports

Background

The extract is written as a CSV and currently selects finance based on order schedules. The order schedule of an order is derived from the in-store date provided from SAP. Orders that are split as a consequence of receiving or loading off plan retain the original order schedule and so the advised Dunelm in-store date but do get assigned to the operational transport schedule (trips) for the day.

Suppliers do manifest and ship orders earlier and later than the advised in-store schedule date dictates and consequently revenue is recognised and invoiced by DHL in different time periods than reflected by the in-store schedule date.

The extract will be updated to provide a more accurate reflection of revenue (payments) realised and invoiced by reporting the revenue (payments) selected by a date range relating to the operational collection date in the plan.

To achieve this, the extract will use dates derived from each revenue record (payments) to define the selection of records rather than the in-store date of the orders as defined below.

Definition of ‘Revenue Date’

When a revenue record (payment) is created in C-TMS once rated from contracts, the revenue date is set to the date the payment was created. Each customer has an Invoice Requirements definition in C-TMS maintenance. All the customers for the Dunelm implementation are set to Accounting Date ‘Collection’. This means that as orders are planned to trips and trips are set to ACCEPTED status, the revenue date on the payments records are updated to become the planned collection date of the orders on the trip.

An outcome of this is that orders planned for collection on a Friday and planned for delivery the following week retain a payment revenue date of Friday. Note that these payments cannot be actualised and invoiced until the corresponding delivery trip is CONFIRMED and the status of the order is set to DELIVERED.

Solution

The solution is designed to cater for both forecast and actualised revenue that falls into a reporting date range using the revenue date on payments. This means the extract can be run prior to or post invoicing.

When the extract is run, the user will enter a from and to date range for the selection of payments. All payments with a revenue date that falls into the reporting date range will be included.

[As a further suggestion, we think having the revenue columns for forecast and again for actualised. This means that the extract can be used to check all the revenue has been actualised prior to invoicing – please confirm]