LookupTable

Optional 

LookupTable is the name of a user-defined custom database table that stores additional order information. Certain data items can be populated with information in this table. The table must have a “Route” column that is used as the unique identifier to match against data from the imported data file. The remaining columns in the table can be named by the user, and may only be used for certain order fields during processing. To populate fields from the data columns, the value specified for the data item should be “Col” followed by the database column name (see example for Driver below). The data items that can be populated with information from the lookup table are: CustID, Driver, OriginAddress, OriginComments, OrderType, ReadyTimeFrom, ReadyTimeTo

Example

KeyNode

Required when LookupTable is specified 

The node used for KeyNode must not contain data that is more than 8 characters long.  The KeyNode specifies the node from the imported file which will be used to match the “Route” column in the lookup table.  If the KeyNode value for an order within the data file does not match a record in the lookup table, the order will not be imported. 

Example

EncryptedPassword

Required 

Specifies whether the internet user's password has been encrypted. Most of the time, this should be set to true. 

Example

Password

Required 

Password for the internet user used for placing orders. 

Example

UserID

Required

Internet user to use for placing the orders. 

Example

CustID

Required

Customer ID used to place the order.

Example

OrderPK

Required 

The OrderPK is used to identify unique orders during import.  It can be used to group rows together (when each row of data in the ASN file contains a different parcel) into the a single order. 

Only one column value is permitted when using tab delimited files (e.g. OrderPK=3 where column 3 is the Store Number). Multiple concatenated columns are allowed for csv (e.g. OrderPK=3,4,5 where columns 3,4,5 are address, city, state) 

Data: OrderPK is not stored in the database nor displayed on the Order form. It is only used by X Import for processing.

OrderNodePK

Optional 

Used to associate multiple records together for XML in an XINI document. Set this value to an element within the Order node that contains a unique value. 

Data: OrderNodePK is not stored in the database nor displayed on the Order form. It is only used by X Import for processing.

AutoPlaceOrder

Optional 

Used to specify if the import should skip the step of receiving an OrderResponse, choosing an order type, and submitting an OrderSelectedRequest with the chosen order type.

If true, you must include an OrderType or the import will fail. Setting to true will roughly double performance as well since it will skip trying to rate all available order types for that customer’s rate chart as well as an additional post/response in the import process.

To let X Import pick the cheapest available order type for the order, set this to false and set OrderType=0,0. This will tell X Import to choose the cheapest order type in the OrderResponse and use it in the OrderSelectedResponse. 

Example

BillingGroup

Optional 

Billing group to use on the resulting orders.

Data: BillingGroup is saved to the database in tblOrder to the CustomerBillingGroup column. Displayed on the main Order form as Billing Group/Cost Center.

BillOfLading

Optional 

Bills of Lading (BOL) are used to aggregate orders. This allows you to execute status actions on groups of orders instead of individually.

Example

Data: BillOfLading is saved to the database in tblOrder to the BOL column. Displayed on the Order form on the Parcels tab as Order BOL.

ConsolidationText

Optional 

Any string can be used to set the consolidation text. Intended to consolidate on demand orders. When used for on demand imports, the import plugin will consolidate the order and not duplicate the parcels with the same barcode.

If OrderA imports with a consolidation string in the database of “ABC 3/30/2020”, and OrderB imports with the same consolidation string, the Parcels from OrderB will be placed on OrderA. OrderB will not be imported as a separate order.

Data: ConsolidationText is saved to the database in tblOrder_Consolidated in the ConsolidationText column. This includes the date, as the consolidation text will try to lookup anything that matches within the last 30 days. This is not displayed on the Order form. 

Required 

Date by which the resulting orders should be delivered.

Data: DeliverDate is stored in the database in tblOrder as DueTimeTo. Displayed on the Order form under Delivery in the To: Field.

DestAddressBarcode

Optional. Supported only in XINI.

This value can be set to the Location Barcode specified for a given address. The address must be associated with the given customer (cannot be a global address). If you use this value, the system will look up the address that has this location barcode value and use that address as the destination address.

Data: The data that is in this field is matched to the column Barcode in tblAddressPoints. This is the Lookup Barcode on the Details tab of the Address form. Whatever is matched here is then used as the DestAddress. 

DestAddress

Required 

The address of the destination location.

