Item Master Data Integration

Item master data is owned and maintained in ERPs like Microsoft Dynamics 365 Business Central or Perfion.
It is possible to change item data directly in Axacon WMS, but those changes are not sent back to Business Central or Perfion.
Data ownership
ERP is the source of truth for item master data. Changes made directly in Axacon WMS should therefore be treated with caution.

Item data models and fields

Required integration sequence

Create item-related data in the following order:

1. Create the ItemGroup.
2. Create the Item.
3. Create the StockKeepingUnit.
4. Update the Item with the value for PrimarySKU.

Why the order matters
Each record must exist before another record can reference it. For example, the
stock-keeping unit must exist before it can be assigned as the item’s primary SKU.

Create an item

The following request creates an item using the default Work Context configured for the integration user.

POST https://[SERVER]/integration/rest/V1/Item
Content-Type: application/json

{
  "Id": "Item6",
  "ItemName": "Fiddle Violinfigen",
  "NetWeight": 7.7,
  "CustomsTariffCode": "6702100000",
  "CountryOfOrigin": "CN",
  "ItemGroupId": "KUNSTIGEPLANTER"
}

Work Context
If no owner, company, or warehouse is specified in the request, Axacon WMS uses
the default Work Context configured for the login user.

Create a section with owner and warehouse in the URL

The owner and warehouse can be specified directly in the request URL.

POST https://[SERVER]/integration/rest/V1/Section?warehouse=Terminal2&owner=auto

{
  "Id": "Section1"
}

Retrieve item data

Get one item

GET https://[SERVER]/integration/rest/V1/Item/Item6

Get all items using a finder

GET https://[SERVER]/integration/rest/V1/Item?finder=findAll

Find stock for a specific item

POST https://[SERVER]/integration/rest/V1/executeFinderInfo/Stock/findByItem
Content-Type: application/json

{
  "0": "Item6"
}

Execute an item command

Block an item

POST https://[SERVER]/integration/rest/V1/executeCommandInfo/BlockItems
Content-Type: application/json

{
  "0": "Item6"
}

Delete an item

DELETE https://[SERVER]/integration/rest/V1/Item/Item6

Use caution
Before deleting an item, make sure it is not referenced by active orders, stock,
or other warehouse records.

Complete item integration example

1. Create the item group

POST https://[SERVER]/integration/rest/V1/ItemGroup

{
  "Id": "789987",
  "Name": "Toys"
}

2. Create the item

POST https://[SERVER]/integration/rest/V1/Item

{
  "Id": "4711",
  "ItemName": "4711-Name"
}

3. Create the stock-keeping unit

POST https://[SERVER]/integration/rest/V1/StockKeepingUnit

{
  "Id": "SKU4711",
  "ItemId": "4711",
  "PackId": "PIECES",
  "Qty": "1",
  "GlobalTradeItemNumber": "65465467"
}

4. Assign the primary SKU to the item

PUT https://[SERVER]/integration/rest/V1/Item

{
  "Id": "4711",
  "PrimarySKU": "SKU4711"
}

Integration file cleanup

Axacon WMS stores integration requests and responses in the database.
Required maintenance
Configure the DeleteIntegrationFilesBefore command to remove old
integration files and prevent unnecessary database growth.

Implementation checklist

• Confirm that the integration user has the correct Work Context.
• Create item groups before items that reference them.
• Create stock-keeping units before assigning PrimarySKU.
• Verify that referenced packs and item groups already exist.
• Use the correct owner and warehouse context.
• Configure integration-file cleanup.