Integrate Solution Manager with Jira

[#1]

Hi,

We struggle with the Solution Manager - Jira integration for bi-directional creation/update of incidents. Middleware to facilitate is the Integration Suite.

When an incident is created in SAP Solution Manager, we want this incident to be forwarded to the Jira tool. We have followed the SAP document 'External Tool Integration API in Focused Build'.

In this document, the required setup is described to be able to automatically forward created incidents to the connected tool. However, when we create a ticket in the Solution Manager, this is not forwarded to Jira.

We have set up the customizing in SPRO in the following way: SAP Solution Manager -> Focused Build -> Integration -> Integrate External Tools. This is the profile that has been set up in Mapping for external Tool Integration:

The destination 'EXTERNAL TOOL' is an RFC destination, set up in SM59 in the following way:

The set-up in 'External Tool Integration' has been done like this:

We have defined a custom Profile.

In this profile, we have added a transaction type, named ZMIV (which is the transaction type for when we create incidents in Solman).

Partner function 00000001 = 'Sold-to Party'.
Now, when we create an incident of type ZMIV, this should be automatically forwarded to the destination defined in the 'External Integration Profile Mapping', which doesn't happen.

Are we missing something here? All insights are welcome.

Thanks a lot.
Dimitri

[Flowace]

It seems you've diligently followed the SAP document 'External Tool Integration API in Focused Build' for bi-directional incident management with Jira.

If incidents are not reaching Jira, check the accuracy of the 'External Integration Profile Mapping,' ensure the RFC destination ('EXTERNAL TOOL') in SM59 is active and correctly configured, confirm the 'ZMIV' transaction type association with incident creation, validate the partner function in the custom profile, and ensure seamless middleware integration.

Scrutinize system logs for error messages, consult updated SAP documentation, and consider seeking assistance from SAP support or community forums for specific version-related insights if the issue persists.