/ISDFPS/PM073 - Message type & unknown; IDoc ignored

SAP Error Message - Details

• Message type: E = Error

• Message class: /ISDFPS/PM -

• Message number: 073

• Message text: Message type & unknown; IDoc ignored

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.

AnswerBot

• What is the cause and solution for SAP error message /ISDFPS/PM073 - Message type & unknown; IDoc ignored ?

  The SAP error message /ISDFPS/PM073 Message type & unknown; IDoc ignored typically indicates that the system encountered an IDoc (Intermediate Document) with a message type that it does not recognize or that is not configured in the system. This can happen for various reasons, including configuration issues, missing message types, or incorrect settings in the IDoc processing.
  Causes:
  
  Unrecognized Message Type: The message type specified in the IDoc does not exist in the system.
  Configuration Issues: The IDoc type or message type may not be properly configured in the relevant SAP modules.
  Missing Partner Profile: The partner profile for the sender or receiver may not be set up correctly, leading to the system not recognizing the message type.
  Incorrect IDoc Type: The IDoc type being sent may not match the expected type for the given message type.
  Transport Issues: If the IDoc was transported from another system, the necessary configurations may not have been transported correctly.
  
  Solutions:
  
  
  Check Message Type: Verify that the message type specified in the IDoc is valid and exists in the system. You can do this by checking the relevant configuration in transaction WE81 (Message Types) or WE82 (IDoc Types).
  
  
  Configure IDoc Types: Ensure that the IDoc type is correctly configured in the system. You can check this in transaction WE30 (IDoc Types) and ensure that the message type is associated with the correct IDoc type.
  
  
  Review Partner Profiles: Check the partner profiles in transaction WE20 to ensure that the message type is correctly defined for the sender and receiver. Make sure that the necessary settings for inbound and outbound processing are in place.
  
  
  Check for Missing Customizations: If the IDoc was transported from another system, ensure that all necessary customizations and configurations have been transported as well.
  
  
  Debugging: If the issue persists, consider using transaction WE19 to simulate the IDoc processing and see if you can replicate the error. This can help in identifying the root cause.
  
  
  Consult Documentation: Review SAP documentation or notes related to the specific message type and IDoc processing for any additional guidance or known issues.
  
  
  Related Information:
  
  
  Transaction Codes:
  
  WE30: IDoc Types
  WE81: Message Types
  WE82: IDoc Types and Message Types
  WE20: Partner Profiles
  WE19: Test Tool for IDocs
  
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific message type or IDoc processing.
  
  
  IDoc Monitoring: Use transaction WE02 or WE05 to monitor IDocs and check for any additional error messages or details that may provide more context on the issue.
  
  
  By following these steps, you should be able to identify the cause of the error and implement the necessary solutions to resolve it.