How To Fix 0D573 - Inbound category &1 not known in target system &2; message refused

SAP Error Message - Details

• Message type: E = Error

• Message class: 0D - FS-CD General Messages

• Message number: 573

• Message text: Inbound category &1 not known in target system &2; message refused

What causes this issue?

The &SYST-MSGV2& target system marks the &SYST-MSGV1& inbound
category as unknown and rejects the report(s).

System Response

No processing takes place in the target system.

How to fix this error?

Check whether the transferred inbound category &SYST-MSGV1& corresponds
to an inbound category defined in the &SYST-MSGV2& target system.
If necessary, correct the coding for your function module for FS-CD exit
V038, or adjust the settings or Customizing in the target system.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 0D573 - Inbound category &1 not known in target system &2; message refused ?

  The SAP error message 0D573 indicates that there is an issue with the inbound category not being recognized in the target system. This typically occurs in scenarios involving data transfer or communication between systems, such as in IDoc processing, ALE (Application Link Enabling), or other integration scenarios.
  Cause:
  The error message "Inbound category &1 not known in target system &2; message refused" suggests that the system is trying to process an inbound message of a specific category (denoted by &1) that is not defined or recognized in the target system (denoted by &2). This can happen due to several reasons:
  
  Configuration Issues: The inbound category may not be properly configured in the target system.
  Missing or Incorrect Mapping: The mapping of the inbound category to the corresponding processing logic may be missing or incorrect.
  Version Mismatch: There may be a version mismatch between the sending and receiving systems, leading to incompatibility in the expected message formats.
  Transport Issues: The message may not have been transported correctly, or the necessary components may not be present in the target system.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Configuration:
  
  Verify that the inbound category is correctly defined in the target system. This can typically be done in transaction codes like WE20 (Partner Profiles) or WE21 (Port Definition).
  Ensure that the necessary settings for the inbound processing are in place.
  
  
  
  Review Mapping:
  
  Check if there is a mapping defined for the inbound category in the target system. If not, you may need to create or adjust the mapping.
  
  
  
  Check for Updates:
  
  Ensure that both the sending and receiving systems are on compatible versions. If there are updates or patches available, consider applying them.
  
  
  
  Monitor IDoc Processing:
  
  Use transaction WE02 or WE05 to monitor the IDocs and check for any additional error messages or logs that might provide more context on the issue.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific inbound category and its expected configuration.
  
  
  
  Testing:
  
  After making the necessary changes, test the inbound processing again to ensure that the error has been resolved.
  
  
  
  Related Information:
  
  Transaction Codes:
  
  WE20: Partner Profiles
  WE21: Port Definition
  WE02/WE05: IDoc Monitoring
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the specific inbound category or error message.
  Documentation: Refer to SAP Help Portal for detailed information on ALE, IDocs, and inbound processing.
  
  If the issue persists after following these steps, it may be beneficial to engage with SAP support or consult with a technical expert familiar with your specific SAP landscape.