in the File Location field to select an alternate file location. If you choose the second option, leave the File Location field blank and use the File Upload Manager to upload the input file to the Costpoint database.Use this application to import inventory transactions from an ASCII text file. You can capture transactions from a non-Costpoint source (for example, bar code systems) and export them into a text file in the defined format for import.
This implementation supports the loading of new inventory transactions, where the preprocessor: (1) reads the input file, (2) validates the input file against the Costpoint database, and (3) inserts and/or updates data in the necessary Inventory, Purchasing, and Receiving tables. The format of the input file records differs according to the transaction type being processed. The first field/character of a record determines the inventory transaction type, the format expected for that transaction, the validations performed, and the database updates to be made.
You can view transactions that are loaded by this preprocessor for I transaction types (Issues to Project/Account/Organizations) on the Enter Issues to Project/Account/Org or PO screen.
You can view transactions that are loaded by this preprocessor for W transaction types (Issues to Manufacturing Orders) on the Enter Manufacturing Order Issues screen.
You can view transactions that are loaded by this preprocessor for L transaction types (Location Transfers) on the Enter Location Transfers screen.
You can view transactions that are loaded by this preprocessor for H transaction types (Actual Counts) on the Manage Actual Counts screen.
There are validation rules for Issues to Manufacturing Orders transactions (type W), Issues to Project/Account/Organization Combinations (type I), Location Transfers (type L), and Actual Counts (type H).
in the File Location field to select an alternate file location. If you choose the second option, leave the File Location field blank and use the File Upload Manager to upload the input file to the Costpoint database.Validation of company tables is triggered by the company ID of the user executing the process. When looking up valid values, the system validates all company-related tables using the user's company ID. When a new inventory record is saved, it is automatically assigned the user's company ID. If you use Find or Query, the process filters on parameters by company. All new parameter rows are saved with the user's company ID. You can also keep parts separated by company in Costpoint if you select the Separate Items By Company check box in the Corporate Settings block of the Configure Product Definition Settings screen.
The system validates certain values by company during the input file validation process (that is, checking for valid values in the input file). When the system validates whether an input file value exists in the following tables, the company ID assigned to the user executing the process is filtered with the list of valid values in the tables:
|
Costpoint Table |
Costpoint Table Name |
|
WHSE |
Warehouse |
|
WHSE_LOC |
Warehouse Location |
|
INVT_ABBRV_CD |
Inventory Abbreviation Code |
|
EMPL |
Employee |
|
PROJ |
Project |
|
ORG |
Organization |
|
MO_HDR |
Manufacturing Order Header |
|
RSN_CD |
Reason Code |
|
RES_HDR |
Reservation Header |
|
PHYS_COUNT |
Physical Count |
|
ITEM/PART |
Item and Part (only if you select the Separate Items By Company check box in the Corporate Settings block). |
The system reads rows from the Input File and inserts them into the Import Inventory Transactions work tables.
The application applies defaults and validates each transaction in its entirety.
The system inserts any errors found into the error work table.
The system inserts transactions with no errors into the Costpoint tables and updates the Inventory tables.
If the application finds transactions with errors, it writes all rows for those errors to the Error File "INUSER_IDMMDDYY.ERR."
Once you exit the screen, the system deletes data in all the work tables, including the error table.
Once transactions are processed and imported, you can view them in the maintenance screens listed in above.
You cannot change transaction lines once they are read and imported into the Costpoint database.
Use the fields in this block to create a new parameter ID or to retrieve a previously saved parameter ID. A parameter ID represents a set of screen selection parameters. After you have saved a parameter ID and its related parameters, you can retrieve them using Query.
You can use the retrieved parameters to produce reports and run processes more efficiently and with greater consistency. The saved parameters are also useful and necessary when you want to run the process as part of a batch job. Many users save a unique set of parameters for each different way they run a report or process. When you select a previously saved parameter ID or parameter description, the associated saved screen selection parameters automatically display as selection defaults. The page setup and print options are also included in the saved parameter ID if there are any. You can change any of the associated selection defaults as necessary.
Enter, or click 
to select, a parameter
ID of up to 15 alphanumeric characters. Choose characters for your parameter
ID that help identify the type of selections you made in the screen, such
as PERIOD or QUARTERLY.
When you save your record, all the selections made in the screen are stored with the parameter ID. Later, you can retrieve the parameter using Query.
You can use the parameter to run the process more efficiently because you can select the parameter ID with its previously defined screen selections. After the default selections display in the screen, you can override the defaults.
Enter, or click to select, a parameter
description of up to 30 alphanumeric characters.
As much as possible, the preprocessor employs default values from the settings screens in Costpoint, including (but not limited to) establishing default values on the Configure Inventory Settings and Configure Serial/Lot Settings screens, warehouse and location information in Inventory, and inventory abbreviation information on the Manage Inventory Projects screen.
The format of each record in the input file is based on the transaction type of the record being processed (I, W, L, or H). The first field/character determines the inventory transaction type, the format expected for that transaction, the validations performed, and the database updates to be made. When you have entered the input file, use the Options group box to choose the format in which the input file data will be processed and saved.
Enter the location of the input file you are importing. There are two ways to do this:
In the File Location field, enter, or click to select, the alternate file location where the input file is located. Alternate file locations are set up in the Manage Alternate File Locations screen.
or
From the Global Menu, click Process » File Upload. On the File Upload Manager dialog box, click Browse and use the dialog box to select the file you want to import. If you select the Overwrite? check box, Costpoint will overwrite any file of the same name that already exists in the Costpoint database. Click Upload when you are finished. If you use this method, leave the File Location field blank. For more information about the File Upload Manager, see the File Upload Manager topic in the Getting Started Guide.
Enter, or click to select, the name of the file to use for the process.
Select the format of the input file from drop-down list. The available options available are:
Delimited — Select this option to process files with fields separated by a pre-defined delimiter (commas or another character). Selecting this option enables the use of the Comma and Other options in the File Delimiter field.
Fixed Length — Select this option to process the file with no field delimiters. For fixed-length, ASCII text input files, you must fill every position in the input file 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, it is not necessary to fill the remaining column lines with spaces.
For example, if the Issue to Project/Account/Organization Combinations input file's maximum line length (that is, the entire input file) is a total of 479 characters and the last character of meaningful data is in position 222, you do not need to add the remaining 257 spaces. However, if the Reservation ID (beginning at position 213 on the input file) is only seven characters long, you must include the Reservation ID plus three additional spaces before entering the Reservation Line Number in position 223.
End every row with a carriage return and a line feed.
If you select the Delimited option in the Input File Format field, select the type of delimiter from the drop-down list.
Comma — Select this option to use a comma as the file delimiter.
Other — Select this option to use another character as the file delimiter; enter the character in the field to the right.
If an error is detected, all rows that were not processed are moved to an ASCII error file in the same format in which they were originally saved. The error file is placed in the same directory as the input file with the name "INUSER_IDMMDDYY.ERR," where the "USER_ID" is the user ID of the person executing the preprocessor, and MMDDYY is the month/day/year that the process was run. If a file with the same name already exists, the new error(s) are appended to the existing file. Select an option to determine what happens if an error occurs during processing.
If you select this option and an error occurs, only those input rows that share the same Inventory Transaction ID, Transaction Type, and Warehouse as the error row are suspended (not loaded to Costpoint) and moved to the error file.
If you select this option and an error occurs, all rows within that input file are suspended (not loaded to Costpoint) and moved to the error file.
There are two options for numbering the inventory transactions, depending on how the input file is loaded.
Select this option to use the input file's transaction ID as the Costpoint inventory transaction ID on all saved transactions. You must provide transaction IDs for all input file rows. The warehouse last transaction ID is not changed.
Select this option to have Costpoint assign IDs to the valid transactions based on the warehouse and transaction type. The application uses the warehouse and transaction type to look up the next system transaction ID. If transaction IDs are provided in the input file, the program uses them only to group transaction rows together. All input file rows with the same warehouse, transaction type, and transaction ID are given the same transaction header. If you have not set up that transaction type for auto-assigning in the selected warehouse in the Transaction IDs subtask of the Manage Warehouses screen, the system returns an error.
ISSUES TO MANUFACTURING ORDERS (TRANSACTION TYPE "W")
ISSUES TO PROJECT/ACCOUNT/ORGANIZATION COMBINATIONS (TRANSACTION TYPE "I")
LOCATION TRANSFERS (TRANSACTION TYPE "L")
ACTUAL COUNTS (TRANSACTION TYPE "H")