bb installation guidesapidp/... · web viewfor bi content bundle activation:...

SAP Hybris Marketing 1.2 (1511)

January 2016

English

SAP Landscape Transformation Replication Server Settings (CET)

SAP SEDietmar-Hopp-Allee 1669190 WalldorfGermany

Building Block Configuration Guide

SAP Best Practices SAP Landscape Transformation Replication Server Settings (CET): Configuration Guide

Copyright

© 2015 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. Please see http://global.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP SE or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.

© SAP SEPage of


Icons

Icon Meaning

Caution

Example

Note

Recommendation

Syntax

Typographic Conventions

Type Style Description

Example text Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths, and options.Cross-references to other documentation.

Example text Emphasized words or phrases in body text, titles of graphics and tables.

EXAMPLE TEXT Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.

Example text Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade, and database tools.

EXAMPLE TEXT Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.

Example text Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.

© SAP SEPage of


Content

1 Purpose............................................................................................................................. 52 Preparation........................................................................................................................ 5

2.1 Identifying the Deployment Scenarios.....................................................................52.2 Prerequisites............................................................................................................52.3 Users and Authorizations.........................................................................................6

3 Configuration.....................................................................................................................93.1 SAP ERP Settings...................................................................................................9

3.1.1 Creating Authorization Profiles (SAP ERP).........................................................93.1.2 Creating an RFC User (SAP ERP)....................................................................10

3.2 SAP CRM Settings................................................................................................113.2.1 Creating Authorization Profiles (SAP CRM)......................................................113.2.2 Creating RFC User for SAP LT (SAP CRM)......................................................12

3.3 SAP Landscape Transformation (SAP LT) General Settings.................................133.3.1 Activating SAP LT Service.................................................................................133.3.2 Creating Authorization Profile............................................................................143.3.3 Creating RFC User for SAP Hybris Marketing to access SAP LT.....................15

3.4 SAP Landscape Transformation (SAP LT) Settings for SAP ERP.........................163.4.1 Creating RFC Destination for SAP ERP System (in SAP LT)............................163.4.2 Creating SAP LT Connection Definition for SAP ERP (in SAP LT)...................18

3.5 SAP Landscape Transformation (SAP LT) Settings for SAP CRM........................193.5.1 Creating RFC Destination for SAP CRM System (in SAP LT)...........................193.5.2 Creating SAP LT Connection Definition for SAP CRM (in SAP LT)...................20

3.6 SAP HANA System Settings..................................................................................223.6.1 Assigning Roles to the SAP ERP Replication User...........................................223.6.2 Assigning Roles to the SAP CRM Replication User..........................................22

3.7 SAP Hybris Marketing Settings..............................................................................233.7.1 Creating RFC Destination for the SAP ERP System.........................................233.7.2 Creating RFC Destination to SAP LT System for SAP ERP..............................243.7.3 Creating RFC Destination to SAP LT System for SAP CRM.............................26

© SAP SEPage of


SAP Landscape Transformation Replication Server Settings

1 PurposeIf you want to replicate data from SAP ERP, or SAP CRM, or both via SAP Landscape Transformation Replication Server (SAP LT) into SAP Hybris Marketing, first implement the settings described in this building block.This building block provides the prerequisite settings for data replication required before executing the initial setup task list in SAP Hybris Marketing. The initial setup tasklist execution is described in the Initial Setup of Hybris Marketing (CED) building block.

If you only want to replicate data from either SAP ERP or SAP CRM, ignore the chapters pointing to the system you do not use.

If you do not want to replicate data via SAP LT at all, for example because you use the embedded deployment option or because you only want to load non-SAP data, this building block is not relevant for you.

2 Preparation2.1 Identifying the Deployment Scenarios Depending on the system landscape you want to realize, multiple deployment scenarios are available for each source system. For a detail description of the deployment scenarios, read the Installation Guide in section 3 (Deployment Scenarios): http://help.sap.com/mkt ® Installation and Upgrade Information ® Installation Guide.

Scenario A: Standalone Deployment Scenario B: Hub-Deployment With Separate SAP HANA System Scenario C: Hub-Deployment With Shared SAP HANA System of SAP Business

Suite Scenario D: Add-On-Deployment With Shared AS ABAP and SAP HANA System

(available for CRM only) Scenario E: Hub-Deployment With Shared SAP HANA System of Other Application

You need to identify which scenario applies, in your specific landscape, for SAP ERP and SAP CRM.

Only Scenarios A, B C, D have been tested as part of this rapid-deployment solution and therefore are included. Scenario E is not documented and not included in the scope of the rapid-deployment solution’s scope.

