The Checklist Setup Information is taken from your checklist files and shows setup fields.
The following table explains the naming conventions of the checkpoint setup data share file: #####y[md].shr
| Field | Definition | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ##### | Store Number | ||||||||||||||||||||||||||||||||
| y | This character denotes that the file contains checkpoint setup information. | ||||||||||||||||||||||||||||||||
| m | This character denotes the month. The characters range from a to l and are as follows:
|
||||||||||||||||||||||||||||||||
| d | This character denotes the day. The characters range from a to z and 1 to 5 and are as follows:
|
The following is an example of an actual record in what is known as “comma-delimited” format. This means that the information you entered in each field in this POS system record is separated by a comma.
“01/01/2015”,”1”,”4WD Checklist”,”B”…
We have numbered the fields in the following record in order to explain them more clearly to you. Each bolded number indicates one field.
| Note: | Some of the fields contained in this file are for internal system processing only and may not be useful to you. |
| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| “01/01/2015” | “1” | “4WD Checklist” | “B” | “15218131037” | “1” | “AF” | “1” | “AIR FILTER” | “N/A” | “” | “OK” |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| “” | “REC RPLCD” | “” | “REPLACED” | “AF” | “” | “” | “” | “” | “” | “” | “” | “” | “B” | “1” |
The following chart lists and describes the contents of the (y) checkpoint setup file.
| Num. | Description | Definition | ISI Field Name | Output Format* | Quoted? | Example Value | General Release Version When Added |
|---|---|---|---|---|---|---|---|
| 1 | System Date | Date from the computer operating system for the day the export is created. | system date | ##/##/#### | X | 01/01/2015 | 15.1 |
| 2 | Checkpoint Set Number | The number of the checkpoint set which can be a value from 1 to 99. | inf5a.set | 1 | 15.1 | ||
| 3 | Checkpoint Set Description | The checkpoint set description. | inf5a.description | X | 4WD Checklist | 15.1 | |
| 4 | Checkpoint Set Print Flag | Multi-use flag. Values are N,B,I, or R. N for None is the default and will not print the checklist set description on PPI invoices and will suppress printing the entire checkpoint set on the checklist report. B for Both will have the description print on PPI invoices and the checkpoint set will appear on the checklist report. I for Invoice will print the checkpoint set description on the PPI invoices but will suppress showing the checkpoint set on the checklist report. R for Report will not print the checklist set description on the PPI invoices but will print the entire checkpoint set on the checklist report. | inf5a.print | X | B | 15.1 | |
| 5 | Last Modified | A date and time stamp signifying when the record was last changed. Not a fixed width | inf5a.last_modified | X | 15218131037 | 15.1 | |
| 6 | Checkpoint Set Number | The checkpoint set number this checkpoint item belongs to. It should match to inf5a.set from above. | inf5b.set | #(2) | 1 | 15.1 | |
| 7 | Checkpoint Item Group | The checkpoint group label this checkpoint item belongs to | inf5b.group | X(5) | X | AF | 15.1 |
| 8 | Checkpoint Item Line Number | The line number of the checkpoint item from the setups. | inf5b.line | #(2) | 1 | 15.1 | |
| 9 | Checkpoint Item Description | The checkpoint item description | inf5b.description | X(40) | X | AIR FILTER | 15.1 |
| 10 | Checkpoint Item Response 1 | Checkpoint Item Response 1 static text and up to three custom response masks. | inf5b.response1 | X(20) | X | N/A | 15.1 |
| 11 | Checkpoint Item Response 1 Service Code | Service code used to check against the work order if this response is the one selected for the checkpoint item. | inf5b.resp_srv_code1 | X(3) | X | 15.1 | |
| 12 | Checkpoint Item Response 2 | Checkpoint Item Response 2 static text and up to three custom response masks | inf5b.response2 | X(20) | X | OK | 15.1 |
| 13 | Checkpoint Item Response 2 Service Code | Service code used to check against the work order if this response is the one selected for the checkpoint item. | inf5b.resp_srv_code2 | X(3) | X | 15.1 | |
| 14 | Checkpoint Item Response 3 | Checkpoint Item Response 3 static text and up to three custom response masks. | inf5b.response3 | X(20) | X | REC RPLCD | 15.1 |
| 15 | Checkpoint Item Response 3 Service Code | Service code used to check against the work order if this response is the one selected for the checkpoint item. | inf5b.resp_srv_code3 | X(3) | X | 15.1 | |
| 16 | Checkpoint Item Response 4 | Checkpoint Item Response 4 static text and up to three custom response masks. | inf5b.response4 | X(20) | X | REPLACED | 15.1 |
| 17 | Checkpoint Item Response 4 Service Code | Service code used to check against the work order if this response is the one selected for the checkpoint item | inf5b.resp_srv_code4 | X(3) | X | AF | 15.1 |
| 18 | Checkpoint Item Response 5 | Checkpoint Item Response 5 static text and up to three custom response masks. | inf5b.response5 | X(20) | X | 15.1 | |
| 19 | Checkpoint Item Response 5 Service Code | Service code used to check against the work order if this response is the one selected for the checkpoint item | inf5b.resp_srv_code5 | X(3) | X | 15.1 | |
| 20 | Checkpoint Item Response 6 | Checkpoint Item Response 6 static text and up to three custom response masks. | inf5b.response6 | X(20) | X | 15.1 | |
| 21 | Checkpoint Item Response 6 Service Code | Service code used to check against the work order if this response is the one selected for the checkpoint item | inf5b.resp_srv_code6 | X(3) | X | 15.1 | |
| 22 | Checkpoint Item Response 7 | Checkpoint Item Response 7 static text and up to three custom response masks. | inf5b.response7 | X(20) | X | 15.1 | |
| 23 | Checkpoint Item Response 7 Service Code | Service code used to check against the work order if this response is the one selected for the checkpoint item | inf5b.resp_srv_code7 | X(3) | X | 15.1 | |
| 24 | Checkpoint Item Response 8 | Checkpoint Item Response 8 static text and up to three custom response masks. | inf5b.response8 | X(20) | X | 15.1 | |
| 25 | Checkpoint Item Response 8 Service Code | Service code used to check against the work order if this response is the one selected for the checkpoint item | inf5b.resp_srv_code8 | X(3) | X | 15.1 | |
| 26 | Checkpoint Item Print Flag | A flag which controls if the checkpoint item description prints on the PPI invoice Values are B,D,R, and N. B for Both will print the description and the response. D for Description will print only the description on the invoice. R for Response will only print the response on the invoice. N for None will suppress the entire checkpoint item from printing. | inf5b.print | X(1) | X | B | 15.1 |
| 27 | Store Number | Store number where the invoice with the checklist was generated. | inf0.store_nbr | X(5) | X | 1 | 15.3 |
* The Output Format column uses X to represent string fields and # to represent numeric fields. E.g. X(5) represents a string up to five characters in length. #(14) represents a number up to 14 digits in length.
** This data share table is composed of two data sources combined together into a single file so the customer does not have to do this themselves. Inf5a.dat stores the master checkpoint set number with information such as description, print, and last_modified. Inf5b.dat stores the individual checkpoint items and responses that can belong to a set. Because it is a one to many relationship the beginning fields of several rows will have what appear to be replicated information.
*** The export is written to export one row for every record in inf5a.dat and inf5b.dat. If there is a problem in the database such as orphaned records, this could present itself visually by seeing rows where the first section of fields are all blank and the second section have values, or the first section of fields have values, and the second section are all blank. Either condition is an indication that the setups of the store need to be reviewed. It is expected that the normal output for the file is to be able to successfully match up an inf5a.dat record with its inf5b.dat records and export rows of information where fields in both sections show data.
