How To Fix MN812 - No purchasing group passed on

SAP Error Message - Details

• Message type: E = Error

• Message class: MN - Message class for subsequent settlement (Purchasing)

• Message number: 812

• Message text: No purchasing group passed on

What causes this issue?

The external data record does not contain a purchasing group.
However, the "Purchasing group" field (MCKONAB-EKGRP) is a
mandatory-entry field.

System Response

The external data record cannot be adopted.

How to fix this error?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message MN812 - No purchasing group passed on ?

  The SAP error message MN812 ("No purchasing group passed on") typically occurs in the context of purchasing documents, such as purchase orders or purchase requisitions, when the system expects a purchasing group to be specified but does not find one. This can happen for various reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Missing Purchasing Group: The purchasing group field is not filled in the relevant document (e.g., purchase order, requisition).
  Configuration Issues: The purchasing group may not be properly configured in the system.
  User Authorizations: The user may not have the necessary authorizations to assign a purchasing group.
  Data Entry Errors: There may be a data entry error where the purchasing group was inadvertently left blank.
  
  Solutions:
  
  
  Check Document Entry:
  
  Ensure that the purchasing group field is filled in when creating or modifying the purchasing document. This can usually be found in the header or item details of the document.
  
  
  
  Configuration Check:
  
  Verify that the purchasing groups are correctly defined in the system. You can check this in the configuration settings under:
  
  SPRO ? Materials Management ? Purchasing ? Define Purchasing Groups.
  
  
  Ensure that the purchasing group is assigned to the relevant purchasing organization.
  
  
  
  User Authorizations:
  
  Check if the user has the necessary authorizations to create or modify purchasing documents with the specified purchasing group. This can be done by reviewing the user's roles and authorizations.
  
  
  
  Data Validation:
  
  If the purchasing group is being derived from another source (like a vendor master record), ensure that the source data is correct and that the purchasing group is maintained in the vendor master.
  
  
  
  Error Logs:
  
  Review any error logs or messages that may provide additional context about why the purchasing group is not being passed on.
  
  
  
  Related Information:
  
  Purchasing Group: A purchasing group is a key organizational unit in SAP that is responsible for the procurement of materials and services. It can be assigned to various purchasing documents and is essential for reporting and analysis.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME51N (Create Purchase Requisition), and ME23N (Display Purchase Order) to troubleshoot and resolve issues.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for relevant notes in the SAP Support Portal.
  
  By following these steps, you should be able to identify the cause of the MN812 error and implement a solution to resolve it. If the issue persists, consider reaching out to your SAP support team for further assistance.