SAP S4/HANA

Enterprise ERP

Overview

Keep Your SAP Plan and the Shop Floor Aligned

SAP holds the plan. Redzone runs it on the floor. This integration connects the two through the Redzone Advanced Integrations add-on, so a released order in SAP becomes a scheduled run in Redzone, and the counts from that run post back to SAP. A custom-coded version of this can take months. This package deploys in weeks, and it works across discrete, process, and mixed-mode lines.

Key Features

SAP
Redzone

Automated Product Master Sync

SAP Material Master data, such as product types and units of measure, syncs to Redzone as it changes, so operators run on the current spec.

SAP
Redzone

Real-Time Schedule Import

Released production and process orders land in Redzone as scheduled runs, so operators can see the queue and its sequence without a planner walking it over.

Redzone
SAP

Production Reconciliation

Counts and "Run Ended" statuses post back to SAP as the run happens, so inventory and order status reflect actual output.

Both Modes

Mixed-Mode Manufacturing Support

One integration covers discrete plants, process plants, and the mixed-mode sites that run both.

How It Works

Standardized Architecture, Incremental Sync

The integration runs a two-way sync between SAP and Redzone. It filters on "last modified date" and "location/plant" to handle incremental (delta) loads, so each cycle processes only new or changed records. The Redzone–SAP integration runs on standardized protocols that require the following components in place before starting configuration.

Component
Requirement
ERP Version
SAP S/4HANA (Cloud version)
Product Sync API
SAP S/4HANA (Cloud version)
Schedule Sync API
API_PRODUCTION_ORDER_2_SRV / API_PROCESS_ORDER_2_SRV
Production Events API
API_PROD_ORDER_CONFIRMATION_2_SRV / API_PROC_ORDER_CONFIRMATION_2_SRV
Add-on Required
Redzone Advanced Integrations add-on (Integration Pack)

Requirements

  • System access

    SAP access with permissions for the relevant transaction codes (for example, MM01–03, CO01–03, SEGW).

  • Redzone configuration

    An active Redzone instance with API Client ID, Client Secret, and Organization/Enterprise IDs.

  • Custom fields

    SAP custom fields to capture Redzone-specific data (for example, Cycle Active Target, Standard Rate) created before configuration

Getting Started

  1. Contact Us

    Book a meeting with a Redzone Integration Specialist to discuss your goals and confirm fit.
    Schedule a call

  2. Select Your Workflows

    Choose from Product Master Sync, Production Schedule Sync (discrete or process), and Production Reconciliation based on your operational priorities.

  3. Review Quote & Purchase

    Confirm the standard Redzone Advanced Integrations add-on Integration Pack, with project fees and delivery milestones set out up front.

  4. Configuration & Testing

    We fit the integration to your environment in three steps:

    • Build: Set up API credentials, tokens, and data routes in the Advanced Integrations add-on environment.
    • Test & validation: Run validation testing in a staging environment (for example, Plant 1710).
    • Mapping: Map SAP internal IDs to Redzone UUIDs and configure custom fields for Redzone concepts (like Manufacturing Type).

  5. Go Live & Support

    Go to production with the Redzone team on hand for setup questions and day-to-day support.

Frequently Asked Questions

Didn’t find what you need? View the full FAQ.

What are the primary workflows supported?

The integration supports 3 standardized scenarios: Product Master Sync (item data from SAP to Redzone), Production Schedule Sync (releases orders into Redzone scheduled runs), and Production Reconciliation (counts from Redzone back to SAP to update inventory and order status).

Does the integration support mixed-mode manufacturing?

Yes. It handles discrete and process orders with separate SAP API libraries (API_PRODUCTION_ORDER_2_SRV and API_PROCESS_ORDER_2_SRV), and it can add a prefix such as D_ or P_ to the order ID, so they stay sorted in Redzone.

How are deletions or technical completions handled?

When SAP marks an order Technically Completed (OrderIsTechnicallyCompleted = TECO), the integration syncs to Redzone and removes or updates the matching scheduled run, so the floor schedule stays current.

Are custom fields required in SAP for the integration?

Yes. Redzone concepts such as Manufacturing Type, Cycle Active Target, and Standard Rate have no native SAP field, so you create them as custom fields in SAP before configuration.

I’m interested. What should I do first?

Redzone builds and manages this integration around your floor and SAP setup. Book a meeting with a Redzone Integration Specialist or contact your Redzone Account Manager to get started.