SAP Profitability and Performance Management (PaPM)

What is SAP PaPM and What Problems Does It Solve?

Bottom Line Up Front: SAP Profitability and Performance Management (PaPM) is a cloud-native, in-memory allocation and costing engine built on SAP HANA. It enables finance and costing teams to model complex allocation logic, simulate scenarios, and disaggregate costs to granular profit objects, without requiring custom ABAP development or locking logic inside S/4HANA's embedded analytics or SAC Planning layer.

Core Capabilities

• Multi-Dimensional Allocation Engine: Supports rule-based, statistical, and driver-based allocation methods across cost centers, business units, products, contracts, and customers simultaneously. Handles thousands of allocation steps in a single model.
• Flexible Cost Object Modeling: Define custom profitability dimensions beyond SAP's standard CO-PA, including program, contract CLIN, customer, region, or any user-defined attribute. Enables margin analysis at whatever grain the business requires.
• Scenario Simulation and What-If Analysis: Model alternate rate structures, overhead pools, or driver assumptions without affecting actuals. Enables pre-award cost modeling, bid pricing, and EAC sensitivity analysis in an isolated environment.
• Shared Service and Overhead Chargeback: Purpose-built for allocating shared service costs (IT, HR, facilities, engineering overhead) across consuming business units or programs using consumption-based or negotiated rates.
• Transfer Pricing and Intercompany Costing: Supports cost-plus, market-based, and dual-rate intercompany pricing models. Particularly relevant for A&D entities with intracompany manufacturing, service delivery, or government-compliant cost buildup requirements.
• Real-Time Calculation on HANA: Leverages SAP HANA's in-memory columnar processing for near-real-time cost calculations. Eliminates batch-only overnight allocation runs and enables iterative, ad hoc cost analysis during the month.

Key Business Problems Solved

• Opaque overhead allocation: Replaces black-box cost center assessment cycles with transparent, auditable, driver-based logic visible to finance and program teams.
• Inflexible CO-PA: Overcomes the fixed-dimension constraints of SAP costing-based CO-PA, enabling dynamic profitability views without schema changes.
• Disconnected planning vs. actuals: Bridges the gap between SAC Planning (formerly BPC) / Integrated Business Planning allocation assumptions and actual CO postings by unifying models in one engine.
• Manual Excel-based allocations: Replaces shadow spreadsheet models that finance teams build outside SAP to simulate allocations, eliminating reconciliation burden and audit risk.
• Slow period-close allocation cycles: Reduces multi-hour batch allocation runs to minutes using HANA's parallel processing architecture.

How PaPM Interfaces with SAP S/4HANA

Data flow: S/4HANA (FI/CO actuals, cost centers, internal orders, WBS elements, material ledger) to HANA Views / CDS (Core Data Services views expose S/4 data to PaPM functions without data replication) to PaPM Engine (allocation functions, rate tables, driver quantities, simulation environments) to Writeback / Reporting (CO-PA, ACDOCA, S/4HANA Embedded Analytics, SAC, or custom HANA tables).

Integration Mechanisms

• SAP HANA Native Connectivity: When PaPM and S/4HANA share the same HANA database (on-premise or RISE), PaPM reads source tables (ACDOCA, COSP, COSS) directly via HANA views: zero data movement, no latency.
• Remote HANA Connection (SDA): For separate HANA instances, Smart Data Access (SDA) federates S/4 tables into PaPM as virtual tables. Suitable for cloud-to-on-prem hybrid deployments.
• BTP Integration / OData APIs: PaPM on BTP exposes OData services for loading master data, rate tables, and driver quantities from S/4 or third-party systems (e.g., project management, HR headcount feeds).
• Posting Logic: Writeback to CO-PA (ACDOCA): PaPM can post calculated profitability records directly back into the Universal Journal (ACDOCA) as actual line items, maintaining a single source of truth in S/4. Postings carry full document trail with reference to PaPM function and model version.
• Posting Logic: Statistical vs. Actual: PaPM supports both statistical postings (for reporting/analysis without impacting CO actuals) and actual FI/CO postings (for period-close and financial reporting). This dual-mode is critical for scenario work that must not contaminate live books.
• Master Data Synchronization: Cost center hierarchies, profit center structures, and WBS element attributes can be replicated from S/4 MDG or directly via HANA views, ensuring PaPM models stay aligned with the controlling area structure.
• Quantity-Based Driver Tables: Headcount, square footage, machine hours, throughput, and other non-financial drivers are loaded from S/4 HR, PM, PP modules or external files and used as allocation keys within PaPM functions.
• SAP Analytics Cloud Integration: PaPM results surface natively in SAC for live plan/actual reporting, margin dashboards, and variance analysis, using S/4HANA's embedded analytics layer without a separate data movement step.

