Details on Hub-Deployment With Separate SAP HANA System

[Former Member]

Hi all,

We'd like to implement Hub-Deployment With Separate SAP HANA System deployment scenario because we need to integrate our SAP CRM system. But we dont't want replicate data via SAP Landscape Transformation Replication Server.

So we execute transaction STC01 and select the CUAN_SETUP_CRMCONTENT task list. In the "Define Parameters for Technical Configuration" phase we find:

But the parameters on Replication with SAP landscape Transformation appear to be mandatory. Is it possible to skip these parameters or give dummy values?

Best regards, Roberto

[former_member213386 · Accepted solution]

Hello Robert,

yes, you can also integrate CRM data without using the SLT option.

In case your CRM Schema is already available in your Hana (eg. 2 NW appl servers share same Hana, or through own managed replication), you can select in the CRM Integration task list the option "Reuse SAP CRM Data". You then enter the Physical Schema Name of your CRM Data.

Provide also the other CRM parameters, like RFC and host/port to CRM for correct setup.

best regards, Sophie.

[Former Member · Accepted solution]

Hello Sophie,

thank you for the answer ... oky when you say we can integrate CRM data without using SLT option ... the fields related to SLT are mandatory ... can we specify dummy values or do you have other solutions?

Related HANA ... our CRM is not available on HANA db so we cannot use that kind of scenariuo ...

Best regards, Roberto 

[former_member213386 · Accepted solution]

Hello Robert,

fields are only mandatory, if you use "Replication" option, if you use "Reuse" they are not. See screenshot. Which release do you use? For Reuse the schema has to be available in the hana database, you could even have created it manually ;-), it needs to contain the relevant tables (see cuan_tc_tables in hybris mkt with application SAP_CUAN_CRM).

best regards, Sophie.

[Former Member · Accepted solution]

Hi Sophie,

thank you  very much .... your solution is very helpful for us and I'd like to understand better. We have SAP hybris Marketing 1.1 (1508) and we can see the Reuse option,

Into "cuan_tc_tables" there are 188 entries related to SAP_CUAN_CRM.

So if I have understood we can create a physical schema with all these tables (can syncronize with BO data service for instance). Kindly could you explain better what is happen between authoring schema and phisical schema? Have we create all 188 tables into own phisical schema with the same names or something happens when I specify the schema mapping (for example we create an empty phisical schema and the thechnical configuration report will do the schema mapping creating all tables that we can see in the SAP_CUAN_CRM? So the big important question for us: What is the authoring schema and how does it works ....

Thank you in advance for all suggestions you can give us ....

best regards, Roberto

[former_member213386 · Accepted solution]

Hello Roberto,

schema mapping is explained in general here:

http://help.sap.com/hana/SAP_HANA_Modeling_Guide_en.pdf  chapter 4.4.

In the different Hana artifacts of hybris marketing, tables of authoring schema SAP_CUAN_CRM are used. At development time, there is indeed such a schema also physically available. On other systems, at first such a schema SAP_CUAN_CRM is not available.

Two options exist now: you do not want to use CRM at all. As the basic Hana artifacts are activated in one step, as prerequisite, a physical schema SAP_CUAN_CRM is created on the Hana database with the necessary, but empty, tables in it. As physical schema name is same as authoring schema name, no schema mapping is required. This is done by the initial setup / base config task list (depending on your release).

The other option (more typical): you want to use the data of your CRM system. An own CRM database schema on the hana database needs to be available. This can be achieved by different means, and the schema name of that schema is typically not SAP_CUAN_CRM, but some other valid schema name (like SAP<SID> or any other valid schema name, e.g. the name of the configuration in case of SLT).

When using task list CUAN_SETUP_CRMCONTENT and option REUSE, the schema mapping from the schema name entered in the report parameters to the authoring schema is done by the task list, you do not need to maintain it manually. Also other tasks are performed on/with the data available in that schema. Concerning the tables: if you use Reuse option, the tables have to be available in the schema already. In case you use SLT, the task list triggers the replication of the tables.

best regards, Sophie.

[Former Member · Accepted solution]

Hi Sophie ... thank you very much  .... really you are resolving many doubts

Our actual situation is we have SAP CRM on NO HANA system and in this moment we don't have own CRM database schema  on the hana database. During initial setup (standalone scenario) of Hybris marketing we got the SAP_CUAN_CRM as phisical/logical schema. So in this case we could use this schema because we don't have CRM content in others database schema. Is it right?

Regards, Roberto

[former_member213386 · Accepted solution]

Hello Roberto,

do i understand it right, you would want to use physically available "dummy" schema SAP_CUAN_CRM, to load data into it, maybe via the above mentioned BO services? In principle, I would not recommend to make use of the dummy schema SAP_CUAN_CRM, because in case of an upgrade, the task list could make changes to that schema.

If you use your own schema, you are more on the safe side. Your "Reuse schema" does not need to be used directly by your CRM system. This is also not the case when a schema gets via SLT into the hana, it is just a replicate.

So you could maybe just copy the dummy schema SAP_CUAN_CRM, give it some other suitable name. The tables are available but empty. Then connect your datasource to that schema / tables in that schema. Then make use of the task list  CUAN_SETUP_CRMCONTENT and option REUSE. Just an idea - not an "officially supported" way...see also installation guide of hybris marketing.

best regards, Sophie.

[Former Member · Accepted solution]

Hello Sophie,

we are following the second option (also for us is the best way) you described above. We copied the dummy schema SAP_CUAN_CRM (export / import with rename of the schema).

When I talked about to fill the SAP_CUAN_CRM because there was a misunderstanding related to option 1 ....

"you do not want to use CRM at all. As the basic Hana artifacts are activated in one step, as prerequisite, a physical schema SAP_CUAN_CRM is created on the Hana database with the necessary, but empty, tables in it. As physical schema name is same as authoring schema name, no schema mapping is required. This is done by the initial setup / base config task list (depending on your release)."

We thought we could use this kind of schema because in this moment we haven't the CRM data on HANA. We'll with these activities when we'll decide the right schema that (as I said before) will be the schema copied from SAP_CUAN_CRM.

Then we'll have other questions ... but I'll open other threads ...hope to find the same partecipation I had here.

Thank you ...

Roberto