SAP ECC Deployment

What is the purpose of SAP ECC deployment? So to find the answer to this question, we will discuss the following information about the SAP ECC deployment.

What Is SAP ECC Deployment?

SAP ECC deployment is used to deploy a software package in SAP. It includes the installation of SAP software and all necessary configurations.

It includes the development environment, data warehouse, and so on.

SAP ECC Deployment Options

There are two options for SAP ECC deployment. They are as follows:

  • Traditional SAP ECC deployment
  • SAP ECC by using SAP NetWeaver 7.0/6.0 SP6 or later versions
  • SAP ECC Deployment Processes

What Are The Three Major Processes?

There are three major processes of SAP ECC deployment. Installation Process of SAP ECC (Installation Process).

So this process is used to install and configure the software in the system or machine. 

Development Environment Configuration Process;

This process configures the development environment to develop and test the applications before they are released into production. 

Data Access Process:

This process is used to access data from any source (e.g., flat file, SQL Server, etc.) and make it available to the user in an appropriate format. It also configures the target system. 

It may also be defined as data access for integrating with batch systems, such as ERP systems. 

Data Warehouse Configuration Process:

It is a process that includes creating a data warehouse, executing a data warehouse load, and accessing data from SAP BW (Business Warehouse). 

Now let us discuss the three major processes in detail below.

Development Environment Configuration (DE) :

The DE process consists of two steps. The first step is to create a target system that can be accessed via client/server technology or Web technology (depending on the solution). 

In this step, it creates an application server and an application client when using client/server technology or Web technology. When using Web technology, it creates a virtual directory in a Web server and makes it accessible via HTTP protocol. 

When using client/server technology, it creates a dynamic link library that supports remote procedure calls (RPCs). The second step is to define security settings for remote procedure calls (RPCs.

So that only authorized users can access the system via RPCs from other applications. 

Data Access (DA) 

The DA process consists of three steps. The first step is to create classes for accessing data from various sources such as flat-file systems, SQL servers, etc.

Also, it defines parameters for accessing these sources of data. A user can use these classes to access data and convert it into the format required by the system. 

The second step is to create a target system that can access data from various sources. This step defines a target data server for accessing data from various sources.

The third step determines parameters for accessing the data from various sources. The user can use these parameters to access data from various sources using the classes created in the first step. 

Data Warehouse Configuration (DWC):

The DWC process consists of three steps. The first step is to create a master data server for accessing data from various sources. 

In this step, it creates a target system that can be accessed via client/server technology or Web technology (depending on the solution). In Web technology, it creates a virtual directory in a Web server and makes it accessible via HTTP protocol. 

When using client/server technology, it creates a dynamic link library that supports remote procedure calls (RPCs). The second step is to define security settings for remote procedure calls (RPCs. 

So that only authorized users can access the system via RPCs from other applications.