/
Batch Attribute and Simplate Mapping

Batch Attribute and Simplate Mapping

[ 1.1 Purpose and Scope ] [ 1.2 How Batch Attributes Appear in WMS+ ] [ 2 Admin Note: ] [ 2.1 Using Simplates to Auto-Populate Fields ] [ 2.2 Field Logic Controlled by the SEM Receiving Procs: Fields ] [ 2.3 Best Practices ] [ 2.4 Summary for Admins ]

WMS+ supports flexible batch attribute configuration for receiving and traceability processes, using a combination of SAP Business One User-Defined Fields (UDFs) and Simplate syntax. Batch attributes appear in WMS+ during receiving when configured by the administrator. Fields can be auto filled using barcode data or system tokens, and GS1 Application Identifiers (AIs) can be mapped to fields such as lot number, expiration date or origin.

Purpose and Scope

Batch-managed items often require additional data to support compliance, traceability, and FIFO or customer-specific labeling. WMS+ enables this by:

  • Exposing batch attribute fields created in SAP Business One.

  • Allowing Simplate syntax to auto-fill field values based on barcode scans or system-generated logic.

  • Supporting auto-population of batch fields during receiving processes.

Configuring batch attributes and Simplate mappings is especially relevant for industries with regulated labeling, short shelf-life products or complex attribute tracking (e.g., food distribution or pharmaceuticals).

How Batch Attributes Appear in WMS+

When receiving batch-managed items, WMS+ displays a batch entry screen that includes standard and custom fields. These may include:

  • Lot Number

  • Quantity

  • Expiration or Manufacturing Date

  • Notes or Free Text

  • UDFs such as Grade, Country of Origin or Moisture Level

Batch Breakdown Screen.png

The fields shown are determined by SAP B1 configuration and a system-managed table called the SEM Receiving Procedures configuration table.

Admin Note:

Admins do not configure this table directly. It is a backend table maintained by implementation partners or during system setup. It controls which fields appear in WMS+, whether they are mandatory, and what Simplate logic (if any) is used to auto-fill values.

Using Simplates to Auto-Populate Fields

Simplates are a templating system used in WMS+ to insert live data into batch fields at the point of capture. This reduces manual entry and ensures accuracy when receiving barcode-labeled goods.

Token

Description

{{$:@barcode.barcode}}

Full scanned GS1 barcode string.

{{$:@barcode.AI}}

Value of the specified GS1 Application Identifier (AI) from the barcode. Examples: {{$:@barcode.10}} = Lot Number, {{$:@barcode.17}} = Expiration Date, {{$:@barcode.310}} = Net weight (kg).

{{$:@barcode.list}}

Semicolon-separated list of all AIs present in the scanned barcode.

{{date:today}}

Today’s date.

{{date-add:{{date:today}};m=3}}

Inserts an expiration date 3 months from today. To add days instead, use d=30 for 30 days.

{{$:counter}}

Auto-incrementing serial number.

{{$$}}

Show all JSON objects available for templating

{{str-right:2:{{date:yy}}}}-{{str-leading0:3:{{date:day-of-year}}}}

Julian Date

{{$:#user.UserName}}

User Name

All Simplate-generated values remain editable by the user in WMS+ unless restricted through custom development.

Example Simplate Expressions

  • {{$:@barcode.10}} inserts the lot number from the scanned barcode.

  • {{$:@barcode.17 ?? {{date:today}}}} inserts the expiry date if available, otherwise uses today’s date.

  • {{$:@barcode.17 ?? $:@barcode.15 ?? {{date:today}}}} chains multiple fallback options.

Field Logic Controlled by the SEM Receiving Procs: Fields

Although Admin Users do not directly edit this table, it's important to understand what it controls:

  • Field Visibility: Only fields marked as visible in the table appear in WMS+.

  • Template Assignment: Simplate expressions entered here define auto-filled logic.

  • Mandatory Status: Fields marked mandatory must be completed before saving.

If batch fields are not appearing or values are not auto-populating as expected, consult your system support team to review the setup of this table.

image-20240718-085432.png

Best Practices

  • Use the {{$$}} token to test and debug Simplate context during setup.

  • Keep only the most relevant batch fields visible to avoid clutter.

  • Use fallback logic (??) for optional values to prevent errors during scanning.

  • Train receiving users on how batch data flows back to SAP B1 and why it matters for traceability.

Summary for Admins

WMS+ uses a structured backend configuration to determine how batch attributes appear and behave during receiving. While Admin Users don’t access the SEM Receiving Procedures table directly, they should:

  • Ensure required UDFs exist in SAP Business One under Inventory → Serial/Batch Number Object.

  • Confirm with support that Simplate logic is in place to auto-fill values using GS1 barcodes.

  • Understand which fields are required, visible, and editable in the WMS+ batch screen.