Import Methods

Note: This feature requires at least one of the following modules licensed at your site:

● Chemical Inventory

● Form R Regulatory Reporting

● Tier II Regulatory Reporting

Inventory Integration offers the following standard import methods for importing small or large numbers of transactions to be automatically entered in your system. Each method imports only specific kinds of transactions, so take care to select the method appropriate to the transactions you want to import. If the transactions you need to import are not all appropriate to a single import method, divide these transactions into separate transaction files—one for each method—and import each file separately using the appropriate method.

One way to begin a transaction file for a specific method is to run a Quick View report displaying some or all of the required data types. You can then:

1. Generate this report output as an Excel spreadsheet.

2. Add/remove data columns until the spreadsheet matches the method's required arrangement (see below).

3. Replace the report's transaction data with the transaction data you want to import.

See below for details on each import method, including the Quick View report most suitable for generating a starting spreadsheet for the method, the columns required for the spreadsheet, and what data to enter in each column.

Basic SDS Transactions

Use this method to import and enter SDS detail transactions: detail Receipts, Usages, Disposals, and so on, involving products defined in your system as SDSs.

The "SDS Transactions Export" Quick View report is designed for the purpose of generating a starting spreadsheet for this import method. If you hide the report's Site and Proprietary SDS columns, the remaining columns exactly match the order required by this import method. For details on this report, see Transaction Reports > SDS Transactions Export.

However you choose to create a transaction file for this method, its columns must follow the order shown in the following table, which represents a portion of a sample transaction file. See below for specifics on each column.

Note: This table shows column headers for information purposes only. When you create a transaction file for import, column headers are optional.

Transaction Date	SDS File Name	Location	Transaction Type	Quantity	Unit of Measure	Transaction Description
2/14/2014	900289	Material Handling/Receiving Bay	Receipt	240	lb	Receipt of standard weekly order
2/15/2014	839211	10092783	Usage (Maintenance)	2.5	gal	Repainted ladies' room

1. Transaction Date: Date when transaction occurred. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

2. SDS File Name: File name of SDS whose product is involved in transaction. Specifics:

● Cannot be blank.

● Must match an existing SDS in Comply Plus. (You cannot create a new SDS during import by entering a new file name here.)

3. Location: Location where transaction occurred. Specifics:

● If the location is blank, you must select the import option to allow transactions with blank locations. (For details, see Importing a Transaction File.)

● If the location does not currently exist in Comply Plus, you must select the import option to allow creation of new locations during import. (For details, see Importing a Transaction File.)

● Location may be entered in either of the following ways:

● Full hierarchical name, each segment/level separated by a slash (/), as shown in first transaction in sample above. Maximum length of each segment/level: 255 characters.

● ID number or code, as shown in second transaction in sample above. (For details on defining IDs for locations, see Administration: Locations.)

4. Transaction Type: ID code of transaction's type. Specifics:

● Cannot be blank.

● Must match an existing transaction type in Comply Plus. (You cannot create a new transaction type during import by entering the new transaction type here.)

5. Quantity: The numeric value of the transaction quantity, not including the unit of measure (see next). Specifics:

● Cannot be blank.

● Must be numeric.

6. Unit of Measure: The unit of measure describing the transaction quantity (see previous). Specifics:

● Cannot be blank.

● Must match an existing unit of measure in Comply Plus. (You cannot create a new unit of measure during import by entering the new unit here.)

7. Transaction Description: Description of the transaction. Specifics:

● Can be blank.

● Suggested maximum length of 255 characters. An available import option may truncate longer descriptions down to 255 characters. (For details, see Importing a Transaction File.)

Basic Part Transactions

Use this method to import and enter part detail transactions: detail Receipts, Usages, Disposals, and so on, involving products defined in your system as parts.

The "Part Transactions Export" Quick View report is designed for the purpose of generating a starting spreadsheet for this import method. If you hide the report's Site column, the remaining columns exactly match the order required by this import method. For details on this report, see Transaction Reports > Part Transactions Export.

Note: This table shows column headers for information purposes only. When you create a transaction file for import, column headers are optional.

