S4F41 – Customizing in Cash Management in SAP S/4HANA — Lesson 2: Liquidity Items, Hierarchies, and Derivation Rules

Learning Objectives

• Explain how Liquidity Items, Hierarchies, and Derivation Rules supports transparent cash and liquidity management.
• Complete the workflow and produce a reviewable liquidity classification and derivation test pack.
• Evaluate the condition where a payment flow is assigned to an incorrect liquidity category and select a supported response.

Detailed Topics

• Liquidity item design: document sequence, decision points, and handoffs required for correct transaction execution.
• Liquidity item hierarchies: determination logic and master-data influences that shape the resulting SAP document flow.
• Derivation from G/L accounts and business context: status changes, confirmations, messages, and operational evidence produced during processing.
• Query structures for liquidity analysis: exception paths and recovery choices needed when normal processing cannot continue.

Instructor Demonstration

Using the stated scenario, the instructor demonstrates Liquidity item design, Liquidity item hierarchies, Derivation from G/L accounts and business context, Query structures for liquidity analysis. Particular attention is given to object relationships, field or status behavior, integration effects, and how liquidity classification and derivation test pack supports review. The demonstration deliberately introduces the exception where a payment flow is assigned to an incorrect liquidity category.

Hands-On Exercise

Complete a controlled activity covering Liquidity item design, Liquidity item hierarchies, Derivation from G/L accounts and business context, Query structures for liquidity analysis and preserve the final result in liquidity classification and derivation test pack.

1. Review prerequisites, process boundaries, master data, authorization, and acceptance criteria.
2. Complete the configured or transactional activity and preserve the resulting document and status trail.
3. Compare the normal result with the controlled exception and identify the most defensible root cause.
4. Record the selected response, validation result, residual risk, responsible owner, and review trigger.

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 liquidity classification and derivation test pack 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 “a payment flow is assigned to an incorrect liquidity category” 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 Liquidity Items, Hierarchies, and Derivation Rules are present.
• The liquidity classification and derivation test pack 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 Liquidity Items, Hierarchies, and Derivation Rules, explain the resulting SAP behavior, and defend the outcome through liquidity classification and derivation test pack.