Child pages
  • Consistent Navigation Attribute Mapping in a HCPR
Skip to end of metadata
Go to start of metadata

Introduction

In contrast to a MultiProvider, the BW system does not allow all kinds of navigation attribute mappings any longer in a HCPR:

In a HCPR, it is always assured that navigation attributes are mapped consistently. That is, the navigation attribute relationship to the main characteristic(as stored in the master data tables) is always kept in the output. Inconsistent navigation attribute mapping is not allowed. See examples below and also note

2215947 "How to Set Navigation Attributes for an aDSO, an HCPR or an Aggregation Level"

Simple Example

In a Multiprovider it was possible to map a characteristic C of an Partprovider to a navigation attribute A__C on the MultiProvider level.

PartProvider  MultiProvider
AA
CA__C

In this case, the relationship between a characteristic value of A and its navigation attribute C (stored in the P or Q master data tables of the characteristic A)  is not kept any longer. Hence, a query might display different attributes in comparison to queries where the result is based on the corresponding master data tables. In addition, in this case it might happen that the assignement from A to C is not unique any longer! That is why this kind of mapping is not possible when creating an HCPR. When a navigation attribute (A__C in our example) is activated on the HCPR level, no mapping is possible/offered  since this means (automatically) that the master data tables are joined with the basis characteristic in order to get the attribute values.

See also Example MultiProvider: Inconsistent Mapping of Navigation Attribute.

Examples of consistent and inconsistent navigation attribute mappings

  • Characteristic A has B as reference characteristic. That is, A and B have the same master data tables. E.g.: 0DEBITOR has 0CUSTOMER as reference characteristic.
  • Characteristic C has D as reference characteristic.
  • HCPR is union of Partproviders.

The following mappings are consistent

Example 1

Partprovider           HCPR

A              -----------      A

B              -----------      B

A__C        -----------     A__C

B__C        -----------     B__C

Example 2

Partprovider           HCPR

A              -----------      B

B              -----------      A

A__C        -----------     B__C           

B__C        -----------     A__C

The relationship between A and A__C is kept.

The relationship between B and B__C is kept.

Example 3

Partprovider           HCPR

A              -----------      A

A__C        -----------     C or D

C or D is a 'standalone' characteristic, there is no relationship between A and C/D in the output.

The following mappings are inconsistent, thus not possible in a HCPR

Example 4

A              -----------      A

B              -----------      B

A__C        -----------     B__C           

B__C        -----------     A__C

The relationship between A and A__C  is broken.

The relationship between B and B__C is broken.

Example 5

Partprovider           HCPR

B              -----------      B

                                   B__C  (unmapped) 

As B__C is not mapped, it returns always the initial value. This is possible in Multiprovider. In HCPR, return initial value for unmapped B__C is not allowed. 

Example 6

Partprovider           HCPR

A              -----------      A

B              -----------      B

A__C        -----------     A__C

C              -----------      B__C              

As C is a standalone characteristic, the relationship between B and B__C is broken in the output.

Example 7

Partprovider           HCPR

A              -----------      A

A__C        -----------     A__D

The relationship between A and A__D is broken.

 

  • No labels