Transaction Date	Part Number	Part Description	Location	Transaction Type	Quantity	Unit of Measure	Transaction Description
3/15/2014	A902		21459007	Disposal (Expiration)	240	fl oz	Disposed of 10 expired bottles
3/19/2014	R004	Sulfuric Acid	Material Handling/Receiving Bay	Receipt	5	gal	Receipt of new reagent (trial)

1. Transaction Date: Date when transaction occurred. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

2. Part Number: Part number whose product is involved in transaction. Specifics:

● Cannot be blank.

● If the part number does not match an existing part number in Comply Plus, you must select the import option to allow creation of new parts during import. (For details, see Importing a Transaction File.)

3. Part Description: Description of part involved in transaction. Specifics:

● Can be blank. Generally, a part description is entered only when creating a new part during import (see previous) to define the new part's description.

● When you enter a part description (as shown for second transaction in sample above): Suggested maximum length of 255 characters. An available import option may truncate longer descriptions down to 255 characters. (For details, see Importing a Transaction File.)

4. Location: Location where transaction occurred. Specifics:

● If the location is blank, you must select the import option to allow transactions with blank locations. (For details, see Importing a Transaction File.)

● If the location does not currently exist in Comply Plus, you must select the import option to allow creation of new locations during import. (For details, see Importing a Transaction File.)

● Location may be entered in either of the following ways:

● Full hierarchical name, each segment/level separated by a slash (/), as shown in second transaction in sample above. Maximum length of each segment/level: 255 characters.

● ID number or code, as shown in first transaction in sample above. (For details on defining IDs for locations, see Administration: Locations.)

5. Transaction Type: ID code of transaction's type. Specifics:

● Cannot be blank.

● Must match an existing transaction type in Comply Plus. (You cannot create a new transaction type during import by entering the new transaction type here.)

6. Quantity: The numeric value of the transaction quantity, not including the unit of measure (see next). Specifics:

● Cannot be blank.

● Must be numeric.

7. Unit of Measure: The unit of measure describing the transaction quantity (see previous). Specifics:

● Cannot be blank.

● Must match an existing unit of measure in Comply Plus. (You cannot create a new unit of measure during import by entering the new unit here.)

8. Transaction Description: Description of the transaction. Specifics:

● Can be blank.

● Suggested maximum length of 255 characters. An available import option may truncate longer descriptions down to 255 characters. (For details, see Importing a Transaction File.)

SDS Form R Transactions

Use this method to import and enter SDS summary Usage transactions for use in Form R reporting. Each transaction imported using this method is automatically of the Sphera-supplied "FormR Use" transaction type, and can have one or more of the Sphera-supplied Form R transaction attributes (Mfg Use / Proc Use / Other Use) applied.

The "Form R Usages for SDSs" Quick View report is designed for the purpose of generating a starting spreadsheet for this import method. If you hide the report's Site, Product Name, and Proprietary SDS columns, the remaining columns exactly match the order required by this import method. For details on this report, see Form R Reports > Form R Usages for SDSs.

Note: This table shows column headers for information purposes only. When you create a transaction file for import, column headers are optional.

Transaction Start Date	Transaction End Date	SDS File Name	Location	Usage Quantity	Unit of Measure	Manufacture	Process	Otherwise Use	Transaction Description
4/1/2014	4/30/2014	511290	Factory Building 2/Production Floor	312	lb	X	X		Standard production usage, April '14
1/1/2014	6/30/2014	944287	33450033	7089	gal			X	Use of fertilizer for grounds, first half 2014

1. Transaction Start Date: Date when transaction began. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

2. Transaction End Date: Date when transaction ended. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

3. SDS File Name: File name of SDS whose product is involved in transaction. Specifics:

● Cannot be blank.

● Must match an existing SDS in Comply Plus. (You cannot create a new SDS during import by entering a new file name here.)

4. Location: Location where transaction occurred. Specifics:

● If the location is blank, you must select the import option to allow transactions with blank locations. (For details, see Importing a Transaction File.)

● If the location does not currently exist in Comply Plus, you must select the import option to allow creation of new locations during import. (For details, see Importing a Transaction File.)

● Location may be entered in either of the following ways:

● Full hierarchical name, each segment/level separated by a slash (/), as shown in first transaction in sample above. Maximum length of each segment/level: 255 characters.

● ID number or code, as shown in second transaction in sample above. (For details on defining IDs for locations, see Administration: Locations.)

