Module 3: Creating Your First Mass Transfer ID

This module covers creating and configuring Mass Transfer IDs (MT_ID) - the core configuration container for SLT replication scenarios. You'll create your first replication configuration from source to target.

1. Understanding Mass Transfer ID

1.1 What is a Mass Transfer ID?

A Mass Transfer ID (MT_ID) is a configuration container that defines:

Source system connection
Target system connection
List of tables to replicate
Transformation rules
Replication settings
Monitoring metadata

Think of MT_ID as...

A project workspace that groups all configuration elements for a specific replication scenario (e.g., "ECC Sales Tables to HANA").

1.2 MT_ID Architecture

graph TB
    A[Mass Transfer ID<br/>MT_ECC_SALES_01] --> B[Source Connection<br/>RFC: SRC_ECC]
    A --> C[Target Connection<br/>HANA: TGT_HANA]
    A --> D[Table List<br/>VBAK, VBAP, KNA1...]
    A --> E[Transformations<br/>Field Mappings, Filters]
    A --> F[Runtime Settings<br/>Jobs, Batch Size]
    A --> G[Monitoring Data<br/>Status, Statistics]
    
    style A fill:#667eea
    style D fill:#764ba2

1.3 Naming Conventions

Best Practices for MT_ID Names:

Pattern	Example	Use Case
`<SOURCE>_<TARGET>_<AREA>`	`ECC_HANA_SD`	Sales & Distribution
`<SOURCE>_<TARGET>_<MODULE>`	`S4_BW4_FI`	Finance module
`<SOURCE>_<TARGET>_<PROCESS>`	`ECC_HANA_REPL`	General replication
`<PROJECT>_<SEQ>`	`PROJ123_01`	Project-based

Naming Rules:

Maximum 16 characters
Alphanumeric and underscore only
Case-insensitive
Must be unique in SLT system

2. Accessing SLT Configuration Cockpit

2.1 Transaction Codes

Transaction	Description	Primary Use
`LTRC`	SLT Replication Configuration	Create/manage MT_IDs
`LTR`	Legacy SLT Transaction	Older interface
`LTRS`	SLT Replication Server	Backend configuration
`/DMIS/MASST`	Mass Transfer Administration	Direct table access

Recommended Transaction

Use LTRC for all configuration tasks. It provides the most user-friendly interface with guided workflows.

2.2 LTRC Cockpit Overview

Launch: Transaction LTRC

Main Screen Sections:

┌─────────────────────────────────────────────────────┐
│  SAP SLT Configuration Cockpit (LTRC)              │
├─────────────────────────────────────────────────────┤
│  Configuration   Display   Utilities   Help         │
├──────────────┬──────────────────────────────────────┤
│ MT_ID List   │  Configuration Details               │
│              │                                       │
│ ► ECC_HANA   │  Source: SRC_ECC_PRD                │
│   S4_BW4_FI  │  Target: TGT_HANA_PRD               │
│   TEST_01    │  Tables: 25                          │
│              │  Status: ● Replicating               │
│              │  Records Transferred: 1,234,567      │
│              │                                       │
│  [+ Create]  │  [Tables] [Transformations] [Monitor]│
└──────────────┴──────────────────────────────────────┘

3. Creating a Mass Transfer ID - Step by Step

3.1 Step 1: Launch Creation Wizard

Navigate:

Transaction: LTRC
Click button: "Create" or press F5
Creation wizard opens

3.2 Step 2: Define Basic Settings

Configuration Screen 1: Basic Data

Mass Transfer ID: ECC_HANA_01
Description: ECC Production to HANA - Initial Setup

Field Details:

Field	Value	Notes
MT_ID	`ECC_HANA_01`	Unique identifier
Description	`ECC to HANA Replication`	Meaningful description
Schema Name	`SLTREPL`	Target HANA schema
Job Name Prefix	`DMIS_ECC`	Background job prefix

Important

Once created, MT_ID cannot be renamed. Choose wisely!

3.3 Step 3: Configure Source System

Configuration Screen 2: Source System

Connection Type: ● RFC Connection
                 ○ Database Connection
                 ○ File System

RFC Destination: SRC_ECC_PRD
Test Connection: [Click to test]

Source System Parameters:

Parameter	Value	Purpose
RFC Destination	`SRC_ECC_PRD`	Created in SM59
Client	`100`	Source client
Logical System	`ECCPRDCLNT100`	Logical system name
Read Package Size	`50000`	Rows per fetch

Test Connection:

Click "Test Connection" button

✅ Success:
   - Response time: 234 ms
   - User: SLTUSER
   - Authorization: OK

❌ Failure: Check RFC destination (SM59)

3.4 Step 4: Configure Target System

Configuration Screen 3: Target System

Target Type: ● SAP HANA Database
             ○ SAP BW/4HANA System
             ○ SAP Data Warehouse Cloud
             ○ Generic Database

Connection Name: TGT_HANA_PRD
Database Schema: SLTREPL
Test Connection: [Click to test]

Target System Parameters:

Parameter	Value	Purpose
Connection Name	`TGT_HANA_PRD`	From DBACOCKPIT
Host	`hana-prd.company.com`	HANA server
Port	`30015`	SQL port
Database	`HDB`	HANA database name
User	`SLTREPL`	Replication user
Schema	`SLTREPL`	Target schema
Write Package Size	`10000`	Bulk insert size

3.5 Step 5: Advanced Settings

Configuration Screen 4: Advanced Settings

Performance Settings:
  ☑ Use Bulk Insert
  ☑ Enable Read/Write Buffering
  ☐ Enable Data Validation (slower)
  
Parallel Processing:
  Number of Jobs: [8]
  Load Distribution: ● Automatic  ○ Manual
  
Error Handling:
  ☑ Stop on Critical Errors
  ☑ Retry Failed Records (Max: 3 attempts)
  ☑ Send Email Notification
  
Logging:
  Logging Level: ● Standard  ○ Verbose  ○ Debug
  Retention Period: [7] days

Recommended Settings:

Setting	Small Systems	Medium Systems	Large Systems
Number of Jobs	4	8-12	16-32
Read Package Size	10,000	50,000	100,000
Write Package Size	5,000	10,000	20,000
Logging Retention	14 days	7 days	3 days

3.6 Step 6: Review and Create

Configuration Screen 5: Summary

Review Configuration:

Mass Transfer ID: ECC_HANA_01
Description: ECC Production to HANA - Initial Setup

Source:
  System: SRC_ECC_PRD (RFC)
  Client: 100
  Logical System: ECCPRDCLNT100

Target:
  System: TGT_HANA_PRD (HANA)
  Schema: SLTREPL
  Host: hana-prd.company.com:30015

Settings:
  Parallel Jobs: 8
  Read Package: 50,000 rows
  Write Package: 10,000 rows
  Error Handling: Enabled

[◄ Back]  [Create and Activate]  [Cancel]

Click: "Create and Activate"

3.7 Creation Process Flow

sequenceDiagram
    participant User as Administrator
    participant SLT as SLT System
    participant Source as Source ECC
    participant Target as Target HANA
    
    User->>SLT: Create MT_ID
    SLT->>SLT: Validate configuration
    SLT->>Source: Test RFC connection
    Source-->>SLT: ✅ Connection OK
    SLT->>Target: Test DB connection
    Target-->>SLT: ✅ Connection OK
    SLT->>Target: Create schema (if not exists)
    Target-->>SLT: Schema ready
    SLT->>SLT: Create logging tables
    SLT->>SLT: Initialize replication jobs
    SLT-->>User: MT_ID created successfully

4. Post-Creation Verification

4.1 Verify MT_ID Status

Check in LTRC:

Transaction: LTRC
Select: ECC_HANA_01

Status Indicators:
├── Overall Status: ● Green (Active)
├── Source Connection: ✅ Connected
├── Target Connection: ✅ Connected
├── Logging Tables: ✅ Created
├── Replication Jobs: ✅ Initialized
└── Error Queue: ✅ Empty

4.2 Verify Database Objects

Check Target HANA Schema:

-- Connect to HANA
hdbsql -n hana-prd.company.com:30015 -u SLTREPL

-- Check schema exists
SELECT SCHEMA_NAME FROM SCHEMAS WHERE SCHEMA_NAME = 'SLTREPL';

-- Check control tables
SELECT TABLE_NAME FROM TABLES 
WHERE SCHEMA_NAME = 'SLTREPL' 
AND TABLE_NAME LIKE '/DMIS/%';

-- Expected control tables:
/DMIS/CL_CONTEXT   -- MT_ID configuration
/DMIS/CL_TABLES    -- Table list
/DMIS/CL_TRANS     -- Transformation rules
/DMIS/CL_MONITOR   -- Monitoring data

4.3 Verify Logging Tables in Source

Check Source System:

Transaction: SE11 (Data Dictionary) in source system

Logging Tables Created:
├── /DMIS/LOG_<TABNAME>  -- Change log table
├── /DMIS/DEL_<TABNAME>  -- Deletion log table
└── Database Triggers     -- Automatic change capture

Example for table MARA:
/DMIS/LOG_MARA    -- Material changes
/DMIS/DEL_MARA    -- Material deletions

Logging Table Structure

Each source table gets corresponding logging tables created automatically during initial load activation.

5. Managing Mass Transfer IDs

5.1 Viewing Existing MT_IDs

Transaction: LTRC

Display Options:

View Mode:
● All MT_IDs
○ My MT_IDs (created by current user)
○ Active Only
○ Inactive Only
○ With Errors

Columns Displayed:
├── MT_ID
├── Description
├── Source System
├── Target System
├── Status
├── Tables Count
├── Records Transferred
├── Last Run Time
└── Created By

5.2 Modifying MT_ID Configuration

Edit Existing MT_ID:

Transaction: LTRC
Select: ECC_HANA_01
Menu: Configuration → Edit

Modifiable Settings:
✅ Description
✅ Advanced settings (jobs, package size)
✅ Error handling options
✅ Logging retention
✅ Email notifications

Non-Modifiable Settings:
❌ MT_ID name
❌ Source system (after tables added)
❌ Target system (after tables added)
❌ Schema name (after activation)

Changing Active MT_ID

To change source/target system, you must:

Stop all replication
Remove all tables
Deactivate triggers
Modify configuration
Re-add tables and restart

5.3 Deactivating and Deleting MT_IDs

Deactivation Process:

Transaction: LTRC
Select: ECC_HANA_01
Menu: Configuration → Deactivate

Steps:
1. Stop all replication jobs
2. Deactivate database triggers
3. Clear logging tables
4. Update status to "Inactive"

Duration: 5-10 minutes (depending on table count)

Deletion Process:

Transaction: LTRC
Select: ECC_HANA_01
Menu: Configuration → Delete

Pre-requisites:
☑ MT_ID must be deactivated
☑ All tables removed
☑ No pending replications
☑ Logging tables empty

Deletion removes:
├── MT_ID configuration
├── Transformation rules
├── Monitoring history
├── Target schema (optional)
└── Logging tables (optional)

Irreversible Action

Deletion is permanent. Configuration cannot be recovered. Export configuration before deletion if needed.

6. Multiple MT_ID Scenarios

6.1 When to Use Multiple MT_IDs

Scenario 1: Separate Business Areas

MT_ID_FI_01  →  Finance tables
MT_ID_SD_01  →  Sales tables
MT_ID_MM_01  →  Material tables

Benefit: Isolated management, independent scheduling

Scenario 2: Different Targets

MT_ID_HANA_01  →  HANA production
MT_ID_BW4_01   →  BW/4HANA analytics
MT_ID_DWC_01   →  Data Warehouse Cloud

Benefit: Same source, multiple destinations

Scenario 3: Development/Test/Production

MT_ID_DEV_01  →  Development target
MT_ID_QAS_01  →  Quality target
MT_ID_PRD_01  →  Production target

Benefit: Separate environments, controlled promotion

6.2 MT_ID Management Strategy

graph TB
    A[Source: ECC Production] --> B[MT_ID_SALES_01]
    A --> C[MT_ID_FINANCE_01]
    A --> D[MT_ID_LOGISTICS_01]
    
    B --> E[HANA Schema: SALES]
    C --> F[HANA Schema: FINANCE]
    D --> G[HANA Schema: LOGISTICS]
    
    E --> H[Analytics: Sales Dashboard]
    F --> I[Analytics: Financial Reports]
    G --> J[Analytics: Supply Chain]
    
    style B fill:#667eea
    style C fill:#667eea
    style D fill:#667eea

Design Principles:

Logical separation by business area
Independent monitoring per MT_ID
Granular error handling per functional area
Flexible scheduling per workload
Easier troubleshooting with focused scope

7. MT_ID Configuration Backup and Transport

7.1 Export MT_ID Configuration

Manual Export:

Transaction: LTRC
Select: ECC_HANA_01
Menu: Utilities → Export Configuration

Export Options:
☑ Basic configuration
☑ Table list
☑ Transformation rules
☑ Advanced settings
☐ Monitoring data (not recommended)

Output File: ECC_HANA_01_config.xml
Location: /usr/sap/SLT/D00/export/

Programmatic Export (ABAP):

DATA: lv_mt_id TYPE dmis_mt_id VALUE 'ECC_HANA_01',
      lt_config TYPE dmis_config_export,
      lv_xml    TYPE string.

CALL FUNCTION '/DMIS/CONFIG_EXPORT'
  EXPORTING
    iv_mt_id  = lv_mt_id
  IMPORTING
    et_config = lt_config
    ev_xml    = lv_xml.

" Save to file
CALL FUNCTION 'GUI_DOWNLOAD'
  EXPORTING
    filename = 'C:\temp\mt_id_config.xml'
  TABLES
    data_tab = lv_xml.

7.2 Import MT_ID Configuration

Import Process:

Transaction: LTRC
Menu: Utilities → Import Configuration

Steps:
1. Select XML file
2. Review configuration preview
3. Map source/target systems (if different)
4. Select options:
   ☑ Create new MT_ID
   ☑ Import table list
   ☑ Import transformations
   ☐ Overwrite existing (dangerous)
5. Execute import

7.3 Transport Between Systems

Transport Path:

DEV (SLT_DEV) →  Transport  →  QAS (SLT_QAS)  →  Transport  →  PRD (SLT_PRD)

Create Transport Request:

Transaction: LTRC
Select: ECC_HANA_01
Menu: Utilities → Create Transport

Transport Type:
● Workbench Request (development objects)
○ Customizing Request (configuration)

Transport Includes:
├── MT_ID configuration
├── Table list
├── Transformation rules
├── Advanced settings
└── Database connection details

Transport Number: DEVK900123

Release and Import:

Transaction: SE09 (Transport Organizer)
Release transport in DEV
Import to QAS using STMS
Test in QAS
Import to PRD using STMS

8. Best Practices for MT_ID Configuration

8.1 Naming and Documentation

✅ Use descriptive names:

Good: ECC_HANA_SALES_MASTER
Bad:  CONFIG_001

✅ Maintain documentation field:

Description: "ECC Sales master data replication to HANA
              for real-time dashboard. Includes VBAK, VBAP,
              KNA1, MARA. Runs 24x7. Contact: John Doe"

✅ Use consistent naming across environments:

DEV: ECC_HANA_SALES_D
QAS: ECC_HANA_SALES_Q
PRD: ECC_HANA_SALES_P

8.2 Performance Optimization

Right-size parallel jobs:

Data Volume/Day	Recommended Jobs	CPU Allocation
< 1 GB	4-6	4 cores
1-10 GB	8-12	8 cores
10-50 GB	16-24	16 cores
> 50 GB	32+	32 cores

Optimize package sizes:

Small rows (&lt;20 fields): 50,000-100,000
Medium rows (20-50 fields): 10,000-50,000
Large rows (&gt;50 fields): 5,000-10,000

8.3 Security Considerations

✅ Use dedicated technical users:

Source: SLTREPL_SRC (minimal read access)
Target: SLTREPL_TGT (write to specific schema only)

✅ Restrict access to sensitive tables:

Do not replicate:
- Password tables (USR02, USH02)
- Security audit logs
- Personal identifiable information (PII) without approval

✅ Enable encryption for connections:

RFC: Use SNC (Secure Network Communication)
HANA: Use SSL/TLS for database connections

9. Troubleshooting MT_ID Creation

9.1 Common Errors

Error 1: RFC Destination Not Found

Error: RFC destination SRC_ECC_PRD does not exist
Solution:
  1. Transaction SM59 in SLT system
  2. Create RFC destination
  3. Test connection
  4. Retry MT_ID creation

Error 2: Insufficient Authorization

Error: User SLTUSER has insufficient authorization
Solution:
  1. Transaction SU53 (Authorization Check) in source
  2. Check missing authorizations
  3. Add role with S_TABU_DIS, S_RFC
  4. Retry connection test

Error 3: Schema Already Exists

Error: Schema SLTREPL already exists with different owner
Solution:
  1. Choose different schema name
  OR
  2. Drop existing schema (if safe):
     DROP SCHEMA SLTREPL CASCADE;
  3. Retry MT_ID creation

Error 4: Database Connection Failed

Error: Cannot connect to HANA database
Solution:
  1. Verify HANA is running
  2. Check network connectivity: telnet hana-prd 30015
  3. Verify user password
  4. Check HANA user has required grants

10. Monitoring MT_ID Health

10.1 Dashboard View

Transaction: LTRC → Select MT_ID → Monitor

┌─────────────────────────────────────────────┐
│  MT_ID: ECC_HANA_01    Status: ● Active    │
├─────────────────────────────────────────────┤
│  Source: SRC_ECC_PRD      ✅ Connected     │
│  Target: TGT_HANA_PRD     ✅ Connected     │
│                                              │
│  Tables: 25 / 25 active                     │
│  Records Today: 1,234,567                   │
│  Avg Latency: 0.8 seconds                   │
│  Errors: 0                                   │
│                                              │
│  [Tables] [Performance] [Errors] [Logs]     │
└─────────────────────────────────────────────┘

10.2 Key Metrics to Monitor

Metric	Healthy Range	Action If Outside
Latency	< 5 seconds	Check network, jobs
Error Rate	< 0.1%	Review error logs
Logging Table Size	< 10 GB	Increase cleanup frequency
Job Utilization	60-80%	Adjust job count
Memory Usage	< 80%	Increase memory or optimize

Summary

In this module, you learned:

✅ What Mass Transfer IDs are and their purpose
✅ Step-by-step MT_ID creation process
✅ Configuring source and target systems
✅ Advanced settings and optimization
✅ Managing multiple MT_IDs
✅ Backup, export, and transport procedures
✅ Best practices for configuration
✅ Troubleshooting common issues
✅ Monitoring MT_ID health

What's Next?

In Module 4, you'll learn:

Adding tables to MT_ID
Table selection strategies
Filtering source data
Performing initial load
Monitoring load progress

Checkpoint

Before proceeding, ensure you have successfully created at least one MT_ID and verified all connection tests pass.

1. Understanding Mass Transfer ID​

1.1 What is a Mass Transfer ID?​

1.2 MT_ID Architecture​

1.3 Naming Conventions​

2. Accessing SLT Configuration Cockpit​

2.1 Transaction Codes​

2.2 LTRC Cockpit Overview​

3. Creating a Mass Transfer ID - Step by Step​

3.1 Step 1: Launch Creation Wizard​

3.2 Step 2: Define Basic Settings​

3.3 Step 3: Configure Source System​

3.4 Step 4: Configure Target System​

3.5 Step 5: Advanced Settings​

3.6 Step 6: Review and Create​

3.7 Creation Process Flow​

4. Post-Creation Verification​

4.1 Verify MT_ID Status​

4.2 Verify Database Objects​

4.3 Verify Logging Tables in Source​

5. Managing Mass Transfer IDs​

5.1 Viewing Existing MT_IDs​

5.2 Modifying MT_ID Configuration​

5.3 Deactivating and Deleting MT_IDs​

6. Multiple MT_ID Scenarios​

6.1 When to Use Multiple MT_IDs​

6.2 MT_ID Management Strategy​

7. MT_ID Configuration Backup and Transport​

7.1 Export MT_ID Configuration​

7.2 Import MT_ID Configuration​

7.3 Transport Between Systems​

8. Best Practices for MT_ID Configuration​

8.1 Naming and Documentation​

8.2 Performance Optimization​

8.3 Security Considerations​

9. Troubleshooting MT_ID Creation​

9.1 Common Errors​

10. Monitoring MT_ID Health​

10.1 Dashboard View​

10.2 Key Metrics to Monitor​

Summary​

What's Next?​