This integration receives SAP Business One production orders and maps them to Aiden WMS document messages. The incoming SAP production order is checked against SAP warehouse configuration before any WMS document is emitted.
|
Input condition |
Mapper result |
Target endpoint header |
|---|---|---|
|
At least one production component line is in a warehouse flagged for picking |
Issue-to-production picking document |
|
|
Header production warehouse is released for receiving |
Receipt-from-production receiving document |
|
|
Both conditions are true |
Two WMS documents are emitted from the same production order |
|
|
Neither condition is true |
No WMS document is emitted |
None |
Warehouse configuration is refreshed hourly from SAP Business One:
Warehouses?$select=WarehouseCode,DefaultBin,EnableBinLocations,U_AEN_WHS_Picking
For issue-to-production, item master data is also fetched from SAP Items for the production-order component lines, selecting ItemCode, InventoryItem, and InventoryUOM. This enriches WMS line UOM behavior.
The checked-in output_*.json files show the target shape, but the generated MapForce Java under mappings/output/com/mapforce/ is the source of truth for current field behavior.
Routing And Preconditions
The route stores the original production order, runs a picking/receiving check, then conditionally invokes one or both mappers.
|
Input field or lookup |
Output decision |
Business rule |
|---|---|---|
|
|
Receiving eligibility |
Receiving can be created when the production order is released for receiving. |
|
Header |
Receiving warehouse match |
Header warehouse is used to decide whether a receipt document is relevant. |
|
|
Picking warehouse match |
Component line warehouses are checked individually. |
|
Matching warehouse |
Picking eligibility |
If any component line warehouse is picking-enabled, an |
|
Kafka message key |
|
The same correlation id is copied into every created WMS document. |
Receipt From Production
The receipt mapper creates an IncomingDocument for the finished product. It represents the expected receipt of the production order header item into WMS.
Header
|
SAP production order input |
WMS output |
Business rule |
|---|---|---|
|
Kafka message key |
|
Preserves message traceability. |
|
|
|
Converted to text for the WMS document id. |
|
Constant |
|
Marks the WMS document as production-order based. |
|
|
|
Finished item code is used as the WMS business partner id. |
|
|
|
Finished item description is used as the business partner name. |
|
|
|
Due date becomes the expected receive date. |
|
Constant |
|
New WMS document is opened for processing. |
|
|
|
Production remarks are carried as operational details where present. |
|
|
|
SAP production order entry is retained for later callback/mapping. |
|
Constant |
|
Identifies the source object type for return flows. |
Lines
|
SAP production order input |
WMS output |
Business rule |
|---|---|---|
|
Header |
|
The finished product is received into the production order header warehouse. |
|
Header |
|
The finished product becomes the receipt line item. |
|
|
|
Planned production quantity becomes the expected receipt quantity. |
|
|
|
Mapper uses available SAP UOM information for WMS. |
|
|
|
Line receive date follows the production due date. |
|
Generated line number |
|
WMS line numbering is generated while retaining the source line number in custom fields. |
Issue To Production
The issue mapper creates an OutgoingDocument for components that WMS must pick for production. Before mapping, the route enriches production-order component items with SAP item master data.
Header
|
SAP production order input |
WMS output |
Business rule |
|---|---|---|
|
Kafka message key |
|
Preserves message traceability. |
|
|
|
Converted to text for the WMS document id. |
|
Constant |
|
Marks the WMS document as production-order based. |
|
|
|
Finished item code identifies the production context. |
|
|
|
Finished item description identifies the production context. |
|
Constant |
|
Uses a fixed WMS production address. |
|
|
|
Start date becomes the expected picking date. |
|
Constant |
|
New WMS picking document is opened. |
|
|
|
Pick remarks are carried to WMS operators. |
|
|
|
SAP production order entry is retained for callbacks. |
|
Constant |
|
Identifies the source object type for return flows. |
Lines
|
SAP production order input |
WMS output |
Business rule |
|---|---|---|
|
|
|
The source production line number is preserved. |
|
|
|
Component warehouse becomes the picking warehouse. |
|
|
|
Component item becomes the WMS item to pick. |
|
|
|
Planned component quantity becomes the pick quantity. |
|
Enriched SAP |
|
Inventory item master data can override or supply WMS UOM. |
|
|
|
Component start date becomes the line pick date. |
|
|
|
Line text is carried as WMS line details where present. |
|
|
|
Issue type is preserved for downstream behavior. |
What Implementers Can Expect
After installation, released SAP production orders can automatically create WMS work for both sides of production: picking component stock out and receiving the finished product back in. Which document appears depends on warehouse setup. Warehouses marked with U_AEN_WHS_Picking = "Y" drive picking documents. The production-order header warehouse and release-for-receiving flag drive receiving documents.
Every WMS document includes the original SAP production order id in customFields.externalId, the object type ProductionOrders, and the incoming message correlation id. This lets later WMS-to-SAP flows connect picking and receiving results back to the source production order.