Data: DestAddress is stored in tblOrder in the DestAddress column. Displayed as the Address field in the Destination address on the Order form.

DestCity

Required 

The city of the destination location.

Data: DestCity is stored in tblOrder in the DestCity column. Displayed as the City field in the Destination address on the Order form.

DestComments

Optional 

Comments on the destination location. (e.g., "Mailroom")

Data: DestComments is stored in tblOrder in the DestComments column. Displayed as the Remarks field in the Destination section of the Order form.

DestContactPhone

Optional 

Phone number of the contact person at the destination location.

Data: DestContactPhone is stored in tblOrder in the DestPhone column. Displayed on the Order form as Phone under the Destination section.

DestName

Required 

Name of the destination location.

Data: DestName is stored in tblOrder in the DestName column. Displayed on the Order form as Name under the Destination section.

DestPlus4

Optional 

The postal code extension of the destination location.

Data: DestPlus4 is stored in tblOrder in the DestPlus4 column. Displayed on the Order form as part of the address under the Destination section.

DestState

Required 

The state or province of the destination location.

Data: DestState is stored in tblOrder in the DestState column. Displayed on the Order form as part of the address under the Destination section.

DestSuite

Optional 

The suite of the destination location.

Data: DestSuite is stored in tblOrder in the DestAddress2 column. Displayed on the Order form as part of the address under the Destination section.

DestZip

Required 

The postal code of the destination location.

Data: DestZip is stored in tblOrder in the DestZip column. Displayed on the Order form as part of the address under the Destination section.

Driver

Optional 

The Driver ID of the driver to assign to the imported on demand order. 

Example

Data: Driver is stored in tblOrderDrivers in the DriverID column, linked to the Order with the OrderID. Displayed on the Order form on the Drivers tab.

Geocode

Optional 

Determines whether addresses are geocoded/validated (latitude & longitude determined). 

Example

Data: This is not stored in the database or displayed in the Operations App, it simply decides whether to validate the address at import or not. 

ValidationFailOver

Optional

Returns minimum specified value when the address does not precisely validate.

Valid types:

1. LatLonMin - Returns new lat/long coordinates only. (keeps old address.) 

   The geocode bit needs to be turned on for the LatLonMin ValidationFailOver process to return lat/lon coordinates.

   rsMaster|GeoCode=0,1

2. AddressMin - Returns new address only. (keeps old lat/long data.)

Required

Date and time by which this order should be picked up. 

Data: PickupDate is stored in tblOrder in ReadyTimeFrom. Displayed on the Order form as Pickup From time. 

OriginAddressBarcode

Optional. Only supported in XINI.

This value can be set to the Location Barcode specified for a given address. The address must be associated with the given customer (cannot be a global address). If used, the system will look up the address that has this location barcode value and use that address as the origin address. 

Data: The OriginAddressBarcode value that is passed in is not stored but rather is used to match from the Address Point and then populate the various address fields in tblOrder (OriginName, OriginAddress, OriginAddress2, OriginCity, OriginState, and OriginZip).

OriginAddress

Required 

The address of the origin location.

Data: The OriginAddress is stored in tblOrder in the OriginAddress column. Displayed as a part of the Origin Address on the Order form.

OriginCity

Required 

The city of the origin location.

Data: The OriginCity is stored in tblOrder in the OriginCity column. Displayed as a part of the Origin Address on the Order form.

OriginComments

Optional 

Comments on the origin location.

Data: OriginComments are stored in tblOrder in the OriginComments column. Displayed on the Order form as Origin Remarks.

OriginContactPhone

Optional 

Phone number of the contact person at the origin location.

Data: OriginContactPhone is stored in tblOrder in the OriginPhone column. Displayed on the Order form as Phone under the Origin Address.

OriginName

Required 

Name of the origin location.

Data: The OriginName is stored in tblOrder in the OriginName column. Displayed as a part of the Origin Address on the Order form.

OriginPlus4

Optional 

The postal code extension of the origin location.

Data: The OriginPlus4 is stored in tblOrder in the OriginPlus4 column. Displayed as a part of the Origin Address on the Order form.

OriginState

Required 

The state of the origin location.

Data: The OriginState is stored in tblOrder in the OriginState column. Displayed as a part of the Origin Address on the Order form.

OriginSuite

Optional 

The suite of the origin location

