Goods delivery

Functional documentation for the Aiden WMS goods delivery mapper (inbound).

This document describes what happens after the mapper is installed: how a WMS goods movement message is routed, which SAP Business One (B1) or WMS documents are created, and which field rules apply. It is intended for end-users and functional consultants.

1. Overview

One inbound message can become different document types depending on documents[0].customFields.objectType (and, for stock transfers, whether the target warehouse is external).

High-level outcomes

2. Message routing

Routing key: documents[0].customFields.objectType.

Configure objectType and (for transfers) targetIsExternal correctly on the WMS message. Wrong values send the document down the wrong path or skip it.

3. Shared behavior (all flows)

3.1 Correlation and tracking

3.2 Serial number check (before document mapping)

For every picked/saved unit that carries a serial, the integration:

1. Builds an item + serial list from the WMS message (Get item and serial helper mapper).

2. Looks up B1 SerialNumberDetails for that ItemCode + SerialNumber.

3. If not found:

   • Looks for an empty serial slot on that item (SerialNumber and MfrSerialNo null).

   • PATCHes the WMS serial onto that slot (SerialNumber and MfrSerialNo).

4. If no empty slot exists → processing stops with a known error: serial not available for the item.

Saved lines without a serial skip the B1 lookup. If one serial check fails, remaining serial checks for the message are not continued (hard stop for the whole message).

Consultant impact: serials must exist (or empty serial masters must be available) in B1 before confirmation. Missing serial masters cause a hard failure, not a partial document.

3.3 Sales order enrichment (Orders only)

Before the delivery-note mapping:

• Collects customFields.externalId from each WMS document (B1 order DocEntry).

• GETs B1 Orders (DocEntry, DocNum, DocumentLines).

• Uses order lines for base-line matching, UoM / units-of-measurement enrichment on packages, etc.

3.4 Warehouse master

Loaded from B1 on a timer (every 3600 seconds from startup):

• WarehouseCode, DefaultBin, EnableBinLocations, U_AEN_WHS_Picking

Main functional use in this project: stock transfer bin allocations when the line warehouse has bin locations enabled and a default bin. (U_AEN_WHS_Picking is loaded with the master; bin allocation is the confirmed consumer in this mapper.)

3.5 Delivery note output sorting

Delivery note JSON is normalized/sorted before it is sent to B1: DocumentLines ordered by VisualOrder.

4. Flow: Delivery notes (objectType = Orders)

4.1 Business behavior

Creates one or more SAP B1 Delivery Notes from a WMS delivery confirmation against sales order(s).

Important rules:

• Base document: order identified by customFields.externalId → B1 BaseEntry.

• Base type: from customFields.objectType via valuemap:

  • Orders → 17

  • StockTransferRequests → 1250000001

• Lines are aggregated from WMS savedLines (picked quantities), joined back to order/document lines for item, UoM, sales BOM, etc.

• Intermediate saved-line paths: batch (batchNumber filled), serial (serialNumber filled), or plain (both empty).

• Batches: when savedLines.batchNumber is filled, B1 batch lines are created (batch no., expiry, qty from baseQuantity).

• Serials: when savedLines.serialNumber is filled, B1 serial lines are created (InternalSerialNumber, qty from savedLines.quantity).

• Packages / SSCC: savedLines.licenseId + carrier drive DocumentPackages / DocumentPackageItems (U_AEN_WMS_Track = license, Type = carrier).

• Header & line additional expenses are copied/grouped into B1 expense structures with base doc references; line expenses set BaseGroup from GroupCode.

• Special lines from WMS line custom fields are carried into B1 DocumentSpecialLines for the fields listed below.

• Sales BOM attributes on WMS lines (parent, parentLine, singleQuantity, respectSingleQuantity) are available in the intermediate line enrichment used by the mapping.

4.2 Field mapping — Delivery Note header

Comments is present on the B1 output schema but is not confirmed as filled from WMS in the current mapping.

4.3 Field mapping — Delivery Note lines

4.4 Field mapping — Header additional expenses

4.5 Field mapping — Line additional expenses

4.6 Field mapping — Special lines

Other freight/amount fields may exist on the WMS special-line payload and intermediate structures; only the fields above are confirmed on the final delivery-note output.

4.7 Field mapping — Packages

4.8 Example (scenario 1_DeliveryNotesNoSerial)

5. Flow: Production issue (objectType = ProductionOrders)

5.1 Business behavior

Creates B1 Inventory Gen. Exit documents for production issues from WMS.

• Runs only if not all lines are backflush (productionOrderIssueType != im_Backflush on at least one line).

• Backflush lines are excluded from the issue document.

• Saved lines without a usable batch path are filtered in intermediate logic (empty batch handling / not-equal filters).

• Quantities aggregated per production order base line; batches and serials attached like other goods movements.

• Base type valuemap includes ProductionOrders → 202.

