In Oracle Profitability and Cost Management Cloud Service (PCMCS), a profitability application is the configured model that implements the organisation’s cost allocation and profitability calculation methodology within the Oracle EPM Cloud environment. The profitability application defines the cost pools (the groupings of costs to be allocated), the allocation dimensions (the business units, products, channels, and geographies across which costs are distributed), the allocation rules (the calculation sequences that move costs from pools to dimensions using defined drivers), and the driver data (the activity metrics — headcount, transaction volumes, floor space — that determine how costs are distributed to recipients). A profitability application is built on top of an Essbase ASO cube — Oracle PCMCS uses ASO as its calculation and storage engine, which determines the profitability application’s performance characteristics and its supported calculation patterns.
PCMCS Architecture Components
| Component | Function | Design Consideration |
|---|---|---|
| Allocation model | Defines the overall methodology: standard costing, activity-based costing, step-down allocation | Must reflect the organisation’s actual management accounting approach, not a generic template |
| Dimensions | Cost pool, allocation dimension (entity/product/channel), driver, period, scenario | Dimensions determine what analytical views the profitability model can produce |
| Allocation rules | Step-by-step calculation sequences that move costs from source pools to target dimensions | Execution sequence matters — a rule that references the output of a prior rule must run after it |
| Driver data | Activity metrics used to weight cost distribution across allocation recipients | Driver data must be updated each period; stale drivers produce incorrect allocations silently |
| Point of view (POV) | Filters the model execution by scenario, year, and period | POV must be set correctly before each allocation run |
| ASO cube | Essbase ASO database that stores the allocation model’s data and results | ASO-specific constraints apply: no write-back; dynamic aggregation; large member count support |
Allocation Execution Sequence
PCMCS allocation rules execute in a defined sequence that is configured by the EPM architect. This sequence embodies the organisation’s allocation methodology: in a step-down cost allocation model, corporate overhead is allocated to business units first, and business unit costs (including their allocated share of corporate overhead) are then allocated to products or customers. If the execution sequence is reversed — business unit-to-product allocation running before corporate-to-business-unit allocation — the product-level profitability results do not include the corporate overhead component, understating true product cost. The allocation execution sequence must be designed from the management accounting methodology, not from the convenience of the EPM configuration interface.
GCC Context: Profitability in Diversified Conglomerates
PCMCS is particularly relevant for GCC family-owned conglomerates and diversified holding companies where a shared service centre provides finance, IT, HR, and legal services to multiple operating subsidiaries. Allocating shared service costs to subsidiaries — and within subsidiaries to product lines and customer segments — produces the segment-level profitability view that holding company management and board members need for capital allocation decisions. For GCC groups preparing for IFRS 8 segment disclosures, the PCMCS profitability model provides the calculation infrastructure that produces the segment profit figures used in statutory disclosure — ensuring that the internal management view of segment profitability and the external IFRS 8 disclosure are derived from the same governed model.
What Goes Wrong in Practice
The most common PCMCS profitability application failure is driver data that is not updated at the frequency required by the allocation methodology. An IT cost allocation that uses headcount as the driver produces incorrect results when headcount data from the prior quarter is used for the current quarter’s allocation — because headcount has changed as employees joined, left, or moved between business units. Driver data update processes must be as rigorous as the financial data load processes they support; a PCMCS application with current financial data but stale driver data produces allocation results that are numerically precise but factually incorrect.
How Loop Wise Solutions Designs Profitability Applications
We design PCMCS profitability applications from the management accounting policy — documenting the allocation methodology, the driver definitions, and the execution sequence in a profitability model specification before any EPM configuration begins. The specification is reviewed and approved by both the finance team (who own the methodology) and the EPM architecture team (who must implement it) before the application is built.
