Do you have any question about this error?
Message type: E = Error
Message class: MN - Message class for subsequent settlement (Purchasing)
Message number: 807
Message text: No purchasing organization passed on
The external data record does not contain a purchasing organization.
However, the "Purchasing organization" field (MCKONAB-EKORG) is a
mandatory-entry field.
The external data record cannot be adopted.
Please correct the external data file.
If the error did not occur in a check run and you have written to the
"actual" data (version '000'), you should cancel the update of the
external supplier business volume data to ensure that the data remains
consistent.
Error message extract from SAP system. Copyright SAP SE.
MN807
- No purchasing organization passed on ?The SAP error message MN807 ("No purchasing organization passed on") typically occurs in the context of purchasing documents, such as purchase orders or purchase requisitions, when the system expects a purchasing organization to be specified but does not find one. This can happen in various scenarios, including when creating or processing purchasing documents.
Causes:
- Missing Purchasing Organization: The purchasing organization field is not filled in the document you are trying to create or process.
- Configuration Issues: The purchasing organization may not be properly configured in the system.
- Master Data Issues: The vendor or material master data may not have a purchasing organization assigned.
- User Input Error: The user may have overlooked entering the purchasing organization in the relevant field.
Solutions:
- Check Document Fields: Ensure that the purchasing organization field is filled in the document you are working with. This is usually a mandatory field.
- Review Master Data:
- Check the vendor master data to ensure that the purchasing organization is assigned correctly.
- Check the material master data to ensure that the purchasing organization is assigned if applicable.
- Configuration Check:
- Verify that the purchasing organization is correctly configured in the system. This can be done by navigating to the relevant configuration settings in SPRO (SAP Project Reference Object).
- Ensure that the purchasing organization is assigned to the relevant company code and plant.
- User Training: If the issue is due to user error, consider providing training or documentation to ensure users understand how to fill in the necessary fields correctly.
Related Information:
If the problem persists after checking these areas, it may be beneficial to consult with your SAP support team or refer to SAP documentation for further assistance.
Get instant SAP help. Start your 7-day free trial now.
MN806
Provisions for income for cond. type & not allowed (have been deleted)
What causes this issue? The indicator "Provision" (provisions for accrued rebate income) has not been set for condition type &V1&. ...
MN805
No external data record for condition type &
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
MN808
No company code passed on
What causes this issue? The external data record does not contain a company code. However, the "Company code" field (MCKONAB-BUKRS) is a ma...
MN809
No material group passed on
What causes this issue? The external data record does not contain a material group. However, the "Material group" field (MCKONAB-MATKL) is ...
Click on this link to search all SAP messages.