SAP Modules

The Synthesized Platform provides SAP module knowledge and configurable relationship mapping, respecting the boundaries and table relationships within each SAP functional area.

Overview

SAP organizes functionality into modules, each with its own set of master data and transactional tables. The platform understands these module boundaries and:

  • Selects relevant tables for the chosen module

  • Maps relationships between tables using pre-configured and custom virtual foreign keys

  • Applies module-appropriate data transformations

  • Maintains referential integrity across related tables

Material Management (MM)

The MM module covers procurement, inventory management, and material master data. MM includes a guided workflow wizard for streamlined configuration.

Master Data Tables

Table Description Key Fields

MARA

Material Master - General Data

MANDT, MATNR, MTART, MATKL, MEINS

MAKT

Material Descriptions

MANDT, MATNR, SPRAS, MAKTX

MARC

Material Master - Plant Data

MANDT, MATNR, WERKS, DISMM, BESKZ

MARD

Material Master - Storage Location Stock

MANDT, MATNR, WERKS, LGORT, LABST

MBEW

Material Valuation Data

MANDT, MATNR, BWKEY, VPRSV, VERPR, STPRS

MARM

Material Units of Measure

MANDT, MATNR, MEINH, UMREZ, UMREN

MVKE

Material Sales Data

MANDT, MATNR, VKORG, VTWEG

Transactional Tables

Table Description Key Fields

MKPF

Material Document Header

MANDT, MBLNR, MJAHR, BUDAT, USNAM

MSEG

Material Document Item

MANDT, MBLNR, MJAHR, ZEESSION, BWART, MATNR

Table Relationships

The MM module tables are related through these key fields:

MARA (Material Master - Root)
├── MAKT (Material Descriptions) ──── MANDT, MATNR
├── MARC (Plant Data) ──────────────── MANDT, MATNR
│   └── MARD (Storage Location) ────── MANDT, MATNR, WERKS
├── MBEW (Valuation) ───────────────── MANDT, MATNR
├── MARM (Units of Measure) ────────── MANDT, MATNR
├── MVKE (Sales Data) ──────────────── MANDT, MATNR
└── MKPF/MSEG (Documents) ──────────── MATNR reference

Field Handling

Field Category Transformation Examples

Client Field

Passthrough

MANDT

Key Fields

Passthrough

MATNR, WERKS, LGORT

Organizational

Passthrough

MTART, MATKL, DISMM, BESKZ

Manufacturer Data

Unique Hashing

MFRNR, MFRPN

Identifiers

Unique Hashing

EAN11, DISPO, EKGRP

Descriptions

Redaction

MAKTX (first 4 chars)

Quantities

Noising

LABST, MENGE

Pricing

Noising

STPRS, VERPR, DMBTR

Geographic

Enum Hashing

HERKL (Country)

Financial Accounting (FI)

The FI module covers general ledger, accounts payable, and accounts receivable. Configure via YAML workflow definitions.

Key Tables

Table Description

BKPF

Accounting Document Header

BSEG

Accounting Document Segment

SKA1

G/L Account Master (Chart of Accounts)

SKB1

G/L Account Master (Company Code)

LFA1

Vendor Master (General Section)

LFB1

Vendor Master (Company Code)

KNA1

Customer Master (General Data)

KNB1

Customer Master (Company Code)

Controlling (CO)

The CO module covers cost center accounting, profitability analysis, and internal orders. Configure via YAML workflow definitions.

Key Tables

Table Description

CSKS

Cost Center Master Data

CSKA

Cost Elements (Chart of Accounts)

CEPC

Profit Center Master Data

COSP

CO Object: Cost Totals for External Postings

Human Capital Management (HCM)

The HCM module covers employee master data, organizational management, and payroll. Configure via YAML workflow definitions.

Key Tables

Table Description

PA0001

Infotype 0001 - Organizational Assignment

PA0002

Infotype 0002 - Personal Data

PA0008

Infotype 0008 - Basic Pay

HRP1000

HR Master - Object Definitions

HCM data is particularly sensitive and will include enhanced data protection rules when the module becomes available.

Module Selection Best Practices

Start with One Module

Begin with a single module to:

  • Validate connectivity and permissions

  • Test transformation rules

  • Establish baseline performance metrics

Consider Dependencies

Some modules share data:

  • MM + FI: Purchase orders create FI documents

  • MM + CO: Goods movements create CO postings

  • FI + CO: Financial postings update controlling

When working with dependent modules, ensure consistency in masking rules across shared fields.

Validate Module Coverage

Before running workflows:

  1. Verify all required tables exist in source schema

  2. Confirm user has SELECT permissions on all tables

  3. Check that target schema can accommodate the data

Custom Module Configuration

All SAP modules can be configured via YAML workflow definitions. The MM module offers a guided workflow wizard for streamlined setup, while other modules use the standard workflow editor:

tables:
  - table_name_with_schema: "SCHEMA.CUSTOM_TABLE"
    transformations:
      - columns: ["MANDT"]
        params:
          type: passthrough
      - columns: ["CUSTOM_FIELD"]
        params:
          type: unique_hashing

Contact support for guidance on custom SAP module configurations.

See Also