Data: The OriginSuite is stored in tblOrder in the OriginAddress2 column. Displayed as a part of the Origin Address on the Order form.

OriginZip

Required

The postal code of the origin location.

Data: The OriginZip is stored in tblOrder in the OriginZip column. Displayed as a part of the Origin Address on the Order form

Optional 

Determines if a confirmation e-mail should be sent to the e-mail address specified on the order. (see also: EmailPOD)

Data: EmailOrderConfirmationChecked is stored in tblOrder in the column EmailOrderConfirmationChecked as a bit (1 for true, 0 for false). Displayed on the Order form under the Email address as the Placed checkbox.

Optional 

The e-mail address associated with the order. The specified e-mail address will receive status messages when events occur on this order. (see also: EmailOrderConfirmationChecked, EmailPODChecked, EmailPOPChecked)

Data: EmailPOD is stored in tblOrder in the column EmailPod. Displayed on the Order form as Email / Fax Alerts.

Optional 

Determines if a Proof of Delivery e-mail should be sent to the address specified in EmailPOD when the order is delivered.

Data: EmailOrderConfirmationChecked is stored in tblOrder in the column EmailPODChecked as a bit (1 for true, 0 for false). Displayed on the Order form under the Email address as the Delivered checkbox.

Optional 

Determines if a Proof of Pickup e-mail should be sent to the address specified in EmailPOD when the order is picked up.

Data: EmailOrderConfirmationChecked is stored in tblOrder in the column EmailPOPChecked as a bit (1 for true, 0 for false). Displayed on the Order form under the Email address as the Picked up checkbox.

Reference1

Optional 

User-defined reference field 1.

Data: Reference1 is stored in tblOrder in the column Reference1. Displayed on the Order form as Reference1.

Reference2

Optional

User-defined reference field 2.

Data: Reference2 is stored in tblOrder in the column Reference1. Displayed on the Order form as Reference2.

OrderType

Required 

The numeric OrderTypeID to use for placing orders. 

Data: OrderType is stored in tblOrder in the OrderType column, using the OrderTypeID. Displayed on the Order form, using the OrderType Description, in the Order Type field. 

ServiceType

Optional 

Specifies the text for the Orders Comments field.

Data: SpecialInst is stored in tblOrder in the SpecialInst column. Displayed on the Order form as Order Comments.

ParcelPieces

Optional 

The number of parcels on this order. 

If parcels are also included in the import file, the order's parcel pieces will match the total number of imported parcels.

Data: ParcelPieces is stored in tblOrder in the Pieces column. Displayed on the Order weightform as Pieces under Parcel Info.

ParcelWeight

Optional 

The total weight of all parcels assigned to this order. 

Data: ParcelWeight is stored in tblOrder in the column Weight. Displayed on the Order form as Weight under Parcel Info.

OverrideDeliveryTimeFrom

Optional 

Specifies a "from" value in the order delivery window to force regardless of the rules in the order type. 

Delimited, OverrideDeliveryTimeFrom=PARSEDATE(TODAY;;yyyy-MM-dd 17:00:00.000)
This will give today’s date 17:00, 2020-03-07 17:00 

Example

OverrideDeliveryTimeTo

Optional 

Specifies a "to" value in the order delivery window to force regardless of the rules in the order type.

Example

OverrideReadyTimeFrom

Optional 

Specifies a "from" value in the order pickup window to force regardless of the rules in the order type. 

Example

OverrideReadyTimeTo

Optional 

Specifies a "to" value in the order pickup window to force regardless of the rules in the order type. 

Example

OrderLength

Length used in dimensional weight calculator.

Data: ParcelLength stored in tblOrder. It is displayed on the dimensional weight calculator on the order form as Length.

OrderWidth

Width used in dimensional weight calculator.

Data: ParcelWidth stored in tblOrder. It is displayed on the dimensional weight calculator on the order form as Width.

OrderHeight

Height used in dimensional weight calculator.

Data: ParcelHeight stored in tblOrder. It is displayed on the dimensional weight calculator on the order form as Height.

OrderDimWtDenominator

Dimensional weight denominator.

Data: DimWtDenominator is stored in tblOrder as DimWtDenominator. It is displayed on the dimensional weight calculator on the order form as Denominator.

UseCalculatedDimensionalWeight

A flag if the Length, Width, and Height values are set to tell the import to calculate the Dimensional Weight.

