An environment is the starting point to build models or applications in SAP BPC. Environments were called application sets or “appsets” in prior versions of SAP BPC.
The environment can be described as a functional area designed to include the applications or models associated with a segment of the business. For example, you can create an environment for sales applications and another environment for head-count planning. Although the general objective of creating environments is to support a business requirement (such as sales planning, production planning, head-count planning, etc.), there are no rules about what models can be contained in an environment. You can decide how you want to develop models within an environment.
You create an environment via the Web Client. You can only create an environment using another environment as the basis. When the system is initially installed, an environment with the technical name ENVIRONMENTSHELL is available. This serves as a reference for creating other environments in the system. We caution you against making any changes to ENVIRONMENTSHELL; instead, use it to create a new environment and customize that environment for the application. You should have system administrator access to create an environment.
Dimensions represent the master, text, and hierarchy data for each of the business entities (e.g., accounts, company codes, and categories). Dimensions belong to the environment in which they are configured. Note that dimensions cannot be used or shared across environments.
A dimension can be marked as secure for a model. When a dimension is marked as secure, specific read and write access has to be granted to users who use the model so they can access the data.
properties, which provide additional meaning to the dimension. For example, an account dimension can include an account type property to indicate the type of account (whether it is an income account or an expense account). You can use property values as selection criteria for reporting.
dimension members. Each dimension member record represents master, text, and hierarchy data associated with the key of a dimension. A dimension member can store hierarchical relationships with another dimension member in the same dimension, which is very useful for reporting hierarchical relationships between data. There is no restriction on the number of hierarchies you can create.
A model is built inside an environment. It is a collection of several dimensions and is designed to meet the planning and consolidation requirements of an organization. The model is where you interface to plan, consolidate, and report data. For instance, you might have a model for a cost center planning application to compare actuals versus plan based on cost centers or a model for legal consolidations that reports your organization’s financial results.
Data Manager Package
SAP BPC provides standard out-of-the-box functionality to execute common tasks required for planning and consolidation such as currency translation, intercompany elimination, and so on. These tasks are executed via a Data Manager package.
A user is an individual who can use the models in an environment.
A team is a group of users that is created based on the users’ roles. For example, all of the developers can be grouped together and identified as a team.
Tasks. Examples of tasks are creating an environment, running a report, configuring security, and so on. Users are granted access to specific tasks based on their role in the organization.
Several tasks can be grouped together and included in a task profile. Task profiles can be assigned to a user or to a group of users in a team.
Data Access Profile
The member access profile identifies data-level access to a model and is relevant only for dimensions that were identified as secured dimensions in the model. For each model that includes dimensions marked as secured dimensions, the member access profile is configured to identify the read and write access available to users for each of the secured dimensions.
SAP BPC includes a rule-based table for defining certain common requirements for planning and consolidation. A company that has business operations in different countries may need to translate their data to one or more reporting currencies for financial reporting. The rules-based table provides a method for defining how local currencies should be translated to reporting currencies.You can set up business rules for account transformations, carry forward balances, validating data, eliminating intercompany transactions, and setting up methods and rules for consolidation of investments.
Logic script is designed to provide greater flexibility in managing data for a model and includes SQL-based and MDX-based programming structures for custom programming. You should attempt to leverage business rules before writing logic script to meet a requirement. Business rules provide a convenient table-based approach to define the rules for different conversions. But there may be business scenarios that cannot be satisfied using business rules; in these cases, logic script provides the means to achieve that objective.