Price code record structure

Use the following record structure to update database prices by price code:

Record structure for price updates by price code
Elements Description

pc

An alphanumeric Data Importer code in the first field indicates that the information that follows is the price code.

Price code

A price code for an item that can be matched to an external pricing service.

Pricing category

In the absence of a price, a comma (with or without a blank space preceding it) serves as a placeholder. No comma or placeholder is necessary after the last price.

 

Example: pc,S.O.G. Con4000, ,65.00

  • pc is the Data Importer code indicating that the record is a price code update.
  • S.O.G. Con4000 is the price update code.
  • ,, is a placeholder because this record does not have a labor price.
  • 65.00 is the new material price.

Guidelines for creating price update records

Observe the following guidelines when entering each record (or row) in the price update file:

  • The first field of each record must contain an alphanumeric Data Importer code to identify the type of record being updated. For example, use "pi" to identify a phase and item code record, "pc" for a price update code record, and "wbs" for a WBS code and WBS value record.

    Note: An update file can contain all three types of records: "pi," "pc," and "wbs."

  • Enter category prices in the order of labor, material, subcontractor, equipment, and other (LMSEO).

    For example, you must enter the labor category price first. If you are not updating the labor price, insert a comma (with or without a blank space preceding it) as a placeholder. Next, enter the material category price or its placeholder,followed by the subcontractor, equipment, and other category prices or their placeholders.

  • You must use commas to separate the prices in a text file.
  • If prices in multiple records affect the same phase and item codes in a database, the price in the last record updates the database.
  • If prices are explicitly set to 0, they are used to update prices in the database. However, prices that are simply left blank are not used.

  • The price field can be a maximum length of 8.3 digits and cannot contain commas, negative signs (-), asterisks (*), bars (|), or letters.