Skip to Content

Sharing SAP Lumira 2.0 artifacts

This blog is part of the Lumira 2.0 launch blog series

In this blog I would like to focus on how a user would be able to share his SAP Lumira, discovery edition documents with other users. Workflows in SAP Lumira, designer edition are similar, however that would be a topic for another blog.

Sharing of discovery documents can be done in following manner

  • Sharing the documents via e-mail
  • Sharing the documents via BI platform

Note: Sharing via BI platform is just one of the key advantages of using BI platform. In case you would like to know others, have a look at Why lumira add-on to BI platform is a Big Deal

Sharing the documents via e-mail

Sharing the document as lumx file via email

All the lumira documents created by a user on his desktop are stored in “SAP Lumira Documents” folder located at “C:\Users\<username>\Documents\” by default. This directory could be different based on your ini settings, but in all cases these documents are stored at one location.

A user can copy this lumira document and then attach it to an e-mail/chat and send it to his colleagues. They will be able to view these documents as long as they have a lumira client.

Sounds simple and easy, right? Even though it is, it is not the recommended way for sharing your lumira documents. The cons for this approach are as follows

  • You cannot track who all have access to this document. This may result in un-authorized and un-intended access to the document and data stored within.
  • There is no way to revoke or recall once you have shared the document.
  • Almost impossible to manage versions of the document, unless you are leveraging an external version management to manage the copies of the document.
  • You cannot schedule documents to user’s Inboxes.
  • You cannot control edit and view rights for the shared document.
  • Difficult to share updates to the documents
  • Embedding the document content within other applications
  • And so on …

Sharing the document as PDF via e-mail

User’s have an option to export the lumira document in PDF format. This is static and non-interactive. It can be used then to share with colleagues via e-mail or for the purpose of business audits.

Share option is available to the user in the top toolbar and is available both in SAP Lumira, discovery edition and on BI platform.

While exporting user would have options to

  • export specific pages or whole story
  • display filters in appendix or not

Sharing the documents via BI platform

This would be the recommended way to share your documents with fellow business users.

Users can save their documents to BI platform within the folders they have write access. Now, only users authenticated on BI platform and authorized to access that folder would be able to open and view those documents.

If they have edit rights they would be able to edit those documents right there on BI platform, and similarly if they have refresh rights they would be able to refresh such documents.

Once these documents are published to BI platform, you can also generate open document links for these documents and share this with other users via email. Or you can embed these links within other applications (like: Fiori Launchpad etc).

Saving the documents to BI platform

You can click on the Save icon in the lumira document toolbar or you can use the file menu option to save or save as the document

Save workflow would allow you to store locally or to BI platform. If you have logged in once before in BI platform during any of the earlier workflows, you would not be prompted for BI platform credentials (unlike Lumira 1.x).

Specify document name, choose the folder you would like to save to and specify if you would like to save the document without data (relevant for documents based on imported data, if you check this option for the document, system would purge the data before saving the document and document would refresh on open each time – useful when you have row-level security for your data).

The document is now listed on your BI platform

Any user authenticated to BI platform and having authorization to the specified folder will be able to view the document. Editing rights for the document can be further denied for certain users.

Sharing the documents via open document links

You can double click to view the document.

You can right click the document in listing to generate the base open document link. Or you can generate the link from within the document using the highlighed icon in the image below.

This open document link can be used to share via email as a link or embedding the document in other applications.

All, the rights to access and authorizations are respected when you share the document via open document links.

Scheduling the documents on BI platform

Further, as a user you can schedule lumira documents on BI platform. For schedule to work, document must satisfy following conditions

  • Document needs to be based on BI platform managed connections. Supported sources are HANA Import, BW Import and Universe Import.
  • You need to have SSO setup for such connections

The documents can be scheduled via right click and schedule in BI platform

Following are the options you have while setting up the schedule

Today, output format for scheduled document is lumx document only. You can choose any destination for the schedule workflow.

