BPC 11 Standard: Can't load BPC Model from Field-based aDSO

[former_member277290]

Hi Gurus!

I am trying to load a BPC Standard Model from an aDSO which uses field-based modeling, and not having any success so far.

When I try to validate my Transformation File, if I have an ABAP Project open in HANA Studio, or look in ST22, I can see a Runtime error "TYPE_NOT_FOUND" is occurring:

I can not see any reason for this. All of the fields in the source aDSO are of type CHAR, except AMOUNT, which is DEC 17,2. The only thing I can think so far is that this is field-based, rather than being InfoObjects.

So my question is whether Field-Based aDSOs are supported as NetWeaver data sources in BPC 11, and if so, whether anybody has come across this 'TYPE_NOT_FOUND' error before and could offer a solution.

Kind Regards,

-Elliott

[Elangovan]

Hi Elliott,

We are also facing the same issue in our implementation. Was there any reply on this issue from SAP?

Regards,

Elango

[former_member277290]

Hi Elango,

No, unfortunately the main response I have had so far is that it's not supported.

I have raised a ticket with them to see if they can fix this.

In the meantime, although it's a minor inconvenience, we have simply had to create Z InfoObjects for each of the dimensions we need to load. You only need to create InfoObjects for the fields that will be checked in the selection criteria when running the Load Package in BPC. It's okay for the aDSO to have other (non-InfoObject) fields, as long as you don't try to pull them into BPC.
We generically used CHAR 32 type InfoObjects to match the data type of BPC's created dimensions.
Do not attempt to use the generated /CPMB/ InfoObjects.

Kind Regards,

-Elliott

[Elangovan]

Hi Elliott,

Thanks for your input. We also followed the same workaround to solve this issue.

Regards,

Elango

[gregor_dieckmann]

Hi Elliott,

to 'document' that something is not supported with a dump is not 'good style', one would expect that the system checks the preconditions and in case these are not met send a message.

As far as I can see the class CL_UJD_INFOPROV_READER tries to use BW generated data elements to create the line type needed to read data with service function RSDRI_INFOPROV_READ, but in the field based case there exist no BW generated data elements; one has to use the ABAP types instead.

I suggest to open a ticket.

Regards,

Gregor

[former_member277290]

Thanks Gregor, I figured as much.

Please note, I am not attempting to 'document' anything here, simply asking a question with a screenshot of the specific error that occurs when I try to perform something. Otherwise, thanks for your suggestion.

Kind Regards,

-Elliott

[gregor_dieckmann]

Hi Elliott,

sorry for being not clear: the first sentence in my last answer was a statement about an SAP standard program, not about you. So read it as ... an SAP program should not document that something is not implemented with a dump but with an error message (ideally with a description of the possible source of the problem). This is why I suggested to open a ticket.

Regards,

Gregor

[former_member277290]

Aaah, thanks now I understand! Apologies for misunderstanding.
Yes, I have raised an incident. Hopefully the dev team can either enhance the product to successfully use Field-based InfoProviders, or at the very least implement some better error handling.

Appreciate your response.