In this blog we identify the most important SAP Project System (PS) tables for users of:
PS data covers project definitions, WBS elements, networks and activities, milestones, budgets and actual cost postings, plus object status. It is critical for project cost, earned value, milestone tracking, budget-vs-actual and capital-project portfolio analytics. SAP Project System tables are found in the following SAP systems:
PS reuses the Order Master (AUFK) and the order tables (AFKO, AFVC, AFVV, AFRU, RESB) shared with PP for network activities, and integrates with CO through COEP for actual cost postings. The underlying data model is broadly consistent between SAP ECC and SAP S/4HANA. SAP Project System (PS) Project Structure TablesProject structure tables define the skeleton of every SAP project: the project definition at the top, the Work Breakdown Structure (WBS) elements beneath it, the hierarchy that links them and the scheduled dates and milestones attached to each element. These are the dimension tables for most project reporting. PROJ - Project Definition. Contains one row per project with the internal project number (PSPNR) as the key. Key fields include the external project ID (PSPID), project description (POST1), responsible person (VERNR), plant (WERKS) and location (STORT). This is your starting point for any project-level reporting. PRPS - WBS Element Master Data. Contains one row per WBS element, keyed on PSPNR. Key fields include the external WBS ID (POSID), description (POST1), parent project number (PSPHI), hierarchy level (STUFE) and object number (OBJNR). OBJNR is the join key you will use to connect WBS elements to budget, cost and status tables. PRHI - Project Hierarchy. Contains the parent-child relationships between WBS elements, keyed on PSPNR and POSNR. Key fields include the upper (parent) WBS element (PRUPS), previous sibling (PRIVL) and next sibling (PRNEX). Use this table to reconstruct the project tree for hierarchical reporting and roll-ups. PRTE - WBS Element Scheduling. Contains the calculated and planned dates for each WBS element, keyed on PSPNR. Key fields include basic start date (PSTER), basic finish date (PEDTE) and scheduling state (STATE). Essential for planned-vs-actual schedule analysis. MLST - Milestone. Contains one row per milestone, keyed on the milestone number (MLNR). Key fields include the WBS element (PSPNR), activity number (VORNR), item number (POSNR), milestone description (MLSTN) and trend analysis number (BEDNR). Use MLST for milestone trend analysis and project progress reporting. SAP Project System (PS) Network TablesA PS Network is technically an order in SAP, so network header and operation data reuses the same tables as PP production orders. If you already report on production orders you will recognise most of the tables in this section. AUFK - Order Master Data. The network header is stored as an order, so it lives in the shared Order Master table keyed on order number (AUFNR). Contains order type, plant, responsible cost centre and system status fields. Join AUFK to AFKO to get the full network header. AFKO - Network Order Header. Contains order-header specific fields such as the scheduling and release data, keyed on AUFNR. Join to AUFK on AUFNR for a complete network-header dataset. AFVC - Network Activity (Operation). Contains one row per activity within a network, keyed on routing number (AUFPL) and counter (APLZL). Key fields include activity number (VORNR), assigned WBS element (PROJN) and work centre (ARBID). This is where you find the activity-level project structure. AFVV - Activity Quantities, Dates and Values. Contains the planned quantities, dates and values for each activity, keyed on AUFPL and APLZL. Key fields include work quantity (MGVRG), early start date (FSAVD) and early finish date (FSEDD). Join to AFVC on AUFPL and APLZL to attach scheduling and quantity data to each activity. AFRU - Activity Confirmations. Contains one row per confirmation posted against a network activity, keyed on confirmation number (RUECK) and counter (RMZHL). Essential for actual hours, actual quantities and progress reporting. RESB - Network Reservations and Components. Contains the material components reserved against each network activity, keyed on reservation number (RSNUM) and item (RSPOS). Use RESB for material commitment, component consumption and procurement analysis on project networks. SAP Project System (PS) Budget and Cost TablesBudget and cost tables are where project financials live. Budgets are held in dedicated PS budget tables, while actual cost postings flow through the shared CO document tables with the WBS or network as the object. BPJA - Budget Annual Values. Contains the annual budget distribution per object, keyed on object number (OBJNR), fiscal year (GJAHR), value type (WRTTP) and version (VERSN). Key fields include the twelve monthly budget amounts (BTR01 through BTR12) and the yearly total (WTJHR). Use BPJA for budget-vs-actual reporting by period. BPEG - Budget Line Items. Contains the individual budget postings that make up the annual totals, keyed on ledger (LEDNR), object number (OBJNR) and fiscal year (GJAHR). Useful for tracing how a project budget was built up and adjusted over time. COEP - CO Document Line Items (Actual Postings). This is the shared CO line-item table where every actual cost posting lands, keyed on controlling area (KOKRS), document number (BELNR) and line item (BUZEI). The OBJNR field identifies the receiving object, which can be a WBS element or a network. Filter by OBJNR to extract project-level actual costs. COSP - CO Cost Totals for External Postings. Contains aggregated cost balances per object and cost element, keyed on object number (OBJNR), fiscal year (GJAHR), value type (WRTTP) and version (VERSN). Use COSP when you need a fast period-balance view rather than line-item detail. SAP Project System (PS) Object Status TablesAll SAP orders, WBS elements and networks use the common JEST, JCDS, TJ02 and TJ30 status framework with OBJNR as the key. Understanding this framework lets you filter and decode status values consistently across PS, PP, PM and CO. JEST - Individual Object Status. Contains one row per status value per object, keyed on object number (OBJNR) and status (STAT). Key fields include the inactive flag (INACT) and change number (CHGNR). Filter on INACT = blank to get only active statuses. JCDS - Status Change Documents. Contains the audit trail of status changes, keyed on OBJNR, STAT and change number (CHGNR). Use JCDS to analyse how long objects spent in each status and when transitions occurred. TJ02 / TJ02T - System Status Codes and Texts. TJ02 contains the system status codes keyed on ISTAT, and TJ02T contains the language-dependent descriptions keyed on ISTAT and language (SPRAS). Join to JEST on STAT = ISTAT to decode system statuses into readable labels. TJ30 - User Status. Contains the user-defined statuses configured in each status profile, keyed on status profile (STSMA) and user status (ESTAT). Join to JEST on STAT to decode user statuses alongside system statuses. SAP Project System (PS) Configuration TablesConfiguration tables (also known as customising tables) contain the settings and descriptions that define how your SAP PS module behaves. These are small, slowly changing tables that are useful for decoding values stored in the transaction tables. The configuration tables listed below apply to both SAP ECC and SAP S/4HANA. T001W - Plants. Contains the list of plants configured in your system, keyed on plant (WERKS). Join to PROJ on WERKS to add plant descriptions to project-level reports. TCJ41 - Project Profile. Contains the project profile definitions, keyed on profile (PROFL). The project profile drives defaults such as responsible cost centre, budget profile and planning profile. Join to PROJ to decode project profiles. TCJ3 - Network Profile. Contains the network profile definitions, keyed on profile (NETPR). The network profile drives defaults for network scheduling, costing and number ranges. Join to AFKO to decode network profiles. Explore SAP PS Tables with a DVW ConnectorThe fastest way to explore SAP PS tables is to connect directly to your SAP system from your preferred analytics platform. DVW Connectors let you browse available tables, preview fields and extract data without writing any ABAP code. All DVW products support both SAP ECC and SAP S/4HANA. To see how all 22 tables in this blog connect to each other, visit our SAP PS Table Relationships page for an interactive data model diagram with join keys and ECC vs S/4HANA compatibility. All DVW products include a 30-day free trial with full functionality, so you can start working with these tables right away. Visit our Free Trial page to get started, or explore our Help Centre for detailed documentation on connecting to SAP PS tables. Next StepsSee these SAP PS tables in action. Register for a 30-day free trial and start extracting project, network activity and budget data from your SAP system today. Comments are closed.
|
Categories
All
Archives
May 2026
|
RSS Feed