Viewing and selecting orders in TCL

For definitions in the customer’s machine the LD COL.TRANSFER file will show the few things that can be done.

For example we can select orders by;

SELECT COL.TRANSFER WITH DATE = “10/13/06”

At the > prompt type;

CT COL.TRANSFER

The whole order can be viewed and errors seen as in the XML and XML.res file on the PERFXP machine. Since this is quite a bit of information to go through if the customer has a large number of orders a day it will be useful to use the QFIND command to narrow down your search for a particular order. An example of this would be;

:select col.transfer with date = "10/12/06"

[404] 52 items selected out of 4529 items.

>qfind

Enter File Name to Search : col.transfer

Enter String to Locate : web7192

Enter String to Locate :

Edit (Y/N) ? n

1416537341A

:ct col.transfer 1416537341a

And thus you can see the order your looking for.

Another useful dictionary is;

LD CUST.DETAIL

The last section or which pertains to CDN customers.

Since the customer may well be doing some of the setups it is quite possible that things like the customer confirmation is omitted (6.1.1 ‘OC’). It may be useful to get a list of those that do have this. From the LD CUST.DETAIL the TRANSFER.LOGIN field has attribute 56 so we can type;

SORT CUST.DETAIL BY NAME WITH 56 56 NAME

This will give the view;

cust.detail      8478889381

Transfer Login   PerfectionTEST

Customer Name    GERBER-ELGIN-243906

A useful tip here is to use SET.WIDE (O prior to the command so we get a nice looking list to send to the customer such as;

cust.detail Transfer Login.......................... Customer Name.........

6308622800  PerfectionTEST                           GERBER-AURORA-130690

4256430444  PerfectionTEST                           GERBER-BELLEVUE-15982

Because of the way the CDN process sends orders via us to the customer and again back through us it is worth noting that if the customer is complaining that they have received the fax automatically sent out by PPG but not the CDN order in Point of Sale then we need to use the above commands (QFIND to find web numbers) on the PERFXP PS.PO.TRANSFER account.

If the orders are not present here either then we need to contact PPG.

The dictionary for COL.TRANSFER on the PERFXP machine in PS.PO.TRANSFER will not have the options the customers machine has in view of this to find an order here simply doing the QFIND command for COL.TRANSFER will facilitate the tracking of an errant order.

Incoming Orders. (from PPG to us prior to Dispatch to Customer ( Single Source))

An example of a select statement for the orders inbound from PPG is;

SELECT COL.TRANSFER WITH A0 = 20070227] AND WITH A0 = [CCS]

Where 20070227 is the date and CSS is a part of the header description in the inbound order. Orders in the Col.transfer list without CSS should be those coming back from the customer to us to be sent to PPG. If you see the xml for either you will see the inbound to us from PPG say order request whereas coming back they will say order confirmation.

From the PerfXP machine go to ps.po.transfer and type the command ct pcx,col.transfer.xref to see the list of orders inbound from PPG waiting to go to the customers machine.

If you do see a list of stuck orders from the PCX command above then chances are the col.transfer process is stuck on the customers machine. You can find the port from col.transfer.status and tandem to it to check for errors. The process can then be restarted from the typical customer online menu. Re-running the PCX command on the PerfXP machine will show that these orders then disappear when the process is restarted and working.

If it is thought there is an error connecting to the PPG side we can test this in an Iexplorer window by using the following URL:

https://buyat.ppg.com/Glaxisjmsi/receiverequest.asmx ?

If the URL works chances are PPG should be able to receive orders.