Background: Project Import

Use the Project Import (PSI) program to import project data from an ASCII file. See Road Map for more information.

This topic has these subtopics:

Why Use a Native Disc
Import Process
Project Import Log
ASCII File Format

Why Use a Native Disc

The file you import data from can reside on your PC (or network) or on a native disc.

Importing from a native disc is much faster since it the data does not have to be read on the PC and then transferred
Import files residing on your PC (or network) are limited to 512-characters

Import Process

The import process consists of these steps:

Run the Project Import program to read the ASCII file.

The program validates the format of the ASCII file and writes the Project Import Log. This log reports the project number that the system assigned and any error messages. The program prints to your default output device.

If you selected the Erase import file when done option, the program erases the ASCII file to prevent reprocessing it.

Review the Project Import Log.
Run the Project Maintenance (PSM) program to maintain the project.

Project Import Log

The log includes this information:

Sequence number
Number assigned to this project
Import project number
Type: See Statement type under ASCII File Format
Error message with field; for example, Customer name missing, Invalid parent item number, Header does not exist; Detail not imported, Enter a value for [field name]

ASCII File Format

Use the Data Dictionary Inquiry (DFQ) program to list the variables that you can include, their position, and length. Enter the data file name for each statement to list this information.

Statement type	Import project description	Data file name
HEADER	Master	P01
CUSTMR	Customer master	P02
ITEM	Inventory	P03
BILLHD	Product structure header	P04
BILLDT	Product structure	P05
RTGHDR	Routing header	P06
RTGDET	Routing operation detail	P07
VENDIT	Vendor item	P08
VENDPR	Vendor item pricing	P09
COMMNT	Header notes	P10
CMCUST	Customer notes	P11
CMITEM	Item notes	P12
CMITBR	Item branch notes	P12A
CMBILH	Bill of material header notes	P13
CMBILD	Bill of material detail notes	P14
CMRTGH	Routing header notes	P15
CMRTGD	Routing detail notes	P16
CMV1A	Vendor item notes	P17
PRJQTY	Quantities	P18

Dates must be in the format YYYYMMDD.
Entries are case sensitive. For example, the program accepts Y and N for fields that you normally select or leave blank, but not y or n.
These are required variables:

Statement type	Required variables
HEADER	HEADER, project number, customer name if you include customer number, parent item no, description, ECL, RRL, and stocking UOM
CUSTMR	CUSTMR, project number, customer number, customer name, postal code, tax code, AR terms, AR credit limit, order limit, currency, and price code
ITEM	ITEM, project number, item number, description, stocking UOM, and controlled?
BILLHD	BILLHD, project number, parent item number, and ECL
BILLDT	BILLDT, project number, parent item, ECL, component number, and quantity per assy
RTGHDR	RTGHDR, project number, parent item number, RRL If Std lot size is blank, the program sets it to 1.
RTGDET	RTGDET, project number, parent item number, RRL, operation sequence, operation code
VENDIT	VENDIT, project number, item, vendor, sequence, purchasing UOM, and UOM conversion
VENDPR	VENDPR, project number, item, vendor, minimum order qty 1 through 10 (some of which may be 0) If Effective date is blank, the program sets it to 00000000. If Expiration date is blank, the program sets it to 99999999.
COMMNT, CMCUST, CMITEM, CMBILH, CMBILD, CMRTGH, and CMV1A	comment type, project number, comments If no Line number, the program assigns 100 with an increment of 10. If notes exist, the program adds 10 to the last line number.
PRJQTY	PRJQTY, project number, sequence number, project qty