2.2 PrerequisitesThis configuration guide assumes that SAP Hybris Marketing is installed and configured as described in the Basic Settings for Hybris Marketing (CEB) configuration guide. For more information, see the installation guide: http://help.sap.com/mkt ® Installation and Upgrade Information ® Installation Guide.

© SAP SEPage of

http://help.sap.com/mkt

http://help.sap.com/mkt


This configuration guide assumes that the SAP ERP system, or the SAP CRM system, or both the systems are already installed and configured within the company system landscape.

One or both of these systems may not be required, depending on the chosen deployment scenario.

If you only replicate data from SAP CRM, but not from SAP ERP, the SAP Customer Value Intelligence solution will not contain sufficient data. The same applies to the additional SAP BusinessObjects content that is delivered as part of the rapid-deployment solution.

SAP Landscape Transformation (SAP LT): SAP LT executes the data replication from the source systems (SAP ERP and SAP CRM) to the SAP HANA model that services SAP Hybris Marketing. It is possible to have separate SAP LT servers for SAP ERP and SAP CRM data replication.SAP Landscape Transformation Replication Server can be technically installed in three alternative locations:

On the source systems: on SAP ERP, on SAP CRM, on both of them. On an independent SAP NetWeaver ABAP server (recommended for productive

scenarios). On the SAP NetWeaver server hosting SAP Hybris Marketing (not recommended for

productive scenarios, due to performance reasons).Before proceeding with the following configuration steps, identify how many SAP LT servers you need and the systems where they need to be hosted. Then, for each SAP LT server, make sure the steps described in the SAP HANA 1.0 Installation Guide - Trigger-based Replication must be executed up to chapter Installation.

For more information about the SAP LT installation process, see the SAP Help Portal for the installation guide: http://help.sap.com/hana_appliance ® Installation and Upgrade Information ® Installation Guide – Trigger-Based Data Replication Using SAP LT Replication Server for SAP HANA.In addition, refer to SAP Note 1605140 (SAP HANA 1.0: Central Note - SAP LT Replication Server) and to the proper SLT Installation/Upgrade note, for example SAP Note 2191214 (Installation/Upgrade SLT - DMIS 2011 SP9).

The deliverables of SAP solutions are developed and tested in a system landscape with specific release and support package (SPS) level. If the SPS level in your system is different, there may be errors during the installation and deployment. The software requirements with support package levels relevant for the applications used with this solution are listed together with the required components in the SAP Hybris Marketing rapid-deployment solution Software Requirements Guide.

2.3 Users and AuthorizationsUsers for installationCreate the following users to execute the implementation steps:

© SAP SEPage of

http://service.sap.com/sap/support/notes/2191214

https://service.sap.com/sap/support/notes/1605140

http://help.sap.com/hana_appliance


Depending on the deployment scenario, SAP ERP or SAP CRM may not be used. In that case, the corresponding installation user is not required.

System User Authorizations

SAP ERP <installation user>

Authorization to the following activities: Execute transactions SU01 and PFCG (Auth.

Object S_TCODE). User administration (Auth. Objects

S_USER_GRP e S_USER_SAS) Authorization profiles administration (Auth.

Objects S_USER_AGR, S_USER_PRO, S_USER_TCD, S_USER_VAL)

SAP CRM <installation user>

Same authorizations as indicated for SAP ERP

SAP LT <installation user>

Authorization roles: SAP_IUUC_REPL_ADMIN SAP_IUUC_REPL_DISPLAY

Authorization to the following activities: Execute transactions LTR, SM59, SICF

(Auth. Object S_TCODE). Administer RFC Connections (Auth. Object

S_RFC_ADM) Administer ICF (Auth. Object S_ICF_ADM)

SAP Hybris Marketing (NetWeaver ABAP)

<installation user>

SAP_ALL, or defined by your system administrator.In addition, the following authorization roles are needed:

For Profile Parameter Maintenance: SAP_BC_BASIS_ADMIN

Role need to be modified, including the following authorization object:

S_TCODETransaction code: STRUST

For Database Connection maintenance: SAP_BC_DB_ADMIN

Role needs to be modified, including the following authorization object:

S_TABU_NAMActivity: Change, DisplayTable name: DBCON

SAP_BC_SIW_DEV

For Client and Transport Maintenance SAP_BC_SIW_DEV SAP_BC_CTS_ADMIN

For Application Setup:

SAP_CEI_TECHNICAL_CONFRole needs to be modified, including the

© SAP SEPage of


template /IWFND/RT_GW_USER, then including the following authorization object:

S_SERVICEProgram: *Type of check: Full authorization (hash value) for TADIR service.

