Stock Transfer to WMS managed warehouse

Functional documentation for the Aiden WMS stock transfer external mapper (outbound).

This document describes what happens after the mapper is installed: how a SAP Business One (B1) stock transfer / stock transfer request becomes a WMS IncomingDocument for external warehouse receiving, which fields are mapped, and which business rules apply. It is intended for end-users and functional consultants.

1. Overview

After installation, when a relevant B1 stock transfer document is published, the mapper produces a WMS document with:

• Document identity and base type TransferRequest

• A synthetic “business partner” representing the from warehouse

• Receive date from the B1 due date

• Lines for items to receive at the to warehouse

• Status and object-type translations

• Correlation id for tracking

Fixed business defaults

2. What the mapper uses as input

2.1 Main payload — B1 stock transfer document

Typical B1 fields used:

• Header: DocNum, DocEntry, DueDate, DocumentStatus, DocObjectCode, FromWarehouse, ToWarehouse, …

• Lines StockTransferLines[]:

  • LineNum, ItemCode, Quantity

  • WarehouseCode (to warehouse on the line)

  • FromWarehouseCode (from warehouse on the line)

  • LineStatus, UoMEntry, UoMCode, MeasureUnit

  • Optional dynamic line properties (name/value) for configurable line details

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

2.2 Correlation id

Integration message key → correlation.correlationId.

2.3 Optional line detail configuration

Java property:

• line.detail.fieldname (default NOT_SET if not configured)

When a stock transfer line carries a dynamic property whose name equals this configured value, that property’s value is written to WMS lines[].details.

If the property is not present or the config does not match, line details are not filled from that mechanism.

No separate warehouse timer or item enrichment runs in this project.

3. Business behavior

3.1 Business partner = from warehouse (important)

Unlike a purchase order mapper, the WMS business partner is not taken from CardCode / CardName for the main BP fields used here.

Example: first line FromWarehouseCode = 01 → BP id 01, name From Warehouse 01.

This presents the sending warehouse as the “partner” on the WMS incoming document for external receiving.

3.2 Line warehouse = destination (to)

WMS lines[].warehouseId comes from the line WarehouseCode (to warehouse), i.e. where goods should be received in the destination context—not the from warehouse.

3.3 Document and line status

B1 statuses look like bost_Open / bost_Close.

3.4 Object type

customFields.objectType is derived from B1 DocObjectCode:

Stock transfer requests in B1 commonly use object code 1250000001 → WMS StockTransferRequests.

3.5 Unit of measure (uomCode)

For each line:

1. If UoMEntry is not -1 → use UoMCode

2. If UoMEntry is -1 → use "m" + MeasureUnit

   • Missing MeasureUnit is substituted with empty → result can be just m

Sample data often has UoMEntry = -1, UoMCode = Handmatig, MeasureUnit = null → WMS uomCode ≈ m.

3.6 Dates

3.7 Quantity

WMS line quantity ← B1 line Quantity (as on the stock transfer line).

4. Field mapping tables

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

4.1 Correlation

4.2 Document header (data)

4.3 Business partner (from warehouse)

4.4 Lines (data.lines[])

5. Value translations (reference)

5.1 Status

5.2 Doc object code → objectType

5.3 Constants

6. What is not mapped / caveats

7. Example (from mapping sample input)

B1 input (excerpt)

Expected WMS shape (from mapping rules)

Published with endpoint header IncomingDocument.

8. End-to-end expectation

1. B1 creates/updates a stock transfer request (or related document) for an external warehouse flow.

2. Document is published to Kafka.

3. Mapper builds a WMS IncomingDocument: transfer-request base type, from-warehouse as BP, to-warehouse on lines.

4. Message is sent to WMS for receiving.

5. Trace with correlation id, DocNum, and customFields.externalId (DocEntry).

9. Implementation checklist for consultants

1. Confirm B1 documents use the expected DocObjectCode (e.g. 1250000001 for STR → StockTransferRequests).

2. Understand WMS BP is the from warehouse, not the B1 card.

3. Understand WMS line warehouse is the to warehouse.

4. Maintain UoM entries; know the -1 / manual fallback (m + measure unit).

5. If line remarks/details are required in WMS, configure line.detail.fieldname to the B1 line property name used in the payload.

6. Align external warehouse processes with baseType = TransferRequest.

7. Trace with correlation id + DocEntry/DocNum.

10. Source artifacts

Generated from the mapping definition and integration routes in this project. If the MapForce mapping or configuration properties change, 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.