CSV import: Purchasing transactions

You can import purchasing transactions by uploading a CSV file, rather than entering them individually in the Purchasing application.

Download a template

We recommend downloading a new blank template from either the transaction list page or the Company setup checklist, whenever you import information into Sage Intacct. This is important because:

  • Templates are automatically customized based on your company configuration, including dimensions and custom fields you created.
  • Templates can be updated by Intacct at any time, especially when a new version of Intacct is released. This means that an older template might not work.
If you download from a transaction list page, you don't need any Company permissions.

To download a template from a transactions list page:

  1. Go to Purchasing > All > Transactions.
  2. Select a transaction type to open a Transaction list page.
  3. Select Import. An Import dialog box opens.
  4. Select the Download template link.

To download a template from the Company setup checklist:

  1. Go to Company > Setup > Configuration > Import data.

    A list of information that you can import appears.

  2. Decide on a type of information to upload, and select the Template link associated with that information.

Prepare a CSV file for import

When you download a template, the correct headers are in the template already. All you have to do is fill in the columns with your data, save it as a CSV file, and upload the file.

The header titles in the template you download correlate to fields in Intacct. Incorrect header titles will cause an upload error.

For more information about the CSV upload process, including best practices, common errors, and how to upload your CSV file, see Prepare your file for CSV import.

Best practices

The following best practices will help you prepare your CSV file for upload.

Avoid common import errors

Intacct recommends following these guidelines to avoid import errors.

Import a CSV file

Now that you've entered your data and looked through it for any of the common issues imports can have, you’re ready to import your file to Intacct.

To import your CSV file:

  1. Go to Company > Setup > Configuration > Import data.

  2. Find the information type that you want to import, and select the corresponding Import link.
  3. In the Import Company Information dialog, set the following and select Import:

After an import, Sage Intacct informs you if the import was successful and how many records were imported.

In a completely successful import, the confirmation page lets you verify all the records in your original file were, in fact, successfully imported without having to verify them manually.

Import encoded CSV files

File Encoding offers options for uploading CSV files in different formats. You can enable the system to detect automatically the type of CSV file that you’re uploading. You can also select a specific CSV file format, such as Mac OSx, Windows-1252, or other types.

Import offline

Some imports can take considerable time, depending on their size and how much processing Intacct must do to the data. When in doubt, select Process offline on the import utility page.

When the offline process is complete, Intacct sends an email to the address you entered in the Import Company Information dialog (where you imported your file).

Intacct recommends that you select Process offline when importing CSV files, and provide your email address. If your import fails, you’ll always be notified, and the failed records are sent to your email.

Handle errors

If you experience import errors, review the importing tips and common errors.

Import errors occur when you try to import information that doesn’t match the requirements of the template. Each template has a set of required information you must enter to import the file successfully, and formats to follow for certain kinds of information. Read the descriptions in the template to determine the most accurate way to enter your data.

If individual transactions are in error, the rows in the transaction that are in error are saved in a CSV file for you along with an error code for each row. Check your email for information about specific errors. See Find and fix CSV import errors for more information.

For more information about the CSV upload process, read Prepare your file for CSV import.

About importing Purchasing transactions

Number of transactions

If you have more than 500 transactions and the import, either online or offline fails, check the batch frequency for the transaction definitions that are associated with the imported transactions. It's recommended that the Summary frequency on the Documents configuration tab of the Order Entry configuration page be set to Each document when importing a large number of transactions.

Serial numbers

The Purchasing transaction import template contains the options to add serial numbers for items.

If you are importing an item that is serialized, then the serial number columns must be populated, taking the following into consideration:

  • There can only be one unit per Serial Number.
  • To add a serial number, you must use the SERIALNO field.
  • Use COMPONENTID to specify the Item ID of a child of a kit that has a serial number assigned to it.

  • Aisle, row, and bin information is optional in the AISLEID, ROWID, and BINID columns.
  • The expiration date (EXPIRATION) is optional.
  • There can be multiple units per Lot Number (LOTNO).
  • Lot tracking can have multiple units in a given lot. Use the TRACK_QUANTITY column to define the quantity.
    • For example: The total quantity of the line is 10 units, but 6 units are in LOTNO Apple and 4 units are in LOTNO Banana. The 6 and 4 are defined in the TRACK_QUANTITY field.

