Skip to content

ASN

Zynk will import ASN data into Mintsoft based on the settings provided at the task level and the data provided in your input file.

To configure the import data to meet your specific requirements, you can use the step-by-step guide for the available fields below.

Tasks

Example

<?xml version="1.0" encoding="utf-8"?>
<ASNs xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
  <ASN>
    <MatchClientOn>Name</MatchClientOn>
    <Client>
        <Name>Hikari</Name>
    </Client>
    <MatchWarehouseOn>Name</MatchWarehouseOn>
    <Warehouse>
        <Name>Site 1</Name>
    </Warehouse>
    <PurchaseOrderReference>EXAMPLE01</PurchaseOrderReference>
    <ProductSupplierID>74</ProductSupplierID>
    <EstimatedDelivery>2023-03-30T00:00:00</EstimatedDelivery>
    <GoodsInType>Carton</GoodsInType>
    <Quantity>100</Quantity>
    <ASNStatusID>1</ASNStatusID>
    <Shipped>false</Shipped>
    <HoursLogged>0</HoursLogged>
    <Quantity>100</Quantity>
    <Items>
      <Item>
        <SKU>10006 00 06 00060</SKU>
        <Quantity>100</Quantity>
      </Item>
    </Items>
  </ASN>
</ASNs>

Field List

ExternalID

Optional
This field is applied in order to uniquely identify records using the identifier from the source system.

When the record is imported successfully, Zynk will store the record in the truth table. The truth table record contains an 'Internal' and 'External' ID. The 'Internal' ID refers to the identifier assigned automatically by Mintsoft.

This field is also used in conjunction with the 'Prevent Reprocessing' task setting. If this setting is set to true and a record with the same ExternalID has been previously imported, the record will be skipped and logged to the fail file.

Type Example XML
string(255) 1 <ExternalID>1</ExternalID>
PurchaseOrderReference

Optional
Optionally give the ASN a reference to a purchase order.

Type Example XML
string EXAMPLE01 <PurchaseOrderReference>EXAMPLE01</PurchaseOrderReference>
EstimatedDelivery

Optional
The estimated delivery date of the shipment.

Type Example XML
long 2023-03-30T00:00:00 <EstimatedDelivery>2023-03-30T00:00:00</EstimatedDelivery>
Comments

Optional Any notes provided by the supplier in relation to the shipment.

Type Example XML
string Leave by the back door. <Comments>Leave by the back door.</Comments>
GoodsInType

Required
The packaging used for the goods in the shipment. This must match a 'goods in' type from Mintsoft.

Type Example XML
string Carton <GoodsInType>Carton</GoodsInType>
Quantity

Required
The total overall quantity of items expected in the shipment.

Type Example XML
int 100 <Quantity>100</Quantity>

Supplier

MatchProductSupplierOn

Optional

You can match the supplier to the ASN using one of the following options:

  • ID Default When this option is given, you must provide the product supplier ID value at the header level.
  • Code When this option is given, you must provide the code value at the <ProductSupplier> level.
  • Name When this option is given, you must provide the name value at the <ProductSupplier> level.

Please note, when a value is not provided, the matching logic defaults to ID and the task will expect a ProductSupplierID to be provided at the header level.

ProductSupplierID

Optional
When the MatchProductSupplierOn is set to ID or is not provided, use this field to set the supplier ID. 

<ProductSupplierID>74</ProductSupplierID>

This must match a supplier ID from Mintsoft.

Product Supplier → Code

Optional
When the MatchProductSupplierOn is set to Code, use this field to set the supplier code. 

<MatchProductSupplierOn>Name</MatchProductSupplierOn>
<ProductSupplier>
    <Name>SUPP0001</Name>
</ProductSupplier>

This must match a supplier code from Mintsoft.

Product Supplier → Name

Optional
When the MatchProductSupplierOn is set to Name, use this field to set the supplier name. 

