Skip to Content
0

Multiprovider to HANA Composite Provider Migration - force Navigational Attributes

May 15, 2017 at 08:51 AM

470

avatar image

Hello,

as described in Note 2080851 - Conversion of MultiProvider to CompositeProvider there is a program RSO_CONVERT_IPRO_TO_HCPR to migrate an existing Multiprovider to (MPRO) the new Hana Composite Provider (HCPR).

The migration of MPRO -navigational attributes is only working if the following condition is met:

[...] the navigation attributes from all PartProviders must be supplied by a navigation attribute from which the characteristic bearing the navigation attribute is also supplied.

In some cases we currently have the situation that a navigational attribute is ticked on in the MPRO, but not assigned to all part-providers, because the Main-IOBJ doesn't exist in the Partprovider.

In this case, the NavAtt MAIN_IOBJ__ATTR will be migrated by the program to a new field HCPR_ATTR with the same assignment on HANA level.

Is there any possibility to force Navigational Attribute migration to the "real" navigational attribute in this case?

Best regards

Moritz

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Andreas Duda Jul 19, 2017 at 09:28 AM
0

Before conversion, run a check on your MultiProvider. Most likely you have warnings which subsequently lead to the use of the described global object.

If you are able to adjust your MultiProvider in a way to get rid of those warnings, you will most likely get rid of those new global objects. Usually this involves activation of navigational attributes in some/all InfoProviders/InfoObject in order to allign the way they get queried. Note there are constellations that may not be able to be resolved in the described way.

Share
10 |10000 characters needed characters left characters exceeded