For more information about importing serial numbers, see CSV import: Serial numbers.

Field descriptions

The field definitions in your template explain what type of information is required for each field, and how to enter valid information. It's always a good idea to read the field definitions before making entries.

You can reorder the columns of your CSV file for ease of use. However, the column header must contain the field name exactly as it appears in the original template.

If you downloaded a template from the Company Setup Checklist or an object list page, your template contains the headers and dimensions that are specific to your company. The headers in a standard template might not contain field definitions specific to your company.

To import dimension values, enter information in the appropriate dimension column of the import spreadsheet. Otherwise, no information appears for that dimension.

If you relabeled any dimensions (see Terminology for more information), your dimension name does not appear in the CSV template, but the original Intacct dimension name does.

Field Name: DONOTIMPORT

#

Any row that starts with # is ignored during import.

Field Name: TRANSACTIONTYPE

Field Name:

TYPE

UI Field Name:

Type

Type:

Character

Length:

30

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid template name

Required:

Yes

Editable:

No

Note:

The transaction type field refers to the name of the transaction definition template. In this instance, transaction type is the same as transaction definition template name.

You can view a list of transaction definition template names by going to Purchasing > Setup > Transaction definitions.

Field Name: DATE

Field Name:

DATE

UI Field Name:

Date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

Yes

Editable:

No

Field Name: GLPOSTINGDATE

Field Name:

GLPOSTINGDATE

UI Field Name:

GL Posting Date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

Yes, if you have enabled override of GL posting date during entry on the Configure Accounts Payable page.

Editable:

Yes

Field Name: DOCUMENTNO

Field Name:

DOCUMENTNO

UI Field Name:

Document Number

Type:

Alphanumeric

Length:

45

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

None

Required:

Yes, if you don't have auto-numbering enabled in your transaction definition

Editable

No

Field Name: VENDOR_ID

Field Name:

VENDOR_ID

UI Field Name:

Supplier

Type:

Alphanumeric

Length:

21

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid supplier

Required:

Yes

Editable:

No

Field Name: TERMNAME

Field Name:

TERMNAME

UI Field Name:

Payment Terms

Type:

Alphanumeric

Length:

40

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Must already exist

Required:

No

Editable:

No

Field Name: DATEDUE

Field Name:

DATEDUE

UI Field Name:

Date Due

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

Yes

Editable:

Yes

Field Name: REFERENCENO

Field Name:

REFERENCENO

UI Field Name:

Reference Number

Type:

Alphanumeric

Length:

100

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

None

Required:

No

Editable:

Yes

Field Name: MESSAGE

Field Name:

MESSAGE

UI Field Name:

Message

Type:

Alphanumeric

Length:

1000

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

None

Required:

No

Editable:

No

Field Name: SHIPPINGMETHOD

Field Name:

SHIPPINGMETHOD

UI Field Name:

Shipping method

Type:

Character

Length:

40

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid shipping method.

Required:

No

Editable:

Yes

Field Name: PAYTO

Field Name:

PAYTO

UI Field Name:

Pay to

Type:

Character

Length:

40

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid Pay to.

Required:

No

Editable:

Yes

Field Name: RETURNTO

UI Field Name:

Return to

Type:

Character

Length:

40

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid Return to.

Required:

No

Editable:

Yes

Field Name: DELIVERTO

UI Field Name:

Deliver to

Type:

Character

Length:

40

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid Deliver to.

Required:

No

Editable:

Yes

Field Name: CURRENCY

Field Name:

CURRENCY

UI Field Name:

Currency

Type:

Character

Length:

3

Default Value:

Base Currency

Valid Values:

Any defined currency, such as USD or EUR. Blank denotes base currency.

Dependencies:

Must reference a previously defined currency

Required:

No

Editable:

Yes

Notes:

Use only in multi-currency companies. This field defines the transaction currency. If no field is defined here, the base currency is used.

Field Name: BASECURR

Field Name:

BASECURR

UI Field Name:

Base Currency

Type:

Character

Length:

3

Default Value:

None

Valid Values:

Any defined, three-letter ISO-4127 currency code, such as USD or EUR

Dependencies:

Must reference a previously-defined currency. Locations in line items must use the same base currency.

Required:

No, except for shared multi-entity companies with multiple base currencies.

Editable:

No

Notes:

Applies only to shared multi-entity companies with multiple base currencies. This field defines the transaction base currency. Verify that locations in line items use the same base currency.

Field Name: EXCHRATEDATE

Field Name:

EXCHRATEDATE

UI Field Name:

Exchange Rate Date

Type:

Date

Length:

10

Default Value:

Today

Valid Values:

Any valid date format

Dependencies:

None

Required:

Yes, unless you provide the EXCHANGE_RATE

Editable:

Yes

Notes:

Use only in multi-currency companies. This field determines the exchange rate as of this date.

Field Name: EXCHRATETYPE

Field Name:

EXCHRATETYPE

UI Field Name:

Exchange Rate Type

Type:

Character

Length:

40

Default Value:

Intacct Daily Rate, unless a custom exchange rate is defined as the default

Valid Values:

Alphanumeric and underscore

Dependencies:

Must reference a previously-defined exchange rate type

Required:

No

Editable:

Yes

Notes:

Use only in multi-currency companies. Defines an optional custom exchange rate type. If no rate is defined here, the Intacct Daily Rate is used.

Field Name: EXCHRATE

Field Name:

EXCHRATE

UI Field Name:

Exchange Rate

Type:

Number

Length:

17, not including decimal point

Default Value:

Defaults to the exchange rate of the CURRENCY on the EXCH_RATE_DATE for the EXCH_RATE_TYPE

Valid Values:

Positive integers

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Use only in multi-currency companies. Overrides the default exchange rate, which is the product of the CURRENCY, EXCH_RATE_DATE, and EXCH_RATE_TYPE.

Field Name: STATE

Field Name:

STATE

UI Field Name:

Transaction Status

Type:

Character

Length:

 

Default Value:

Draft

Valid Values:

Draft, Submitted, Pending, and Closed

Dependencies:

None

Required:

Yes

Editable:

Yes

Field Name: NEEDBYDATE

Field Name:

NEEDBYDATE

UI Field Name:

Need by date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name: DONOTSHIPBEFOREDATE

Field Name:

DONOTSHIPBEFOREDATE

UI Field Name:

Do not ship before date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name: DONOTSHIPAFTERDATE

Field Name:

DONOTSHIPAFTERDATE

UI Field Name:

Do not ship after date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name: PROMISEDDATE

Field Name:

PROMISEDDATE

UI Field Name:

Promised by date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name: CONTRACTSTARTDATE

Field Name:

CONTRACTSTARTDATE

UI Field Name:

Contract start date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name: CONTRACTENDDATE

Field Name:

CONTRACTENDDATE

UI Field Name:

Contract end date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name: CANCLEAFTERDATE

Field Name:

CANCLEAFTERDATE

UI Field Name:

Cancel after date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name: LINE

Field Name:

LINE

UI Field Name:

 

Type:

Number

Length:

 

Default Value:

None

Valid Values:

Number

Dependencies:

None

Required:

Yes

Editable:

No

Field Name: ITEMID

Field Name:

ITEM_ID

UI Field Name:

Item ID

Type:

Character

Length:

30

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid item ID

Required:

Yes

Editable:

Yes

Field Name: ITEMDESC

Field Name:

ITEMDESC

UI Field Name:

Item Description

Type:

Character

Length:

100

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

None

Required:

No

Editable:

Yes

Field Name: ITEMALIASID

Field Name:

ITEMALIASID

UI Field Name:

Cross-reference item ID

Type:

Character

Length:

30

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Refers to a valid cross-reference item ID

Required:

No

Editable:

Yes

Field Name: WAREHOUSEID

Field Name:

WAREHOUSEID

UI Field Name:

Warehouse

Type:

Character

Length:

30

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

Must refer to a valid warehouse

Required:

Yes, if the item type is Inventory or Stockable Kit

Editable:

Yes

Field Name: QUANTITY