5. Usage Quantity: The numeric value of the Form R usage quantity, not including the unit of measure (see next). Specifics:

● Cannot be blank.

● Must be numeric.

6. Unit of Measure: The unit of measure describing the usage quantity (see previous). Specifics:

● Cannot be blank.

● Must match an existing unit of measure in Comply Plus. (You cannot create a new unit of measure during import by entering the new unit here.)

7. Manufacture: Indicates whether the "Mfg Use" Form R transaction attribute applies to the usage. Specifics:

● Any non-blank entry (such as the X in the sample above) indicates a Form R "Manufacture" usage activity, and the "Mfg Use" attribute will be applied.

● Any blank entry indicates the usage is not a Form R "Manufacture" usage activity, and the "Mfg Use" attribute will not be applied.

8. Process: Indicates whether the "Proc Use" Form R transaction attribute applies to the usage. Specifics:

● Any non-blank entry (such as the X in the sample above) indicates a Form R "Process" usage activity, and the "Proc Use" attribute will be applied.

● Any blank entry indicates the usage is not a Form R "Process" usage activity, and the "Proc Use" attribute will not be applied.

9. Otherwise Use: Indicates whether the "Other Use" Form R transaction attribute applies to the usage. Specifics:

● Any non-blank entry (such as the X in the sample above) indicates a Form R "Otherwise Use" usage activity, and the "Other Use" attribute will be applied.

● Any blank entry indicates the usage is not a Form R "Otherwise Use" usage activity, and the "Other Use" attribute will not be applied.

10. Transaction Description: Description of the transaction. Specifics:

● Can be blank.

● Suggested maximum length of 255 characters. An available import option may truncate longer descriptions down to 255 characters. (For details, see Importing a Transaction File.)

SDS Summary Transactions

Use this method to import and enter SDS summary transactions—transactions summarizing individual inventory activities during a specified date range—non-specific to Form R and Tier II regulatory reporting. For details on importing reporting-related SDS transactions, see SDS Form R Transactions above or SDS Tier II Transactions below.

However, if either the Form R Regulatory Reporting module or the Tier II Regulatory Reporting module is licensed at your site, the "Form R Usages for SDSs" and "Tier II Maximums and Averages (SDS)" Quick View reports are easily altered for the purpose of creating a starting spreadsheet for this import method. Simply remove and add a few select columns until the spreadsheet matches the order required by this import method (see below). For details on these reports, see Form R Reports > Form R Usages for SDSs or Tier II Reports > Tier II Maximums and Averages (SDS).

Note: This table shows column headers for information purposes only. When you create a transaction file for import, column headers are optional.

Transaction Start Date	Transaction End Date	SDS File Name	Location	Transaction Type	Quantity	Unit of Measure	Transaction Description
5/1/2014	5/31/2014	511290	Factory Building 2/Storage	Disposal (Total)	86	lb	Total of disposals during April '14
1/1/2014	3/31/2014	993337	76139002	Max Qty	615	fl oz	Greatest on-hand quantity reached during Q1

1. Transaction Start Date: Date when transaction began. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

2. Transaction End Date: Date when transaction ended. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

3. SDS File Name: File name of SDS whose product is involved in transaction. Specifics:

● Cannot be blank.

● Must match an existing SDS in Comply Plus. (You cannot create a new SDS during import by entering a new file name here.)

4. Location: Location where transaction occurred. Specifics:

● If the location is blank, you must select the import option to allow transactions with blank locations. (For details, see Importing a Transaction File.)

● If the location does not currently exist in Comply Plus, you must select the import option to allow creation of new locations during import. (For details, see Importing a Transaction File.)

● Location may be entered in either of the following ways:

● Full hierarchical name, each segment/level separated by a slash (/), as shown in first transaction in sample above. Maximum length of each segment/level: 255 characters.

● ID number or code, as shown in second transaction in sample above. (For details on defining IDs for locations, see Administration: Locations.)

5. Transaction Type: ID code of transaction's type. Specifics:

● Cannot be blank.

● Must match an existing summary transaction type in Comply Plus. (You cannot create a new transaction type during import by entering the new transaction type here.)

6. Quantity: The numeric value of the transaction quantity, not including the unit of measure (see next). Specifics:

● Cannot be blank.

● Must be numeric.

7. Unit of Measure: The unit of measure describing the transaction quantity (see previous). Specifics:

● Cannot be blank.

● Must match an existing unit of measure in Comply Plus. (You cannot create a new unit of measure during import by entering the new unit here.)

8. Transaction Description: Description of the transaction. Specifics:

● Can be blank.

● Suggested maximum length of 255 characters. An available import option may truncate longer descriptions down to 255 characters. (For details, see Importing a Transaction File.)

SDS Tier II Transactions

Use this method to import and enter SDS summary Average and Maximum transactions for use in Tier II reporting. Each transaction imported using this method is automatically one of the Sphera-supplied "TierII Ave" or "TierII Max" transaction types, depending on its column in the transaction file. Each row in the file can include either one or two transactions; see below for details.

The "Tier II Maximums and Averages (SDS)" Quick View report is designed for the purpose of generating a starting spreadsheet for this import method. If you hide the report's Site, Product Name, and Proprietary SDS columns, the remaining columns exactly match the order required by this import method. For details on this report, see Tier II Reports > Tier II Maximums and Averages (SDS).

Note: This table shows column headers for information purposes only. When you create a transaction file for import, column headers are optional.

Transaction Start Date	Transaction End Date	SDS File Name	Location	Maximum Quantity	Maximum Unit of Measure	Average Quantity	Average Unit of Measure	Transaction Description
1/1/2014	6/30/2014	871044	71198299			615.75	lb	Ave Quantity for T2, Q1&2 2014
1/1/2014	12/31/2014	452277	Factory Building 2/Paint Shop	819	gal	222.75	gal	Max/Ave Quantity for T2, 2014

1. Transaction Start Date: Beginning date of the time period covered by the Maximum or Average. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

2. Transaction End Date: Ending date of the time period covered by the Maximum or Average. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

3. SDS File Name: File name of SDS whose product is involved in transaction. Specifics:

● Cannot be blank.

● Must match an existing SDS in Comply Plus. (You cannot create a new SDS during import by entering a new file name here.)

4. Location: Location where transaction occurred. Specifics:

● If the location is blank, you must select the import option to allow transactions with blank locations. (For details, see Importing a Transaction File.)

● If the location does not currently exist in Comply Plus, you must select the import option to allow creation of new locations during import. (For details, see Importing a Transaction File.)

● Location may be entered in either of the following ways:

● Full hierarchical name, each segment/level separated by a slash (/), as shown in second transaction in sample above. Maximum length of each segment/level: 255 characters.

● ID number or code, as shown in first transaction in sample above. (For details on defining IDs for locations, see Administration: Locations.)

5. Maximum Quantity: The numeric value of the Tier II maximum quantity, not including the unit of measure (see next). Specifics:

● Must be numeric.

● If Average Quantity and Unit of Measure (see below) are blank, this entry cannot be blank.

6. Maximum Unit of Measure: The unit of measure describing the Tier II maximum quantity (see previous). Specifics:

● Must match an existing unit of measure in Comply Plus. (You cannot create a new unit of measure during import by entering the new unit here.)

● If Average Quantity and Unit of Measure (see below) are blank, this entry cannot be blank.

7. Average Quantity: The numeric value of the Tier II average quantity, not including the unit of measure (see next). Specifics:

● Must be numeric.

● If Maximum Quantity and Unit of Measure (see above) are blank, this entry cannot be blank.

8. Average Unit of Measure: The unit of measure describing the Tier II average quantity (see previous). Specifics:

● Must match an existing unit of measure in Comply Plus. (You cannot create a new unit of measure during import by entering the new unit here.)

● If Maximum Quantity and Unit of Measure (see above) are blank, this entry cannot be blank.

9. Transaction Description: Description of the transaction. Specifics:

● Can be blank.

● Suggested maximum length of 255 characters. An available import option may truncate longer descriptions down to 255 characters. (For details, see Importing a Transaction File.)

Part Form R Transactions

Use this method to import and enter part summary Usage transactions for use in Form R reporting. Each transaction imported using this method is automatically of the Sphera-supplied "FormR Use" transaction type, and can have one or more of the Sphera-supplied Form R transaction attributes (Mfg Use / Proc Use / Other Use) applied.