DimWtDenominator

Parcel level dimensional weight denominator.

Data: ParcelNodeDimWtDenominator is stored in tblParcel as DimWtDenominator.

MasterBillOfLading

Optional 

Master Bills of Lading aggregate Bills of Lading.

Ref

Required to import parcels 

Parcel reference.

Data: Ref is stored in tblParcel as Reference. Displayed on the Parcels tab of the Order form as Reference for the parcel. This is also the parcel barcode.

Pieces

Required to import parcels 

Number of Parcel Pieces on the Parcel Import

Data: Stored in tblOrder as Pieces. Displayed on the General tab of the Order form as Pieces.

Length

Required to import parcels 

Parcel length.

Data: Length is stored in tblParcel as ParcelLength. It is displayed on the Parcels tab of the Order form under the Dims button

Width

Required to import parcels 

Parcel width.

Data: Width is stored in tblParcel as ParcelWidth. Displayed on the Parcels tab of the Order form under the Dims button.

Height

Required to import parcels 

Parcel height. 

Data: Height is stored in tblParcel as ParcelHeight. Displayed on the Parcels tab of the Order form under the Dims button.

Weight

Required to import parcels

Parcel weight.

Data: Weight is stored in tblParcel as Weight. It is displayed on the Parcels tab of the Order form as Weight.

ParcelId

Optional 

Parcel ID.

Data: ParcelId is stored in tblParcel as CustomerParcelID. Displayed on the Parcels tab of the Order form as CustomerParcelID.

MasterParcelId

Optional 

Master parcel id. This functions exactly like the routed MasterParcelBarcode. If this value is scanned as a barcode, it will mark all parcels with the same value as scanned.

Data: MasterParcelID is stored in tblParcel as CustomerMasterParcelID. Displayed on the Parcels tab of the Order form as CustomerMasterParcelID.

CustomerReference1

Optional 

Parcel customer reference 1.

Data: CustomerReference1 is stored in tblParcel as CustomerReference1. Displayed on the Parcels tab of the Order form as CustomerReference1.

CustomerReference2

Optional 

Parcel customer reference 2.

Data: CustomerReference2 is stored in tblParcel as CustomerReference2. Displayed on the Parcels tab of the Order form as CustomerReference2.

Comment

Optional 

Parcel comment.

Data: Comment is stored in tblParcel as Comment. Displayed on the Parcels tab of the Order form as Comment.

ParcelType

Optional 

Parcel type.

Data: ParcelType is stored in tblParcel as Type (as an tinyint - the ParcelTypeID from tblParcelTypes). The description for the ParcelType is displayed on the Parcels tab of the Order form as Parcel Type (drop-down list).

ParcelNodeRef

Required to import XML parcels 

Parcel reference (barcode). Used instead of Ref for XML parcel imports

Data: ParcelNodeRef is stored in tblParcel as Reference. It is displayed on the Parcels tab of the Order form as Reference for the parcel. This is the parcel barcode as well.

ParcelNodeLength

Required to import XML parcels

Parcel dimensional length. Used instead of Length for XML parcel imports Note: Must be an X Path expression that evaluates to a node set. Literals (0,1) do not work for this field. Can be set to a nonexistent node (/this/does/not/exist).

Data: ParcelNodeLength is stored in tblParcel as ParcelLength. Displayed on the Parcels tab of the Order form under the Dims button.

ParcelNodeWidth

Optional 

Parcel dimensional width. Used instead of Width for XML parcel imports.

Data: ParcelNodeWidth is stored in tblParcel as ParcelWidth. Displayed on the Parcels tab of the Order form under the Dims button.

ParcelNodeHeight

Optional 

Parcel dimensional height. Used instead of Height for XML parcel imports.

Data: ParcelNodeHeight is stored in tblParcel as ParcelHeight. Displayed on the Parcels tab of the Order form under the Dims button.

ParcelNodeWeight

Optional

Parcel weight. Used instead of Weight for XML parcel imports.

Data: ParcelNodeWeight is stored in tblParcel as Weight. Displayed on the Parcels tab of the Order form as Weight.

ParcelNodeParcelID

Optional 

Parcel ID. Used instead of ParcelID for XML parcel imports. 

Data: ParcelNodeParcelID is stored in tblParcel as CustomerParcelID. Displayed on the Parcels tab of the Order form as CustomerParcelID.

