ME38 — Maintain Scheduling Agreement Delivery Schedule
ME38 is used to create or change delivery schedule lines for a scheduling agreement item. It is most useful when a supplier must be given dated requirement quantities under a scheduling agreement or schedule lines require adjustment. Start with the exact organizational keys, business document and date, then reconcile the resulting SAP document or status before changing master data or configuration.
Verified practitioner reference for ME38 — Maintain Scheduling Agreement Delivery Schedule. The page covers purpose, when to use it, practical execution, the key business data to capture, how to prove the result, S/4HANA context, common mistakes, ownership and related SAP objects.
Published 19 Sept 2026· 604 words
Esta página ainda não está disponível em português.
Purpose
create or change delivery schedule lines for a scheduling agreement item. Treat ME38 as one step in an end-to-end process. Values shown or posted here are usually driven by master data, organization, dates and preceding documents, so an accurate diagnosis starts by preserving those inputs rather than changing the symptom screen first.
When it is used
ME38 is typically used when a supplier must be given dated requirement quantities under a scheduling agreement or schedule lines require adjustment. It is also valuable in project and regression testing because it provides a repeatable business state. In production, use the narrowest document or organizational selection that answers the question and capture the before-state before any posting, clearing or configuration change.
How to use it in practice
- Open the scheduling agreement and relevant item.
- Review existing lines and cumulative quantities.
- Enter or change delivery dates and quantities based on approved planning demand.
- Check blocks or trade-compliance status where applicable.
- Save and verify the schedule in the agreement and downstream release process.
Key data objects
These are the fields and business objects that most often explain the result in ME38. Record them in support evidence so the next person can reproduce the same outcome.
- scheduling agreement/item — verify the exact value, validity/date context and relationship to the source document.
- delivery date — verify the exact value, validity/date context and relationship to the source document.
- scheduled quantity — verify the exact value, validity/date context and relationship to the source document.
- cumulative quantities — verify the exact value, validity/date context and relationship to the source document.
- release/international-trade status — verify the exact value, validity/date context and relationship to the source document.
How to prove it in the data
Use document flow and chronology. Start from the source business event, inspect the ME38 document or master data, then follow the resulting accounting, purchasing or asset document and reconcile amount, quantity, account assignment and status. A correct proof uses the same company code or plant, business date, document keys and currency/unit context at every step.
ECC vs S/4HANA
SAP Help documents ME38 as the transaction for maintaining scheduling agreement delivery schedules, including current S/4HANA scenarios. Where S/4HANA offers a Fiori successor or a changed data model, the classic transaction can still be valuable for support, but the strategic process and clean-core guidance should govern new implementations.
Common pitfalls and how to diagnose them
- Entering schedule lines inconsistent with the agreement validity/target. Reconcile the exact business document and date before applying a workaround.
- Changing dates to hide MRP exceptions instead of correcting planning. Reconcile the exact business document and date before applying a workaround.
- Ignoring cumulative quantities in JIT/forecast processes. Reconcile the exact business document and date before applying a workaround.
Whose problem this is
Primary ownership is the MM/P2P team, with adjacent teams involved when the evidence crosses into Asset Accounting, Project System, tax, Basis, Security or integration. Escalate with document numbers, organization, dates, expected result, actual result and checks already completed.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-tcodes/me38ERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.