5.2 Field mapping — Inventory Gen. Exit

No CardCode, packages, expenses, or bin allocations in this flow.

6. Flow: Stock transfer external (objectType = StockTransferRequests and targetIsExternal = Y)

6.1 Business behavior

Creates a B1 Stock Transfer from a WMS stock transfer request when the target is marked external.

• Lines built from savedLines, joined to document lines for lineNum / warehouse.

• Serials included when present (empty serial filtered out of serial path).

• Batches included when present (batch quantity from baseQuantity; no batch expiry on this MFD).

• No DocDate on the stock-transfer output schema.

• Bin allocations: if the line’s warehouseId matches a B1 warehouse with EnableBinLocations = tYES and a DefaultBin, bin allocation rows are written (BinAbsEntry = default bin, quantity from line/batch/serial path).

6.2 Field mapping — Stock Transfer

7. Flow: WMS incoming document (internal stock transfer)

7.1 Business behavior

When objectType = StockTransferRequests and the target is not external, the mapper does not post a B1 stock transfer. It creates a WMS Incoming Document for the receiving warehouse process.

Observed constants / structure from the mapping:

• data.baseType = TransferRequest

• Business partner is derived from the source warehouse (not the WMS BP master): id = source lines.warehouseId; name = 'From warehouse ' + source warehouse id

• details is a direct copy of WMS documents.details (no “From warehouse” prefix on details)

• Lines aggregated from saved lines (item, qty, UoM); line warehouse = lines.customFields.toWarehouse

• Batch/serial info blocks built from savedLines when batch or serial is non-empty (batch number, qty, expiry; serial numbers)

• Correlation id from the integration Kafka message key / XIAM message id

• Owner copied when present on the WMS document

7.2 Field mapping — Incoming document (summary)

Published to to.kafka.warehouse with endpoint IncomingDocument.

8. Flow: Purchase document (objectType = PurchaseOrders)

8.1 Business behavior

Maps the WMS confirmation into a purchase-document payload shape (not a B1 Delivery/GRPO in this route).

• Header/BP/dates/details largely copied from the WMS documents block.

• Lines grouped by saved line document line; quantity summed.

• Item, warehouse, UoM, details joined from order lines by documentLine.

• Serials exposed as dynamic properties:

  • Collection name: serialNumbers

  • Element name: serialNumber

• No batches in this MFD.

• Header/line additional expenses renamed into purchase-doc expense field names (expenseCode, expenseLine, expenseLineTotal, expenseGroupCode, expenseDistributioMethod [spelling as in MFD], expenseVatGroup, …).

• customFields.objectType on output is set to constant StockTransferRequests in the MapForce mapping (verify against your WMS purchase-doc expectations if this looks unexpected functionally).

• Publish target: warehouse Kafka topic with HTTP endpoint header IncomingDocument (same endpoint name as internal stock-transfer incoming; payload remains the purchase mapper output).

8.2 Field mapping — Purchase document

Published to to.kafka.warehouse with endpoint IncomingDocument.

9. Supporting mapper: Get item and serial

Not a business document. Builds the working list used for B1 serial validation (one output row per savedLines entry):

10. Value translations (reference)

10.1 Object type → B1 base type

Valuemaps differ slightly per mapper (input key is documents[].customFields.objectType):

10.2 Production issue type

10.3 Stock transfer external flag

10.4 Warehouse bins (stock transfer)

11. What is not done / failure & skip cases

12. End-to-end happy path (sales order delivery)

1. WMS completes picking/packing for a sales order and publishes a goods message (objectType = Orders).

2. Integration validates/registers serials in B1 as needed.

3. Integration loads the B1 order line structure.

4. Delivery Notes mapper builds B1 DN JSON (lines, batches, serials, packages, expenses).

5. JSON is sorted by VisualOrder and posted to B1 as DeliveryNotes.

6. U_AEN_WMS_TRANSID and correlation ids support support/troubleshooting.

13. Implementation checklist for consultants

1. objectType on WMS documents must match one of: Orders, ProductionOrders, StockTransferRequests, PurchaseOrders.

2. For stock transfers, set targetIsExternal correctly (Y = post B1 transfer; otherwise WMS incoming).

3. customFields.externalId must be the B1 base document key (order / production order / STR DocEntry as applicable).

4. Maintain serial number masters (or empty serial slots) in B1 for serialized items.

5. For deliveries with packages, ensure licenseId and carrier are filled on saved lines if SSCC/packages are required in B1.

6. For production issues, set productionOrderIssueType so backflush lines are not double-issued.

7. For bin-managed warehouses used in external transfers, set DefaultBin and EnableBinLocations in B1.

8. Use transaction.id / U_AEN_WMS_TRANSID for tracing.

14. Source artifacts

Generated from the mapping definitions and integration routes in this project. If MapForce mappings or routing 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.