Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 135
Message text: Sales document & not a billing document
When the settlement documents for rebate arrangement &V2& were
imported, sales document &V1& was read. This document is not a billing
document (sales document type &V3&).
INCLUDE ISR_VERARBEITUNG OBJECT DOKU ID TX
INCLUDE ISR_SYSTEMFEHLER OBJECT DOKU ID TX
Error message extract from SAP system. Copyright SAP SE.
MN135
- Sales document & not a billing document ?The SAP error message MN135 ("Sales document & not a billing document") typically occurs when there is an attempt to process a billing document (like creating an invoice) for a sales order that is not in a status that allows billing. This error can arise in various scenarios, such as when the sales order is incomplete, not fully delivered, or has not been properly processed.
Causes:
- Incomplete Sales Order: The sales order may not have all the necessary data filled out, or it may be missing required items.
- Delivery Status: The sales order may not have been fully delivered. Billing can only occur for items that have been delivered.
- Document Flow Issues: There may be issues in the document flow where the sales order is not linked correctly to a delivery or other related documents.
- Billing Block: The sales order may have a billing block set, preventing it from being billed.
- Sales Order Status: The status of the sales order may not allow for billing (e.g., it may be in a status that indicates it is still being processed).
Solutions:
- Check Sales Order Status: Review the status of the sales order in the SAP system. Ensure that it is complete and ready for billing.
- Verify Delivery: Ensure that the items in the sales order have been delivered. You can check the delivery document associated with the sales order.
- Remove Billing Block: If there is a billing block on the sales order, it needs to be removed. This can be done by editing the sales order and removing the block.
- Complete Sales Order: If the sales order is incomplete, complete all necessary fields and ensure that all items are accounted for.
- Check Document Flow: Review the document flow to ensure that all necessary documents (sales order, delivery, etc.) are correctly linked and processed.
- Consult with SAP Support: If the issue persists, it may be beneficial to consult with your SAP support team or refer to SAP documentation for further troubleshooting.
Related Information:
VA03
(Display Sales Order), VL03N
(Display Outbound Delivery), and VF03
(Display Billing Document) to check the status and details of the sales order and related documents.By following these steps, you should be able to identify the cause of the MN135 error and take appropriate action to resolve it.
Get instant SAP help. Start your 7-day free trial now.
MN134
***** FUNCTION GROUPS WN01/WN02 ******
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN133
Billing or accounting document not created until you save
What causes this issue? Settlement accounting for arrangement &V1& has been effected and the billing or accounting document created but not y...
MN136
Billing doc. & not a billing doc. for rebate arrangement & (Purchasing)
What causes this issue? During import of the settlement documents, customer billing document &V1& was read. This document belongs to rebate a...
MN137
Billing document & not yet forwarded to Financial Accounting
What causes this issue? Billing document &V1& has not yet been released to Financial Accounting. The document must be released to Financial A...
Click on this link to search all SAP messages.