SAP HANA Live Installation Tips + Tables.

By admin Last updated Jan 20, 2021

Whilst importing delivery units into your HANA System you can sometimes run into some common errors which can easily be fixed without the means of opening a SAP Incident.

Lets look at an example.

Here you are importing SAP HANA Analytics into your system. During the import you see an error:

To get a more in depth look a what actually went wrong here, we would need to look into the installation log (this is printed after the import fails) or the indexserver.trc file:

[37654]{228998}[123/-1] 2014-04-07 23:24:06.604933 e REPOSITORY activator.cpp(01179) : Repository: Activation failed for at least one object;At least one runtime reported an error during revalidation. Please see CheckResults for details.

The problem in such cases is the person who was responsible for the prerequisites for the import did not check SAP note 1781992 before starting the import.

It is very important to have the necessary tables in the SAP_ECC Schema or else the import will fail. Best thing to do if this fails is to compare the existing tables with the tables listed in the note:

select table_name from m_cs_tables where schema_name = ‘SAP_ECC’ order by table_name asc;

What if you have already imported the tables and the installation log is saying that it cannot find some particular tables. Here is an example of something you may see in the logs:

2016-05-30 15:14:55:381|-02:00|8|SYSTEM|Object: sap.hba.ecc.TCURM_BWKEY_BUKRS_WERKS.calculationview ==> Error Code: 40117

2016-05-30 15:14:55:382|-02:00|8|SYSTEM|Repository: Encountered an error in repository runtime extension;Model inconsistency. Create Scenario failed: ColumnTable SAPERP:TCURM not found (cannot get catalog object)(calculationNode (BW_1$$$$TCURM$$))The following errors occurred: Inconsistent calculation model (34011)

2016-05-30 15:14:55:409|-02:00|8|SYSTEM|Object: sap.hba.ecc.T156C_BSTAUS.calculationview ==> Error Code: 40117

2016-05-30 15:14:55:410|-02:00|8|SYSTEM|Repository: Encountered an error in repository runtime extension;Model inconsistency. Create Scenario failed: ColumnTable SAPERP:T156C not found (cannot get catalog object)(calculationNode (T156C))The following errors occurred: Inconsistent calculation model (34011)

2016-05-30 15:14:55:442|-02:00|8|SYSTEM|Object: sap.hba.ecc.SpecialGLCode.calculationview ==> Error Code: 40117

2016-05-30 15:14:55:443|-02:00|8|SYSTEM|Repository: Encountered an error in repository runtime extension;Model inconsistency. Create Scenario failed: ColumnTable SAPERP:T074T not found (cannot get catalog object)(calculationNode (T074T))The following errors occurred: Inconsistent calculation model (34011)

2016-05-30 15:14:55:474|-02:00|8|SYSTEM|Object: sap.hba.ecc.SpecialGLCodeValueHelp.calculationview ==> Error Code: 40117

As you can see, I have highlighted the tables which are failing to be found. Checking the transaction SE11 you can see these tables there, so what is the problem? The next step is to check if the tables are in terminated state, or “POOLED” state. These tables should be changed to “TRANSPARENT” state.

se14 –>

–> Press “Continue adjustment”.

1: What do you do if the import is still failing after all the tables have been imported?

Check the tables for invalid attributes and make sure the tables are set up correctly. (This just involves recreating the table).

You should also note which Delivery Units have failed to import. Re-importing the Delivery Unit again is also a valid approach to fix activation or deployment errors.

2: What do I do if the activation of some of views is failing after the import?

Make sure that when the tables are being searched in the schema, that it is searching the correct schema, this will involve insuring you have your schema mapping done correctly. An example of this can be seen in the below trace:

One table for a calculation view was searched in schema DT4_XT5: “- CalculationNode(WRF_CHARVALT): ColumnTable DT4_XT5:WRF_CHARVALT not found (cannot get catalog object).”

When searching this schema doesn’t exist. Therefore the activation of “sap.is.retail.ecc.RetailCharacteristicValue” will obviously fail. So now you have to ask yourself the question, what schema did I start the installation with, did I start with a different schema and change it somewhere in between the process? Also check to see if you moved the “WRF_CHARDVALT” table elsewhere.

3: What if the user does not have the required privileges when activating CAR HANA Content or any other content?