Field Name:

QUANTITY

UI Field Name:

Quantity

Type:

Numeric

Length:

8

Default Value:

None

Valid Values:

Integer

Dependencies:

None

Required:

Yes

Editable:

Yes

Notes You can't have a negative quantity if the Item type = Inventory, Kit, or Stockable kit.
Field Name: UNIT

Field Name:

UNIT

UI Field Name:

Unit

Type:

Character

Length:

N/A

Default Value:

Count

Valid Values:

Count, Length, Time, Volume, Weight, etc.

Dependencies:

Valid unit

Required:

Yes

Editable:

Yes

Field Name: PRICE

Field Name:

PRICE

UI Field Name:

Price

Type:

Numeric

Length:

10,2

Default Value:

0

Valid Values:

Decimal

Dependencies:

None

Required:

No

Editable:

Yes

Field Name:ENTRY_DELIVERTO

Field Name:

ENTRY_DELIVERTO

UI Field Name:

Deliver to

Type:

Character

Length:

N/A

Default Value:

None

Valid Values:

Alphanumeric and underscore

Dependencies:

None

Required:

No

Editable:

Yes

Field Name:TAXABLE

Field Name:

TAXABLE

UI Field Name:

Taxable

Type:

Character

Length:

N/A

Default Value:

Derived from ITEM

Valid Values:

T or F (for true or false respectively)

Dependencies:

None

Required:

No

Editable:

Yes

Field Name:DEPARTMENTID

Field Name:

DEPARTMENTID

UI Field Name:

Department

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

None

Required:

No

Editable:

No

Field Name:LOCATIONID

Field Name:

LOCATIONID

UI Field Name:

Location

Type:

Character

Length:

20

Default Value:

None

Valid Values:

An existing valid location

Dependencies:

None, except in shared multi-entity companies with multiple base currencies; the LOCATION_ID must use the same currency as the BASECURR field.

Required:

No

Editable:

Yes, if the transaction is not partially or fully paid, or partially or fully converted.

Notes:

In shared multi-entity companies with multiple base currencies, LOCATION_ID must be in an entity that uses the same base currency as BASECURR.

Field name:PODOCUMENTENTRY_CLASSID

Field Name:

PODOCUMENTENTRY_CLASSID

UI Field Name:

Class

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid class

Required:

No

Editable:

No

Note:Used on the line item.
Field name:PODOCUMENTENTRY_PROJECTID

Field Name:

PODOCUMENTENTRY_PROJECTID

UI Field Name:

Project

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid project

Required:

No

Editable

No

Note:Used on the line item.
Field Name:PODOCUMENTENTRY_CUSTOMERID

Field Name:

PODOCUMENTENTRY_CUSTOMERID

UI Field Name:

Customer

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid customer

Required:

No

Editable

No

Note:Used on the line item.
Field Name:PODOCUMENTENTRY_EMPLOYEEID

Field Name:

PODOCUMENTENTRY_EMPLOYEEID

UI Field Name:

Employee

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid employee

Required:

No

Editable

No

Note:Used on the line item.
Field Name:PODOCUMENTENTRY_VENDORID

Field Name:

PODOCUMENTENTRY_VENDORID

UI Field Name:

Supplier

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid supplier

Required:

No

Editable:

No

Note:Used on the line item.
Field Name:SUB_LINE_NO

Field Name:

SUB_LINE_NO

UI Field Name:

 

Type:

Number

Length:

 

Default Value:

None

Valid Values:

Number

Dependencies:

None

Required:

Yes, if you have subtotals for your transaction

Editable:

Yes

Note:Usually subtotals are auto-calculated.
Field Name:SUBDESC

Field Name:

SUBDESC

UI Field Name:

Description

Type:

Alphanumeric and underscore

Note:

Must match the description available in your subtotals

Field Name:ABSVAL

Field Name:

ABSVAL

UI Field Name:

Transaction Value

Type:

Numeric

Length:

10,2

Default Value:

0

Valid Values:

Decimal

Dependencies:

None

Required:

No

Editable:

Yes

Field Name:PERCENTVAL

Field Name:

PERCENTVAL

UI Field Name:

Percent