Deployment Options

• On-Premise / RISE with SAP: PaPM deployed on same HANA appliance as S/4. Tightest integration, lowest latency. Requires adequate HANA memory sizing. Common for large enterprise deployments prioritizing data residency.
• SAP BTP (Cloud): PaPM as a cloud service on BTP. Connected to S/4 (on-prem or cloud) via HANA Cloud connections or replication. Preferred for greenfield or companies not on HANA in-house.
• Hybrid: S/4HANA on-premise plus PaPM on BTP. Connected via SDA or data replication. Common migration path; introduces latency and replication complexity that must be managed.

Restrictions, Limitations, and Potential Downsides

SME Perspective: PaPM is powerful but not a universal answer. The following constraints are material to an A&D organization with complex program cost structures, government accounting requirements, and significant existing SAP investment. These should be weighed carefully before committing to PaPM as the primary costing engine.

• Not a native CAS / DCAA-compliant system: PaPM has no built-in FAR/DFARS cost accounting standard logic. Indirect rate structures (G&A, Fringe, OH) must be custom-configured, and audit trail requirements under DCAA must be enforced through design decisions, not product defaults.
• Limited native project/WBS costing: PaPM does not replace PS (Project System) or the CO product costing module. It is an allocation and profitability layer, not a job costing or standard cost estimate engine. EAC management remains in PS/CO.
• Significant model design complexity: Building allocation models that accurately reflect an A&D indirect rate structure requires deep knowledge of both PaPM's function types and the underlying CO configuration. Poorly designed models produce misleading results that are hard to audit.
• Separate licensing cost: PaPM is not included in the base S/4HANA license. It requires a separate SAP subscription, adding cost that must be justified against the value delivered over existing CO capabilities.
• HANA dependency: PaPM on-premise requires an SAP HANA database. Organizations on AnyDB (Oracle, SQL Server, DB2) running S/4 cannot deploy on-premise PaPM without a HANA migration or BTP deployment.
• Writeback performance and locking risks: When PaPM posts results back to ACDOCA at scale, it can create database lock contention during period-close windows if not carefully sequenced with other CO closing steps.
• Steep learning curve for costing SMEs: PaPM's function-based modeling paradigm is unfamiliar to traditional CO consultants. Talent scarcity is real. Experienced PaPM architects are rare compared to CO or CO-PA specialists.
• Versioning and change management complexity: Managing multiple allocation model versions (plan, actual, simulation, prior period restatements) requires rigorous governance. Without it, version proliferation leads to reconciliation nightmares.
• Limited out-of-the-box A&D content: SAP's industry best-practice content for PaPM is generic. There are no pre-built templates for CPFF/CPIF/FFP contract types, forward pricing rate development, or CAS-compliant pool/base structures.
• Cloud deployment data residency concerns: For classified or ITAR-sensitive environments, deploying PaPM on BTP public cloud may conflict with data residency and access control requirements without dedicated sovereign cloud arrangements.

How PaPM Applies to a Large Aerospace and Defense Company

Core A&D Costing Challenge: Large A&D primes operate under Cost Accounting Standards (CAS), DCAA audit scrutiny, and multi-layered indirect rate structures across dozens of business units, sites, and contract types. The challenge is not just computing costs: tracing, allocating, and defending them across a complex, regulated cost pool hierarchy.

High-Value Use Cases