For Service Integration Workbench SAP_BC_SIW_DEV SAP_BC_WEBSERVICE_DEBUGGER SAP_BC_WEBSERVICE_ADMIN_TEC

For BI content bundle activation: SAP_BC_BGRFC_SUPERVISOR

If you use a separate BW client, the user in the BW client needs at least the following authorization roles:

SAP_BC_SIW_DEV SAP_BC_WEBSERVICE_DEBUGGER SAP_BC_WEBSERVICE_ADMIN_TEC SAP_BC_BGRFC_SUPERVISOR

SAP HANA <installation user for SLT>

Use the SYSTEM user.As an alternative (if you don’t want to use the SYSTEM user) create a specific user (that is SLT_USER) with the following authorizations.

System Privileges:CREATE SCHEMAROLE ADMINUSER ADMIN

Object Privileges:SYS_REPL (EXECUTE, SELECT, INSERT, UPDATE, DELETE)

For details, check the Security Guide – Trigger-Based Data Replication Using SAP LT Replication Server (here), section 5 Authorizations, sub section Authorizations in the SAP HANA System

For an efficient implementation, we recommend granting SAP_ALL authorization temporarily. This authorization profile provides full authorization rights. If providing this level of authorization is not an option for your project, restrict the rights of the installation user according to your company’s security policy. For security reasons, after completing the activation, we recommend that you remove the authorizations you have given to the users who have performed the implementation steps.

© SAP SEPage of

http://help.sap.com/hana/SAP_HANA_Security_Guide_Trigger_Based_Replication_SLT_en.pdf


Installation users are ONLY used for initial configuration and content activation activities.

Users for background system-to-system communicationsThe creation of users involved in background system-to-system communications (for example, in data replication) is executed within the current guide.Here is a brief summary of users and the respective document sections:

System User name Use Created in Section

SAP ERP SLT_USER Used by SAP LT to access SAP ERP

3.1.2

SAP CRM SLT_USER Used by SAP LT to access SAP CRM

3.2.2

SAP LT CEI_SLT_USER Used for SAP Hybris Marketing to access SAP LT

3.3.3

SAP HANA SAP_CUAN_ERP_DATA Used by SAP LT for SAP ERP tables replication

3.4.2

SAP HANA SAP_CUAN_CRM_DATA Used by SAP LT for SAP CRM tables replication

3.5.2

3 Configuration3.1 SAP ERP Settings

This chapter is only relevant if you want to replicate SAP ERP data to SAP Hybris Marketing using SAP LT Replication Server (Deployment Scenario B - Hub-Deployment With Separate SAP HANA System). If not, skip the whole chapter.

3.1.1 Creating Authorization Profiles (SAP ERP)

UseThis activity creates an authorization profile for the SAP LT user.

Procedure1. In SAP ERP, access the activity using one of the following navigation options:

Transaction code PFCG

SAP ERP menu Tools ® Administration ® User Maintenance ® Role Administration ® Roles

2. On the Role Maintenance screen, in the Role field, enter SAP_IUUC_REPL_REMOTE. 3. Choose Copy role.4. On the Query screen, in the to role field, insert Z_IUUC_REPL_REMOTE. 5. Choose Copy all.

6. On the Role Maintenance screen, choose Change.7. On the Authorizations tab, choose the Expert Mode for Profile Generation button.

© SAP SEPage of


8. In the Define Maintenance Type dialog box, select the Edit old status radio button. Choose Execute.

9. You need now to include the following additional authorization objects in the role:Authorization Object: S_RFC

Activity: 16 (Execute)Name of RFC to be protected: SDTB, SDIFRUNTIMEType of RFC to be protected: FUGR

Authorization Object: S_RFCActivity: 16 (Execute)Name of RFC to be protected: SCSI_GET_SYSTEM_INFOType of RFC to be protected: FUNC

Authorization Object: S_DMISActivity: 02 (Change), 03 (Display)MBT PCL Scenario: SLOPMBT PCL Processing Role Level: PACKAGE

To include an additional authorization, execute following steps:a. Choose Manual Entry of authorization objects.b. In the Manual selection of authorizations screen insert the authorization

object (that is S_RFC).c. Choose Continue.d. In the Change Role: Authorizations screen, expand the hierarchy up to

the newly created authorization object (identified by the yellow triangle).e. Change the fields according to the provided values (use Change button

on the left side of the field, that is set Activity to 16 (Execute)). 10. Once all the new authorization objects are included and corresponding fields are valued,

choose the Generate button.11. On the Assign Profile Name for Generated Authorization Profile screen, choose Execute