You must be Logged on to comment or reply to a post.
  • Do I understand it correctly that the output of a scheduled Lumira document will be for example an email with the lumx-file in the attachment? What can be configured under the "destinations" setting?

    • Hi Cesar,

      SAP Lumira server is required for viewing content on BI platform.

      You may share the lumx document on BI as agnostic content, but then they cannot be opened on BI platform.



    • You need to follow the below steps

      • Upgrade Lumira 1.31 Desktop to Patch 8
      • Open the document to be converted
      • Save the document with Conversion flag enabled

      Launch Lumira 2.0, discovery edition

      • Document will now be listed in Lumira Discovery
      • Open the Document to convert to new format (plan for manual adaptation SAP Note 2509882)
      • Save this converted document on Lumira Discovery and Publish to BI Platform



  • Hi,

    I have few *.lums ( Lumira 1.31.6) documents in BOXI4.2 SP4 server with Lumira 2.0  SP2 Add-on. Now to download & migrate those old Lumira docs to new *.lumx version, I am trying to connect my Lumira 1.31.8 client to BI Platform. But client is not showing me *.lums files in BI Platform. As a result, I am not able to download the Lumira docs to convert.

    I am getting below message:

    "You have connected to SAP BI Platform with newer version of SAP Lumira Server for BI Platform that is not compatible with your version of SAP Lumira. Saving your document to this server may render the document to be incompatible with your version of SAP Lumira. Please contact your SAP BI Platform Administrator"

    Please let me know how can I fetch and convert my old lums document to lumx document in this case.


    Animikh Chaudhury

    • Hi Animikh,

      You will not be able to connect to BI Platform with Lumira 2.0 server from a Lumira 1.x client. You can launch the BI launchpad and right click to download the .lums documents.



      • Hi Ashutosh,

        Thanks for reply!!!

        But sorry that I have not found any option to download LUMS file by right clicking on the file in BI Launchpad 4.2. It will be great, if you can provide me simple step. Please correct me if I am missing something.


        Animikh Chaudhury



    I clicked on the Generate OpenDocument link, it shows a physical server address instead of the alias name, for example, -01&sPageNumber=1&sRefresh=false

    I need a user friendly alias name, I checked the open document process properties, the property there looks correct. where else can I set this so it uses a user friendly alias name instead of the physical server address?

    • You can customize the OpenDocument URL within the CMC under "Applications" --> "OpenDocument" --> "Processing Settings".

      There you can add a server alias instead of the physical server address...

  • Hi Ashutosh,

    I am facing an unique issue while trying to schedule a lumx document(built with Lumira Designer 2.0) with BEx Query as Datasources. I am able to schedule the file in some Folders and not in some. AM I missing out on some other authorization Setting here?





  • Hi Ashutosh,

    I have few .lumx documents in BO 4.2 SP4 with Lumira 2.0 Add-on. Some of these lumx documents are created with Lumira Discovery and some with Lumira Designer. Documents created with Lumira Discovery can be scheduled without any problem but when I try to schedule lumx documents created with Lumira Designer, they are staying in running status for approximately 30 minutes and then showing status failed. I found following errors in the log file:

    Error occurred during scheduled PDF export. PDF not produced

    The export result is : [PDF was not generated within the time limit of 1800000 milliseconds]

    Do you have any idea why is Scheduling working with lumira Discovery documents and not with lumira designer documents.

    Thanks and best Regards,



        Hi Ashutosh

        Thanks for your reply. The problem was with the Lumira Designer Application. To enable scheduling, Lumira Designer Application must contain Technical Component "Export PDF" and logic to create PDF File in the "on scheduling" function of the application. I changed accordingly and now I can also schedule Lumira Designer Documents.

        Thanks and best regards


  • Hello,

    Does someone know what can be behind this error ?

    "Object failed to run due to an error while processing on the Job Server"

    I'm trying to schedule an LUMX document with SAP universes sources but after each try I received this error message and I really don't know what is the problem...

    Any tips would help me.

    Thanks and regards,


    • I am assuming you are using UNX universes. What is the Data source behind the universe? And what is the authentication option being used? Is it stored credential?