<MatchProductSupplierOn>Name</MatchProductSupplierOn>
<ProductSupplier>
    <Name>Example Supplier 1</Name>
</ProductSupplier>

This must match a supplier name from Mintsoft.

Client

MatchClientOn

Optional

You can match the client to the record using one of the following options:

  • ID Default When this option is given, you must provide the client ID value at the header level.
  • Code When this option is given, you must provide the code value at the <Client> level.
  • Name When this option is given, you must provide the name value at the <Client> level.
  • ShortName When this option is given, you must provide th short name value at the <Client> level.

Please note, when a value is not provided, the matching logic defaults to ID and the task will expect a ClientID to be provided at the header level.

ClientID

Optional
When the MatchClientOn is set to ID or is not provided, use this field to set the client ID. 

<ClientID>1</ClientID>

This must match a client ID from Mintsoft.

Client → Code

Optional
When the MatchClientOn is set to Code, use this field to set the supplier code. 

<MatchClientOn>Code</MatchClientOn>
<Client>
    <Code>CLIE0001</Code>
</Client>

This must match a client code from Mintsoft.

Client → Name

Optional
When the MatchClientOn is set to Name, use this field to set the client name. 

<MatchClientOn>Name</MatchClientOn>
<Client>
    <Name>Client Example 1</Name>
</Client>

This must match a client name from Mintsoft.

Client → ShortName

Optional
When the MatchClientOn is set to ShortName, use this field to set the client short name. 

<MatchClientOn>ShortName</MatchClientOn>
<Client>
    <ShortName>Client 1</ShortName>
</Client>

This must match a client short name from Mintsoft.

Warehouse

MatchWarehouseOn

Optional

You can match the warehouse to the record using one of the following options:

  • ID Default When this option is given, you must provide the warehouse ID value at the header level.
  • Code When this option is given, you must provide the code value at the <Warehouse> level.
  • Name When this option is given, you must provide the name value at the <Warehouse> level.

Please note, when a value is not provided, the matching logic defaults to ID and the task will expect a WarehouseID to be provided at the header level.

WarehouseID

Optional
When the MatchWarehouseOn is set to ID or is not provided, use this field to set the warehouse ID. 

<WarehouseID>3</WarehouseID>

This must match a warehouse ID from Mintsoft.

Warehouse → Code

Optional
When the MatchWarehouseOn is set to Code, use this field to set the warehouse code. 

<MatchWarehouseOn>Warehouse</MatchWarehouseOn>
<Warehouse>
    <Code>WARE0001</Code>
</Warehouse>

This must match a warehouse code from Mintsoft.

Warehouse → Name

Optional
When the MatchWarehouseOn is set to Name, use this field to set the warehouse name.

<MatchWarehouseOn>Name</MatchWarehouseOn>
<Warehouse>
    <Name>Warehouse Example 1</Name>
</Warehouse>

This must match a warehouse name from Mintsoft.

Items

ProductID

Optional
You can optionally provide the related product ID. This will link the item to a corresponding product in Mintsoft.

Please note, that for each item either a ProductID or SKU value must be provided.

Type Example XML
long 1 <ProductID>1</ProductID>

The given value must match a product ID from Mintsoft.

SKU

Optional
You can optionally provide the related product SKU. This will link the item to a corresponding product in Mintsoft.

Please note, that for each item either a ProductID or SKU value must be provided.

Type Example XML
string 10006 00 06 00060 <SKU>10006 00 06 00060</SKU>

The given value must match a product SKU from Mintsoft.

Quantity

Required
You must provide the quantity expected to be received on the ASN item.

Type Example XML
int 100 <Quantity>100</Quantity>
SourceLineID

Optional
You can provide an identifier from the external system for the ASN item.

Type Example XML
string 1 <SourceLineID>1</SourceLineID>
SSCCNumber

Optional
The Serial Shipping Container Code for the ASN item.

Type Example XML
int 100 <SSCCNumber>000000000000000001</SSCCNumber>