• Indirect Rate Development and Simulation: Model forward pricing indirect rates (labor overhead, fringe, G&A, material handling) using PaPM's scenario engine. Compare Negotiated rates vs. Actuals vs. Budget rates. Simulate impact of headcount changes, facilities consolidation, or R&D reclassification on pool/base ratios before locking rates for bid submissions.
• Program-Level Profitability Allocation: Allocate shared engineering, tooling, test, and G&A costs down to individual programs, contracts, or CLINs using driver-based logic (direct labor hours, direct cost, headcount). Enables true program margin visibility beyond what standard CO-PA provides with fixed dimensions.
• Segment Reporting and Business Unit Costing: For A&D companies organized into business segments (Space, Defense Systems, Aviation), PaPM enables segment-level cost buildup with inter-segment service cost transfers, consistent with ASC 280 / IFRS 8 segment reporting requirements.
• Make vs. Buy and Subcontract Analysis: Simulate fully-burdened cost of internal manufacturing vs. subcontracting by repointing allocation bases and driver tables. PaPM's what-if environment allows rapid scenario turnaround without touching live CO data.
• Bid and Proposal Cost Modeling: Prototype cost buildup for new contract proposals using historical actuals and forward rates as inputs. Model multiple rate scenarios (most likely, ceiling, floor) to stress-test bid economics before submission.
• Intracompany Transfer Pricing: Manage cost-plus or negotiated-rate intercompany charges between manufacturing sites, shared service centers, and program offices within the same corporate structure, with full audit trail back to the originating cost element.

Integration Points with A&D-Specific SAP Landscape

• PS / cProjects (Project System): Pull WBS-level actuals from Project System as PaPM source data to allocate overhead to specific programs and contracts by CLIN or deliverable.
• SAP Manufacturing / PP-PC: Use standard cost estimates and actual order costs from Production Planning as inputs to program cost calculations, bridging shop floor to contract-level profitability.
• SAP HR / Time Management: Drive labor overhead allocations using actual direct/indirect labor hours from CATS timekeeping, ensuring rate calculations reflect actual workforce deployment, which is critical for DCAA floor checks.
• GovCon Billing (SD/PSCD): Cross-reference PaPM allocated costs against billed costs on T&M and CPFF contracts to identify over/under-recovery situations before invoicing.

How Standard S/4HANA Accomplishes the Same Capabilities Without PaPM

Key Point for SMEs: Many PaPM capabilities are achievable within standard S/4HANA, requiring deeper CO configuration, potentially S/4HANA's embedded analytics or SAC for reporting layers, and acceptance of certain flexibility limitations. The question is not "can S/4 do this" but "at what configuration cost, flexibility, and maintenance burden."

Capability	PaPM Approach	Standard S/4HANA Alternative
Multi-step overhead allocation	PaPM function chains with full auditability and scenario support	CO Assessment / Distribution cycles with iterative cycle configuration. Functional but rigid: changing allocation logic requires CO cycle reconfiguration and retesting. (Native)
Profitability analysis beyond fixed CO-PA dims	User-defined environments with unlimited custom characteristics	Account-based CO-PA (ACDOCA-based) supports additional characteristics via enhancement, but requires ABAP development and schema changes. (Effort Required)
Scenario / simulation costing	Native simulation environments in PaPM, isolated from actuals	Separate controlling area or plan version in CO. Operationally cumbersome; requires duplicating master data and actuals manually. (Workaround)
Driver-based allocation (headcount, sq ft)	PaPM statistical key figure integration with any data source	CO Statistical Key Figures (SKFs) natively support driver-based allocation, but are limited to CO master data objects. External driver data requires custom load programs. (Mostly Native)
Real-time / on-demand allocation	HANA in-memory execution; near-real-time for ad hoc requests	CO period-end allocation runs are batch jobs. Some real-time cost splitting possible via activity-based cost objects, but not equivalent. (Batch Only)
Transfer pricing / intercompany rates	Built-in rate tables, dual-rate support, scenario modeling	SAP Intercompany (SD/MM/FI-based) or CO activity type price planning. Configurable but complex for multi-entity structures. (Native)
Indirect rate development / forward pricing	Custom rate simulation within PaPM environments	No native forward pricing rate tool. Must use SAC Planning (formerly BPC), IBP, or Excel-based rate models with CO plan integration. (Gap: External Tool)
Fixed burden rate application (FPRA)	PaPM rate tables store FPRA rates; scenario versions compare FPRA vs. actuals	SAP Costing Sheets (CO) natively apply fixed overhead rates (fringe, OH, G&A, material handling) to cost objects. Primary mechanism A&D companies use to apply FPRA rates. (Native: Preferred)
Granular program/contract margin reporting	PaPM environments write to custom HANA tables or ACDOCA; consumed in SAC	CO-PA account-based plus profit center accounting. Sufficient for many use cases if profit centers are structured at program level. (Mostly Native)

The S/4 Native Argument

