Pipeline
3
SECTION
4.5.8.2 -SITE MASTER-FILE ASCII INPUT
USAGE: To import a file containing,
all or a subset, of new or changed information to be posted to the Site
master-file. The input file is required to be in a very strictly stylised
format so that Pipeline can allocate data to the correct fields on the correct
Site records. Not all fields are available for import.
DISCUSSION: Make sure that you have a good backup of your data
and that no-one is using Pipeline during the update. Pipeline may not update
the files as you expected and the only completely safe way to correct the mistake
is to restore your data from backup.
The import file required must be called stnmf.csv, although case is not important in Windows. This
file must reside in your data directory, eg \UNT3DATA\COMP1. Also, the file must not be in use. This is
important because if you have created the file from a spreadsheet and have
saved it but not closed it, the file will still be locked by the spreadsheet
program and Pipeline will not be able to open it.
The input file must be in CSV format. This is a comma-delimited
file (without quotes) with one record per line. Exporting from
Excel, choosing the CVS format, will produce the correct format automatically.
Each alphanumeric field must be left justified. Pipeline will make no attempt
to remove leading spaces (for names, etc.). Numeric fields should not have any
dollar signs or commas. Do not use commas in any alpha fields.
These will be treated as a field break and Pipeline will not import the row
correctly. A blank cell will be treated as a valid entry, thus a blank alpha
cell will clear the corresponding field in the master-file and a blank numeric
cell will reset the corresponding field in the master-file to zero. Thus if you
do not wish to change a field, either delete the row, delete the column or make
sure that the cell contains the same information as the field in the
master-file currently has.
The first line of the input file must contain only
field names. These fields are mostly identical to those exported using SITE
ASCII EXPORT (see SECTION 3.5.7.1). In fact
the easiest way to create the initial file is to export it first using this
program with the headings option turned on. This also has the advantage of
accurately exporting the current information. There are some fields available
in the Import program that are not created in the Export program. The full list
is detailed below. Note the use of the underscore character instead of spaces.
This format must be copied exactly.
RENAME_TO
COPY_TO
Are not supported, yet.
The following fields are currently supported.
CODE
OWNER_WORK_PHONE
SITE_PHONE
OWNER_FAX
DIRECTOR1_WORK_PHONE
DIRECTOR1_FAX_PHONE
OWNER_EMAIL
SAME-DAY-SETTLEMENT
DIRECT-DEBIT_CASH
DIRECT-DEBIT_CARWASH
AGENT_BSB
AGENT_BANK_ACCOUNT
MAX_DAYS_S/CHECK
DAYS_PER_S/CHECK
INC_NO-SALE_S/CHECK
INC_CANCEL_S/CHECK
INC_ERR/DEL_S/CHECK
INC_REFUNDS_S/CHECK
INC_S/DOC_S/CHECK
SOFTWARE_MAINT
PIEFACE?
PROMO?
COCO?
ATM?
MAX._TESTS
SITE_GROUP
GUARANTEE_VALUE
GUARANTEE_TYPE
Notes:
1)
The order of the columns is not important but they must not appear more
than once.
2)
CODE must appear, as it is used to link the row
to the Site Code as it currently exists on the Site master-file.
3)
Apart from CODE, you must have at least one more column.
4)
RENAME_TO is only required if you wish Pipeline to change the
current Site code to another code. The new code must not exist and the old code
will not exist after the import program has run. If you wish to switch two
codes, it is possible to do this by entering three lines. The first row will
change one of the codes to a dummy value, the second row will rename the second
Debtor code to the first code and the third row will rename the first code to
the second, eg ONE ®
XXX; TWO ®
ONE; XXX ®
TWO. This function is currently not supported.
5)
COPY_TO is used when you wish to duplicate Site items.
Sometimes you have a group of codes that you wish to enter again, eg for
export. This option can have other fields changed at the same time but it will
change the original code’s fields, so normally this option is only used by
itself. This function is currently not supported.
6)
RENAME_TO and COPY_TO can be used together, but
care should be taken to achieve the results you expect.
7)
OTHER_KEY’s are replaced by whatever you have defined it as
in SYSTEM DEFAULTS.
8)
Some fields are only relevant to specific installations.
9)
If you try to import the raw file form the ASCII EXPORT program,
it will not read in successfully unless you choose to export with comma
delimiters between fields and without quotes around fields (numeric and alphanumeric).
This can be set in the options part of the export program. Normally this is not
the way this function is used, the purpose of this function being to manipulate
the file in a spreadsheet program and importing the result.
10)
Most fields are not verified on import. You must enter valid
information. For the field that are validated, invalid data will be ignored.
When the program starts, it will firstly check
whether the import file exists and is accessible. Having established this,
Pipeline will read the first line of the file and check for its correctness. If
no obvious errors are found, you will be asked to confirm that you have made a
backup and then you will be asked to confirm that you wish to proceed.
Pipeline will then read import lines one at a time
confirming firstly that the CODE field corresponds to a Site code and then renaming,
copying or just replacing the fields and records, as defined by the columns you
have chosen. If an invalid or blank row is encountered, it will be skipped.
Pipeline will continue processing until it reaches the end of the import
program. Finally the import file will be renamed to stnmf.old (to stop you from
accidentally rerunning the program with used data) before returning you the MAIN
MENU.
