System Architecture

SAPFEVER employs a unified clean architecture ensuring enterprise-grade reliability, scalability, and security across all products. Built for mission-critical SAP integrations.

Clean Architecture Enterprise-Grade Unified Core

Why Architecture Matters

🔒

Enterprise Security

Layered security model ensures SAP credentials and data never leak between components or sessions.

🔄

Consistent Behavior

Same core logic powers both CLI and MCP interfaces - identical results regardless of how you access SAP.

Production Ready

Battle-tested in enterprise environments. Designed for 24/7 operation with thousands of concurrent users.

High-Level Design

User Interfaces
sapf-mcp-server
MCP Protocol
sapf-cli
Command Line
Experience Managers
MCP Manager
JSON-RPC, Tool/Resource lifecycle
CLI Manager
Commands, Output formatting
Shared Core (Unified Logic)
Runtime Manager
Tool loading, Config
SAP Manager
RFC, Sessions
License Manager
Quotas, Validation
SAP Layer
SAP Systems
RFC Connection
ABAP Runtime
ZBAPI Framework

Component Overview

Entry Points

sapf-mcp-server

Handles JSON-RPC communication for MCP clients. Exposes tools and resources via the Model Context Protocol standard.

sapf-cli

Handles command-line arguments and standard output formatting. Ideal for scripting, automation, and tool development.

Experience Managers

Translate interface-specific protocols to unified core operations.

MCP Manager

Manages MCP tool/resource lifecycle, context handling, and protocol translation for AI assistant integration.

CLI Manager

Manages CLI command execution, argument parsing, and smart output rendering (tables, JSON, text).

Shared Core Infrastructure

The heart of SAPFEVER - identical logic powers all interfaces, ensuring consistent behavior.

Runtime Manager

Handles dynamic tool loading, resource management, template processing, and configuration.

SAP Manager

Manages RFC connections, session handling, pagination, and ABAP execution.

License Manager

Validates license keys, enforces quotas, and manages system ID restrictions.

SAP Integration Layer

Our SAP Integration Protocol (SIP) provides a standardized way to communicate with SAP systems through RFC calls.

RFC Connection Features

  • Connection pooling for optimal performance
  • SAProuter support for secure network traversal
  • Automatic reconnection on connection loss
  • Multi-system support in single deployment

ZBAPI Framework

  • Standardized ABAP tool execution pattern
  • Built-in pagination for large datasets
  • JSON request/response protocol
  • Structured error handling with ET_MESSAGES

Enterprise Benefits

For IT Leaders

  • 1
    Single deployment, multiple interfaces - MCP server and CLI share the same core, reducing maintenance overhead
  • 2
    Audit trail built-in - Every SAP operation is logged with user, timestamp, and parameters
  • 3
    License governance - Control tool access, execution limits, and system IDs centrally

For Consultants

  • 1
    Portable license - Single license works across multiple client SAP systems
  • 2
    Consistent tooling - Same tools work identically via CLI scripts or AI assistants
  • 3
    Build custom tools - Create and monetize SAP tools in the marketplace

Supported SAP Systems

🏢
SAP ECC
ERP Central Component
S/4HANA
Next-gen ERP Suite
📊
BW/4HANA
Business Warehouse
🔧
Solution Manager
System Monitoring

Works with any SAP system supporting RFC connections - including custom ABAP systems and industry solutions.