Discovering Rescheduling Options

Objective

After completing this lesson, you will be able to configure manual and automatic rescheduling methods as well as backward integration between SAP Digital Manufacturing and SAP S/4HANA.

Rescheduling Options

Rescheduling is the process of adjusting operation schedules to respond to changing production requirements, resource availability, and unforeseen disruptions. In SAP Digital Manufacturing's Dispatching and Monitoring app, rescheduling enables production supervisors and manufacturing administrators to dynamically modify when and where operations are performed on the shop floor.

Common scenarios requiring rescheduling include:

  • Machine breakdowns and unscheduled maintenance
  • Rush orders requiring priority handling
  • Material shortages affecting production sequence
  • Resource availability changes
  • Quality issues requiring operation repetition
The SAP Dispatching and Monitoring tool. Top panel shows initial resource allocation, bottom panel demonstrates optimized resource usage with highlighted changes.

Rescheduling Methods

MethodUse Case
Drag-and-DropQuick adjustments for individual operations
Direct Date/Time ModificationPrecise time changes
Resource ReassignmentMoving operations between resources
Downtime ReschedulingHandling unscheduled disruptions

Manual Rescheduling

  • Drag-and-Drop Rescheduling
    • Quick Process
      1. Select the operation in the dispatch area.
      2. Drag to new time slot or different resource.
      3. System displays availability and conflicts.
      4. Drop and confirm the change.
    • Key Features
      • Operations can be rescheduled regardless of release status.
      • Tools are automatically reassigned to the new scheduled time.
      • Immediate visual feedback prevents scheduling conflicts.
  • Direct Date/Time Modification: For precise adjustments, directly edit the operation's start date and time fields.
  • Resource Reassignment: When moving operations between resources, the system validates resource capabilities, availability, capacity constraints, and tool availability.

Automatic Rescheduling for Unscheduled Downtime

The system automatically reschedules operations when unscheduled downtime occurs due to machine faults, unexpected maintenance, or unplanned job changeovers.

How it Works

  1. System detects or user enters unscheduled downtime.
  2. Identifies operations scheduled during downtime period.
  3. Automatically moves affected operations based on predefined rules.

Important Notes

  • Only applies when operations exist within the downtime window.
  • Only works for operations in the Dispatch area.
  • Downtime periods are highlighted and protected from new scheduling.
  • Dispatchers can modify (increase or decrease) the downtime period as needed.

Rescheduling Configuration Options

  • Rescheduling Horizon
    • Define the time frame for rescheduling operations:
    • Start Condition: Beginning of the rescheduling horizon.
    • End Condition: End of the rescheduling horizon.
    • Buffer Time: Additional period for unforeseen delays.
  • Rescheduling Without Downtime
    • Perform immediate rescheduling without considering downtime events. You can reschedule to the same resource or a different resource.
  • Rescheduling with Unscheduled Downtime
    • Enable the Enable Unscheduled Downtime option to allow the system to automatically manage operations affected by unscheduled downtime.
    • Rules Configuration for Current Resource:
      • Use available slots after the unscheduled downtime duration, or
      • Deallocate all operations after the unscheduled downtime.
    • Rules Configuration for Alternate Resources:
      • Use only available slots on alternate resources, or
      • Deallocate all on alternate resources.
  • Handling Conflicts: When the target slot is already occupied, the Find Slot Algorithm prompts users to select an alternative slot, ensuring efficient resource utilization.

SAP S/4HANA Integration - Backward Update

Backward Integration enables planning changes from the shopfloor level (SAP Digital Manufacturing) to be written back to the ERP system (SAP S/4HANA). In this way, a change made in Dispatching and Monitoring is automatically played back without the need for manual follow-up. This closes the loop between planning and execution.

When is it Needed?

  • When production dates are adjusted on the shopfloor.
  • For workstation changes due to machine failures or capacity bottlenecks.
  • For synchronization of planning data between MES and ERP in real-time.
  • To make planning deviations immediately visible in the ERP.

Business Benefits

  • Consistent data between shopfloor and ERP.
  • Real-time synchronization of schedule changes.
  • Avoidance of manual feedback to the ERP.
  • Closed-Loop Planning.

How does it Work Technically?

This requires four main components.

SAP Digital Manufacturing, BTP Destination, Cloud Connector, and SAP S/4HANA (ERP).

Step 1: Rescheduling in DM

Shopfloor employees or planners change in the Dispatching and Monitoring App:

  • Start/end dates of operations
  • Assigned work centers
  • Sequence of orders

Step 2: Triggering the Backward Update

  • DM checks if Backward Update is active
  • Upon activation: DM prepares OData call
  • Changes are formatted as JSON/XML payload

Step 3: OData Communication

  • DM sends PATCH/POST request via BTP Destination
  • Cloud Connector forwards request to SAP S/4HANA
  • API_PRODUCTION_ORDERS receives the data

Step 4: Update in SAP S/4HANA

  • Production order is updated (Transactions CO02/CO03)
  • Operation dates and work center assignments are changed
  • Change documents are generated

The SAP Dispatching and Monitoring interface with a reschedule action and an integration message dashboard displaying order updates and backward update status.

Configuration Guide

Step 1: Activate OData Service in SAP S/4HANA

  • T-Code: /IWFND/MAINT_SERVICE
  • Actions:
    • Add and activate OData service /API_PRODUCTION_ORDERS
    • Assign necessary authorizations to the technical user:
      • S_RFC (RFC calls)
      • Suitable PFCG role (for production orders)
      • SAP_GATEWAY authorizations
  • Verification: Test the OData service via /IWFND/GW_CLIENT

Step 2: Configure SAP Cloud Connector

  • Configure Access Control:
    • Backend Type: SAP System (ABAP)
    • Protocol: HTTPS
    • Internal Host/Port: <S/4HANA-Hostname>:<Port>
    • Virtual Host/Port: virtual-s4h.company.com:8000
    • Location ID: S4H_PROD_01
  • Release OData paths:
    • /sap/opu/odata/sap (with all sub-paths)
    • /sap/opu/odata4/sap (with all sub-paths)

Step 3: Create Destination in SAP BTP

  • Navigation: BTP Cockpit → Subaccount → Connectivity → Destinations
  • Destination Settings:
    • Name: S4H_PROD_ERP (must match DM Business Settings)
    • Type: HTTP
    • URL: http://virtual-s4h.company.com:8000
    • Proxy Type: OnPremise
    • Authentication: BasicAuthentication or OAuth2SAMLBearerAssertion
    • Location ID: S4H_PROD_01 (must match Cloud Connector)
    • User/Password: Technical S/4HANA User
    • Additional Properties:
      • sap-client=100
      • HTML5.DynamicDestination=true (optional)

Step 4: Create Plant in SAP Digital Manufacturing (DM)

  • App: Manage Plants
  • Requirement: Create plant with exactly the same name as in SAP S/4HANA

    (e.g., S/4HANA Plant 1000 → DM Plant must also be 1000)

Step 5: Configure ERP Destination in DM

  • App: Manage Business Settings
  • Setting: ERP Destination = S4H_PROD_ERP (matches BTP Destination Name)

Step 6: Activate Collaboration Directive

  • App: Manage Collaboration Links (link directive as needed)
  • Actions:
    • Choose directive ERP_UPDATE_REO_BACK_SCHEDULE
    • Assign appropriate plant
    • Set Status to Active
    • Enable Direct Access SAP S/4HANA

Step 7: Enable Backward Update in Dispatching & Monitoring

  • AppDispatching and MonitoringSettingsIntegration Settings.
  • Setting: Enable Backward Update, scope per plant if needed.