ITEM PREPROCESSOR (SQL)

This is the help for Microsoft SQL Server databases. Click here to open the help for Oracle databases.

The Item Preprocessor is an add-on product in Costpoint Product Interfaces that you can use to upload item information (i.e., parts, services, or goods) from flat ASCII text files into Costpoint. This preprocessor will also update item information for existing rows if the input file has a value for a column. However, if an input file field is null, the existing database columns in Costpoint that apply will not be deleted or changed to null. You can specify the network location and name of the input file, and the application will perform all necessary database and business rule validation.

This preprocessor application is a separately licensed product for Deltek Costpoint.  You must obtain a user license from Deltek and have Costpoint properly configured on a Microsoft SQL Server database platform in order to use this application. Please contact your Deltek account manager or Deltek Support for more information.

If you select the Separate Items By Company checkbox in the Product Definition Corporate Settings subtask of the Product Definition Corporate Settings screen, the system will assign your company ID to your newly processed items and saved parameters. Users logged into other companies will not be able to change or delete these items or parameters. If you select the Separate Items by Company checkbox, you can have two item records in the database with the same ID (and revisions, if you also selected the Allow Multiple Revisions for Each Item checkbox in the Product Definition Corporate Settings subtask of the Product Definition Corporate Settings screen), as long as the items are linked to different companies. If you are changing or deleting an item, item record, or its related data, the company ID must be the same for both your user ID and the item ID.

If you do not select the Separate Items by Company checkbox, all items in the database will be available to users in all companies, and two items will not be able to coexist with the same item ID or revision in the database.

Use the Material Requirements Planning control functions (in the MRP Corporate Settings subtask of the MRP Settings screen) to enable MRP planning by company ID.

Setup Procedures

You must perform the following before you run the Item preprocessor:

  1. Set up the Unit of Measure Codes referenced in the input file in the Units of Measure screen in Costpoint Product Definition.

  2. Set up the Commodity Codes referenced in the input file in the Commodity Codes screen in Costpoint Product Definition.

  3. Set up the Product Classification Codes referenced in the input file in the Product Classifications screen in Costpoint Product Definition.

Input File

Use the Select pushbutton to choose an ASCII text file to be uploaded, or enter the filename.  This is a required field.  The input file cannot have an extension of .ERR. The .ERR extension is reserved for the error file. You can process only one input file at a time.

All user ID columns in the Costpoint 5.0 database contain a maximum of 20 characters. However the input file will limit user ID field lengths to 18 characters to accommodate existing fixed-length input files from previous Costpoint databases.

International users: The data can contain non-English characters, provided they are in the ASCII character set. Before creating an ASCII text (.TXT) file, be sure that your keyboard language is set to "EN" (United States English) to prevent the application from generating errors.  

We recommend the use of .TXT and .CSV file-naming conventions.

Input File Format

Delimited

Select this radio button to indicate that the input file has delimiters as field separators. This is the default.

Fixed Length

Select this radio button to indicate the input file contains fields that start and end in a specified column.  If the Input File is a fixed-length format file, you must fill every position with the appropriate number of either characters or spaces for a given column before entering data for the next column.  It is not necessary to zero fill numbers; you can use spaces to maintain the proper format. Numeric fields should be right justified; character fields should be left justified. Once you have entered the last character of meaningful data for the input file, you need not fill the remaining column lines with spaces. 

For example, the Part 2 (PRT2) record format's maximum line length (i.e., the entire input file) is a total of 689 characters and the last character of meaningful data is in position 90, you do not need to add the remaining 599 spaces. However, let's say that the Commodity Code (beginning at position 100 on the input file) is five characters long. You must include the Commodity Code plus three additional spaces before entering the Make or Buy Code beginning in position number 108. Please refer to the "Processing Details" section for additional information.

File Delimiter

If the input file is Delimited, you must choose the delimiter. The default is Comma. To use another delimiter, select the Other radio button and enter a single character in the field to the right.

Note:  The delimiter cannot be embedded in any of the input fields.  When the program encounters the declared delimiter, it interprets it as the end of the input field.

Error Handling

Use the options in this group box to determine how validation errors will be handled.  Errors occur if the input file record is not valid or a condition is not met for a field that is being processed in an input file record. If you select the Process Valid Records radio button, all valid rows on the input file will be processed. Process Valid Records is the default.  If you select the Process No Records radio button, no input rows will be processed when errors are encountered. In either case, an error report listing all validation errors will be produced as well an ASCII error file (if the Produce NO ASCII Error File checkbox is unselected). The error file will have the same filename as the original input file except the suffix will be ".ERR," and the file will contain all input rows that are in error.  This error file can then be corrected, renamed, and reprocessed until all rows are processed. The program will timestamp the TIMESTAMP field at the end of each record, indicating the most recent instance in which the file was created. 

Error File

Produce NO ASCII Error File

Select this checkbox if you do not want to produce an ASCII error file.

Process

Select this button on the toolbar to process the input file.

Process/Print

Select this button on the toolbar to process the input file and print the error report.

PROCESSING DETAILS

PART (PT2)

ERROR MESSAGES