• CO Assessment Cycles cover the majority of cost center-to-cost center and cost center-to-profitability segment allocations when configured properly. For companies with well-structured CO hierarchies, this is often sufficient.
• Account-Based CO-PA (ACDOCA) in S/4HANA eliminates many of the reconciliation problems of costing-based CO-PA and provides a solid foundation for multi-dimensional margin analysis without PaPM.
• SAC Planning (formerly BPC) can cover rate simulation and forward pricing scenarios by connecting to CO plan versions, avoiding the need for a separate PaPM environment for planning-only use cases.
• SAP Costing Sheets are the single most important native capability for FPRA-based burden application. They allow government contractors to apply negotiated fringe, overhead, G&A, and material handling rates directly to manufacturing orders, production orders, internal orders, and project WBS elements, with full traceability to the originating cost element base. This is standard CO functionality and does not require PaPM.
• The honest trade-off: Standard S/4 requires more CO configuration expertise, ABAP for edge cases, and acceptance of batch-only allocation timing. PaPM trades those constraints for additional licensing cost and a new skill domain.

SAP-Embedded Third-Party Solutions for GovCon Costing and ICS

Closing the Gap Without PaPM: A category of SAP-certified, embedded GovCon solutions addresses the ICS/ICR gap that standard S/4HANA leaves open. These products run natively within the SAP environment, draw directly from ACDOCA and CO cost objects, and produce DCAA-adequate ICS schedules without requiring a separate analytics platform or manual Excel preparation. For organizations weighing PaPM against the standard S/4 toolkit, these solutions represent a targeted and proven alternative for the indirect rate calculation and annual submission use case specifically.

• Dassian GovCon: ICR and Forward Pricing Application (FPA): SAP channel partner solution with two relevant modules: the ICR module generates the full FAR 52.216-7 ICS schedule package (Schedules A through O) directly from SAP cost objects, and the FPA automates indirect rate calculation by pool and base from SAP actuals and projections. Together they cover the indirect rate lifecycle from FPRA development through final ICS submission, within the existing SAP environment.
• Cognitus CIS-GovCon: Incurred Cost Reporting: SAP-endorsed, S/4HANA-embedded solution supporting FAR, DFARS, CAS, and DCAA compliance. The incurred cost reporting module automates ICS schedule preparation directly from S/4HANA cost and contract data, aligned to the DCAA adequacy checklist, alongside NICRA rate management, contract flowdown, and audit readiness in a unified SAP-native footprint.

Additional considerations:

• Key distinction from PaPM: Both Dassian ICR/FPA and Cognitus CIS-GovCon are purpose-built for the GovCon indirect rate and ICS use case, with pre-configured DCAA schedule formats, CAS-aligned pool/base structures, and contract-level cost traceability. PaPM is a general-purpose allocation and profitability modeling engine that can be configured to address similar scenarios but requires significant custom design to replicate this compliance-specific functionality.
• Complementary positioning: These solutions and PaPM are not mutually exclusive. A contractor could deploy Dassian or Cognitus for ICS production and FPRA rate development within SAP, while using PaPM for broader program profitability modeling, segment reporting, and scenario analysis that extends beyond the indirect rate lifecycle.
• Evaluation consideration: For organizations whose primary unmet need is ICS automation and indirect rate calculation within SAP, a targeted GovCon add-on solution may offer a faster path to value, lower implementation risk, and stronger DCAA audit defensibility than a PaPM-based custom build.

SAP Costing Sheets and FPRA Rate Application in S/4HANA

The Most Important Native Capability SMEs Must Understand: For CAS-compliant government contractors, SAP Costing Sheets are the workhorse of burden rate application. They are how most A&D companies apply FPRA-negotiated rates to contracts today, without PaPM, without custom code, and with DCAA-auditable traceability baked into the CO posting logic. Understanding costing sheets is prerequisite to any honest evaluation of PaPM's incremental value.

What is an SAP Costing Sheet?

• Definition: A Costing Sheet is a CO configuration object that defines how overhead surcharges are calculated and applied to cost objects (production orders, internal orders, WBS elements, cost estimates). It specifies a base cost element group, an overhead rate or percentage, a credit object (overhead cost center), and the conditions under which the rate applies.
• How it maps to FPRA: Each FPRA rate type, including Fringe, Labor Overhead (by department or labor category), Material Overhead, Other Direct Cost (ODC) burden, and G&A, can be represented as a row in a costing sheet. The negotiated rate percentage is stored in Overhead Rate configuration, updated annually (or upon rate renegotiation) without touching program data.
• Condition-based rate logic: Costing sheets support condition tables that vary rates by plant, controlling area, company code, order type, or custom fields, enabling a prime with multiple sites and business units to apply different FPRA rates by location or segment within a single SAP system.
• Credit posting: When overhead is applied via costing sheet, SAP automatically posts a credit to the designated overhead cost center, maintaining the balance between absorbed overhead and actual cost pool spend. This is the core reconciliation mechanism for over/under-absorption tracking.

