About the price update log

When you import a price update file, the Data Importer creates an Import Data log that lists all the records that were updated as well as records that could not be updated for some reason.

Viewing the Import Data log

To view the Import Data log, you can click the Log button in the Data Importer window immediately after the import, or you can click the Log icon on the ribbon when you return to the Data view.

Interpreting the price update log

The Import Data log has three parts:

• Summary information
• Errors found
• Records matched

The following sections explain each part in more detail.

Summary information

The summary section shows:

• The number of rows in the price update file that match records in the database.
• The total number of rows in the price update file.
• The number of database records that match criteria in the price update file.
• The total number of database records.

• The number of item records that were updated.

  Note:  

  • Each updated record is counted only once, even if it was updated multiple times or if it was updated to match the initial value(s).
  • The count is increased for each record that is linked to an updated item record.

• The number of fields updated in the database. This count is increased:

  • Each time a field, or a combination of fields, was updated for a given record. (Each update is counted, even if a field was updated multiple times.)
  • Each time a field was updated to match the initial value(s).
  • Each combination of field and record that is linked to an updated item record.

• A list of warnings about the number of database records that could not be updated because:

  • The item record uses crews.
  • The item categories specified in the price update file do not exist in the item record.
  • The item record is linked to an item that uses a different price code.
  • The price in the update file is not a-number.

Errors found

This section lists errors found in the update file during processing.

An error is reported for a row in the price update file if the row includes:

• A blank phase code.
• A blank item code.
• A blank price update code.
• A blank WBS code or WBS value.

An error is also reported there was no match in the database for a row in the price update file.

Records matched

This section lists the database records that matched the criteria in the import file. For each record that was matched, the list shows:

• A code to identify the record.
• The number of the row that was matched in the update file.
• The phase and item updated.
• The original and the updated category unit price.
• An indicator for linked prices.
• A note if the price update was skipped for one of the reasons in the warnings section.