Nexeed
    • Introduction
    • Station UI
      • Introduction
      • Getting started
      • Configuration
      • Dashboard
      • Utility Bar
        • Scanner
        • Notification Center
      • Operations
        • Packing
        • Discard
        • Complete
        • Shortage
        • Unpacking
    • Web UI
      • Label management
        • Create a label
        • Design a label
      • Packaging process
        • Create a packaging process
      • Packaging sequence main page
      • Packaging sequence
      • Packaging station main page
      • Packaging station UI
      • Packaging unit main page
      • Packaging unit
    • Legacy
      • Introduction to the Packaging Control web application
      • Starting the application
      • Login
      • Set up Packaging Control
      • Packing
        • Packaging form
        • Cancellation wizard
      • Process-specific dialogs
        • Ending the process (reject)
        • Starting the repacking process
        • Weight validation
      • Configuration menu
      • Filter options
    • Operations manual
      • Overview
      • System architecture and interfaces
        • Deployment view
        • Architecture
      • System requirements
        • Paco/helm-chart
        • Paco/paco-service
        • Paco/paco-database
        • PackagingControl_<version>_client.mespkg
        • Paco/core-service
        • Paco/core-web-service
        • Paco/printing-service
      • Migration from previous versions
        • Migration from MES to IAS
        • Migration of database
        • Resources mapping from MES to IAS
        • Migration changes from MES to IAS
        • Migration guides from MES to IAS
        • IAS version upgrades
        • Database update with database job
        • Migration job
      • Setup and configuration
        • Helm configuration
        • Database install from scratch
        • Configuration of Packaging Control
        • Configuration of logging
        • Configuration of related service endpoints
        • Configuration of legacy API redirect
        • Configuration of the home tenant ID
        • Configuration of observability
        • Type data
        • Manager and provider modules
        • Timeout configuration
        • Printing
        • Function modules
        • Sub-function modules
        • Client configuration
        • Global functionality
        • Packing unit details
        • Multi-installation deployment
        • Click-once client installation
        • Core service
        • Core web service
        • Printing service
        • Permissions and roles
      • Start and shutdown
        • Startup dependencies
        • Shutdown
      • Regular operations
      • Failure handling
        • Error codes
        • Warning codes
      • Backup and Restore
      • Logging and monitoring
      • Known limitations
        • Multitenancy capability
        • On premise
        • Database support
        • Client non-web login mechanism
    • API documentation
      • Core Service
        • Core service internal HTTP API
        • Core service restricted public HTTP API
      • Legacy Service
        • Paco service internal HTTP API
        • Paco service restricted public HTTP API
      • Printing Service
        • Printing service internal HTTP API
    • Glossary
Packaging Control
  • Industrial Application System
  • Core Services
    • Block Management
    • Deviation Processor
    • ID Builder
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • Global Production Overview
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Product Setup Management
    • Part Traceability
    • Process Quality
    • Setup Specs
  • Execution
    • Line Control
    • Material Management
    • Order Management
    • Packaging Control
    • Rework Control
  • Intralogistics
    • AGV Control Center
    • Stock Management
    • Transport Management
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
    • Maintenance Management
    • Tool Management
  • Enterprise & Shopfloor Integration
    • Archiving Bridge
    • Data Publisher
    • Direct Data Link
    • Engineering UI
    • ERP Connectivity
    • Gateway
    • Information Router
    • Master Data Management
    • Orchestrator

Nexeed Learning Portal

  • Packaging Control
  • Scan events

Scan events

The Scan Events configuration is no longer part of the general application settings of the Packaging Control client, but must be carried out in OpCon Server Systems (OSS). This configuration can be used to determine events that validate or modify the scanned data (e.g. cut off at end of CR LF) after the information has been received but not yet processed within an operation.

mes oss client configuration 5

Available event sources:

  • Default
    Default scan source that is processed during each scan operation.

  • Part
    Processed if a part (product) has been detected.

  • Box
    Processed if a box has been detected.

  • Pallet
    Processed if a pallet has been detected.

  • SapSubHU
    Processed if a SAP sub-HU (handling unit) has been uniquely detected.

  • SapMainHU
    Processed if a SAP main HU (handling unit) has been uniquely detected.

  • AutomaticSetupStep1
    Processed during the first stage of the automatic setup.

  • AutomaticSetupStep2
    Processed during the second stage of the automatic setup.

  • AutomaticSetupStep3
    Processed during the third stage of the automatic setup.

  • SapSubHUQuantity
    Processed if the quantity of the SAP sub-HU (handling unit) has been uniquely detected.

  • SapMainHUQuantity
    Processed if the quantity of the SAP main HU (handling unit) has been uniquely detected.

  • SapSubHUMaterial
    Processed if the material (type) of the SAP sub-HU (handling unit) has been uniquely detected.

  • SapMainHUMaterial
    Processed if the material (type) of the SAP main HU (handling unit) has been uniquely detected.

  • Gs1EpcGraiHex
    Processed if a GS1 EPC GRAI (Global Returnable Asset Identifier) has been uniquely detected.

  • SerialNumber
    Processed if a part (product) has been detected using the serial number.

  • SapSubHUBatch
    Processed if the batch of the SAP sub-HU (handling unit) has been uniquely detected.

  • SapMainHUBatch
    Processed if the batch of the SAP main HU (handling unit) has been uniquely detected.

If scanned parts (products) are to be detected generally as serial numbers (SerialNumber) and not as Part, it is necessary that the preceding check of the scan event Part always fails. This is achieved by configuring the scan event Part under Verification (RegEx) with the regular expression ^$ and checking Required.

The following table describes the settings for each event source.

If the Override Default option is activated, the event source Default is explicitly not processed.

Parameter Description

Step

Automatically created index of the verification/modification step.

Text

Descriptive text for the step.

Verification (RegEx)

The regular expression to verify the corresponding data (RegEx match).

Modification (RegEx)

AutomaticallyThe regular expression to modify the corresponding data (RegEx replace).

String Extraction (start position)

Specifies the zero-based character start position for a substring operation. #

String Extraction (total length)

Specifies the total length of the string to be extracted from the specified start position.

Verify Required

Determines whether the verification must succeed.

Referenced Step

An alternative verification step can be referenced here, which may be executed after the current step. The referenced step can in turn have an alternative verification step. This allows several verification steps to be linked together.
Link options
1. AND link - The current and the referenced verification step have each set the Required = true parameter. In this case, both verification steps must be executed successfully.
2. OR link - The current and the referenced verification step have each set the Required = false parameter. In this case, one of the two verification steps must be executed successfully. See example below.

Example of referenced step

mes oss client configuration 6

Here, step 0 is executed first. If the verification is successful (scanned value must begin with S followed by nine numbers), step 1 is no longer executed. If the verification fails, step 1 is executed (scanned value must begin with 1JUN followed by 18 numbers). If this step also fails, the verification has failed. If one of the two steps is successful, the entire verification is successful.

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2025, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses