Skip to Content

The technical configuration is an elementary part of setting up SAP Hybris Marketing. For example, on the one hand you have to perform post-installation activities to bring a newly installed system into operation. On the other hand, during the lifecycle of a system, technical parameters have to be set and adapted.

This blog will give you an overview of how the technical configuration works with respect to transport requests. The Technical Configuration Cockpit handles the technical configuration in Hybris Marketing during an installation. How transports are handled depends on the entry in the field Role of System. In the scenario of  “Essentials” you have the following options:

  • Development System: If you start the task list “Essentials” in a development or a configuration system, the technical configuration creates objects and customizing and writes them to transport request.
  • Productive System: If you start the task list “Essentials” in a production or a quality system, the technical configuration does not create any objects or customizing, but the system is able to import objects via a transport request from a development or configuration system.
  • Other System: If you start the task list “Essentials” in another system (such as a demo system), the system creates objects according to your configuration settings in the wizard, but does not write them to a transport request.


RoleOfSystem.PNG



Development System

If the entry in the field Role of System is “Development System”, objects are created by the technical configuration and written to transports. In the following table you can see which objects are created in which step and written to which transport.

Type of Transport

Name of Transport

Objects of Transport

Generated by Step

Customizing Requests

Common Customizing Activities

Customizing of System Alias and Segmentation Profiles

Routing of ODATA Services – relation between ODATA and System Alias

Initialize SAP Audience Discovery and Targeting and Generate OData Services

Workbench Requests

Activated BI Queries

Elements of the Query Builder

Activate and Transport BI Content

Workbench Requests

Common Workbench Objects

SAP Gateway Metadata about Model and Service Group, required IFC nodes and Services Data Provider Implementation Definition

Generate OData Services

In addition to the transports in the table, there should also be a workbench transport containing the packages for OData services and BI content. These packages were created manually as described in the installation guide.

After you have successfully finished the task list “Essential”, go to transaction SE09, and release and transport in the following sequence:

  1. Workbench Request: Package for OData service and BI content – created manually
  2. Customizing Request: Common Customizing Activities
  3. Common Workbench Objects
  4. Activated BI Queries


Quality or Productive System


Before you start the task list “Essential” you have to take care of the import of the transports regarding technical configuration.

As there are dependencies and preconditions, the sequence of the transport import plays a role. Therefore please perform following steps:


a) Go to transaction STMS_IMPORT and import the transports in the following sequence

1) Workbench Request: Package for OData service and BI content – created manually

2) Customizing Request: Common Customizing Activities

3) Workbench Request:  Common Workbench Objects


b) Execute the Technical Configuration Cockpit using transaction CUAN_INITIAL_SETUP

Choose scenario “Essential” and enter “Prod. System” in field Role of System.

As a consequence, some tasks are not processed anymore during the technical configuration because some objects are not created but are imported by transports. E.g. the step Generate OData Services is skipped.

c) Go to transaction STMS and import the transport

  • Workbench Request: Activated BI Queries

The activation of BI content presupposes that HANA content is active. For this reason this transport need to be imported after the technical configuration.


In the figure below you can see an overview of how the transport management of the technical configuration works for Hybris Marketing in a typical three-landscape environment.

Transport_Landscape.PNG



We have noticed in some cases that the customizing requests were not imported to a business client, but only to client 000. Therefore it’s important to make sure that customizing transport were imported to the correct client. You can find more information about this at SAP Help Portal in chapter Handling Target Clients.

Other System

If you want set up your Hybris Marketing System as a standalone system, e.g. a demo system, then choose Other System for Role of System. The system creates all the required objects according to your configuration settings, but does not write them to a transport request.


Demo_Landscpe.PNG


To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply