The input data file should be a CSV-formatted text file. A comma (“,”) will be used to separate each column. A carriage-return+line-feed character combination will be used to terminate each row. If a carriage-return+line-feed character combination must be included as part of the data of a single column, the column’s data should be enclosed in double-quotes.

The file will consist of a header row followed by one or more data rows. The header row will explicitly state which fields will be updated (and, by inference, which tables). The header row will include fields from a set of four tables. The row does not need to list all the fields in a table, nor does it need to reference each available table; it should only list as many fields as will be imported. The order in which it lists these fields will dictate the order in which the data will appear in the subsequent data rows.

Immediately following the header row there should be one or more data rows. Each data row shall contain the necessary command, key and data values needed to import one row of data into the database table(s). There must be one value column for each field-definition column declared in the header (though the columns can be left blank when appropriate).

Supported System Tables

MOVE_MANAGEMENT

MOVE_MANAGEMENT_CF

MOVE_MANAGEMENT_HOUSEHOLD_GOODS

MOVE_MANAGEMENT_HOUSEHOLD_GOODS_CF

The first non-blank row in the import file shall be interpreted as the header row. The header row shall be used to define which fields will be imported to the household goods detail (as such, they are referred to as field-definition columns).

Each field to be imported shall occupy one column. There is no upper limit to the number of columns. Every column should be unique within the header row (no duplicate columns).

The format for each field-definition column is <table name>!<field name>. For example, in order to update the Shipment_Type field of a MOVE MANAGEMENT HOUSEHOLD GOOD record, the field-definition column should say “MOVE_MANAGEMENT_HOUSEHOLD_GOOD!SHIPMENT_TYPE”.

Following the header row are one or more data rows. Each data row shall contain mandatory columns in addition to one or more data columns. The data columns must exactly match the layout defined in the header row. The mandatory columns are as follows:

All subsequent columns should contain data (or be blank when appropriate). The field order should exactly match the field order specified in the header row, as should the field count.

Generally speaking, the import can update any field in any of these tables other than any foreign key fields that link these tables to each other. For lookup-type fields (any field that appears as a drop-down list on the screen) the value given to the import is the full text of the value the user sees on the screen (NOT the ID or code that is looked up and stored in the database). A country or a currency field should be imported using the appropriate three-letter symbol (not the full name).

The unsupported fields for this import include:

MOVE_MANAGEMENT_SERVICE_REQUEST (all fields)

MOVE_MANAGEMENT!

MOVE_MANAGEMENT_HOUSEHOLD_GOOD!