The "Form R Usages for Parts" Quick View report is designed for the purpose of generating a starting spreadsheet for this import method. If you hide the report's Site and Product Name columns, the remaining columns exactly match the order required by this import method. For details on this report, see Form R Reports > Form R Usages for Parts.

Note: This table shows column headers for information purposes only. When you create a transaction file for import, column headers are optional.

Transaction Start Date	Transaction End Date	Part Number	Part Description	Location	Usage Quantity	Unit of Measure	Manufacture	Process	Otherwise Use	Transaction Description
1/1/2014	6/30/2014	E711		Factory Building 2/Production Floor	312	lb	X		X	Standard production usage, Q1&2 2014
4/1/2014	6/30/2014	X128	Formaldehyde (50% Dilution)	44562099	7089	gal		X	X	First use of new part, Q2 2014

1. Transaction Start Date: Date when transaction began. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

2. Transaction End Date: Date when transaction ended. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

3. Part Number: Part number whose product is involved in transaction. Specifics:

● Cannot be blank.

4. Part Description: Description of part involved in transaction. Specifics:

● Can be blank. Generally, a part description is entered only when creating a new part during import (see previous) to define the new part's description.

5. Location: Location where transaction occurred. Specifics:

● If the location is blank, you must select the import option to allow transactions with blank locations. (For details, see Importing a Transaction File.)

● If the location does not currently exist in Comply Plus, you must select the import option to allow creation of new locations during import. (For details, see Importing a Transaction File.)

● Location may be entered in either of the following ways:

● Full hierarchical name, each segment/level separated by a slash (/), as shown in first transaction in sample above. Maximum length of each segment/level: 255 characters.

● ID number or code, as shown in second transaction in sample above. (For details on defining IDs for locations, see Administration: Locations.)

6. Usage Quantity: The numeric value of the Form R usage quantity, not including the unit of measure (see next). Specifics:

● Cannot be blank.

● Must be numeric.

7. Unit of Measure: The unit of measure describing the usage quantity (see previous). Specifics:

● Cannot be blank.

● Must match an existing unit of measure in Comply Plus. (You cannot create a new unit of measure during import by entering the new unit here.)

8. Manufacture: Indicates whether the "Mfg Use" Form R transaction attribute applies to the usage. Specifics:

● Any non-blank entry (such as the X in the sample above) indicates a Form R "Manufacture" usage activity, and the "Mfg Use" attribute will be applied.

● Any blank entry indicates the usage is not a Form R "Manufacture" usage activity, and the "Mfg Use" attribute will not be applied.

9. Process: Indicates whether the "Proc Use" Form R transaction attribute applies to the usage. Specifics:

● Any non-blank entry (such as the X in the sample above) indicates a Form R "Process" usage activity, and the "Proc Use" attribute will be applied.

● Any blank entry indicates the usage is not a Form R "Process" usage activity, and the "Proc Use" attribute will not be applied.

10. Otherwise Use: Indicates whether the "Other Use" Form R transaction attribute applies to the usage. Specifics:

● Any non-blank entry (such as the X in the sample above) indicates a Form R "Otherwise Use" usage activity, and the "Other Use" attribute will be applied.

● Any blank entry indicates the usage is not a Form R "Otherwise Use" usage activity, and the "Other Use" attribute will not be applied.

11. Transaction Description: Description of the transaction. Specifics:

● Can be blank.

● Suggested maximum length of 255 characters. An available import option may truncate longer descriptions down to 255 characters. (For details, see Importing a Transaction File.)

Part Summary Transactions

Use this method to import and enter part summary transactions—transactions summarizing individual inventory activities during a specified date range—non-specific to Form R and Tier II regulatory reporting. For details on importing reporting-related part transactions, see Part Form R Transactions above or Part Tier II Transactions below.

The "Part Summary Transactions Export" Quick View report is easily altered for the purpose of creating a starting spreadsheet for this import method. If you hide the report's Site column, the resulting columns exactly match the order required by this import method. For details on this report, see Transaction Reports > Part Summary Transactions Export.

Note: This table shows column headers for information purposes only. When you create a transaction file for import, column headers are optional.

Transaction Start Date	Transaction End Date	Part Number	Part Description	Location	Transaction Type	Quantity	Unit of Measure	Transaction Description
6/1/2014	6/30/2014	S991		Factory Building 1/Production Floor	Usage (Total)	111.5	gal	Total of usages during June 2014
5/1/2014	5/31/2014	H167	R-90 Sprocket	76139002	Receipt (Total)	220	lb	Total quantity received during May 2014

1. Transaction Start Date: Date when transaction began. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

2. Transaction End Date: Date when transaction ended. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

3. Part Number: Part number whose product is involved in transaction. Specifics:

● Cannot be blank.

4. Part Description:Description of part involved in transaction. Specifics:

● Can be blank. Generally, a part description is entered only when creating a new part during import (see previous) to define the new part's description.

5. Location: Location where transaction occurred. Specifics:

● If the location is blank, you must select the import option to allow transactions with blank locations. (For details, see Importing a Transaction File.)

● If the location does not currently exist in Comply Plus, you must select the import option to allow creation of new locations during import. (For details, see Importing a Transaction File.)

● Location may be entered in either of the following ways:

● Full hierarchical name, each segment/level separated by a slash (/), as shown in first transaction in sample above. Maximum length of each segment/level: 255 characters.

● ID number or code, as shown in second transaction in sample above. (For details on defining IDs for locations, see Administration: Locations.)

6. Transaction Type: ID code of transaction's type. Specifics:

● Cannot be blank.

● Must match an existing summary transaction type in Comply Plus. (You cannot create a new transaction type during import by entering the new transaction type here.)

7. Quantity: The numeric value of the transaction quantity, not including the unit of measure (see next). Specifics:

● Cannot be blank.

● Must be numeric.

8. Unit of Measure: The unit of measure describing the transaction quantity (see previous). Specifics:

● Cannot be blank.

● Must match an existing unit of measure in Comply Plus. (You cannot create a new unit of measure during import by entering the new unit here.)

9. Transaction Description: Description of the transaction. Specifics:

● Can be blank.

● Suggested maximum length of 255 characters. An available import option may truncate longer descriptions down to 255 characters. (For details, see Importing a Transaction File.)

Part Tier II Transactions

Use this method to import and enter part summary Average and Maximum transactions for use in Tier II reporting. Each transaction imported using this method is automatically one of the Sphera-supplied "TierII Ave" or "TierII Max" transaction types, depending on its column in the transaction file. Each row in the file can include either one or two transactions; see below for details.

The "Tier II Maximums and Averages (Part)" Quick View report is designed for the purpose of generating a starting spreadsheet for this import method. If you hide the report's Site and Product Name columns and add a Part Description column, the resulting columns exactly match the order required by this import method. For details on this report, see Tier II Reports > Tier II Maximums and Averages (Part).

Note: This table shows column headers for information purposes only. When you create a transaction file for import, column headers are optional.

Transaction Start Date	Transaction End Date	Part Number	Part Description	Location	Maximum Quantity	Maximum Unit of Measure	Average Quantity	Average Unit of Measure	Transaction Description
1/1/2014	6/30/2014	S211		44562718	771	lb	233.5	lb	Max/Ave Quantity for T2, Q1&2 2014
1/1/2014	6/30/2014	H556	Yellow Traffic Paint	Factory Building 2/Paint Shop	56	gal			Max Quantity for T2, Q1&2 2014

1. Transaction Start Date: Beginning date of the time period covered by the Maximum or Average. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

2. Transaction End Date: Ending date of the time period covered by the Maximum or Average. Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)

3. Part Number: Part number whose product is involved in transaction. Specifics:

● Cannot be blank.

4. Part Description: Description of part involved in transaction. Specifics:

● Can be blank. Generally, a part description is entered only when creating a new part during import (see previous) to define the new part's description.

5. Location: Location where transaction occurred. Specifics:

● If the location is blank, you must select the import option to allow transactions with blank locations. (For details, see Importing a Transaction File.)

● If the location does not currently exist in Comply Plus, you must select the import option to allow creation of new locations during import. (For details, see Importing a Transaction File.)

● Location may be entered in either of the following ways:

● Full hierarchical name, each segment/level separated by a slash (/), as shown in second transaction in sample above. Maximum length of each segment/level: 255 characters.

● ID number or code, as shown in first transaction in sample above. (For details on defining IDs for locations, see Administration: Locations.)