ParcelNodeMasterParcelID

Optional 

Master parcel ID. Used instead of MasterParcelID for XML parcel imports. This functions exactly like the routed MasterParcelBarcode. If this value is scanned as a barcode, it will mark all parcels with the same value as scanned.

Data: ParcelNodeMasterParcelID is stored in tblParcel as CustomerMasterParcelID. Displayed on the Parcels tab of the Order form as CustomerMasterParcelID.

ParcelNodeCustomerReference1

Optional

Parcel customer reference 1. Used instead of CustomerReference1 for XML parcel imports.

Data: ParcelNodeCustomerReference1 is stored in tblParcel as CustomerReference1. Displayed on the Parcels tab of the Order form as CustomerReference1.

ParcelNodeCustomerReference2

Optional

Parcel customer reference 1. Used instead of CustomerReference2 for XML parcel imports.

Data: ParcelNodeCustomerReference2 is stored in tblParcel as CustomerReference2. Displayed on the Parcels tab of the Order form as CustomerReference2.

ParcelNodeComment

Optional 

Parcel comment. Used instead of Comment for XML parcel imports.

Data: ParcelNodeComment is stored in tblParcel as Comment. Displayed on the Parcels tab of the Order form as Comment.

ParcelNodeParcelType

Optional

Parcel type. Used instead of ParcelType for XML parcel imports.

Data: ParcelNodeParcelType is stored in tblParcel as Type (as an tinyint - the ParcelTypeID from tblParcelTypes). The description for the ParcelType is displayed on the Parcels tab of the Order form as Parcel Type (drop-down list).

ForceLocationScanPickup

Optional

When to require force location scanning at the order's pickup address.

• 0 - None (Default setting)

• 1 - Upon Arrival

• 2 - Upon Departure

• 3 - Both

ForceLocationScanDelivery

Optional

When to require force location scanning at the order's delivery address.

• 0 - None (Default setting)

• 1 - Upon Arrival

• 2 - Upon Departure

• 3 - Both

Example

UserField0

Optional 

User field.

Data: UserField(0-12) is stored in tblOrderUserData in the UserData(0-12) columns. It is displayed on the Order form on the User Fields tab as User Field (0-12) by default. (The customer may have renamed these fields; see the general Options under Order for the name if so.)

UserField1

Optional 

User field.

Data: UserField(0-12) is stored in tblOrderUserData in the UserData(0-12) columns. It is displayed on the Order form on the User Fields tab as User Field (0-12) by default. (The customer may have renamed these fields; see the general Options under Order for the name if so.)

UserField2

Optional 

User field.

Data: UserField(0-12) is stored in tblOrderUserData in the UserData(0-12) columns. It is displayed on the Order form on the User Fields tab as User Field (0-12) by default. (The customer may have renamed these fields; see the general Options under Order for the name if so.)

UserField3

Optional 

User field.

Data: UserField(0-12) is stored in tblOrderUserData in the UserData(0-12) columns. It is displayed on the Order form on the User Fields tab as User Field (0-12) by default. (The customer may have renamed these fields; see the general Options under Order for the name if so.)

UserField4

Optional 

User field.

Data: UserField(0-12) is stored in tblOrderUserData in the UserData(0-12) columns. It is displayed on the Order form on the User Fields tab as User Field (0-12) by default. (The customer may have renamed these fields; see the general Options under Order for the name if so.)

UserField5

Optional 

User field.

Data: UserField(0-12) is stored in tblOrderUserData in the UserData(0-12) columns. It is displayed on the Order form on the User Fields tab as User Field (0-12) by default. (The customer may have renamed these fields; see the general Options under Order for the name if so.)

UserField6

Optional 

User field.

Data: UserField(0-12) is stored in tblOrderUserData in the UserData(0-12) columns. It is displayed on the Order form on the User Fields tab as User Field (0-12) by default. (The customer may have renamed these fields; see the general Options under Order for the name if so.)

UserField7

Optional 

User field.

Data: UserField(0-12) is stored in tblOrderUserData in the UserData(0-12) columns. It is displayed on the Order form on the User Fields tab as User Field (0-12) by default. (The customer may have renamed these fields; see the general Options under Order for the name if so.)

UserField8

Optional 

User field.