Type:

Character

Length:

3.2

Default Value:

None

Valid Values:

Numbers

Dependencies:

None

Required:

No

Editable:

Yes

Field Name:SUBLOCATIONID

Field Name:

SUBLOCATIONID

UI Field Name:

Location

Type:

Character

Length:

20

Default Value:

None

Valid Values:

An existing valid location

Dependencies:

None, except in shared multi-entity companies with multiple base currencies, the LOCATION_ID must use the same currency as the BASECURR field

Required:

No

Editable

Yes, if the AP supplier invoice is not partially or fully paid

Notes:

In shared multi-entity companies with multiple base currencies, LOCATION_ID must be in an entity that uses the same base currency as BASECURR

Field name:SUBDEPARTMENTID

Field Name:

SUBDEPARTMENTID

UI Field Name:

Department

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

None

Required:

No

Editable

No

Field name:PODOCUMENTSUBTOTALS_CLASSID

Field Name:

PODOCUMENTSUBTOTALS_CLASSID

UI Field Name:

Class

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid class

Required:

No

Editable:

No

Notes:

Used to designate the Class ID on a purchase order.

Field name:PODOCUMENTSUBTOTALS_PROJECTID

Field Name:

PODOCUMENTSUBTOTALS_PROJECTID

UI Field Name:

Project

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid project

Required:

No

Editable

No

Notes:

Used to designate the Project ID on a purchase order.

Field Name:PODOCUMENTSUBTOTALS_CUSTOMERID

Field Name:

PODOCUMENTSUBTOTALS_CUSTOMERID

UI Field Name:

Customer

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid customer

Required:

No

Editable

No

Notes:

Used to designate the Customer ID on a purchase order.

Field Name:PODOCUMENTSUBTOTALS_EMPLOYEEID

Field Name:

PODOCUMENTSUBTOTALS_EMPLOYEEID

UI Field Name:

Employee

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid employee

Required:

No

Editable

No

Notes:

Used to designate the Employee ID on a purchase order.

Field Name:PODOCUMENTSUBTOTALS_VENDORID

Field Name:

PODOCUMENTSUBTOTALS_VENDORID

UI Field Name:

Supplier

Type:

Alphanumeric

Length:

20

Default Value:

None

Valid Values:

Alphanumeric

Dependencies:

Refers to a valid supplier

Required:

No

Editable:

No

Notes:

Used to designate the Supplier ID on a purchase order.

Field Name:VENDORDOCNO

UI Field Name:

Supplier Document Number

Type:

Character

Length:

20

Required:

No
Field Name:MEMO

UI Field Name:

Memo

Type:

Character

Length:

400

Required:

No
Field Name:DISCOUNT_MEMO

UI Field Name:

Notes

Type:

Character

Length:

4000

Required:

No
Field Name:FORM1099

UI Field Name:

Form 1099

Type:

Character

Default Value:

F

Valid Values:

T (True), F (False)

Required:

No
Field Name:BILLABLE

UI Field Name:

Billable

Type:

Character

Default Value:

F

Valid Values:

T (True), F (False)

Required:

No
Field Name:OVERRIDETAXAMOUNT

UI Field Name:

Tax override (only for Avalara tax)

Type:

Character

Default Value:

false

Valid Values:

true, false

Required:

No

Notes:

This field is only applicable for Avalara AvaTax.
Field Name:TAX

UI Field Name:

Transaction tax (Transaction Line Tax)

Type:

Currency

Length:

40

Valid Values:

Digits 0-9

Required:

No

Notes:

This field is only applicable for Avalara AvaTax and when OVERRIDETAXAMOUNT is true. However, the field is currently ignored.
Field Name:TRACK_QUANTITY

Field Name:

TRACK_QUANTITY
Required:Yes, if Items have lots.
Notes:

Lot tracking can have multiple units in a given lot. Use the TRACK_QUANTITY column to define the quantity.

For example: The total quantity of the line is 10 units, but 6 units are in LOTNO Apple and 4 units are in LOTNO Banana. The 6 and 4 are defined in the TRACK_QUANTITY field.

Field Name:SERIALNO

Field Name:

SERIALNO
Required:Yes, if you are importing an Item that is serialized.
Notes:If you are importing an Item that is serialized, then the serial number columns should be populated. There can only be one unit per Serial Number.
Field Name:AISLEID

Field Name:

AISLEID
Required:No
Dependencies:Must be part of a valid Warehouse.
Notes:Used to designate an aisle.
Field Name:ROWID

Field Name:

ROWID
Required:No
Dependencies:Must be part of a valid Warehouse.
Notes:Used to designate a row.
Field Name:BINID

Field Name:

BINID
Required:No
Dependencies:Must be part of a valid Warehouse.
Notes:Used to designate a bin.
Field Name:LOTNO

Field Name:

LOTNO
Required:No
Notes: Lot tracking can have multiple units in a given lot. The units are defined as the quantity in TRACK_QUANTITY.
Field Name:EXPIRATION

Field Name:

EXPIRATION
Required:No
Notes:Used to designate the expiration date of the item.
Field Name:PODOCUMENTSUBTOTALS_ITEMID

Field Name:

PODOCUMENTSUBTOTALS_ITEMID

Required:

No
Notes:Used to designate an Item ID on a PO.
Field Name:PODOCUMENTENTRY_NEEDBYDATE

Field Name:

PODOCUMENTENTRY_NEEDBYDATE

UI Field Name:

Need by date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name:PODOCUMENTENTRY_DONOTSHIPBEFOREDATE

Field Name:

PODOCUMENTENTRY_DONOTSHIPBEFOREDATE

UI Field Name:

Do not ship before date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name:PODOCUMENTENTRY_DONOTSHIPAFTERDATE

Field Name:

PODOCUMENTENTRY_DONOTSHIPAFTERDATE

UI Field Name:

Do not ship after date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name:PODOCUMENTENTRY_PROMISEDDATE

Field Name:

PODOCUMENTENTRY_PROMISEDDATE

UI Field Name:

Promised by date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name:PODOCUMENTENTRY_DATECONFIRMED

Field Name:

PODOCUMENTENTRY_DATECONFIRMED

UI Field Name:

Date confirmed

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name:PODOCUMENTENTRY_CANCLEAFTERDATE

Field Name:

PODOCUMENTENTRY_CANCLEAFTERDATE

UI Field Name:

Cancel after date

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name:PODOCUMENTENTRY_DATESHIPTOSUPPLIER

Field Name:

PODOCUMENTENTRY_DATESHIPTOSUPPLIER

UI Field Name:

Date shipped to supplier

Type:

Date

Length:

 

Default Value:

None

Valid Values:

Date

Dependencies:

None

Required:

No

Editable:

Yes

Notes:

Applicable only if 'Enable shipping dates in Purchasing and Order Entry' is set to true on the Configure Inventory Control page.

Field Name: NAMEOFACQUIREDASSET
UI Field Name:Name of acquired asset
Type:Character
Length:100
Default Value:None
Valid Values:Any
Dependencies:None
Required:No
Editable:No
Field Name: SELECTEDASSETMODE

UI Field Name:

Asset creation

Type:

Character

Length:

1

Default Value:

S

Valid Values:

S, M, N (S = Create fixed asset, M = Create multiple fixed assets, N = Do not create asset)

Dependencies:

None

Required:

No

Editable:

No

Field Name: ASSETQUANTITY

UI Field Name:

Number of assets

Type:

Number

Length:

10

Default Value:

None

Valid Values:

Digits 0-9

Dependencies:

None

Required:

No

Editable:

No

Field Name: INCLUDETAXINASSETCOST - This field only applies to companies subscribed to the Taxes application.
UI Field Name:Include tax in asset cost
Type:Character
Max Length:5
Default Value:F
Valid valuesT, F (T = True, F = False)
Dependencies:None
Required:No
Editable:No
Field Name: TAXSOLUTIONID - This field only applies to companies subscribed to the Taxes application.
UI Field Name:Tax solution
Type:Character
Length:100
Default Value:None
Valid Values:Alphanumeric and underscore
Dependencies:None
Required:Yes, if your organization is configured for multiple tax jurisdictions and you are importing at the top level
Editable:No