BPGE table — PS Cost Planning: Total Values per Cost Element

Each record in BPGE represents the total planned amount for one cost element on one object (a WBS element or network activity, identified by object number) within one cost planning document, for one plan version and one value type, summed across the entire planning horizon of that document. It is the aggregate counterpart to BPJA (which splits the same total by fiscal year) and BPPE (which splits it further by period). BPGE does not itself carry any time dimension: if the total in BPGE does not match the sum of the corresponding rows in BPJA, the planning document is internally inconsistent, which normally only happens after a failed mass change, an aborted BAPI call, or a direct table manipulation outside the standard planning transactions.

Always restrict by MANDT, PLNUM and POSNR before pulling from BPGE; the table can hold a large number of rows once a project has been re-planned repeatedly across versions and value types, and an unrestricted select by cost element alone returns rows from unrelated projects. VERSN is easy to forget and produces silent mismatches: a plan value looks missing when it is simply sitting under a different version than the one the report is filtering on. WRTTP is the field that separates genuine plan values from commitment-style rows, so a query that ignores it can double count.

A planner reports that a cost planning document total shown in the project report does not match what was entered on screen. Select BPGE by PLNUM, restrict to the relevant POSNR and VERSN, and sum WKGBTR across KSTAR and WRTTP. Compare that figure against the same restriction on BPJA summed across all fiscal years. If the BPGE total and the BPJA sum disagree, the document is internally broken and needs regeneration through the planning transaction rather than a manual correction.

BPGE continues to exist on S/4HANA as the underlying total-values table for PS cost planning documents; it has not been replaced by a CDS-based compatibility view in the way several CO totals tables have. Cost planning content is increasingly surfaced through Fiori-based project cost planning apps and CDS views for reporting, but those read the same planning tables underneath rather than a redesigned data model, so the table structure and its relationship to BPJA and BPPE are unchanged for practical diagnostic purposes.

A mismatch between BPGE and the reported plan total is a Project System functional consultant question first, since it usually traces back to how the cost planning document was created, versioned or mass-changed. It becomes a technical question only when a custom program or interface has written to the planning tables directly, at which point the developer who built that interface owns the fix.

BPGE sits with BPBK (planning document header), BPJA (annual values) and BPPE (period values) as the four-table core of PS cost element planning, all maintained through the cost planning transactions in the WBS element and Easy Cost Planning environment. On the master data side it depends on PRPS for the WBS element and PROJ for the project definition, and on the reporting side its totals are compared against actual cost tables such as COSPD when checking plan against actual.