Data: UserField(0-12) is stored in tblOrderUserData in the UserData(0-12) columns. It is displayed on the Order form on the User Fields tab as User Field (0-12) by default. (The customer may have renamed these fields; see the general Options under Order for the name if so.)

UserField9

Optional 

User field.

Data: UserField(0-12) is stored in tblOrderUserData in the UserData(0-12) columns. It is displayed on the Order form on the User Fields tab as User Field (0-12) by default. (The customer may have renamed these fields; see the general Options under Order for the name if so.)

UserField10

Optional 

User field.

Data: UserField(0-12) is stored in tblOrderUserData in the UserData(0-12) columns. It is displayed on the Order form on the User Fields tab as User Field (0-12) by default. (The customer may have renamed these fields; see the general Options under Order for the name if so.)

UserField11

Optional 

User field.

Data: UserField(0-12) is stored in tblOrderUserData in the UserData(0-12) columns. It is displayed on the Order form on the User Fields tab as User Field (0-12) by default. (The customer may have renamed these fields; see the general Options under Order for the name if so.)

UserField12

Optional 

User field.

Data: UserField(0-12) is stored in tblOrderUserData in the UserData(0-12) columns. It is displayed on the Order form on the User Fields tab as User Field (0-12) by default. (The customer may have renamed these fields; see the general Options under Order for the name if so.)

Accessorial1ID

Optional 

Used if you wish to add an accessorial Item onto the imported order. It represents the numerical ItemID of the accessorial item you wish to add to the imported order. If you specify an ItemID here, you must specify a quantity for the item in Accessorial1Quantity as well. 

Example

Accessorial1Quantity

Optional

Used in conjunction with Accessorial1ID to specify the quantity for the item in imported on demand order. If you specify a quantity here, you must specify an ItemID for the item in Accessorial1ID. 

Example

Accessorial2ID

Optional 

Used to add additional accessorial items beyond the first. The usage is the same as for Accessorial1ID. 

Example

Accessorial2Quantity

Optional 

Used to add additional quantities for accessorial items beyond the first. The usage is the same as for Accessorial1Quantity. 

Example

Accessorial3ID

Optional 

Used to add additional accessorial items beyond the first. The usage is the same as for Accessorial1ID. 

Example

Accessorial3Quantity

Optional 

Used to add additional quantities for accessorial items beyond the first. The usage is the same as for Accessorial1Quantity.

Example

Accessorial4ID

Optional 

Used to add additional accessorial items beyond the first. The usage is the same as for Accessorial1ID. 

Example

Accessorial4Quantity

Optional 

Used to add additional quantities for accessorial items beyond the first. The usage is the same as for Accessorial1Quantity.

Example

Accessorial5ID

Optional 

Used to add additional accessorial items beyond the first. The usage is the same as for Accessorial1ID. 

Example

Accessorial5Quantity

Optional 

Used to add additional quantities for accessorial items beyond the first. The usage is the same as for Accessorial1Quantity. 

Example

Accessorial6ID

Optional 

Used to add additional accessorial items beyond the first. The usage is the same as for Accessorial1ID. 

Example

Accessorial6Quantity

Optional 

Used to add additional quantities for accessorial items beyond the first. The usage is the same as for Accessorial1Quantity. 

Example

Accessorial7ID

Optional 

Used to add additional accessorial items beyond the first. The usage is the same as for Accessorial1ID.

Example

Accessorial7Quantity

Optional 

Used to add additional quantities for accessorial items beyond the first. The usage is the same as for Accessorial1Quantity.

Example

Accessorial8ID

Optional 

Used to add additional accessorial items beyond the first. The usage is the same as for Accessorial1ID. 

Example

Accessorial8Quantity

Optional 

Used to add additional quantities for accessorial items beyond the first. The usage is the same as for Accessorial1Quantity. 

Example

Accessorial9ID

Optional 

Used to add additional accessorial items beyond the first. The usage is the same as for Accessorial1ID. 

Example

Accessorial9Quantity

Optional 

Used to add additional quantities for accessorial items beyond the first. The usage is the same as for Accessorial1Quantity. 

Example

Accessorial10ID

Optional 

Used to add additional accessorial items beyond the first. The usage is the same as for Accessorial1ID. 

Example

Accessorial10Quantity

Optional 

Used to add additional quantities for accessorial items beyond the first. The usage is the same as for Accessorial1Quantity. 

Example