Import Inventory Transactions

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.

Field Description
View Inventory Transactions

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.

Note: There are two ways to work with input files in Costpoint
  • You can access the input file from the network by using Alternate File Locations.
  • You can upload the input file to the Costpoint database; in which case, no further access to network folders is necessary.

If you decide to use the first option, click 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.

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).

Warning:

Multiple users can run the application simultaneously; however, each user can run the application only one time.

Multicompany

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).

Processing Details

When importing inventory transactions, the process steps include the following:

  1. The system reads rows from the Input File and inserts them into the Import Inventory Transactions work tables.
  2. The application applies defaults and validates each transaction in its entirety.
  3. The system inserts any errors found into the error work table.
  4. The system inserts transactions with no errors into the Costpoint tables and updates the Inventory tables.
  5. If the application finds transactions with errors, it writes all rows for those errors to the Error File "INUSER_IDMMDDYY.ERR."
  6. Once you exit the screen, the system deletes data in all the work tables, including the error table.
  7. Once transactions are processed and imported, you can view them in the maintenance screens listed in above.
  8. You cannot change transaction lines once they are read and imported into the Costpoint database.