Nexeed
    • Introduction
    • User Manual
      • Log into the Desktop Client
      • User interface
      • Set language
      • Adjust configuration
      • Adjust settings
      • Master data
        • Actions
        • Categories
        • Groupings
        • Material classes
        • Part types
      • Operation
        • Product parts lists
        • Product assembly plan
        • Packaging instructions
        • Type/material actions
    • Operations manual
      • Overview
      • System architecture and interfaces
        • Interface mappings with ERP
      • System requirements
        • Backend
        • Client
        • Required infrastructure services
        • Messaging middleware
      • Migration from previous versions
        • Data from MES to IAS
        • Configuration files to RuntimeConfiguration
        • Resources mapping from MES to IAS
        • V3.2 to V3.3
      • Setup and configuration
        • Database
        • Service
        • Client
        • Runtime
      • Start and shutdown
      • Regular operations
      • Failure handling
        • Authentication troubleshooting
        • Authorization troubleshooting
      • Backup and Restore
      • Logging and monitoring
      • Known limitations
        • Multitenancy Capability
        • On Premise
        • ClickOnce
        • Database Limitation
        • IAS Constraints
        • Direct Access Grants
    • Developer documentation
      • Getting started
        • Setup for ERPC use cases
      • How-to
        • Explode product setup (import from ERP)
        • Import packaging setup from ERP
        • Get product setups after explosion
        • Get production versions
    • API documentation
    • Glossary
Product Setup Management
  • 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

  • Product Setup Management
  • Developer documentation
  • How-to
  • Explode product setup (import from ERP)

Explode product setup (import from ERP)

Prerequisites

Product setup explosion does not require active connection with ERPC. However, the "raw" product setup and material master synchronization from SAP (via ERPC) is required at least once to have data in the Product Setup Management database that the explosion algorithm can use.

Explosion modes

The endpoint (see in the API documentation - ExplodeProductSetup) can trigger the explosion in 3 different modes. Based on the mode, one or multiple product setups will be created and returned. The items are in a flat structure, except for dummy assembly (phantom material) items as this flag indicates the presence of sub-materials.

Explosion on root level

Only one product setup will be created and returned by the API (the one with the provided TypeNumber), even if the materials have further data in the database.

Explosion until specified level

Potentially multiple product setups will be created and returned by the API, as the algorithm checks recursively the available raw and master data for the materials and their sub-materials until the specified recursion level. If the data is available the explosion trigger for these materials as well.

Explosion until deepest level

The only difference compared to the specified level case is that the algorithm will not stop, but processes the sub-material data recursively until it is available.

Triggering the explosion

The explosion uses the given TypeNumber and BenDate properties from the request for locating the corresponding raw product setup data and material master data. The product setup only becomes visible after the explosion.

Validation options

For detailed information about how to change these validation flags, check the adjust configuration part of the user manual.

  • BomExplosion.ValidateMaterialMasterExists - if true, the explosion can be triggered if all the items (and the provided TypeNumber) have corresponding MaterialMaster data in the Product Setup Management database.

  • BomExplosion.ValidateBackflush - if true, the explosion can be triggered if all the ProductionRelevant items have false Backflush value.

Mandatory parameters

  • TypeNumber

  • BenDate

Optional parameters

  • BenNumber

  • ExplosionMode

    • RootLevel by default

  • Explosion Level

    • When ExplosionMode is set to SpecifiedLevel

  • Status

    • Explode only those product setups that match the specified status.

  • RevisionLevel

    • For now this is only a placeholder

  • ShortkeyBen

    • For now this is only a placeholder

  • WithAlternative

    • By default, true - alternative items are included in the explosion

  • Category

    • For now this is only a placeholder

Contents

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

Changelog Corporate information Legal notice Data protection notice Third party licenses