Item

Functional documentation for the Aiden WMS item mapper (outbound).

This document describes what happens after the mapper is installed: how a SAP Business One (B1) item is turned into an Aiden WMS item master, which master data is required, and which field rules apply. It is intended for end-users and functional consultants.

1. Overview

After installation, when an item is published from B1, the mapper produces a WMS item document with:

• Item code and name

• Item group name (resolved from B1 group number)

• Batch / serial / inventory / enabled flags

• Base unit of measure

• One or more units (UoM code, name, factor, barcodes, dimensions)

Fixed / technical defaults

2. What the mapper uses as input

2.1 Main payload — B1 item

One Kafka message = one B1 item document, including for example:

• Identity: ItemCode, ItemName, ItemsGroupCode

• Flags: InventoryItem, ManageBatchNumbers, ManageSerialNumbers, ManageSerialNumbersOnReleaseOnly, Frozen

• UoM: InventoryUoMEntry, InventoryUOM, UoMGroupEntry, SalesUnit, SalesItemsPerUnit, PurchaseUnit, PurchaseItemsPerUnit

• Collections: ItemUnitOfMeasurementCollection (weights/lengths/volumes per UoM), ItemBarCodeCollection

ItemCode is also used as the integration external application id for monitoring.

2.2 Master data loaded automatically (hourly)

Before items are processed, the integration loads from B1 and keeps in memory:

Consultant impact: UoM definitions, UoM groups, item groups, and measure units must be correct in B1. Wrong masters → wrong WMS unit codes, factors, or dimensions. After deploy/restart, wait until the first configuration cycle finishes (consumer starts only then).

2.3 Correlation id

Integration message key → correlation.correlationId for end-to-end tracing.

3. Business behavior

3.1 Item group name

WMS data.itemGroup is not the numeric B1 group code.

• Lookup: ItemsGroupCode equals item group Number

• Result: corresponding GroupName (e.g. 100 → Artikel)

3.2 Boolean flags

isSerial logic:

1. Evaluate ManageSerialNumbersOnReleaseOnly as boolean (tYES→true, else false).

2. If true (serial only on release): use ManageSerialNumbers mapped the same way (tYES→true, else false).

3. If false: WMS isSerial is forced to false.

So “serial on release only” without treating the item as a full serial item in the main flag can yield isSerial = false while serialOnOutbound = true when release-only is tYES.

Frozen items: Frozen = tYES → isEnabled = false in WMS (item not enabled for warehouse use).

3.3 Base UoM (baseUomCode)

Resolved primarily from the inventory UoM:

• Prefer B1 UoM master Code for InventoryUoMEntry when a matching UnitOfMeasurements.AbsEntry exists.

• Fallbacks involve InventoryUOM text, manual/-1 UoM entry cases, and optional m + name style codes when the structured UoM path is incomplete.

Scenario example: inventory UoM entry 1 → base code "1" (Pak).

3.4 Units array — two regimes

A) UoM group path (preferred when group data is available)

When the item has a usable UoMGroupEntry and matching Unit of Measurement Group definitions:

B) Fallback simple units (limited / no UoM group path)

When the structured group path does not yield units (count/empty checks in the mapping), the mapper can synthesize units from header fields:

Conditions avoid emitting duplicate/empty sales or purchase units when they match inventory or each other (not-equal / logical checks in MapForce).

For full multi-level packaging in WMS, maintain a proper UoM group and item UoM/barcode collections in B1. Relying only on sales/purchase unit strings is a fallback.

3.5 Dimensions (canonical WMS units)

Per unit, dimensions are normalized to:

Sources are the item’s ItemUnitOfMeasurementCollection (Weight1/Length1/Width1/Height1/Volume + their unit codes), joined to WeightMeasures / LengthMeasures by unit code.

Missing measures typically yield 0 (as in the scenario target for the base pack when no dimensions are maintained).

3.6 Barcodes

Barcodes are taken from ItemBarCodeCollection and attached to the unit whose UoM entry matches ItemBarCodeCollection.UoMEntry. Multiple barcodes per UoM are supported (array).

4. Field mapping tables

Legend columns: WMS output field | B1 / source input | What happens | Notes

4.1 Correlation

4.2 Item header (data)

4.3 Units (data.units[]) — UoM group path

4.4 Units — fallback path (no full UoM group expansion)

5. Value translations (reference)

6. What is not mapped / caveats

7. Example (scenario 1_Item_with_units_of_measure)

B1 input (excerpt)

WMS output (excerpt from 99_target.json)

8. End-to-end expectation

1. Integration starts and loads UoM, UoM groups, item groups, length/weight measures from B1.

2. Kafka item consumer starts.

3. B1 item change/publish arrives on from.kafka.

4. Mapper builds WMS item JSON (flags, group name, units, barcodes, dimensions).

5. Message is sent to to.kafka for WMS Items.

6. Use correlation.correlationId and ItemCode for support.

9. Implementation checklist for consultants

1. Maintain Item Groups, UoMs, UoM groups, and length/weight measures in B1 before go-live.

2. For multi-level packaging, assign a proper UoM group and item UoM/barcode rows—not only free-text sales units.

3. Understand Frozen → WMS disabled (isEnabled = false).

4. Align serial expectations with ManageSerialNumbers vs ManageSerialNumbersOnReleaseOnly (§3.2).

5. Fill item UoM dimensions in B1 if WMS needs weight/volume for logistics.

6. After restart, confirm configuration load completed before expecting item messages to flow.

7. Trace with correlation.correlationId and itemId (ItemCode).

10. Source artifacts

Generated from the mapping definition and integration behavior in this project. If the MapForce mapping or master-data load changes, update this document.

Maintaining this document

For the original documentation intent, when to update, source-of-truth checklist, and a ready-made refresh prompt, see README.md and the repository AGENTS.md.