to confirm the default profile name.12. Choose Back (F3) twice.

ResultThe profile for the SAP LT user has been created.

3.1.2 Creating an RFC User (SAP ERP)

UseTo enable communication between SAP LT and SAP ERP, you have to create a Remote Function Call (RFC) user in the SAP ERP system.

Procedure1. In SAP ERP, access the activity using one of the following navigation options:

Transaction code SU01

SAP ERP menu Tools ® Administration ® User Maintenance ® Users

2. In the User field, enter SLT_USER.3. Choose Create (F8).4. On the Maintain User screen, maintain the following values:

© SAP SEPage of


Address

Last Name SLT_USER

Function RFC User for SLT to access the ERP

Logon data

User type System

Password Define your password (for example remote)

Repeat Password Repeat your password

Defaults

Logon Language EN

Roles

Role Z_IUUC_REPL_REMOTE

5. Save your entries (Ctrl + S).

ResultYou have successfully created an RFC user.

3.2 SAP CRM Settings

This chapter is only relevant if you want to replicate SAP CRM data to SAP Hybris Marketing using SAP LT Replication Server (Deployment Scenario B - Hub-Deployment With Separate SAP HANA System). If not, skip the whole chapter.

3.2.1 Creating Authorization Profiles (SAP CRM)

UseThis activity creates an authorization profile for the SAP LT user.

Procedure1. Access the activity using one of the following navigation options:


SAP CRM menu Architecture and Technology ® System Administration ® Administration ® User Maintenance ® Role Administration ® Roles

2. On the Role Maintenance screen, in the Role field, enter SAP_IUUC_REPL_REMOTE. 3. Choose Copy role.4. On the Query screen, in the to role field, insert Z_IUUC_REPL_REMOTE. 5. Choose Copy all.

6. On the Role Maintenance screen, choose Change.7. On the Authorizations tab, choose the Expert Mode for Profile Generation button.8. In the Define Maintenance Type dialog box, select the Edit old status radio button.

Choose Execute.9. You need now to include the following additional authorization objects in the role:

© SAP SEPage of


Authorization Object: S_RFCActivity: 16 (Execute)Name of RFC to be protected: SDTB, SDIFRUNTIMEType of RFC to be protected: FUGR






on the left side of the field, that is set Activity to 16 (Execute)). 10. Once all the new authorization objects are included and corresponding fields are valued,



ResultThe profile for the SAP LT user has been created.

3.2.2 Creating RFC User for SAP LT (SAP CRM)

UseTo enable communication between SAP LT and SAP CRM, you must create an RFC user in the SAP CRM system. Ignore this activity if an RFC user has already been created.



SAP CRM menu Architecture and Technology ® System Administration ® Administration ® User Maintenance ® Users

2. In the User field, enter SLT_USER.3. Choose Create (F8).4. On the Maintain User screen, maintain the following values:

Address

© SAP SEPage of


Last Name SLT_USER

Function RFC User for SAP LT to access SAP CRM

Logon data

User type System



Defaults

Logon Language EN

Roles

Role Z_IUUC_REPL_REMOTE


ResultYou have successfully created an RFC system user in SAP CRM, to be used by SAP LT.

3.3 SAP Landscape Transformation (SAP LT) General Settings

In case you use more than one SAP LT replication server (that is one for ERP and one for CRM), the settings described in this chapter need to be replicated on all of the SAP LT servers.

3.3.1 Activating SAP LT Service

UseIn this activity you activate the SAP LT service. After installation, Web Dynpro and SAP LT Replication services are initially disabled. You must enable these services for trigger-based replication to work.

For more information about the following procedure, see the Activation of Web Dynpro and Relevant Services section of the SAP HANA 1.0 Installation Guide - Trigger-based Replication: http://help.sap.com/hana_appliance ® Installation and Upgrade Information ® Installation Guide – Trigger-Based Data Replication Using SAP LT Replication Server for SAP HANA.

Procedure1. In the SAP LT system, access the transaction choosing the following navigation option:

Transaction code SICF

SAP LT menu Tools ® Administration ® Administration ® Network ® HTTP Service Hierarchy Maintenance

2. On the Maintain Services screen, choose Hierarchy Type: SERVICE.3. Choose Execute.

© SAP SEPage of



4. On the Maintain service screen, expand the service nodes listed below and make sure that they are active. To activate a service, right-click the node and choose Activate Service:

/sap/bc/webdynpro/sap/iuuc_replication_config /sap/bc/webdynpro/sap/iuuc_repl_mon_powl /sap/bc/webdynpro/sap/iuuc_helpcenter /sap/bc/webdynpro/sap/iuuc_helpcenter_document /sap/bc/webdynpro/sap/iuuc_repl_mon_schema_oif /sap/bc/webdynpro/sap/iuuc_repl_wdc_config_gaf /sap/public/bc /sap/public/bc/ur /sap/public/bc/icons /sap/public/bc/icons_rtl /sap/public/bc/webicons /sap/public/bc/pictograms /sap/public/bc/webdynpro /sap/public/bc/webdynpro/adobeChallenge /sap/public/bc/webdynpro/mimes /sap/public/bc/webdynpro/ssr /sap/public/bc/webdynpro/ViewDesigner /sap/public/myssocntl

If you cannot find the iuuc_repl_mon_schema_oif service, you need to perform the following to activate this Web Dynpro service:

a. Go to transaction code SE80 (or Tools ® ABAP Workbench ® Overview ® Object Navigator), open package CNV_IUUC_REPLICATION.

b. Navigate to the following path: Web Dynpro ® Web Dynpro Components ® iuuc_repl_mon_schema_oif ® Web Dynpro Applications.

c. Double-click iuuc_repl_mon_schema_oif and then in the menu bar choose Goto ® HTTP Service Maintenance.

d. The system displays a dialog box that states that there is no such a service, and provides the option to create it.

e. Choose Yes to create the service.f. After you choose the Yes button, you may be required to assemble this

change in a workbench request.g. Activate iuuc_repl_mon_schema_oif in transaction SICF.

ResultServices required for trigger-based replication are active.

3.3.2 Creating Authorization Profile

UseThis activity creates an authorization profile for SAP Hybris Marketing to access SAP LT.



© SAP SEPage of


SAP LT menu Architecture and Technology ® System Administration ® Administration ® User Maintenance ® Role Administration ® Roles

2. On the Role Maintenance screen, in the Role field, enter SAP_IUUC_REPL_REMOTE. 3. Choose Copy role.4. On the Query screen, in the to role field, insert Z_CEI_SLT_USER. 5. Choose Copy all.

6. On the Role Maintenance screen, choose Change.7. On the Authorizations tab, choose the Expert Mode for Profile Generation button.8. In the Define Maintenance Type dialog box, select the Edit old status radio button.

Choose Execute.9. You need now to include the following additional authorization objects in the role:

Authorization Object: S_RFCActivity: 16 (Execute)Name of RFC to be protected: SDTB, SDIFRUNTIMEType of RFC to be protected: FUGR






on the left side of the field, that is set Activity to 16 (Execute) ). 10. Once all the new authorization objects are included and corresponding fields are valued,



ResultThe user profile for has been created.

3.3.3 Creating RFC User for SAP Hybris Marketing to access SAP LT

Use© SAP SE

Page of


To enable SAP Hybris Marketing to access SAP LT, you must create an RFC user in the SAP LT system.



SAP LT menu Architecture and Technology ® System Administration ® Administration ® User Maintenance ® Users

2. In the User field, enter CEI_SLT_USER.3. Choose Create (F8).4. On the Maintain User screen, maintain the following values:

Address

Last Name CEI_SLT_USER

Function RFC User for Hybris Marketing for SLT

Logon data

User type System



Defaults

Logon Language EN

Roles

Role Z_CEI_SLT_USER


ResultYou have successfully created an RFC system user in SAP LT, to be used by SAP Hybris Marketing.

3.4 SAP Landscape Transformation (SAP LT) Settings for SAP ERP

This chapter is only relevant if you want to replicate SAP ERP data to SAP Hybris Marketing using SAP LT Replication Server (Deployment Scenario B - Hub-Deployment With Separate SAP HANA System).If not, skip the whole chapter. The described settings are to be executed on the SAP LT Server used for replication of SAP ERP data (that, in some cases, can be the SAP ERP server itself).

3.4.1 Creating RFC Destination for SAP ERP System (in SAP LT)

UseAn RFC Destination has to be defined in the SAP LT server, pointing to the SAP ERP system.

© SAP SEPage of



Transaction code SM59

SAP LT menu Tools ® Administration ® Administration ® Network ® RFC Destinations

2. Choose Create (F8).3. Maintain the following values:

Field Entry

RFC Destination <ERP system name>CLNT<client>_SLT, for example, CS7CLNT200_SLT

Connection Type 3 (Connection to ABAP® system)

Description SAP ERP System

4. Choose Enter.

Technical settings

Load Balancing No

Target Host <Target Host ERP system>

Instance No. <Instance No. of ERP system>

Logon & Security

Language EN

Client <ERP client>

User SLT_USER (created in section 3.1.2)

