This integration receives Aiden WMS goods-receipt transactions and turns them into SAP Business One service-layer requests. The first document in the incoming message decides the business scenario through documents[0].customFields.objectType.
|
Input |
Mapper result |
SAP endpoint |
|---|---|---|
|
|
Purchase delivery note |
|
|
|
Production receipt / inventory goods receipt |
|
|
|
Stock transfer |
|
Messages with another objectType are logged as unmatched and are not mapped to an SAP endpoint.
The checked-in output_*.json files are examples of the target shape, but the generated MapForce Java under mappings/output/com/mapforce/ is the source of truth for the current logic.
Common Behavior
The mapper uses the WMS transaction id as traceability on the SAP document:
|
Input field |
Output field |
In-between behavior |
|---|---|---|
|
|
|
Copied as text to the SAP user-defined field. |
|
|
|
Copied as provided by WMS. No date truncation is performed by the mapper. |
|
|
|
Parsed as a number and used as the base SAP document entry. |
|
|
SAP base line fields |
The mapper joins saved receipt quantities back to their original WMS document line. |
For serial and batch handling, the mapper reads savedLines. A saved line with a serial number becomes serial-number detail. A saved line with a batch number becomes batch-number detail. Lines without serial or batch data are mapped as normal quantity lines.
Purchase Delivery Notes
Purchase receipts are created when the WMS document has objectType = "PurchaseOrders". The result is posted to PurchaseDeliveryNotes.
Header
|
WMS input |
SAP output |
Business rule |
|---|---|---|
|
|
|
The vendor/customer code from WMS becomes the SAP business partner code. |
|
|
|
Receipt processing date is used as the SAP document date. |
|
|
|
Keeps the SAP document traceable to the WMS transaction. |
|
|
|
Document-level additional expenses are copied to the SAP document. |
Additional expenses are mapped field-for-field:
|
WMS input |
SAP output |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Lines
|
WMS input |
SAP output |
Business rule |
|---|---|---|
|
|
|
Links the delivery note line to the original SAP purchase order. |
|
|
|
Identifies the source purchase-order line. |
|
|
|
The mapper converts the WMS object type to the SAP purchase order base type. |
|
Matching |
|
Quantities are summed per source line and tracking group. |
|
|
|
Non-empty serial numbers create SAP serial-number rows. |
|
Serial saved-line quantity |
|
Quantity is copied for each serial entry. |
|
|
|
Non-empty batch numbers create SAP batch-number rows. |
|
|
|
Expiry date is copied when provided. |
|
|
|
Batch quantity uses base quantity, not display quantity. |
Production Receipts
Production receipts are created when the WMS document has objectType = "ProductionOrders". The result is posted to InventoryGenEntries.
Header
|
WMS input |
SAP output |
Business rule |
|---|---|---|
|
|
|
The WMS processing timestamp becomes the SAP document date value. |
|
|
|
Keeps the receipt traceable to the WMS transaction. |
Lines
|
WMS input |
SAP output |
Business rule |
|---|---|---|
|
|
|
Links the goods receipt to the original SAP production order. |
|
WMS line grouping |
SAP base line handling |
The mapper groups saved receipt lines by |
|
|
|
The mapper converts the WMS object type to the SAP production order base type. |
|
Matching |
|
Quantities are summed per source line and tracking group. |
|
|
|
Non-empty serial numbers create serial-number rows. |
|
Serial saved-line quantity |
|
Quantity is copied for each serial entry. |
|
|
|
Non-empty batch numbers create batch-number rows. |
|
|
|
Expiry date is copied when provided. |
|
|
|
Batch quantity uses base quantity, not display quantity. |
Stock Transfers
Stock transfers are created when the WMS document has objectType = "StockTransferRequests". The result is posted to StockTransfers.
Before stock-transfer mapping runs, the integration refreshes SAP warehouse configuration hourly from:
Warehouses?$select=WarehouseCode,DefaultBin,EnableBinLocations
That warehouse list is passed into the MapForce mapper so it can allocate lines to the correct SAP bin.
Header
|
WMS input |
SAP output |
Business rule |
|---|---|---|
|
|
|
Keeps the stock transfer traceable to the WMS transaction. |
Lines And Bins
|
WMS input |
SAP output |
Business rule |
|---|---|---|
|
|
|
Links the transfer to the source SAP stock-transfer request. |
|
Matching WMS document line |
|
Keeps each transfer line tied to its source request line. |
|
|
|
The mapper converts the WMS object type to the SAP stock-transfer-request base type. |
|
Matching |
|
Quantities are summed per source line and tracking group. |
|
|
|
Serial-managed items create SAP serial-number rows. Some serial rows use quantity |
|
SAP warehouse list where |
|
The mapper uses the matching warehouse |
|
Mapped line quantity |
|
Bin allocation quantity follows the mapped transfer-line quantity. |
What Implementers Can Expect
After installation, supported WMS goods receipts automatically become SAP Business One documents for purchase orders, production orders, or stock-transfer requests. The mapper preserves the WMS transaction id on every SAP document, links lines back to SAP base documents through externalId and line numbers, and carries serial, batch, expiry, and base quantity information where present.
For stock transfers, correct bin output depends on SAP warehouse configuration being available to the integration. If a warehouse is not bin-enabled or no matching WarehouseCode is returned, the mapper cannot derive the default bin allocation for that warehouse.