S4123 – Project Controlling in SAP S/4HANA Project System — Lesson 4: Settlement Rules, Period-End Closing, Capitalization, Reporting, Reconciliation, and Governance

Learning Objectives

• Explain the SAP structures, data, settings, roles, and dependencies governing project settlement and close.
• Perform and validate capitalization, reporting, reconciliation, and governance using reviewable system evidence.
• Evaluate the condition where period-end close produces unexpected balances because planning versions, budget tolerances, overhead rules, results-analysis keys, settlement profiles, and receiver rules are inconsistent and select proportionate corrective action.

Detailed Topics

• Settlement Rules applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Period-End Closing applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Capitalization applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Reporting applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• Reconciliation applied to the course scenario, expected SAP behavior, dependencies, and evidence.
• and Governance applied to the course scenario, expected SAP behavior, dependencies, and evidence.

Instructor Demonstration

The instructor traces a project finance team controlling capital and customer-project performance from baseline planning through period-end close. The walkthrough connects navigation, configuration or process logic, system messages, and evidence captured in the S4123 project cost, budget, results-analysis, and settlement workbook. It also tests the exception where period-end close produces unexpected balances because planning versions, budget tolerances, overhead rules, results-analysis keys, settlement profiles, and receiver rules are inconsistent.

Hands-On Exercise

Complete a controlled SAP exercise covering Settlement Rules, Period-End Closing, Capitalization, Reporting, Reconciliation, and Governance and preserve the verified result in the S4123 project cost, budget, results-analysis, and settlement workbook.

1. Confirm scope, prerequisites, master data, roles, dependencies, and acceptance criteria.
2. Execute the workflow while recording settings, transactions, outputs, and system messages.
3. Test normal behavior, one boundary condition, and the stated exception.
4. Document corrections, evidence, ownership, retest criteria, and handover actions.

Scenario Analysis

• Identify which object, rule, setting, or process step most strongly influences project settlement and close.
• Compare two defensible responses and explain business, technical, control, and support trade-offs.
• Determine how the S4123 project cost, budget, results-analysis, and settlement workbook should be approved, retained, retested, and updated.

Troubleshooting Guidance

Start where expected SAP behavior first differs from the observed result. Check master data, configuration sequence, authorization, integration, status, and transaction evidence separately. Treat “period-end close produces unexpected balances because planning versions, budget tolerances, overhead rules, results-analysis keys, settlement profiles, and receiver rules are inconsistent” as a hypothesis until system settings, logs, documents, and outcomes confirm the cause.

Validation Checklist

• Required SAP structures, master data, roles, settings, and dependencies are present.
• The S4123 project cost, budget, results-analysis, and settlement workbook connects each conclusion to objective, reviewable evidence.
• Normal processing, the boundary condition, integration behavior, and exception were tested.
• Corrections, ownership, retest criteria, documentation, and operational handover are complete.

Lesson Outcome

Learners can apply Settlement Rules, Period-End Closing, Capitalization, Reporting, Reconciliation, and Governance, explain the resulting SAP behavior, and defend the outcome through the S4123 project cost, budget, results-analysis, and settlement workbook.