Import file format

This table shows the format that is required for the CSV file. The file must contain a header row that contains the header names in the order that is shown in the table. The header names must be spelled correctly. Subsequent rows must contain 14 commas that separate the 15 data elements. If a line does not have a value for an element, the file must contain a placeholder, which is a comma, for that element. You can use a text editor, such as Notepad, or Excel to create the CSV file.

Element number	Header name	Data	Required element	Example
1	warehouseKey	Warehouse number	Yes	sr01
2	employeeKey	Employee number**	Yes	12344
3	departmentHeaderKey	Department ID at the header level **	No	dept1
4	workOrder	Work Order number**	Yes*	54321
5	project	Project**	Yes*	proj1
6	machineKey	Machine number**	Yes*	m101
7	erpItemKey	ERP product number	Yes***	1-001
8	promiseDate	Promise date	No	2/1/2011
9	requestedQty	Requested quantity	Yes	10
10	issuedQty	Issued quantity	Yes	10
11	chargeNumber	Charge number	No	c110
12	departmentLineKey	Department ID for the line item**	No	dept2
13	customerItemKey	Customer product number	Yes***	1-001c
14	inventoryType	Inventory type, c-customer or d-distributor	Yes, if line is a Return	c
15	machineLineKey	Machine number at line level**	No	m101

* The work order, project, and machine number are required if these options are selected on the employee's record in Storeroom.

**These values are replaced by the default values from warehouse records in Storeroom, if Use Defaults in Entries is selected on the warehouse record. For example, if a default department is defined for the warehouse, it overrides the imported values in the departmentHeaderKey and DepartmentLineKey fields. If a default employee is also defined, the default department from the Employee record is used.

*** Either the erpItemKey or customerItemKey is required, but you can include both for a line item. If the erpItemKey, or Distribution SX.e product, is associated with active and inactive customer product records, inactive records do not cause an error during issue and returns import processing. The inactive records are ignored if an active record is available.

To avoid an error, ensure that you do not identify the inactive customer product as the customerItemKey on the import file. Only specify the Distribution SX.e product as the erpItemKey.

Each CSV file can contain issues for multiple warehouses, machine types, etc. The record can represent an issue of stock or a return. A return is indicated by a negative issued quantity value in the file.