ORDER TO CASH ROUTE DETERMINATION

Route determination in RP1 is determines by custom enhancement of carrier service information made up
of Route, Carrier and Depot (optional i.e. not all services are depot controlled ).
Route is determined from custom tables controlled by transaction ZSDM.
As per SFRL’s HLD document, the existing Route Determination function in RP1
(Z_O2SD_ROUTE_DETERMINATION) will be used for delivery services for all new order types in the
same way as for existing RP1 document types (sales order and delivery). So, the new document types
must be valid for route determination.

During online processing of Sales document, Function Z_O2SD_ROUTE_DETERMINATION will create the
list of all potential routes with carrier. Then the list of valid routes will be sorted by based on below
mentioned parameters checks.

FOLLOWING PARAMETER CHECKS WITH ZTABLES ARE USED TO DETERMINE

ROUTE:
1) Table ZO2SD_RD01, Entry should be maintained for sales organisation and distribution channel, sales
document type. Additional fields are checks for creating mode(VA01) and changing mode (VA02) of order
type.
Three activities can be defined for these mode:
a) Always determine route,
b) Never determine route and
c) Only determine if it route is blank.

2) Table ZO2SD_RD02, Entry should be maintained for sales organisation and distribution channel,
delivery type.
Additional fields are checks for creating mode(VL01N) and changing mode (VL02N) of delivery type.
Three activities can be defined for these mode:
a) Always determine route,
b) Never determine and
c) Only determine if it route is blank.
3) Table ZO2SD_RD03, contains a list of potential route codes for each SD document category Eg. 'B' for
quotation, 'C' for orders, 'J' for deliveries etc.

4) Table ZO2SD_RD04, check for Material division. If division is not maintained in this table, then the
services is not valid and is removed from the list of potential services.

5) Table ZO2SD_RD11 for sales items and table ZO2SD_RD12 for delivery items. If the item category
exists in these appropriate table, then it is NOT required for the determination process.
6) Table ZO2SD_RD05, For Shipping Conditions. If a service has shipping conditions specified for it then
the shipping condition of the sales document must be amongst them.

6) Table ZO2SD_RD06, the leading part (First 3 characters) of postcode of Ship-to-party is called
‘outcode’. Outcode should be entered in table against the appropriate carrier, service group and
depot(optional).

Table ZO2SD_RD13, Used for postcode restriction. If any of the potential services is maintained for
postcode in this table, then the service is removed from the list of potential services.

7) Table ZO2SD_RD07, if no customer groups are specified in table ZO2SD_RD07 then all customer
groups are valid. Table ZO2SD_RD09, if customer group 1 is specified in the table then for that
customer group 1 field, list of potential routes will be selected.
8) Table ZO2SD_RD08, Entry should be maintained for Route, carrier and Sales document type. Sales
document type must be amongst the existed entries otherwise the route is not valid and is removed from
the list of potential routes.

9) Delivery date requirement, if a customer delivery time (held against the schedule line in the arrival time field)
has been specified, the service must have a delivery time that spans the customer delivery time, if not then the
service is removed from the list of potential services. It is also removed if the service has no specific delivery time
range.

10) Table ZO2SD_RD_ROUTE, Compare the service limits with items data of sales order, this includes
quantity, weight and net value. If any of the service limits are not met then the service is removed from
the list of potential services.

NOTE : Here, net value is the cost condition VPRS which is maintained under item level at conditions tab.

As most of the routes in table has price limit up to 100 GBP. Check VPRS has price less than 100
GBP for all the items in Sales order.
Please make sure that the weight of BOM header is maintained otherwise no route will be
determined. Weight should be within the limit of services.
 After the above-mentioned checks, remaining valid Routes are then sorted by Service Preference,
where 1 has the highest priority and 99 has the lowest priority.
The service with the highest priority is then assigned the line item.

 If Route is determined, then the carrier services will be populated as Forwarding agent in partner tab
of ITEMs. If Depot exist for route, then Depot will be populated as Depot partner function.
 If no potential services (routes) exist, then an error is returned to the user during the save phase of any
sales document.
See below the example of one of the error:

 If the same routes are used by existing RP1 customers and migrating customer but each requires
separate pricing, the ZDEL pricing condition for delivery services allows price to be differentiated at the
customer account level, or for a group of customers by using Customer Group 5 (labelled “Promo Code”).

ROUTE ANALYSIS - To turn the analysis on or off, use transaction ZSDM go to menu path Tool and
select 'Analysis on' or 'Analysis off'.
If Analysis is on, then the route determination analysis screen will appear during the online processing of
sales documents and deliveries that shows the steps of route determination.

ROUTE DETERMINATION OF THE EXCALIBUR PROCESS:

1) When the Create Order or Amend Order interface is executed - In addition to the standard process
checks which is described above. In Excalibur, the list of potential services (routes) filtered by the service
type from route master table ZO2SD_ROUTE. Service type is a generic name for a group of routes e.g.
'NEXT DAY' or 'BEFORE 10AM'. Then it will follow the rest of the checks as per the standard process.

2) When the Delivery Service Enquiry interface is executed - Instead of assigning a single service to an
item the list of potential services are sorted into Service Type sequence, and one service form each service
type is returned along with the service type description. This is because at this point Excalibur is only
interested in generic services e.g. 'Next Day', 'Before 10AM' and not the specific carrier service. The CSA
will present these service types to the customer, and the chosen service type route code will be used on
the create order and used in the process described in Excalibur process.
A list of services is supplied for both the requested delivery date and the day after. Although the carrier and
depot information will not exist the route will always exist as this is the link to which service type the
customer requested.

When does automatic Route determination happen?

 During processing of the Sales Document - Almost every time the <Enter> button is pressed or the
screen view changes, the enhancement will re-evaluate the parameters that are used to determine
service details. Now the service information is only populated on the order if the determination
process is successful for all order items, otherwise the fields remain blank.

 At Save of the Sales Document - Carrier service information is again determined. If carrier service
information cannot be determined an error message is output stopping the order from being saved,
unless the sales document is incomplete for some other reason, in which case the message is
issued as a warning only. If partial routes can be determined then the route, carrier and depot is
populated for those item only, with item where no determination was successful having no route,
carrier or depot information.

 At Save of the Delivery Document - Carrier service information is determined. If carrier service
information cannot be determined an error message is output stopping the delivery from being
 saved.

When does automatic route determination not happen?

 When a sales document has been delivered or partially delivered i.e. as soon as subsequent documents
exist.

 During change of a delivery if the delivery block flag has a value, which indicates that it is being processed by
LIS.

 When a delivery document has been picked, packed, post goods issued.

 During change of a delivery, if the above conditions are passed then a check is made on the delivery date,
postcode of the ship-to address, item delivery quantity and weight, if none of these have changed then
determination does not happen. This is also true if the user manually changes the route.
If any of the above are true automatic determination will not happen, in which case the user could override the
service information, be it route, carrier or depot (routes are carrier specific, therefore, changing the carrier may cause
the route/carrier combination to become invalid).