IDoc partner profile
Partner profile not found for IDoc
Inbound or outbound IDoc processing fails because SAP cannot find a matching partner-profile parameter for the partner, message type and direction.
Likely root causes
- WE20 partner profile is missing the required inbound/outbound parameter.
- Partner type/number in the control record does not match the profile.
- Message type/process code/port combination was not transported or maintained.
What to inspect
- WE02/WE05 control record partner number, partner type and message type.
- WE20 partner profile for the exact direction/message type.
- Port/process code assigned to the matching parameter.
Resolution path
- Correct control-record partner data if the sender mapped it incorrectly.
- Maintain the required partner-profile parameter through integration governance.
- Verify message type, process code and port all belong to the intended interface.
- Reprocess only after the profile matches the IDoc control record.
ERPClimb is an independent platform and is not affiliated with SAP SE.