Unassigned members in BPC 11.1 embedded business rules

[former_member601686]

Hi gurus,

We have an embedded model for Consolidation on BPC 11.1. We extract the data from S/4HANA with no mappings, meaning that when a field on ACDOCA is not informed (normal occurrence in some fields, eg transaction type), this is an unassigned value on BPC. This does not work for business rules as per SAP's response below - we had raised a ticket:

'Other Dimension Filter' of elimination business rule header is far complicated than you imagine. It not only support defining a base member, but also a parent member of a specific hierarchy or even dimlist.

Thus, if BPC enhance Other Dimension Filter to support # (No matter you directly define it in the filter, or use DIMLIST or parent). It is a complicated enhancement and easily lead to regression issues.

Obvious workaround would be to use mappings between S/4 and BPC, assigning D_NULL type of member in these dimensions. This defeats the purpose of having a common data dictionary across S/4 and BW/BPC plus it has an impact on performance on our CDS Views.

Has anyone come across this situation? Any suggestions on how to avoid this situation?

[former_member186338]

"Obvious workaround would be to use mappings between S/4 and BPC, assigning D_NULL type of member in these dimensions. This defeats the purpose of having a common data dictionary across S/4 and BW/BPC plus it has an impact on performance on our CDS Views." - do you checked that the performance impact is significant? Please provide full sequence of HANA views from ACDOCA in S/4 to BPC11

[former_member601686]

Thanks for your response Vadim. Looking at the CDS views in more detail, this would only imply an if-then-else statement to assign a dummy null member by dimension. We haven't had time to do a proper performance analysis, but since our views are quite straightforward, I would expect this to not have an impact in the performance. Still goes against following the same principles across S/4 and BW/BPC, but seems like the only possible solution based on SAP support responses.

[former_member186338]

You have a nonstandard requirement - to filter for some specific fields in the rules and this field can be empty. To my mind, assigning dummy member on the HANA view level is a good solution without real performance impact.