Characteristic ZCOSTCTR is not mapped to any attributes in the SAP HANA model Error

[Former Member]

Hi,

Currently we are working on NW BPC 10.1 Unified model.

We are trying to add ZPER(performer) and ZREV(reviewer) to /ERP/COSTCTR.

we followed below document

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20952a42-a33a-3210-b2b0-d03f3eee7...

According to the document we created Z Info object(ZCOSTCNTR) and calculation view.

While assigning the view name we are getting the bellow errors.

"Characteristic ZCOSTCTR is not mapped to any attributes in the SAP HANA model."

And the also find the attached screen shots.

Regards

Anitha

[gregor_dieckmann · Accepted solution]

Hi Anitha,

please check in transaction RSD1 whether field onf the HANA view are assigned to InfoObjects, check buttons 'Propose HANAAssignments' and/or 'Maintain HANA-Assignments', cf. also BW documentation:

Using Virtual Master Data - Modeling - SAP Library

Remark:

If you follow the idea of the How To paper you mentioned then you will get additional master data values having the attribute values you need for BPFs. If you want to be able to use the attributes ZPER, ZREV for existing cost centers as well you have use a join (instead of a union) on the HANA side and a table that contains all cost centers and the respective attributes ZPER, ZREV.

Regards,

Gregor

[Former Member · Accepted solution]

Hi Gregor,

Thanks for your reply.

I have one more doubt.

we have ZCOSTCTR (ZPER and ZREV attributes included) and /ERP/COSTCTR.

we don't have any data in ZCOSTCTR and /ERP/COSTCTR has some data(which is non editable).

That is the reason we created calculation view using union.

But the problem is we are not allowed to enter data to ZPER and ZREV either in hana or in bw maintenance screen.

Please help us how to resolve this issue we are very new to this unified model.

or please provide the document how to create work status and BPF.

[gregor_dieckmann · Accepted solution]

Hi

what do you mean with 'we are not allowed to enter data to ZPER and ZREV'? You mean you cannot maintain BW master data using transaction RSD1?

Please check the blog

http://scn.sap.com/community/data-warehousing/business-planning/blog/2013/12/23/unifying-bpc-nw-and-...

for some demos about work status and BPF.

Regards,

Gregor

[Former Member · Accepted solution]

Hi,

After creating and assigning calculation view to /ERP/COSTCTR, maintain master data option is not there in BW system,only display option is there.

Here FCO_C_COST_CENTER is a calculation view which included ZPER and ZREV from ZCOSTCTR, created in hana system.

Regards

Anitha

[gregor_dieckmann · Accepted solution]

Hi Anitha,

in BW one can expose 'external' data as BW master data, here data are exposed using a HANA view. But the 'ownership' then is not in BW but 'external'. As a result, via BW one cannot maintain the this external 'master data'.

In RSD1 one can maintain only BW owned master data.

It seems that you still confuse some objects:

• /ERP/COSTCTR is a BW characteristic; ERP master data are exposed in BW via an HANA view; master data maintenance is in ERP only
• ZCOSTCTR (as I understand you) is a BW characteristic with master data in BW, having attributes ZPER, ZREV; you can maintain master data using RSD1.

As I mentioned above the scenario in the How-To paper is not your scenario:

• How To paper: new values should be added to an existing characteristic, but the new values belong to BW not to ERP; no attributes will be changed
• Your use case: you want to have new attributes for /ERP/COSTCTR that don't exist in ERP (and thus in the HANA view); still unclear for me if you want new master data values in addition or only maintain these additional attributes for existing ERP cost centers.

Now it depends on requirements in your project how to proceed:

• Forget about /ERP/COSTCTR and use a BW characteristic ZCOSTCTR with master data in BW and the attributes you need (no HANA view); then you have to replicate the ERP cost centers to BW
• Create ZCOSTCTR based on a HANA view; the new HANA view has to join ERP cost centers with an additional storage that contains the attribute values. This storage might come from a helper characteristic in BW that just contains cost center -> ZPER, ZREV combinations maintained in BW.

Regards,

Gregor

[Former Member · Accepted solution]

Hi,

we have done in the same way.

Here we are using join condition, but we don't have similar ID's in both the cost centers.

Do we need to manually enter the cost center ids from /ERP/COSTCTR to ZCOSTCTR?

or any other way?

Reards

Anitha

[former_member434685 · Accepted solution]

Hello Anitha

Did you enter the Cost Centers manually? Or did you find some other way?

Explanations of Gregor are very useful but if you have to enter the Cost Centers manually in ZCOSTCTR then you almost lose the sense of using /ERP/COSTCTR and a HANA view.

Regards

Sergio

[gregor_dieckmann · Accepted solution]

Hi,

it seems that the topic of this thread is about a functionality that is known in BW under the name of local BW characteristic in a BW work space. But by now (as far as I know), local characteristics are not supported based on HANA views.

Example:

• BW characteristic is M with attributes A1, A2,
• 'local' characteristic L with respect to M should allow new values, overwrite some attributes, say A2, and have two new attributes A3, A4.

As already indicated above one might use a HANA view characteristic H in BW to merge M and L with HANA DB techniques. Thus M might be /ERP/COSTCTR and L might be ZCOSTCTR.

Then the idea is to store the new and changed (at least one attribute is changed) master data values in the master data table of M. Then to get the values and attributes of H one has to 'merge' the values of M and L, this is not a simple JOIN. There rules are as follows:

1. Compute the INNER-JOIN of M and L; take the attribute values A1 from M and A2, A3, A4 from L.
2. Compute the complement of the INNER-JOIN from 1. with respect to M; leave attribute A1 initial (please don't use NULL) and take A2, A3, A4 from M and UNION it to the result of 1.

This then is - more or less - the functionality of local characteristics in BW work spaces.

One 'usability' issue might remain, i.e. one does not see the existing master data values of M when maintaining values for L. To solve this one can create a 'master data maintenance' application using BW-IP. To do this you can replace characteristic M by direct update DSO with one technical key field that plays the role of L; in the data part one can include 'attributes' A2, A3, A4. Expose these characteristics as key figures and create an aggregation level with L, 1KYF_A2, 1KYF_A3, 1KYF_A4. Create an input-ready query Q on top of this aggregation level. The query then displays the content of the DSO. By definition the contents of the DSO should be the new or changed 'master data' values of M. Create a characteristic relationship on the DSO that implements the obove 'merge logic' in the CREATE method and uses 'access mode for result values' based on characteristic relationships in the 'master data' maintenance query Q. Create a planning function on SAVE that does the anti-merge, i.e. that splits the values to values that belong to M and to L; only persist the values to L in the DSO (with the attribute values, of course). New master data values can be created using new lines in the query.

In the end, this then is an implementation of the functionality of BW local characteristics with standard BW techniques, including master data maintenance using a BW query. Thus you would also get the UI (e.g. Analysis Office) 'for free'.

Regards,

Gregor

[former_member434685 · Accepted solution]

Thanks a lot for your approach Gregor. I will try it.

Sergio