Purchase Order

Functional documentation for the Aiden WMS purchase order mapper (outbound).

This document describes what happens after the mapper is installed: how a SAP Business One (B1) purchase order becomes a WMS incoming/receipt document, which lines are included, and which field rules apply. It is intended for end-users and functional consultants.

1. Overview

After installation, when a purchase order is published to the integration, the mapper produces a WMS document that contains:

• Document identity and base type PurchaseOrder

• Vendor (business partner)

• Receive date

• Filtered order lines (inventory items on picking warehouses only)

• Remaining open quantities

• Optional expenses and customer reference (NumAtCard)

• Correlation id for tracking

Fixed business defaults

2. What the mapper uses as input

2.1 Main payload — B1 purchase order

The primary input is the B1 purchase order document, including for example:

• Header: DocNum, DocEntry, CardCode, CardName, DocDueDate, DocumentStatus, NumAtCard

• Lines: DocumentLines[] (LineNum, ItemCode, WarehouseCode, LineStatus, RemainingOpenQuantity, UoM fields, FreeText, line expenses)

• Header expenses: DocumentAdditionalExpenses[]

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

2.2 Inventory item enrichment (automatic, per message)

Before mapping, the integration calls B1 Items for every distinct line item code on the PO:

• $select=ItemCode,InventoryItem

• Requests are batched (max.items.from.service.layer, default 20 item codes per call)

Business impact: only lines whose item is an inventory item (InventoryItem = tYES) are sent to WMS. Non-inventory items (services, non-stock, etc.) are dropped.

2.3 Warehouse list (automatic, hourly)

The integration periodically loads warehouses from B1:

• WarehouseCode

• U_AEN_WHS_Picking (Y / N)

• (also retrieved: EnableBinLocations, DefaultBin — not used as primary line filter in this mapping)

Business impact: only lines whose warehouse is marked picking-enabled (U_AEN_WHS_Picking = Y) are sent to WMS.

2.4 Correlation id

Integration message key → correlation.correlationId.

3. Business behavior

3.1 Which lines are sent to WMS?

A B1 PO line is included in data.lines only when both are true:

1. Enriched item master has InventoryItem = tYES for that ItemCode

2. Line WarehouseCode matches a warehouse with U_AEN_WHS_Picking = Y

Otherwise the line is omitted.

Configure inventory flags on items and picking warehouses in B1 before go-live. Otherwise receipts may miss lines or include none.

3.2 Quantity = remaining open quantity

WMS line quantity is mapped from B1 RemainingOpenQuantity, not from the original ordered Quantity.

This is critical for consultants: the mapper is aimed at what is still open to receive, not the original PO quantity.

3.3 Document and line status

B1 statuses look like bost_Open / bost_Close.

Header status strip does not apply the Close→Closed valuemap in the same way as lines; header typically becomes Open / Close after removing bost_.

3.4 Unit of measure (uomCode)

For each included 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

Examples from scenario-style data: manual UoM (UoMEntry = -1) with MeasureUnit = Pallet → mPallet; empty measure → m.

3.5 Receive date

data.receiveDate ← DocDueDate (PO due date becomes expected receive date in WMS).

3.6 Customer / vendor reference (NumAtCard)

If filled, NumAtCard is exposed as a dynamic custom property:

• Property name: NumAtCard

• Property value: B1 NumAtCard

3.7 Additional expenses

• Header DocumentAdditionalExpenses → data.customFields.DocumentAdditionalExpenses[]

• Line DocumentLineAdditionalExpenses → lines[].customFields.DocumentAdditionalExpenses[]

Copied fields include ExpenseCode, LineTotal, GroupCode, DistributionMethod, VatGroup, LineNum.

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

4.4 Lines (data.lines[])

Only lines that pass inventory item + picking warehouse filters (§3.1).

4.5 Expenses

5. Value translations (reference)

5.1 Status

5.2 Warehouse picking

5.3 Inventory item enrichment

5.4 Constants

6. What is not mapped / caveats

7. Example (scenario 1_PurchaseOrder)

B1 input (excerpt)

WMS output (excerpt from 3_target.json)

Use this scenario to validate filters + open qty, not a happy-path open receipt with positive quantities.

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

1. Purchase order is created/updated in B1 and published to Kafka.

2. Integration loads picking warehouses (timer) and, per message, enriches line items with InventoryItem.

3. Mapper builds WMS incoming document:

   • Header + vendor + due date

   • Only inventory lines on picking warehouses

   • Quantities = remaining open

4. Message is published for WMS IncomingDocument.

5. Trace with correlation.correlationId and customFields.externalId (DocEntry).

9. Implementation checklist for consultants

1. Mark stock items as Inventory Item in B1.

2. Set U_AEN_WHS_Picking = Y on warehouses that must create WMS receipt work.

3. Understand that WMS quantity is remaining open, not ordered qty.

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

5. Expect non-inventory PO lines (freight service items, etc.) not to appear in WMS.

6. After partial GRPO in B1, republished POs should show reduced open quantities.

7. Trace with correlation id + DocEntry / DocNum.

10. Source artifacts

Generated from the mapping definition and integration behavior in this project. If the MapForce mapping or enrichment 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.