How To Fix AG806 - No goods accepted on &1. The next possible date is: &2

SAP Error Message - Details

• Message type: E = Error

• Message class: AG - Nachrichten ATP-Server

• Message number: 806

• Message text: No goods accepted on &1. The next possible date is: &2

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message AG806 - No goods accepted on &1. The next possible date is: &2 ?

  The SAP error message AG806 "No goods accepted on &1. The next possible date is: &2" typically occurs in the context of goods receipt processing in SAP, particularly when dealing with inventory management or logistics. This message indicates that there is a restriction on accepting goods on the specified date (&1), and it provides the next possible date (&2) when goods can be accepted.
  Cause:
  
  Date Restrictions: The system may have been configured to restrict goods receipts on certain dates, such as weekends, holidays, or specific cut-off times.
  Inventory Management Settings: There may be settings in the inventory management module that prevent goods from being accepted on certain dates.
  Plant or Storage Location Issues: The plant or storage location may have specific rules or configurations that restrict goods acceptance.
  Open Purchase Orders: There may be no open purchase orders for the items being received on the specified date.
  System Configuration: The system may be configured to only allow goods receipts on certain days or during specific time frames.
  
  Solution:
  
  Check the Date: Verify the date you are trying to process the goods receipt. If it is a non-working day or a holiday, consider processing it on the next possible date provided in the error message.
  Review Configuration: Check the configuration settings in the inventory management module to see if there are any restrictions on goods receipts for the specified date.
  Consult with Logistics Team: If you are unsure about the restrictions, consult with your logistics or inventory management team to understand the policies in place.
  Adjust Purchase Orders: Ensure that there are open purchase orders for the items you are trying to receive. If necessary, create or adjust purchase orders accordingly.
  Check Plant/Storage Location Settings: Review the settings for the specific plant or storage location to ensure that they allow for goods receipts on the desired date.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like MIGO (Goods Movement) or ME23N (Display Purchase Order) to check the status of purchase orders and goods movements.
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message.
  Documentation: Refer to SAP documentation for inventory management and goods receipt processes for more detailed information on handling goods receipts and related configurations.
  
  If the issue persists after checking the above points, it may be beneficial to involve your SAP support team or consult with SAP experts for further troubleshooting.