Nexeed
    • Introduction
    • User manual
      • Machine Maintenance
      • Tool Maintenance
      • Machine Task Templates
      • Tool Task Templates
      • Schedules
      • Configuration
        • General
        • ERP
        • Task templates
        • Result classifications
        • Bosch Cognitive Service
      • Working with tasks
        • Using the Kanban view for tasks
        • Corrective Task
        • Preventive Task
      • Using task templates
        • Machine task template
        • Tool task template
      • Using schedules
      • Filter and search functions
    • Operations manual
      • Overview
      • System Architecture and Interfaces
      • System Requirements
        • bci-app/nginx
        • maintenance-management/mm-service
        • mm/mm-connector-sparepart
      • Migration from Previous Versions
        • Resources mapping from MES to IAS
      • Setup and Configuration
        • Configuration of the helm chart
        • MM Connector Spare Part
        • ERP Connector & Orchestrator Packages
      • Start and Shutdown
      • Regular Operations
      • Failure Handling
      • Backup and Restore
        • Tenant restore
      • Logging and Monitoring
        • Module Health Endpoints and K8S Probes
      • Known Limitations
    • Developer documentation
      • How-Tos
        • Embedded views
        • Dialog views
    • API documentation
      • HTTP API
      • Async API
    • Glossary
Maintenance 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

  • Maintenance Management
  • Operations manual
  • Setup and Configuration
  • MM Connector Spare Part
preview 2.6

MM Connector Spare Part

  • We need to configure a plant that using MM Connector Spart Part by insert data into two tables mmcsp_tenant & mmcsp_plant. No default data is inserted when service starts up.

    INSERT INTO [mmcsp_tenant]
           ([tenant_id]
           ,[tenant_name]
           ,[source_system])
     VALUES
           (<tenant_id, varchar(45),>
           ,<tenant_name, varchar(100),>
           ,<source_system, varchar(5),>)
    INSERT INTO [mmcsp_plant]
           ([plant_code]
           ,[tenant_id]
           ,[plant_name]
           ,[language])
     VALUES
           (<plant_code, varchar(5),>
           ,<tenant_id, varchar(45),>
           ,<plant_name, varchar(100),>
           ,<language, varchar(10),>)
    • tenant_id (mandatory): id of tenant in NIAS, should match with the tenant id inserted into table 'mmc_ProxyTenants' of MM Connector

    • tenant_name (optional): name of tenant

    • source_system (mandatory): source system of spare part in INDIRA (Q87, P87…​)

    • plant_code (mandatory): plant code in SAP (0110, 0150 …​)

    • plant_name (optional): plant name

    • language (optional): language of plant (EN, DE, FR …​), default is EN

  • Example

    INSERT INTO mmcsp_tenant
           ([tenant_id]
           ,[tenant_name]
           ,[source_system])
     VALUES ('ID_OF_A_TENANT', 'NAME_OF_A_TENANT', 'P87')
    INSERT INTO mmcsp_plant
           ([plant_code]
           ,[tenant_id]
           ,[plant_name]
           ,[language])
     VALUES ('CODE_OF_A_PLANT', 'ID_OF_A_TENANT', 'NAME_OF_A_PLANT','EN')
  • To make this MM Connector Spare Part serve another plant, we need to manually add, update data into this 'mmcsp_tenant' & 'mmcsp_plant' tables.

  • To do the spare part reservation in SAP via S4R3 ODATA API, we need to configure data in table 'mmcsp_api_mappings'. This table contains the API endpoint and API key for communication with SAP.

  • Default endpoint is inserted by a liquibase script when the service starts for the first time. However it lacks information about, sap target system, sap api key. We need to manually update data in the table 'mmcsp_api_mappings'.

    UPDATE [mmcsp_api_mappings]
    SET [endpoint_url] = replace(endpoint_url,'[SAP_SYSTEM]','sap_target_system')
       ,[api_key] = <api_key, varchar(255),>
    • endpoint_url (mandatory): Replace [SAP_SYSTEM] in default data with target SAP system (X87, Q87, P87)

    • api_key (mandatory): api key for communication with SAP

  • Example: sap_target_system = 'X87', api_key = 'API_KEY_FOR_SAP_ODATA_API'

    UPDATE [mmcsp_api_mappings]
    SET [endpoint_url] = replace(endpoint_url,'[SAP_SYSTEM]','X87')
      ,[api_key] = 'API_KEY_FOR_SAP_ODATA_API'
  • Scheduled tasks of spare part sync is configured at table 'mmcsp_scheduled_task'. We can update the cron_expression (follow Java Cron Expression) of the task at the table to change trigger time & frequency. Then restart mm spare part service to activate the change. As the spare part sync job takes several hours to complete synchronization, it’s recommended not to run the spare part sync job several times a day.

  • Default triggers are inserted by liquibase:

    • Spare part sync job: 2:00 of every Saturday at UTC timezone

  • If we want to change trigger time of spare part sync job:

    UPDATE [mmcsp_scheduled_task]
    SET [cron_expression] = <cron_expression, varchar(50),>
     WHERE [task_code] = 0
    • task_code : 0 for spare part sync job.

INDIRA configuration

The INDIRA URL and API key can be configured via custom values in the HELM Chart. The following values can be set in the custom-values.yaml file to configure your INDIRA base URL and API key:

global.modules.mm.indiraBaseUrl

global.modules.mm.indiraApiKey

Contents

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

Changelog Corporate information Legal notice Data protection notice Third party licenses