SAP SuccessFactors Landscape Explained: Environments, Instances, Tenants, Provisioning, and Data Centers

When I started learning SAP SuccessFactors, I often came across terms such as DEV, TEST, PROD, PREVIEW, Tenant, Environment, Provisioning, and Data Centre.

At first glance, many of these terms seem similar. However, understanding the relationship between them is essential for every SuccessFactors consultant.

In this blog, we’ll break down these concepts step by step using simple examples and analogies.

SAP Lansdcape

What is a SuccessFactors Landscape?

A SuccessFactors Landscape refers to the collection of systems available to a customer for:

• Development
• Testing
• Validation
• Live business operations

Instead of making changes directly in the live system, organizations maintain multiple systems, each serving a specific purpose.

A typical landscape may contain:

• DEV (Development)
• TEST (Testing/UAT)
• PREVIEW
• PROD (Production)

Environment vs Instance: The Most Important Concept

One of the most common misconceptions among beginners is treating Environment and Instance as the same thing.

They are not.

What is an Environment?

An Environment is a category in which a tenant resides.

SAP SuccessFactors provides two primary environments:

Productive Environment

This environment contains systems used for business operations and customer testing activities.

Preview Environment

This environment receives SAP upgrades before the Productive Environment.

Customers use it to test upcoming releases and identify any potential impact before those changes reach Production.

What is an Instance (Tenant)?

An Instance, also known as a Tenant, is the actual SuccessFactors system that users access.

Each tenant has:

• Its own URL
• Its own database
• Its own configuration
• Its own data

Examples:

• DEV Tenant
• TEST Tenant
• PROD Tenant
• PREVIEW Tenant

Simple Analogy

Think of a university campus.

Environment = Campus

Instance/Tenant = Building

A campus can contain multiple buildings, and each building serves a different purpose.

Similarly, an environment can contain multiple tenants.

Understanding the Different Instances

DEV (Development) Instance

The Development instance is used by consultants and administrators for:

• Configuration
• Development
• Initial testing
• Troubleshooting

This is where new configurations are built before moving to higher environments.

Think of DEV as the workshop where solutions are created.

TEST Instance

The Test instance is used for:

• User Acceptance Testing (UAT)
• Regression testing
• Business validation
• Training activities

Business users typically validate changes here before deployment to Production.

Think of TEST as the quality assurance area.

PROD (Production) Instance

The Production instance is the live system used by employees, managers, and HR teams.

Examples include:

• Employee transactions
• Organizational changes
• Workflows
• HR processes

Because PROD contains live business data, changes are carefully controlled.

Think of PROD as the actual workplace.

PREVIEW Instance

The Preview instance exists within the Preview Environment.

Its primary purpose is to:

• Test upcoming SAP releases
• Validate integrations
• Validate custom configurations
• Identify release-related issues

SAP upgrades Preview systems several weeks before Production systems.

This gives customers time to prepare for upcoming changes.

Think of PREVIEW as an early-access version of SuccessFactors.

Why Do Some Customers Use PREVIEW for Testing?

Many customers have a landscape such as:

DEV → PREVIEW → PROD

Instead of:

DEV → TEST → PROD

In these cases, there is no dedicated TEST tenant.

As a result, the PREVIEW tenant is often used for:

• User Acceptance Testing
• Business validation
• Release testing

This is why many consultants casually refer to PREVIEW as the testing system.

Technically:

• PREVIEW describes the environment.
• TEST describes the purpose of the system.

However, in many real-world implementations, the Preview tenant serves as the testing system.

Common SuccessFactors Landscapes

Three-System Landscape

DEV → PREVIEW → PROD

Responsibilities:

DEV

• Configuration
• Development

PREVIEW

• Testing
• UAT
• Release validation

PROD

• Live operations

This is a common landscape among small and medium-sized organizations.

Four-System Landscape

DEV → TEST → PROD + PREVIEW

Responsibilities:

DEV

• Development

TEST

• UAT
• Business testing
• Regression testing

PREVIEW

• SAP release testing

PROD

• Live operations

This provides clear separation between business testing and release testing.

What is Provisioning?

Provisioning is neither an Environment nor an Instance.

Provisioning is a backend administration tool used to manage SuccessFactors tenants.

It allows administrators and implementation partners to:

• Configure tenant settings
• Enable features
• Schedule jobs
• Monitor integrations
• Perform tenant-related activities

Think of Provisioning as the control room that manages the entire landscape.

Understanding Data Centers

Now that we understand Environments and Instances, let’s introduce another important concept: Data Centers.

Many beginners mistakenly think that Data Centers and Environments are the same thing.

They are not.

What is a Data Center?

A Data Centre is the physical location where SAP hosts customer systems.

It contains:

• Servers
• Storage
• Network infrastructure
• Security controls
• Backup and recovery systems

Your SuccessFactors tenant runs inside an SAP data center.

Relationship Between Data Centers, Environments, and Instances

The relationship can be visualized as:

Data Center ↓ Environment ↓ Instance (Tenant)

For example:

Data Center DC12 ↓ Productive Environment ↓ DEV, TEST, PROD

Why Are Preview Systems Hosted Separately?

SAP upgrades Preview environments before Productive environments.

This allows customers to:

• Test new SAP features
• Validate integrations
• Identify issues before Production upgrades

A simplified example:

Production Data Center

• DEV
• TEST
• PROD

Preview Data Center

• PREVIEW

When SAP releases a Half Yearly (1H and 2H ) update:

1. Preview systems are upgraded first.
2. Customers perform testing.
3. Productive systems are upgraded later.

This approach significantly reduces upgrade risk.

Key Takeaways

✔ Environment and Instance are different concepts.

✔ Productive and Preview are Environments.

✔ DEV, TEST, PROD, and PREVIEW are Instances (Tenants).

✔ DEV is used for development and configuration.

✔ TEST is used for business validation and UAT.

✔ PROD is the live business system.

✔ PREVIEW is used to validate upcoming SAP releases.

✔ Many customers use PREVIEW as their testing system when a dedicated TEST tenant is not available.

✔ Provisioning is a backend administration tool used to manage tenants.

✔ Data Centers are the physical SAP hosting locations where customer tenants reside.

Understanding these concepts provides a strong foundation for learning advanced SuccessFactors topics such as Data Models, MDF Objects, Foundation Objects, Role-Based Permissions, Integrations, and Employee Central architecture.