When checking the logs you see errors with activation which refer to, lets say SAP_CRM schema. When looking for this schema in the catalog you cannot see it, so this leads to the question, does this actually exist or is my user prohibited from viewing this? The answer which is most likely is the lather. Make sure your user has been granted the SELECT privilege on the SAP_CRM schema. A good guide would be to follow SAP Note 1936727

So referring to the Note, you could check the _SYS_REPO to see if any important privileges are missing such as EXECUTE, INSERT, etc. Please note that normally the _SYS_REPO normally only needs the SELECT privilege for a plain installation.

4: What if you face errors when importing HANA SMART BUSINESS FOR ERP 1.0?

Checking the installation log after the import fails you see:

Object: sap.hba.r.sappl604::BSMOverview.calculationview ==> Error Code: 40117 Severity: 3

Object: sap.hba.r.sappl604::BSMOverview.calculationview ==> Repository: Encountered an error in repository runtime extension;Model inconsistency. Create Scenario failed:

ColumnView _SYS_BIC:sap.hba.r.sappl604/BSMInfoOverview not found (cannot get catalog object)(CalculationNode (BSMInfoOverview))

The following errors occured: Inconsistent calculation model (34011)

Details (Errors):

– CalculationNode (BSMInfoOverview): ColumnView _SYS_BIC:sap.hba.r.sappl604/BSMInfoOverview not found (cannot get catalog object).

The solution for this can be found in SAP Note 2317634

5: You receive errors when performing data previews on the package sap.hba.ecc?

When viewing the sap.hba.ecc packages you can see some calculation views are marked red. When clicking on data preview you see error:

What we now need to ask is, did any of these views ever work at all or is it specific to individual views? If you answered “yes” to the first question, then I would re-deploy the delivery unit again which should fix this issue.

If it is specific views that are causing the issue, then try to re-deploy each view separately through Studio and activate again. If this does not work then work go into the Diagnosis Files tab in the HANA Studio and pull down the most recent errors which should have been printed in the indexserver.trc file. Check to see which table is trying to be reached for this view and what schema it is in. Check if the user you are logged in with has the correct privileges along with the _SYS_REPO. (An authorisation trace may be useful here).

The solution for this can also be found in SAP Note 2318731.

6: Do you attempt to install HANA Live in a single or multitentant database container (a.k.a. MDC, Multi-DB)?

HANA Live needs to be installed in the database tenant where also the application runs on / the schema resides. As of HANA SPS 09, the HANA Application Lifecycle Manager can be used to deploy the content package(s). However, the hdbalm command line tool does not provide an option to specify a tenant database as the import target. Every tenant database in a multiple-container system has dedicated ports for SQL, internal communication and if an SAP HANA XS classic server (xsengine service) is running in the tenant database, there is also a dedicated port for HTTP-based client communication.
See the following example command: hdbalm -u SYSTEM -h lo1234.mycompany.com -p 8000 install SAP_APO_ANALYTICS_1.0.zip
While this example command will correctly install the DU specified in a Single DB, in a Multi-DB environment this causes the DU to be installed in the SystemDB tenant! As already mentioned this is not the correct tenant as it needs to run in the same tenant where the application schema is located.
So when deploying HANA Live content in a Multi-DB environment, it is required to first Configure HTTP(S) Access to Multitenant Database Containers via SAP HANA XS Classic.

The chapter on Connections for Multitenant Database Containers provides guidance how you can determine the ports used by a particular tenant database. The HTTP(S) port specified needs then to be passed on to the hdbalm command.

** SAP Note 2118742 – Analyzing HANA Live content package deployment problems** This note has now been updated and co-written with the HANA HALM Development team. It now includes a handy video and also the package hierarchy if anyone would like to see it. **

Schema Mapping:

You must set up a schema mapping to map the authoring schema of a content package to the physical database schema of the relevant tables. The authoring schema is the database schema that is referred to in the content package. In a customer system, the tables are typically stored in another database schema, namely either in the schema configured in SAP Landscape Transformation Replication Server (for the side-by-side scenario) or in the database schema of the ABAP installation (for the integrated scenario). For more information, see Configuration of Replication Between Back End and SAP HANA DB.

Required Steps

In the SAP HANA Studio, in the Modeler perspective, on the Quick Launch tab, select the relevant SAP HANA system and choose Setup, then Schema Mapping to add a new schema mapping from the authoring schema to the physical schema.

