CJI3 — Project Actual Cost Line Items
CJI3 is used to display actual project/WBS cost line items with document, cost element and sender/receiver detail. It is most useful when project controllers need to reconcile WBS actual costs, investigate unexpected postings or support settlement. Start from the exact business object, organizational scope and status, then prove the result through document flow, logs or master data before applying a corrective action.
This ERPClimb practitioner page covers CJI3 — Project Actual Cost Line Items. It focuses on the transaction's real operational role, the parameters that matter, the evidence needed to diagnose problems, S/4HANA context, and the mistakes that cause most support rework.
Published 19 Sept 2026· 626 words
Esta página ainda não está disponível em português.
Purpose
display actual project/WBS cost line items with document, cost element and sender/receiver detail. CJI3 is most useful when treated as part of an end-to-end process rather than a shortcut. The object status you see here is usually influenced by upstream master data, configuration, planning or document history, so capture those inputs before changing anything.
When it is used
CJI3 is typically used when project controllers need to reconcile WBS actual costs, investigate unexpected postings or support settlement. It is also valuable during project testing because it exposes a repeatable state that can be compared before and after configuration or master-data changes. In production, narrow the population first and distinguish display/analysis from actions that post, approve, replicate or change status.
How to use it in practice
- Select the project/WBS and accounting period.
- Add document, cost element and sender fields.
- Drill into the source FI/CO document.
- Separate commitments from actual costs when reconciling budget.
- Compare totals with project reports and settlement results.
Key data objects
These are the most useful anchors when working in CJI3. Capture them in screenshots, test evidence and incident handovers so another consultant can reproduce the same result and identify whether the issue is data, configuration, status or integration.
- project/WBS — verify the exact value, validity/date context and relationship to the affected process.
- posting period/date — verify the exact value, validity/date context and relationship to the affected process.
- cost element/G/L — verify the exact value, validity/date context and relationship to the affected process.
- document — verify the exact value, validity/date context and relationship to the affected process.
- amount and sender — verify the exact value, validity/date context and relationship to the affected process.
How to prove it in the data
Build an evidence chain rather than relying on one message: identify the source requirement or master record, show the transaction status or worklist entry, then show the resulting document, posting, warehouse object, planning element or replication log. Use the same date and organizational scope throughout. That makes the diagnosis repeatable and separates a true fix from a coincidental retry.
ECC vs S/4HANA
Project actuals on S/4HANA ultimately integrate with the Universal Journal, while CJI3 remains a familiar PS line-item analysis tool. Where a Fiori app or cloud service becomes the strategic user experience, the SAP GUI transaction can still remain valuable for support, migration and deep technical analysis, but it should not be used to justify a legacy design for new work.
Common pitfalls and how to diagnose them
- Comparing CJI3 actuals with a report that includes commitments. Return to the exact object status and chronology before applying a workaround.
- Using today's WBS hierarchy to explain historical assignments without checking changes. Return to the exact object status and chronology before applying a workaround.
- Summing multiple currencies without a consistent value field. Return to the exact object status and chronology before applying a workaround.
Whose problem this is
Primary ownership is the PS team, with adjacent functional, Basis, Security or integration teams joining when the evidence crosses system boundaries. Escalate with the object/document number, organization, date/time, expected result, actual status and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/cji3ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.