Quick Answer

SAP PS FICO integration means every cost and revenue on a project is also a posting in SAP Finance (FI) and Controlling (CO). WBS elements and network activities are CO objects, so invoices, labour confirmations, goods issues and overheads land on them with the same cost elements finance uses. At period end, results analysis and settlement carry project values to cost centers, assets and profitability analysis. In SAP S/4HANA, all of it sits in one Universal Journal. SaiSatwik designs SAP PS FICO integration so project managers and controllers read the same numbers.

What does SAP PS FICO integration mean?

Definition: SAP PS FICO integration is the set of links that make SAP Project System objects part of the financial and controlling structure. A WBS element is not a separate ledger. It is an account assignment object inside CO, tied to a company code, a controlling area and a profit center.

That design is why SAP PS reports and finance reports agree. A supplier invoice posted to a WBS element updates the G/L, the project’s actual costs and the profit center at the same moment. There is no overnight interface to reconcile.

Which FICO settings does every SAP PS project depend on?

Before a single project is created, several FICO structures must exist. Missing any of them stops the project definition from saving. The table shows what each one gives a project.

FICO object	What it gives the project
Company code	The legal entity whose books the project posts to
Controlling area	The CO scope for cost collection and settlement
Profit center	Segment and margin reporting for the project
Cost elements	The categories of cost and revenue on every posting
Activity types and rates	The price of internal labour and machine time
Costing sheet	The rules that calculate overhead on project costs

How do project costs flow from SAP PS into FICO?

Costs reach a project through four main routes. Each one posts to FI and CO at the same time, with the WBS element or network activity as the account assignment.

• Supplier invoices and direct postings. An invoice or journal entry carrying a WBS element posts the expense and the project cost together.
• Labour confirmations. Hours confirmed on network activities are valued at the activity rate and credit the work center’s cost center.
• Goods issues. Material issued to a project posts its value from inventory to the project.
• Overheads. CJ44 for one project or CJ45 collectively applies the costing sheet to add overhead.

Commitments matter as well. Open purchase orders show on the project as committed cost, which is what availability control in SAP PS checks against the budget.

What is the SAP PS period-end close sequence?

The SAP PS period-end close follows a fixed order, because each step uses values the previous step produced. Finance teams usually run it as one scheduled job chain.

1. Complete actual postings. Invoices, confirmations and goods issues for the period.
2. Calculate overhead. CJ45 applies costing sheets across projects.
3. Run results analysis. KKAJ values customer projects. See the guide to results analysis in SAP PS.
4. Settle. CJ8G moves costs and results to receivers. The SAP PS settlement guide covers rules and receivers.
5. Report. Plan, actual and commitment reports per project and per profit center.

How do capital projects connect SAP PS to Asset Accounting?

Capital projects add Asset Accounting (FI-AA) to the integration. An investment profile on the WBS element creates an asset under construction when the element is released. Monthly settlement builds its value, and final settlement capitalises the completed fixed assets.

Large programmes often add SAP Investment Management above the projects to govern the capital budget. The comparison of SAP Investment Management and SAP EPPM explains where that layer fits.

What changed for SAP PS FICO integration in SAP S/4HANA?

The biggest change is the Universal Journal. In SAP S/4HANA, FI and CO postings land in one table, ACDOCA. Project costs, G/L lines and profitability data sit in the same line item.

Cost elements also changed. They are now G/L accounts with a cost element category, maintained in the chart of accounts instead of a separate CO master. Migration teams need to plan for this early, since SAP has set mainstream maintenance for ECC to end in 2027, with optional extended maintenance to 2030, according to SAP’s maintenance announcement.

Why does tight PS and FICO integration matter?

Disconnected project and finance data hides overruns until they are expensive. McKinsey and Oxford research found large IT projects run 45 percent over budget on average. Integrated cost data does not prevent overruns, but it surfaces them the week they start.

How does SaiSatwik approach SAP PS FICO integration?

SaiSatwik runs SAP PS and FICO design as one workstream, not two teams passing documents. Project profiles, settlement profiles, costing sheets and profit center derivation are agreed in the same workshops with controllers in the room.

That approach is standard in every engagement from the SaiSatwik SAP practice, on ECC and SAP S/4HANA alike. For the project side of the picture, start with the SAP PS beginner guide.

Related SaiSatwik Reading

More from the SAP PS series:

• SAP PS project cost planning guide. How plans feed CO reporting.
• SAP EPPM architecture and integration overview. The wider integration map.
• SAP ECC to S/4HANA migration guide. Planning the move to the Universal Journal.

FAQs about SAP PS FICO integration

Is a WBS element a cost object in SAP CO?

Yes. A WBS element with the account assignment indicator is a CO account assignment object. Costs, revenues and commitments post to it, and it settles to final receivers at period end.

Which transaction calculates overhead on SAP PS projects?

CJ44 calculates overhead for an individual project and CJ45 runs it collectively. Both apply the costing sheet assigned to the WBS element or network.

Do SAP PS and FI need reconciliation?

Not in the usual sense. Postings to projects are FI and CO postings at the same time. In SAP S/4HANA they share one line item in the Universal Journal, so project and ledger values cannot drift apart.

Who should own SAP PS FICO integration design?

Both the project controlling lead and the finance controller. Settlement, overhead and revenue recognition choices affect the financial statements, so finance must sign them off, while the project side owns structure and planning.