Char as KF issues

[PankajVPatil]

Hello Experts,

We are on SAP BPC 10.1 Embedded on HANA 7.40 system with SP14 level.

Have created a Multiprovider containing couple of standard and real time cubes with few Direct Update DSOs containing a "Char as KF" InfoObject.

Following are the issues related to the "Char as KF" :

1) To make the Multiprovider HANA optimized, we have had to remove out the DSOs containing Char as KF IO. Although from forums had an understanding that this was resolved in SP13 level; so not sure if there is further any setting associated to make the Multiprovider (including DSOs) a HANA optimized object.

2) Few validation reports are planned to be created on the Multiprovider. However, the Char as KF IO which is part of the Multiprovider does not become visible in the BEx Query Designer. Again please confirm if we have any setting associated with it.

Thanks,

Pankaj

[gregor_dieckmann · Accepted solution]

Hi Pankaj,

PAK support in MultiProvider and CompositeProviders was switched off if a 'characteristic as key figure' was used there. This was necessary due some technical limitations. These limitations are now solved, with implementation of note 2319395 PAK also works in the above case.

To your second points: Queries using 'characteristics as key figures' are only allowed based on planning enabled InfoProviders. So for reporting use a query on a planning provider. This limitation exists to avoid usage of both 'characteristic as key figure' 1KYF_A together with characteristic A in one query.

Regards,

Gregor

[PankajVPatil · Accepted solution]

Hi Gregor,

Thank you for the responses. Really appreciate it.

I have one more issue as follows:

3) We have a month as a custom char info object created on the reference char of 0CALMONTH. Now this char needs to be consumed as a "Char as KF" as we have to manually enter the month values through our input ready queries. The idea behind leveraging the 0CALMONTH as a reference char is that we enable auto-validations on the month values that the user will input. Thus the wrongly input values will not get saved and/or a system generated warning may flag up.

However the issue is that the system do not allow to insert the custom month IO under "Char as KF" portion of the DSO. I think this is because, (and by definition) the char as KF is treated as free text as unlike in case of the month which has a pre-determined set of values contained in 0CALMONTH's hierarchy.

So how do I get the best of both ?

Also is there an alternate approach I can try out ?

Thanks,

Pankaj

[gregor_dieckmann · Accepted solution]

Hi Pankaj,

the feature 'characteristic as key figure' is just what the name says: a characteristic in the data part of a DSO can be exposed as a key figure. This is also true for time characteristics (that was not supported from the beginning but is possible with note 2124605). Whether 'all' values are allowed or whether there exist a check table for a 'characteristic as key figure' depends on the usual BW settings in RSD1, i.e. values will be checked to be in the master data table if it exists.

Analysis Office also supports F4 help for characteristics as key figures if the characteristics have a master data table. Unfortunately, F4 help for time characteristics is not yet supported.

In fact, the 'short text' feature is a special case of this general feature.

Regards,

Gregor

[PankajVPatil · Accepted solution]

An Update to the above -

The DSO now contains the custom month. Existing DSO contents had to be deleted.

In the query, have used this Char as KF object however during the click on search help (question mark icon) get a error message as "No Selection State Support!".

Is there any setting I need to enable to get the associated master data in search help ?

Thanks,

Pankaj

[PankajVPatil · Accepted solution]

Hi Gregor,

You are right. F4 for 0CALMONTH is not possible as the time char itself does not have any master data. So have created a custom base char which has calendar month like values and the char as KF is defined on this base char to be the ref. char.

So now in the query I see the F4 icon for it although upon clicking on it get a error message as "No Selection State Support!". As you mentioned I have maintained short text in the base char but the values do not appear and the error persists.

Is there something I am missing ?

Thanks,

Pankaj

[gregor_dieckmann · Accepted solution]

Hi Pankaj,

I think Analysis Office will use the default settings of the characteristic; since you don't have the characteristic in the query but the 'characteristic as key figure' try to use the F4 help settings in RSD1, second tab 'Business Explorer' and there use 'Query Filter Value Settings':

- Query Definition: Values in Master Data Table (default)

- Query Execution: Values in Master Data Table.

Regards,

Gregor

[PankajVPatil · Accepted solution]

Hi Gregor,

I tried both the settings you mentioned in above post and to complement tried different options in the 3rd setting i.e. in "Representation at Query Execution" but still get the "No Selection State Support!" error.

I am able to enter the month value manually and the data is saved to the DSO correctly.

When I enter some random value (not in MD) manually, the data gets saved in DSO by replacing that random text with # and the system in AO generates the following warning :

Data cell <char as kf IO> has no master data "ABC" or you do not have authorizations.

This means that the system recognizes the associated master data during the data save only that its not being popped up through the F4 (search help).

Thanks,

Pankaj

[PankajVPatil · Accepted solution]

Hi Gregor,

I set up the RSTT trace to check what gets triggered upon clicking of the F4 icon.

For normal char objects, the following 2 Function Modules are executed (in sequence).

- BICS_PROV_SET_STATE

- BICS_PROV_GET_MEMBERS

But in case of the Char as KF the *SET_STATE FM do not trigger and hence the *GET_MEMBERS FM is not run.

So the real question is what will enable the *SET_STATE FM to get trigger ?

Any ideas ?

Thanks,

Pankaj

[gregor_dieckmann · Accepted solution]

Hi Pankaj,

I asked the AO colleagues for help. Please implement note 2326132; this note is not released yet but will be relased soon.

Regards,

Gregor

[PankajVPatil · Accepted solution]

Thanks Gregor. For now we have opted the excel based route.

[former_member194957]

Hi Pankaj,

              It would suggestable to use HCPR instead of MPRO to create UNION scenarios. You would be able to view Char as KF and add to query. You can use the same underlying part providers and create a HANA composite provider.

Hope this helps.

Regards

Tharun.

[PankajVPatil]

Hi Tharun,

Thanks for the response.

For point #2, as an alternative we have created an aggregation level which resembles the multi provider structure and will leverage this for validation reports.