Translating PS, internal orders, and CO-PA into project management and accounting

How SAP Project System (project definitions, WBS elements, networks, settlement rules, results analysis) and the CO controlling landscape (internal orders, CO-PA) map onto D365 Project management and accounting, project types, WIP calculation, revenue recognition, and the Project Operations decision.

What you will be able to do

Introduction

SAP's project accounting estate spans three intersecting modules. Project System (PS) provides the object hierarchy: project definitions, WBS elements, networks, and activities that accumulate costs and drive billing.

SAP PS: the project object model

SAP PS organises project data in a four-level hierarchy stored across three primary tables.

Internal orders, CO-PA, and the controlling landscape

Internal orders (AUFK, order category 01) are lightweight cost collectors. They accumulate actual costs and commitments and are settled periodically. SAP organisations use them for a wide range of purposes:

D365 Project management and accounting

D365 PMA organises project accounting around the project group — a configuration object that governs accounting behaviour for all projects assigned to it. The project group carries:

The Project Operations decision

D365 Project Operations is a separate application built on Dataverse and Microsoft Power Platform. It extends PMA with:

Settlement, WIP, and revenue recognition

Period-end project accounting in SAP consists of three transactions: results analysis (KKA3 or CJ44), settlement (CJ88), and goods receipt/invoice processing for project-purchased materials.

Knowledge check

Summary

SAP's project accounting estate — PS hierarchy, CO settlement, and CO-PA — maps to D365 PMA with the following principal translations: