Some features in this document require MIL-Comply Release 1.4.0223+.

MIL-Comply supports a specialized CSV import format for creating defense shipments.  It works with both Comply/Labeling and Comply/Shipper.  The import files may contain all of the data required for its purpose, or serve as a starting point with the user entering additional data. The import format supports the full range of MIL-Comply work product, from Mil-Std-129R container labels to WAWF Receiving Reports and Invoices.

When created with a csvmp file extension the file may be opened automatically as an email attachment, web page link, or Windows Explorer, in the same way a .txt file opens in Notepad.   Or it may be retrieved by the user from the In-Box in Labeling or Shipper.  In cases where the file must be created with a csv extension, such as when exported from some programs, it can be opened from the In-Box.  The In-Box is simply a folder on the user’s machine or a network drive that is dedicated to the user or shared with others.

As an alternative, the same functionality can be achieved with the Mil-Pac M12 format, which is a key-value pairs file format.

Examples of CSVmp Files

The CSVmp file below creates a shipment for delivery order N0010420FX000, with a shipment number to be assigned automatically by MIL-Comply. It has a single line item, and includes a IUID for each of the two items to be shipped.

LITM,1,0001AA,1005-01-235-1674,WIDG-364223-AR2,1HLD9,WIDGET ASSEMBLY,2,EA,M10,03/21


Each CSVmp row starts with a record type, and the version of that record which follows.  The example above demonstrates four CSVmp row types:

  • UCIE – marks the file as a CSVmp.  It may include some additional options for the import process.
  • DOCM – identifies the document being created with a contract number and delivery order, if applicable.    
  • LITM – defines a line item being shipped, includes data like the CLIN, NSN, Noun, Part Number and the Quantity shipped.  There would be one of these for each CLIN.
  • IUID – adds a UID to the shipment, associated with one of the LITMs by its CLIN.    

A basic CSV file has two required rows, UCIE and DOCM, then generally one or more Line Item (LITM) rows.   There are a few fields that are required, however, most of the data can be added by the user on the fly.  The exterior container weight of a data item more likely to be determined on the fly than maintained in a business system. 

The DOCM line must include a contract and/or delivery order number.   A shipment number can be included, or assigned automatically by MIL-Comply.   The same is true for a reference number, which allows for tracking by an internal identifier, such as sales order number.   For UID shipments, the UIIs may be included in the file or added by the user.

Data for a Military Shipment Label (MSL) could be added to the shipment by the user, or imported.  The next example expands upon the first by including data for a MSL.  This adds a few more fields to the DOCM line and some addresses.  The example below added a shipment number (XYZ0023) and reference number (FY21-000221) for demonstration purposes.    

LITM,1,0001AA,1005-01-235-1674,WIDG-364223-AR2,1HLD9,WIDGET ASSEMBLY,2,EA,M10,03/21


The addresses data can be limited to just the CAGE or DODAAC, left for the user to retrieve from MIL-Comply database (very easy).  Note that the Mark-For lacks a DODAAC.   This is because the data are Mark-For Instructions, rather than an address.   Addresses can also be imported as discrete components: three entity lines, three physical address lines, city, state, zip code, and country code.   This alleviates the need for MIL-Comply to parse and determine what is what in a single line. 

WAWF Receiving Reports & Invoices

A few more fields can be added to the DOCM row to create a DD250/Receiving Report and/or Invoice (or entered by the user).   There are record types that support all of the features the MIL-Comply WAWF transactions.   These additional fields include:

  • Additional addresses/codes:  Contract Administration Office, Payment Office, Prime Contractor, QAR, Issued By, LPO
  • Document-level fields: FOB, Acceptance Point, Invoice Number and Date, Ship-In-Place, etc.
  • Initiator Instructions – aka Block 23
  • Additional Email Addresses – up to nine email addresses to receive WAWF workflow notifications
  • Attachments – identified by path, attached at time of transmission to WAWF

Special Invoice Transactions

In addition to the standard Commercial Invoice that MIL-Comply can submit to WAWF for a Receiving Report, two other more specialized invoice transactions are supported by CSV import:

  • Cost Voucher (SF1034/SF1035)
  • Navy Shipbuilding Invoice (NSI)
  • Progress Billing (SF1443)

CSVmp File Specifications

For more information, including sample import files, request access to the CSVmp Format Specifications.