Skip to main content

Overview

A System in S4Kit represents an SAP landscape—a collection of related environments (instances) that share the same SAP system configuration.

System Types

S4Kit supports different SAP system types:

Creating a System

Via Dashboard

  1. Navigate to Systems in the sidebar
  2. Click Add System
  3. Fill in the system details:
    • Name: A friendly name (e.g., “Production ERP”)
    • Alias: A short identifier used in code (e.g., “production”)
    • Type: Select the SAP system type
    • Description: Optional description

System Fields

How Connection Works

The SDK’s connection parameter uses fixed instance environment values, not custom aliases:
Available environments: sandbox, dev, quality, preprod, productionYour API key determines which system’s instance is used. If your key only has access to “ERP Americas”, then connection: 'production' connects to ERP Americas’ production instance.

Managing Systems

Edit System

Update system details from the dashboard:
  1. Go to Systems
  2. Click on the system to edit
  3. Update the fields
  4. Click Save

Delete System

Deleting a system removes all associated instances, services, and API key access configurations. This action cannot be undone.
  1. Go to Systems
  2. Click on the system
  3. Click Delete System
  4. Confirm the deletion

Best Practices

Naming Conventions

Use consistent naming that reflects your SAP landscape:

One System Per Landscape

Create one S4Kit system per SAP landscape. For example, if you have:
  • A production ERP
  • A development ERP
  • A separate CRM system
Create three S4Kit systems, each with their own instances.

Multi-Region Setup

For global deployments with regional SAP systems, create separate S4Kit systems for each region. Use different API keys to control access: Each API key is scoped to its system’s instances. Using connection: 'production' with the US key connects to ERP Americas’ production.

System Configuration

After creating a system, you’ll need to:
  1. Add Instances: Configure the environment endpoints
  2. Bind Services: Select which OData services to expose
  3. Configure Authentication: Set up SAP credentials

Instances

Configure system environments

Services

Bind OData services