Impact of Write-back optimazation setting in BPC 10.1 NW on HANA/BPC BADIs

[Former Member]

Currently we are on BPC 7.5 NW. We are planning to upgrade to BPC 10.1 on SAP HANA. After the upgrade, as per OSS note 1902743, we want to set the model level setting  'ENABLE_HANA_MDX'  to  'X'  for write-back optimization. As per OSS note, the setting can not be saved if any of the following BPC BADI implementations exists, also found that once the setting set to 'X' we cannot implement any of the following BADIs.

• Write-back BADI
• Work status BADI
• Validation BADI

I understand that OSS note 1902743 is valid for systems with HANABPC 800 and 801 releases. Creating this discussion to seek advices on finding out whether the note is also valid for BPC 10.1 HANABPC 810/BW 7.4 SP 10 as we are upgrading our environment to BPC 10.1 on HANA.

After the upgrade, our system release/SP details are as follows:

Component	Release	SP
CPMBPC	810	5
HANABPC	810	5
SAP_BW	740	10

HANA Revision 96

After the upgrade, once we set the write-back optimization setting, Can we implement any of the above three BPC BADIs ?

If we cannot implement these BADIs, what are the other best practices available to implement the above mentioned BADIs ?

Please suggest !

Thanks in advance.

[former_member186338 · Accepted solution]

Hi Ram,

Looks like you mixed ENABLE_HANA_MDX and ENABLE_NATIVE_HANA_MODEL...

Vadim

[Former Member · Accepted solution]

Hi Vadim

Thanks for the quick reply.

Thank you for correcting me. 

As per your reply, after the upgrade, we want to enable both model level parameters ENABLE_HANA_MDX and ENABLE_NATIVE_HANA_MODEL in our system which will be BPC 10.1 on HANA for write-back optimization.

Could you please let us know Is that an issue with the above mentioned three BPC BADIs in our upgrade system ?

Thanks

Ram

[former_member186338 · Accepted solution]

Hi Ram,

If you enable ENABLE_NATIVE_HANA_MODEL then you will be unable to use the mentioned badi's. No way!

Vadim

[Former Member · Accepted solution]

Hi Ram,

ENABLE NATIVE HANA MODEL pushes delta calculation in write-back to HANA. All those 3 BADI type are called during write back, but work on ABAP server. That's why they are incompatible.

Please keep in mind that this setting is Model specific, while BADI is global.

Regards,

Gersh

[Former Member · Accepted solution]

Hi Vadim & Gersh

Thanks for your responses.

Now I understand that once we enable parameter ENABLE_NATIVE_HANA_MODEL, we cannot use the above mentioned three BADIs even in BPC 10.1 on HANA(HANA 810).

Could you Please let us know Is SAP provided any other options/other BADIs to utilize the functionality offered by these three BADIs ?

I have another following question on same parameter:

Currently in BPC 7.5, in BADI implementations of UJ_CUSTOM_LOGIC, we are using methods in SAP standard class CL_UJR_WRITE_BACK to write back data to application. After the upgrade to BPC 10.1 on HANA, we want to replace methods in CL_UJR_WRITE_BACK with new methods in class CL_UJ0_WRITE_BACK.

If we enable parameter ENABLE_NATIVE_HANA_MODEL, Can we use methods in SAP standard class CL_UJ0_WRITE_BACK in BADI implementations of UJ_CUSTOM_LOGIC ?

Thanks

Ram

[former_member186338 · Accepted solution]

Just one question - do you really need ENABLE_NATIVE_HANA_MODEL? What issue do you want to solve? In many cases write back badi is the only solution to perform some calculations...

Vadim

[Former Member · Accepted solution]

Hi Ram,

To answer your first question of replacement it depends of what particular functionality you want to replace. Those BADI can be used in a lot of use cases and some of them can be replaced, but some can't.

Regarding write-back class, yes you can use it. Delta calculation is done inside it, so if that setting is ON then delta is calculated inside HANA.

Additionally, I'd recommend testing performance with that setting and without before you decide to set it.

Regards,

Gersh

[Former Member · Accepted solution]

HI Vadim

Thanks for your response.

We want to enable the parameter ENABLE_NATIVE_HANA_MODEL to improve the write back performance as per OSS note. That is the only purpose.

Hi Gersh

Thanks for your clarification that we can use write back class in the BADI implementation of UJ_CUSTOM_LOGIC even parameter ENABLE_NATIVE_HANA_MODEL enabled.

Hi Vadim & Gersh

Are there any other issues we will face if we enable the ENABLE_NATIVE_HANA_MODEL ?

Thanks

Ram

[former_member186338 · Accepted solution]

"We want to enable the parameter ENABLE_NATIVE_HANA_MODEL to improve the write back performance as per OSS note. That is the only purpose." - do you really have a performance issue?

Vadim

[Former Member · Accepted solution]

Hi Ram,

If you want to use BADI then don't switch on ENABLE_HANA_MDX

It is just a different engine to calculate MDX.

Using ABAP to calculate MDX won't have a huge performace issue.

that setting is there for those who doesn't use BADI and want to take the full benefit of HANA.

Andy

[Former Member · Accepted solution]

Hi Vadim

Currently we are in the process of upgrade of system to BPC 10.1 on HANA. As of now, we don't have any performance issues.

Hi Andy

Thanks for the reply.

Thanks

Ram

[former_member341535 · Accepted solution]

Hi Vadim,

Can you please explain why “no way”?

We have implemented a write back BADI calling a Stored Procedure it in a project and it works well.

We did activate ENABLE_NATIVE_MODEL and we have created a disaggregation procedure based on the HANA views generated by this parameter.

This procedure is then triggered by a write back BADI so data is disaggregated while data is input.

Should we not have done that?

Thanks and Regards