Example

Package sap.hba.ecc refers to the authoring schema SAP_ECC. In your customer landscape the ECC tables are replicated into schema CUSTOMER. Then a schema mapping from SAP_ECC to CUSTOMER needs to be added.

SAP HANA Live 1.0 for Manufacturing

If you find yourself trying to implement HANA live views for Manufacturing and you see the following errors:

1: Execute deployment (activationMode = ONE_COMMIT_ACTIVATION) of delivery unit (name: HCO_HBA_OEE, vendor: sap.com, id: 4105)

2: Content error: Activation of at least one object failed

3: Content error: Object: sap.hba.oee.ShopFloorDataElementTypes.calculationview ==> Error Code: 40117

4: Content error: Repository: Encountered an error in repository runtime extension;Model inconsistency. Create Scenario failed: ColumnTable SAPENP:/OEE/C_TE_TYPET not found (cannot get catalog object)(calculationNode (_OEE_C_TE_TYPET))The following errors occurred: Inconsistent calculation model (34011)

5: Content error: Object: sap.hba.oee.ShopFloorDataCollectionElement.calculationview ==> Error Code: 40117

6: Content error: Repository: Encountered an error in repository runtime extension;Model inconsistency. Create Scenario failed: ColumnTable SAPENP:/OEE/C_TIMEELEMT

OEE is no longer supported. To get the tables that I have listed below you have to deploy the MII product.

SAP Manufacturing Integration and Intelligence 15.1 – SAP Help Portal Page

For HANA Live views for Manufacturing, the tables listed in Note 1782065 and 1781992 need to exist in SAP HANA database.
In addition to that, these tables must also exist in the database:

List of tables replicated from ERP to HANA in Schema SAP_ECC:

Master tables:
1. /OEE/MPH_KPITARG
2. /OEE/MPH_LAYOUT
3. /OEE/MPH_MRKDWN
4. /OEE/MPH_NODE
5. /OEE/MPH_NODEAMG
6. /OEE/MPH_NODEATO
7. /OEE/MPH_NODESTR
8. /OEE/MPH_NODET
9. /OEE/MPH_CFN

Configuration tables:
1. /OEE/C_DCELEM
2. /OEE/C_DCELEMT
3. /OEE/C_TIMEELEM
4. /OEE/C_TIMEELEMT
5. /OEE/C_MCGRP
6. /OEE/C_MCGRPT
7. /OEE/C_KPI
8. /OEE/C_KPIT
9. /OEE/C_CLFN
10. /OEE/C_CLFNT
11. /OEE/C_GRC
12. /OEE/C_GRCT
13. /OEE/C_PRC
14. /OEE/C_PRCT
15. /OEE/C_TE_TYPE
16. /OEE/C_TE_TYPET
For Authorization related data the following tables must also be replicated:
USRBF2
UST12

This is a list of tables replicated from MII to HANA in Schema SAP_MII:

1. MPM_PROD_RUN_HR

2. MPM_PROD_RUN_INT
3. MPM_PROD_RUN_DATA
4. MPM_DATA_AS_MC_EVT
5. MPM_SCHEDULED_DOWN

MII on HANA scenario:

In case the MII is on HANA then the above 5 tables are not required to be replicated.

For OEE report analysis, the following local tables must exist in HANA database in schema SAP_HBA.
1. REPORT_VARIANT_HDR
2. REPORT_VARIANT_DTL

These tables gets created automatically when OEE package installed.
Additional tables to be replicated in Schema SAP_MII:

From “HCO HBA OEE 100 SP06” onwards the following additional tables have to be replicated to SAP_MII schema along with the tables mentioned above.

1. MPM_PRDRUN_INT_EVT
2. MPM_PROD_EVENTS
3. MPM_EVENT_MAP
4. MPM_EVENT_NODE_MAP
5. MPM_DATA_EVENT_MAP

List of tables needed for each HANA Live component:

SAP HANA Analytics for PLM 1.0

Before beginning the install for SAP HANA Live for PLM 1.0, you must have the required tables before the install.

See this note which lists the tables:

Tables for SAP HANA Analytics for PLM 1.0

SAP HANA Analytics for GRC 1.0

Before beginning the install for SAP HANA Live for GRC 1.0, you must have the required tables before the install.