Skip to Content

This blog is part of a blog series.


Scope

In this demo a new ‘unified’ environment is created in BPC.

Role

LOB expert

User interface

BPC admin UI (HTML5)

After logging on to the HTML5 web client of BPC, we open the list of all environments available (00:12). Since we want to create a new one, we open up the respective dialog (00:16). Here you see the new option of a ‘unified’ environment type. In this case this is the only option since the system has only SAP_BW installed. If it had the BPC add-on istalled in addition, it would as well offer the ‘classic’ environment type. The environment type defines the type of data models that can be created within the environment as well as the feature set offered. In a ‘unified’ environment we can only have ‘unified’ data models, in the ‘classic’ only ‘classic’.

After choosing the ‘unified’ environment type we enter ID and description and create the new environment, which now shows up the the environment list (00:42).Finally we select the environment and connect to it. All subsequent modelling and runtime activities in the blog series will happen in the context of this environment, which you can easily verify at the bottom of the screen where you will always find ‘Environment: E2E_Demo’.



To report this post you need to login first.

3 Comments

You must be Logged on to comment or reply to a post.

  1. Apeksha Jain

    Thanks Uwe for this blog series.

    Assuming the BPC Add-on is installed, do we have only the “Classic” and “unified” types available while creating the environment?

    Also since the classic and unified are different environments, how do we plan to integrate the planning models created in the two?

    Regards,

    Apeksha

    (0) 
    1. Uwe Fischer Post author

      Hi Apeksha,

      correct, if you have the BPC add-on installed, you get both, the ‘classic’ and the ‘unified’ environment types. If you only had BW installed without the add-on, it would only offer ‘unified’.

      The models of the two environment types are quite different. See for example the transaction handling: in ‘classic’ we have the optimistic locking with last-one-wins, whereas ‘unified’ comes with pessimistic locking, what-if capabilities and consistent save. A mixture of the two is not possible. Hence, we keep them separate. Existing and further functionality can be used to integrate them, e.g. data manager which you use today to integrate BPC and BW.

      Best regards,

      Uwe

      (0) 

Leave a Reply