📁 What is SAP Project Systems (PS)?
In SAP Project Systems (PS) is an integrated module within SAP ECC 6.0 / S/4HANA that Supports organisations to plan, execute, monitor, and close projects of any size and problem. PS integrates Consolidates with FI, CO, MM, SD, HR, and PP modules and is widely used in industries such as engineering, construction, oil & gas, IT services, and manufacturing. A solid understanding of PS is highly valued in SAP consulting roles.This tutorial or document breaks down the process step by step, using simple language and real-world examples to help you master the skill.
Cost And Budget Management
Plan and control project costs, budgets, and commitments using WBS elements and availability control.
Scheduling And Resources
Model project timelines using Networks, activities, milestones, and CPM scheduling with resource assignments.
Full Module Integration
PS integrates with FI, CO, MM, SD, PM, and HR - making it one of the most cross-functional SAP modules.
Interview Tip: Interviewers often test whether candidates understand the difference between WBS (cost/budget structure) and Networks (scheduling/resource structure). Always be ready to explain how they complement each other within one project.
🟢 Basic SAP PS Interview Questions
These questions cover the fundamental concepts and objects of SAP PS.They are mostly asked in entry-level and junior consultant interviews. A strong grip of these topics show your foundational knowledge of this module.
SAP PS is an integrated SAP module used to plan, execute, monitor, and close projects. It provides tools for cost planning, budgeting, scheduling, resource management, and revenue recognition. PS is tightly integrated with FI, CO, MM, SD, HR, and PP, making it ideal for project-centric industries like construction, engineering, oil & gas, and IT services.
The Project Definition is the top-level object in SAP PS. It holds general data for the entire project including the project number, responsible person, project profile, planned/actual dates, and controlling/company code assignments. All WBS elements, networks, and milestones sit beneath the Project Definition in the hierarchy.
A WBS is a hierarchical decomposition of a project into manageable deliverables. Each node is called a WBS element. In SAP PS, WBS elements are used for cost planning, budgeting, and settlement. They carry a unique WBS element code (stored in table PRPS) and can be assigned to cost centres or profitability segments for settlement purposes.
WBS elements define the cost and budget structure of a project they answer "what needs to be done" and "how much will it cost." Network activities define the scheduling and resource structure - they answer "when and how" tasks are performed, with dependencies, durations, and resource assignments.
- WBS is used for cost planning, budgeting, and settlement
- Networks are used for time scheduling, resource planning, and CPM
- Network activity costs roll up into the WBS cost structure
SAP PS uses system statuses that are assigned automatically based on business transactions:
CRTD- CreatedREL- Released (allows posting of costs)TECO- Technically CompletedCLSD- Closed (no further postings allowed)DLFL- Deletion Flag
In addition, user statuses can be configured via status profiles to enforce custom business rules and approval workflows.
A Project Profile is a configuration object that pre-populates default settings when creating a new project. It defines the plant, controlling area, costing variant, results analysis key, network type, planning board profile, and budget profile. Using project profiles ensures consistency and reduces manual setup errors across multiple projects of the same type.
A Milestone is a key event or checkpoint in a project timeline. It has a specific date but zero duration. In SAP PS, milestones are attached to network activities or WBS elements and can be used to:
- Trigger milestone billing in SD (billing plan)
- Release subsequent activities
- Trigger status changes or workflow notifications
- Measure project progress in Earned Value Management
Internal activities are performed by internal work centres. They are costed using activity types and rates from CO. When time is confirmed against them, actual costs post to the network order using the activity rate.
External activities are assigned to vendors and automatically generate purchase requisitions or purchase orders through MM integration. This allows PS to manage both internal labour and outsourced work within the same network structure.
🔵 Intermediate SAP PS Interview Questions
These questions are suited for candidates with 2–4 years of SAP PS experience. They cover important functional areas like budgeting, settlement, integrations, and period-end activities that are central to day-to-day PS consulting work.
Cost Planning is the detailed estimate of expected project costs, entered at WBS element level by cost element. It can have multiple versions and is used for internal analysis.
Budget is the formally approved spending limit. It is managed via transactions CJ30 (original budget) and CJ36 (budget releases). Only the released budget is checked by Availability Control (AVAC). You cannot control actual spending against a cost plan - only against a released budget.
Availability Control (AVAC) checks actual costs plus open commitments against the released budget on a WBS element in real time. It is activated via the budget profile assigned to the project profile. AVAC can be configured to:
- Issue a warning when a threshold (e.g. 85%) is reached
- Raise an error that blocks postings when the budget is fully consumed
- Send workflow notifications to the project manager
AVAC only works on released budget amounts - unreleased budget is not considered in the check.
Settlement transfers actual costs from WBS elements or network orders to receivers such as cost centres, G/L accounts, profitability segments (CO-PA), or assets under construction (AuC). It is a critical period-end activity in SAP PS.
- Settlement is configured using a settlement profile and settlement rule on the WBS element
- Transaction
CJ88runs project settlement - For capital projects, costs settle to AuC (Asset Under Construction) and eventually to a final fixed asset
- Settlement can be full or proportional (percentage-based)
Project stock is material that is reserved and valuated specifically for a project WBS element or network activity. It is managed as special stock type Q and is physically and financially segregated from general plant stock. This ensures that materials procured for a specific project can only be consumed against that project, improving project cost accuracy and preventing cross-project material usage.
SAP PS integrates with SD in the following ways:
- Sales orders reference WBS elements as the account assignment object, enabling revenue recognition at project level
- Milestone billing in SD is controlled by project milestones in PS - once a milestone is confirmed, the billing block is released
- Project revenues flow into Results Analysis (RA) for POC-based revenue recognition
- SD billing documents post revenue to the WBS element for matching against project costs
Results Analysis (RA) calculates the revenue to be recognised for ongoing projects based on the cost-to-complete method (POC - Percentage of Completion). It compares planned revenue and actual costs to determine how much revenue should be recognised in the current period, and posts RA data to CO-PA and FI. RA is required for project-based revenue recognition under IFRS 15 and similar accounting standards. It runs as a period-end activity via transaction KKA2 or CJ88.
The Project Information System is the standard reporting environment in SAP PS. It provides hierarchical and list-based reports for monitoring project costs, revenues, budgets, and progress. Key standard transactions include:
CN41- Cost Element Report for WBSCN42- Hierarchical Cost ReportCJ31- Budget Status ReportCN60- Project Progress Report
The Project IS uses SAP Logical Databases to extract data efficiently from PS tables like PRPS, PROJ, and CO tables.
Overhead is calculated in PS using costing sheets assigned to the costing variant of the WBS or network. The costing sheet defines:
- Base - which cost elements trigger the overhead (e.g. labour costs)
- Overhead rate - the percentage or amount to apply
- Credit object - the cost centre that is credited
Transaction CJ44 applies overhead to WBS elements as a period-end activity. The result is an actual overhead cost posting on the project.
🔴 Top 50 Advanced SAP PS Interview Questions
These 50 questions are designed for senior consultants, solution architects, and lead PS professionals with 5+ years of experience. Each answer includes a short real-world example to help you explain clearly in interviews.
Interview Strategy: For this Topic advanced questions, always structure your answer as: Definition → How it works → Real examples. This three-part pattern shows both knowledge and practical experience.
EVM measures project health by comparing PV (Planned Value), EV (Earned Value), and AC (Actual Cost). Key formulas: CPI = EV ÷ AC (cost efficiency), SPI = EV ÷ PV (schedule efficiency). CPI below 1.0 means over budget; SPI below 1.0 means behind schedule.
Example: Project budget = ₹10L, 50% complete on schedule (PV=5L), actual costs = ₹6L, but only 40% done (EV=4L). CPI = 4/6 = 0.67 (over budget). SPI = 4/5 = 0.80 (behind schedule). Use CN60 to view EVM data in PS.
TECO (Technically Complete) stops new commitments but still allows financial postings - settlements, invoices, RA runs. CLSD (Closed) blocks ALL postings. You set TECO when physical work is done, and CLSD only after all invoices, settlements, and RA are cleared.
Example: A construction project completes site work in March → set TECO. Final vendor invoice arrives in April → posted successfully. Settlement and RA run in April period-end. No open items remain → set CLSD in May.
WBS elements with an investment profile are linked to an AuC (Asset Under Construction). During the project, costs settle periodically from WBS → AuC. On project completion, AuC is capitalised to a final asset using AIAB (distribution rules) and AIBU (capitalisation).
Example: A ₹50L factory building project runs for 12 months. Each month CJ88 settles WBS costs to AuC. On TECO, the ₹50L AuC balance is capitalised as a Building asset (Class 1000) and depreciation starts from the following month.
RA calculates revenue to recognise for ongoing projects per IFRS 15 / POC method. Common RA methods: 01 – Revenue-based POC, 03 – Cost-based POC (most common), 06 – Completed contract. Run via KKA2. Posts RA data to FI and CO-PA.
Example: IT services project: planned revenue ₹20L, planned cost ₹16L. By month 3, actual cost = ₹8L (50% POC). RA method 03 recognises ₹10L revenue (50% of ₹20L) and posts a revenue surplus of ₹2L to CO-PA.
AVAC checks actual + commitments vs released budget in real time. Configured in the budget profile (T-code OPS9): set usage % thresholds and assign action - 1=Warning, 2=Warning + mail, 3=Error (hard stop). Activated automatically on budget release.
Example: Budget profile has 85% → Warning and 100% → Error. WBS budget = ₹10L released. When actuals + POs reach ₹8.5L, PM gets a warning mail. At ₹10L, any new PO creation in ME21N gets a hard error - posting blocked.
In plan-independent mode, WBS plan and network activity costs are maintained separately - no automatic link. In plan-dependent mode, network activity costs automatically populate a WBS cost plan version, keeping schedule and budget always in sync.
Example: Plan-dependent setup: Engineer confirms 40 hours on Activity A010 at ₹500/hr. The WBS plan for WBS.1.1 auto-updates with ₹20,000. Any rescheduling of the activity also revises the WBS cost plan - no manual correction needed.
A simulation version is a copy of the operative project used for what-if analysis. Created in CJ20N via Edit → Copy to Simulation. You can change dates, quantities, and costs without affecting the live project. Compare simulation vs operative using the Project IS reports.
Example: Client requests 2-month extension. Create simulation version SIM-01, shift all network activities by 8 weeks. Compare costs - delay adds ₹3L in overhead. Present simulation report to client before approving the formal change order.
Project stock (type Q) is material valuated and reserved against a specific WBS element or network activity. It is segregated from plant stock. GI from project stock uses movement type 221 Q, which debits cost to the WBS element directly.
Example: PO created for 100 steel pipes assigned to WBS.2.3. GR posts 100 pipes to project stock (Q stock). During construction, GI with mvt 221 Q transfers 30 pipes to project - WBS.2.3 gets debited ₹45,000 (30 × ₹1,500). Remaining 70 pipes stay in Q stock.
Sales order billing plan lines have billing blocks. PS milestones are linked to these billing plan lines. When the PS milestone is confirmed (usage decision made), the billing block is automatically removed, allowing SD to create the billing document via VF04.
Example: Contract: 30% on design completion, 70% on delivery. SO has two billing plan lines. Milestone MS-10 (Design Complete) confirmed in PS → ₹3L billing block removed → SD creates invoice for ₹3L. MS-20 (Delivery) triggers the ₹7L final invoice.
The settlement rule defines where costs settle - receiver type (CTR, AUC, G/L, PA), receiver number, settlement type (FUL/PER), and percentage. Configured in CJ20N under WBS element → Settlement Rule tab. The settlement profile (from Project Profile) controls which receivers are allowed.
Example: WBS.3.1 settlement rule: 60% → Cost Centre CC-1001, 40% → Profitability Segment (PA) for customer ABC. Running CJ88 in March distributes ₹10L actual cost as ₹6L to CC-1001 and ₹4L to PA.
CPM is automatic in SAP PS networks. After scheduling (forward/backward pass), the system calculates float (slack) for each activity. Activities with zero float form the critical path - any delay directly delays the project end date. View via Gantt chart in CJ20N or CN21.
Example: Network has activities A→B→C (10+15+5 days) and A→D→C (10+8+5 days). Path A-B-C = 30 days is critical (zero float). Path A-D-C = 23 days has 7-day float. If activity B delays by 3 days, project end shifts by 3 days.
SAP PS supports 4 relationship types: FS (Finish-Start - most common), SS (Start-Start), FF (Finish-Finish), SF (Start-Finish - rare). Each can have a lag (positive delay) or lead (negative overlap) in days.
Example: Activity "Lay Foundation" FS+2d → "Pour Concrete" means concrete pouring starts 2 days after foundation is finished (curing time). SS relationship: "Excavation" SS+5d → "Drainage" means drainage can start 5 days after excavation begins.
A costing sheet defines: Base (cost element group that triggers overhead), Overhead Rate (%), Credit (cost centre credited). Assigned to the costing variant in the project profile. Overhead is applied via CJ44 each period.
Example: Costing sheet: Base = Labour cost elements (43xxxxx), Rate = 25%. WBS accrues ₹8L labour in April. Running CJ44 posts ₹2L overhead to WBS and credits Cost Centre ADMIN-01 with ₹2L. Total project cost = ₹10L.
The budget profile (configured in OPS9) controls: time frame for budgeting (years), whether overall/annual budget is used, currency, availability control activation, tolerance limits, and whether budget is carried forward annually. Assigned to the project profile.
Example: Budget profile BP01: Overall budget enabled, AVAC active, tolerance 1=85% warning, 2=100% error, currency=INR, annual budget NOT active. This means the total project budget is checked, not individual fiscal year slices.
The investment profile is assigned to a WBS element to enable automatic creation of an AuC (Asset Under Construction) when the WBS is saved. It controls the AuC asset class and whether the AuC is created per WBS or per project. Used for all capital expenditure projects.
Example: WBS element "Plant Expansion – Civil" gets investment profile IP-CAPEX. On saving, AuC 100045 (asset class 4100 – AuC Buildings) is auto-created. All costs on this WBS settle to AuC 100045 until capitalisation.
When a network is released, SAP creates a network order (internal order type PR10) in CO. Costs post to the network order first. Settlement of the network order transfers costs to the assigned WBS element. Cost flow: Activity Confirmation → Network Order → WBS → Final receiver (CC / AuC / PA).
Example: Engineer confirms 8 hours on Activity 0010. CO posts ₹4,000 (8h × ₹500/h) to Network Order 700001. Period-end settlement moves ₹4,000 from Network Order 700001 to WBS element WBS.1.2. WBS settlement then moves it to AuC.
A standard WBS (also called a model project) is a reusable project structure template. It stores a pre-defined hierarchy of WBS elements, networks, and cost plans. New projects are created by copying the template via CJ01 → Copy from. This ensures consistency and saves setup time.
Example: A telecom company runs 50 tower installation projects per year. A standard WBS "TOWER-STD" has 12 WBS elements and a 45-activity network. Each new project is copied from this template - saving 3 hours of setup per project = 150 hours/year saved.
A service activity (activity category 2) procures services via a service entry sheet (MM-SRV) - used for unplanned or variable-quantity services. An external activity (category 1) procures a defined scope via a standard PO. Service entries allow flexible quantity and value booking.
Example: External activity: PO for "Supply and Install 50 Solar Panels" - fixed scope. Service activity: "Security Guard Services" - monthly variable hours. The security service is entered via ML81N (service entry sheet) each month with actual hours.
Inter-company PS projects involve two company codes - a billing company (provides services) and a receiving company (owns the project WBS). Costs are transferred via inter-company billing using SD billing documents. Configuration requires inter-company billing settings in SD and CO reconciliation ledger postings.
Example: Company A (Engineering) performs design work for a project owned by Company B (Construction). Activity costs post to Company A. An inter-company SD invoice is raised from A to B. Company B WBS gets debited, and inter-company revenue posts in Company A - creating a clean P&L split.
PS integrates with Cash Management via payment items derived from project-related documents (POs, billing documents). Cash outflows come from project POs; cash inflows from milestone billing invoices. Enables cash planning at WBS level in CJI3 cash flow report.
Example: Project has ₹30L in open POs (outflows) and ₹15L in outstanding customer invoices (inflows). Cash Management shows net outflow of ₹15L. Treasury uses this to ensure adequate liquidity is maintained for the project's current month obligations.
Overall budget is the total approved spend for the full project life. Annual budget is a year-wise slice. AVAC can check either or both. If annual budget is active, spending in each fiscal year is checked independently against that year's released amount.
Example: 3-year project with overall budget ₹3Cr. Annual budget: FY2024=₹80L, FY2025=₹1.4Cr, FY2026=₹80L. In FY2024, if actuals reach ₹80L, AVAC blocks further postings - even though ₹2.2Cr overall remains unused. Annual slice protects against front-loading costs.
RRB allows billing based on actual resources consumed on a project (time, materials, expenses). The dynamic item processor (DIP profile) reads actual costs from WBS/network, maps them to SD condition types, and creates a debit memo request. Billing document is created from the debit memo in VF04.
Example: Time & Material contract: Consultant works 100 hours in March. DIP profile reads confirmed hours from network activity, applies rate ₹2,000/hr = ₹2L. A debit memo request DMR-1001 is created. VF04 processes it into invoice INV-5678 sent to the customer.
The DIP profile controls how actual costs from PS objects are transformed into SD billing items. It defines cost element groups (sources), SD material numbers (targets), and quantity/value determination rules. Configured in ODP1 and assigned to the WBS element or sales order.
Example: DIP profile CONS-01: Source group "Labour costs" (cost elements 430000–439999) maps to Material "CONS-LABOUR" in SD. Source "Expenses" maps to Material "CONS-EXPENSE". Each source gets its own billing rate - labour at ₹2,000/hr, expenses at cost + 15%.
Forward scheduling starts from the project start date and calculates the earliest finish. Backward scheduling starts from the required end date and calculates the latest start. SAP PS uses backward scheduling by default to ensure deadline compliance. Scheduled via CJ29 or automatically in CJ20N.
Example: Project deadline 31-Dec. Backward pass calculates Activity "Commissioning" must start by 15-Dec (5 days duration). "Testing" must finish by 14-Dec, so start by 01-Dec (14 days). This gives the PM clear latest start dates for each activity to meet the deadline.
Commitments are obligations against the budget not yet invoiced. Types: Purchase Requisition commitment (PR created), Purchase Order commitment (PO created - replaces PR commitment), Funds commitment (manual reservation). AVAC checks actuals + all commitments vs released budget.
Example: Budget ₹10L released. Actuals = ₹4L. Open PO = ₹5L. AVAC checks ₹4L+₹5L = ₹9L vs ₹10L = 90% - triggers warning. If a new PR of ₹1.5L is raised, AVAC checks ₹4+5+1.5=₹10.5L → exceeds budget → error blocks the PR.
Cost elements are CO objects mirroring FI G/L accounts. Primary cost elements (type 01) map to expense G/Ls (materials, salaries). Secondary cost elements (type 21/42/43) are used for internal allocations, settlements, and overhead. All PS cost postings are categorised by cost element.
Example: WBS cost element report (CN41) shows: Material (430000) = ₹5L, Labour (420000) = ₹3L, Overhead (secondary 940000) = ₹2L, Total = ₹10L. Drilling down by cost element shows exactly where budget is being spent - enabling targeted cost control.
A work centre (created via IR01) represents a resource - a person, team, machine, or plant section. It is assigned to internal network activities and contains the activity type (for costing), capacity, and scheduling parameters. Cost = Work quantity × Activity type rate from CO.
Example: Work centre WC-ENG (Engineering Team) assigned activity type AT-ENG at ₹800/hr. Activity 0020 "Detailed Design" has WC-ENG assigned, planned 200 hrs. Planned cost = 200 × ₹800 = ₹1.6L. Actual cost posts when hours are confirmed in CNF1.
Capacity planning in PS checks work centre availability against network activity requirements. Capacity requirements are generated when a network activity is saved with a work centre. View overloads in CM01 (capacity planning table) or CN48 (PS capacity report). Levelling can be done manually or semi-automatically.
Example: WC-CIVIL has capacity 8 hrs/day. In Week 12, three projects each assign 6 hours to WC-CIVIL = 18 hrs required vs 8 hrs available = 10 hrs overload. CM01 highlights this. PM reschedules one project's activity by 1 week to resolve the overload.
Progress analysis in PS calculates the degree of completion (POC) for EVM. Measurement methods: Milestones (POC based on confirmed milestones), Estimated (manual % entry), Duration (time elapsed / total duration), Quantities (work confirmed / planned). Configured per WBS/activity via measurement method in the project profile.
Example: WBS.2.1 uses milestone method. 3 milestones defined: M1=20%, M2=60%, M3=100%. M1 and M2 confirmed → POC = 60%. System uses 60% to calculate EV = 60% × planned cost for EVM reporting in CN60.
SAP PS allows multiple cost plan versions (version 0 = operative, versions 1–99 = additional). Each version stores a separate set of planned costs per WBS element per cost element per period. Used for baseline comparisons, scenario planning, and re-forecasting. Managed in CJ40 (overall plan) or CJ42 (annual plan).
Example: Version 0 = original approved plan ₹10L. After scope change in month 3, Version 1 = revised plan ₹12L. CN41 cost element report can compare both versions side-by-side with actuals - showing the ₹2L scope increase clearly to stakeholders.
The project profile defines defaults for the whole project: controlling area, costing variant, budget profile, RA key, planning board. The network profile (assigned within the project profile) defines network-specific defaults: network type, scheduling type, factory calendar, and confirmation parameters.
Example: Project profile PP-INFRA → controls area IN01, budget profile BP01, RA key RA-POC. Network profile NP-01 (embedded in PP-INFRA) → network type PS01, backward scheduling, factory calendar IN_STD, final confirmation = auto GR. Both work together to fully configure the project.
A billing element is a WBS element flagged as a billing-relevant account assignment object. Only billing elements can be assigned to sales order line items. This controls at which level of the WBS hierarchy revenue is posted and RA is calculated - usually at the top WBS level per deliverable.
Example: Project WBS hierarchy: WBS.1 (billing element ✓), WBS.1.1, WBS.1.2. Sales order item references WBS.1. All revenue posts to WBS.1. Cost detail rolls up from WBS.1.1 and WBS.1.2. RA runs at WBS.1 level comparing total revenue vs rolled-up costs.
Standard PS period-end sequence: 1) Post all goods movements & invoices, 2) Network confirmations (CNF1), 3) Overhead calculation (CJ44), 4) Results Analysis (KKA2), 5) Settlement of networks to WBS (CJ88), 6) Settlement of WBS to receivers (CJ88), 7) Check FI balance (CO-FI reconciliation).
Example: Month-end March: All PO invoices posted by 31-Mar. 1-Apr: Run CJ44 - ₹2L overhead posted. Run KKA2 - ₹8L RA revenue recognised. Run CJ88 - networks settled to WBS, WBS settled to AuC. FI period closes 3-Apr after reconciliation check passes.
Project summarisation aggregates cost data from individual WBS elements into summarisation hierarchies for management reporting. Run via CJEO. Enables fast portfolio-level reporting without scanning individual project tables. Essential for organisations with hundreds of active projects.
Example: A company has 200 active projects grouped by Business Unit (BU). Running CJEO daily aggregates all WBS costs into BU-level summaries. CFO can view total capex spend per BU in real time from the summarisation hierarchy without waiting for project-level reports to run.
System statuses (CRTD, REL, TECO, CLSD) are set automatically by SAP based on business transactions. User statuses are custom statuses configured in a status profile (T-code BS02) and assigned to the project profile. They can allow, forbid, or require specific business transactions and can enforce approval workflows.
Example: Status profile SP-PROJ: User statuses: "APPR" (Approved by PM), "FROZ" (Frozen - no changes). FROZ status is configured to forbid new WBS creation and budget changes. When a project is put on hold, FROZ is set - SAP blocks any structural or financial changes until FROZ is removed.
ETC (Estimate to Complete) is the projected remaining cost to finish the project. EAC (Estimate at Completion) = Actual + ETC. In SAP PS, forecast values can be maintained manually per WBS element in CJ40 using a forecast version, or derived automatically from remaining work on network activities.
Example: WBS planned = ₹20L, actuals to date = ₹12L, but scope increased. PM estimates ₹11L remaining (ETC). EAC = ₹12L + ₹11L = ₹23L - a ₹3L overrun. This forecast is entered in CJ40 as version 2 and shown in the cost report alongside original plan for management review.
When GR is posted against a PO with a WBS account assignment, the actual cost is posted directly to the WBS element. The PO commitment is simultaneously reduced by the GR quantity/value. For project stock items, GR goes to Q stock - the WBS is only debited on the subsequent goods issue (GI).
Example: PO for ₹5L electrical cables assigned to WBS.3.1. Before GR: WBS has ₹5L PO commitment. After GR (MIGO, mvt 101): WBS commitment drops to zero and WBS actual cost increases by ₹5L. Budget utilisation = actuals + remaining commitments vs released budget.
Partial capitalisation occurs when a portion of a capital project is completed and placed in service before the full project is finished. The AuC balance for the completed portion is capitalised using AIAB (distribution) and AIBU (capitalisation) - the project remains active for the remaining work.
Example: Factory expansion: Block A (₹20L) completed in June, Block B (₹30L) ongoing. AIAB distributes 40% of AuC (₹20L) to Asset "Factory-Block A". AIBU capitalises it - depreciation starts July. Block B costs remain in AuC until completion in December.
RPSCO (Project Info Database) is the primary summarisation table for PS reporting. It stores cost totals by OBJNR + value type (WRTTP: 01=plan, 04=actual, 41=commitment) + fiscal year + period. All standard PS cost reports read from RPSCO for performance. Always join PRPS.OBJNR → RPSCO.OBJNR.
Example: ABAP query: SELECT from RPSCO WHERE OBJNR = 'PR000001234' AND WRTTP = '04' AND GJAHR = '2025' gives all actual cost lines for WBS by period. Sum WKG001 to WKG012 for full-year actuals. Used in custom project dashboards and BW extractors.
A cost plan is an internal estimate - AVAC does NOT check against it. A budget (original + supplements + transfers) is the formal spending limit - AVAC checks actuals + commitments against the released budget only. Unreleased budget is invisible to AVAC.
Example: WBS cost plan = ₹15L (internal estimate). Budget entered = ₹12L, but only ₹8L released so far. AVAC only controls against ₹8L released. Actual + commitments reach ₹8L → AVAC error. Even though cost plan says ₹15L and budget shows ₹12L - only the ₹8L release matters.
If annual budget is active, unused budget at year-end does not automatically carry forward. The budget carryforward program (CJCF) transfers unused annual budget to the next fiscal year. This requires the budget profile to allow carryforward. Requires FI period to still be open or a special period used.
Example: FY2024 annual budget = ₹10L, spent = ₹7L, unused = ₹3L. Run CJCF to carry ₹3L to FY2025 annual budget. Without CJCF, FY2025 starts with only its own original annual budget - AVAC would block ₹3L of planned spend from day one of the new year.
Assembly processing links a sales order to a production/project order for make-to-order (MTO) scenarios. When a sales order is created for an assembly-managed material, a PS network or production order is automatically created and linked. Costs flow directly to the sales order item for revenue matching.
Example: Customer orders a custom machine (MTO). On SO creation, PS automatically creates Network NW-5001 linked to the SO item. All material and labour costs post to NW-5001. On delivery, revenue posts to the SO. RA compares costs vs revenue for period-end recognition.
OBJNR (Object Number) is the universal key linking PS objects to CO postings. Format: PR + PSPNR for WBS elements, OR + AUFNR for network orders. All CO tables (COSP, COSS, RPSCO) use OBJNR as the key. It is stored in PRPS.OBJNR and AUFK.OBJNR.
Example: WBS element PSPNR = 000001234. Its OBJNR = 'PR000001234'. To find all actual costs: SELECT from COSP WHERE OBJNR = 'PR000001234' AND WRTTP = '04'. To find commitments: SELECT from COOI WHERE OBJNR = 'PR000001234'. OBJNR is the master key for all PS financial queries.
CJI3 (Project Actual Cost Line Items) displays all individual cost line items posted to project objects - actuals from GRs, invoices, confirmations, and settlements. Unlike RPSCO (summarised), CJI3 shows each individual document. Useful for audit trails and detailed cost investigations.
Example: PM notices ₹50,000 excess on WBS.2.1 in CN41 report. Run CJI3 for WBS.2.1 in April → see 45 line items. Filter by amount {'>'} ₹10,000 → find PO 4500001234 goods receipt for ₹48,000 posted on 15-Apr for unplanned materials - root cause identified in 2 minutes.
Network types are configured in the network profile and control the order type for the network. Common types: PS01 (standard project network - most common), PS02 (maintenance network for PM integration). Each type has its own number range, settlement profile, and order management settings. Configured in OPSC.
Example: PS01 networks settle to WBS elements (standard project work). PS02 networks integrate with Plant Maintenance - used when a project contains both project work (PS01) and equipment maintenance activities (PS02). Both network types can coexist under the same WBS hierarchy.
Key S/4HANA PS changes: Universal Journal (ACDOCA) replaces CO tables - all PS actuals now in one table. Project Management Fiori apps replace old GUI transactions. Overhead Ledger obsolete - reconciliation ledger removed. BW extractors updated. cProjects replaced by SAP Portfolio and Project Management (PPM).
Example: In ECC, PS actuals queried from COSP+COSS+RPSCO (multiple tables). In S/4HANA, all actual line items are in ACDOCA with field PSPNR for WBS. Custom ABAP reports need rewriting - SELECT from ACDOCA WHERE PSPNR = 'WBS-001' AND GJAHR = 2025 replaces the old multi-table join.
A statistical WBS element is flagged with the "statistical" indicator in PRPS. Costs posted to it are for information purposes only - they do not reduce the budget or trigger AVAC, and are not settled. Used for tracking/reporting sub-totals without affecting the cost accounting flow of the parent WBS.
Example: Engineering project: WBS.1 is the real account assignment. WBS.1.S is statistical, used to separately track "IT costs" (laptops, software) for management reporting. Costs still post to WBS.1 (real) but are also recorded statistically on WBS.1.S for IT spend dashboards - without double-counting budget.
The project definition planning dates (basic start/finish) are high-level dates used as constraints or for WBS-only projects without networks. The network scheduled dates are calculated precisely via CPM scheduling from activity durations and relationships. Network dates override WBS dates when both exist.
Example: Project definition has planned end = 31-Dec. Network backward scheduling from 31-Dec calculates that Activity 0010 "Site Survey" must start by 01-Mar. If the WBS planning date says start 01-Apr, the network date takes precedence for scheduling - the Gantt will show 01-Mar as the constrained start.
Three flags on each WBS element: Account Assignment Element - costs can be posted directly to this WBS (required for any WBS receiving actual costs). Planning Element - cost planning is allowed on this WBS. Billing Element - can be assigned to a sales order item for revenue. All three can be active simultaneously or selectively.
Example: Project structure: WBS.1 (Billing ✓, Planning ✓, Account Assignment ✗ - header only). WBS.1.1 (Account Assignment ✓, Planning ✓, Billing ✗ - receives costs). WBS.1.2 (Account Assignment ✓, Planning ✓, Billing ✗). Revenue posts to WBS.1; costs post to WBS.1.1 and WBS.1.2.
Check in sequence: 1) Does the WBS element have a settlement rule defined? (CJ20N → WBS → Settlement Rule tab). 2) Is the settlement profile assigned to the WBS via the project profile? 3) Is the receiver (cost centre/AuC) valid and active? 4) Is the settlement type PER or FUL set correctly? 5) Is the period open in CO and FI?
Example: CJ88 error on WBS.4.1. Check CJ20N → WBS.4.1 → Settlement Rule tab → blank (no rule). Root cause: project was created from a template but settlement rules were not transferred. Fix: add settlement rule manually - receiver = Cost Centre CC-2001, 100% FUL. Re-run CJ88 - settlement succeeds.
🗄️ Important SAP PS Database Tables
Every SAP PS consultant should be familiar with the key database tables used in Project Systems. These tables are essential for ABAP reporting, data extraction, and troubleshooting project data issues.
| Table | Description | Key Fields | Important Fields |
|---|---|---|---|
| PROJ | Project Definition - one row per project | PSPNR | PSPID (project ID), VBUKR (company code), VERNR (person responsible), PLFAZ/PLSEZ (plan start/end) |
| PRPS | WBS Element Master - one row per WBS element | PSPNR | POSID (WBS ID), PRART (WBS type), OBJNR (object number for CO), VERNR, KOSTL (cost centre) |
| PRHI | WBS Hierarchy - parent-child relationships between WBS elements | UP + AUFNR | UP (parent WBS number), OBJNR |
| AUFK | Order Master Data - used for network orders and internal orders | AUFNR | AUART (order type), WERKS, BUKRS, KOSTV (resp. cost centre) |
| AFKO | Network Header - network-level header data | AUFNR | NETZ (network number), PSPEL (WBS element), GSTRS/GSTRI (scheduled/actual start) |
| AFVG | Network Activities - one row per activity | AUFNR + VORNR | LTXA1 (description), ARBID (work centre), AUFKT (activity type), PSPEL (WBS assignment) |
| MSPT | Milestones for Networks | AUFNR + MSNR | MSPTP (milestone type), MSDAT (date), FAPRO (billing rule) |
| RPSCO | Project Info DB - summarised cost/plan data per WBS element | OBJNR + WRTTP + GJAHR + PERIO | WTGES (total value), BEKNZ (debit/credit indicator) |
| COSP | CO Cost Totals for External Postings - actual costs on WBS | OBJNR + WRTTP + GJAHR + KSTAR | WKG001–WKG016 (period values) |
| COSS | CO Cost Totals for Internal Postings - internal activity costs | OBJNR + WRTTP + GJAHR + KSTAR | WKG001–WKG016 (period values) |
Tip: Use transaction SE16N to browse data in these tables. For WBS cost reports, always join PRPS with RPSCO on the OBJNR field. The OBJNR in PRPS is in the format PR<PSPNR> and links all CO postings to the WBS element.
⚡ Key SAP PS Transactions
Knowing the most important PS transactions demonstrates practical hands-on experience to interviewers. The table below covers the essential transactions used daily by PS consultants.
| Transaction | Description | Area |
|---|---|---|
| CJ20N | Project Builder - create/change/display projects (WBS + Networks) | Project Management |
| CJ01/CJ02/CJ03 | Create / Change / Display WBS Element | WBS |
| CN21/CN22/CN23 | Create / Change / Display Network | Network |
| CJ30 | Original Budget Entry for WBS | Budgeting |
| CJ36 | Budget Release for WBS | Budgeting |
| CJ38 | Budget Transfer between WBS Elements | Budgeting |
| CJ88 | Settle Projects (WBS and Networks) | Period-End |
| CJ44 | Overhead Calculation for Projects | Period-End |
| KKA2 | Results Analysis for Projects | Period-End / Revenue |
| CNF1 | Network Activity Confirmation - individual | Confirmation |
| CN41 | Cost Element Report for WBS | Reporting |
| CN42 | Hierarchical Cost Report | Reporting |
| CJ31 | Budget Status Report | Reporting |
Interview Ready?
Resolve all PS questions, focus on the Advanced section for senior roles, and always back your answers with practical experience from your projects. Mention transactions and table names - it display real hands-on knowledge.
📘 Related SAP Tutorials
SAP FICO Training
Career paths, certification guide, and hands-on FICO module training for beginners and experienced consultants.
Read Tutorial