Beruflich Dokumente
Kultur Dokumente
0 May 2012
SAP QIM is therefore a generic framework that supports you with mapping and tracking all kinds of
issues and ideas and with continuous improvement processes.
Is it portal-based
SAP QIM does not provide specific portal roles or business packages for SAP NW Portal. However, the
existing NWBC roles can be used to create portal roles via according portal functionality.
SAP_QIM_COORDINATOR => all provided applications and navigation targets and also access to
administrative functions in the productive QIM system.
SAP_QIM_ISSUE_DRIVER => all applications for creating, processing and monitoring issues and activities,
but no administrative functions.
The authorizations for executing functions in SAP QIM are specified in the roles in the transaction PFCG.
SAP QIM adheres to the standard AS ABAP authorization concept.
What kind of issues and activities can I monitor with SAP QIM?
All notification categories in SAP ERP, i.e. quality notifications, claims, service notifications, general
notifications, and maintenance notifications and related tasks.
Action-relevant audit issues from any SAP system and related actions.
Can I get on overview on all issues which are related to a distinct material or
customer, even beyond systems and applications?
Yes, according to the given selection criteria by naming the material, customer or any other object plus
the required reference system and object category, the user can receive a list of issues for these business
objects, which goes across system limits and applications.
Would it be possible to monitor also issues and related activities from other
sources than SAP ERP or even NonSAP systems?
Based on the given architecture it would be conceivable to query issues and activities within the QIM
worklists. The open interface of SAP QIM allows to incorporate further, customer-specific data via
implementation of additional services or RFCs that retrieve data from other sources.
What is the structure of an issue, and what kinds of issue types are supported?
Issues can consist of:
Reference information, attachments, business partners can be defined at any level, depending on the
structure definition in customizing.
Furthermore it is possible to define user status based on the enhancement concept of the given BOPF
framework and configuration.
In addition a connection to documents within DMS is possible by assigning these documents as reference
objects (not as attachment then).
Information activities can be used to simply bundle other activities with a distinct title. They do
not contain and status and do not require and response or confirmation, they might have a long
text for detailed description and also attachments, and they cannot be changed.
Question-based activities are simple activities that are described by a question which can also
request a response, e.g. a date, a code or a number. They can be applied for better guidance of
the processing user in order to lead them directly to a solution approach. They comprise a simple
status scheme. In most cases it is helpful to configure questions so that they will automatically
be set in process in order to allow a quick completion after provision of a response.
Extended activities allow a more detailed processing in terms of different statuses to be gone
through. Here also different people can be assigned as partners such as the activity processor,
the person who will validate it etc. Extended activities can have follow-up actions assigned that
will be executed on setting the activity in process, e.g. the creation of a related quality
notification in the connected target system for a given set of reference information. These
activities have a more comprehensive status scheme.
Activities of all categories can be defined as preparing task via activity templates, which will then be used
in the configuration of distinct issue types or when defining business rules based on different parameters
for different use cases.
You create activity templates in Customizing for a specific activity type. In the template, for example, you
can specify the type of response, you can specify follow-up actions, and set default activity properties.
Material, customer, vendor, delivery, delivery item, purchase order, purchase item, batch, quality issue,
notification, DMS document
These texts are stored in different fields and can be displayed then together (as historic texts) within the
application.
Examples are different issue descriptions or activity descriptions The text type controls the fields for entering
text when you create an issue or an activity and the fields for code and code group. Via assignment of a catalog
to a text type, you can specify the catalog as a search criterion for finding and assigning code groups and codes
for quality issues and quality activities. The text types are grouped in a text schema. In the standard system,
SAP supplies a text schema for each issue category (issue, defect, cause, and effect) and for the activity
category QIM_ACT. In the standard system, the text schemas contain a text type for entering descriptions and a
text type for entering detailed descriptions.
In SAP QIM, you can define different partner roles that are necessary when processing an issue or
activity, such as issue submitter, issue driver, interested party, or quality manager. The specific partners
for an activity or an issue are identified by business partner IDs. For this to work, business partner
master records must exist in the QIM system.
You can specify partner roles in Customizing for each issue type or activity type.
The only master data which is needed are the configuration date in terms of codes, business rules,
business partners, and activity templates.
Does SAP QIM distinguish short-term and long-term activities, also in terms of
different checks when closing an issue?
Ye, it is possible to short or long-term activities within an issue related to the given business process.
E.g. an effectiveness check is typically executed later, even after the completion of the according issue.
I.e. an issue can be completed even when long-term activities are still open.
Does SAP QIM provide predefine roles for partners to be involved in the
process?
Yes, via customizing of issue types and activity templates it is possible to preconfigure distinct roles
which might be applicable for a given process. Also via business rules partner roles and even partners
can be preplanned.
Other attachments cannot be printed with the issue, but via a mail sending option they can be
considered.
What kind of validation steps and effectiveness checks does QIM offer?
Activities as well as issues can be validated at the end of the process, meaning e.g. for a validation of one
or several activities you can define according validation or effectiveness check activities, and the result
can also be documented in the original activity as validation status.
For the issue a separate decision can be made in terms of documenting success or lack of success.
When completing an issue there can be long-term activities (e.g. those relevant for long-term
effectiveness check) still open.
Causes can be defined at issue header, defect or even cause level. Same with effects.
Some of these follow-up actions need further information as reference data, which can e.g. be
transferred from the assigned activity or even issue. The successful execution of a follow-up action can
be documented by a status but also by adding a new reference object in the according activity.
For creating an issue there is a guided activity application that allows a step-wise entering of
related information.
Based on configuration and according business rules, information is pulled automatically into the
issue, so that the user does not have to identify everything from scratch.
There can be question-based activities that lead the user via responses to a root-cause or even a
solution approach.
Analytics
In addition, SAP QIM uses the Business Context Viewer (BCV) as a generic component that enables
context-related analysis of information.
Currently there are several queries defined for analyzing issues and activities presented in the worklists,
i.e. connected with the POWL via a side panel.
These queries allow a graphical representation of KPIs or results and support also a common dashboard
for getting an overview of the current quality situation.
The more common deployment options might be to either install SAP QIM on top of a given SAP system
such as SAP ERP or any other SAP system or at least with connection with other applications.
SAP QIM requires the SAP NetWeaver 7.31 release (ABAP stack) and the business suite foundation layer.
But in terms of supporting integrated scenarios e.g. in order to link an issue to other business processes
or even drive additional steps during the course of the issue resolution in other applications, the
connection or the availability of information in the same box might be helpful.
Also in terms of monitoring the possible connection to one or more backend systems is of high benefit.
This is also the goal of the engine approach of SAP QIM to be open for all kinds of issue processes, not
only logistical ones.
Can I easily change the term issue into a term which is typically used in my
company and business, like finding?
Based on a flexible terminology redefinition, you can adapt messages, texts for redefinition object types,
and interface texts to the terminology commonly used in your enterprise. If, for example, you want to
use a different term instead of quality issue, you can replace this term at the specified places. You set up
terminology redefinition in Customizing for QIM under Environment Redefine Terminology. Here, you
can create different variants of the terminology redefinition and then store them as user parameters in
the user master record or as application parameters in the role.
Personalization is done by individual users. The adaptations are only relevant for these users.
Customizing is done by an administrator with the appropriate authorization and is for the whole
client in a system.
Which settings exactly are possible depends on whether a page (for example, a work center) or an
application is to be adapted.