Sales Order

Functional documentation for the Aiden WMS sales order mapper.

This document describes what happens after the mapper is installed: which SAP Business One (B1) sales order 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 sales order is published to the integration, the mapper produces a WMS document that contains:

• Document identity and type

• Customer (business partner)

• Ship-to address

• Order lines for picking-enabled warehouses only

• Optional sales BOM structure on BOM-related lines

• Optional freight/expenses and text special lines

• Correlation id for tracking

Fixed business defaults

These values are always set by the mapper (not taken from B1):

2. What the mapper uses as input

2.1 Main payload — B1 sales order

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

• Header: DocNum, DocEntry, CardCode, CardName, DocDueDate, DocumentStatus, PartialSupply, DocObjectCode, PickRemark, NumAtCard

• Ship-to address: AddressExtension.ShipTo*

• Lines: DocumentLines[]

• Header additional expenses: DocumentAdditionalExpenses[]

• Special lines: DocumentSpecialLines[]

2.2 Warehouse list (automatic)

The integration periodically loads warehouses from B1:

• WarehouseCode

• U_AEN_WHS_Picking (Y / N)

• (also retrieved but not used in field mapping: EnableBinLocations, DefaultBin)

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

2.3 Sales BOM helper data (automatic)

From the same sales order, the integration builds a helper list of lines where:

• TreeType = iSalesTree (sales BOM parent lines)

That list is used only to calculate sales BOM parent/child quantities and parent line references on the WMS lines. Consultants do not need to supply this separately.

2.4 Correlation id

The message correlation id (integration message key) is written to:

• correlation.correlationId

Use this to trace a WMS document back to the integration message.

3. Business behavior

3.1 Which lines are sent to WMS?

A B1 order line is included in data.lines only when its WarehouseCode matches a warehouse with U_AEN_WHS_Picking = Y.

Lines for warehouses with U_AEN_WHS_Picking = N (or unknown warehouse) are not sent to WMS.

Configure picking warehouses correctly in B1 (U_AEN_WHS_Picking) before go-live. Otherwise orders may arrive in WMS with missing lines.

3.2 Document and line status

B1 statuses look like bost_Open / bost_Close.

The mapper:

1. Removes the bost_ prefix → Open / Close

2. Translates Close → Closed (other values stay as-is, e.g. Open)

Applied to:

• Header: DocumentStatus → data.status

• Line: LineStatus → lines[].status

3.3 Partial delivery flags

B1 tYES / tNO flags are converted to booleans:

3.4 Object type

For a normal sales order this is Orders.

3.5 Unit of measure on lines (uomCode)

For each line:

1. If UoMEntry is not -1 → use UoMCode

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

   • If MeasureUnit is missing, an empty string is used after m (result can be just m)

UoMEntry is also copied unchanged to lines[].customFields.UoMEntry.

3.6 Ship-to address

Address is taken from ship-to fields on the sales order (AddressExtension), not bill-to.

3.7 Sales BOM structure (lines[].salesBom)

B1 tree types used:

When is salesBom present on a line?

• Only if the line is a sales BOM parent or ingredient (iSalesTree or iIngredient).

• Otherwise the salesBom object is omitted.

Fields:

Practical expectation for consultants:

• Sales BOM parents and ingredients are flagged in WMS via salesBom.

• Parent kit lines get parent = true and respectSingleQuantity = true.

• Quantity/parent-line calculations depend on VisualOrder ordering of sales-tree lines on the B1 document.

• Non-BOM lines (normal items, production tree, etc.) do not get a salesBom block.

3.8 Customer reference (NumAtCard)

If filled in B1, NumAtCard is sent as a dynamic custom property:

• Property name: NumAtCard

• Property value: the B1 NumAtCard value

(Output schema path: dynamic property / property.name.)

3.9 Additional expenses

• Header DocumentAdditionalExpenses → data.customFields.DocumentAdditionalExpenses[]

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

Copied fields: ExpenseCode, LineTotal, GroupCode, DistributionMethod, VatGroup, and line number (LineNum / LineNumber).

3.10 Special lines (text lines)

B1 DocumentSpecialLines are not all copied blindly.

A special line is sent to WMS only when both are true:

1. LineType = dslt_Text (text line only — comment in mapping: “Alleen tekst regels”)

2. AfterLineNumber equals the current order line’s VisualOrder (text is attached in context of that visual order / line position)

Mapped into data.customFields.DocumentSpecialLines[] with amounts/texts copied from B1 (order number, line type, subtotals, freights, tax, gross totals, line text, etc.).

4. Field mapping tables

Legend:

• WMS output field — path in the Aiden WMS order document

• B1 / source input — field on the sales order or other source

• What happens — copy or transformation

• Notes — consultant-relevant remarks

4.1 Correlation

4.2 Document header (data)

4.3 Business partner

4.4 Address (data.address)

4.5 Lines (data.lines[])

Only lines for picking-enabled warehouses (§3.1).

4.6 Sales BOM on lines (lines[].salesBom)

Only for TreeType in (iSalesTree, iIngredient) — see §3.7.

4.7 Line additional expenses

4.8 Header additional expenses

4.9 Special lines (data.customFields.DocumentSpecialLines[])

Filtered — see §3.10.

5. Value translations (reference)

5.1 Yes/no flags

5.2 Warehouse picking flag

5.3 Status

5.4 Document object code

5.5 Sales tree types

5.6 Special line type filter

6. What is not mapped / important omissions

Consultants should not expect the following from this mapper:

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

1. Sales order is created/updated in SAP B1 and published to the integration.

2. Integration loads picking warehouse configuration from B1.

3. Mapper converts the order to a WMS order document:

   • Header + BP + ship-to address

   • Only lines on picking warehouses

   • Status/partial-delivery/UoM/BOM rules applied

4. WMS receives an OutgoingDocument ready for outbound warehouse processing.

5. correlation.correlationId and customFields.externalId (DocEntry) support support/troubleshooting.

8. Example (from project scenario data)

Illustrative values based on scenario_files/1_Sales_order and mapping examples.

B1 input (excerpt)

WMS output (expected shape)

9. Implementation checklist for consultants

1. Warehouses: set U_AEN_WHS_Picking = Y on every warehouse that must create WMS work.

2. Ship-to address: maintain AddressExtension ship-to fields on the sales order.

3. UoM: understand -1 UoM entry fallback (m + measure unit).

4. Sales BOM: use iSalesTree / iIngredient and consistent VisualOrder if WMS must receive BOM structure.

5. Text lines: use dslt_Text special lines with AfterLineNumber aligned to the related line VisualOrder.

6. Tracking: use correlation.correlationId and customFields.externalId (DocEntry) for support.

7. Defaults: expect handling=Manual, priority=3, baseType=SalesOrder on every document.

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.