Scribd
Upload
50 views2 pages

HCPR Cannot Be Activated Due To Error 0DATAPAKID - KEY, 0RECORDMODE - KEY,,, Are Missing

The document addresses an issue where the activation of a Hierarchical CompositeProvider (HCPR) fails due to missing attributes (0DATAPAKID_KEY, 0RECORD_KEY, 0RECORDMODE_KEY) in the calculation model. It provides a resolution by executing a specific report to rebuild the logical index and suggests checking the indexserver_alert file for the involved partprovider. The document is relevant for users of SAP NetWeaver 7.4 and 7.5.

Uploaded by

Sri srivastava
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
50 views2 pages

HCPR Cannot Be Activated Due To Error 0DATAPAKID - KEY, 0RECORDMODE - KEY,,, Are Missing

The document addresses an issue where the activation of a Hierarchical CompositeProvider (HCPR) fails due to missing attributes (0DATAPAKID_KEY, 0RECORD_KEY, 0RECORDMODE_KEY) in the calculation model. It provides a resolution by executing a specific report to rebuild the logical index and suggests checking the indexserver_alert file for the involved partprovider. The document is relevant for users of SAP NetWeaver 7.4 and 7.5.

Uploaded by

Sri srivastava
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

2020-07-14 2387953

2387953 - HCPR cannot be activated due to error


0DATAPAKID_KEY, 0RECORDMODE_KEY,,, are missing
Version 3 Type SAP Knowledge Base Article
Language English Master Language English
Release Status Released to Customer Category Problem
Component BW-WHM-DBA-HCPR (CompositeProvider) Released On 12.07.2017

Please find the original document at https://launchpad.support.sap.com/#/notes/2387953

Symptom

The activation of an HCPR fails with an error such as:

EC:2048"column store error: fail to create scenario: [34011] Inconsistent calculation model;calculationNode
(U1):Attribute
Attribute 0DATAPAKID_KEY is missing in node U1.ADSO.1.
Attribute 0RECORD_KEY is missing in node U1.ADSO.1.
Attribute 0RECORDMODE_KEY is missing in node U1.ADSO.1.

Environment

• SAP NetWeaver 7.4


• SAP NetWeaver 7.5

Reproducing the Issue

Activate a HCPR that includes aDSOs or standard DSOs.

Resolution

Execute report RSDDB_LOGINDEX_CREATE for the appropriate partprovider in order to rebuild the logical
index.

Which partprovider is involved can be checked and identied by using the indexserver_alert file:

• see SAP note 1641210


• or call transaction DBACOCKPIT --> Diagnostics --> Diagnosis Files and search for the latest available
indexserver_alert file.

Example:

If you get an error for U1.ADSO.1, search in the the indexserver_alert file for the term:

• "name": "U1.ADSO.1","operation": {"__CalcScenarioDSNodeData__": true,"source":

© 2020 SAP SE or an SAP affiliate company. All rights reserved 1 of 2


2020-07-14 2387953

In this below example the assigned partprovider of "U1.ADSO.1"," is "SAPABAP1:0BW:BIA:XYZ" (XYZ =


name of partprovider)

In case you get the error in the AFTER_IMPORT method, transport the corresponding aDSO too.

Keywords

0DATAPAKID_KEY; 0RECORD_KEY; 0RECORDMODE_KEY

Products

SAP NetWeaver 7.4


SAP NetWeaver 7.5

Other Components

Component Description

BW-BEX-OT-HCPR CompositeProvider Query

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2020 SAP SE or an SAP affiliate company. All rights reserved 2 of 2

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy