SAP Knowledge Base Article - Preview

2014959 - How to prevent incident creation when there are errors in documents on SM_CRM


  • When creating an Incident and entering a wrong Component Field which doesn't exist, the Incident still gets saved with the wrong Component Field.
  • When creating an Incident in SM_CRM with "Reported By" entry whose Business Partner doesn't exist, Incident gets saved with error message:
    "Business Partner XXXX (Reported by) is not a business partner"
  • VAR Customers: When an end user creates Very High incident Out of Office hours, the incident should go to SAP automatically, but since the customer created in the wrong SAP component, the incident get stuck at SAP side.
  • A text has been flagged as "obligatory" in the Transaction type Text determination procedure, but the Incident can still be saved even if the text has not been provided in the document. 



  • SAP Solution Manager 7.1 
  • SAP Solution Manager 7.2


SAP Solution Manager 7.1 ; SAP Solution Manager 7.2


BP <entered name> (does not exist), Reported by, Assigned to, "is not a business partner" and CRM_UI, SM_CRM, ITSM, SOLMAN, sold-to party, Ibase, mandatory, force, error, IT service management, obligatory, prevent saving, disable save, text determination procedure, text, saved with errors, incident, web ui, , KBA , SV-SMG-SUP , Service Desk / Incident Management , SV-SMG-CM , Change Request Management , CRM-BTX-BF , Basic Functions for Business Transactions , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.