Skip to Content
Product Information
Author's profile photo Lorenz Moehl

Simple IT Request: New features with Focused Build SP02

In this blog post, I would like to give you an overview of new features of the Simple IT Request included in Focused Build SP02.

Besides continual performance improvements and overall stabilization, we focused on developing the following three core features:

  • Support for standard transaction types – enhancing our multiple input channel concept
  • New transaction type for an approval-based Service Request – fully integrated in Fiori MyInbox
  • Rich text support – enabling end users to create requests in an even more convenient way

Before going into detail, I would like to point you to my colleague’s blog post about Simple IT Request in general. If you’re looking for a general overview, Stefans post is the right place to start: Simple IT Request – Focused Build Standalone Extensions Part 3. And now let’s focus on the new features of the Simple IT Request with Focused Build SP02:

Support for standard transaction types

One of the Simple IT Requests main advantages is providing a single input-channel for the end users to consume any kinds of IT-Services. Due to personal preferences, business requirements or technical limitations it is still possible to use other input-channels than the Service-Catalog. SP02 now brings you the functionality to have all your IT-Requests source-independent centralized in the MyRequest App.

Approval-based Service Request

With SP02, we introduced a new transaction type pair: S4AT & S4RQ. Based on the standard Service Requests and its corresponding template, this pair provides the possibility to approve Service Requests. An additional partner function for the approver was introduced and the transaction workflow was adapted respectively.

Approvals can be done in CRM UI or within the Fiori App MyInbox. By minimizing the Approvers time-effort and centralizing your processes, the MyInbox integration offers another advantage of the Simple IT Request.

Support for Rich Texts

Since Solution Manager 7.2 SP6, you have the possibility to maintain formatted text and even include inline screenshots. This being a massive improvement for any Solution Manager user, we adapted both Simple IT Request Apps to fully support Rich Texts as well.

Despite being a great feature, the Rich Text configuration comes with some additional effort in customizing and coordinating with CRM UI.

Essential prerequisite is to activate Rich Text formatting for each text type used in the Simple IT Request. My suggestion is to activate formatting for every text-type in the specific text determination procedures. This ensures a consistent way of maintaining texts, either in Simple IT Request or in CRM UI.

Please refer to Gordons blog-post for activating Rich Text formatting in CRM UI:SAP Solution Manager 7.2 IT Service Management – Text with Inline Screenshots.

The detailed configuration guide and additional information regarding Focused Build can be found under following link: Focused Build for SAP Solution Manager

If you have any questions or input, please feel free to comment and share!

 

Assigned Tags

      6 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Consultants Consultant
      Consultants Consultant

      Hi Lorenz,

      Thanks for the blog, I have configured the simple IT request setup and having issue in the fields setup.

      1. I want to bring custom fields into my service request.
      2. Fields are getting disabled when I save the request template, below is the screenshot of the same.
      3. Also in the app, category view is not displaying but the list view is appearing with no fields.

      We are in ST 720 SP07 with OST SP02 version only.

      Check the screenshots. It is weird.

       

       

      Author's profile photo Lorenz Moehl
      Lorenz Moehl
      Blog Post Author

      Hi,

       

      did you activate both Piecelists for SP1 (/SALM/SIMPLE_IT_REQ) and SP2 (/SALM/SITR_SP02)? Additionally you can check for Gateway errors in transaction /IWFND/ERROR_LOG and the console in the developer tools of your browser.

      Otherwise it's hard to tell without system access. If possible you can open an incident (component SV-SMG-OST) and I'll take a look at this.

       

      Best regards,

      Lorenz Möhl

      Author's profile photo Consultants Consultant
      Consultants Consultant

      Hi Lorenz,

      I have activated all the piece list as per the document for SP02, still issues are there.

      I have raised incident 3 days back, no one has replied yet. Can you check this incident "163165" and update me on the incident, I am trying to get an update since 3 days back, no one is replying on this.

      Can you support on this,  we are struck with this app.

       

      Author's profile photo Marjan PARSA
      Marjan PARSA

      Hello, is it possible to have 2 different transactions types for simple it request and to custom the actions?

      Best Regards

      Author's profile photo Lorenz Moehl
      Lorenz Moehl
      Blog Post Author

      Hi,

       

      Simple IT Request offers 2 Applications. The Catalog App is used to create requests. Here every template transaction (e.g. S4IT for Incident Templates) can only create one specific transaction type (e.g. SMIN for Incidents). The second Application is the MyRequests App. Here comes the 'Support for standard transaction types' feature in handy, as explained in my blog post. You can monitor all transaction types used in ITSM. You just need to adapt the customizing to your needs.

      In regards to the Actions: You can customize the source and target status, as well as Button type and label. This is done is customizing activity 'Customizing of Activities for My Requests App'.

       

      Best regards,

      Lorenz Möhl

      Author's profile photo Martha Griggs
      Martha Griggs

      I think that the introduction of the S4AT & S4РК system was a very important step. For me, as a leader, it is very important to monitor the progress of my team and agree (or disagree) some issues that relate to our common work. And, of course, thanks for the options for optimizing and editing text)
      Hope you continue to improve the quality of SP02.