SAP ERP Glossary
Clear, jargon-free definitions of key SAP ECC, S/4HANA, and RISE terminology. No marketing speak, just practical explanations.
Filter by Category
A
ABAP Test Cockpit (ATC)
TechnicalSAP tool that analyzes custom ABAP code for S/4HANA compatibility issues, syntax errors, performance problems, and security vulnerabilities. Essential for planning Brownfield conversions.
B
Brownfield Conversion
Migration ApproachTechnical upgrade path to S/4HANA that converts your existing ECC system in-place. Same system ID, full data history, minimal business process change. Carries forward existing customization and technical debt.
C
Custom Code
TechnicalABAP programs, enhancements, user exits, and BAdIs developed specifically for your organization. Often incompatible with S/4HANA and requires remediation or replacement before conversion.
E
SAP ECC (ERP Central Component)
PlatformSAP's traditional on-premises ERP system, predecessor to S/4HANA. Mainstream maintenance ends December 31, 2027. Extended maintenance available through 2030 at additional cost.
Extended Maintenance
SupportSAP's post-2027 support option for ECC customers. Provides security patches and critical fixes but no functional enhancements. Costs approximately 3-5% of license value annually, increasing over time.
F
SAP Fiori
User InterfaceModern, web-based user interface for SAP applications. Replaces traditional SAPGUI screens with responsive, role-based apps. Limited availability on ECC (200 apps) vs S/4HANA (10,000+ apps).
G
Greenfield Implementation
Migration ApproachClean-slate S/4HANA implementation with new system ID. Start fresh with standard processes, selective data migration, and minimal technical debt. Longer timeline but transformational opportunity.
H
SAP HANA
TechnologyIn-memory database required for S/4HANA. Delivers faster processing through columnar storage and in-memory computing. ECC can run on HANA but doesn't leverage full capabilities.
I
IDoc (Intermediate Document)
IntegrationSAP's standard format for electronic data interchange. Used for asynchronous communication between SAP systems and external applications. Common integration pattern for EDI, B2B.
R
RISE with SAP
DeploymentSAP's cloud ERP subscription model bundling S/4HANA Cloud Private Edition, BTP, infrastructure, and managed services. Shifts from CapEx to OpEx but customers still own significant operational responsibilities.
S
SAP S/4HANA
PlatformSAP's next-generation ERP system built on HANA database. Simplified data model, real-time analytics, modern UX. Available on-premises, private cloud (RISE), or public cloud.
Selective Data Transition
Migration ApproachHybrid S/4HANA migration approach combining Greenfield methodology with filtered data migration. New system ID but selective historical data. Balances transformation with continuity.
Shared Responsibility Model
OperationsDivision of operational duties between SAP and customer in RISE/Private Cloud. SAP manages infrastructure; customer owns application configuration, security, monitoring, and business processes.
Simplification Item
TechnicalSAP documentation of data model changes between ECC and S/4HANA. Describes what's deprecated, replaced, or requires adjustment. Critical for planning Brownfield conversions.
T
Third-Party Support
SupportAlternative ECC maintenance from vendors like Rimini Street or Spinnaker Support. Typically 50% cheaper than SAP, with faster response times but no direct SAP relationship.