Customer Line Items
Every customer line item — open, cleared, or all as of a key date — with its net due date and, once paid, its clearing document. The collections team's daily list (the old FBL5N), built on I_OperationalAcctgDocItem.
Sample build of the Customer Line Items report — open / cleared / all by key date, with the clearing document and net due date, tied to the Manage Customer Line Items balance, and rendered tool-neutral so it runs in Power BI, SAC, or Tableau.
| Document | Type | Posting | Net due | Amount | Status |
|---|---|---|---|---|---|
| 1900045123 | DR | 12 May 26 | 11 Jun 26 | 420,000 | Open |
| 1900044901 | DR | 02 Mar 26 | 01 Apr 26 | 1,100,000 | Open · 82d |
| 1900045088 | DR | 28 Apr 26 | 28 May 26 | 180,000 | Open · 25d |
| 1900044806 | DG | 15 Feb 26 | — | (60,000) | Cleared |
Every line item for the selected customers — open or cleared as of the key date — with its net due date and, once paid, its clearing document. Tied to the Manage Customer Line Items balance.
Document 1900044901 (1.10M) is 82 days past its net due date and still open — the single largest overdue receivable, roughly a third of the overdue balance on its own. Worth a collections call.
Status is "open on the key date": an item cleared after the key date still shows open, and the clearing date can differ from the payment date (SAP KBA 3169351). Set the key date to today before working the list.
The report's query logic — it reads the released CDS view I_OperationalAcctgDocItem (customer lines) and returns each line with its net due date, clearing document, and an open / cleared status as of the key date. The same SQL becomes a dbt model in your warehouse.
Show / hide SQL
SELECT it.CompanyCode,
it.Customer,
je.AccountingDocument AS document_no,
je.AccountingDocumentType AS doc_type,
je.PostingDate,
ADD_DAYS(it.DocumentItemDate,
TO_INTEGER(it.NetPaymentDays)) AS net_due_date,
it.AmountInCompanyCodeCurrency AS amount,
it.ClearingJournalEntry AS clearing_doc,
CASE WHEN it.ClearingDate IS NULL
OR it.ClearingDate > :P_KEY_DATE
THEN 'Open' ELSE 'Cleared' END AS status
FROM I_JournalEntry AS je
JOIN I_OperationalAcctgDocItem AS it
ON je.CompanyCode = it.CompanyCode
AND je.AccountingDocument = it.AccountingDocument
AND je.FiscalYear = it.FiscalYear
WHERE it.FinancialAccountType = 'D' -- D = customer (Debitor)
AND it.CompanyCode = :P_COMPANY_CODE
AND ( :P_STATUS = 'A' -- A = all items
OR (:P_STATUS = 'O' AND (it.ClearingDate IS NULL OR it.ClearingDate > :P_KEY_DATE))
OR (:P_STATUS = 'C' AND it.ClearingDate <= :P_KEY_DATE) )
ORDER BY net_due_date;The data-warehouse model — one fact surrounded by conformed dimensions (what you slice by) and measures (what you aggregate), expressed as dbt so it migrates with you. Grain: one row per line item (open or cleared).
| Element | Type | Definition |
|---|---|---|
| dim_customer | dimension | Customer — Business Partner (customer role), name, group |
| dim_company_code | dimension | Company code & ledger context |
| dim_gl_account | dimension | Reconciliation (receivables) account — RACCT |
| dim_date | dimension | Conformed calendar — posting & net due date |
| amount | measure | Line-item amount in company-code currency (HSL) |
| status | measure | Open / cleared as of the key date |
| days_overdue | measure | Key date minus net due date (open items) |
Every source object behind this report. Each linked object has its own page — with its fields and its real S/4HANA status, so you build on the right thing.
| Object | Role | Key fields | S/4HANA status |
|---|---|---|---|
| I_OperationalAcctgDocItem | Customer line item with payment terms — the read object | released | Released CDS view |
| ACDOCA | Universal Journal — the open amount & account assignment | 6 PK · 360+ | Transparent table |
| BSEG | Open-item management & payment terms (baseline date, net days) | 4 PK | Transparent table |
| Business Partner | Customer master (customer role) — the dimension | BUT000 | Transparent table |
| BSID / BSAD | Legacy customer open/cleared index — reference only, do not extract | — | Compat view → ACDOCA |
| Manage Customer Line Items | The S/4HANA app (FBL5N's successor) this report reconciles to — reference | app | Reconcile target |
- Line item
- One posting line on a customer account — an invoice, payment, or credit.
- Open item
- A line that isn't yet paid / matched — still owed.
- Cleared item
- A line that's been matched off (paid or offset) by a clearing document.
- Clearing document
- The journal that clears an open item; its date is the clearing date.
- Net due date
- When the item is actually due: baseline date plus the payment-term days.
- Key date
- The "open on" date — status is judged as of this date, so set it to today.
- ACDOCA
- SAP's single table holding every finance posting (the "Universal Journal").
- BSEG
- The table that still manages open items and payment terms in S/4HANA.
- I_OperationalAcctgDocItem
- The released view that gives the customer line with its terms (account type D = customer).
- Business Partner
- The single S/4HANA master for suppliers and customers (table BUT000).
- ODP-RFC
- An older extraction route SAP now bans for non-SAP tools (Note 3255746).