Password Password created in section 3.1.2, for example, remote

Current User

Trust Relationship No

Status of Secure Protocol

Inactive

Unicode

Communication Type with target system

Set the Unicode flag if Unicode Test has been executed successful. This test can be performed by choosing Unicode Test in the menu area. The RFC destination must first be saved before the test can be performed. An information message appears (Example of a message: Target is a Unicode system (character size 2)).

5. Save (Ctrl + S) your RFC destination.6. You can now test your newly created RFC connection using the Connection Test button.

You can also test the RFC connection using the menu path Utilities ® Test, and then choose Connection Test or Authorization Test. The connection test performs only a technical test (Host, IP Address) of the target system. The authorization test performs an invisible logon to the target system using the maintained user and password of the RFC destination.

ResultYou have successfully created the RFC destination for the system.

© SAP SEPage of


3.4.2 Creating SAP LT Connection Definition for SAP ERP (in SAP LT)

UseIn the SAP LT system, you define a configuration set that defines a connection between the source system, the SAP LT system, and the SAP HANA system. This set defines the database tables to be replicated from the source system to the target SAP HANA system.

This chapter is only relevant if you want to replicate SAP ERP data to SAP Hybris Marketing using SAP LT Replication Server (Deployment Scenario B - Hub-Deployment With Separate SAP HANA System). If not, skip the whole chapter.


Transaction code LTRC

2. On the SAP LT Replication Server – Cockpit: Overview screen, choose Create Configuration button.

3. On the Create Configuration screen, enter the following values for the SAP ERP connection. After maintaining the values for one of the wizard’s steps, choose Next.

Field name Value

Specify General Data

Configuration Name SAP_CUAN_ERP_DATA

Description SAP ERP to Hybris Mkt. connection

Specify Source System

RFC Connection Checked

RFC Destination < the connection defined in section 3.4.1> (for example, <ERP system name>CLNT<client>_SLT)

Allow Multiple Usage Checked

Read from Single Client

Checked

Specify Target System

DB Connection Checked

Database System HANA

User Name The SAP HANA installation user for SLT, see section 2.3 (that is SLT_USER). As a quick alternative (not recommended), the SYSTEM user will work as well.

Password <user password>

Host name <server name of the SAP HANA database>

Instance Number <instance number of the SAP HANA database>

Logical Port Number <keep default> (15 for HDB)

© SAP SEPage of


Specify Transfer Settings

No. of Data transfer Jobs

2 (Depending on system performance considerations, this number may change)

Real Time Checked

4. Save the connection.

It may take several minutes to synchronize the change to the SAP HANA system.

ResultThe SAP LT connection from the SAP ERP system to the SAP HANA database has been established.In the SAP HANA database a new SAP_CUAN_ERP_DATA user and an SAP_CUAN_ERP_DATA schema have been created.

3.5 SAP Landscape Transformation (SAP LT) Settings for SAP CRM

This chapter is only relevant if you want to replicate SAP CRM data to SAP Hybris Marketing using SAP LT Replication Server (Deployment scenario B - Hub-Deployment With Separate SAP HANA System).If not, skip the whole chapter. The described settings are to be executed on the SAP LT Server used for replication of SAP CRM data (that, in some cases, can be the SAP CRM server itself).

3.5.1 Creating RFC Destination for SAP CRM System (in SAP LT)

UseAn RFC Destination has to be defined in the SAP LT server, pointing to the SAP CRM system.




SAP LT menu Tools ® Administration ® Administration ® Network ® RFC Destinations

2. Choose Create (F8).3. Enter the following data:

Field Entry

© SAP SEPage of


RFC Destination <CRM system name>CLNT<client>_SLT,for example, CS7CLNT200_SLT

Connection Type 3 (Connection to ABAP system)

Description SAP CRM System

4. Choose Enter.

Technical settings

Load Balancing No

Target Host <Target Host SAP CRM system>

Instance No. <Instance No. of SAP CRM system>

Logon & Security

Language EN

Client <CRM client>


Password Password created in section 3.2.2, for example, remote

Current User



Inactive

Unicode


Set the Unicode flag if Unicode Test has been executed successful. This test can be performed by choosing Unicode Test in the menu area. The RFC destination has to be saved first before the test can be performed. An information message appears (Example of a message: Target is a Unicode system (character size 2)).

5. Save (Ctrl + S) your RFC destination.6. You can also test the RFC connection using the menu path Utilities ® Test. Then you can

choose Connection Test or Authorization Test. The connection test performs only a technical test (Host, IP Address) of the target system as the authorization test performs an invisible logon to the target system using the maintained user and password of the RFC destination.


