SAP PI/PO developer are normally spending a lot of time documenting what they have been making of changes. We want to make the process much simpler for the end to end development. And capture the correct information. Not just information that cannot be used.
We have created a mock prototype of a feature we are working on. We would really appreciate some input about if this fits your organization. Please share a comment or write to firstname.lastname@example.org
We have the following process.
- An incident that is triggered by the component based message alerting in SAP PI. You can easily setup rules to handle the different alerts and how to react to them.
- Then we create a ticket, which is a new concept in the IRT tool. A ticket is what you could refere to as an Incident, Change Request, Service Request or Gap. It can have a list of status like, in development, in testing or done. You will be able to configure the list and if there should be auto numbers or you have the values in a separate helpdesk system. You can create tickets without an incident if it, for instance, is a business requirement
- The ticket can get PI object assigned. So you can add any PI Repository or Repository object to the ticket, for instance, a message mapping or channel that has been changed for solving the ticket. When you look at a message mapping you can see which ticket it has been assigned to and thereby get information about why something was changed.
- Testing from the ticket. It is then possible to calculate which Interfaces/ICOs to do testing on. If you are missing some tests you can add them. And then run all the tests.
You can get more information of the future of the tool by signing up for it at http://figaf.com/irt
I have two videos about the concept. One that features the overall perspective and along with more explanation along the way.
The short direct to the point video
The long version with more explanation
You can get more information of the future of the tool by signing up to it at http://figaf.com/irt