S4TM3 – Charges and Settlement in SAP S/4HANA TM — Lesson 1: Charge Management Concepts and Agreement Foundations

Learning Objectives

• Explain how Charge Management Concepts and Agreement Foundations supports reliable freight settlement.
• Complete the workflow and produce a reviewable charge-management design map.
• Evaluate the condition where an agreement is valid but is not selected for the freight document and select a supported response.

Detailed Topics

• Charge types and calculation bases: business purpose, responsible roles, and SAP objects that establish the operating scope.
• Calculation sheets and calculation rules: organizational assignments, master records, and dependencies required before processing begins.
• Freight agreements and validity conditions: navigation, field control, and status logic used to create a reliable starting point.
• Transportation charge master-data governance: approval and evidence checkpoints that confirm the foundation is ready for use.

Instructor Demonstration

The instructor traces Charge types and calculation bases, Calculation sheets and calculation rules, Freight agreements and validity conditions, Transportation charge master-data governance through the course scenario, explaining navigation, decision logic, dependencies, system messages, and the evidence retained in charge-management design map. The walkthrough also shows how to investigate the condition where an agreement is valid but is not selected for the freight document.

Hands-On Exercise

Complete a controlled activity covering Charge types and calculation bases, Calculation sheets and calculation rules, Freight agreements and validity conditions, Transportation charge master-data governance and preserve the final result in charge-management design map.

1. Define the expected business result and the SAP objects that should produce it.
2. Perform the lesson scenario, capturing before-and-after evidence for every material decision.
3. Test the exception without changing unrelated settings or data, then explain the first divergence.
4. Apply proportionate remediation and complete a focused regression test before handover.

Scenario Analysis

• Which SAP object, rule, master record, or process step most strongly influences the observed result?
• What evidence distinguishes a configuration problem from data, authorization, integration, or timing causes?
• How should the charge-management design map be approved, retained, monitored, and updated after handover?

Troubleshooting Guidance

Start at the earliest point where expected SAP behavior differs from the observed result. Review process sequence, master data, organizational assignments, configuration, authorization, integration, and timing separately. Treat “an agreement is valid but is not selected for the freight document” as a testable hypothesis until settings, documents, logs, reports, and retest outcomes confirm the cause.

Validation Checklist

• Required structures, master data, roles, settings, and dependencies for Charge Management Concepts and Agreement Foundations are present.
• The charge-management design map connects each conclusion to objective, reviewable SAP evidence.
• Normal processing, the stated exception, integration behavior, and access boundaries were tested.
• Corrections, retest criteria, ownership, documentation, monitoring, and operational handover are complete.

Lesson Outcome

Learners can apply Charge Management Concepts and Agreement Foundations, explain the resulting SAP behavior, and defend the outcome through charge-management design map.