3.5.2 Creating SAP LT Connection Definition for SAP CRM (in SAP LT)

UseIn the SAP LT system, you define a configuration set that defines a connection between the source system, the SAP LT system, and the SAP HANA system. This set defines the database tables to be replicated from the source system to the target SAP HANA system.

© SAP SEPage of




Transaction code LTRC

2. On the SAP LT Replication Server – Cockpit: Overview screen, choose Create Configuration button.

3. On the Create Configuration screen, maintain the following values for the SAP CRM connection. After maintaining the values for one of the wizard’s steps, choose Next.

Field name Value

Specify General Data

Configuration Name SAP_CUAN_CRM_DATA

Description SAP CRM to Hybris Mkt. connection

Specify Source System

RFC Connection Checked

RFC Destination < the connection defined in section 3.5.1> (for example, <CRM system name>CLNT<client>_SLT)

Allow Multiple Usage Checked

Read from Single Client

Checked

Specify Target System

DB Connection Checked

Database System HANA

User Name The SAP HANA installation user for SLT, see section 2.3 (that is SLT_USER). As a quick alternative, the SYSTEM user will work as well.

Password <user password>

Host name <server name of the SAP HANA database>

Instance Number <instance number of the SAP HANA database>

Logical Port Number <keep default> (15 for HDB)

Specify Transfer Settings

No. of Data transfer Jobs

2 (Depending on system performance considerations, this number may change)

Real Time Checked

4. Save the connection.

It may take several minutes to synchronize the change to SAP HANA system.

© SAP SEPage of


ResultThe SAP LT connection from the SAP CRM system to the SAP HANA database has been established.In the SAP HANA database a new SAP_CUAN_CRM_DATA user and an SAP_CUAN_CRM_DATA schema have been created.

3.6 SAP HANA System Settings

3.6.1 Assigning Roles to the SAP ERP Replication User

UseThe purpose of this activity is to assign proper replication roles to the SAP HANA user to be used in SAP ERP data replication.

This chapter is only relevant if you want to replicate SAP ERP data to SAP Hybris Marketing using SAP LT Replication Server. If not, skip the whole chapter.

Procedure1. Open the SAP HANA Studio (in MS Windows, choose Start ® All Programs ® SAP

HANA ® SAP HANA Studio).2. Open the SAP HANA Modeler perspective (menu Window ® Open Perspective ® SAP

HANA Modeler).3. In the SAP HANA Systems view, expand <SAP HANA instance> ® Security ® Users. 4. Double-click the SAP_CUAN_ERP_DATA user. A window with user details opens.5. On the Granted Roles tab, choose the plus button.6. In the Type name to find a role field, enter SAP_CUAN_ERP_DATA.7. In the Matching items screen, select the following roles (for multiple select, press the CTRL

key while choosing the items): SAP_CUAN_ERP_DATA_DATA_PROV SAP_CUAN_ERP_DATA_POWER_USER SAP_CUAN_ERP_DATA_SELECT_USER SAP_CUAN_ERP_DATA_USER_ADMIN

8. Choose OK.9. Choose Deploy button at top-right part of the screen.

For more information about user roles, see SAP HANA Security Guide - Trigger-Based Replication (SLT) on the SAP Help Portal: http://help.sap.com/hana_appliance ® Security information

ResultReplication roles are assigned to the SAP ERP replication user in SAP HANA.

3.6.2 Assigning Roles to the SAP CRM Replication User

UseThe purpose of this activity is to assign proper replication roles to the SAP HANA user to be used in SAP CRM data replication.

© SAP SEPage of



This chapter is only relevant if you want to replicate SAP CRM data to SAP Hybris Marketing using SAP LT Replication Server. If not, skip the whole chapter.

Procedure1. Open the SAP HANA Studio (in MS Windows, choose Start ® All Programs ® SAP

HANA ® SAP HANA Studio).2. Open the SAP HANA Modeler perspective (menu Window ® Open Perspective ® SAP

HANA Modeler).3. In the SAP HANA Systems view, expand <SAP HANA instance> ® Security ® Users. 4. Double-click the SAP_CUAN_CRM_DATA user. A window with user details opens.5. On the Granted Roles tab, choose the plus button.6. In the Type name to find a role field, enter SAP_CUAN_CRM_DATA.7. In the Matching items screen, select the following roles (for multiple select, press the CTRL

key while choosing the items): SAP_CUAN_CRM_DATA_DATA_PROV SAP_CUAN_CRM_DATA_POWER_USER SAP_CUAN_CRM_DATA_SELECT_USER SAP_CUAN_CRM_DATA_USER_ADMIN

