Entering content frame

Background documentation Creating Packages in Enterprise Extensions Locate the document in its SAP Library structure

Several Extensions are bundled, and thus delivered together, in each Enterprise Add-On. None of the individual Extensions show any dependencies with the others. Thus, they represent decoupled software units; each Extension is then implemented using a structure package. The R/3 Enterprise Add-On provides a container for Extensions and corresponds to a software component itself.

Example

EA-HR, EA-FIN, EA-TRAVEL, and EA_RETAIL are all examples of Extensions.

Installing or upgrading R/3 Enterprise always comprises the R/3 Enterprise Core, the R/3 Plug-In, and some Extensions that are included in an R/3 Enterprise Add-On.

To use the Extensions, you must first activate them. For more information, see Activating Enterprise Extensions.

Graphic

This graphic is explained in the accompanying text

R/3 Plug-In

The R/3 Plug-In is needed to integrate some of the mySAP solutions – such as CRM or APO – in the R/3 Enterprise Core.
In an R/3 Enterprise context, the R/3 Plug-In is also used as an interface between the Enterprise Core and the Extensions wherever they use mySAP solutions. The R/3 Plug-In also allows you simultaneously to connect several Extensions to the Enterprise Core, and thus to exchange data between them.

Note

In customer developments, the R/3 Plug-In is always needed whenever a mySAP solution needs to communicate with the Enterprise Core.

 

 

Leaving content frame