SAP Reference

ME31L

Create S/4HANA status: Active

Create Scheduling Agreement

Module: MM · Materials Management
What the badges mean
S/4HANA status: Active
Active and unchanged in S/4HANA.
S/4HANA status: Deprecated
Still readable today, but no longer SAP's strategic path — plan around it.
S/4HANA status: Replaced
Replaced by a new persistence in S/4HANA; the classic name may still answer reads (see read mechanism).
S/4HANA status: Migrating to IBP
Planning scope is moving from APO toward IBP.
S/4HANA status: Active (StRM) · Replaced (EWM)
Path-dependent: active with SAP Stock Room Management, replaced where EWM is the warehouse path.
S/4HANA status: Replaced · Compat View
Compatibility view: the classic table name is redirected to a view over the new persistence — see how the physical model moved.
S/4HANA status: Active · Proxy View
Proxy view: reads route through NSDM proxy/CDS views — see how the physical model moved.
master
Data class: what the table holds — master data, transaction documents, org structure, config, or texts (one row per language — see the quirks guide).
In field listings, K marks a primary-key field, and linked type codes in the Type column jump to the matching quirks-guide section.

Boilerplate SQL

Databricks SQL

Starting point for querying the tables behind this transaction. Set your Unity Catalog location and filter values below — they’re substituted into the SQL and the copy button.

Query parameters

4 parameters not filled: <catalog>, <schema>, <MANDT>, <EBELN>

-- ============================================================
-- T-Code : ME31L Create Scheduling Agreement
-- Purpose: Create Scheduling Agreement — auto-generated boilerplate from tcode-table-map
-- Grain  : One row per EKKO joined to EKPO, EKET, T161
-- Tables : EKKO, EKPO, EKET, T161
-- Notes  : Auto-generated skeleton. Add MAKT/T001W/LFA1/KNA1 enrichment joins as needed for the business question. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
  h.MANDT       AS "Client",
  h.EBELN       AS "Purchasing Document Number",
  h.DESCRIPTION AS "Description",
  l.EBELP       AS "Item Number of Purchasing Document",
  e.EBELP       AS "Item Number of Purchasing Document",
  e.ETENR       AS "Delivery Schedule Line Counter",
  t.BSTYP       AS "Purchasing Document Category"
FROM <catalog>.<schema>.ekko h
LEFT JOIN <catalog>.<schema>.ekpo l
  ON l.MANDT = h.MANDT
 AND l.EBELN = h.EBELN
LEFT JOIN <catalog>.<schema>.eket e
  ON e.MANDT = h.MANDT
 AND e.EBELN = h.EBELN
LEFT JOIN <catalog>.<schema>.t161 t
  ON t.MANDT = h.MANDT
 AND t.BSART = h.BSART
WHERE
  h.MANDT = '<MANDT>'
  AND h.EBELN = '<EBELN>'
ORDER BY h.EBELN;

Tables Used by This Transaction

A curated list of the main business tables behind this transaction, drawn from this reference’s catalog. Tables a query joins only for names and descriptions may be left out.

How these tables connect — join details in the list below.

Loading relationship diagram…

Join details

  • EKKOEKPOheader item · 1:N
    ON ekko.EBELN = ekpo.EBELN
  • EKKOT161check table · N:1
    ON ekko.BSART = t161.BSART

R read · W write · R/W read + write

More Materials Management t-codes