BPC 10.1 Office 2013 saved reports refresh when re...

BPC 10.1 Office 2013 saved reports automatically refresh when reopened in Office 2016 when logged out of BPC.

What happens is that a user saved reports out in a folder after refreshing in Office 2013 and now when a user just opens up that report using Office 2016 without being logged in the report refreshes and the information is lost because they are not connected to BPC.

SAP Managed Tags:
EPM Add-In for Excel

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Has there been any update to this issue, or is it answered elsewhere? We are having this same issue and our IT doesn't have enough experience with EPM to solve the issue for us. I've been having to resolve other issues we've encountered with the EPM Excel Add-in since our upgrade to Excel 2016. Thanks!

ibrvanri

Better to ask new question then to comment in the old one created by "Former member"

Accepted Solutions (0)

Answers (1)

First - incorrect tag!

Not SAP BusinessObjects Planning and Consolidation for Public Sector, option for SAP NetWeaver
Has to be: EPM Add-In for Excel
And secondary: SAP BusinessObjects Planning and Consolidation, version for SAP NetWeaver

Moderator alerted!

Second - if you create a new report in 2016 is it OK?

What EPM SP is used?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

I will work on fixing the tag. If the report is created in 2016 then there is no issue. The concern is about the reports that have been generated and saved out over the past few years.

EPM SP 23.2 and EPM SP25

"EPM SP 23.2 and EPM SP25" - both used for Office 2013 and for Office 2016?

You have the issue with both EPM versions?

Try to investigate the issue yourself - with simple report with the issue try to change some report properties save and test...

We are now on Office 2016 and its happening with reports that were previously saved using Office 2013. Just trying to see if someone has encountered this without me spending too much time trying to investigate this issue.

Looks like you are the first one!

I had no issues with reports created with Office 2013 after upgrade to Office 2016.

You need to investigate the issue yourself including some test case:

Create test report in Office 2013 and then open it in Office 2016.

Please explain to me why you flagged my question? Did it break any of these rules?? Instead of helping me you flag me?

1. Log in to fully participate, giving feedback to those who help you through likes and comments. Use your real identity to build your own personal brand.

2. Be yourself. The idea of SAP Community is to represent yourself authentically. Provide as much information as you can in your profile. Using someone else’s contact information is prohibited. It is also strongly recommended that you post a photo of yourself. Do not post photos of others or graphics. Such content could be subject to moderation and removed.

3. Search before you post. There are many answered questions and helpful postings already in the SAP Community. Before posting a new question, please search the community to see if it’s already been asked /answered. That’s the fastest way to get your information.

4. Avoid slang. There are many languages and cultures represented in the SAP Community. The main language of SAP Community is English.

5. Share expertise transparently. We are a community based site that encourages public knowledge sharing. Be open about your knowledge and how you obtained it.

6. Avoid solicitations. Avoid marketing your company’s products and services. If you want people to know your affiliation with your company, put those details in your profile to make the information available to the community. Do not embed links to ads in your posts. The same applies to email solicitations and advertising. If you want someone to trust you enough to buy what you offer, share your expertise and they will seek you out.

7. Be professional and courteous. Temper negative emotions, keeping communications professional. Do not berate other members for asking questions or posting something you don’t like. The SAP Community is intended to be open on a variety of topics.

8. Be responsive. If a community member has answered your question, please mark the answer as “accepted.” By doing so, other members can find the answers more easily.

9. Don’t copy / paste other people’s content. Make sure your content is original and unique. Don't cross-post (create multiple copies of the same content using different primary tags).

10. Report rule violations. Click the alert moderator button if you believe an SAP Community member is violating the rules of engagement. Provide as much information as possible.

11. Avoid external links. Using links to market your company or products is prohibited, as is adding links to closed content or content that requires subscription fees to read.

12. Provide support feedback through the correct channel. SAP Community is a place for conversation with SAP and each other, but it is not an official support channel. For escalations to SAP support, contact the Customer Interaction Center.

Do not publish identifying or private information related to your Support experience. To protect the privacy of customers and support employees, the following will result in immediate removal: screenshots of support incidents, incident numbers, personal information, or other sensitive information.

13. Don't hijack questions. Don't post a different question in an existing question as a reply, especially if the question has not recently been active. If it is related, please create a new question and link to the old/existing question.

14. Don't resurrect questions. Don't reopen a question that has already received an answer that was marked as "accepted" by the author. If your problem looks the same and the posted solution does not work in your case, then you have a different issue and you need to create a new question referencing the existing one. You are allowed to “resurrect” a question only when the link in the answer is broken and you want the author to fix it.

I have flagged your message because of absolutely incorrect primary tag! And I already explained it in my first answer. Using incorrect tag is the most common moderator alert reason:

Hope it's clear!

Correct tagging is a critical thing for our Community!

P.S. Your old question https://answers.sap.com/questions/85015/hierarchy-update-not-overwrite.html

is also flagged by me due to incorrect tag!

So maybe allowing someone time to fix the tag and not just alert the moderator would be the more helpful thing to do instead of the action you took. Please feel free to forgo my questions in the future and allow others to answer if you are just going to take this approach and not help out. THanks

Most of the users will never correct tags (may be not your particular case). And it's the correct practice for all users in the Community to alert moderator about incorrect tag! The moderator will change the tag based on alert message. It's a routine job for moderators. It was the same for old SCN when somebody post to the space not related to the question asked.

In your case posting to "SAP BusinessObjects Planning and Consolidation for Public Sector, option for SAP NetWeaver" resulted in:

Your question is shown in a very specific tag with practically no followers - no answers will be provided.

Correcting of the tag increase visibility of your question.

Looks like you do not understand how this Community is working...

Ask a Question

Top Q&A Solution Author

User

Count