Products and Product Instances are used to describe software that SAP delivers. It’s also these entities that you need to understand to maintain your systems. In the 2nd part of my blog on landscape descriptions, we’ll talk about these entities in some detail. In doing so, we’ll have to introduce two new concepts to our simplified description given in part I, namely the reuse, versioning, and nesting of elements. These two things are important, because they define what you have to do manually when managing your systems.
In the 1st part of this landscape description blog series (see Additional Info), Products were explained with an analogy to a car. Once the roles of the entities Product, Product Instance, and Software Components are understood on this very high level, we can go into some details. Even if more similarities with cars could be found here also, we’ll be more abstract from now on.
While Products, Software Components, and Product Instances basics can be explained with a simple analogy, the assignment to Product Systems needs to be done carefully – the reason why is that we are dealing with Products in different versions, and their parts having dependencies caused by reuse, which has big advantages (obviously less versions of objects overall), but leads to some complexity by means of nesting and versioning, which turns up both in Product definitions and the Product Systems used to run Products in the landscape.
Products are applications that you buy and run to fulfill your business needs.
A Product System is a group of one to several Technical Systems used to install a Product Version.
Figure 1: Product Versions A and J installed with some overlap on two Technical Systems ABP and JAP and being handled in two Product Systems ABP and JVP
Here’s the situation in figure 1 explained:
The including of Product Instances can be done explicitly or implicitly. Details are explained later.
Even, if Product Instances of several Product Versions are installed on the same Technical System, in maintenance you address one Product Version you want to maintain.
Example: SAP ERP 6.0 shall get SAPEHP 4, so underlying SAP NetWeaver 7.0 needs to get EHP1.
Therefore, the assignment of Technical Systems and Product Instances to Product Systems needs to be correct. This will help you to achieve this:
Products, as we learned, are made of Product Instances. A Product is somewhat abstract, for example. In real life you’ll always deal with a Product Version. Therefore, it’s needed and sufficient to choose the right product version. Also, even if in one Product System more than one Product can be handled, in one Product System only one version of each Product can exist.
SAP enhancement packages (EHPs😞 EHPs define functions that can be added to an existing Product Version. Therefore, when installing an EHP, you need to have both, the Standalone Product Version (for example SAP ERP 6.0) and the EHP version (for example SAP EHP 4 for SAP ERP😞 So in that case, both of them need to be marked as installed in the SAP Solution Manager. This is true for EHPs for SAP ERP, SAP CRM, SAP SRM, and SAP SCM.
As said before, Product Instances can contain other Product Instances – they can do so explicitly or implicitly. Implicit containing you find for Product Instances of one Product,
Figure 2: Product A contains Product Instances A, B, C, D, and contains PI 1 /2 of Product B implicitly.
Example of “implicitly contained Product Instances”:
Product Instance A belonging to SAP ERP 6.0 reusing Product Instance B of SAP NetWeaver 7.0 (AS ABAP and AS Java)
That means that:
Figure 3: Product Instance X contains Product Instances O, P, and Q; PI Q contains PIs R, L, M explicitly.
Example of “explicitly included Product Instances”:
Product Instance X belonging to Product SAP ERP 6.0; PI X = ECC Server reusing
Product Instance Y belonging to Product SAP NetWeaver 7.0, PI Y = AS ABAP
In any case, when dealing with explicitly contained Product Instances, you need not assign the explicitly contained Product Instance. The reason is, that explicit containment is found, where a Product Instance from a different Product is used. The dependency is such that they need to run on the same Technical System. An example for explicitly contained Product Instances you find in SAP CRM making use of Product Instance SAP NetWeaver AS ABAP.
Functionally Equivalent Instances (FEIs) are Product Instances, which have been modified without changing their function (often to deal with an update of lower layers in your system) – for more information see Data Adjustment in SMSY after a Upgrade of an SAP NetWeaver Hub System.
Next Steps in Understanding Landscape Descriptions
I hope this will help clarify things. In the next blog you will get some more concrete insights into the tools and processes you have to use to manage the landscape description of your company.