Stock Transfer from WMS managed warehouses

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

This document describes what happens after the mapper is installed: how a SAP Business One (B1) Stock Transfer Request becomes a WMS OutgoingDocument for picking toward another (often external / non-picking) warehouse, which fields are mapped, and which business rules apply. It is intended for end-users and functional consultants.

1. Overview

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

• Document identity and base type (typically TransferRequest)

• A synthetic business partner representing the destination (to) warehouse

• Pick date, handling mode, status

• Lines to pick from the from warehouse, with destination stored on the line

• Flag targetIsExternal based on whether the destination warehouse is picking-enabled in B1

• Correlation id for tracking

Fixed / default values

2. What the mapper uses as input

2.1 Main payload — B1 stock transfer document

Typical fields used:

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

• Lines StockTransferLines[]:

  • LineNum, ItemCode, Quantity

  • FromWarehouseCode (pick from)

  • WarehouseCode (destination to)

  • LineStatus, UoMEntry, UoMCode, MeasureUnit

  • Optional dynamic line property (name/value); name U_se_winkel is used for line details

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

2.2 Warehouse master (automatic, hourly)

Loaded from B1:

• WarehouseCode

• U_AEN_WHS_Picking (Y / N)

• (also retrieved: DefaultBin, EnableBinLocations)

Business impact: destination warehouse picking flag drives WMS customFields.targetIsExternal (Y/N). Downstream flows (e.g. goods delivery) may use this flag to choose B1 stock transfer vs WMS incoming paths.

2.3 Correlation id

Integration message key → correlation.correlationId.

3. Business behavior

3.1 Direction of warehouses (critical)

This is the opposite partner convention of the “external → WMS incoming” mapper (which uses from-warehouse as BP). Here the outgoing document is oriented as: pick in from-WH, deliver toward to-WH.

3.2 Business partner = to warehouse

Example: first line to warehouse 04 → BP id 04, name To Warehouse 04.

B1 CardCode / CardName are not used for these BP fields.

3.3 Base type

data.baseType comes from B1 DocObjectCode:

Stock transfer requests typically use 1250000001 → TransferRequest.

3.4 Target is external (targetIsExternal)

data.customFields.targetIsExternal is set to Y or N by looking up the destination warehouse (line WarehouseCode) in the warehouse master and reading U_AEN_WHS_Picking:

(Implementation uses if-else / equal against warehouse codes and picking flags, with constants Y/N.)

Consultant meaning: if the to warehouse is not a normal Aiden picking warehouse, the target is flagged external so other integrations know how to complete the move (e.g. post B1 stock transfer vs create WMS incoming).

3.5 Status

3.6 Unit of measure

For each line:

1. If UoMEntry is not -1 → use UoMCode

2. If UoMEntry is -1 → use "m" + MeasureUnit (missing measure → empty → often just m)

3.7 Dates and handling

3.8 Line details (U_se_winkel)

If a line dynamic property has name U_se_winkel, its value is mapped to lines[].details.

This is hard-coded in the mapping (not a free config property in this project).

3.9 Address

data.address.addressId is constant Transfer (no full ship-to address block from B1 in this map).

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 (to warehouse)

4.4 Lines (data.lines[])

5. Value translations (reference)

5.1 Doc object code → baseType

5.2 Status (lines)

5.3 Constants

6. What is not mapped / caveats

7. Example (from mapping sample)

B1 input (excerpt)

Warehouse master (excerpt)

Expected WMS shape (from mapping rules)

8. End-to-end expectation

1. B1 creates a stock transfer request from an internal picking warehouse to another (often external) warehouse.

2. Document is published to Kafka.

3. Integration loads warehouse picking flags and maps to WMS OutgoingDocument.

4. WMS picks from from warehouse; destination is carried as to-warehouse / external flag.

5. Downstream confirmation flows use objectType / targetIsExternal as designed.

6. Trace with correlation id, DocNum, and DocEntry.

9. Implementation checklist for consultants

1. Use DocObjectCode 1250000001 for STRs so baseType = TransferRequest.

2. Set U_AEN_WHS_Picking correctly: destination non-picking warehouses should yield targetIsExternal = Y.

3. Train users: WMS pick warehouse = from; partner/to-warehouse = to.

4. Maintain UoM; know -1 → m + measure unit fallback.

5. If shop/line text is needed, fill B1 line property U_se_winkel.

6. Do not confuse this project with stocktransfer-external-wms (IncomingDocument / from-warehouse BP).

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 warehouse rules 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.