Costing Sheet Architecture for A&D FPRA Rate Structure

• Fringe Benefits Rate: Applied as a percentage of direct and indirect labor cost elements. Condition logic can differentiate regular vs. overtime, exempt vs. non-exempt, or union vs. non-union labor categories. Credit posts to Fringe Benefits cost center pool.
• Labor Overhead (OH) Rate: Applied as a percentage of direct labor (post-fringe or pre-fringe depending on contractor's CAS disclosure). Typically defined by department, division, or site. Credit posts to corresponding overhead cost center pool for absorption tracking.
• Material Handling (MH) Rate: Applied as a percentage of purchased parts, subcontract, or raw material cost elements. Covers procurement, receiving, inspection, and storage costs. Isolates labor-driven pools per CAS 410/418 requirements.
• G&A Rate: Applied as a percentage of total cost input (TCI) or value-added base per the contractor's CAS disclosure. Typically applied as the final layer after all other burden has been absorbed. Credit posts to G&A expense pool.
• IR&D / B&P Surcharge: Configurable as a separate costing sheet row to apply IR&D and B&P cost recovery rates, keeping allowable vs. unallowable cost separation explicit within the CO posting chain, supporting FAR 31.205 compliance.
• Special Tooling / Facilities: Dedicated costing sheet rows for facilities capital cost of money (FCCM) per CAS 414 and cost of money per CAS 417, applied separately from labor overhead for contractors with GFF or contractor-acquired special tooling.

How Costing Sheets Interact with the Broader CO Architecture

• Standard Cost Estimates (CK11N / CK40N): Costing sheets feed directly into material cost estimates, building the full cost-rolled standard cost (direct material plus direct labor plus overhead burden) that becomes the inventory valuation basis and the cost estimate used in contract proposals.
• Production and Manufacturing Orders (CO-OBJ): During actual order execution, costing sheets recalculate overhead surcharges on actual costs posted to the order. WIP and variance calculation at period-end reflects actual vs. planned overhead absorption, which is the basis for over/under-recovery reporting.
• Internal Orders and WBS Elements (CO-OPA / PS): For cost-reimbursable contracts, costing sheets apply burden to program WBS elements as direct costs are posted, creating a real-time burdened cost view without manual allocation runs. Costs on the WBS are burdened at the negotiated FPRA rate in real time. This is the most direct DCAA-relevant application.
• Actual Costing / Material Ledger: In S/4HANA with actual costing enabled, costing sheet surcharges participate in the actual cost rollup, allowing end-of-period revaluation of WIP and finished goods at actual (vs. standard) overhead absorption rates.
• Period-End Overhead Calculation (KGI2 / CO43): The overhead calculation transaction reprocesses all open orders and WBS elements against current costing sheet rates at period-end, the mechanism for applying rate changes mid-year upon FPRA amendment.

PaPM and Costing Sheets: Two Deployment Approaches

Not an Either/Or Decision: PaPM and costing sheets are not mutually exclusive. There are two credible deployment models for organizations considering PaPM alongside an existing costing sheet architecture. Understanding the trade-offs of each is essential before committing to either path.

Option A: PaPM in Conjunction with Costing Sheets

• How it works: Costing sheets continue to apply FPRA-negotiated burden rates directly to production orders, WBS elements, and internal orders in real time, as they do today. PaPM is layered alongside as the rate development and simulation engine, used to model pool/base projections, stress-test rate scenarios, and support FPRP negotiations. Once rates are agreed, they are loaded into costing sheet configuration as normal.
• Why this is the lower-risk path: Costing sheets remain the system of record for rate application. All downstream modules and tools that reference costing sheet rates, including standard cost estimates (CK11N), material ledger actual costing, and third-party tools that read CO configuration, continue to function without modification.
• What PaPM adds in this model: It addresses the gap that costing sheets cannot fill, specifically the rate development, simulation, and scenario modeling work that today lives in Excel or SAC Planning. The rest of the architecture is unchanged.
• The analysis in this document applies to this model. Where this paper evaluates PaPM capabilities relative to standard S/4 functionality, it assumes costing sheets remain in place for rate application and PaPM is used for modeling and analysis upstream of that process.

Option B: PaPM Replaces Costing Sheets for Rate Application

• How it works: Rather than loading agreed FPRA rates into costing sheet configuration, the rates are stored in PaPM rate tables. PaPM applies the overhead burden calculations and writes results back to ACDOCA or CO-PA, replacing the costing sheet mechanism for overhead posting entirely.
• The appeal: PaPM offers more flexibility for complex, iterative rate structures where interrelated pools require circular or multi-pass resolution logic that costing sheets cannot handle natively. Rate changes can be applied within PaPM models without touching CO configuration directly.
• The significant downside: Costing sheets are deeply embedded in the standard SAP A&D architecture. Standard cost estimates (CK11N/CK40N), production order costing, material ledger actual costing, and a range of third-party GovCon tools and reporting configurations reference costing sheet rates as a native data source. Replacing costing sheets with PaPM as the rate application mechanism requires those dependencies to be identified and rerouted to PaPM. In a mature A&D SAP environment, this is a non-trivial effort with material audit risk during transition.
• When it may be justified: If a contractor's indirect rate structure has complexity that genuinely exceeds what costing sheets can model, such as multi-tier iterative pool interactions or real-time mid-period rate adjustments at scale, Option B may be worth the implementation cost. For most large primes with established CO architectures, Option A is the more practical starting point.

Where Costing Sheets Fall Short Regardless of PaPM Deployment

• Costing sheets apply rates; they do not build them. The FPRA percentage stored in costing sheet configuration must come from somewhere, typically an Excel model or SAC Planning. This is the gap PaPM is positioned to address in both deployment options.
• No what-if simulation capability. Costing sheets cannot model alternate rate scenarios against live program costs without changing production configuration, a risk no program controller would accept during an active contract period.
• Audit support for rate justification is entirely outside the costing sheet framework. Demonstrating to DCAA how the FPRA rate was derived, what assumptions drove pool and base projections, and how sensitivity was tested requires a separate planning and modeling environment regardless of which deployment option is chosen.

The Forward Pricing Rate Proposal to Agreement Process

Why This Process Matters to SAP Configuration: The FPRP-to-FPRA lifecycle is the single most consequential input to how SAP costing sheets, overhead cost centers, and indirect rate structures are configured and maintained. Every SAP rate table, every costing sheet percentage, and every overhead cost center budget ties back to a negotiated rate agreement with the cognizant federal agency.

Key Definitions

• FPRP: Forward Pricing Rate Proposal: A contractor-submitted document proposing the indirect rates it expects to incur in a future period, typically the next 1 to 5 fiscal years. Includes pool and base projections, methodology narrative, and supporting schedules. Submitted to the ACO and audited by DCAA.
• FPRA: Forward Pricing Rate Agreement: A bilateral agreement between the contractor and the ACO establishing the indirect rates to be used for pricing proposals, contract modifications, and progress payments during the covered period. Subject to final settlement via incurred cost audit.
• FPRR: Forward Pricing Rate Recommendation: When a formal FPRA cannot be reached, DCAA issues an FPRR that the ACO uses instead. Contractors may use FPRR rates for proposal pricing but assume the risk of rate variance at final settlement.
• Provisional Billing Rates: Interim rates used for billing on cost-reimbursable contracts when FPRA rates have not yet been negotiated for the current period. Set by ACO agreement; adjusted at year-end when final rates are established.

The Full FPRP to FPRA Lifecycle

Phase 1: Internal Preparation - Rate Development and Pool/Base Projection

• Finance / contracts pricing team builds multi-year forecast of indirect cost pools (labor, fringe, facilities, G&A expenses) and allocation bases (direct labor hours, direct costs, total cost input)
• Assumptions include headcount plans, facility lease/depreciation schedules, major capital investments, and anticipated direct business volume by segment
• CAS disclosure statement reviewed to confirm pool/base methodology is consistent with disclosed practices
• SAP touchpoint: Historical actuals extracted from ACDOCA / cost center reports form the base year anchor for projections; prior year costing sheet rates compared to actuals to compute over/under-recovery history

Phase 2: Proposal Submission - FPRP Package Submission to ACO / DCAA

• Contractor submits FPRP per FAR 42.1701 requirements: rate schedules, pool/base worksheets, narrative methodology, organizational charts, and supporting cost data
• Proposal covers each indirect cost pool separately: Fringe, Site-specific Labor Overhead, Material Handling, Subcontract Administration, IR&D/B&P, and G&A
• Submission typically 6 to 12 months before the start of the rate period to allow DCAA audit and ACO negotiation time
• Large primes with multiple business segments may submit segment-specific FRPPs, potentially audited by a different DCAA office

Phase 3: DCAA Audit - Audit of Forward Pricing Rate Proposal

• DCAA auditors review historical cost trends from the contractor's books (typically from SAP) against projections, verifying reasonableness, allowability (FAR Part 31), and consistency with CAS disclosures
• Floor checks: DCAA may physically verify headcount, confirm time charging practices, and validate that labor categories in proposals match actual job assignments in SAP HR / CATS timekeeping
• DCAA issues an audit report with questioned costs, unsupported projections, or recommended rate adjustments, typically expressed as a range or point estimate per pool
• SAP touchpoint: Cost center actual reports, cost element line item details (KSB1), and statistical key figure actuals are the primary exhibits supporting DCAA inquiries. System-generated reports carry higher credibility than Excel-compiled summaries

Phase 4: Negotiation - ACO Negotiation and Rate Settlement

• The ACO (supported by DCAA audit findings) negotiates each rate with the contractor's pricing and contracts team; PCO/ACO has authority to accept, modify, or reject proposed rates
• Contractor may provide supplemental analysis, revised forecasts, or sensitivity models to support its proposed rates. This is a primary use case for PaPM or SAC Planning (formerly BPC) scenario modeling
• If parties agree, an FPRA is executed as a bilateral agreement; if not, DCAA issues an FPRR and the ACO proceeds unilaterally for pricing purposes
• Negotiated rates are documented by rate type, base, period, and any special conditions (e.g., ceilings, escalation adjustments)

Phase 5: SAP Implementation - Loading Agreed Rates into SAP Costing Sheets

• Once FPRA is executed, negotiated rates for each pool are entered into SAP overhead rate configuration (KZS2 / costing sheet overhead rates), effective-dated to the start of the rate period
• Costing sheet assignment is verified on all relevant order types, WBS element profiles, and cost estimate variants to ensure rates flow to the correct cost objects
• New standard cost estimates are released (CK11N / CK24) incorporating the new FPRA rates, updating inventory valuation and the cost baseline for all active programs
• Overhead cost center budgets (KP06) are updated to reflect expected absorption at the new rates, enabling over/under-absorption monitoring throughout the year

Phase 6: In-Year Monitoring - Rate Monitoring, Amendment, and Over/Under-Absorption Tracking

• Monthly: compare actual indirect pool spend against absorbed overhead (posted via costing sheets) to compute cumulative over/under-absorption by pool, a critical metric for billing rate sufficiency
• If actual costs are tracking materially above or below FPRA rates, contractor may initiate an FPRA amendment, resubmitting a revised proposal for the remaining rate period
• Over-absorbed overhead (rates too high vs. actual pool) creates a liability to the government on cost-type contracts; under-absorbed (rates too low) indicates unrecovered costs. Both have contract financial implications
• SAP touchpoint: Cost center variance reports, plan/actual comparisons (S_ALR_87013611), and activity price variance reports are the primary monitoring tools; PaPM or SAC Planning (formerly BPC) can provide forward-looking absorption forecasts

Phase 7: Final Settlement - Final Indirect Rate Audit and Rate Closure

• After fiscal year-end, contractor submits final indirect cost rate proposal per FAR 42.705 (Incurred Cost Submission / ICS), typically within 6 months of fiscal year close
• DCAA audits the ICS against actual costs in SAP; establishes final rates for the year which supersede FPRA rates for billing and contract settlement purposes
• Differences between FPRA (billing) rates and final audit rates result in upward or downward contract billing adjustments across all affected cost-reimbursable contracts
• Final rates close the FPRA period and become the historical actuals that anchor the next FPRP cycle, completing the loop back to Phase 1

Where SAP Supports vs. Gaps in the FPRP Process

FPRP Stage	What SAP Natively Provides	Gap / External Requirement
Rate Development	Historical actuals from ACDOCA, cost center reports, SKF actuals as base data	Projection modeling, pool/base forecasting, and sensitivity analysis requires SAC Planning (formerly BPC), IBP, PaPM, or Excel (Gap)
DCAA Audit Support	System-generated cost element reports (KSB1), cost center actuals (KSB2), activity price reports, which carry high credibility with DCAA	Narrative rate justification, management assertions, and cost allowability analysis are manual and outside SAP (Partial)
Rate Loading	Overhead rate configuration in costing sheets (KZS2); effective-dated rate changes; automatic recalculation on orders	None. This is a core SAP strength (Native)
In-Year Monitoring	Plan/actual variance reports, cost center over/under-absorption via KO8G / period-end reporting	Forward-looking absorption forecast (rest-of-year) requires planning tool integration (Partial)
FPRA Amendment	Rate update in costing sheet config; re-release of cost estimates with new rates; retroactive overhead recalculation	Mid-year rate renegotiation modeling and impact analysis on open contracts is outside SAP (Partial)
Final Rate Settlement (ICS)	Actual cost extraction for ICS preparation; cost element actuals by pool and base are available natively	ICS report formatting and billing adjustment processing requires contractor-specific development or GovCon add-on (Gap)

PaPM's Role in the FPRP Lifecycle: PaPM is most directly valuable in Phases 1, 2, and 4, where rate projection modeling, scenario sensitivity analysis, and negotiation support data are needed. Its ability to simulate pool/base interactions, model headcount or volume changes, and compare rate scenarios makes it a credible upgrade over Excel for contractors with complex, multi-segment rate structures. However, it does not replace the DCAA audit interface, the FAR/CAS compliance framework, or the costing sheet mechanism that applies agreed rates in production.

Why Major A&D Companies Are Not Widely Using PaPM

Candid Industry Assessment: PaPM adoption among large A&D primes remains limited. Understanding why is as strategically important as understanding the product's capabilities. These are not reasons to dismiss PaPM, but they are the real objections your peers have raised and the barriers that must be addressed for a successful implementation.

• Significant existing CO investment is "good enough": Most large A&D primes spent decades and hundreds of millions configuring SAP R/3 and ECC CO to support DCAA-auditable indirect rate structures. Migrating that logic to PaPM models carries reaudit risk and business disruption that is hard to justify without a compelling capability gap.
• CAS compliance requires proven tooling: Government contractors operating under CAS 401 through 420 need demonstrable, auditable, consistent cost accounting practices. Introducing a new calculation engine that DCAA auditors are unfamiliar with creates audit friction and disclosure statement amendment requirements, a significant deterrent.
• Niche talent pool: Qualified PaPM architects who also understand government contracting cost structures are extremely rare. Most SAP A&D SI partners have limited PaPM bench strength, raising delivery risk for complex implementations.
• Product maturity and awareness: PaPM (formerly HANA Profitability and Cost Management / PCM) has been through multiple rebrands and capability shifts. Many A&D CIOs and CFOs are not aware of the current product's capabilities or differentiation from legacy CO tooling.
• Competing investments: Major A&D primes are currently prioritizing S/4HANA migration, cloud transition (RISE), and cybersecurity (CMMC) investments. PaPM is not seen as a migration prerequisite and therefore deprioritized in capital planning cycles.
• Shadow Excel models are entrenched: Finance and program control teams have built sophisticated Excel-based indirect rate models and allocation simulators over many years. These are politically difficult to displace even when inferior, because they are owned by the people doing the analysis.
• Insufficient A&D-specific content from SAP: SAP has not invested heavily in pre-built A&D PaPM content libraries, GovCon templates, or DCAA audit trail accelerators. Without this, implementation requires full custom design, increasing cost and risk.
• SAC Planning (formerly BPC) / IBP incumbency: Companies that have invested in SAC Planning or IBP for planning and rate scenario modeling often see PaPM as redundant, or at minimum, struggle to articulate a clear boundary between the tools in a joint architecture.

Where PaPM Is Gaining Traction

• Commercial Aerospace: Airlines and MRO providers with complex shared service cost structures and margin-by-route or margin-by-tail analysis needs are earlier PaPM adopters than defense primes.
• Greenfield RISE Deployments: Companies starting fresh on RISE with SAP have no legacy CO investment to protect and are more open to adopting PaPM's cloud-native architecture from the outset.
• Finance Transformation Programs: A&D companies undertaking broad finance transformation (zero-based budgeting, cost transparency initiatives) sometimes include PaPM as the allocation transparency engine within a larger program.