Symptom
Certain Journal Entries are classified in the "Overdue" column within the Cash Flow Analyzer or Liquidity Forecast apps, even though the document's Net Due Date is set in the future.
Environment
SAP S/4HANA Cloud Public Edition
Reproducing the Issue
- Open the Liquidity Forecast (or Cash Flow Analyzer) app for a key date that is before the journal entry’s net due date and observe the payable shown in the Overdue column.
- Open the Accounts Payables app (journal entry view, Aging grid) for the same key date.
- Observe the same payable shown in a future time bucket (Future) with zero amount in Overdue.
Cause
The One Exposure from Operations (FQM) platform determines the position of a cash flow based on a specific logic hierarchy. The system does not primarily use the Net Due Date for the time axis, but rather:
- Planning Date (FDTAG): The system first checks this field in the journal entry line item.
- Value Date (VALUT): If the Planning Date is empty, the system refers to the Value Date.
Resolution
This is standard system behavior.
The Planning Date is a derived field calculated at the point of entry. Once a document is posted, the accounting logic that determines the Planning Date cannot be easily re-triggered or manually edited through standard Fiori interfaces for existing documents.
Keywords
liquidity forecast, cash flow analyzer, aging grid, accounts payable aging, overdue bucket, future bucket, planning date, FDTAG, value date, VALUT, one exposure, flow builder, cash management, forecast classification, due date discrepancy , KBA , FIN-FSCM-CLM-2CL , Cash Management (Public Cloud) , Problem
SAP Knowledge Base Article - Public