BPC 10.0 Analysis 2.7 SP03 EPM plug-in input error - Cannot submit when sorting is activated

[lisa_savinovich]

Dear Experts,

We are testing the Analysis add-in with the EPM plug-in version 2.7 SP03 (we have BPC 10.0, NW 7.3, windows 10, and Excel 2016 ) and hit an error when saving with our existing static input template that uses filtering. The error message is "Cannot submit when sorting is activated in autofilter. To submit you have to remove the sorting and then refresh the worksheet."

Is there a way to get the Analysis add-in/EPM plug-in to ignore the autofilter as we do not want to change all of our input templates with filter (the volume templates with filtering is high)?

[former_member186338 · Accepted solution]

Bad news! Looks like the person from SAP do not understand the difference between epm report and epmsave... functions!

By the way, if you have single EPMSaveData in one cell and autofilter on different cell range - do you have this issue?

[lisa_savinovich · Accepted solution]

Hello Vadim,

Our previous version of the Analysis add-in/EPM plug-in was 2.6.100.78647. We have been using EPM since 2013 and it is the first time that we have seen this error with a version that we used.

Thank you,

Lisa

[former_member186338 · Accepted solution]

Autofilter always had issues with EPM reports. Which EPM version was used before?

[lisa_savinovich · Accepted solution]

Hi Vadim,

The scenario that you suggest works when the autofilter is in cells where the cells do not have an EPMSaveData formula.

Regards,

Lisa

[former_member186338]

Looks like in the new version EPM developers added check for autofilter. Even in previous versions it was possible to save incorrectly with autofilter enabled (but without this message). In general - don't use autofilter on input forms.

[lisa_savinovich]

Hello Vadim,

It is good advice that I will share it with our user community. I have also created a message with SAP and we found a note that we are hoping means the issue is addressed in the SP04 version.

Thank you for taking the time to review this issue and reply.

Best regards,

Lisa

[former_member186338]

Well, EPMSaveData is the third case 🙂 You have to explain it from the very beginning!

I prefer not to use EPMSaveData due to very low performance, but in this particular case with Excel autofilter - it has to work absolutely correctly! You have to contact SAP again and to stress the point that you don't have EPM reports - only EPMSaveData! Then they will correct check for autofilter and will not prevent data saving if no EPM reports!

[former_member186338]

"Static" report in general means that you have normal EPM report but with static column/row/both axis!

Look on my sample: https://blogs.sap.com/2013/03/01/static-report-in-bpc-nw-10/

[lisa_savinovich]

Hi Vadim,

I have not closed our message as we were not satisfied with their response that they would not correct it and stated that in my reply to their proposal. Based on your comment, I sent another comment attempting to clarify in the message that for the issue we noted, that we are using the EPMSaveData function. In earlier conversations with the first responder to our SAP message, I had commented that we were using the EPM function rather than an EPM report while using the term "static template". Unfortunately, we have always referred to our basic input template with the EPMSaveData function as a static input template.

Thank you,

Lisa

[former_member186338]

2 lisa.savinovich

Looks like it's some misunderstanding from both sides!

I see no reason why EPMSaveData will conflict with autofilter. But it can be a complex case when EPMSaveData is used in the local member of normal EPM report... Or some cells in the sheet are using EPMSaveData and in another place of the same sheet you have normal EPM report...

[lisa_savinovich]

Hi Vadim,

Unfortunately, SAP is taking the stance that they will not be fixing the autofilter issue for templates that use empsavedata.

Below is the reply:

"We confirm you that this limit is the same also for : epmsavedata, epmsavedataonly, epmsavecomment, epmsavecommentonly.

Excel sorting is not supported when you want to save data."

Kind regards,

Lisa

[lisa_savinovich]

Hello Vadim,

I had some further discussion with SAP on this topic and they have agreed that the current block is too restrictive; it should only be when there is an EPM report in the worksheet. They are looking into fixing this issue.

Kind regards,

Lisa

[former_member186338]

Yes, may be they will fix it in a reasonable time 🙂

[lisa_savinovich]

Hello Vadim,

The fix is timely in that it will be included in Analysis 2.7 SP05. I was able to test the early release and confirm that it was resolved.

Thank you,

Lisa

[former_member186338]

Perfect progress! My congratulations!

[former_member186338]

EVDRE is very different compared to standard EPM report! With EVDRE you don't have formulas in the cells with row and column members. It means that with EVDRE it's possible to use Excel sorting.

EPM report is a different story. Excel sorting resulted in unpredictable errors sometimes. In previous EPM versions SAP simply ignored this issue. Now they decided to block saving instead of correcting complex EPM code (and I am not sure if it's possible to correct it...)

[lisa_savinovich]

Hi Vadim,

We have never used EVDRE, thank you for clarifying. Our basic input template is static and uses the EPMSaveData function rather than an EPM Report with the sheet option allowing for data input.

Thanks again,

Lisa

[former_member186338]

And it's definitely a good idea to share the note number!

[lisa_savinovich]

Hello Vadim,

The note, 2730590 - BPC: EVDRE Save Data issue with Sorting, gave us false hope that SAP knew of the issue even though the note is EVDRE. However, it sounded similar. Unfortunately, SAP is just saying the fix is to remove the sorting in the note. We did send a message to SAP on this issue as we have thousands of templates with this Excel feature that have worked for 6 years in various versions of the EPM add-in and the Analysis add-in with the EPM plug-in. SAP's response is that we need to remove the filter/sort as there were issues with saving data when sorting was used.

Thank you for checking in and replying to this post.

Best regards,

Lisa