Converting Orders to Dispatch

To move a customer who has our existing Ticket Printing system to Dispatch:

Settings

• Change the SYSTEM OPTIONS to activate Dispatch.

• Change plants in Plant Maintenance:
  • Change the plant type to DISPATCH - CONCRETE
  • Set the plant color
  • Hit <F2> to save the changes and create the TIMES tab.
  • Set the values in the TIMES tab.

• Shut down CompuCrete and login again.

Convert Existing Data

Trucks must be assigned a home plant. Once this is complete, the current plant for each truck should be set to its home plant so it will show on the Truck tab.

update arttruck
set current_plant = home_plant_no = '01'

To avoid potential foreign-key violations in the future, execute the following steps:

• Edit any existing orders that have numeric-only Order Codes (use the following script and review the results).

select order_code, cust_no from artordhd
where order_code between '0' and '9'
order by order_code

NOTE: In the SQL samples below, the system is transitioning to Dispatch on 3/15/2007. Substitute the date as necessary.

• Because some sites rely on ORDER CODE rather than JOB ID, be sure to save existing order codes into JOB_PO_LOC if the JOB_PO_LOC is not in use. Use the following script if necessary:

update artordhd
set job_po_loc = order_code
where delivery_date > '03/14/2007'
and (job_po_loc = '' or job_po_loc is null)

• Convert future-dated orders so they are ready by executing the following script in IBCONSOLE. This script saves the existing order code in the NOTES_4 field in case something goes wrong.

update artordhd
set notes_4 = order_code, order_code = GEN_ID(GEN_DIORDERID,1), ORDER_STATUS = 'O'
where delivery_date > '03/14/2007'
order by delivery_date, cust_no, order_code

Orders entered from the Ticketing Order Entry will not have the default plant times that were only set up a few minutes ago. The following script will populate these fields in the Dispatch Orders table.

update artordhd O
set batch_setup_minld = (select batch_setup_minld from artplant P where P.plant_no = O.plant_no),
batch_load_secyd = (select batch_load_secyd from artplant P where P.plant_no = O.plant_no),
plant_wash_minld = (select plant_wash_minld from artplant P where P.plant_no = O.plant_no),
job_setup_minld = (select job_setup_minld from artplant P where P.plant_no = O.plant_no),
job_wash_minld = (select job_wash_minld from artplant P where P.plant_no = O.plant_no)
where delivery_date > '03/14/2007'

Generated Projected Loads

Orders will not appear on the Dispatch Schedule Screen without their projected load data (DITPRJLD). This data is generated when the order is entered in Dispatch Order Maintenance. Since this data was entered using the Ticketing Order Maintenance, there are no projected loads.

At this time, there is no automated procedure to generate this data outside the Dispatch Order Maintenance program. Since Order Maintenance will generate this data anytime there is a change to an order, the only solution is to change one of the dispatch related fields.

• Run the following script to identify all orders that were flagged for Dispatch in the earlier step:

select cust_no, count(*) from artordhd
where order_code > '0' and order_code <= '9'
and order_status = 'O'
group by cust_no

• Go into Order Maintenance for these customers. The dispatch orders for these customers should be at or near the top since the numeric Order Code will sort ahead of any alpha orders they have.