Environment (AppSet)

An Environment is the highest-level container in BPC. It represents a complete business application (e.g., "Global Finance" or "Corporate Consolidation"). Security, Dimensions, and Data Manager packages are maintained at the Environment level.

Models (Applications)

Within an Environment, you create one or more Models. A Model is a multidimensional data store (an InfoCube in the backend) designed for a specific business process.

Types of Models

Model Optimization

In the BW backend, a standard BPC Model generates a real-time InfoCube. Over time, as planning data is written, the uncompressed Delta tables (F-Fact table) grow. BPC administrators must routinely run Light Optimize (or Full Optimize) via Data Manager to compress data into the E-Fact table and update database statistics, ensuring sustained query performance.

Required Dimension Types

A Financial or Consolidation model must contain the following dimension types:

Supporting Dimension Types

• Currency (R): Reporting currency (e.g., LC, USD, EUR). Required if the model supports currency translation.
• Intercompany (I): Represents the counter-party in an intercompany transaction. Required for consolidation eliminations.
• Audit / Data Source (D): Tracks where data came from (e.g., Input, BW Load, Allocation Logic).
• User Defined (U): Custom dimensions like Product, Customer, or Project.

Dimension Properties

Properties are attributes attached to dimension members. They are critical for filtering in reports and driving Script Logic. For example, the ACCTYPE property on the Account dimension tells BPC whether to treat the account as Income (credit balance) or Expense (debit balance), which automatically flips the sign for reporting in the EPM Add-in.

Hierarchies

Dimensions can have one or more Hierarchies (e.g., a Geographical hierarchy and a Management hierarchy for Entities). In BPC Standard, hierarchies are Parent-Child based. The PARENTH1 property defines the parent of a specific member.

The /CPMB/ Namespace

When you create objects in the BPC web client, they are physically generated in BW within the /CPMB/ namespace.

Data Extraction from BW

To load actuals from standard BW InfoCubes/DSOs into BPC Standard:

1. Create a Data Manager Package using the process chain /CPMB/LOAD_INFOPROV_UI.
2. Create a Transformation File to map the BW InfoObjects to the BPC Dimensions.
3. Execute the package, which extracts data from the BW provider and writes it to the BPC InfoCube.

What is a DM Package?

A Data Manager Package is a user-friendly wrapper around a standard SAP BW Process Chain. It allows business users (planners) to execute complex background jobs without accessing the SAP GUI.

Common DM Packages

Delta vs. Full Load

When loading data via Data Manager, BPC handles data updates based on the load type:

• Update / Merge: Adds new records and overwrites existing records if the exact dimensional intersection matches. Does not clear other data.
• Replace & Clear: Clears the entire intersection of data specified in the scope before loading the new file. Crucial for ensuring deleted records in the source are removed from BPC.

Transformation Files (.xls)

A Transformation File maps the columns of a source file (or InfoProvider) to the Dimensions of the target BPC model. It contains three main sections:

*OPTIONS
FORMAT = DELIMITED
HEADER = YES
DELIMITER = ,

*MAPPING
ACCOUNT = col(1)
ENTITY = col(2)
TIME = col(3)
SIGNEDDATA = col(4)

*CONVERSION
ACCOUNT = ACC_CONVERSION.xls
    

Conversion Files (.xls)

While the Transformation file handles column-to-dimension mapping, a Conversion File handles row-by-row data translation. It acts as a lookup table.

Core Concepts

Unlike Excel formulas that run in memory, Script Logic executes on the server against the database. It processes data in batches.

Scoping (XDIM_MEMBERSET)

The most important rule in Script Logic is defining the scope. Scoping restricts the dataset pulled into server memory for the calculation. Poor scoping leads to severe performance issues.

// Restrict the memory scope to specific members
*XDIM_MEMBERSET CATEGORY = Budget
*XDIM_MEMBERSET TIME = 2026.JAN, 2026.FEB
*XDIM_MEMBERSET ACCOUNT = 400000, 410000
    

The WHEN / REC / ENDWHEN Loop

This is the fundamental processing loop in Script Logic. It evaluates records in the scope and writes new records based on conditions.

*WHEN ACCOUNT
  *IS "400000" // If the account is Revenue
    // Write a new record to the Tax account, calculating 5% of Revenue
    *REC(FACTOR = 0.05, ACCOUNT = "210000")
  *IS "410000"
    // Move the value to a different Entity
    *REC(EXPRESSION = %VALUE%, ENTITY = "US01")
*ENDWHEN
    

Default.LGF