6. Maximum Quantity: The numeric value of the Tier II maximum quantity, not including the unit of measure (see next). Specifics:

● Must be numeric.

● If Average Quantity and Unit of Measure (see below) are blank, this entry cannot be blank.

7. Maximum Unit of Measure: The unit of measure describing the Tier II maximum quantity (see previous). Specifics:

● Must match an existing unit of measure in Comply Plus. (You cannot create a new unit of measure during import by entering the new unit here.)

● If Average Quantity and Unit of Measure (see below) are blank, this entry cannot be blank.

8. Average Quantity: The numeric value of the Tier II average quantity, not including the unit of measure (see next). Specifics:

● Must be numeric.

● If Maximum Quantity and Unit of Measure (see above) are blank, this entry cannot be blank.

9. Average Unit of Measure: The unit of measure describing the Tier II average quantity (see previous). Specifics:

● Must match an existing unit of measure in Comply Plus. (You cannot create a new unit of measure during import by entering the new unit here.)

● If Maximum Quantity and Unit of Measure (see above) are blank, this entry cannot be blank.

10. Transaction Description: Description of the transaction. Specifics:

● Can be blank.

● Suggested maximum length of 255 characters. An available import option may truncate longer descriptions down to 255 characters. (For details, see Importing a Transaction File.)

Start Lot Transactions

Use this method to import and enter Start Lot transactions to create new lots in your system. Each transaction imported using this method is of the Start Lot transaction type you choose during import, and results in a new lot with the properties defined below and a default Lot-Specific component definition.

As with other import methods, you can generate a Quick View report containing relevant data columns as an Excel spreadsheet to begin a starting spreadsheet for this import method. However you choose to create the transaction file, its columns must follow the order shown in the following table, which represents a portion of a sample transaction file. See below for specifics on each column.

Note: This table shows column headers for information purposes only. When you create a transaction file for import, column headers are optional.

Location	Number of Lots	Lot Size	Unit of Measure	Product Name	Manufacturer	Product Description	Date of Inventory
20091892	15	5	gal	Formula 32-00Q	Glo-Rite Labs	Glow-in-the-Dark Paint	3/12/2014
R&D Wing/Lab Room 7	50	12	fl oz	Freakishly Formic Acid	Acid Vicious	Undiluted Formic Acid (Lab Reagent)	3/15/2014

1. Location: Location where lots begin. Specifics:

● If the location is blank, you must select the import option to allow transactions with blank locations. (For details, see Importing a Transaction File.)

● If the location does not currently exist in Comply Plus, you must select the import option to allow creation of new locations during import. (For details, see Importing a Transaction File.)

● Location may be entered in either of the following ways:

● Full hierarchical name, each segment/level separated by a slash (/), as shown in second transaction in sample above. Maximum length of each segment/level: 255 characters.

● ID number or code, as shown in first transaction in sample above. (For details on defining IDs for locations, see Administration: Locations.)

2. Number of Lots: Number of lots you want to create at this location, with the properties shown in the other columns. Specifics:

● Cannot be blank.

● Must be a numeric, whole value.

3. Lot Size: The numeric value of each lot's balance, not including the unit of measure (see next). Specifics:

● Cannot be blank.

● Must be numeric.

4. Unit of Measure: The unit of measure describing the lot size (see previous). Specifics:

● Cannot be blank.

● Must match an existing unit of measure in Comply Plus. (You cannot create a new unit of measure during import by entering the new unit here.)

5. Product Name: Name of product contained by lot(s). Specifics:

● Can be blank.

● Maximum length: 80 characters.

6. Manufacturer: The numeric value of the Tier II maximum quantity, not including the unit of measure (see next). Specifics:

● Can be blank.

● Maximum length: 50 characters.

● If this manufacturer name does not match an existing name in your system's manufacturer index, this new name is added to the index upon import.

7. Product Description: Description of the new lot(s). Specifics:

● Can be blank.

● Suggested maximum length of 255 characters. An available import option may truncate longer descriptions down to 255 characters. (For details, see Importing a Transaction File.)

8. Date of Inventory: Creation date of lot(s). Specifics:

● Cannot be blank.

● Must be in numeric format appropriate for your region. (Example above shown in US format.)