8. Choose OK.9. Choose Deploy button at top-right part of the screen.

For more information about user roles, see SAP HANA Security Guide - Trigger-Based Replication (SLT) on the SAP Help Portal: http://help.sap.com/hana_appliance ® Security information

ResultReplication roles are assigned to the SAP CRM replication user in SAP HANA.

3.7 SAP Hybris Marketing Settings

3.7.1 Creating RFC Destination for the SAP ERP System

UseAn RFC Destination has to be defined in the SAP NetWeaver server for SAP Hybris Marketing, pointing to the SAP ERP system. This connection is used during execution of CUAN_SETUP_ERPCONTENT task list with deployment Reuse SAP ERP Data in the CED Configuration Guide.

This chapter is only relevant in case of Reuse of SAP ERP data in SAP Hybris Marketing task list. If not, you can skip the whole chapter.

Procedure1. Log on to the SAP Hybris Marketing system using the SAP GUI.2. Access the activity using one of the following navigation options:


Application menu Tools ® Administration ® Administration ® Network ® RFC Destinations

© SAP SEPage of




Field Entry

RFC Destination <ERP system name>CLNT<client>_CEI,for example, CS7CLNT200_CEI

Connection Type 3 (Connection to ABAP system)

Description SAP ERP System

5. Choose Enter.

Technical settings

Load Balancing No

Target Host <Target Host ERP system>

Instance No. <Instance No. of ERP system>

Logon & Security

Language EN

Client <ERP client>


Password The password of the SLT_USER, for example, remote

Current User unchecked



Inactive

Unicode


Set the Unicode flag if Unicode Test has been executed successful. This test can be performed by choosing Unicode Test in the menu area. The RFC destination has to first be saved before the test can be performed. An information message appears (Example of a message: Target is a Unicode system (character size 2)).


You can also test the RFC connection following the menu path Utilities ® Test. Then you can choose Connection Test or Authorization Test. The connection test performs only a technical test (Host, IP Address) of the target system as the authorization test performs an invisible logon to the target system using the maintained user and password of the RFC destination.


3.7.2 Creating RFC Destination to SAP LT System for SAP ERP

UseA temporary RFC Destination has to be defined in the SAP NetWeaver server for SAP Hybris Marketing, pointing to the SAP LT System used for replication of SAP ERP data. This

© SAP SEPage of


connection is used during execution of CUAN_INITIAL_SETUP task list in the CED Configuration Guide.





Field Entry

RFC Destination

CEI_SETUP_SLT_ERP

Connection Type

3 (Connection to ABAP system)

Description Connection to SAP LT, used for the setup of SAP ERP Data replication

5. Choose Enter.

Technical settings

Load Balancing No

Target Host <Target Host SAP LT system>

Instance No. <Instance No. of SAP LT system>

Logon & Security

Language EN

Client <SAP LT client>

User CEI_SLT_USER

Password CEI_SLT_USER password (defined in section 3.3.3)

Current User Blank



Inactive

Unicode




You can also test the RFC connection using the menu path Utilities ® Test. Then you can choose Connection Test or Authorization Test. The connection test performs only a technical test (Host, IP Address) of the target system as the authorization test performs

© SAP SEPage of


an invisible logon to the target system using the maintained user and password of the RFC destination.


3.7.3 Creating RFC Destination to SAP LT System for SAP CRM

UseA temporary RFC Destination has to be defined in the SAP NetWeaver server for SAP Hybris Marketing, pointing to the SAP LT System used for replication of SAP CRM data. This connection is used during execution of CUAN_INITIAL_SETUP task list in the CED Configuration Guide.





Field Entry

RFC Destination

CEI_SETUP_SLT_CRM

Connection Type

3 (Connection to ABAP system)

Description Connection to SAP LT, used for the setup of SAP CRM Data replication

5. Choose Enter.

Technical settings

Load Balancing No

Target Host <Target Host SAP LT system>

Instance No. <Instance No. of SAP LT system>

Logon & Security

Language EN

Client <SAP LT client>

User CEI_SLT_USER

Password CEI_SLT_USER password (defined in section 3.3.3)

Current User Blank


Status of Secure Inactive

© SAP SEPage of


Protocol

Unicode




You can also test the RFC connection using the menu path Utilities ® Test. Then you can choose Connection Test or Authorization Test. The connection test performs only a technical test (Host, IP Address) of the target system as the authorization test performs an invisible logon to the target system using the maintained user and password of the RFC destination.


© SAP SEPage of

bb installation guidesapidp/... · web viewfor bi content bundle activation:...

Documents