Every model has a special script file named Default.lgf. This logic runs automatically every time a user saves data via an input schedule or journal. It should be kept extremely lightweight (e.g., simple sign-flipping or basic driver calculations) to prevent long wait times during data saves.

Why use a BAdI?

Script Logic is great for simple math, but it struggles with complex loops, string manipulation, reading from external BW tables, or highly complex allocations. BAdIs allow you to write pure ABAP code to manipulate BPC data.

The UJ_CUSTOM_LOGIC BAdI

To integrate ABAP into a BPC process, developers implement the standard enhancement spot BADI_UJ_CUSTOM_LOGIC. The ABAP developer creates a filter value (e.g., MY_ALLOCATION).

The business user can then trigger this ABAP code from a standard Data Manager Package or within Script Logic using the *START_BADI command:

*START_BADI MY_ALLOCATION
  QUERY = ON
  WRITE = ON
*END_BADI
    

Performance Implications

BAdIs are generally much faster than Script Logic for large datasets because they use internal ABAP tables and optimized SQL reads/writes directly against the HANA database. However, they require IT dependency, removing the "Finance-owned" aspect of BPC.

Report Editor

The Report Editor is a drag-and-drop interface used to define the Rows, Columns, and Page Axis of an Excel report. It automatically generates the EPM formulas needed to retrieve data.

Key EPM Functions

Advanced users build reports using direct cell-based EPM formulas rather than the Report Editor for ultimate formatting control.

Local Members

A Local Member is a calculated row or column that exists only in the Excel report, not in the BPC database (e.g., a "Gross Margin %" variance column). Local Members automatically expand and move dynamically with the report layout.

Dynamic Formatting

Because BPC reports are dynamic (rows expand and collapse), standard Excel formatting is destroyed upon refresh. EPM uses a Dynamic Formatting Sheet. You define formatting rules based on dimension properties (e.g., "If Account property CALC=Y, make the row bold and blue"), and the EPM Add-in reapplies these formats perfectly after every refresh.

Administration Workspace

Used by Modelers and Admins to manage the backend structure:

• Create and modify Dimensions and Properties.
• Manage Models and Environment settings.
• Configure Security Users, Teams, and Task Profiles.
• Manage Business Rules for Consolidation (Currency Translation, Eliminations).

Business User Workspace

Provides a web-based entry point for end-users:

• Launch the EPM Add-in contextualized to specific reports.
• View and interact with Workspaces (web-based dashboards).
• Execute and track Business Process Flows (BPF).
• Manage Document repositories.

BPF Architecture

Workspaces within BPFs

When a user clicks a step in their BPF inbox (e.g., "Enter OPEX"), the BPF automatically opens the correct EPM Input Schedule, pre-filtered to their specific Entity and Time context. This prevents users from entering data in the wrong place.

Work States

Admins define sequential states. A common sequence is:

1. Unlocked: Data entry allowed by all planners.
2. Submitted: Planners can no longer edit; Managers can review.
3. Approved: Data is locked for everyone except system administrators.

Controlling Dimensions

Work Status is applied to a slice of data defined by specific dimensions (e.g., Entity, Category, Time). Example: You can lock "Actuals" for "Q1" for "Entity US", while leaving "Entity UK" open.

Owner vs. Manager

The Entity dimension typically contains an OWNER property and a REVIEWER (Manager) property. Only the Owner can transition the state from Unlocked to Submitted. Only the Reviewer can transition the state from Submitted to Approved, or reject it back to Unlocked.

Security Components

Key Concepts to Know Cold

• /CPMB/ Namespace: Know that BPC Standard generates objects here and they shouldn't be edited via RSA1.
• Default.lgf: The script logic file that executes automatically on every data send.
• XDIM_MEMBERSET: The crucial script logic command used to restrict the data scope and ensure performance.
• Light Optimize: The Data Manager package used to compress the underlying BW InfoCube and update DB statistics.
• Data Access Profile vs Task Profile: DAP controls *what data* you see (Row-level). Task Profile controls *what actions* you can perform (App-level).

Common Interview Questions

1. What is the difference between BPC Standard and BPC Embedded?
2. Explain the difference between a Transformation File and a Conversion File.
3. How would you improve the performance of a slow-running Script Logic?
4. What is the difference between Update/Merge and Replace/Clear in Data Manager?
5. Explain the concept of Local Members in the EPM Add-in.
6. When would you choose to use an ABAP BAdI instead of Script Logic?
7. How does Work Status integrate with the Entity dimension? (Owner/Reviewer properties).
8. What BW objects are generated when you create a Model in BPC Standard?