Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 548
Message text: Delivery schedule missing for purchasing document &, item &
A supplier business volume update for the purposes of subsequent
(end-of-period rebate) settlement (Purchasing) was to have been carried
out for purchasing document &V1&, item &V2& at the time of -&V3&- (&V4&
).
To carry out the update, the update program needs the data records for
the delivery schedule.
However, there is no delivery schedule for purchasing document &V1&,
item &V2&. The document conditions contain conditions requiring
<DS:GLOS.3526C095AFAB52B9E10000009B38F974>subsequent settlement</>.
No supplier business volume update for "subsequent settlement"
accounting purposes will be carried out.
Please look into the matter. You must create the delivery schedule and
post the supplier business volumes retrospectively.
Error message extract from SAP system. Copyright SAP SE.
MN548
- Delivery schedule missing for purchasing document &, item & ?The SAP error message MN548 indicates that there is a missing delivery schedule for a specific purchasing document and item. This error typically occurs in the context of materials management and procurement processes when the system cannot find the expected delivery schedule for a purchase order or scheduling agreement.
Cause:
- Missing Delivery Schedule: The most common cause is that the delivery schedule has not been created or is not properly linked to the purchasing document.
- Incorrect Document Type: The purchasing document may not be of a type that supports delivery schedules.
- Data Entry Errors: There may be typographical errors in the purchasing document or item number.
- Incomplete Configuration: The system may not be configured correctly to handle delivery schedules for the specific purchasing document type.
- Document Status: The purchasing document may be in a status that does not allow for delivery schedules to be processed.
Solution:
- Check Delivery Schedule: Verify if a delivery schedule exists for the specified purchasing document and item. You can do this by navigating to the relevant transaction (e.g., ME33L for scheduling agreements).
- Create or Update Delivery Schedule: If a delivery schedule is missing, you may need to create one. Use transaction ME38 (for scheduling agreements) or ME21N (for purchase orders) to add or update the delivery schedule.
- Review Document Type: Ensure that the purchasing document type you are using supports delivery schedules. If not, consider using a different document type.
- Correct Data Entry: Double-check the purchasing document and item numbers for any errors. Ensure that you are referencing the correct documents.
- Check Configuration: If you suspect a configuration issue, consult with your SAP Basis or configuration team to ensure that the system is set up correctly for handling delivery schedules.
- Status Check: Ensure that the purchasing document is in a status that allows for the processing of delivery schedules. If it is blocked or in a different status, you may need to resolve that first.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in materials management.
Get instant SAP help. Start your 7-day free trial now.
MN547
Delivery date missing for schedule line & of purchasing doc. &, item &
What causes this issue? Schedule line &V3& for item &V2& of purchasing document &V1& does not contain a delivery date. This s...
MN546
Please pass on PO history or schedule for document &, item &
What causes this issue? Internal program error.System Response Processing has been canceled.How to fix this error? Contact your system administrato...
MN549
Updating for sched. agmt. with master conditions only from material doc.
What causes this issue? The price determination process for scheduling agreements with master conditions takes place at the time of goods receipt. Th...
MN550
Document condition and condition record have different calculation rules
What causes this issue? The document condition has the calculation rule &V1&, whereas the associated condition record has the calculation rul...
Click on this link to search all SAP messages.