Goods Receipt on WMS managed warehouse (ad-hoc)

Functional documentation for the Aiden WMS goods receipt → inventory inbound mapper.

This document describes what happens after the mapper is installed: which SAP Business One (B1) goods receipt / purchase delivery note data is sent to Aiden WMS, how values are translated, and which business rules apply. It is intended for end-users and functional consultants.

1. Overview

After installation, when a B1 goods receipt (purchase delivery note) is published to the integration, the mapper produces a WMS inventory inbound that contains:

• Fixed reason PDN (“Ad-Hoc Purchase Delivery Note”)

• Supplier identification (CardCode / CardName) and B1 DocNum

• One or more inventory lines derived from B1 document lines, expanded when serials or batches exist

• Warehouse, synthetic bin id, item, quantity, UoM, optional serial/batch/expiry

• Correlation id for tracking

Fixed business defaults

Runtime endpoint

After mapping, the Camel route sets the outbound endpoint header to:

• InventoryInbound

There is no warehouse master load and no BOM helper in this project (unlike sales order / sales return mappers).

2. What the mapper uses as input

2.1 Main payload — B1 goods receipt (Purchase Delivery Note)

The primary input is the full B1 document JSON (Service Layer entity), typically a purchase delivery note (oPurchaseDeliveryNotes), including for example:

• Header: DocNum, CardCode, CardName

• Lines: DocumentLines[] with ItemCode, Quantity, WarehouseCode, UoMEntry, UoMCode, MeasureUnit, UnitsOfMeasurment, FreeText

• Optional line children:

  • SerialNumbers[] (InternalSerialNumber, ItemCode, …)

  • BatchNumbers[] (BatchNumber, ExpiryDate, ItemCode, Quantity, …)

2.2 Correlation id

The message correlation id (integration message key / Kafka key) is passed into MapForce as parameter exchangeProperty and written to:

• correlation.correlationId

Use this to trace a WMS inventory inbound back to the integration message.

DocNum is also registered as the integration external application id (monitoring), separate from the mapped JSON body.

3. Business behavior

3.1 Why three kinds of WMS lines?

MapForce emits up to three parallel line expansions from each B1 document line context (clone objects on the output array). Practically:

A single B1 line can therefore result in multiple WMS lines if it carries serials and/or batches, in addition to the plain-line path when the batch-empty filter allows it.

Consultant impact: WMS may receive more lines than B1 line count. Serial-managed and batch-managed items expand into tracking-specific lines. Validate UoM factors (UnitsOfMeasurment) for batch quantities.

3.2 Document line numbering

WMS documentLine is not taken from B1 LineNum.

It is generated with MapForce auto-number, using start and step 1.

The same auto-number stream feeds plain, serial, and batch expansions, so line numbers are sequential across generated WMS lines (not necessarily aligned 1:1 with B1 LineNum).

3.3 Warehouse and bin

Example: warehouse 01 → bin id 01-ONT1.

There is no filter on picking-enabled warehouses in this mapper (all document lines participate in the mapping structure as defined).

3.4 Unit of measure (uomCode)

For each generated line (plain / serial / batch expansions share the same UoM logic from the parent B1 line):

1. If UoMEntry is not -1 → use UoMCode

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

   • Missing MeasureUnit is substituted with empty string before concat (result can be just m)

3.5 Plain item lines

• Filter: batch number path is null-substituted to empty string, then compared; valuemap keeps only compare result 0 (default false → line suppressed for other compare results).

• itemId ← B1 line ItemCode

• quantity ← B1 line Quantity

• No batchNumber, expiryDate, or serialNumber on this expansion

3.6 Serial lines

• Filter: B1 SerialNumbers.InternalSerialNumber is not null

• One WMS line per serial record

• itemId ← serial’s ItemCode (not necessarily re-read only from parent line)

• quantity ← constant 1

• serialNumber ← InternalSerialNumber (after missing → empty substitute on the serial path used for filters/output as wired)

• No batch/expiry on this expansion

3.7 Batch lines

• Filter: batch number is not null (after missing substitute on the batch value path)

• One WMS line per batch record

• itemId ← batch’s ItemCode

• quantity ← BatchNumbers.Quantity divided by line UnitsOfMeasurment

• batchNumber ← batch BatchNumber

• expiryDate ← batch ExpiryDate

• No serial on this expansion

If UnitsOfMeasurment is 0 or inconsistent, batch quantities in WMS will be wrong. Ensure B1 line UoM factors are correct for batch-managed items.

3.8 Line details

On all three expansions, WMS details is filled from the B1 line FreeText.

3.9 Header custom fields and reason

data.owner and data.details are not mapped.

4. Field mapping tables

Legend:

• WMS output field — path in the Aiden WMS inventory inbound document

• B1 / source input — field on the goods receipt or other source

• What happens — copy or transformation

• Notes — consultant-relevant remarks

4.1 Correlation

4.2 Header (data)

4.3 Shared line fields (all expansions)

4.4 Plain item expansion

4.5 Serial expansion

4.6 Batch expansion

5. Value translations and constants (reference)

5.1 Fixed constants

5.2 UoM rule

5.3 Batch-empty filter (plain lines)

5.4 Endpoint

6. What is not mapped / important omissions

Consultants should not expect the following from this mapper:

7. End-to-end expectation (happy path)

1. A Purchase Delivery Note / Goods Receipt PO is posted in SAP B1 and published to the integration.

2. Integration sets correlation from the Kafka key and external application id from DocNum.

3. Mapper builds a WMS inventory inbound:

   • Reason PDN / Ad-Hoc Purchase Delivery Note

   • Supplier + DocNum in custom fields

   • Lines expanded for plain / serial / batch cases

   • Bin ids as warehouse-ONT1

4. Message is published with endpoint InventoryInbound.

5. WMS books ad-hoc inbound inventory accordingly.

8. Example (illustrative)

Based on mappings/inputExample.json (Purchase Delivery Note) and confirmed MapForce rules.
Scenario files under scenario_files/1_mainRoute are placeholders and are not reliable expected I/O samples.

B1 input (excerpt)

WMS output (expected shape)

9. Implementation checklist for consultants

1. Document type: ensure the published B1 document is the intended goods receipt / PDN payload for this flow.

2. Warehouse codes: must match WMS warehouses; bin is always WarehouseCode-ONT1 — configure that bin (or accept the convention) in WMS.

3. UoM: understand -1 fallback (m + measure unit) and batch quantity ÷ UnitsOfMeasurment.

4. Serial items: expect one WMS line per serial with quantity 1.

5. Batch items: expect one WMS line per batch with batch number and expiry.

6. Reason: WMS will always see reason PDN / Ad-Hoc Purchase Delivery Note (not free text from B1 comments).

7. Tracking: use correlation.correlationId and customFields.DocNum for support.

8. Do not expect picking-warehouse filtering or BOM handling from this mapper.

10. Source artifacts (for reference)

Generated from the mapping definition and integration behavior in this project. If the MapForce mapping changes, this document should be reviewed and updated.

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.