How To Fix /PF1/MSG_FH_GUI655 - Type of add. info not specified (prop.:'/01'?) for recip.item &2 (PO &1)

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/MSG_FH_GUI -

• Message number: 655

• Message text: Type of add. info not specified (prop.:'/01'?) for recip.item &2 (PO &1)

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 /PF1/MSG_FH_GUI655 - Type of add. info not specified (prop.:'/01'?) for recip.item &2 (PO &1) ?

  The SAP error message /PF1/MSG_FH_GUI655 Type of add. info not specified (prop.:'/01'?) for recip.item &2 (PO &1) typically indicates that there is a missing or incorrectly specified type of additional information for a recipient item in a Purchase Order (PO). This error can occur in various scenarios, particularly when dealing with purchase requisitions, purchase orders, or related documents in the SAP system.
  Cause:
  
  Missing Configuration: The error may arise if the system expects certain additional information (like a specific type of data) that has not been configured or is missing in the relevant master data.
  Incorrect Data Entry: There may be an issue with the data entered for the recipient item in the purchase order, such as an incorrect or incomplete entry in the fields that specify additional information.
  Custom Development: If there are custom enhancements or developments in the SAP system, they may not be handling the additional information correctly, leading to this error.
  Data Inconsistency: There could be inconsistencies in the data related to the recipient item or the purchase order.
  
  Solution:
  
  Check Configuration: Review the configuration settings for the relevant purchasing documents in the SAP system. Ensure that all necessary fields for additional information are properly defined.
  Review Data Entry: Go back to the purchase order and check the recipient item details. Ensure that all required fields are filled out correctly and that the type of additional information is specified.
  Consult Documentation: If there are specific requirements for the additional information type, consult the SAP documentation or your organization's guidelines to ensure compliance.
  Debugging: If you have access to the development environment, you may want to debug the transaction to see where the error is being triggered and what data is being processed at that time.
  Contact Support: If the issue persists, consider reaching out to your SAP support team or consulting with SAP support for further assistance. They may have insights into specific configurations or known issues related to this error.
  
  Related Information:
  
  Transaction Codes: You may want to check the relevant transaction codes such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), or ME23N (Display Purchase Order) to see if the error occurs in these transactions.
  SAP Notes: Search for SAP Notes related to this error message in the SAP Support Portal. There may be specific patches or updates that address this issue.
  User Exits and BAdIs: If your organization has implemented user exits or Business Add-Ins (BAdIs) related to purchasing, review them to ensure they are not causing the issue.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.