SAP QIM

SAP Quality Issue Management (SAP QIM) PDF download from SAP Help Portal: http://help.sap.com/saphelp_qim100/helpdata/en/26/d50f49b6a54a37839e4326987edeb1/frameset.htm Created on March 21, 2015

The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.

Note This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.

© 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

Table of content

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 1 of 106

Table of content 1 SAP Quality Issue Management (SAP QIM) 1.1 What's New in SAP QIM 1.0 1.1.1 Support Package 5 1.1.1.1 End of Purpose Check for Personal Data 1.1.1.2 Flexible Search Helps for Quick Access to Quality Issues 1.1.2 Support Package 4 (Feature Pack 2) 1.1.2.1 Flexible Selection Options in Worklist 1.1.2.2 BAdIs for Pushbuttons in Worklist 1.1.2.3 BAdI for Date Calculation in Activities 1.1.2.4 Search for Activity Data Using Enterprise Search 1.1.2.5 Basic Search in Issue Long Texts 1.1.2.6 Archiving of Activities and Issues 1.1.2.7 Customer-Specific Field Control 1.1.2.8 Enhanced Definition and Assignment of Reference Objects 1.1.2.9 Side Panel for Applications for Processing Issues and Activities 1.1.2.10 Workflow for Notification of New Issues 1.1.2.11 Problem-Solving Process Using 8D Methodology 1.1.2.12 Adaptation Options for the User Interface 1.1.2.13 QIM-Specific CHIP for Quick Access to Quality Issues 1.2 Use of SAP QIM 1.2.1 Connection of Systems in a Side-by-Side Scenario 1.3 Worklists for Quality Issues and Quality Activities 1.3.1 Selection Criteria 1.3.2 Layout 1.3.3 Definition of Queries 1.3.3.1 Selection According to Calculated Dates 1.3.3.2 Selection According to Variable User or Business Partner 1.3.4 Structure Mapping 1.3.5 Jumps 1.3.6 Additional Information 1.3.7 Status Change 1.3.8 Monitoring Control of Issues and Activities 1.4 Issue Processing 1.4.1 Overview: Creating Quality Issues 1.4.1.1 Create Quality Issue (Quick) 1.4.1.2 Create Quality Issue (Guided) 1.4.1.3 Create Quality Issue (Advanced) 1.4.1.4 Issue Status 1.4.1.4.1 Status Profile for Issues 1.4.2 Changing of Quality Issues 1.4.3 Subitems: Defect, Cause, Effect 1.4.4 Quality Activities 1.4.4.1 Activity Templates 1.4.4.1.1 Proposed Activity Templates 1.4.4.2 Determination of Activities Using BRFplus 1.4.4.3 Determination of Partner for Activities Using BRFplus 1.4.4.4 Transfer of User Data for Activity Driver/Completed By for Activ 1.4.4.5 Activity Status 1.4.4.5.1 Status Profile for Extended Activities 1.4.4.6 Definition of Follow-Up Actions 1.4.5 Settings Dependent on the Text Type 1.4.6 Codes and Code Groups 1.4.6.1 Determination of Codes and Code Groups Using BRFplus 1.4.7 Partners 1.4.7.1 Partner Roles 1.4.7.2 Partners in a QIM Issue 1.4.7.2.1 Transfer of User Data for Issue Submitter 1.4.7.3 Determination of Partner for Issues Using BRFplus 1.4.8 Reference Objects 1.4.8.1 Reference Objects for Issue Types

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 2 of 106

1.4.8.2 Reference Objects for Activity Templates 1.4.9 Printing of Issues or Activities 1.4.10 E-Mailing of Issues or Activities 1.4.11 Additional Information in Side Panel 1.4.12 Change Documents 1.4.13 Workflow Scenarios for Issue Processing 1.4.13.1 Technical Implementation 1.4.14 Issue Processing with Digital Signatures 1.4.15 Problem Analysis Using 8D Methodology 1.4.15.1 8D: Technical Implementation 1.4.15.2 8D Report 1.5 System Administration Work Center 1.5.1 Process Control 1.5.2 Configure Rules 1.5.3 Communication with External Systems 1.5.4 Audit Trail 1.5.5 Environment 1.5.6 System Settings for Reporting 1.6 Enterprise Search 1.7 Reports 1.7.1 Reports in Business Context Viewer (BCV) 1.7.1.1 Example: BCV Query via BAPI Search Connector 1.7.2 Reports Using Search and Operational Analytics 1.7.3 Reports for Related Issues or Defects 1.7.4 Reports in Other Systems 1.8 Technical System Integration 1.8.1 ID Mapping 1.8.2 Setting Up System Connections 1.9 User Interface Adaptation 1.9.1 Adaptation of the Role Menu 1.9.2 Adaptation of the QIM Work Centers 1.9.2.1 Launchpads in QIM 1.9.3 Adaptation of the Web Applications in QIM 1.9.3.1 Context-Based Adaptation of QIM Web Applications 1.9.3.2 Adaptation Using Field Control 1.9.4 Terminology Redefinition 1.9.5 User Status 1.9.6 Web Dynpro Personalization and Customizing 1.9.7 Web Dynpro Configuration 1.10 Roles in SAP Quality Issue Management 1.10.1 Coordinator 1.10.2 Issue Driver 1.10.3 Authorizations 1.10.4 Generation of Portal Roles 1.11 System Architecture 1.12 Sequence of Configuration Steps in SAP QIM 1.13 Search and Operational Analytics: Content for SAP QIM 1.13.1 Search and Analytics Models 1.13.1.1 Issue 1.13.1.2 Defect 1.13.1.3 Cause 1.13.1.4 Effect 1.13.1.5 Issue Attachment 1.13.1.6 Activity 1.13.1.7 Activity Attachment 1.13.1.8 ODP for Issue and Subissue 1.13.2 TransientProviders 1.13.2.1 QIM Issues 1.13.3 DataSources 1.13.3.1 QIM Issues 1.13.4 Content Objects in Software Component IAM 1.13.4.1 Content Objects for Customizing in IAM

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 3 of 106

1.14 Archiving QIM Data 1.14.1 Archiving Activities with /IAM/ACT 1.14.1.1 Checks for /IAM/ACT 1.14.1.2 Creating Preprocessing Variants for /IAM/ACT 1.14.2 Archiving Issues with /IAM/ISSUE 1.14.2.1 Checks for /IAM/ISSUE 1.14.2.2 Creating Preprocessing Variants for /IAM/ISSUE 1.14.3 Setting Up Application-Specific Customizing 1.14.4 Displaying Archived QIM Data

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 4 of 106

1 SAP Quality Issue Management (SAP QIM) Product Information Product

SAP QIM

Release

1.0 SP05

Based On

SAP enhancement package 3 for SAP NetWeaver 7.0 SP05

Documentation Published

August 2014

See SAP Note 2015336 for corrections that are made after the documentation has been delivered.

More Information For more information about cross-application components that are relevant for SAP QIM, see: SAP NetWeaver by Key Capability Processes and Tools for Enterprise Applications SAP NetWeaver Information Lifecycle Management

1.1 What's New in SAP QIM 1.0 In this structure, you will find information about new features in SAP QIM 1.0 as of Support Package 4. You will find the Release Notes for previous Support Packages as usual on SAP Service Marketplace under Solutions SAP Quality Issue Management and in the QIM system under Help Release Notes .

http://service.sap.com/releasenotes

SAP

1.1.1 Support Package 5 1.1.1.1 End of Purpose Check for Personal Data You can specify the end of purpose for personal data in SAP QIM. This means that the end of purpose check using SAP Information Lifecycle Management (ILM) also takes into account the personal data stored in SAP QIM. Personal data can be assigned partners in the QIM system that are stored in the system as SAP business partners. Personal data can also be customers and vendors in connected ERP systems that you have assigned as reference objects.

Technical Details Technical Name of Product Feature

QIM_105_EOP

Product Feature Is

New

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Available as of

SAP QIM 1.0 SP05

Required Business Functions

Information Lifecycle Management (ILM)

Effects on Existing Data This product feature allows you to control the deletion and blocking of the business partner master data used in SAP QIM by means of the component SAP Information Lifecycle Management (ILM). The personal data stored in the business partner master data can be blocked if the business activities for which the master data is required are completed and the residence time for this data has expired. After this, only those users who have additional authorization can access this data. Once the retention period has also expired, the blocked personal data can be destroyed so that it is irretrievable.

Effects on Customizing For information about how you define the end of purpose for personal data in SAP QIM, see Customizing for QIM under for Personal Data .

Environment

Define End of Purpose

More Information Section

Security Information

Data Protection

in the Administrator's Guide for SAP QIM, available on SAP Service Marketplace under

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 5 of 106

http://service.sap.com/instguides

SAP Business Suite Applications

SAP Quality Issue Management

1.1.1.2 Flexible Search Helps for Quick Access to Quality Issues In the QIM_QUICK_ACCESS CHIP for quick access to quality issues, defects, effects, and causes, it is possible to include flexible search helps. If you use Enterprise Search in SAP QIM, this is also integrated in the quick access so you can run a free text search.

Technical Details Technical Name of Product Feature

QIM_105_QUICKACCESS_SEARCH

Product Feature Is

Changed

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Available as of

SAP QIM 1.0 SP05

Effects on System Administration To include a search help, open the Quality Issues page in Customizing mode (see also Adaptation of the QIM Work Centers). Then choose Configuration Settings in the setup menu of the CHIP and assign the search help.

More Information QIM-Specific CHIP for Quick Access to Quality Issues

1.1.2 Support Package 4 (Feature Pack 2) 1.1.2.1 Flexible Selection Options in Worklist When you define queries for worklists for issues and activities, you can use flexible selection options by means of variables for the business partner or user or by having the system calculate dates.

Technical Details Technical Name

QIM_104_POWL_SELECTION

Product Feature Is

New

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Availability

SAP QIM 1.0 SP04

More Information Selection According to Variable User or Business Partner Selection According to Calculated Dates

1.1.2.2 BAdIs for Pushbuttons in Worklist With two new Business Add-Ins (BAdIs), you can define your own pushbuttons in the worklists for issues and activities and thus, for example, implement your own print or export function.

Technical Details Technical Name

QIM_104_BADI_POWL

Product Feature Is

New

Country Dependency

Valid for all countries

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 6 of 106

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Availability

SAP QIM 1.0 SP04

Effects on Customizing You will find the BAdIs in Customizing for QIM under Worklists .

Worklists for Quality Issues and Activities

Business Add-Ins (BAdIs) for Enhancement of Lists of

1.1.2.3 BAdI for Date Calculation in Activities You can use this BAdI to calculate one or more timepoints for one or more activities. For example, you can use it to automatically calculate an expected end date of an activity from an expected start date entered for this activity using the duration maintained for the corresponding activity template in the Customizing settings. An example implementation is delivered for this use case.

Technical Details Technical Name

QIM_104_BADI_ACTVTY

Product Feature Is

New

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Availability

SAP QIM 1.0 SP04

Effects on Customizing You will find the BAdI in Customizing for QIM under information, see the documentation for the BAdI.

Issue Processing

Business Add-Ins (BAdIs)

BAdI: Date Calculation for Activities

. For more

1.1.2.4 Search for Activity Data Using Enterprise Search With the search for activity data in Enterprise Search, it is possible to make data for QIM issues and QIM activities available to the Enterprise Search component of SAP NetWeaver Application Server ABAP, also known as Embedded Search. This means that you can search across all structured data of the objects listed above in the system in which you are running SAP QIM.

Technical Details Technical Name

QIM_104_ESH_ACT

Product Feature Is

New

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Availability

SAP QIM 1.0 SP04

Effects on Customizing You set up the search for quality activities in Customizing for QIM under

Search and Analytics

Configure Search

.

More Information Search and Operational Analytics: Content for SAP QIM

1.1.2.5 Basic Search in Issue Long Texts When searching for QIM issues, defects, causes, and effects using the basic search in Embedded Search, the long texts of the objects are now also included in the search.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 7 of 106

Technical Details Technical Name

QIM_104_ESH_ISS

Product Feature Is

Changed

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Availability

SAP QIM 1.0 SP04

Effects on Existing Data The relevant delivered search models were therefore changed. To be able to use the modification, you must regenerate the connectors.

1.1.2.6 Archiving of Activities and Issues Using archiving, you can export data that you no longer require in the system, but need to retain for documentation purposes, for example, to an archive file and thus free up space in the database. The following archiving objects are delivered: /IAM/ACT for archiving QIM quality activities with the corresponding data /IAM/ISSUE for archiving QIM quality issues with the corresponding data

Technical Details Technical Name

QIM_104_ARCH

Product Feature Is

New

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Availability

SAP QIM 1.0 SP04

Effects on Existing Data After archiving, the data can be displayed but no longer changed.

Effects on System Administration You can access all archiving functions, and Customizing and the documentation for the QIM archiving objects, in archive administration (transaction SARA). Archive administration can also be accessed from the QIM work center System Administration . To open the documentation for the archiving objects, enter the technical name of the archiving object in archive administration and choose Goto -> Documentation .

More Information Archiving QIM Data

1.1.2.7 Customer-Specific Field Control You can store a customer-specific field control for the Web Dynpro applications for processing issues and activities. This allows you, for example, to define certain input fields as required-entry fields or show them in display mode. As field control directly affects the BOPF node, no influence on the interface is necessary using context-based adaptations (CBAs) of the Web Dynpro applications.

Technical Details Technical Name

QIM_104_FIELD_CONTROL

Product Feature Is

New

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 8 of 106

Availability

SAP QIM 1.0 SP04

Effects on Existing Data The general field control in BOPF for the business object overrides the customer-specific settings for field control. For example, in a completed issue all fields are shown in display mode, regardless of the settings for field control.

Effects on Customizing You make the settings for field control in Customizing for QIM under documentation for the Customizing activity.

Environment

Define Field Control

. For more information about the procedure, see the

1.1.2.8 Enhanced Definition and Assignment of Reference Objects You have the following enhanced options when defining reference objects in Customizing and when assigning reference objects to issues or activities: You can define several reference objects without a fixed technical reference to an SAP system by copying the delivered object type External reference object (GOJ) and adapting the copy accordingly. For more information about the procedure, see SAP Note 1820834. The new object type Storage location (STL) is delivered as an example of an object type copied in this way. You can define and assign a search help for the object type External reference object (GOJ) and for the copies of the object type GOJ you create yourself. For more information about the procedure, see SAP Note 1909219. You can adapt the search dialog box for existing reference objects, for example, by adding additional search helps or hiding existing search helps. For more information about the procedure, see also SAP Note 1909219. You can select several objects at once when assigning reference objects.

Technical Details Technical Name

QIM_104_REF_OBJ

Product Feature Is

New

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Availability

SAP QIM 1.0 SP04

Effects on Customizing You make the settings for the object types for reference objects in Customizing for QIM under Basic Settings Generic Settings for Reference Objects Define Object Types . A new column for the assignment of a search help is only ready for input for the object type GOJ and its copies.

1.1.2.9 Side Panel for Applications for Processing Issues and Activities The side panel for applications for issue and activity processing allows the display of various Web Dynpro CHIPs that relate to the object being displayed or processed in the main application. You can open the side panel when creating issues or activities using the advanced create function, or when processing or displaying issues and activities, using the link Additional Information . When processing issues, the following CHIPs are available: The generally available CHIP Notes for adding public or private notes about the current object The new QIM-specific CHIP Related Issues or Subissues that shows in graphical form which other issues or defects exist with the same reference objects or the same code When processing activities, you can only add notes.

Technical Details Technical Name

QIM_104_SIDEPANEL

Product Feature Is

New

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Availability

SAP QIM 1.0 SP04

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 9 of 106

Effects on Customizing You can make other CHIPs available in the side panel. To do this, you can use a new Business Add-In that you can find in Customizing for QIM under Processing Business Add-Ins (BAdIs) BAdI: Enhancement of QIM Web Dynpro Applications .

Issue

More Information Additional Information in Side Panel Reports for Related Issues or Defects

1.1.2.10 Workflow for Notification of New Issues With the workflow for notification of new issues, it is possible to inform the issue driver when an issue is reported that he or she needs to process. New workflow objects are delivered for this, for example: Workflow template 56900008 Standard task 56907941

Technical Details Technical Name

QIM_104_WORKFLOW

Product Feature Is

New

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Availability

SAP QIM 1.0 SP04

Effects on Customizing For information about how you activate the new workflow, see Customizing for QIM under

Environment

Activate Workflow

.

1.1.2.11 Problem-Solving Process Using 8D Methodology You can map problem-solving processes using 8D methodology in SAP QIM. New functions and new content are delivered for this. The new functions also allow you to define the content for other problem-solving methodologies yourself. The new functions include the following: Customizing activities to divide a QIM issue into steps (or phases). As part of the scope of content for 8D, eight steps are delivered for the eight disciplines. The option of defining a follow-up issue for a QIM issue. Within the scope of the content delivered for 8D, it is possible to create an 8D problem analysis from a defect (for example, for a customer complaint). The option of assigning a specific Web Dynpro application configuration to an issue type. Within the scope of the content for 8D, a new issue type for 8D problem analyses (Q8D) and the application configuration QIM_OVP_8DISS are delivered. This application configuration depicts the 8D steps on the interface and also permits the following: You can create immediate containment actions in step D3 using a quick entry function. You can copy activities from step D5 to step D6. You can influence the copy process using a new Business Add-In (BAdI). You can enter the percentage contribution of different causes for a defect. You can assign the validation status Effectiveness Check Outstanding , enter the effectiveness of an activity in percent, and store a free text for the verification of the result. The option of selecting according to steps in the worklist for activities. A special print form (I8D) for printing or e-mailing an 8D report, to which the new PDF-based form QAM_ISSUE_8D is assigned in Customizing. The option of combining several 8D reports (one 8D report for each defect for which the problem analysis is relevant) in one PDF document for printing or emailing.

Technical Details Technical Name

QIM_104_8D

Product Feature Is

New

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Availability

SAP QIM 1.0 SP04

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 10 of 106

Effects on Existing Data New validation status for activities: Effectiveness Check Outstanding

Effects on System Administration Adapt your PFCG roles as described in SAP Note 1994956.

Effects on Customizing The Customizing settings for the issue types were enhanced. For example, there is a new column for the assignment of an issue type-specific Web Dynpro application configuration. You can also make settings for follow-up issues. For more information, see the documentation for the Customizing activity in Customizing for QIM under Issue Processing Define Issue Types . In Customizing, there are also new activities for defining the steps of a problem-solving process (under Issue Processing Problem-Solving Methodologies ). You can use the Customizing content delivered for 8D by activating the BC Set. You do this in Customizing for QIM under Issue Processing ProblemSolving Methodologies Activate BC Sets for 8D . You will find the BAdI for influencing the copy process for activities in Customizing for QIM under Issue Processing Business Add-Ins (BAdIs) BAdI: Influence Copying of Activities . In Customizing for the print forms, there is a new Defect Selection indicator, which you can use to specify that individual defects of an issue can be selected in the dialog box for printing or e-mailing issues.

More Information Problem Analysis Using 8D Methodology

1.1.2.12 Adaptation Options for the User Interface In addition to the existing enhancement options, you have other options for adapting the Web user interfaces for the processing of QIM issues and QIM activities: You can assign a specific Web Dynpro application configuration to an issue type. This allows you to vary the user interface for the processing of issues of an issue type without context-based adaptations. For issue processing or problem analysis, you can define steps and make settings for them. You can use these step settings in your issue type-specific Web Dynpro application configurations. As an application example, the Web Dynpro application configuration QIM_OVP_8DISS is delivered for the processing of 8D problem analyses. You can enter follow-up issue types for an issue type. This function is relevant when processing defects for a QIM issue. If issue types for follow-up issues are stored in Customizing, the Trigger Problem Analysis pushbutton appears automatically on the user interface. In the table for defects, you can add new columns from the column set with the information relating to the follow-up issues. You can include a new field in the Web Dynpro component configuration for processing causes in which you can enter the percentage contribution of the causes to a defect. As an application example, the Web Dynpro component configuration QIM_OVP_8DISS_CAUSE_OVERVIEW is delivered. You can include a new field in the Web Dynpro component configuration for activity details in which you can enter the effectiveness of an activity in percent. You can also include a field for storing a free text for the verification of the result. As an application example, the Web Dynpro component configuration QIM_OVP_8DISS_ACT_OVERVIEW is delivered. You can include a pushbutton for copying activities. As an application example, the Web Dynpro component configuration QIM_OVP_8DISS_D50_ACTIVITY_TREE is delivered. You can influence the copy process using the new Business Add-In (BAdI) /IAM/BADI_COPY_ACTIVITY. If you set the relevant indicator in Customizing for print forms, it is possible to select individual defects when printing or e-mailing issues. For the easy capturing of a number of activities, for example, for a question catalog, you can include a UIBB that is based on the FPM form repeater component and uses the delivered FPM feeder class /IAM/CL_ACTIVITY_FORMRP_FEEDER. As an application example, the Web Dynpro component configuration QIM_OVP_8DISS_D30_ACTIVITY_FRMRP is delivered for the creation of 8D containment actions.

Technical Details Technical Name

QIM_104_UI_ADAPT

Product Feature Is

New

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Availability

SAP QIM 1.0 SP04

Effects on Existing Data If you adapt the Web Dynpro configurations centrally, users may have to reset their personalization for the central changes to become visible.

Effects on System Administration PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 11 of 106

If you assign a specific Web Dynpro application configuration to an issue type, you must adapt your PFCG roles as described in SAP Note 1994956.

Effects on Customizing The Customizing settings for the issue types were enhanced. For example, there is a new column for the assignment of an issue type-specific Web Dynpro application configuration. You can also make settings for follow-up issues. For more information, see the documentation for the Customizing activity in Customizing for QIM under Issue Processing Define Issue Types . In Customizing, there are also new activities for defining the steps of a problem-solving process (under Issue Processing Problem-Solving Methodologies ). You will find the BAdI for influencing the copy process for activities in Customizing for QIM under Issue Processing Business Add-Ins (BAdIs) BAdI: Influence Copying of Activities . In Customizing for the print forms, there is a new Defect Selection indicator, which you can use to specify that individual defects of an issue can be selected in the dialog box for printing or e-mailing issues.

1.1.2.13 QIM-Specific CHIP for Quick Access to Quality Issues To allow easier access to subitems of a QIM quality issue (defects, effects, and causes) and to improve performance, the generic quick-access CHIP was replaced by the QIM-specific CHIP QIM_QUICK_ACCESS.

Technical Details Technical Name of Product Feature

QIM_104_QUICKACCESS

Product Feature Is

Changed

Country Dependency

Valid for all countries

Software Component Version

QAM

Application Component

CA-IAM-QIM (Quality Issue Management)

Available as of

SAP QIM 1.0 SP04

Effects on Existing Data To include the new CHIP, the delivered application configuration QIM_CHIP_PAGE_ISSUES was changed for the page for opening quality issues.

Effects on System Administration If you used Customizing to redefine the page for opening quality issues or the generic CHIP for quick access, you may have to make your changes again after you install the support package. Users may also have to reset their personalization so that the central changes become visible.

1.2 Use of SAP QIM SAP Quality Issue Management (SAP QIM) offers you the option of capturing various types of quality issues, processing them by initiating suitable quality activities, and monitoring the processing status throughout the resolution process. The application thus supports the entire issue resolution process from issue capturing to issue resolution and a final validation. You can also map use cases that go beyond classical quality management, such as improvement requests or service requests. 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. You can integrate different SAP systems and – with the help of the open interfaces supported by ABAP systems – also integrate non-SAP systems. SAP QIM thus offers you the following advantages: Integrated solution and a central point of access for processing and monitoring quality issues, also from other applications and systems (for example, FMEA, audits, quality notifications, claims) Intuitive usability owing to a Web-based, customizable user interface Standardized and efficient processes for issue processing, for example, rule-based determination of partners, codes, and activities Comprehensive analytical functions that reach beyond application and system boundaries Transparent documentation of the issue handling process and thus better cost control With SAP QIM, you can map the capturing and processing of quality issues in one end-to-end process. For example, you can do the following: Access quality issues and quality activities using role-based worklists Create new quality issues, define quality activities, and determine responsible partners Use terminology to fit your requirements thanks to the adaptable user interface Determine partners, codes, and activities automatically (based on rules) at the level of quality issue and quality activity Display quality issues in hierarchy form Check the effectiveness of the quality activities initiated (own status) Create quality activities quickly and efficiently using activity templates Use the wide range of issue and activity types provided Use activity templates to create quality activities more quickly Request a response from the issue or activity driver depending on the quality issue type or activity type

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 12 of 106

Map the problem-solving process using 8D methodology

Implementation Considerations You should install this component if you want to capture quality issues within one system or across different systems, process them efficiently, and document the process clearly and transparently. You can use SAP QIM in the following scenarios: Standalone: SAP QIM as a standalone solution Add-on: SAP QIM as an add-on solution to an existing system, for example, SAP ERP In this variation, SAP QIM and SAP ERP run on the same system. The master data and organizational data in SAP ERP is available as a basis. Side-by-side: SAP QIM as a standalone solution parallel to an existing system In this variation, SAP QIM and SAP ERP run on separate systems. The systems communicate via RFC connections or services. For more information, see Connection of Systems in a Side-by-Side Scenario.

More Information System Architecture Administrator's Guide for SAP QIM (on SAP Service Marketplace under Quality Issue Management )

https://service.sap.com/instguides

SAP Business Suite Applications

SAP

Features Using the various adaptable work centers in SAP NetWeaver Business Client, you have access to exactly those applications and functions that you require to perform your tasks: Home Get an initial overview of the existing issues and activities. The home page provides an overview of the Worklists for Quality Issues and Quality Activities. There, you can get an overview of the urgency of unresolved quality issues and activities, for example. A graphic shows an analysis of the number of quality issues by priority and status. Using Enterprise Search, you can search for issues. Inbox Access work items, alerts, and notifications directly. For more information, see Inbox (CA-EPT-IBO). Worklists Create personal worklists for existing quality issues and quality activities of different origins (for example, quality notifications, audit questions, claims) to be able to coordinate and monitor their processing. You can sort issues and activities according to their status, for example. The worklist provides you with a central point of access for objects from different source systems. For more information, see Worklists for Quality Issues and Quality Activities. Quality Issues Create new quality issues and process existing quality issues. For example, you can access a specific quality issue directly or search for quality issues. Several applications are available for creating new issues. For more information, see Overview: Creating Quality Issues. Quality Activities Create new quality activities for a quality issue and process existing quality activities. For example, you can access a specific quality activity directly or search for quality activities. For more information, see Quality Activities. System Administration Access comprehensive process control and configuration functions. For example, you can create and process catalogs, access decision tables for rulebased determination of activities, partners, and codes using BRFplus, and control communication with external systems. For more information, see System Administration Work Center. Reports Use comprehensive analytics options. You can, for example, display all quality issues resolved within a specific time period or analyze quality issues and quality activities according to different criteria. For more information, see Reports. You have a wide range of options for adapting the delivered structure of the work center and the interfaces in the applications to fulfill the requirements of your enterprise. For more information, see User Interface Adaptation.

1.2.1 Connection of Systems in a Side-by-Side Scenario To use the advantages of SAP QIM to the full, a typical scenario is the installation of SAP QIM as a separate solution to which you can connect various existing systems, such as SAP ERP systems, via RFC connections or services. You can integrate objects from other systems by including them in the worklists for issues and activities or by assigning them as reference objects to a QIM quality issue or a QIM quality activity.

Features You can integrate the following SAP ERP objects as of the specified releases: Worklists Object

General notification

As of SAP ERP 4.6C

As of enhancement package 6 for SAP

ERP 6.0

ERP 6.0

X

General notification item

X

General notification task

X

Service notification

X

Service notification item

As of enhancement package 5 for SAP

X

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 13 of 106

Service notification task

X

Quality notification

X

Quality notification item

X

Quality notification task

X

Maintenance notification

X

Maintenance notification item

X

Maintenance notification task

X

Claim

X

Claim task

X

Action-relevant audit question

X

Audit action

X

FMEA defect item

X

FMEA action

X

Note For more information about the integration of the objects in the worklists (for example, about constraints and the remote POWLs that are used for access), see Customizing for object access under Worklists for Quality Issues and Activities ( Implementation Information ) pushbutton.

, then under the settings for object categories using the

Reference objects Object

As of SAP ERP 4.6C

General notification

X

Service notification

X

Quality notification

X

Maintenance notification

X

Maintenance order Claim

As of enhancement package 5 for SAP ERP 6.0

As of enhancement package 6 for SAP ERP 6.0

X X

Action-relevant audit question

X

FMEA defect item

X

Batch

X

Customer

X

Outbound delivery

X

Outbound delivery item

X

Document

X

Equipment

X

Functional location

X

Storage location

X

Plant

X

Purchase order

X

Purchase order item

X

Material in ERP

X

Material in NW (product) Vendor

X X

Note For more information about the integration of the objects (for example, about constraints and the BAPIs that are used for access), see Customizing for object access under Basic Settings Generic Settings for Reference Objects Define Object Access , then under the settings for categories using the ( Implementation Information ) pushbutton. If you want to connect to an object from a system with different release level, you can check whether the function modules listed are available in your system. For more information about how you add additional reference objects yourself, see SAP Note 1820834.

More Information Technical System Integration Setting Up System Connections

1.3 Worklists for Quality Issues and Quality Activities PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 14 of 106

1.3 Worklists for Quality Issues and Quality Activities To get an overview of existing quality-related issues and activities in different systems and applications, you can create worklists in QIM based on various selection criteria. This provides you with a harmonized overview from which you can jump to the various systems. The worklist draws together objects from the QIM system itself and from connected SAP systems and non-SAP systems.

Integration The worklist provides you with a central point of access for objects from different source systems. These objects include the following: Quality issues, defects, and quality activities from an SAP QIM system (see also Issue Processing) Quality notifications, quality notification items, and quality notification tasks from an SAP ERP system General notifications, notification items, and general notification tasks in an SAP ERP system Service notifications, service notification items, and service notification tasks from an SAP ERP system FMEA defect items and FMEA actions in an SAP ERP system Maintenance notifications, maintenance notification items, and maintenance notification tasks from an SAP ERP system Claims and claim tasks in an SAP ERP system Action-relevant audit questions and audit actions in an SAP system To facilitate the view across all systems, the objects in QIM were decoupled from a specific data model. For each source system object, for example, quality notification item, there is an object category in QIM. In Customizing, you specify for each object category which system is to be used to read the data. A structure mapping is stored for each object category. For more information about the technical integration of the objects, see Technical System Integration.

Prerequisites You have made the following settings in Customizing under Activities to call up worklists correctly:

Cross-Application Components

Quality Issue Management

Worklists for Quality Issues and

Settings to access quality issues and quality activities Settings for assigning authorizations in the POWL cockpit If you wish, you can also make other settings in Customizing, for example, for the monitoring control of quality issues. For more information about the enhancement of worklists in QIM, see SAP Note 1865206.

Activities 1. 2. 3. 4. 5. 6. 7. 8. 9.

You create a new worklist under New Worklist . Here, you can specify the selection criteria for the list of worklists. You change the selection criteria for a worklist under Change Worklist if you have authorization to do this. You change the layout of a worklist under ( Open Settings Dialog ). You can display and print the displayed list of worklists in PDF format (under Print Version ). You can export the displayed list of worklists to Microsoft Excel (under Export ). You can open the object in the respective row of the worklist and its reference objects in the source system via links (see Jumps). For one or more rows in the worklist, you can display additional information, for example, about the underlying object category. You can make a status change for several rows simultaneously and thus set a number of issues in process, for example. To improve monitoring, you can show a traffic light in the worklist for a monitoring control of issues and activities. The monitoring control is possible, for example, according to status or according to the requested start and end date.

10. You can change the layout of the worklist page, by grouping, deleting, or renaming the worklists, for example. To do this, choose

( Personalization ).

1.3.1 Selection Criteria When you create or change a worklist, you specify the selection criteria for the issues or activities to be listed.

Features The most important selection criterion for a worklist is the object category. All other entries for the selection criteria depend on which object category you have selected. A worklist for quality notifications, for example, requires different entries - in particular for the issue ID - than a worklist for FMEA defect items. In combination with the object category, the source system is mandatory for the selection. To improve performance when selecting entries, you can specify the maximum number of hits to be displayed in the result list for the combination of source system and object category. You should make your entry dependent on the capacity of the respective source system. To get a harmonized view in a list with different source systems and different object categories, the following selection criteria are particularly important: Issue Type So a user can select all issue types from various systems in the same manner in his or her worklist, you can store a list of issue types across all systems and, if necessary, a mapping in Customizing. For more information, see Customizing for QIM under Worklists for Quality Issues and Activities Define Access to Quality Issue Types . Status For a selection of the status of issues and activities across all systems, some statuses are automatically converted by the system. This conversion is stored in Customizing for the object category in a structure mapping.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 15 of 106

Activities 1. You create a worklist for the combination of object category and source system (multiple selection is also possible). Here, you can specify the number of hits displayed per combination. 2. In addition, you can restrict the worklist using other selection criteria and thus list only those quality issues, for example, for which a specific user is responsible. 3. You change the selection criteria for an existing worklist under Change Worklist if you have authorization to do this. With centrally defined worklists that you did not create yourself, it is possible that you are not permitted to change the selection criteria. 4. For more information about the individual selection criteria, choose More Field Help in the respective context menu (right mouse button). 5. When searching using the input help for a selection criterion, you can copy several values from a table or a text editor and paste them in a field. You can also paste value intervals. In both cases, the respective number of new rows are inserted for the copied values where these values are entered. 6. If problems occur with the selection of data, you can display the relevant messages in the list display under Logs Worklist .

1.3.2 Layout You can change the layout of the worklist page overall and also change the layout of each individual list of worklists. The layout of a list of worklists can be adapted for all users centrally and by each user personally.

Features Page Layout Using personalization, each user can specify a choice of worklists, divide these into categories, sort them, and rename them if necessary. Additional settings for the layout support your personal requirements. You access personalization by choosing

( Personalization ). For more information, see the documentation for SAP NetWeaver ABAP under Personalization.

List Layout The layout of a list of worklists depends on the query that the list is based on. In the standard system, a separate query is delivered for each object category, which is stored in Customizing for QIM in the POWL Administrator Cockpit (POWL Cockpit). Any changes you make in the POWL Cockpit are relevant for all users. For more information, see Definition of Queries. In addition, each user can adapt the layout of his or her own worklist. This is possible via ( Open Settings Dialog ). Here, you can make settings for the column selection, sorting, filtering, or print versions. Under Display , you have the option of specifying hierarchy columns, for example. For more information, see the documentation for SAP NetWeaver ABAP under View with Settings.

1.3.3 Definition of Queries You define the layout of a list of worklists and make default settings for selection criteria in a query. On the one hand, administrators can create queries centrally in the back-end system and make them available to all users. With these default queries (also known as admin queries), little effort is required to make worklists with flexible selection and a specific layout available to a number of users. For example, you can thus define queries with variable time periods or partners. On the other hand, each user can define user-specific queries in the worklist using the New Worklist pushbutton.

Activities You define default queries in the POWL Administrator Cockpit . This is available in Customizing for QIM under Worklists for Quality Issues and Activities Make Settings in POWL Cockpit (transaction POWL_COCKPIT). You can also deactivate queries here. For more information, see the documentation for the Customizing activity.

More Information Selection According to Calculated Dates Selection According to Variable User or Business Partner

1.3.3.1 Selection According to Calculated Dates You can define a default query for a worklist whose selection is not based on fixed dates but for which the timeframe is calculated relatively in the future. You can select objects whose requested end will be reached in four weeks, for example.

Activities 1. In Customizing for QIM under (transaction POWL_COCKPIT).

Worklists for Quality Issues and Activities

Make Settings in POWL Cockpit

, open the POWL Administrator Cockpit

2. Select Standard POWL and choose Execute .

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 16 of 106

3. Select the personalization application QIM_GQIA_POWL and choose Register Query . 4. Select the query for which you want to define a calculated date and choose Maintain Query . 5. If necessary, switch to change mode and choose Calculated Dates .

1.3.3.2 Selection According to Variable User or Business Partner You can define a default query for a worklist that shows for each individual user which QIM issues or QIM activities he or she is assigned to. This is possible if you enter a variable in the respective selection field, which is then replaced by the current user or business partner who opens the worklist. You can use the following variables: – is replaced by the current user ID – is replaced by the business partner ID for the current user You can also use the variables in the front end during user-specific creation of a new worklist. This is useful, for example, if the business partner has to be entered in a field but the current user does not know the business partner assigned to him or her. The user can then enter the variable in the respective selection field.

Prerequisites You have assigned the conversion class CL_QAM_MAP_USER2PARTNER to the user or business partner search field in SMT mapping (see also Structure Mapping). If you want to use the variable , the business partner for the user must exist.

Activities 1. In Customizing for QIM under (transaction POWL_COCKPIT).

Worklists for Quality Issues and Activities

Make Settings in POWL Cockpit

, open the POWL Administrator Cockpit

2. Select Standard POWL . 3. Select the personalization application QIM_GQIA_POWL and choose Register Query . 4. Choose Maintain Query . 5. Open the query in which you want to use a variable and choose Query Parameters . 6. Enter the corresponding variable in a user or business partner field.

1.3.4 Structure Mapping To display a harmonized list of all the different objects in the worklist, the system performs a structure mapping. This assigns the different structures of the objects in the source systems to a generic structure in QIM. However, not every field of the generic target structure in QIM is filled by each source object; only the fields that are relevant for the respective object are filled.

Integration You use the Service Mapping Tool (SMT) for the definition of the structure mapping. This Web application is available in SAP QIM under Administration Edit Structure Mapping .

System

Features The structure mapping defined in SMT is stored in Customizing for the respective object category. For the object categories delivered with QIM, the structure mapping is also provided. You can change this mapping as required. You can find the assignment of the mapping to the object category in Customizing for QIM, for example, under Worklists for Quality Issues and Activities Define Access to Quality Issues . In addition to the field mapping for the assignment of source and target structures, the system also performs a value mapping for the status by transformation. This means that different status values of source objects are converted to a common status in QIM. This allows harmonized selection by status in the worklist (see Selection Criteria). As well as this value mapping within the structure mapping, there is also an ID mapping for the assignment of different values in the source system and QIM system in a nonharmonized system landscape. If this ID mapping fails to work, the system displays the value from the source system in the worklist. In this case, the system sets a Local indicator, which you can display in the worklist to check the ID mapping.

1.3.5 Jumps Using the link following an object ID in the worklist, you can jump directly to the object itself or to its reference objects in the source system and display or edit the object there.

Prerequisites In Customizing for QIM under objects in the worklist.

Basic Settings

Generic Settings for Reference Objects

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

, you have made the settings for the reference objects of the

Page 17 of 106

Note In the worklist, reference objects other than those defined for processing quality issues in SAP QIM can be relevant (see also Reference Objects). The user that is stored in the RFC connection for the respective source system must have authorization to access the required object in the source system. In addition to object-specific authorizations, the underlying RFCs must be stored in the authorization object S_RFC. For information about which RFCs are relevant for which object, see the various Customizing activities for access to quality issues and quality activities in the worklist or for access to reference objects. In the respective Customizing activity, you can access the relevant information in the settings for the object category by choosing ( Implementation Information ).

Features If an object is located in an SAP system that supports Web applications, you can edit the object directly in the source system. In the following cases, the navigation options in the source system are restricted, however: If objects are located in an older system that does not support the display of Web applications (for example, SAP R/3 4.6C) and you are working with SAP NetWeaver Business Client for HTML, only restricted navigation is possible in the source system. For example, you cannot jump to other applications. For products (object category Material in NW , MAT_NW), only restricted navigation is possible in the source system for each release level for technical reasons. Retail articles and product groups are handled as ERP materials and belong to the object category MAT_ERP, that is, the data is displayed via the material master display (transaction MM03). For the object category plant (PLANT_ERP) , no jump is supported.

1.3.6 Additional Information In the worklists for quality issues and activities, you can display additional information for one or more objects, that is for one or more rows in the list of worklists.

Features You can access the following information for one row: Detailed information If you select a row in the worklist, detailed information, such as any detailed descriptions available in the source system, is displayed below the list. Information about the object category If you select a row, you can access information about the object category that is relevant for the selected row by choosing Object Category . Information is displayed about possible restrictions in the selection criteria, for example, and a list of available fields. If you select one or more rows in the worklist, the function Additional Information is available. This opens the side panel in which Business Context Viewer (BCV) query views are displayed in the form of diagrams for the rows that are currently selected. For more information, see Reports in Business Context Viewer (BCV).

1.3.7 Status Change You can change the status of several objects in one step.

Note Some objects have no status, for example, the defect in the QIM system. A status change is not possible for these objects. If a digital signature is necessary for a status change (see Issue Processing with Digital Signatures), no mass change of the status is possible.

Features If you select one or more rows in your worklist, you can change the status for the selected objects under Issues or Activities . The following statuses are possible: Set in Process Complete The status is automatically changed in the source system. If necessary, other steps are triggered by the system. Under Logs , you can display lists of system messages relating to the respective status change.

1.3.8 Monitoring Control of Issues and Activities To monitor the quality issues and quality activities listed in the worklists, you can store different criteria for a monitoring control in the system. You can visualize the result in the worklist in the form of a traffic light.

Features The monitoring control is enabled technically by implementations of the following Business Add-Ins (BAdIs):

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 18 of 106

BADI_QAM_POWL_ISSUE_VALUATION for the monitoring control of quality issues BADI_QAM_POWL_ACT_VALUATION for the monitoring control of quality activities In the standard system, two implementations are delivered for each of the two BAdIs: Monitoring control according to status Examples: Completed quality issues or quality activities get a green traffic light, issues and activities in process get a yellow traffic light, and canceled ones get a red traffic light. Monitoring control according to requested start and end date Examples: When the requested start date is reached, but the end date is not reached, the issue or the activity gets a yellow traffic light. If both dates are exceeded, a red traffic light is set. For more information, see the documentation for the BAdI implementations. All BAdI implementations delivered in the standard system are activated, that is, you can use these monitoring control criteria immediately in the worklist. You can create your own BAdI implementations for other criteria.

Activities Display Traffic Light in Worklist 1. To display the traffic light for monitoring, insert the Traffic Light column in the layout of the respective list. 2. In the selection criteria for the list under Monitoring Control , specify the criterion (that is, the BAdI implementation) for the monitoring control.

Define Your Own Monitoring Control 1. Create your own BAdI implementation in Customizing for QIM under Worklists for Quality Issues and Activities Business Add-Ins (BAdIs) for Monitoring Control . You can use the existing implementations supplied as a guide. 2. Create the filter value for the implementation in Customizing for QIM under Worklists for Quality Issues and Activities Define Monitoring Control of Issues and Activities . The filter values stored here are available to users of the worklist as options when they select a criterion for monitoring control.

Note If individual BAdI implementations (and thus criteria for monitoring control) are not to be available to the users of the worklist, set the Inactive indicator for the respective filter value in the Customizing activity Define Monitoring Control of Issues and Activities .

1.4 Issue Processing In issue processing in SAP QIM, you have the option of capturing different types of quality issues and processing them by initiating suitable quality activities. You can also map use cases that go beyond classical quality management, such as improvement requests or service requests.

1.4.1 Overview: Creating Quality Issues You have three ways of creating an issue in Quality Issue Management: Create Quality Issue (Guided) Create Quality Issue (Quick) Create Quality Issue (Advanced)

Note If you use SAP Audit Management, you can also create a quality issue in QIM from a corrective or preventive action. For more information, see SAP Note 1771893.

Features You can use the functions Create Quality Issue (Guided) and Create Quality Issue (Quick) to create a quality issue quickly. You can use the Create Quality Issue (Advanced) function for the comprehensive entry of all data.

Issue Type You always create issues with an issue type. When you open a create function, you get a list of all the issue types defined in Customizing. From this list, you must select the issue type for which you want to create the issue. The issue type specifies the central settings for the processing of an issue. For example, it controls the default settings of code groups, partners, and activity templates, and which subitems can be created for an issue. The issue type also predefines the possible reference objects for an issue.

1.4.1.1 Create Quality Issue (Quick) You use this function to create a quality issue without needing to know detailed data about the issue.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 19 of 106

Quick creation allows entries in the following areas: Reported by Issue description Main reference object Issue code Urgency Timeframe Business partners In quick creation, only the Person Responsible is specified as a business partner. You can use the function Determine Partners and Codes to trigger the determination of partners using predefined business rules. If the business rules find other partner roles than the Person Responsible , these can be displayed. Only when the issue is further processed are all partners displayed that were found using the business process rules. Detailed description Attachments You can assign an attachment. When you finish processing, you can specify whether you set the status for the issue directly to In Process or whether you save the issue with the status New . If you finish processing with Save & Set in Process , it is possible that conflicts may occur if mandatory partners are missing or an approval is required. In this case, you cannot finish processing with Save & Set in Process . You can only close the application with the Save function.

1.4.1.2 Create Quality Issue (Guided) In guided creation of a quality issue, the creation of an issue is subdivided into the following individual steps: Describe issue Define reference objects Define urgency and partners Define activities Review and finish If you finish processing with Save & Set in Process , the issue is set directly to the status In Process . Conflicts can occur here if mandatory partners are missing and you cannot add these, or if an approval is required. In this case, you cannot save using Save & Set in Process ; you can only use the Save function to save the issue in the status New . You can make customer-specific changes to the sequence of the predefined steps (see Adaptation of the Web Applications in QIM).

1.4.1.3 Create Quality Issue (Advanced) With this create function, you can enter comprehensive data about an issue.

Features Issue Hierarchy You can show the issue hierarchy in the advanced create function and view a hierarchical structure of all elements that are assigned to an issue, for example: Reference objects Business partners Attachments Defects and their subobjects Activities and their subobjects Change documents When you double-click an element in the issue hierarchy, the details of the element are displayed.

Subitems Depending on the issue type, you can document defects, causes, or effects for an issue. The settings for this are made in Customizing for QIM under Processing Define Issue Types (see also Subitems: Defect, Cause, Effect).

Issue

1.4.1.4 Issue Status Status Assignment During the course of processing, an issue can be assigned different statuses (for example, Set in Process, Complete ). Depending on the entries required, you can assign the issue status manually. A newly created issue is assigned the status New . You can set the issue status to In Process when you have entered all required information and, for example, entered the business partner for a mandatory partner role. To be able to complete an issue, all mandatory short-term activities, that is, activities for which the Long-Term Activity indicator is not set, must be completed (see also Activity Status). When an issue was completed, you can assign a validation status, for example, Successful, Not Successful . Which business transaction triggers which status change is stored in the SAM editor (transaction SAMDT). The status modeling cannot be changed to meet

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 20 of 106

customer-specific needs.

Approval Process In addition, you can activate an approval process for an issue type in Customizing. To do this, in Customizing for Quality Issue Management under Issue Processing Define Issue Types , set the Approval Required indicator. When this indicator is set, an issue must be approved via an additional status. An issue can then only be assigned the status In Process if it was approved. However, it is still possible to process the issue in the status New .

Digital Signature You can document status changes using digital signatures (see also Issue Processing with Digital Signatures).

User Status You can add your own customer-specific user statuses to the issue status (see also User Status).

Activities You can display the status profile for issues in the SAM editor (transaction SAMDT). To do this, enter the following data: Business Object: /IAM/ISSUE Node Name: ROOT Schema Name: /IAM/ISSUE_ROOT

More Information You can find a simplified graphical representation of the possible status changes of an issue under Status Profile for Issues.

1.4.1.4.1 Status Profile for Issues The status profile /IAM/ISSUE_ROOT stored in the SAM editor defines the process flow for issue processing. Only certain actions are allowed for certain statuses.

Note In the SAM editor, all status types that an issue can have are displayed (with the exception of customer-specific user statuses). The following section describes the lifecycle status and approval status in more detail. Other status types, for example, archiving status or digital signature status, are not taken into account. Also note that the decision whether an approval is required or not is stored in Customizing for the issue type. This cannot be displayed in the SAM editor. The following diagram shows a graphical representation of the possible status changes:

Status Diagram

The following table shows which status changes are possible for each initial status and which actions initiate the status change:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 21 of 106

Status

Possible Actions to Trigger Status Change

New Status

New

Set in Process/ Save and Set in Process

In Process

Deletion Flag

Flagged for Deletion

Approve

Approval Status: Approved

New and To Be Approved

Issue Status: New Reject

Approval Status: Rejected Issue Status: Completed

In Process/ In Process After Completion Completed

Cancel

Canceled

Complete

Completed

Reopen

In Process After Completion

1.4.2 Changing of Quality Issues You can change issues in SAP QIM under Quality Issues . You always make changes in the advanced maintenance function of a quality issue, in which all subareas are displayed. The Create Quality Issue (Guided) and Create Quality Issue (Quick) functions are not available in change mode. When you change an issue, the activities that were already entered for the issue are then not ready for input. To change an activity, you must select the activity and choose Edit Activity . The selected activity is then ready for input. Only the selected activity can be edited; the other activities remain locked so that several activities can still be processed by different users at the same time. The activities can be changed independently of each other in SAP QIM under Quality Activities .

1.4.3 Subitems: Defect, Cause, Effect Defects, causes, and effects represent subitems of an issue. Causes and effects can, in turn, also be created as subitems for a defect. In the standard system, you can enter your own activities for defects and causes. You make the settings for the subitems in Customizing for the issue types: The subitems have their own issue categories: QDF: Defect QEF: Effect QCA: Cause For subitems, you can create your own issue types in which the relevant settings can be made. Thus, for each subitem, you can also store your own BRFplus rules for activity determination and code determination and configure settings for the code groups, for example (see Codes and Code Groups). You assign the issue types to other issue types as subitems. In issue processing, the subitems are all displayed as their own subarea. When an issue is saved, the subitems receive their own ID and can be processed individually in SAP QIM under Quality Issues . There is no status management for defects, causes, and effects. However, you must have completed all mandatory short-term activities of the subitems to be able to complete an issue.

Prerequisites You have made the settings for the subitems in Customizing for Quality Issue Management under

Issue Processing

Define Issue Types

.

1.4.4 Quality Activities Activities include all types of actions or measures taken to resolve an issue. Activities are created with a specific activity type, which, for example, determines the partner roles for an activity. For an activity type, you can define activity templates to simplify the creation of activities. In the Web Dynpro configuration delivered by SAP, you can create activities at the level of issues, defects, and causes.

Prerequisites Check the following settings in Customizing: Quality Quality Quality Quality

Issue Management Issue Management Issue Management Issue Management

Issue Processing Issue Processing Issue Processing Issue Processing

Define Settings for Activity Categories Define Activity Types Define Activity Templates Define Issue Types

Features The processing of activities is controlled via the activity category. The activity category determines basic properties of an activity, such as the status profile, which cannot be changed. Activities with the category Information do not have status management, for example.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 22 of 106

SAP delivers four activity categories: Basic activity These can be activities that must be performed immediately after an issue is created, for example, and in which a partner is not necessarily involved. Information These can be activities that serve to provide information about an issue and can also be used as an element to group a number of activities. Only restricted processing functions are available for information activities, so that, for example, no response and no partner assignment is possible. Question These can be activities whose answer can describe the issue and its context. The answer can be specified via the type of response, for example. Extended activity These are activities that contain comprehensive tasks and can usually only be processed together with a partner.

Activity Type You can create any activity types in Customizing for each activity category. The activity type includes the following settings: The role of the responsible partner Whether an activity is automatically set to the In Process status after having been created Whether the user who created the activity is automatically entered as the person responsible for the activity (see also Transfer of User Data for Activity Driver/Completed By for Activity). In the Partner Role Settings folder, you can specify whether it is mandatory to enter a partner for a role. Then, a partner must be entered for the activity before it can be set to In Process . You can specify that only one partner can be entered for a partner role.

Activity Templates To simplify the creation of activities, you can define activity templates in which you make certain default settings for the activities (see Activity Templates).

Adding New Activities There are different ways of adding activities: Using predefined business rules (see Determination of Activities Using BRFplus). In Customizing In Customizing, you can specify that activity templates are automatically assigned to an issue, a defect, an effect, or a cause. From activity template pool You can copy the required template from the list of activity templates defined in Customizing. You can search for the templates, for example, via codes, code groups, or the template text. Proposed activities In Customizing or in the decision table for determining activities using BRFplus, you can define activity templates as proposals. The proposed activities are displayed as a list in the application and can be copied to an issue, a defect, or a cause (see Proposed Activity Templates). Entered manually You can create activities without an activity template. When you create an activity, you must specify the activity type.

Note When you create activities manually, you cannot specify a response value. You can only define response values in Customizing for the activity templates.

Structuring Activities As a Hierarchy You can structure the activity list in an issue as a hierarchy. When you add a new activity, it is inserted as a subnode for the activity on which the cursor is positioned. This allows you to group activities with a specific objective or purpose. You can group activities regardless of their category. If you want to insert an activity at the top level of a hierarchy, no activity must be selected. You can also build up a hierarchy when you define activity templates (see Activity Templates). When you insert proposed activities in the activity list that are part of an activity hierarchy, the hierarchical relationship of these activities is always taken into account, that is, a proposed activity is always inserted beneath its parent activity, regardless of which row is selected.

Sort Number You use the sort number to specify the sort sequence in which the activities are to be processed. You specify the sort sequence in Customizing when building a hierarchy for subordinate activity templates and when assigning activity templates to an issue type. The activities are sorted in the sequence that is laid down by the sort number when an issue is created. You can change the sort sequence of the activities in the issue manually.

Origin The origin is specified for each activity: For activities that are copied over from Customizing automatically or as a proposal, the origin is given as Predefined . For proposed activities, the Proposal indicator is also set in the activity properties. For activities that are determined using BRFplus rules, the origin is given as Rule . For activities that are assigned manually, the origin is given as Manually Entered .

Activity Properties Long-term activity If you set the Long-Term Activity indicator, you can complete an issue but the activity still has the status In Process and can still be processed after completion of the issue. The indicator can be set in Customizing for the activity template as a proposal.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 23 of 106

Mandatory activity Mandatory activities must be completed within the issue resolution process. As long as an issue contains a mandatory activity that is not completed, the issue itself cannot be completed. If this indicator was set in Customizing for the activity template, it cannot be unset in the application. If both the Long-Term Activity indicator and the Mandatory Activity indicator are set, you can complete the issue even if the activity is still open, but you cannot delete the activity after the issue is completed.

Response Type You can enter responses for all activity categories apart from Information . In Customizing, you can specify for an activity template that a response is necessary and also specify a response value: Date Code Quantitative A unit must be specified for the response value. Boolean None If you have not specified a response value, the Response Value field is not visible in the application.

Note When you create activities manually in the issue without an activity template, you cannot specify a response value.

Activities You create activities in the Web Dynpro configuration delivered by SAP when processing an issue, a defect, or a cause. Each activity is assigned an activity ID. You can process activities individually in SAP QIM under Quality Activities .

1.4.4.1 Activity Templates Using activity templates, you can simplify the creation of activities when you create an issue. In activity templates, you can specify certain defaults that apply for all activities that are created with this template. 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.

Prerequisites You have checked the following Customizing settings: Quality Issue Management Quality Issue Management

Issue Processing Issue Processing

Define Activity Templates Define Issue Types

Features When defining activity templates in Customizing, you can build a hierarchy for activity templates: You can bundle activities that belong together and transfer the whole bundle when you process an issue. A bundle can be inserted in another bundle of activity templates. All types of activity categories can be inserted or used as a parent node. When you build an activity template hierarchy, you can specify that activity templates should be transferred automatically to the issue, or that activity templates should be proposed and must then be transferred by the user. You can display activity hierarchies for an issue type graphically in SAP Quality Issue Management under System Administration in the screen area Process Control Activity Network . You can specify the duration at the level of activity templates. If a start date is specified for an activity, the end date is calculated automatically based on the duration specified in Customizing. You then assign activity templates to an issue type. By means of the issue category, you can control whether the activity templates apply for issues, defects, effects, or causes. When you create an issue, you can copy the activity templates from Customizing and create new activities with the templates. Activity templates can be copied to an issue, defect, cause, or effect using rule determination in Business Rule Framework plus (BRFplus).

More Information See also Proposed Activity Templates and Determination of Activities Using BRFplus.

1.4.4.1.1 Proposed Activity Templates At the level of the issue type and at the level of the activity templates, you can specify that in the application, activity templates are copied over automatically for an issue, or that the activity templates can be selected manually from a template pool.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 24 of 106

Activity templates without the Proposal indicator are copied over directly when an issue is created. Activity templates with the Proposal indicator are not specified directly, but can be copied over to the issue using .

Add Activities

Proposed Activities

You define automatic or proposed activity templates at two levels: When you build an activity hierarchy When you assign activity templates to an issue type The following scenarios result from this: An activity template was marked as proposed when assigned to the issue type. The activity template contains more subordinate activity templates that are also proposed. The activity template contains more subordinate activity templates that are copied over automatically. An activity template was marked as automatic when assigned to the issue type. The activity template contains more subordinate activity templates that are also copied over automatically. The activity template contains more subordinate activity templates that are proposed. You can also determine proposed activity templates using the decision table for activity determination in Business Rule Framework plus (BRFplus). These activity templates are also displayed in the list of proposed activity templates.

Prerequisites You have defined activity templates and, if required, built up activity hierarchies in Customizing under Define Activity Templates . You have assigned activity templates to the issue types in Customizing under

Quality Issue Management

Quality Issue Management

Issue Processing

Issue Processing Define Issue Types

.

When determining activity templates using BRFplus, you have set the Proposal indicator in the decision table.

Activities 1. You select the proposed activity templates in the application in the Activities assignment block under Add Activities Proposed Activities . A dialog box appears with all activity templates that were assigned to the issue type and that were not copied over automatically. 2. Select the activity template that you want to copy over. Behavior in an activity hierarchy: The parent activity template is proposed; automatic transfer is specified for the subordinate nodes: If the parent activity template is copied over, the subordinate templates are also copied over. The parent activity template is automatically copied over, the subordinate activity templates are proposed: The subordinate templates are not copied over automatically, but can be selected as proposals in the dialog box. The parent activity template is proposed and the subordinate templates are also proposed: Each template in the hierarchy can be selected individually. Activity templates that were already copied over to the issue are grayed out in the dialog box. They can still be selected and copied over to the issue multiple times.

Note If you have selected a row in the list of activities, the new activity is created as a subnode of the selected row. If you want to create the activity at the top level, you must deselect all rows, for example, using CTRL+mouse click.

1.4.4.2 Determination of Activities Using BRFplus Business Rule Framework plus offers you a Web-based workbench in which you can define rules and set up automatic determination of activities, partners, and codes. The rules are specified in decision tables.

Example You can specify that depending on a specific issue code and priority, a specific activity template is automatically entered in an issue. The following BRFplus objects are delivered for activity determination: BRFplus application: QIM_ISSUE_DETERMINE_ACTIVITIES This application has the BRFplus storage type Customizing and can be transported like other Customizing. If necessary, the BRFplus application can be replaced by customer-specific applications. BRFplus function: QIM_ISSUE_DETERMINE_ACTIVITY This function is part of the BRFplus application QIM_ISSUE_DETERMINE_ACTIVITIES that is defined as Customizing and can be replaced by a customerspecific function. BRFplus rule set: DETERMINE_ACTIVITY This rule set specifies the process for rule evaluation through to evaluation of the decision table. The rule set can be replaced by a customer-specific one, just as for the whole BRFplus application. Decision table: DECISION_TABLE The decision table contains condition and result columns in which you specify the input and output parameters.

Note You can also call the decision table for activity determination and the activity determination workbench directly in QIM under System Administration in the screen area Configure Rules .

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 25 of 106

Features To be able to derive bundles of activity templates, you can specify a parent activity template in the result columns for an activity template. All activity templates for which a parent activity template was specified are positioned beneath the parent activity template when you create the issue. You can specify the BRFplus application and BRFplus function for activity determination for each issue type in Customizing. To create your own applications and functions for different issue types, you can use the BRFplus application QIM_ISSUE_DETERMINE_ACTIVITIES as a template. If you do not specify a BRFplus application or function in Customizing, no activities are determined for an issue type via BRFplus.

Activities To activate activity determination using BRFplus, proceed as follows: 1. In Customizing for Quality Issue Management under want to use for activity determination. 2. Call the transaction BRFPLUS.

Issue Processing

Define Issue Types

, specify the BRFplus application and function that you

3. Search for the application QIM* and choose Application as the object type. 4. Drill down in the tree to Expression Decision Table . 5. Open the table QIM Issue - Decision Table for Activity Determination . Enter the required data. 6. Enter the relevant BRFplus function and application in Customizing for an issue type. 7. Create an issue in Quality Issue Management. If you choose the function Determine Activities for activities, those activities are inserted that fulfill the specified criteria.

More Information For more information about BRFplus, see Business Rule Framework plus (BRFplus). You can find the documentation for BRFplus under SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Application Developers Business Rule Framework plus .

Note The documentation for BRFplus exists in English only.

1.4.4.3 Determination of Partner for Activities Using BRFplus Business Rule Framework plus offers you a Web-based workbench in which you can define rules and set up automatic determination of activities, partners, and codes. The rules are specified in decision tables.

Example You can specify that for a specific activity template, a specific partner is directly entered in the activity. The following BRFplus objects are delivered for partner determination in activities: BRFplus application: QIM_ACTIVITY_DETERMINE_PARTY (QIM Activity Determine Partners) This application has the BRFplus storage type Customizing and can be transported like other Customizing. If necessary, the BRFplus application can be replaced by customer-specific applications. BRFplus function: /IAM/ACT_PARTY_DET_QIM This BRFplus function is the interface to the QIM applications Create Quality Issue (Guided), Create Quality Issue (Quick) , and Create Quality Issue (Advanced) . The BRFplus function /IAM/ACT_PARTY_DET_QIM is an SAP object with the BRFplus storage type System and cannot be changed or replaced. BRFplus rule set: DETERMINE_PARTY This rule set specifies the process for rule evaluation through to evaluation of the decision table. The rule set can be replaced by a customer-specific one, just as for the whole BRFplus application. To enable this, each customer-specific rule set must be assigned to the BRFplus function /IAM/ACT_PARTY_DET_QIM. Decision table DETERMINE_PARTY_DCSN_TABLE (QIM Issue - Decision Table for Partner Determination) The decision table contains condition and result columns in which you specify the input and output parameters. The entry of the partner role as an output parameter is mandatory. Output parameter Position : The position refers here either to a business partner group hierarchy or a position in HR Organizational Management. To be able to derive values for a position, you must define a position origin for a partner role in Customizing for Quality Issue Management under Issue Processing Partners Define Partner Roles . You use the position origin to specify whether the position is determined from a business partner group hierarchy or from HR Organizational Management. The position specifies the task that certain employees in an enterprise have, such as experts. For example, filter value 01 determines the assigned business partners for a position (= node) in a business partner group hierarchy and calls the implementation /IAM/IMPL_BUPA_HIERARCHY in BAdI /IAM/BADI_POSITION_TO_BUPA. Via the BAdI, all business partners that are assigned to this node are found by expanding the node. For each of the business partners assigned to the node, an entry is made in the list of partners in the QIM issue, whereby the specified partner role is always used.

Note

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 26 of 106

You can also call the decision table for partner determination in activities and the partner determination workbench for activities directly in QIM under System Administration in the screen area Configure Rules .

Features If, when you insert new entries with partner role and business partner (either directly or those found by the function), an existing entry with the same partner role but without a partner ID is found, no new entry is created but the partner ID is added in the existing entry. If identical entries exist for a combination of partner role and business partner, no new entry is created if entries were derived using the decision table. This also applies in the case where several identical combinations of partner role and position or business partner result when the decision table is evaluated. Here also, no redundant entries are added to the list of partners for the QIM issue. You cannot start partner determination for activities directly when processing an issue; it is done automatically by the system when a new activity is created.

Activities To maintain the values in the decision table, proceed as follows: 1. Call the transaction BRFPLUS. 2. Open the application QIM_ACTIVITY_DETERMINE_PARTY (QIM Activity Determine Partners) with the object type Application . This application has the storage type Customizing and can be transported like other Customizing settings. 3. Drill down in the hierarchy tree to Expression Decision Table . Open the decision table Determine_Party_Dscn_Table . 4. Enter the required values. Specifying a partner role is mandatory. Table fields that are empty will not be taken into account in the evaluation. 5. Save your entries. The decision table is evaluated when you create a new activity.

More Information For more information about BRFplus, see Business Rule Framework plus (BRFplus). You can find the documentation for BRFplus under SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Application Developers Business Rule Framework plus .

Note The documentation for BRFplus exists in English only.

1.4.4.4 Transfer of User Data for Activity Driver/Completed By for Activity Transfer of User Data for Activity Driver For each activity type, you can specify that the logged-on SAP user is automatically determined as the activity driver: A unique business partner ID must be created for the SAP user in the transaction BP or using the report /IAM/APP_CREATE_BUPA. If you select Employee as the business partner role, you can assign the employee data Personnel Number and User Name on the Identification tab. In Customizing for Quality Issue Management under Issue Processing Define Issue Types , enter the initiator role. In Customizing under Issue Processing Define Activity Types , set the Automatically Add 'Created By' User As Responsible indicator and specify the responsible partner role.

Note You can jump to the relevant transactions for the business partner settings in SAP QIM under System Administration .

Determine 'Completed By' for Activity Automatically If a business partner ID was created for the SAP user, the data is copied over automatically and displayed in the Completion screen area when an activity is completed.

Constraints The following restrictions apply for the transfer of employee data as the activity driver and activity completer: If a partner was already entered, the entry is not overwritten. The data can only be copied over if one business partner only can be assigned to an employee. If more than one business partner ID exists for an employee, the system cannot transfer the data.

1.4.4.5 Activity Status The status management for activities depends on the activity category. For the activity categories, different status profiles were defined in the SAM editor

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 27 of 106

(transaction SAMDT): Basic activity: simple status profile Information: technical status profile (required, for example, for the archiving status, but not for the lifecycle status) Question: simple status profile Extended activity: extended status profile For extended activities, the status Postpone is possible. In this status, the activity is no longer ready for input, but can be changed back to the status In Process at a later stage. In Customizing under SAP Quality Issue Management Issue Processing Define Activity Types , you can specify that the activities of an activity type are immediately set in process and do not have the status New . This is useful for activities that do not require any preliminary clarification. An activity can only be set to In Process when all required data was entered, such as a mandatory partner.

Activity Completion To be able to complete activities, all follow-up actions that exist for an activity must have been completed successfully.

Activity Validation As soon as an activity has the status Completed , you can validate the activity. An activity can be validated with the following statuses: Successful Not successful Not measurable

Digital Signature You can document status changes using digital signatures (see also Issue Processing with Digital Signatures).

User Status You can add your own customer-specific status to the activity status (see also User Status).

Activities To display the status profiles delivered for activities, process as follows: 1. Open the SAM editor using the transaction SAMDT. 2. Under Business Object , enter /IAM/ACTIVITY. 3. Under Node Name , enter the node ROOT. 4. Under Schema Name , use the input help to select the status profile you want to display.

More Information You can find a simplified graphical representation of the possible status changes – using the example of extended activities – under Status Profile for Extended Activities.

1.4.4.5.1 Status Profile for Extended Activities The status profile /IAM/ACT_ROOT_EXTENDED_ACT stored in the SAM editor defines the process flow for processing extended activities. Only certain actions are allowed for certain statuses.

Note In the SAM editor, all status types that an extended activity can have are displayed (with the exception of customer-specific user statuses). The following section describes the lifecycle status in more detail. Other status types, for example, archiving status or digital signature status, are not taken into account. The following diagram shows a graphical representation of the possible status changes:

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 28 of 106

Status Diagram

The following table shows which status changes are possible for each initial status and which actions initiate the status change: Status

Possible Actions to Trigger Status Change

New Status

New

Set in Process

In Process

Postpone

Postponed

Complete

Completed

Cancel

Canceled

Deletion Flag

Flagged for Deletion

Postponed

Set in Process

In Process

In Process

Complete

Completed

Return

Returned

Cancel

Canceled

Postpone

Postponed

Cancel

Canceled

Set in Process

In Process

Reopen

In Process

Returned

Completed

1.4.4.6 Definition of Follow-Up Actions Follow-up actions define actions or functions that are triggered automatically by the system when an activity is set to the status In Process . A follow-up action can, for example, specify that an e-mail is sent to a partner.

Features Each follow-up action requires an active implementation of the Business Add-In (BAdI) /IAM/BADI_ACT_FOLLOW_UP . The BAdI implementation defines the required reference objects (material, batch, and so on), the business partners, quantities, date fields, and parameters. The follow-up action is assigned to an activity template in Customizing for Quality Issue Management. Here, you can also specify defaults for parameters. The following properties apply to follow-up actions: If a follow-up action was specified for an activity template, the Follow-Up Action tab is visible when you are processing the activity. A follow-up action is fixed to an activity and cannot be moved to another activity. The processing of follow-up actions is documented by their own processing status and their own processing log. A follow-up action can only be executed once. It can only be repeated if it was not successful. New reference objects can be added to the list of reference objects via follow-up actions (for example, a newly created material document). Activities with a follow-up action cannot be completed directly; they must first be set to the status In Process .

Activities 1. You define follow-up actions in Customizing for Quality Issue Management under Issue Processing Define Follow-Up Actions . Here, you enter the key and the text for the follow-up action and the possible target systems for each follow-up action. 2. Create the BAdI implementation in Customizing under Issue Processing Business Add-Ins (BAdIs) BAdI: Definition of Follow-Up Actions

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

.

Page 29 of 106

3. Assign the follow-up action to an activity template in Customizing under Issue Processing Define Activity Templates . In the Follow-Up Action Parameters folder, you can specify default values for the parameters. 4. The reference objects are determined automatically by the BAdI and displayed under Issue Processing Define Activity Templates in the Reference Objects folder. The mandatory objects are indicated accordingly. The follow-up action cannot be executed without these objects. The object types that are created via the follow-up action are also listed and indicated accordingly. 5. When processing an issue, create an activity using the activity template to which the relevant follow-up action was assigned. The Follow-Up Action tab is displayed.

1.4.5 Settings Dependent on the Text Type In issue processing, a number of different text areas are available in which you can enter descriptions for issues, defects, or activities, for example. One text area comprises the fields for the description and detailed description and the fields for codes and code groups. You therefore make presets for codes and code groups depending on the text types (see section Presetting Code Groups via the Text Type ). A specific text type was defined in Customizing for each text area.

Note For example, the text type IDESC was created for the description of an issue, that is, the fields for entering the issue description, the detailed description, the codes and code groups in the Issue Overview screen area belong to this text type. The settings for text types include the following activities in Customizing: 1. You find the existing text types under Cross-Application Components Processes and Tools for Enterprise Applications Functions for BOPF Environment Dependent Object Text Collection Maintain Text Schema . The existing text types are listed in the Text Type folder.

Reusable Objects and

Note If you want to include your own text types, you should choose a customer-specific namespace that starts with Z or Y so that no identical entries are created. In the Text Type to Text Schema Assignment folder, the respective text types are assigned to a text schema. The standard schemas for QIM have the prefix QIM_* .

Example In the standard system, the text types IDESC and ISOLU are assigned to the text schema QIM_ISSUE. 2. In Customizing for QIM, the text schema is assigned to an issue category or an activity category under Define Settings for Issue Categories or Define Settings for Activity Categories . You cannot change the existing assignment of the text schema.

Note You can, however, extend the text schema by including your own text types in it. You must then add the new fields for creating texts to the Web UI configuration so that they are displayed on the interface. 3. The issue or activity categories are assigned to an issue type or activity type under Define Issue Types or Define Activity Types , thus making the respective text schema effective in the application.

Example The text schema QIM_ISSUE with the two text types IDESC and ISOLU is assigned to the issue category QIM (quality issue). The text schema is therefore valid in all issue types to which the issue category QIM is assigned. In the issue overview, the fields Issue Description, Detailed Description, Code Group , and Code belong to the text type IDESC. The corresponding fields in the Issue Resolution screen area belong to the text type ISOLU.

Defining a Catalog for the Text Type Using the text type, it is also possible to set a default catalog when searching for codes. To do this, in Customizing for QIM choose Basic Settings Text Types Define Settings for Text Types . You can assign a catalog to a text type, which is then displayed as a proposal for the code search in the text area for this text type, for example, in the issue resolution. The catalog serves only as a proposal for the search and can also be changed if necessary (see also Codes and Code Groups).

Presetting Code Groups via the Text Type In Customizing for QIM under Issue Processing code group depending on a text type.

Define Issue Types

or

Issue Processing

Define Activity Templates

, you can define defaults for a

The permitted text schema is preset via the issue or activity category. From the text schema, you can specify a text type and a default code group for the text types (see also Codes and Code Groups).

Example You have created an issue type with the issue category Quality Issue . The text schema QIM_ISSUE is assigned to the issue category Quality Issue . The text schema contains the two text types IDESC and ISOLU. If you now assign a code group COD_1 to the text type ISOLU, this code group is proposed by default in issue processing in the Issue Resolution screen area.

Storing Historical Texts

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 30 of 106

For each text type, you can specify that a history is stored for the long texts entered in the various text areas. Long texts entered are frozen and become historical if the text is changed in a different language or if the text is changed by another user. The frozen long texts are displayed in their own text area and cannot subsequently be changed. You activate long text history in Customizing for QIM under whether historical texts can be stored.

Basic Settings

Text Types

Define Settings for Text Types

. Specify for each text type

For each text type, a history is displayed directly beneath the respective long text field, sorted according to the time of entry. The newest text is at the top. There is also an overview of the historical texts of all text types, also sorted according to the time of entry. The display of the historical texts is integrated in the advanced processing of issues, in individual processing of activities, and in the hierarchy view.

1.4.6 Codes and Code Groups You can use codes and code groups to classify different objects in Quality Issue Management according to specific aspects. You can assign codes to the following areas: Issues Activities Defects Causes Effects Responses Resolutions You define codes globally in Customizing for Quality Issue Management, independent of their use. The identification of a code is unique and does not depend on a code group. You can therefore assign codes to different code groups.

Example You define a code 10 with the text red. The code 10 can only exist once and it can be identified uniquely, independent of its assignment to a code group. In principle, you can select all codes each time you use one; however, you can also control the search to be more specific by assigning codes to catalogs, code groups, and by building code group hierarchies. In Customizing, you can specify that the catalog is set by default when you search for codes. The default can be changed when searching for codes. The default catalog setting is made in Customizing for the text types. You can therefore specify different catalogs for different areas of issue or activity processing. You can also set defaults for code groups for each issue type and activity template. The default settings for code groups are also dependent on the text type. In the standard system, the text types IDESC (issue description) and ISOLU (issue resolution) are defined for issues. If you assign a specific code group to these two text types for an issue type, the code groups are copied over by the system during issue processing: The code group for the issue description is copied over during issue definition. The code group for the issue resolution is copied over during issue assessment. By means of the issue type, you can also control the default setting of the code group for defects, effects, and causes: In the standard system, the text types DDESC (defect description) and DLCTN (defect location) are defined for defects. The text type CDESC is defined for causes. The text type EDESC is defined for effects. You can assign your own code groups to these text types per issue type. In the standard system, the text types ADESC (activity description) and ARESP (response description) are defined for activity templates. If you assign a specific code group to these two text types for an activity template, the code group is copied over for the activities: The code group for the activity description is copied over during activity definition. The code group for the response description is copied over in the response. The prerequisite here is that you have activated the response in Customizing for the activity template.

Prerequisites Check the following settings in Customizing: Assignment of catalogs to text types In Customizing for Quality Issue Management, choose Codes In Customizing for Quality Issue Management, choose Catalogs and code groups In Customizing for Quality Issue Management, choose Default setting of code groups in issue types In Customizing for Quality Issue Management, choose Default setting of code groups in activity templates In Customizing for Quality Issue Management, choose

Basic Settings

Text Types

Issue Processing

Codes

Issue Processing

Define Catalogs and Code Groups

Issue Processing

Define Issue Types

Issue Processing

Define Activity Templates

, Code Group folder , Code Group folder

More Information For more information, see Settings Dependent on the Text Type.

1.4.6.1 Determination of Codes and Code Groups Using BRFplus PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 31 of 106

Business Rule Framework plus offers you a Web-based workbench in which you can define rules and set up automatic determination of activities, partners, and codes. The rules are specified in decision tables.

Example You can specify that depending on a specific priority, a specific code is directly entered in an issue. The following BRFplus objects are delivered for code determination: BRFplus application: QIM_ISSUE_DETERMINE_CODE This application has the BRFplus storage type Customizing and can be transported like other Customizing. If necessary, the BRFplus application can be replaced by customer-specific applications. BRFplus function: QIM_ISSUE_DETERMINE_CODE This function is part of the BRFplus application QIM_ISSUE_DETERMINE_CODE that is defined as Customizing and can be replaced by a customerspecific function. BRFplus rule set: DETERMINE_CODE This rule set specifies the process for rule evaluation through to evaluation of the decision table. The rule set can be replaced by a customer-specific one, just as for the whole BRFplus application. Decision table: DECISION_TABLE The decision table contains condition and result columns in which you specify the input and output parameters.

Note You can also call the decision table for code and code group determination in issues and the code determination workbench directly in QIM under System Administration in the screen area Configure Rules .

Features The BRFplus application and BRFplus function can be used per issue type for code determination or code group determination. In Customizing for Quality Issue Management under Issue Processing Define Issue Types , you can specify a BRFplus application and a BRFplus function for each issue type. This also allows you to run code determination for defects, causes, and effects separately. To create different BRFplus applications, you can copy the BRFplus application QIM_ISSUE_DETERMINE_CODE.

Activities To activate code determination using BRFplus, proceed as follows: 1. In Customizing for Quality Issue Management under want to use for code determination. 2. Call the transaction BRFPLUS.

Issue Processing

Define Issue Types

, specify the BRFplus application and function that you

3. Search for the application QIM* and choose Application as the object type. 4. Drill down in the tree to Expression Decision Table . 5. Open the table QIM Issue - Decision Table for Code Determination . Enter the required data.

More Information For more information about BRFplus, see Business Rule Framework plus (BRFplus). You can find the documentation for BRFplus under SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Application Developers Business Rule Framework plus .

Note The documentation for BRFplus exists in English only.

1.4.7 Partners Normally, a number of people are involved in an issue and its resolution. It is therefore necessary to assign different people with different roles to an issue or an activity. 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. In addition, partner roles and partner IDs can be determined using predefined business rules that were set up in Business Rule Framework plus (BRFplus), depending on specific details such as the priority.

More Information PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 32 of 106

For more information, see Partner Roles and SAP Business Partner. For more information about BRFplus, see Business Rule Framework plus (BRFplus). You can find the documentation for BRFplus under SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Application Developers Business Rule Framework plus .

Note The documentation for BRFplus exists in English only.

1.4.7.1 Partner Roles Partner roles describe the tasks of persons or groups of people who are involved in an issue or activity. Various partner roles are delivered by SAP as proposals, such as issue driver, interested party, or activity driver. You can also define partner roles freely to fulfill your own requirements. At the level of the partner role, you can also specify whether you want to plan business partner IDs based on a business partner group hierarchy or HR Organizational Management.

Prerequisites You have created all partner roles in Customizing under Quality Issue Management Issue Processing Partners Define Partner Roles . In this Customizng activity, you have also specified whether you want to plan the business partner IDs via a position in HR Organizational Management or a position (node) in a business partner group hierarchy. You have assigned the relevant partner roles to the issue types and activity types in Customizing under Quality Issue Management Define Issue Types or Quality Issue Management Issue Processing Define Activity Types .

Issue Processing

Features You can copy all partner roles to an issue or activity that were assigned to the respective issue type or activity type in Customizing. The partner role of the issue submitter, the role of the person responsible, and mandatory partner roles are copied directly to the issue or activity and displayed. Optional partner roles can be selected for an issue or activity as required.

Note The responsible partner role can only be assigned to one unique partner per activity or issue.

1.4.7.2 Partners in a QIM Issue You assign a partner ID to the partner role of a QIM issue; this ID is used to identify a specific partner. The data for a partner is maintained in the business partner master data. Business partner maintenance is a central function for storing and managing all partner information.

Prerequisites Settings in Customizing In Customizing for Quality Issue Management under Issue Processing Define Issue Types you can jump to master data maintenance and define default partners for a partner role.

Default Partners

using the Define Partners pushbutton,

In this Customizing activity, you can also specify whether a partner role is mandatory and unique, that is, that the role can only be assigned once. For mandatory partner roles, you must specify a business partner ID for the issue or activity at the latest when the status is changed to In Process . Otherwise the status change is not possible. For activity types, you define default partners under Issue Processing Define Activity Templates assignment of business partner and partner roles under Issue Processing Define Activity Types

Details .

. You set the indicator for the unique

Features Create Business Partners There are different methods of creating business partners in the SAP system: You have created the business partners in your SAP system using the function Maintain Business Partner (transaction BP) (see also SAP Library SAP ERP SAP ERP Cross-Application Functions Cross-Application Components SAP Business Partner Functions Processing Business Partner Data ). You have created business partners from customer masters and vendor masters using the synchronization cockpit (transaction MDS_LOAD_COCKPIT) (see also SAP Library SAP ERP SAP ERP Cross-Application Functions Cross-Application Components Master Data Synchronization ). You can create business partners from HR master data and organizational data using the report HRALXSYNC (see also SAP Library SAP ERP Central Component Human Resources Personnel Management (PA) Personnel Administration Integration of Personnel Administration with Other

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 33 of 106

Applications Integration with SAP Business Partner ). You can link business partners with SAP users in SAP QIM by choosing System Administration Create Business Partners for Users . Via a PFCG role, such as SAP_QIM_COORDINATOR, the report /IAM/APP_CREATE_BUPA selects the users that are assigned to this role and creates a business partner for the selected users. You can transfer the business partner data to SAP QIM using the SAP distribution functions (see also SAP Library SAP ERP Functions Cross-Application Components SAP Business Partner Functions Distribution of Business Partner Data ). In SAP QIM, you can create or change business partners via

System Administration

Maintain Business Partner

SAP ERP Cross-Application

.

1.4.7.2.1 Transfer of User Data for Issue Submitter For each issue type, you can specify that the logged-on user is automatically entered in the partner list as issue submitter: A unique business partner ID must be created for the SAP user in the transaction BP or using the report /IAM/APP_CREATE_BUPA. If you select Employee as the business partner role, you can assign the employee data Personnel Number and User Name on the Identification tab. In Customizing for Quality Issue Management under Issue Processing Define Issue Types , enter the initiator role. Once a business partner ID is assigned to the SAP user, the business partner ID is entered in the partner list when an issue is created. The following restrictions apply here: If a partner was already entered, the entry is not overwritten. The data can only be copied over if one business partner only can be assigned to an employee. If more than one business partner ID exists for an employee, the system cannot transfer the data.

Note You can jump to the relevant transactions for the business partner settings in SAP QIM under System Administration .

1.4.7.3 Determination of Partner for Issues Using BRFplus Business Rule Framework plus offers you a Web-based workbench in which you can define rules and set up automatic determination of activities, partners, and codes. The rules are specified in decision tables.

Example You can specify that for a specific issue type, a specific partner is directly entered in an issue. The following BRFplus objects are delivered for partner determination in issues: BRFplus application: QIM_ISSUE_DETERMINE_PARTY (QIM Issue Determine Partners) This application has the BRFplus storage type Customizing and can be transported like other Customizing. If necessary, the BRFplus application can be replaced by customer-specific applications. BRFplus function: /IAM/ISSUE_PARTY_DET_QIM This BRFplus function is the interface to the QIM applications Create Quality Issue (Guided), Create Quality Issue (Quick) , and Create Quality Issue (Advanced) . The BRFplus function /IAM/ISSUE_PARTY_DET_QIM is an SAP object with the BRFplus storage type System and cannot be changed or replaced. BRFplus rule set: DETERMINE_PARTY This rule set specifies the process for rule evaluation through to evaluation of the decision table. The rule set can be replaced by a customer-specific one, just as for the whole BRFplus application. To enable this, each customer-specific rule set must be assigned to the BRFplus function /IAM/ISSUE_PARTY_DET_QIM. Decision table DETERMINE_PARTY_DCSN_TABLE (QIM Issue - Decision Table for Partner Determination) The decision table contains condition and result columns in which you specify the input and output parameters. The entry of the partner role as an output parameter is mandatory. Output parameter Position : The position refers here either to a business partner group hierarchy or a position in HR Organizational Management. To be able to derive values for a position, you must define a position origin for a partner role in Customizing for Quality Issue Management under Issue Processing Partners Define Partner Roles . You use the position origin to specify whether the position is determined from a business partner group hierarchy or from HR Organizational Management. The position specifies the task that certain employees in an enterprise have, such as experts. For example, filter value 01 determines the assigned business partners for a position (= node) in a business partner group hierarchy and calls the implementation /IAM/IMPL_BUPA_HIERARCHY in BAdI /IAM/BADI_POSITION_TO_BUPA. Via the BAdI, all business partners that are assigned to this node are found by expanding the node. For each of the business partners assigned to the node, an entry is made in the list of partners in the QIM issue, whereby the specified partner role is always used.

Note You can also call the decision table for partner determination in quality issues and the partner determination workbench in issues directly in QIM under System Administration in the screen area Configure Rules .

Features If, when you insert new entries with partner role and business partner (either directly or those found by the function), an existing entry with the same partner role but without a partner ID is found, no new entry is created but the partner ID is added in the existing entry. If identical entries exist for a combination of partner role and business partner, no new entry is created if entries were derived using the decision table. This also

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 34 of 106

applies in the case where several identical combinations of partner role and position or business partner result when the decision table is evaluated. Here also, no redundant entries are added to the list of partners for the QIM issue.

Activities To maintain the values in the decision table, proceed as follows: 1. Call the transaction BRFPLUS. 2. Open the application QIM_ISSUE_DETERMINE_PARTY (QIM Issue Determine Partners) with the object type Application . This application has the storage type Customizing and can be transported like other Customizing settings. 3. Drill down in the hierarchy tree to Expression Decision Table . Open the decision table Determine_Party_Dscn_Table . 4. Enter the required values. Specifying a partner role is mandatory. Table fields that are empty will not be taken into account in the evaluation. 5. Save your entries. 6. Create an issue in Quality Issue Management. When you select the function Determine Partners , the partner roles and partners that match the specified criteria are entered in the partner table.

More Information For more information about BRFplus, see Business Rule Framework plus (BRFplus). You can find the documentation for BRFplus under SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Application Developers Business Rule Framework plus .

Note The documentation for BRFplus exists in English only.

1.4.8 Reference Objects You can assign objects to which a quality issue refers (such as materials, batches, vendors, delivery items) as reference objects. Technically, the reference objects can be located in other systems.

Integration You can open the reference objects in the source system via links from the QIM system. For information about how the technical integration is implemented, see Technical System Integration.

Features Delivered Reference Objects In the standard system, object types and object categories are delivered for numerous types of reference objects. The object type describes an entity in general (for example, material); the object category describes the origin more exactly (for example, material in ERP or material/product in SAP NetWeaver). For some object types, there are several object categories for different release levels of the system in which the object is available (for example, maintenance notification). You can find out which object types and object categories are available for reference objects in Customizing for QIM under for Reference Objects .

Basic Settings

Generic Settings

General Reference Objects One notable case is the delivered External reference object (object type GOJ) that is intended for flexible use because it does not have a technical equivalent in another system. It is based on the BOL component IAMGOJ for the business object GeneralObject . This BOL component can also be used as the basis for other reference objects. For example, it is the basis for another delivered object type Storage location (STL). All reference objects that are based on the BOL component IAMGOJ have the following special features: The reference to the object in another system only means that you can search for this object in the external system. For this purpose, you can define your own search help in the external system if required and assign it in Customizing for the object type. However, this type of search help has the constraint that you can only search for the technical name and description (or for a combination of two technical names as with the reference object storage location). In the QIM Web application, you cannot jump to the respective object in another system. If you create your own reference objects on the basis of IAMGOJ, you do not need to create your own BAdI definition; you can copy the enhancement implementation /IAM/ACCESS_GENERALOBJECT_NW for the delivered BAdI /IAM/BADI_GENERALOBJECT_CAT. In the copied enhancement implementation, you can reuse the delivered BAdI implementation /IAM/ACCESS_ERP_GENERALOBJECT with another filter value.

Navigation and Jumps From the QIM user interface, you can navigate to the assigned reference objects in the remote systems. Note, however, the following features for some delivered reference objects: If reference objects are located in an older system that does not support the display of Web applications (for example, SAP R/3 4.6C) and you are working with SAP NetWeaver Business Client for HTML, only restricted navigation is possible in the source system. For example, you cannot jump to other applications.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 35 of 106

For products (object category Material in NW , MAT_NW), only restricted navigation is possible in the source system for each release level for technical reasons. Retail articles and product groups are handled as ERP materials and belong to the object category MAT_ERP, that is, the data is displayed via the material master display (transaction MM03). No jump is supported for the following object categories: External reference object (GOJ_NW) Plant (PLANT_ERP)

Activities Entering Systems for Reference Objects In Customizing for QIM, you specify in which systems the reference objects are located (under Basic Settings Generic Settings for Reference Objects Define Object Access ). An easier means of maintaining object access is provided by a wizard, which you can find in Customizing for QIM under Start QIM Customizing Wizards .

Note The user that is stored in the RFC connection for the source system must have authorization to access the required object in the source system. In addition to object-specific authorizations, the underlying RFCs must be stored in the authorization object S_RFC. For information about which RFCs are relevant for which object, see the Customizing activity for object access in the settings for the object category under

( Implementation Information ).

Defining Other Reference Objects For more information about how you define additional reference objects, see SAP Note 1820834.

More Information Reference Objects for Issue Types Reference Objects for Activity Templates

1.4.8.1 Reference Objects for Issue Types As issues mostly arise in connection with other business processes, it is important to be able to assign issues the relevant reference objects, such as materials, customers, batch number, bills of material, and so on. For reference objects, a logical system must be specified that is the original system of the reference object.

Prerequisites You have made the settings for the object types in Customizing for Quality Issue Management under Objects .

Basic Settings

Generic Settings for Reference

Features You can specify the relevant reference objects for each issue type. In Customizing for Quality Issue Management, choose Issue Processing Types , Reference Objects folder. Here, you can specify a main reference object that is displayed in the header data of an issue.

Define Issue

All object types that you specified in Customizing for an issue type are available for you to specify as objects in the Reference Objects assignment block when you create an issue. For reference objects, you can also define access to subobjects that can be copied over to the issue when you select the corresponding reference object. For this to work, access to the dependent objects must be set up in Customizing under Basic Settings Generic Settings for Reference Objects Define Access to Dependent Objects . From this list, you can select the access to subobjects for a reference object of the issue type. When you create an issue, you can select the subobjects for an object using the Subobject function.

Example For the reference object material , access to the dependent objects batch and material was specified. When you select material as the reference object for an issue, you can select batches or a plant as subobjects for the material using the Subobject function.

1.4.8.2 Reference Objects for Activity Templates To be able to specify activities in connection with the relevant objects, it is necessary to assign the activities the relevant reference objects, such as materials, customers, batch numbers, bills of material, and so on. For reference objects, a logical system must be specified that is the original system of the reference object.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 36 of 106

Prerequisites You have made the settings for the object types in Customizing for Quality Issue Management under Objects .

Basic Settings

Generic Settings for Reference

Features You can specify the relevant reference objects for each activity template. In Customizing for Quality Issue Management, choose Activity Templates , Reference Objects folder.

Issue Processing

Define

All object types that you specified in Customizing for an activity template are available for you to specify as objects in the Reference Objects assignment block when you create an activity. The reference objects required by follow-up actions are automatically copied over to the activity without you having to specify the corresponding object types in Customizing.

1.4.9 Printing of Issues or Activities To print activities or issues, you use Adobe PDF forms. You make the settings for printing in Customizing.

Prerequisites In Customizing under

Issue Processing

Define Print Forms

, you have specified the print forms that can be used when printing an issue.

You have assigned the respective print forms to an issue type under Processing Define Activity Types .

Issue Processing

Define Issue Types

, or to an activity type under

Issue

Features Defaults set in Customizing: In Customizing, you can specify that printing is created as a separate activity and the PDF document is appended as an attachment: When you define the print forms, specify an activity template with which an activity for printing is then created. Specify a document type so that a PDF document can be appended to the newly created activity as an attachment. You can set a default country so that the print data is formatted using country-specific conventions.

Activities 1. Choose the print function when processing an issue or an activity. A dialog box appears showing the individual work steps. 2. Process the individual work steps.

1.4.10 E-Mailing of Issues or Activities To be able to send an issue or activity by e-mail, you must have configured the print settings in Customizing.

Prerequisites In Customizing under

Issue Processing

Define Print Forms

, you have specified the print forms that can be used when printing an issue.

You have assigned the respective print forms to an issue type under Processing Define Activity Types .

Issue Processing

Define Issue Types

, or to an activity type under

Issue

Features Defaults set in Customizing: In Customizing, you can specify that e-mailing is created as a separate activity and the PDF document is appended as an attachment: When you define the print forms, specify an activity template with which an activity for e-mailing is then created. Specify a document type so that a PDF document can be appended to the newly created activity as an attachment. You can set a default country so that the form can be formatted using country-specific conventions.

Activities 1. Choose the e-mailing function when processing an issue or an activity. A dialog box appears showing the individual work steps. 2. Process the individual work steps.

1.4.11 Additional Information in Side Panel PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 37 of 106

1.4.11 Additional Information in Side Panel When creating issues using the advanced create function, or when processing or displaying an issue, you can use the link Additional Information to open the side panel. The side panel can include various Web Dynpro CHIPs that relate to the object being displayed or processed in the main application. When processing issues, the following CHIPs are available: Notes Related Issues or Subissues When processing activities, you can only add notes. You can add further CHIPs yourself, for example, to enable collaboration using SAP Jam (Web Dynpro CHIP BSSP_SW_FEEDS). The prerequisite for this is that you have activated the business function Enable Social Media ABAP Integration 3 (BC_SRV_STW_03), which is available as of SAP NetWeaver AS ABAP 7.31 SP06. For more information, see the SAP NetWeaver documentation about Web Dynpro ABAP Page Builder under Enhancing Web Dynpro Applications with a Side Panel.

Integration The transfer of the ID for the current issue or activity to the CHIPs in the side panel for the context reference (tagging) is enabled via the Business Add-In (BAdI) BADI_QAM_GEN_APPL_CONTROLLER. For more information about the BAdI, see Customizing for QIM under Issue Processing Business Add-Ins (BAdIs) BAdI: Enhancement of QIM Web Dynpro Applications

.

Features Adding Notes In the Web Dynpro CHIP BSSP_NOTES, you can store public or private notes about the object currently being displayed or processed.

Reports for Related Issues or Subissues For more information, see Reports for Related Issues or Defects.

1.4.12 Change Documents Changes to an issue or activity in SAP Quality Issue Management are documented by means of change documents. You can open the change documents via the evaluation of the audit trail or display them when processing issues or activities via the issue or activity hierarchy. When you display them in the issue or activity hierarchy, all change documents for the selected object and its subordinate objects are displayed. All change documents are displayed for the selected object; only an aggregated view for the subordinate objects. You can use the external ID of the change document in the table to open the document in the audit trail.

Activities To open the change documents for SAP Quality Issue Management in the audit trail, proceed as follows: 1. Call the evaluation of the new audit trail in QIM under System Administration (transaction S_AUT10) in enhancement mode. 2. Enter the selection data and start the evaluation. A list appears containing all the change documents found that meet the selection criteria.

More Information See also Audit Trail

1.4.13 Workflow Scenarios for Issue Processing To improve the cooperation of all persons involved in processing an issue, you can set the system up to send notification e-mails or work items automatically following certain events. For this, you use the functions of SAP Business Workflow. The following scenarios are mapped as examples for the workflow objects delivered with QIM: The issue driver is informed when a new issue is created. He or she can then initiate relevant activities. The issue driver is informed as soon as all activities for an issue are completed. The issue driver can then validate the activities and close the issue. The activity driver is informed as soon as the activity processor sets the activity in process. In addition, you can create your own workflow templates and thus map other scenarios, such as the following: If the driver of an issue or activity was changed, you can notify the new driver. When certain status changes take place, for example, when an issue is created, set in process, or completed, you can inform interested parties. When an issue is created for which an approval is required, you can inform the approver. When an activity is completed, you can inform the interested parties and the drivers of the issue and activity.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 38 of 106

Prerequisites SAP Business Workflow is set up, and in particular, the automatic Customizing has been executed. You do this this in Customizing for SAP NetWeaver under Application Server Business Management SAP Business Workflow Maintain Standard Settings .

Features Delivered Objects Workflow templates and workflow objects are delivered to map the following workflow scenarios: Inform issue driver when an issue was created Workflow template WS56900008 (abbreviation Q Issue Info ) Inform issue driver when all activities are completed Workflow template WS56900002 (abbreviation Q Acty Compl ) Inform activity driver when activity is in process Workflow template WS56900003 (abbreviation Q Acty Proc ) You can open the workflow template in the Workflow Builder (transaction SWDD). For more information about the delivered objects, see Technical Implementation.

Delivery of Workflow Whether notification is by e-mail or by work item depends on the settings in the business partner master record for the respective partner (see also Partners in a QIM Issue): 1. If a user name is assigned to the business partner, the user receives a work item in the Inbox work center in QIM. 2. If no user name is assigned to the business partner, he or she receives an e-mail under the e-mail address stored in the business partner master record. 3. If no e-mail address is stored either, the workflow cannot be executed. A direct jump to the object is possible from the e-mail or the work item.

Activities If you want to use the delivered workflow templates and tasks, you must perform the task-specific Customizing. For more information, see Customizing for SAP QIM under Environment Activate Workflow . In addition, you can develop your own workflow templates using the standard tasks delivered with QIM. To do this, copy the delivered workflow templates in the Workflow Builder (transaction SWDD) and adapt your copies. When the workflows are active, you can activate logging via an event trace in the System Administration work center under Environment.

More Information For general information about SAP Business Workflow, see SAP Business Workflow: Reference Documentation in the documentation for SAP NetWeaver.

1.4.13.1 Technical Implementation The interface between SAP QIM and SAP Business Workflow is implemented by means of ABAP Objects . Communication takes place via Business Objects Processing Framework (BOPF) .

Object Types The following ABAP Objects classes are relevant as object types for the workflows: CL_QAM_ISSUE_WF_CONNECT CL_QAM_ACTIVITY_WF_CONNECT The events that trigger a workflow can therefore be all events of these ABAP Objects classes.

Standard Tasks The following standard tasks delivered with QIM can be edited in the dialog. For these standard tasks, you must ensure that they are classified as General Tasks . You do this in the task-specific Customizing or in the transaction PFTC under Additional Data Agent Assignment . The actual agent assignment is done via the respective partner role in QIM. Task

Description

Agent

TS 56907941

Process Issue

Issue Driver (expression &ISSUE_RESPONSIBLE_USER&)

TS 56907924

Check Issue Completion

Issue Driver (expression &ISSUE_RESPONSIBLE_USER&)

TS 56907929

Activity in Process

Activity Driver (expression &ACTIVITY_RESPONSIBLE_USER&)

In addition, there are delivered standard tasks that run in the background.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 39 of 106

The delivered standard tasks are available as modules and can be used unmodified in your own workflow scenarios.

Workflow Template The following workflow templates are delivered with QIM: Workflow Templates

Description

Triggering Event

WS 56900008

Inform Issue Driver About Issue

A new issue was created (CL_QAM_ACTIVITY_WF_CONNECT-CREATED)

WS 56900002

Inform Issue Driver About Activity Completion

All activities in the issue are completed

WS 56900003

Inform Activity Driver About Activity Processing

(CL_QAM_ACTIVITY_WF_CONNECT-COMPLETED) The activity driver has set the activity in process (CL_QAM_ACTIVITY_WF_CONNECT-INPROCESS)

You can use these workflow templates directly and also use them as the basis for your own workflow templates by copying and modifying them.

1.4.14 Issue Processing with Digital Signatures With the digital signature function, the QIM system provides you with a tool that allows you to sign and log business transactions, such as status changes, within the context of issue processing. The digital signature ensures that the signatory can be identified unambiguously and that the name of the signatory is documented together with the business transaction, date, and time. In Customizing, you can specify which business transactions must be signed and whether the signature is to be executed by one or more persons, synchronously, or asynchronously.

Example An issue can only be approved with the digital signature of the quality manager. An activity to start an escalation process can only be set in process by a digital signature from the quality manager and the escalation manager responsible.

Prerequisites 1. You have made the settings for the digital signature in Customizing for QIM under Environment Digital Signature . 2. In Customizing for the issue type, you have specified the business transactions for which a digital signature is required. You do this in Customizing for QIM under Issue Processing Define Issue Types .

Features You can activate the digital signature for business transactions when processing issues and activities. To do this, you specify in the issue type or the activity type how the signature process is to be executed. In addition to an individual signature, a signature process with several signatories is possible. This signature process can run synchronously or asynchronously.

Note In SAP QIM, you can only use signature strategies to which a system signature based on user ID and password is assigned as the signature method. The digital signature is only possible when creating issues using the advanced create function, when changing issues, or when processing activities. The signature is automatically queried when the user attempts to execute the business transaction. A dialog box appears in which the signature must be entered. With a synchronous signature process, the various signatories must provide their signature directly one after the other in the application. Only when the last required signature has been executed can a new application be called, otherwise the whole signature process is invalid. With an asynchronous signature process, the signatories can provide their signature independently of one another at their own workplace. Each user authorized to provide a signature within a signature strategy who has not yet signed the respective object can cancel a signature process. The signatures that were already executed are then revoked and the object returns to the status that it had before the start of the signature process. The signature process – and also a cancelation of the process – is documented in the system. You can display the log in the issue or activity hierarchy when processing issues or activities. You can also open the logs under System Administration Environment (see also Environment). Using the Worklists for Quality Issues and Quality Activities, you can list the issues and activities for which a digital signature is required.

More Information For more information, look up the keyword Digital Signature (CA-DSG) at http://help.sap.com.

1.4.15 Problem Analysis Using 8D Methodology You can conduct a problem analysis in SAP QIM according to the 8D methodology by creating and processing a QIM issue with the issue type 8D Problem Analysis . To ensure that the eight disciplines in 8D are covered, an 8D problem analysis is divided into steps. The user interface for 8D problem analysis differs from the user interface for the processing of other QIM issues. There is a separate screen area for each discipline. To create an 8D problem analysis, you have different options: You can create it directly by choosing the issue type for an 8D problem analysis under

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Create

Quality Issue (Advanced)

.

Page 40 of 106

You can trigger a problem analysis for a defect that, for example, belongs to a QIM issue with the issue type Customer Complaint . Here, you create a follow-up issue, for example, with the issue type 8D Problem Analysis . In this case, some fields are automatically copied from the customer complaint or the defect to the 8D problem analysis. For more information, see below in the process description. You can also link a directly created 8D problem analysis with an existing defect. You can use the method framework delivered with 8D (for example, the option to divide an issue into steps) to implement other problem-solving methodologies. For more information about the technical implementation of 8D in SAP QIM, see 8D: Technical Implementation.

Prerequisites The Customizing necessary for the 8D methodology (for example, the issue type 8D Problem Analysis (Q8D) is delivered via BC Sets. To be able to use the delivered Customizing settings, you must activate the BC Sets in Customizing for QIM under BC Sets for 8D .

Issue Processing

Problem-Solving Methodologies

Activate

If you want to use the delivered Customizing for a Defect with Problem Analysis (issue type QDP), you must also exchange the usual issue type for Defect (QDF) when defining hierarchies of issue types (in Customizing for QIM under

Issue Processing

Define Issue Types

Subitems

). This allows you, for

example, to create an 8D problem analysis (issue type Q8D) as a follow-up issue from the issue type for customer complaints (QI1) at defect level (issue type QDP).

Process The following process describes how to create an 8D problem analysis when it is created for a defect: 1. When processing a defect, for example, a customer complaint, you can trigger or assign an 8D problem analysis. 2. To first identify any similar QIM issues or defects that may have the same material as a reference object or the same code as the defect, you can search for related issues or defects in the side panel. To do this, select the defect and choose Additional Information . For more information, see Reports for Related Issues or Defects. If you find a suitable 8D problem analysis, you can assign the current defect to this existing problem analysis under Referenced Defects if required. 3. To create a new 8D problem analysis, choose Trigger Problem Analysis . For creating the problem analysis, all issues types are available that are entered in Customizing for the issue type of the defect under Follow-Up Issues . 4. When you create an 8D problem analysis as a follow-up issue, some data is filled automatically; you can add other data manually. More information about the individual screen areas: In the Issue Overview , the system automatically copies the dates for the requested start and requested end from the original issue, for example, the customer complaint. The main reference object is the material of the defect from the customer complaint. The defect is also entered automatically as the referenced defect. If the problem analysis is relevant for other similar defects, you can also assign these. In the step D1 – Team , you enter the members of the problem-solving team by specifying the partner roles and business partners. In the step D2 – Problem Description , the system copies the data (for the codes and description, for example) from the defect. You can overwrite this copied data. In the step D3 – Containment Action(s) , you can create immediate containment actions for the 8D problem analysis using a quick entry function. The system uses the activity type or activity template that you stored in Customizing for the respective step. The end date of this step is set automatically when all activities are completed. If you have done a root cause analysis of the defect, you can enter the root causes in the step D4 – Root Causes . Technically, the system creates causes with the issue type Cause for Problem Analysis (QCP) (subitem of the 8D issue type). For each cause, you can specify under % Contribution which portion of the defect was contributed by each cause.

Recommendation You can save the documentation of your root cause analysis as an attachment to the 8D problem analysis in the QIM system. For each cause, you can specify activities for remedying the cause of a defect in the step D5 – Chosen Permanent Corrective Action(s) . When planning is completed, you can use the copy pushbutton with the quick info Implement Activity to copy the activity to the D6 step. Technically, this creates a new activity for which some of the data is copied. The D5 activity is then set to Completed by the system. The end date of this step is set automatically when all activities are completed. The step D6 – Implemented Permanent Corrective Action(s) includes the activities that you introduced in the D5 step. With the exception of the status, date fields, and the attachments, the system copies all data from the corresponding D5 activity. You can add other activities manually. The end date of this step is set automatically when all activities are completed. In the step D7 – Action(s) to Prevent Recurrence , you can define activities: in this case, however, at the level of the 8D problem analysis. Here, the activities that you entered in Customizing for the 8D issue type under Automatic and Proposed Activity Templates are listed automatically. The end date of this step is set automatically when all activities are completed. To wrap up an 8D problem analysis, you can enter an assessment of the resolution in the step D8 – Congratulate Your Team . Here, you can also set the end date of the 8D problem analysis. Under Documentation , the PDF forms are stored that you created during the course of the process by printing or e-mailing an interim status of the problem analysis or the final 8D report (see also 8D Report). Under Attachments , you can assign other documents to the 8D problem analysis, such as documents relating to the defect analysis. 5. For all activities in the 8D process, you can enter the effectiveness in percent and store a free text for the verification of the result. If you want to do this at a later date, you can assign the validation status Effectiveness Check Outstanding for the 8D problem analysis. An activity with this status cannot be archived. 6. If you want to process specific activities within an 8D problem analysis, it is possible to select by steps in the worklist for activities.

Result You can print out the results of the 8D problem analysis or send them by e-mail using a special PDF form for 8D reports. For more information, see 8D Report.

1.4.15.1 8D: Technical Implementation PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 41 of 106

Technically, an 8D problem analysis is a QIM issue with a special issue type for 8D problem analysis (Q8D). For this issue type, steps are delivered in Customizing for QIM under Issue Processing Problem-Solving Methodologies Define Steps for which you can make other settings (for example, assign timepoints). Each step corresponds to an 8D discipline. To enable the eight disciplines or steps to be displayed on the user interface, a dedicated Web Dynpro application configuration is delivered for the 8D issue type (QIM_OVP_8DISS). This application configuration is assigned to the issue type Q8D in Customizing for issue types.

More Information For technical background information about the concept of the QIM Web applications, see Adaptation of the Web Applications in QIM.

1.4.15.2 8D Report To print the result or interim versions of the 8D problem analysis or send them by e-mail, a special PDF-based print form is available for 8D reports. You can use the 8D print form when printing or mailing from the 8D problem analysis or from the underlying customer complaint. If several defects are assigned to the 8D problem analysis or the customer complaint, you can choose which defects are to be included in the 8D report (if you made the respective settings in Customizing). If you select several defects, an 8D report is created for each defect in which some data is taken from the defect and some data is taken from the 8D problem analysis (see below in the Features section for more information). The 8D reports for all selected defects are output consecutively in a PDF document.

Prerequisites You have made the settings for the print form in Customizing for QIM under Issue Processing Define Print Forms . For the issue type 8D Problem Analysis (Q8D), the print form I8D is delivered in the 8D BC Set. The PDF-based form QAM_ISSUE_8D is assigned to this print form. For this print form, for example, you can specify whether you can select the defects in the print dialog that are to be included in the 8D report. If you want the printed forms to appear under Documentation in the problem analysis, you must assign an activity template and a document type.

Features You can create an 8D report directly from the 8D problem analysis or from the underlying customer complaint. In both cases, you must select the respective print form for 8D reports in the dialog box for printing or e-mailing. If you create the 8D report from the customer complaint, the data is taken partly from the original customer complaint, partly from the defect, and partly from the 8D problem analysis. If you create the 8D report from the 8D problem analysis and referenced defects are assigned to it, some data is also taken from the defect. Which data comes from where is shown in the following table: Field/Screen Area

Origin in 8D Report Without Reference to Defects

Origin in 8D Report With Reference to Defects – If Different

Title Block Bar code Logo

Issue ID of 8D problem analysis as bar code type EAN128 Object Navigator (transaction SE80) Repository

PUBLIC

QIM

MIME

LOGO_8D.bmp

8D Report

Fixed title

Type

Text for issue type of 8D problem analysis

External Reference No.

The first External Reference Object (object type GOJ) in

The first External Reference Object (object type GOJ) in

the reference object list of the 8D problem analysis

the reference object list of the parent QIM issue (for example, customer complaint)

Progress

Shows the progress status of each D step as a color code: White: Requested end date is not defined Gray: Requested end date is defined, end date is open Yellow: Requested end date lies one day before today's date Green: Requested end date lies before or is identical to the end date Red: Requested end date is later than the end date/current date

Start Date

Start date from the issue overview and the D8 step of the 8D problem analysis (date fields of the steps are identical)

Report Date

Current printing date

Header Data 8D Title

Issue description (short text) of 8D problem analysis

Material

Main reference object Material of 8D problem analysis

Issue description (short text) of 8D problem analysis of parent QIM issue (for example, customer complaint)

Material No. Customer Customer No.

Reference object Customer (object type CUS) of 8D

Reference object Customer (object type CUS) of parent

problem analysis

QIM issue (for example, customer complaint)

Contact (at customer, incl. contact data)

First business partner with partner role CONTACT of 8D

First business partner with partner role CONTACT of parent

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 42 of 106

problem analysis

QIM issue (for example, customer complaint)

D1 – Team Role First Name Last Name E-Mail Telephone

Business partner from 8D problem analysis

Department

Department entered in SAP user of business partner

D2 – Problem Description Issue description

Issue description (short text) and detailed description (long Issue description (short text) and detailed description (long text) of 8D problem analysis text) of referenced defect

Defect Code Defect Location

Code group and code of respective fields of 8D problem analysis

Code group and code of respective fields of assigned referenced defect

Number of Parts Affected

Defect quantity from No. of Occurrences field in 8D problem analysis

Defect quantity from No. of Occurrences field in referenced defect

Data on all activities from the D3 step of the 8D problem analysis

Data on all activities from the D3 step of the 8D problem analysis and on all activities of the referenced defect

D3 – Containment Action(s) Containment actions

D4 – Root Cause(s) Root causes of defects

Data on all causes from the 8D problem analysis

D5 – Chosen Permanent Corrective Action(s) Per cause: Chosen permanent corrective actions

Data on all activities from the D5 step of the 8D problem analysis

D6 – Implemented Permanent Corrective Action(s) Per cause: Implemented permanent corrective actions

Data on all activities from the D6 step of the 8D problem analysis

D7 – Action(s) to Prevent Recurrence Actions to prevent recurrence

Data on all activities from the D7 step of the 8D problem analysis

D8 – Congratulate Your Team Result

Issue assessment from 8D problem analysis

Close Date

Completion date from the issue overview and the D8 step of the 8D problem analysis (date fields of the steps are identical)

Activities 1. In the 8D problem analysis or customer complaint, choose the icon for printing or sending e-mails. 2. Select the form for 8D reports (I8D). 3. Select the images that you want to be included at the end of the 8D report.

Note The images from the underlying customer complaint are not included in the 8D report and are thus not available for selection. 4. If the relevant indicator is set in Customizing for the print form, you can select the defects for which the PDF document is to be created. When printing or mailing from the 8D problem analysis, the referenced defects from the 8D problem analysis are available for selection. When printing or mailing from a customer complaint, the defects from the customer complaint are available for selection. 5. When mailing, you can choose which of the attachments that were added in the various 8D steps should be attached to the e-mail. 6. The created PDF document is then displayed in the print preview. 7. Only if you actually print or send the PDF document is an activity with the PDF document added to the 8D problem analysis as an attachment under Documentation .

More Information Problem Analysis Using 8D Methodology

1.5 System Administration Work Center In the System Administration area, a coordinator in SAP Quality Issue Management can make settings in the productive system.

Prerequisites The System Administration area is available only to users with the role of coordinator.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 43 of 106

Features In the standard system, the following settings are possible under System Administration : Process Control Enables the user to make settings that are relevant for issue processing. Configure Rules Enables the user to configure rules, for example, for partner or activity determination. Communication with External Systems Enables the user to make mapping settings and monitor data transfer. Audit Trail Enables the user to manage the logging of changes in the system. Environment Enables the user to access messages in the application log and workflow settings. System Settings for Reporting Enables the user to define reports and queries in Business Context Viewer. If you want other setting options to be available under System Administration , you must change the relevant launchpads. You do this in Customizing for QIM under Environment Set Up Launchpads (see also Launchpads in QIM).

1.5.1 Process Control As coordinator for SAP QIM, you can check some of the settings relevant for issue processing in the System Administration work center.

Features You can do the following: Call Customizing settings for codes and catalogs (see Codes and Code Groups) Display Customizing settings for issue type (see Overview: Creating Quality Issues) Make settings for business partners (see Partners in a QIM Issue) Display the Customizing settings for activity templates and display an activity hierarchy graphically as an activity network (see Activity Templates)

1.5.2 Configure Rules As coordinator for SAP QIM, in the System Administration work center you can use Business Rule Framework plus (BRFplus) to define rules for the determination of partners, activities, and codes or code groups. BRFplus is a Web-based application in which you can define rules and specify parameters in decision tables.

Features You can set up the following rules: Determination of Activities Using BRFplus Determination of Partner for Issues Using BRFplus Determination of Partner for Activities Using BRFplus Determination of Codes and Code Groups Using BRFplus For more information about BRFplus, see Business Rule Framework plus (BRFplus). You can find the documentation for BRFplus under SAP NetWeaver Library SAP NetWeaver Library: Function-Oriented View Application Server Application Server ABAP Other Services Services for Application Developers Business Rule Framework plus .

Note The documentation for BRFplus exists in English only.

1.5.3 Communication with External Systems As coordinator for SAP QIM, you can make some settings for system integration in a running system and monitor the communication in the System Administration work center.

Features Monitoring To monitor communications, you can open and manage the logs for system access. This is possible for access to issues and activities in the worklists and for reference objects for QIM issues (under Access Object Types ). The same settings are also possible in Customizing for QIM.

Mapping

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 44 of 106

You can make settings for structure mapping and ID mapping. You can access the Service Mapping Tool (SMT) and make settings for structure mapping. You can assign this structure mapping in Customizing for QIM in the settings for access to object categories (for reference objects and for objects in the worklist). The assignment is possible for the object category in general or for specific systems. For more information about structure mapping, see the example relating to worklists under Structure Mapping. In a nonharmonized system landscape, you can store a key mapping for individual values. For more information, see ID Mapping. For more information about the procedure for editing the ID mapping, see Creation, Editing, and Deletion of Key Mapping Information.

1.5.4 Audit Trail As coordinator for SAP QIM, you can make settings for the logging of data changed in SAP QIM in the System Administration work center. You can also evaluate the logged data. The functions of the Audit Trail component are available for this.

Features The following change document objects are relevant for SAP QIM: /IAM/ISSUE /IAM/ACTIVITY For information about the functional scope, see the documentation for the Audit Trail component under Audit Trail (BC-SRV-ASF-AT).

More Information Change Documents

1.5.5 Environment As coordinator for SAP QIM, you can access various logs and make workflow settings in the System Administration work center.

Features Application Log For information about the functional scope when displaying logs, see the documentation for the application log under Displaying Logs.

Workflow You can make settings for workflow tasks and assign agents for them, for example. In addition, you can activate the logging of workflow events (event trace) and display the results of the trace.

Digital Signature You can access logs for the digital signature. The following applications and signature objects are relevant for QIM: Application

Signature Object

IAM: Quality issue/Change request

Quality issue

IAM: Quality activity/Activity

Quality activity

For more information, look up the keyword Digital Signature (CA-DSG) at http://help.sap.com.

Archiving You can access Archive Administration and make all settings for archiving activities and issues. For more information, see Archiving QIM Data.

1.5.6 System Settings for Reporting As coordinator for SAP QIM, you can define and manage reports in the System Administration work center. To do this, you use the configuration center of Business Context Viewer (BCV).

Prerequisites You have activated the following business functions: BCV_MAIN BCV_MAIN_01 You have made the necessary settings for the query cache. For more information, see Customizing for QIM under Viewer .

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Environment

Configure Business Context

Page 45 of 106

Viewer

.

Features For information about the functional scope of the BCV configuration center, see the documentation for BCV under Configuration Center.

Note Via the PFCG role SAP_BCV_ADMIN2, you have access to additional administration functions.

1.6 Enterprise Search With Search and Operational Analytics, SAP NetWeaver provides a common technical infrastructure that supports and harmonizes data provisioning for analytics and also for searching data. Within this, Enterprise Search offers a central point of access to find structured and unstructured business data in your current system using a search screen. Structured business data can be business objects, such as QIM quality issues; unstructured data can be documents, such as attachments to a quality issue.

Example In the basic search, you can search for the string SMITH and get a result list with all occurrences of this term, for example, all issues that a user SMITH processed in any way or all issues in which the name Smith appears in the attachment.

Prerequisites For all objects that you want to search using Enterprise Search, you have created connectors and indexed the data in the transaction ESH_COCKPIT. The basis for this are search and analytics models. For information about the search and analytics models that are delivered with SAP QIM, see Search and Operational Analytics: Content for SAP QIM. For more information about the settings required, see Customizing for QIM under

Search and Analytics

Configure Search

.

Features For information about the default search options in the basic search, see the SAP NetWeaver documentation about search and operational analytics under Searching.

Note Note that in the Enterprise Search version that SAP QIM uses, the terms AND and NOT are not operators, but are also searched for as strings. You should therefore use a plus sign (+) for AND operations or no operator, and a minus sign (-) instead of NOT to exclude terms. To refine the search, you can enter values for various search criteria under Advanced Search . Here, the selection options for a search criterion are dynamically adapted to the values already selected for other criteria. Note here that different search criteria are linked with AND. However, if you enter the same search criterion twice, the corresponding values are linked with OR. This is relevant particularly when searching for reference objects. If you want to search for different reference objects for an issue, you must use the specific search criterion (for example, Reference Object Material ) and not the general criterion Reference Object .

Example If you want to search for issues that have a particular plant and a particular customer as reference objects, proceed as follows: 1. 2. 3. 4.

Filter according to the category in which you want to search. This displays several of the search criteria that are relevant for this category. As your search criterion, select Reference Object Plant and select a specific plant. If required, add an additional row using the plus sign after the input field. As your search criterion, select Reference Object Customer and select a specific customer. Only those customers are available that are assigned to issues to which the plant you already selected is also assigned.

If you want to search for issues in which either the plant or the customer is assigned, you can insert the search criterion Reference Object twice and select the respective values.

More Information Getting Started – Using the Search

1.7 Reports You can evaluate issues and activities with different objectives: The evaluation of context-sensitive information when processing an issue by analyzing related issues for the same reference objects such as material and customer to recognize any systematic defects or trends in the process The comparison of frequencies of defects or numbers of different status values for issues of all types

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 46 of 106

Regular analyses and reports for management To meet these objectives, queries, evaluations, and dashboards can be created centrally by an administrator. Users can also integrate their own personal favorites and reports. They can use predefined queries for evaluating issues and activities, add their own queries and reports, or integrate links to further information (for example, navigation to a transaction in a connected system).

Features Reports in QIM are mainly possible using the following technologies: Business Context Viewer (BCV) BCV reports are integrated into the QIM home page and in the Worklists for Quality Issues and Quality Activities. For more information, see Reports in Business Context Viewer. Search and Operational Analytics For operative reporting, you can define your own BI queries on the basis of supplied Operational Data Providers (ODPs) as part of search and analytics models. For more information, see Reports Using Search and Operational Analytics. CHIPs in the side panel You can call up context-sensitive information about an issue that you are displaying or processing by displaying the side panel using the Additional Information link. Various CHIPs are available in the side panel, for example, for Reports for Related Issues or Defects. You can add other CHIPs. For more information, see Additional Information in Side Panel. Reports and transactions in connected systems For more information, see Reports in Other Systems.

1.7.1 Reports in Business Context Viewer (BCV) BCV in SAP QIM offers a framework that allows different types of additional information to be integrated in the application. This information can then be analyzed according to the business requirements of the user. For more information, see the documentation for Business Suite Foundation under Business Context Viewer (BCV).

Prerequisites If you are assigned to the PFCG role SAP_BCV_ADMIN2, you have a wide range of configuration options available. For more information about the settings necessary for using BCV, see Customizing for QIM under .

Search and Analytics

Configure Business Context Viewer

Features Side Panel You can open context-sensitive query views in BCV in the side panel of the QIM worklists by selecting entries in the list of worklists and choosing Additional Information . You then have access to the functions of the BCV side panel, which are described in detail in the documentation for BCV under Side Panel. For example, individual key figures are displayed directly in graphical form in the side panel overview. You can enlarge each key figure in the main window and use other BCV functions there. For detailed analyses, you can display groups of query views as dashboards. You define the required queries and key figures in the BCV configuration center. Here, you also specify the display format of the results and key figures in the form of a query view, for example, as a graphic or in table format. You also use the BCV configuration center to group several query views in a dashboard. For more information, see the documentation for BCV under Configuration Center. To display key figures in an overview and in a dashboard, business content in the form of queries, query views, and a dashboard is delivered for QIM. You can adapt and extend this business content. For example, you can use your own queries to determine the data so trends can be displayed.

CHIPs You can also integrate BCV queries into the QIM user interface as CHIPs. As an example, a graphic is available on the home page, showing the number of issues by priority and status. For more information about this example, see Example: BCV Query via BAPI Search Connector.

1.7.1.1 Example: BCV Query via BAPI Search Connector As an example of a BCV query for a BAPI search connector, a CHIP is integrated in the QIM home page that shows the number of issues by priority and status as a graphic.

Features Technically, the BCV query 1QAM_ISSUE_PRIORITY_LC is delivered for this graphic. This query uses the BAPI search connector 1QAM_ISSUE_PRIO_LC.

Note Note that the search connector only provides the fields Priority , Status , and Number of Issues . To display other result fields, you must define a new search connector. You can use the search connector supplied as a template.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 47 of 106

Note also that, for performance reasons, the search connector for the class CL_QAM_BCV_SIN_DS_QAM_ISSUES only provides the fields to which a meaning has been assigned. The BAPI search connector provided uses the DataSource 0QAM_ISSUES for access. Therefore you must activate this DataSource in the transaction RSA5.

1.7.2 Reports Using Search and Operational Analytics With Search and Operational Analytics , SAP NetWeaver provides a common technical infrastructure that supports and harmonizes data provisioning for analytics and also for searching data. For operational reporting, you can use Operational Analytics with Operational Data Provisioning. The Operational Data Provider (ODP) 0QAM_ISSUES, which is part of the search and analytics model 0QAM_ISSUES, is available for the definition of analytical queries for operational reporting.

Prerequisites 1. You have activated the DataSource 0QAM_ISSUES. You do this in the transaction RSA5. 2. You have created a connector for the search and analytics model 0QAM_ISSUES in the transaction ESH_COCKPIT.

Features When you have created a connector for the search and analytics model 0QAM_ISSUES, you can define analytical queries with the Business Explorer (BEx) Query Designer. The TransientProvider 2O0QAM_ISSUES, generated at runtime, is available as the InfoProvider. For more information about creating analytical queries for operational reporting, see the documentation for SAP NetWeaver under: Using Analytic Queries for Operational Data Providers BEx Query Designer

More Information Search and Operational Analytics: Content for SAP QIM

1.7.3 Reports for Related Issues or Defects When creating issues using the advanced create function, or when processing or displaying an issue, you can use the link Additional Information to open the side panel, where graphics appear showing the issues and the defects that are related to the current issue or a selected subitem (for example, a defect or a cause). The link can be a common reference object or the code. The graphics are updated depending on the context. If no subitem is selected, the related issues or defects displayed in the graphic are related to the issue being processed. You can use this feature, for example, to identify an existing 8D problem analysis that fits for a defect, which you can then assign to the defect. For more information, see Problem Analysis Using 8D Methodology.

Integration Technically, the report is provided by the CHIP Related Issues or Subissues (QAM_RELATED_ISSUES), which is called once for issues and once for defects. The common parameters used for selection in the CHIP are stored in the back-end system, for example, the reference objects customer and material , or the code. If you wish to add additional reference objects, enhance the structure QAMS_REL_ISSUES_DYNAMIC and the selection and result structure of the BOPF query SELECT_ISSUES_FOR_CONTEXT for the business object /IAM/ISSUE. For more information, see the documentation for the class /IAM/CL_I_Q_SEL_FOR_CONTEXT.

Features The QAM_RELATED_ISSUES CHIP displays the related issues in a portfolio graphic that takes into account the time interval between the related issues and the number of parameters that do not match (parameter distance). A circle represents a group of issues, in which certain parameters match. If the CHIP is passed a material and a code, for example, a maximum of three circles can be displayed: A circle with the parameter distance 0, that encompasses the issues that have the same material and the same code A circle with the parameter distance 1, that encompasses the issues that have the same material only A circle with the parameter distance 1, that encompasses the issues that have the same code only The size of the circles displayed depends on the number of issues with matching parameters. When you select a circle in the graphic, the corresponding related issues or defects are listed in a table below the graphic. You can display detailed information about the related issues via a link. In the side panel editor, you can configure the timeframe for selection and a table view of the data. For information about calling the side panel editor, see the SAP NetWeaver documentation about Web Dynpro ABAP Page Builder under Embedding the Side Panel.

1.7.4 Reports in Other Systems

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 48 of 106

In the Reports work center, reports in the connected systems are available to you. Here you can evaluate notifications, audit issues, or FMEA defects in the transactional system (such as SAP ERP), for example, or – if available – in SAP NetWeaver BI.

Prerequisites You have defined RFC destinations for the systems in which the reports and transactions are to be opened. To use the delivered entries, the following RFC destinations (connection type H) must exist: SAP_ERP_QualityManagement SAP_BW

Activities In addition to the delivered reports, you can add additional reports and transactions by extending the appropriate launchpad in Customizing for QIM under Environment Set Up Launchpads (role QIM, instance REPORTS). Here you must store the RFC destination of the connected system as the system alias. For more information, see Launchpads in QIM.

1.8 Technical System Integration One important feature of SAP Quality Issue Management is the option of integrating objects beyond system boundaries. This is relevant particularly for the following functions: Worklists for quality issues and activities Assignment of reference objects

Features General Features To enable the integration of different objects and systems, the objects in SAP QIM were decoupled from a specific data model. For this, object types were defined in SAP QIM. For all object types, abstract definitions were stored in the business object layer (BOL) via the geNIL Model Editor (transaction GENIL_MODEL_EDITOR). The following genIL components are relevant for SAP QIM: Worklists Quality issue: QAM_QI Quality activity: QAM_QA Quality issue type: QAMQIT Reference objects (examples) Material: IAMMAT Plant: IAMPLA Customer: IAMCUS Vendor: IAMVEN Document: IAMDOC In SAP QIM, the object types are subdivided into object categories. Access to the specific objects in the source systems is technically executed by categorydependent implementations of Business Add-Ins (BAdIs): The system accesses the business object layer (BOL) via the object category. The BOL calls the genIL component, which in turn calls the category-dependent BAdI implementation. Depending on the object category, the system accesses an object with a specific data model. This object may be located in another source system, such as an SAP ERP system, or it may be located in the same system.

Setting Options You make the settings for the object types and object categories in Customizing for QIM, depending on whether the settings are for worklists or reference objects: Worklists: Worklists for Quality Issues and Activities Reference objects: Basic Settings Generic Settings for Reference Objects The technical implementation is the same in both areas. You specify for an object category which system is to be used to display the data, for example. For more information about the setting options, see the documentation for the respective Customizing activities.

Mapping The assignment of the different data models is done via structure mapping. This is stored in Customizing for the object category. For more information, see the example relating to worklists under Structure Mapping. For nonharmonized systems, you can also store an ID mapping (key or value mapping). For more information, see ID Mapping.

More Information Connection of Systems in a Side-by-Side Scenario Setting Up System Connections

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 49 of 106

1.8.1 ID Mapping In a nonharmonized system landscape, you can store a key or value mapping for individual IDs (keys or values) so that the data is displayed in a harmonized manner in a QIM system. The ID mapping is done between the source system and the reference system specified for the respective object type. After a successful ID mapping, the value from the reference system is displayed in QIM. Key mapping is relevant for master data. If you assign a reference object, whose values do not match in the various systems, to a QIM issue, you can store a mapping. Value mapping is relevant for Customizing data. If you want to make a selection across different issue types in the worklist (see Selection Criteria), you can store a mapping in Customizing.

Integration For ID mapping, functions in the Master Data Governance component are used: Key mapping Value mapping

Prerequisites You have activated the business function MDG_FOUNDATION.

Activities Key Mapping 1. Make the following settings for each object type in Customizing for QIM under Basic Settings Generic Settings for Reference Objects Define Object Access : Reference system: The values from the other systems are mapped to this system. If you do not enter a system, the local system is the reference system. Reference system category: Select an object category that is supported in the reference system, for example, MAT_ERP in an ERP system. The system uses the data model and the respective API for the reference system category for access to the objects. Provider of list agency ID: We recommend that you specify the local system with its logical systems.

Note Alternatively, a coordinator can make the settings for the object type in the System Administration work center under Systems Access Object Types .

Communication with External

2. In the same Customizing activity, specify in the system-dependent settings for an object category whether an ID mapping is required. 3. In the System Administration work center under Communication with External Systems Edit ID Mapping , specify the assignment of the values. 4. To check whether a mapping to the reference system was done, you can display the Local column in the worklist. This column shows an indicator that is set if the ID field shows the key from the source system and not from the reference system.

Value Mapping For value mapping for the issue types, proceed as described in Customizing for QIM under Quality Issue Types .

Worklists for Quality Issues and Activities

Define Access to

1.8.2 Setting Up System Connections To be able to display objects from other SAP systems in your QIM worklist or to be able to assign reference objects from other systems to QIM objects, you must first set up the connection to the relevant system.

Procedure 1. Define a logical system for the local QIM system. You do this in Customizing for SAP NetWeaver under Application Link Enabling (ALE) Basic Settings Logical Systems Define Logical System .

Application Server

IDoc Interface /

Example If you are running SAP QIM in system QIX, client 000, you name the logical system QIXCLNT000. 2. In the same Customizing activity, you define logical systems for all systems that you want to connect to SAP QIM. 3. Assign all the logical systems you just created to their respective client. You do this in the same section of Customizing for SAP NetWeaver in the Customizing activity Assign Logical System to Client . 4. Create RFC connections for the logical systems you created. You do this in Customizing for SAP NetWeaver under Application Server IDoc Interface / Application Link Enabling (ALE) Communication Create RFC Connections . The following RFC connections are required: Under ABAP Connections , create an RFC destination for the local QIM system with the connection type 3.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 50 of 106

For all source systems that you want to connect to the QIM system, also create RFC destinations with connection type 3. Also, under HTTP Connections to ABAP System (connection type H), create an RFC connection with the same name plus the suffix _HTTP for all source systems. This is required to call applications via object-based navigation. 5. Ensure that the user who is stored in the RFC connection has authorization to access the objects in the source system. In addition to object-specific authorizations, the underlying RFCs must be stored in the authorization object S_RFC. For information about which RFCs are relevant for which object, see the various Customizing activities for object access in Customizing for QIM: Reference objects: Basic Settings Generic Settings for Reference Objects Define Object Access Worklists: Worklists for Quality Issues and Activities Define Access to In the respective Customizing activity, you can access the relevant information in the settings for the object category by choosing ( Implementation Information ). 6. Assign the RFC connections to the logical systems. You do this in Customizing for SAP NetWeaver under Application Server IDoc Interface / Application Link Enabling (ALE) Communication Determine RFC Destinations for Method Calls . There, you select the logical system and choose Standard BAPI Destination . 7. Specify which object is to be read from which system. You do this in the Customizing activities for object access in SAP QIM: Reference objects: Basic Settings Generic Settings for Reference Objects Define Object Access Worklists: Worklists for Quality Issues and Activities Define Access to In the system-dependent settings for an object category, enter the logical systems from which the respective object is to be read and then set the Active indicator. An icon shows whether the QIM system supports access to the specified logical system.

Note To support you with setting up the system connections, various wizards are available in Customizing for QIM under

Start QIM Customizing Wizards

.

1.9 User Interface Adaptation You can adapt the user interface at different levels to the requirements of your enterprise.

Features The following adaptations are possible: Change navigation structure You can change the appearance of the navigation structure by adapting the role menu in the transaction PFCG. For more information, see Adaptation of the Role Menu. Adapt work center pages (for example, Home, System Administration) You can change the SAP QIM work center using the functions of the Web Dynpro ABAP Page Builder. For example, you can move, delete, or add individual blocks (CHIPs). These changes can be made at different levels with different ranges of coverage: Personalization: Only visible for the respective user Customizing: Visible throughout the client Configuration: Visible throughout the system For more information, see Adaptation of the QIM Work Centers. Allow access to other applications Many applications in SAP QIM are made available via CHIPs of the type launchpad link list . You can change these launchpad link lists in Customizing. For more information, see Launchpads in QIM. Change layout of worklists You can change the layout of the worklist page overall and also change the layout of each individual list of worklists. For more information, see Layout. Change applications for processing issues and activities You can change the Web applications by hiding individual fields or whole blocks or specifying default values, for example. In the guided application, you can hide whole steps. The changes can also be made at different adaptation levels (personalization, customizing, configuration). In the configuration, you can also make context-based adaptations and thus display the same application differently for the issue driver and the issue submitter, for example. For more information, see Adaptation of the Web Applications in QIM. Assign issue type-specific application configuration You can assign a specific application configuration to an issue type. This allows you to vary the user interface for the processing of issues of an issue type without context-based adaptations. You assign the application configuration in Customizing for QIM under Issue Processing Define Issue Types in the Configuration ID field. Redefine terminology You can adapt messages, texts for object types, and interface texts to the terminology commonly used in your enterprise. For more information, see Terminology Redefinition. Create user statuses Using additional pushbuttons, you can add new functions such as a new status. For more information, see User Status. Link to help documents You can create links to your own documents via the Help Center. For more information, see the documentation for NetWeaver AS ABAP under Utilizing the Help Center for SAP Business Suite Applications.

More Information Web Dynpro Personalization and Customizing Web Dynpro Configuration

1.9.1 Adaptation of the Role Menu

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 51 of 106

SAP NetWeaver Business Client (NWBC) is the user interface for SAP QIM. In NWBC, the menu for a role that is stored in the transaction PFCG determines the navigation structure and the call of other applications via object-based navigation (OBN).

Features For detailed information about the interaction between the settings in the transaction PFCG and the display in NWBC, see the documentation for NWBC under 5 Role Maintenance in PFCG.

Note The documentation for NWBC exists in English only. You can also make further changes via an entry in the role menu in the transaction PFCG by starting personalization, customizing, or configuration. To do this, choose Details in the context menu of a node.

More Information Web Dynpro Personalization and Customizing Web Dynpro Configuration

1.9.2 Adaptation of the QIM Work Centers The work centers serve as a central point of access for different tasks that can be performed in QIM. They help to structure your work. This structure can be adapted to fulfill the requirements of your enterprise and of each individual user.

Features The work centers in QIM are defined as pages in the Web Dynpro ABAP Page Builder. Technically, they are page configurations of the Web Dynpro component WDR_CHIP_PAGE. They include NetWeaver CHIPs of different types. CHIPs of the type launchpad link list serve to call up applications or reports. For more information, see the documentation for Web Dynpro ABAP Page Builder under Creating Mashups with the Page Builder.

Activities Changes can be made to the work centers with different ranges of coverage: Users in an enterprise can adapt the work centers to their own needs by moving, deleting, or adding CHIPs using the Personalization function. This creates a user-specific copy of the work center. If changes to a work center are delivered and these are to be made visible, the users must reset their personalized copies to the default using the appropriate pushbutton. Depending on the type of CHIP, users can also make settings via the menu of the CHIP. Administrators can adapt the work centers for the whole client (using Customizing) or for the whole system (using Configuration). For more information, see Web Dynpro Configuration. You can also make settings for CHIPs of the type launchpad link list centrally in Customizing for QIM (see Launchpads in QIM).

1.9.2.1 Launchpads in QIM Various CHIPs of the type launchpad link list are integrated in the work centers. Via these launchpads, the users have access to different applications that are relevant for QIM, for example, in the System Administration Work Center.

Features For general information about the functional scope of launchpad link lists, see the documentation for Web Dynpro ABAP Page Builder under Launchpad Link List.

Activities You can specify centrally which applications are to be made available to the users for selection. You do this in Customizing for QIM under Up Launchpads . In the documentation for this Customizing activity, you also find information about how to embed additional launchpads.

Environment

Set

More Information Launchpads

1.9.3 Adaptation of the Web Applications in QIM

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 52 of 106

The applications in QIM with which you can process issues or activities are based on various floorplans of the Floorplan Manager for Web Dynpro ABAP (FPM). Depending on the floorplan, various adaptations are possible.

Features Personalization and Customizing In all applications, end users can use personalization and administrators can use customizing to make changes at field level. For example, you can hide individual fields or default values.

Note You can also store a default value for the source system of reference objects in the user master record under the user parameter /IAM/DEF_SRC_SYSTEM. In customizing, other adaptations are possible, for example, the addition of decorative UI elements. For more information, see the documentation for Web Dynpro ABAP under Personalization and Customizing.

Configuration More extensive adaptations are possible by configuration in the Flexible User Interface Designer (FLUID) of the Floorplan Manager: The application for the guided creation of an issue is based on the Floorplan for Guided Activity (GAF) in FPM. Here, for example, you can hide individual steps or change the sequence of the steps. The applications for advanced creation and quick creation of an issue, and for displaying or changing an issue or activity are based on the Floorplan for the Overview Page (OVP). Here, for example, you can hide individual assignment blocks, change the sequence of the blocks, or display them in stacked form (also possible in personalization). You can add help texts for Web Dynpro applications to all applications. Using context-based adaptations (CBAs) in the Floorplan Manager, you can create different configurations, for example, for different partner roles in QIM.

Note If you want to include additional fields for new quantity codes, timepoint codes, or text types on the interface, you must integrate the new codes or text types in the respective feeder parameters for the FPM configuration. To improve the performance of the Web application, note that you should not add any unnecessary codes or text types to the feeder parameters. For more information about the procedure, for example, see Web Dynpro Configuration.

Field Control You can control attributes for individual fields (for example, required entry field, display) in Customizing without having to directly change the interface. For more information, see Adaptation Using Field Control.

More Information As well as the general Web Dynpro functions, you have the option of adapting QIM-specific terminology by making settings for terminology redefinition in Customizing for QIM. In addition to these adaptations to the user interface, you can also extend the functionality of the QIM applications by defining a user status.

1.9.3.1 Context-Based Adaptation of QIM Web Applications You can adapt the applications for displaying, processing, and advanced creation of issues and activities based on context, that is, dependent on specific parameters (adaptation dimensions) such as the partner role or the issue type.

Example You can provide a restricted user interface to a user that has the partner role Interested Party . You can find general information about context-based adaptations in the SAP NetWeaver documentation about Floorplan Manager under Context-Based Adaptations (CBAs).

Features Content-based adaptations are possible in the UIBB component configurations for the following application configurations: QIM_OVP_ISSUE: Overview page (OVP) for issues QIM_OVP_8DISS: Overview page for 8D problem analyses QIM_OVP_ACTIVITY: Overview page (OVP) for activities The possible adaptation dimensions are stored in different adaptation schemas. The delivered adaptation schemas each include different adaptation dimensions. The adaptation schema QIM_ADAPT is relevant for the overview page for issues and 8D problem analyses. Some of the included dimensions can be used for the UIBBs for processing the issue or problem analysis itself and some for the UIBBs for processing the corresponding activities. The following table shows in

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 53 of 106

detail which dimension of the adaptation schema QIM_ADAPT is relevant for what: Dimension

Description

Use

UIBB Level

Comment

ISSUE_TYPE

Issue type

Issue data/activity data

All (QIM_OVP_ISSUE_CC and

Can also be set as an application parameter in the PFCG role.

QIM_OVP_8DISS_CC and lowerlevel UIBBs) ISSUE_HIER

Hierarchy type

Issue data/activity data

All (QIM_OVP_ISSUE_CC and QIM_OVP_8DISS_CC and lower-

Is not filled by the application, so can only be set as an application

level UIBBs)

parameter in the PFCG role. To use it, you must first specify parameter values yourself. Is not currently used in QIM.

DEP_OBJ_TY

Object type

-

-

ACT_W_TMPL

With template?

Activity details (all tabs, for example, Overview, Reference Objects, Business Partners, Attachments)

UIBBs for activity data, for example, all UIBBs for tabs within QIM_OVP_ISSUE_ACTIVITY_TA B, QIM_OVPH_ISSUE_ACTIVITY_T AB, or QIM_OVP_8DISS_{D50,D60,D7 0}_ACTIVITY_TAB)

ACT_CAT

Activity category

Activity details (all tabs, for

UIBBs for activity data, for

example, Overview, Reference Objects, Business Partners, Attachments)

example, all UIBBs for tabs within QIM_OVP_ISSUE_ACTIVITY_TA B, QIM_OVPH_ISSUE_ACTIVITY_T AB, or QIM_OVP_8DISS_{D50,D60,D7 0}_ACTIVITY_TAB)

ISS_APPR

Approval required

Issue data/activity data

All (QIM_OVP_ISSUE_CC and QIM_OVP_8DISS_CC and lowerlevel UIBBs)

USER_ROLE

Partner role code

Issue data/activity data

All (QIM_OVP_ISSUE_CC and QIM_OVP_8DISS_CC and lower-

Can also be set as an application parameter in the PFCG role.

level UIBBs) ISS_CAT

Issue category

Issue data/activity data

All (QIM_OVP_ISSUE_CC and QIM_OVP_8DISS_CC and lower-

Can also be set as an application parameter in the PFCG role.

level UIBBs) DSIGN_CD

Issue with digital signature

Issue data/activity data

All (QIM_OVP_ISSUE_CC and QIM_OVP_8DISS_CC and lowerlevel UIBBs)

ACT_DS_CD

Activity with digital signature

Activity details (all tabs, for example, Overview, Reference Objects, Business Partners, Attachments)

UIBBs for activity data, for example, all UIBBs for tabs within QIM_OVP_ISSUE_ACTIVITY_TA B, QIM_OVPH_ISSUE_ACTIVITY_T AB, or QIM_OVP_8DISS_{D50,D60,D7 0}_ACTIVITY_TAB)

ISS_STATUS

Issue status

Issue data/activity data

All (QIM_OVP_ISSUE_CC and QIM_OVP_8DISS_CC and lowerlevel UIBBs)

The adaptation schema QIM_AADAPT is relevant for the overview page for activities. Some of the included dimensions relate to the activity in the header, some to the subactivities. The following table shows in detail which dimension of the adaptation schema QIM_AADAPT is relevant for what: Dimension

Description

Use

UIBB Level

Comment

ACT_TYPE

Activity type

ACT_W_TMPL

With template?

UIBBs for activity data, for Can also be set as an application example, all UIBBs for tabs within parameter in the PFCG role. QIM_OVP_ACTIVITY_ACTIVITY

ACT_CAT

Activity category

Details of subactivities (all tabs, for example, Overview, Reference Objects, Business Partners, Attachments)

ACT_FOA

Follow-up action?

USER_ROLE

Partner role code

ACTHD_TYPE

Activity type header

ACTHDWTMPL

Template? header

ACTHD_CAT

Activity category header

ACTHD_FOA

Follow-up action? header

AHD_PROC

Activity processor header

_TAB and QIM_OVPH_ACTIVITY_ACTIVIT Y_TAB

Activity data (including header data All (QIM_OVP_ACTIVITY_CC and Can also be set as an application in overview and partner, date, parameter in the PFCG role. lower-level UIBBs) reference objects, attachments for activity)

Note

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 54 of 106

Make sure that you only use the respective matching dimensions in the different UIBBs. Also note that the adaptation dimensions expand themselves exponentially. Therefore if you set a parameter for each of several dimensions, you must also define a component configuration for adaptation for each possible combination.

Activities To display or create an adaptation, proceed as follows: 1. Open the ABAP Workbench (transaction SE80). 2. In the package QAM_UI, open the Web Dynpro application configuration QIM_OVP_ACTIVITY or QIM_OVP_ISSUE or QIM_OVP_8DISS. 3. Choose Display Configuration . 4. Open the component configuration QIM_OVP_ACTIVITY_CC or QIM_OVP_ISSUE_CC or QIM_OVP_8DISS_CC. 5. Open the component configuration for the UIBB whose adaptations you want to display. 6. To display the possible adaptation dimensions and the existing adaptations, choose the pushbutton with the quick info Adaptations & Comparisons . The dimensions are displayed in the table in the upper screen area. 7. If you select an existing adaptation, the adapted component configuration is displayed in the lower screen area. 8. To create a new adaptation, select the base configuration or an existing adaptation and choose Add .

Example Context-based adaptations are delivered for various simplifications of the user interface. Some examples are described below. Activity Processing For users with the partner role Activity Processor (PROCSSR), the user interface was simplified to allow these users to focus on processing. This is achieved, for example, by hiding the activity hierarchy. This is done in an adaptation of the component configuration QIM_OVP_ACTIVITY_CC that forms the framework for the overview page.

Note In QIM, only an adaptation on the basis of the adaptation dimension Partner role is possible at this upper level. The reason for this is that, in addition to the adaptation, additional programming is necessary even at this level, which was only implemented for the partner role. You can use all other adaptation dimensions only for the adaptation of lower-level UIBBs. At lower level, for example, on the detailed screen of the activity to be processed (in the UIBB QIM_OVP_ACTIVITY_OVERVIEW_FORM), technical information such as the code group and code are invisible for the activity processor. There are other adaptations in the UIBB QIM_OVP_ACTIVITY_OVERVIEW_FORM, for example, for the adaptation dimension Template? header . Only for activities with a template are the fields with detailed information about the template visible on the user interface. Issue Processing On the detailed screen for the issue being processed (in the UIBB QIM_OVP_ISSUE_OVERVIEW_FORM), the respective field with the approval status is only displayed for issues for which an approval is required. Similarly, for issues for which a digital signature is required, the status of the digital signature is only visible for these issues.

1.9.3.2 Adaptation Using Field Control You can adapt the attributes for individual fields and thus display them as required entry fields or in display mode. You can either specify the field attributes statically or determine them dynamically depending on certain conditions. A condition could be, for example, that another field has a specific value.

Integration Field control is available for the applications for processing issues and activities. As field control directly affects the BOPF node, no influence on the interface is necessary using context-based adaptations (CBAs) of the Web Dynpro applications.

Features In field control, there is a distinction between modifiable and influencing fields. The modifiable fields are visible on the user interface and can be influenced by field control. Control is exercised by the influencing fields, which do not necessarily have to be visible on the user interface. For each modifiable field, you can specify which influencing fields have control. If you have defined your own fields in the customer namespace, you can also include these as modifiable or influencing fields in field control.

Activities For information about how you set up field control, see Customizing for QIM under

Environment

Define Field Control

.

1.9.4 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

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 55 of 106

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.

Features Messages You can copy the messages for the QIM applications and QIM Customizing used in the standard system and adapt them to your terminology. The following QIM message classes are relevant for this: /IAM/OBJECT: Messages that are relevant when creating issues and activities /IAM/CONFIG: Messages that are relevant within QIM Customizing To do this, create your own message class and save this in QIM Customizing for terminology redefinition. In your message class, you must only enter the new text under the respective number.

Redefinition Object Types You can change texts for many DDIC data types (structures or data elements). To do this, in Customizing for terminology redefinition select the corresponding object type using the input help, for example, object type ITY for the issue type. You can use the input help to find out which data type corresponds to the object type. Copy the data type in the transaction SE11 and make your changes. Then enter the copy with your changes in Customizing.

Interface Texts You can replace texts on the interface that are technically stored in the online text repository (OTR) with an OTR alias in the packages /IAM/UI or QAM_UI (or subpackages) with your own OTR texts. You recognize OTR texts in a Web Dynpro configuration by their prefix $OTR:. Create a new OTR alias and save the assignment to the alias that is to be replaced in Customizing for terminology redefinition. If the text is also used directly in a Web Dynpro configuration, you must replace the alias name there manually. Use the where-used list to display all the places where the OTR alias you want to replace is used.

Parameters You can store the redefinition that you have created in QIM Customizing in the following places: As the user parameter /IAM/REDEFINITION in the user master record in transaction SU01 (centrally) or SU3 (by the users themselves) As an application parameter in the menu for the role (transaction PFCG) in the details view of a Web Dynpro application

1.9.5 User Status You can add your own customer-specific user status to the applications for creating and processing issues and activities, which can be set in addition to the delivered system statuses. This means you can enhance the control of business processes by the system statuses by including a user status.

Example When processing an activity, you can add a selection list that is used to prompt for approval by the board.

Features You can implement a user status using the extensive options available in Web Dynpro configuration and by changes in the Business Object Processing Framework (BOPF). This provides you with a flexible method for implementing a user status and running reports with it without modification, by displaying the user status in the worklist. You can have the user status set manually by the user or by a BOPF action. You can also use the user status to control a delivered system status if you define a validation action in BOPF for the standard action of the system status, which reads out the user status.

Activities To define a user status, proceed as follows: 1. Create a status variable in the Data Dictionary (DDIC, transaction SE11). 1. To do this, first create a domain in Character String (CHAR) format with a length of 2 characters. Under Value Range , store the values that the status can have. 2. Create a data element to which you assign this domain. 3. Create an append structure and add the data element you created to it: If the status variable is to apply to an issue, create the append structure for the BOPF enhancement structure /IAM/INCL_EEW_I_ROOT. If the status variable is to apply to an activity, create the append structure for the BOPF enhancement structure /IAM/INCL_EEW_ACT_ROOT. 2. Enhance the business object in the enhancement browser of the BOPF Enhancement Workbench (transaction /BOBF/CUST_UI). 1. Create an enhancement for the business object for which you want to define the status: /IAM/ISSUE: Quality issue /IAM/ACTIVITY: Quality activity The system generates the enhancement according to your entries in the wizard and creates a corresponding node beneath the business object. 2. Open the generated enhancement.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 56 of 106

3. Create actions for the status change by choosing Create Action in the context menu for the ROOT node.

Example For a board approval, you can create the following actions: Change from initial value to To Be Approved by Board Change from To Be Approved by Board to Approved by Board Change from To Be Approved by Board to Rejected by Board Here you can use the following delivered class and parameter structure. Check first in the class documentation whether the business logic suits your requirements: Class: /IAM/CL_SET_USER_STATUS Parameter structure: /IAM/S_SET_USER_STATUS 4. Optional (programming required): If you want to indicate visually whether a status change is possible on the user interface (for example, by graying out an option), create a determination for the ROOT node. Use the delivered determination SET_DYNAMIC_ROOT_PROPERTIES as a guide. For the determination pattern, choose the option Create Properties . 5. Optional (programming required): If you want to prevent the execution of a standard action using a user status, create an action validation for the standard action. Use the delivered action CHECK_ACTION_ATTACHMENT_AUTH for the business object /IAM/ISSUE as a guide. 3. To visualize the user status and execute actions, use Customizing to include it in the Web Dynpro application configuration or component configuration. 1. In the ABAP Workbench (transaction SE80), open the Web Dynpro application configuration and choose Web Dynpro Configuration Test Execute in Administration Mode . 2. Insert pushbuttons for the status change in Customizing mode, for example. For the FPM event ID, use the prefix I_ for issues and A_ for activities, followed by the action that you created in BOPF. If you use the delivered class /IAM/CL_SET_USER_STATUS in the action, fill the event parameters according to the parameter structure /IAM/S_SET_USER_STATUS. 3. If you want to include the user status as a selection list, the text is displayed immediately on the interface. 4. If the user status is only to be changed by actions, include the status field as read-only. 4. Include the user status in the worklist. 1. To do this, create an append structure for the corresponding delivered structure in the transaction SE11: QAMS_GQI_ATTRIBUTE for issues QAMS_GQA_ATTRIBUTE for activities Use the same component name as for the append structure for the BOPF structure (see step 1.3 above). 2. Enhance the structure mapping in the Service Mapping Tool, which you access in Customizing under Cross-Application Components Processes and Tools for Enterprise Applications Enterprise Services Enhance Enterprise Services Extend Mappings Extend Mappings : Mapping QAM_QI_QI for issues Mapping QAM_QA_QA for activities Enhance one of the following mapping steps in the field mapping to include a new field relationship: Issues: Mapping step ISSUE_TO_GQI, transformation 00001 Field relationship QAMS_QGI_ATTRIBUTE- to QAMIS_ISSUE_MAP- Activities: Mapping step ACTIVITY_2_GQA, transformation 00001 Field relationship QAMS_QGA_ATTRIBUTE- to QAMAS_ACTIVITY_MAP- 3. In the worklist, change the layout and display the field for the user status. 5. You can attach a digital signature to a user status.

Note For technical reasons, you can only use the digital signature for a BOPF action without a parameter structure. To activate the digital signature, store the BOPF action you created as a business transaction. You do this in the transaction SM30 via the following views: Quality issues: /IAM/V_I_ACT_DS Quality activities: /IAM/V_A_ACT_DS

1.9.6 Web Dynpro Personalization and Customizing In the Web Dynpro environment, it is possible using personalization and customizing to edit the interface directly when you call an application or a page. The basis for this is the Web Dynpro ABAP configuration framework.

Features 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. For more information, see: Adaptation of the QIM Work Centers Adaptation of the Web Applications in QIM For general information about the adaptation of Web Dynpro applications, see the documentation for Web Dynpro ABAP under Personalization and Customizing.

More Information The configuration framework also allows the configuration of Web Dynpro applications or pages for more extensive adaptations by an administrator or developer (see Web Dynpro Configuration).

1.9.7 Web Dynpro Configuration PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 57 of 106

1.9.7 Web Dynpro Configuration By configuration of Web Dynpro components, applications, and pages, major adaptations to the user interface in the development environment, the configurator, are possible. Adaptations made by configuration are visible throughout the system.

Features Which functions exactly are available depends on whether you want to adapt a page (for example, a work center) or an application. If you want to configure pages, use the Web Dynpro ABAP Page Builder. For more information about the Page Builder, see the documentation under Creating Mashups with the Page Builder. If you want to adapt an application, you can use the functions of the Floorplan Manager for Web Dynpro ABAP. For general information about the configuration of Web Dynpro components and applications, see the documentation for Web Dynpro ABAP under Configuration.

1.10 Roles in SAP Quality Issue Management To allow task-specific access to the applications in SAP Quality Issue Management, you can assign different roles to the employees in your enterprise. In a role, the navigation structure, that is the arrangement of the work centers, and authorizations for access are specified. The following roles are delivered in the standard system with SAP QIM: Role

Use

Coordinator SAP_QIM_COORDINATOR

Employees who are assigned this role have comprehensive authorizations in SAP Quality Issue Management. The role includes all available authorization profiles for executing Web Dynpro ABAP-based applications and the work center for system administration.

Issue Driver SAP_QIM_ISSUE_DRIVER

Employees who are assigned this role have all necessary authorizations for executing Web Dynpro ABAP-based applications in SAP Quality Issue Management. The exception to this is the work center for system administration.

QIM Support – display authorizations only SAP_QIM_SUPPORT

The QIM Support role is not intended as an operational role for SAP QIM users, but is only for the display of information within the scope of support.

Note that you may require other authorizations stored in roles for those components that are reused in SAP QIM, for example, Business Context Viewer, Enterprise Search, BRFplus, Master Data Governance. For more information, see the documentation for the respective component.

Implementation Considerations You make the settings for the roles in the transaction PFCG. You can use the roles in SAP NetWeaver Business Client (NWBC) and SAP NetWeaver Portal. The definition of the delivered PFCG roles is, however, for use in NWBC. To be able to use the roles in the portal as well, you must upload them to the portal (see Generation of Portal Roles).

General Settings Configure the following RFC connections in the transaction SM59: Under ABAP Connections , create an RFC destination for the local QIM system with the connection type 3. For all source systems that you want to connect to the QIM system, also create RFC destinations with connection type 3. Also, under HTTP Connections to ABAP System (connection type H), create an RFC connection with the same name plus the suffix _HTTP for all source systems. This is required to call applications via object-based navigation. To call reports in the Reports work center, create RFC destinations for the systems in which the reports are located. For more information, see Reports.

Notes on Object-Based Navigation When you make new entries for object-based navigation (OBN), note that the entries in the transaction PFCG must match the OBN parameters under Other Node Details and the following entries in Customizing for QIM for jumps: Basic Settings Generic Settings for Reference Objects Define Details for Jump to Linked Applications Worklists for Quality Issues and Activities Define Details for Jump to Linked Applications The system alias that is stored in the Customizing activities for a jump must also be assigned to the parameter portal_bo_alias in the corresponding OBN entry in the transaction PFCG. This assignment guarantees the call of the actual system. You can assign the following system aliases in these places: SAP_QIM for the system in which SAP QIM itself is installed SAP_IAM for the systems that are used from SAP QIM

More Information For more information, see the documentation for NWBC under: 5.11 Remote Systems 5.12 Object-Based Navigation (OBN).

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 58 of 106

Note The documentation for NWBC exists in English only.

1.10.1 Coordinator Role: SAP_QIM_COORDINATOR

The main task of the coordinator in SAP Quality Issue Management (SAP QIM) is to track and coordinate the processing of quality issues and the related quality activities. The coordinator analyzes existing content, adds additional information, derives follow-up actions, and triggers workflow processes for distinct steps by, for example, assigning additional or different partners. The coordinator also checks the overall progress of the resolution of an issue. Reports and queries are available to support the coordinator in fulfilling his or her tasks. Coordinators also act as power users by managing settings in productive systems, such as adding codes, setting up business rules for the automatic determination of partners, codes, or activities, or configuring access to other systems. Within the scope of compliance coordination, the coordinator can access audit trail transactions to be able to track all changes in the SAP QIM system.

Activities In detail, the coordinator is responsible for the following tasks: Analyzing and tracking the worklists for quality issues and quality activities across all systems Coordinating the quality activities Assigning partners or processors to a quality issue Providing additional information about individual quality issues Creating new quality issues Completing and validating a quality issue Managing and changing system settings (without transport) Managing and editing decision tables for the rule-based determination of codes, partners, and activities

Integration In addition to this role, the role of Issue Driver is also relevant for SAP Quality Issue Management. Both roles can be used in SAP NetWeaver Business Client and in SAP NetWeaver Enterprise Portal. For more information, see Generation of Portal Roles.

1.10.2 Issue Driver Role: SAP_QIM_ISSUE_DRIVER

The task of the issue driver in SAP Quality Issue Management is to process a quality issue and initiate appropriate quality activities. To do this, the issue driver checks the content of an incoming issue and adds more information to it, if possible, so that all data required for its subsequent resolution process is available and all partners are clearly defined. Then the issue driver sets the issue in process and thus triggers the resolution process and the workflows connected with it. The issue driver typically reviews the status of the issue when the activities related to it are set in process or completed. The issue driver documents the overall resolution and completes the process.

Activities In detail, the issue driver is responsible for the following tasks: Analyzing and tracking his or her own quality issues with the aid of the worklists for quality issues and quality activities across all systems Coordinating the quality activities for a quality issue Assigning partners to a quality issue Providing additional information about a quality issue Creating new quality issues Completing and validating a quality issue

Integration In addition to this role, the role of Coordinator is also relevant for SAP Quality Issue Management. Both roles can be used in SAP NetWeaver Business Client and in SAP NetWeaver Enterprise Portal. For more information, see Generation of Portal Roles.

1.10.3 Authorizations 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.

Integration The authorization objects are located in the IAM layer and are also used for objects that do not belong to SAP QIM, for example, for change requests and activities in the SAP Management of Change application.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 59 of 106

Features The following authorization objects are delivered with SAP QIM (object class IAM): Authorization Object

Name

IAM_CAT_AC

Authorization object to restrict access to QIM worklist object

/IAM/IAUTH

Authorization object for issue/change request

/IAM/AAUTH

Authorization object for activity

/IAM/ATTMT

Authorization object for attachments for issue/change request/activity

IAM/I_RLCD

Authorization object for role codes for issue/change request

IAM/A_RLCD

Authorization object for role codes for activity

IAM/A_ATTR

Authorization object for attribute maintenance for activity

/IAM/TXTTY

Authorization object for descriptions

IAM_CODEGR

Authorization object for code groups

IAM/I_STAT

Authorization object for lifecycle status for issue/change request

IAM/A_STAT

Authorization object for lifecycle status for activity

/IAM/OREF

Authorization object for reference objects for issue/change request/activity

/IAM/CODGR

Authorization object for selection of code groups/codes

IAM/CHGLOG

Authorization object for change log in IAM

Note Note that the authorization object /IAM/IAUTH includes the Reported By field. Within your organization, make sure that only data is stored in this field that is not subject to additional confidentiality. In many authorization objects, you can set the authorization dependent on an authorization group. The authorization groups are used to map organizational units in your enterprise. You set up authorization groups in Customizing for QIM under Environment Define Authorization Groups for Issues/Activities . You can use the Business Add-In (BAdI) /IAM/BADI_ISSUE_AUTHORITY to extend the authorizations of individual users. For more information, see the documentation for the BAdI in Customizing for QIM under Environment BAdI: Enhanced Authorization Check for Issues/Activities .

1.10.4 Generation of Portal Roles If you want to use the PFCG roles in SAP NetWeaver Portal, you must upload the roles to the portal. By doing this, the corresponding portal roles are generated automatically.

Prerequisites Make sure that the placeholder SAP_ECC_IAM is stored in the transaction PFCG in the role menu under Other Node Details in the Target System field for the entries that refer to other SAP ERP systems. During generation of the roles, checks are made for which these placeholder entries are necessary. In the portal, the following systems must be available with their respective assigned system aliases: The QIM system must be available and have the system alias SAP_QIM assigned. One of the SAP ERP systems that is connected to the QIM system must have the system alias SAP_ECC_IAM assigned. Technical checks are made using this system when the roles are generated. Each system that you connected to the QIM system via system integration must be available in the portal and have a system alias assigned that corresponds to the name of the assigned logical system. You can find the names of the logical systems in QIM Customizing for access to the respective object under the System-Dependent Settings node. To call the delivered reports (see Reports), the corresponding systems must be available and the system aliases SAP_BW or SAP_QualityManagement must be assigned. The portal component BP ERP05 COMMON PARTS 1.61 SP03 (Business Package for Common Parts) must be installed. This Business Package includes the business objects necessary for navigation.

Activities Upload the PFCG roles to the portal with the role upload tool. For information about the upload tool, see SAP Note 1685257 and the documentation for the portal under Upload of Roles from ABAP-Based Systems.

1.11 System Architecture SAP QIM uses various different generic tools that are part of different software components. The business content lies in the software components IAM and QAM.

Structure PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 60 of 106

Below is a list of the software components required for SAP QIM with their most important tools or content objects: SAP NetWeaver Application Server ABAP (software components SAP_BASIS and PI_BASIS) Web Dynpro ABAP Framework Floorplan Manager (FPM) for the user interface of Web Dynpro applications Page Builder and Launchpad for navigation pages Personal Object Worklist (POWL) for worklists Operational Search and Analytics for Enterprise Search and reports Status and Action Management (S&AM) Archive Development Kit (ADK) for data archiving Adobe Document Services (ADS) for printing PDF-based forms TREX as search engine Knowledge Provider (KPro) to connect a content management system for attachments (documents and links) General services (software component SAP_ABA) SAP business partner SAP Web UI Framework (software component WEBCUIF) Business object layer (BOL) and generic interaction layer (genIL) as the link between business object logic and remote APIs to external data SAP Business Suite Foundation (software component SAP_BS_FND) Business Object Processing Framework (BOPF) for object modeling Business Context Viewer (BCV) for reports Business Rule Framework plus (BRFplus) for rule-based determinations Master Data Governance (MDG) for ID mapping Issue and Activity Management (software component IAM) Business objects /IAM/ISSUE and /IAM/ACTIVITY in BOPF FPM feeder classes Object types and object type configurations for reference objects Quality Issue Management (software component QAM) Web Dynpro applications and application configurations POWL queries BCV queries Search models Object types and object type configurations for worklists SAP NetWeaver Business Client (NWBC) as UI client The following diagram shows a graphical representation of this system architecture:

System Architecture of SAP QIM

Other Optional Components Portal as alternative UI client SAP Information Lifecycle Management (ILM) to define rules for data archiving and data destruction

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 61 of 106

1.12 Sequence of Configuration Steps in SAP QIM You perform most of the configuration steps in the SAP Customizing Implementation Guide under Cross-Application Components Management . In the documentation for the individual Customizing activities, you will find information about the exact procedures.

Quality Issue

Process To configure SAP QIM, work through the process as detailed below. Optional steps are indicated accordingly. 1. Optional: Copy over the delivered Customizing settings for SAP QIM by activating the corresponding BC Sets. You do this in Customizing for QIM under Activate BC Sets for QIM . You have then made all the necessary settings in the system for the predefined standard processes, with the exception of the access to remote systems. In the next stages of the configuration process, you can adapt the delivered settings to suit your requirements. 2. Make the settings for number range intervals, quantity codes, and timepoints in Customizing for QIM under Basic Settings . 3. Configure the system connections to the remote systems that you want to connect to SAP QIM. For more information, see Setting Up System Connections. 4. Make the settings for access to the reference objects for an issue or activity. You do this in Customizing for QIM under Basic Settings Generic Settings for Reference Objects Define Object Access . Alternatively, you can make the settings using the respective QIM Customizing wizard. You access the wizard in Customizing for QIM under Start QIM Customizing Wizards . 5. Make the settings for document management in Customizing for QIM under Basic Settings Attachments Define Document Types and Document Schemas . 6. Optional: Make the settings for text types in Customizing for QIM under Basic Settings Text Types . For more information, see Settings Dependent on the Text Type. 7. Assign the document schema to the issue and activity categories in Customizing for QIM under Issue Processing . 8. Make the settings for printing and e-mailing issues and activities in Customizing for QIM under Issue Processing . For more information, see Printing of Issues or Activities. 9. Optional: Make the settings for priorities and criticalities in Customizing for QIM under Issue Processing Urgency . 10. Create partner roles in Customizing for QIM under Issue Processing Partners . 11. Make the settings for codes and code groups in Customizing for QIM under Issue Processing Codes . 12. Optional: For the rule-based determination of partners, codes, and code groups, you can use Business Rule Framework plus (BRFplus). For more information, see Configure Rules. 13. Make the settings for activity types in Customizing for QIM under Issue Processing Define Activity Types . 14. Optional: Make the settings for follow-up actions in Customizing for QIM under Issue Processing Define Follow-Up Actions . In particular, set up the target systems here. 15. Make the settings for activity templates in Customizing for QIM under Issue Processing Define Activity Templates . 16. Optional: Set up the rules for activity determination with BRFplus. For more information, see Determination of Activities Using BRFplus. 17. Make the settings for issue types in Customizing for QIM under Issue Processing Define Issue Types . 18. Make the settings for the worklist, particularly for access to issues, activities, and issue types in Customizing for QIM under Worklists for Quality Issues and Activities . In this Customizing section, you also define the authorizations for access under Make Settings in POWL Cockpit . 19. Optional: If you want to use Enterprise Search to search for issues, you must create and index connectors for the search and analytics models supplied. For more information, see Customizing for QIM under Search and Analytics Configure Search and Search and Operational Analytics: Content for SAP QIM.

More Information In addition to this basic configuration, you can also make more major adaptations and, for example, adapt the user interface (see User Interface Adaptation) or define other reference objects.

1.13 Search and Operational Analytics: Content for SAP QIM With Search and Operational Analytics, SAP NetWeaver provides a technical infrastructure that supports and harmonizes data provisioning for analytics and also for searching data. Search and Operational Analytics therefore provides the prerequisites for mapping search and analysis scenarios for QIM data. In a commonly used modeling environment, search and analytics models are made available for this.

Prerequisites For information about the necessary Customizing settings, see Customizing for QIM under

Search and Analytics

.

Integration The content objects delivered for SAP QIM are in the software components IAM and QAM.

Features In this documentation structure, you will find detailed technical information about the content objects delivered.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 62 of 106

More Information Enterprise Search in SAP QIM Reports in SAP QIM

1.13.1 Search and Analytics Models You can display the search and analytics models supplied in the transaction ESH_MODELER and extend them if required.

Prerequisites To display the models, you require the authorizations in the role SAP_ESH_LOCAL_ADMIN. To change the models, you require the authorizations in the role SAP_ESH_TRANSPORT.

1.13.1.1 Issue : 0QAM_I_QIM_T01

This search and analytics model is used to search for QIM quality issues. Technical Data Model Use

Application model

Software Component for Search and Analytics

QAM

Prerequisites To use the search and analytics model for Embedded Search, you must have made your settings in Customizing for QIM under Configure Search .

Search and Analytics

Integration The data is read from the DDIC by the BAdI implementation QAM_I_QIM_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA. To search for subissues or attachments to an issue or subissue, use the following models: Defect Cause Effect Issue Attachment

Default Request (All Response Attributes) Technical Name

DEFAULT

Use

Attribute search

Overview of the Nodes in the Model In the following sections, you will find information about the nodes of the search and analytics model. For more technical information about the nodes, see the steps Model Nodes , Node Response , and, if required, Operational Data Provider in the system in the transaction ESH_MODELER.

Root Node: Issue Header Extraction Technical Name for Root Node

QAM_I_ROOT

DDIC Structure

/IAM/S_ESO_I_ROOT

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Root node ROOT of business object /IAM/ISSUE.

Operational Data Provider: Issue Header Extraction Technical Name

0QAM_I_QIM

ODP Semantics

Master data attributes

Direct Access Activated

No

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 63 of 106

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_I_QIM_IAUTH_T01

/IAM/IAUTH

Authorization object for issue/change request

Logical Conjunction Authorization Type

Logical Conjunction

Search

0QAM_I_QIM_IAUTH_T01

Analytics

0QAM_I_QIM_IAUTH_T01

Analytics result filter

0QAM_I_QIM_IAUTH_T01

Navigation Target Navigation Target

Description

Details

UI Technology

0QAM_I_QIM_OVP_ISSUE_T01

Display issue

Displays the issue in the QIM Web Dynpro Web Dynpro (Application Server) application

Node: Issue Descriptions Extraction Technical Name for Node

QAM_I_DESC

DDIC Structure

/IAM/S_ESO_I_DESC

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node DESCRIPTION of business object /IAM/ISSUE.

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_I_QIM_TXTTY_T01

/IAM/TXTTY

Authorization object for descriptions

Logical Conjunction Authorization Type

Logical Conjunction

Search

0QAM_I_QIM_TXTTY_T01

Analytics

0QAM_I_QIM_TXTTY_T01

Analytics result filter

0QAM_I_QIM_TXTTY_T01

Node: Issue Object Reference with Description Technical Name for Node

QAM_I_OREF

DDIC Structure

/IAM/S_ESO_I_OREF

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node OBJECT_REFERENCE of business object /IAM/ISSUE.

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_I_QIM_OREF_T01

/IAM/OREF

Authorization object for reference objects for issue/change request/activity

Logical Conjunction Authorization Type

Logical Conjunction

Search

0QAM_I_QIM_OREF_T01

Analytics

0QAM_I_QIM_OREF_T01

Analytics result filter

0QAM_I_QIM_OREF_T01

Node: Issue Partner Extraction Technical Name for Node

QAM_I_PARTY

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 64 of 106

DDIC Structure

/IAM/S_ESO_I_PARTY

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node PARTY of business object /IAM/ISSUE.

Node: Issue Quantity Extraction Technical Name for Node

QAM_I_QUANTITY

DDIC Structure

/IAM/S_ESO_I_QUANTITY

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node QUANTITY of business object /IAM/ISSUE.

Overview of the Node Relationships in the Model In the following sections, you will find information about the node relationships of the search and analytics model. For more technical information about the nodes, see the step Node Relations in the system in the transaction ESH_MODELER.

Node Relationship: Issue Descriptions Extraction Node

QAM_I_DESC

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Node Relationship: Code Node

0CODE./IAM/CODE

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_DESC. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

CODE

Value

Join Operator Equal

CODE

Node Relationship: Code Group Node

0CODE_GROUP./IAM/CODE_GROUP

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_DESC. Foreign Keys Attributes of Parent Node CODE_GRP

Value

Attributes of Child Node CODEGROUP

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Value

Join Operator Equal

Page 65 of 106

Node Relationship: Issue Object Reference with Description Node

QAM_I_OREF

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

Yes

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Node Relationship: Object Type Code Node

0OBJ_TYPE_CODE./IAM/OBJ_TYPE_CODE

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_OREF. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

TYPE_CD

Value

Join Operator Equal

TYPE

Node Relationship: Object Subtype Code Node

0OBJ_SUBTYPE_CODE./IAM/OBJ_SUBTYPE_COD

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_OREF. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

TYPE_CD

TYPE

Equal

SUBTYPE_CD

SUBTYPE

Equal

Node Relationship: Issue Partner Extraction Node

QAM_I_PARTY

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

DB_KEY

Attributes of Child Node PARENT_KEY

Value

Join Operator Equal

Node Relationship: Partner Role Code PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 66 of 106

Node

0PARTY_ROLE_CODE./IAM/PARTY_ROLE_CODE

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_PARTY. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

PARTY_ROLE_CODE

Value

APPLICATION

Join Operator Equal

PARTY_ROLE_CODE QIM

Node Relationship: Issue Quantity Extraction Node

QAM_I_QUANTITY

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Node Relationship: Unit of Measure Node

0UNIT_OF_MEASURE./IAM/UNIT_OF_MEASURE

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QUANTITY. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

UNITCODE

Value

Join Operator Equal

MSEHI

Node Relationship: Issue Descriptions Extraction – Text Type Issue Description (IDESC) Node

0QAM_I_QIM_T01.QAM_I_DESC

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node DB_KEY

Value

Attributes of Child Node

Value

Equal

PARENT_KEY DESC_TYPE

Join Operator

IDESC

Node Relationship: Issue Descriptions Extraction – Text Type Issue Resolution (ISOLU) Node

0QAM_I_QIM_T01.QAM_I_DESC

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 67 of 106

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

DESC_TYPE

Join Operator Equal

PARENT_KEY ISOLU

Node Relationships: Issue Object Reference with Description For the node 0QAM_I_QIM_T01.QAM_I_OREF there are multiple associations: one for each QIM object type. This section describes all these associations collectively. Node

0QAM_I_QIM_T01.QAM_I_OREF

Relationship Type

Association

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys, Same for All Associations Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Other Foreign Keys by Association Association

Attributes of Child Node

Value

QAM_I_ROOT2QAM_I_OREF_CUS Reference object customer

TYPE_CD

CUS

QAM_I_ROOT2QAM_I_OREF_PLA Reference object plant

TYPE_CD

PLA

QAM_I_ROOT2QAM_I_OREF_MAT Reference object material

TYPE_CD

MAT

QAM_I_ROOT2QAM_I_OREF_BAT Reference object batch

TYPE_CD

BAT

QAM_I_ROOT2QAM_I_OREF_DLV Reference object outbound delivery

TYPE_CD

DLV

Reference object functional location

TYPE_CD

FL

QAM_I_ROOT2QAM_I_OREF_VEN Reference object vendor

TYPE_CD

VEN

QAM_I_ROOT2QAM_I_OREF_MAI Indicator main reference object

MAIN_REF_IND

X

QAM_I_ROOT2QAM_I_OREF_FL

Description

Note

Cardinality: Up to one

N_IND

Node Relationship: Issue Partner Extraction – Responsible Node

0QAM_I_QIM_T01.QAM_I_PARTY

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node DB_KEY

Value

Attributes of Child Node

Value

RESPONSIBLE_IND

Join Operator Equal

PARENT_KEY X

Node Relationship: Issue Quantity Extraction – Complaint Quantity

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 68 of 106

Node

0QAM_I_QIM_T01.QAM_I_QUANTITY

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Equal

PARENT_KEY ROLE_CD

Join Operator

COM

Node Relationship: Authorization Group Node

0AUTH_GROUP./IAM/AUTHORIZATION_G

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

APPLICATION

APPLICATION

Equal

AUTH_GROUP

AUTH_GROUP

Equal

Node Relationship: Lifecycle Status (Issue Status) Node

0ISS_LCYC_STAT./IAM/ISSUE_LCYCLE_ST

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

LCYCLE_CD

Value

Join Operator Equal

KEY1

Node Relationship: Issue Type and Text Node

0ISSUE_TYPE./IAM/ISSUE_TYPE

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

APPLICATION

APPLICATION

Equal

ISSUE_TYPE

ISSUE_TYPE

Equal

Node Relationship: Priority

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 69 of 106

Node

0PRIORITY./IAM/PRIORITY

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

APPLICATION

APPLICATION

Equal

PRIORITY

PRIORITY

Equal

Node Relationship: Criticality Node

0CRITICALITY./IAM/CRITICALITY

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

APPLICATION

APPLICATION

Equal

CRITICALITY

CRITICALITY

Equal

Node Relationship: Validation Status of an Object Node

0VALIDATION_STAT./IAM/VALIDATION_CD

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

VALIDATION_CD

Value

Join Operator Equal

KEY1

Node Relationship: Effectiveness Check Status of an Object Node

0EFFECTIVENESS_STAT./IAM/EFFECTIVENESS_C

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node EFFECTIVENESS_CD

Value

Attributes of Child Node

Value

KEY1

Join Operator Equal

Node Relationship: Issue Header Extraction – Issue Category Effect Node

0QAM_I_QEF_T01.QAM_I_QEF_ROOT

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 70 of 106

Relationship Type

Association

Cardinality

Arbitrary

Reverse Cardinality

Up to one

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

ISSUE_ID

Value

Join Operator Equal

ROOT_ISSUE_ID

Node Relationship: Issue Header Extraction – Issue Category Cause Node

0QAM_I_QCA_T01.QAM_I_QCA_ROOT

Relationship Type

Association

Cardinality

Arbitrary

Reverse Cardinality

Up to one

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

ISSUE_ID

Value

Join Operator Equal

ROOT_ISSUE_ID

Node Relationship: Issue Header Extraction – Issue Category Defect Node

0QAM_I_QDF_T01.QAM_I_QDF_ROOT

Relationship Type

Association

Cardinality

Arbitrary

Reverse Cardinality

Up to one

Subquery

No

This node is a subnode of the root node QAM_I_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

ISSUE_ID

Value

ROOT_ISSUE_ID

Join Operator Equal

1.13.1.2 Defect : 0QAM_I_QDF_T01

This search and analytics model is used to search for QIM quality issues of the category Defect . Technical Data Model Use

Application model

Software Component for Search and Analytics

QAM

Prerequisites To use the search and analytics model for Embedded Search, you must have made your settings in Customizing for QIM under Configure Search .

Search and Analytics

Integration The data is read from the DDIC by the BAdI implementation QAM_I_QDF_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA. To search for other issue categories or attachments to an issue or subissue, use the following models: Issue Cause Effect

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 71 of 106

Issue Attachment

Default Request (All Response Attributes) Technical Name

DEFAULT

Use

Attribute search Input help

Overview of the Nodes in the Model In the following sections, you will find information about the nodes of the search and analytics model. For more technical information about the nodes, see the steps Model Nodes , Node Response , and, if required, Operational Data Provider in the system in the transaction ESH_MODELER.

Root Node: Issue Header Extraction Technical Name for Root Node

QAM_I_QDF_ROOT

DDIC Structure

/IAM/S_ESO_I_ROOT

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Root node ROOT of business object /IAM/ISSUE.

Operational Data Provider: Defect Header Extraction Technical Name

0QAM_I_QDF_T

ODP Semantics

Master data attributes

Direct Access Activated

No

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_I_QDF_IAUTH_T01

/IAM/IAUTH

Authorization object for issue/change request

Logical Conjunction Authorization Type

Logical Conjunction

Search

0QAM_I_QDF_IAUTH_T01

Analytics

0QAM_I_QDF_IAUTH_T01

Analytics result filter

0QAM_I_QDF_IAUTH_T01

Navigation Target Navigation Target

Description

Details

0QAM_I_QDF_OVP_SUBISSUE_T01

Display defect

Displays the defect in the QIM Web Dynpro Web Dynpro (Application Server) application

UI Technology

0QAM_I_QDF_OVP_ROOT_ISSUE_T01

Display root issue

Displays the parent issue in the QIM Web Dynpro application

Web Dynpro (Application Server)

Node: Defect Description: Code and Texts Technical Name for Node

QAM_I_QDF_DESC

DDIC Structure

/IAM/S_ESO_I_DESC

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node DESCRIPTION of business object /IAM/ISSUE.

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_I_QDF_TXTTY_T01

/IAM/TXTTY

Authorization object for descriptions

Logical Conjunction Authorization Type

Logical Conjunction

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 72 of 106

Search

0QAM_I_QDF_TXTTY_T01

Analytics

0QAM_I_QDF_TXTTY_T01

Analytics result filter

0QAM_I_QDF_TXTTY_T01

Node: Object References with Description Technical Name for Node

QAM_I_QDF_OREF

DDIC Structure

/IAM/S_ESO_I_OREF

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node OBJECT_REFERENCE of business object /IAM/ISSUE.

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_I_QDF_OREF_T01

/IAM/OREF

Authorization object for reference objects for issue/change request/activity

Logical Conjunction Authorization Type

Logical Conjunction

Search

0QAM_I_QDF_OREF_T01

Analytics

0QAM_I_QDF_OREF_T01

Analytics result filter

0QAM_I_QDF_OREF_T01

Node: Issue Partner Extraction Technical Name for Node

QAM_I_QDF_PARTY

DDIC Structure

/IAM/S_ESO_I_PARTY

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node PARTY of business object /IAM/ISSUE.

Overview of the Node Relationships in the Model In the following sections, you will find information about the node relationships of the search and analytics model. For more technical information about the nodes, see the step Node Relations in the system in the transaction ESH_MODELER.

Node Relationship: Defect Description: Code and Texts Node

QAM_I_QDF_DESC

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_QDF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

PARENT_KEY

Value

Join Operator Equal

Node Relationship: Code Node

0CODE./IAM/CODE

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 73 of 106

This node is a subnode of the node QAM_I_QDF_DESC. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

CODE

Value

Join Operator Equal

CODE

Node Relationship: Code Group Node

0CODE_GROUP./IAM/CODE_GROUP

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_QDF_DESC. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

CODE_GRP

Value

Join Operator Equal

CODEGROUP

Node Relationship: Object References with Description Node

QAM_I_QDF_OREF

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

Yes

This node is a subnode of the root node QAM_I_QDF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Node Relationship: Object Type Code Node

0OBJ_TYPE_CODE./IAM/OBJ_TYPE_CODE

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_QDF_OREF. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

TYPE_CD

Value

Join Operator Equal

TYPE

Node Relationship: Object Subtype Code Node

0OBJ_SUBTYPE_CODE./IAM/OBJ_SUBTYPE_COD

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_QDF_OREF. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Value

Join Operator

Page 74 of 106

TYPE_CD

TYPE

Equal

SUBTYPE_CD

SUBTYPE

Equal

Node Relationship: Issue Partner Extraction Node

QAM_I_QDF_PARTY

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_QDF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Node Relationship: Partner Role Code Node

0PARTY_ROLE_CODE./IAM/PARTY_ROLE_CODE

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_QDF_PARTY. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

PARTY_ROLE_CODE

Value

APPLICATION

Join Operator Equal

PARTY_ROLE_CODE QIM

Node Relationship: Defect Description: Code and Texts – Text Type Defect Description (DDESC) Node

0QAM_I_QDF_T01.QAM_I_QDF_DESC

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_QDF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Equal

PARENT_KEY DESC_TYPE

Join Operator

DDESC

Node Relationship: Defect Description: Code and Texts – Text Type Defect Location (DLCTN) Node

0QAM_I_QDF_T01.QAM_I_QDF_DESC

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_QDF_ROOT.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 75 of 106

Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Equal

PARENT_KEY DESC_TYPE

Join Operator

DLCTN

Node Relationships: Object References with Description For the node 0QAM_I_QDF_T01.QAM_I_QDF_OREF there are multiple associations: one for each QIM object type. This section describes all these associations collectively. Node

0QAM_I_QDF_T01.QAM_I_QDF_OREF

Relationship Type

Association

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_QDF_ROOT. Foreign Keys, Same for All Associations Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Other Foreign Keys by Association Association

Description

Attributes of Child Node

Value

TYPE_CD

MAT

TYPE_CD

CUS

TYPE_CD

VEN

QAM_I_QDF_ROOT2QAM_I_QDFO Reference object outbound delivery REF_DLV

TYPE_CD

DLV

QAM_I_QDF_ROOT2QAM_I_QDFO Reference object batch

TYPE_CD

BAT

TYPE_CD

PLA

QAM_I_QDF_ROOT2QAM_I_QDFO Reference object material

Note

REF_MAT QAM_I_QDF_ROOT2QAM_I_QDFO Reference object customer REF_CUS QAM_I_QDF_ROOT2QAM_I_QDFO Reference object vendor REF_VEN

REF_BAT QAM_I_QDF_ROOT2QAM_I_QDFO Reference object plant REF_PLA

Node Relationship: Issue Partner Extraction – Responsible Node

0QAM_I_QDF_T01.QAM_I_QDF_PARTY

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_QDF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

RESPONSIBLE_IND

Join Operator Equal

PARENT_KEY X

Node Relationship: Criticality Node

0CRITICALITY./IAM/CRITICALITY

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 76 of 106

This node is a subnode of the root node QAM_I_QDF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

APPLICATION

APPLICATION

Equal

CRITICALITY

CRITICALITY

Equal

Node Relationship: Application Node

0APPLICATION./IAM/APPLICATION

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QDF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

APPLICATION

Value

Join Operator Equal

APPLICATION

Node Relationship: Issue Category Node

0ISSUE_CATEGORY./IAM/ISSUE_CATEGORY

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QDF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

ISSUE_CATEGORY

Value

Join Operator Equal

ISS_CATEGORY

Node Relationship: Issue Type and Text Node

0ISSUE_TYPE./IAM/ISSUE_TYPE

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QDF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

APPLICATION

APPLICATION

Equal

ISSUE_TYPE

ISSUE_TYPE

Equal

Node Relationship: Issue Header Extraction Node

0QAM_I_QIM_T01.QAM_I_ROOT

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QDF_ROOT.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 77 of 106

Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

ROOT_ISSUE_ID

Value

Join Operator Equal

ISSUE_ID

1.13.1.3 Cause : 0QAM_I_QCA_T01

This search and analytics model is used to search for QIM quality issues of the category Cause . Technical Data Model Use

Application model

Software Component for Search and Analytics

QAM

Prerequisites To use the search and analytics model for Embedded Search, you must have made your settings in Customizing for QIM under Configure Search .

Search and Analytics

Integration The data is read from the DDIC by the BAdI implementation QAM_I_QCA_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA. To search for other issue categories or attachments to an issue or subissue, use the following models: Issue Defect Effect Issue Attachment

Default Request (All Response Attributes) Technical Name

DEFAULT

Use

Attribute search

Overview of the Nodes in the Model In the following sections, you will find information about the nodes of the search and analytics model. For more technical information about the nodes, see the steps Model Nodes , Node Response , and, if required, Operational Data Provider in the system in the transaction ESH_MODELER.

Root Node: Issue Header Extraction Technical Name for Root Node

QAM_I_QCA_ROOT

DDIC Structure

/IAM/S_ESO_I_ROOT

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Root node ROOT of business object /IAM/ISSUE.

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_I_QCA_IAUTH_T01

/IAM/IAUTH

Authorization object for issue/change request

Logical Conjunction Authorization Type

Logical Conjunction

Search

0QAM_I_QCA_IAUTH_T01

Analytics

0QAM_I_QCA_IAUTH_T01

Analytics result filter

0QAM_I_QCA_IAUTH_T01

Navigation Target Navigation Target

Description

Details

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

UI Technology

Page 78 of 106

0QAM_I_QCA_OVP_SUBISSUE_T01

Display cause

Displays the cause in the QIM Web Dynpro Web Dynpro (Application Server) application

0QAM_I_QCA_OVP_ROOT_ISSUE_T01

Display root issue

Displays the parent issue in the QIM Web Dynpro application

Web Dynpro (Application Server)

Node: Issue Descriptions Extraction Technical Name for Node

QAM_I_QCA_DESC

DDIC Structure

/IAM/S_ESO_I_DESC

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node DESCRIPTION of business object /IAM/ISSUE.

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_I_QCA_TXTTY_T01

/IAM/TXTTY

Authorization object for descriptions

Logical Conjunction Authorization Type

Logical Conjunction

Search

0QAM_I_QCA_TXTTY_T01

Analytics

0QAM_I_QCA_TXTTY_T01

Analytics result filter

0QAM_I_QCA_TXTTY_T01

Node: Object References with Description Technical Name for Node

QAM_I_QCA_OREF

DDIC Structure

/IAM/S_ESO_I_OREF

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node OBJECT_REFERENCE of business object /IAM/ISSUE.

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_I_QCA_OREF_T01

/IAM/OREF

Authorization object for reference objects for issue/change request/activity

Logical Conjunction Authorization Type

Logical Conjunction

Search

0QAM_I_QCA_OREF_T01

Analytics

0QAM_I_QCA_OREF_T01

Analytics result filter

0QAM_I_QCA_OREF_T01

Overview of the Node Relationships in the Model In the following sections, you will find information about the node relationships of the search and analytics model. For more technical information about the nodes, see the step Node Relations in the system in the transaction ESH_MODELER.

Node Relationship: Issue Descriptions Extraction Node

QAM_I_QCA_DESC

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_QCA_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Value

Join Operator

Page 79 of 106

DB_KEY

Equal

PARENT_KEY

Node Relationship: Code Group Node

0CODE_GROUP./IAM/CODE_GROUP

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_QCA_DESC. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

CODE_GRP

Value

Join Operator Equal

CODEGROUP

Node Relationship: Code Node

0CODE./IAM/CODE

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_QCA_DESC. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

CODE

Value

Join Operator Equal

CODE

Node Relationship: Object References with Description Node

QAM_I_QCA_OREF

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

Yes

This node is a subnode of the root node QAM_I_QCA_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Node Relationship: Object Type Code Node

0OBJ_TYPE_CODE./IAM/OBJ_TYPE_CODE

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_QCA_OREF. Foreign Keys Attributes of Parent Node TYPE_CD

Value

Attributes of Child Node TYPE

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Value

Join Operator Equal

Page 80 of 106

Node Relationship: Object Subtype Code Node

0OBJ_SUBTYPE_CODE./IAM/OBJ_SUBTYPE_COD

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_QCA_OREF. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

TYPE_CD

TYPE

Equal

SUBTYPE_CD

SUBTYPE

Equal

Node Relationship: Issue Descriptions Extraction Node

0QAM_I_QCA_T01.QAM_I_QCA_DESC

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_QCA_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Equal

PARENT_KEY DESC_TYPE

Join Operator

CDESC

Node Relationships: Object References with Description For the node 0QAM_I_QCA_T01.QAM_I_QCA_OREF there are multiple associations: one for each QIM object type. This section describes all these associations collectively. Node

0QAM_I_QCA_T01.QAM_I_QCA_OREF

Relationship Type

Association

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_QCA_ROOT. Foreign Keys, Same for All Associations Attributes of Parent Node

Value

DB_KEY

Attributes of Child Node

Value

Join Operator Equal

PARENT_KEY

Other Foreign Keys by Association Association

Description

Attributes of Child Node

Value

TYPE_CD

MAT

TYPE_CD

CUS

TYPE_CD

PLA

TYPE_CD

VEN

QAM_I_QCA_ROOT2QAM_I_QCAO Reference object outbound delivery REF_DLV

TYPE_CD

DLV

QAM_I_QCA_ROOT2QAM_I_QCAO Reference object batch

TYPE_CD

BAT

QAM_I_QCA_ROOT2QAM_I_QCAO Reference object material

Note

REF_MAT QAM_I_QCA_ROOT2QAM_I_QCAO Reference object customer REF_CUS QAM_I_QCA_ROOT2QAM_I_QCAO Reference object plant REF_PLA QAM_I_QCA_ROOT2QAM_I_QCAO Reference object vendor REF_VEN

REF_BAT

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 81 of 106

Node Relationship: Issue Header Extraction Node

0QAM_I_QIM_T01.QAM_I_ROOT

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QCA_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

ROOT_ISSUE_ID

Value

Join Operator Equal

ISSUE_ID

Node Relationship: Application Node

0APPLICATION./IAM/APPLICATION

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QCA_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

APPLICATION

Value

Join Operator Equal

APPLICATION

Node Relationship: Issue Category Node

0ISSUE_CATEGORY./IAM/ISSUE_CATEGORY

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QCA_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

ISSUE_CATEGORY

Value

Join Operator Equal

ISS_CATEGORY

Node Relationship: Issue Type and Text Node

0ISSUE_TYPE./IAM/ISSUE_TYPE

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QCA_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

APPLICATION

APPLICATION

Equal

ISSUE_TYPE

ISSUE_TYPE

Equal

1.13.1.4 Effect PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 82 of 106

: 0QAM_I_QEF_T01

This search and analytics model is used to search for QIM quality issues of the category Effect . Technical Data Model Use

Application model

Software Component for Search and Analytics

QAM

Prerequisites To use the search and analytics model for Embedded Search, you must have made your settings in Customizing for QIM under Configure Search .

Search and Analytics

Integration The data is read from the DDIC by the BAdI implementation QAM_I_QEF_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA. To search for other issue categories or attachments to an issue or subissue, use the following models: Issue Defect Cause Issue Attachment

Default Request (All Response Attributes) Technical Name

DEFAULT

Use

Attribute search

Overview of the Nodes in the Model In the following sections, you will find information about the nodes of the search and analytics model. For more technical information about the nodes, see the steps Model Nodes , Node Response , and, if required, Operational Data Provider in the system in the transaction ESH_MODELER.

Root Node: Issue Header Extraction Technical Name for Root Node

QAM_I_QEF_ROOT

DDIC Structure

/IAM/S_ESO_I_ROOT

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Root node ROOT of business object /IAM/ISSUE.

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_I_QEF_IAUTH_T01

/IAM/IAUTH

Authorization object for issue/change request

Logical Conjunction Authorization Type

Logical Conjunction

Search

0QAM_I_QEF_IAUTH_T01

Analytics

0QAM_I_QEF_IAUTH_T01

Analytics result filter

0QAM_I_QEF_IAUTH_T01

Navigation Target Navigation Target

Description

Details

UI Technology

0QAM_I_QEF_OVP_SUBISSUE_T01

Display effect

Displays the effect in the QIM Web Dynpro application

Web Dynpro (Application Server)

0QAM_I_QEF_OVP_ROOT_ISSUE_T01

Display root issue

Displays the parent issue in the QIM Web Dynpro application

Web Dynpro (Application Server)

Node: Effect Description: Code and Texts PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 83 of 106

Technical Name for Node

QAM_I_QEF_DESC

DDIC Structure

/IAM/S_ESO_I_DESC

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node DESCRIPTION of business object /IAM/ISSUE.

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_I_QEF_TXTTY_T01

/IAM/TXTTY

Authorization object for descriptions

Logical Conjunction Authorization Type

Logical Conjunction

Search

0QAM_I_QEF_TXTTY_T01

Analytics

0QAM_I_QEF_TXTTY_T01

Analytics result filter

0QAM_I_QEF_TXTTY_T01

Overview of the Node Relationships in the Model In the following sections, you will find information about the node relationships of the search and analytics model. For more technical information about the nodes, see the step Node Relations in the system in the transaction ESH_MODELER.

Node Relationship: Effect Description: Code and Texts Node

QAM_I_QEF_DESC

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_QEF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Node Relationship: Code Node

0CODE./IAM/CODE

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_QEF_DESC. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

CODE

CODE

Value

Join Operator Equal

Node Relationship: Code Group Node

0CODE_GROUP./IAM/CODE_GROUP

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_I_QEF_DESC.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 84 of 106

Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

CODE_GRP

Value

Join Operator Equal

CODEGROUP

Node Relationship: Effect Description: Code and Texts – Text Type EDESC Node

0QAM_I_QEF_T01.QAM_I_QEF_DESC

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_I_QEF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

DESC_TYPE

Join Operator Equal

PARENT_KEY EDESC

Node Relationship: Criticality Node

0CRITICALITY./IAM/CRITICALITY

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QEF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

APPLICATION

APPLICATION

Equal

CRITICALITY

CRITICALITY

Equal

Node Relationship: Issue Header Extraction Node

0QAM_I_QIM_T01.QAM_I_ROOT

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QEF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

ROOT_ISSUE_ID

ISSUE_ID

Value

Join Operator Equal

Node Relationship: Issue Type and Text Node

0ISSUE_TYPE./IAM/ISSUE_TYPE

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QEF_ROOT. Foreign Keys

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 85 of 106

Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

APPLICATION

APPLICATION

Equal

ISSUE_TYPE

ISSUE_TYPE

Equal

Node Relationship: Application Node

0APPLICATION./IAM/APPLICATION

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QEF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

APPLICATION

Value

Join Operator Equal

APPLICATION

Node Relationship: Issue Category Node

0ISSUE_CATEGORY./IAM/ISSUE_CATEGORY

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_I_QEF_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

ISSUE_CATEGORY

Value

ISS_CATEGORY

Join Operator Equal

1.13.1.5 Issue Attachment : 0QAM_ATTM_T01

This search and analytics model is used to search for attachments to a quality issue or subissue (for example, defect, effect, cause) in QIM. Technical Data Model Use

Application model

Software Component for Search and Analytics

QAM

Prerequisites To use the search and analytics model for Embedded Search, you must have made your settings in Customizing for QIM under Configure Search .

Search and Analytics

Integration The data is read from the DDIC by the BAdI implementation QAM_ISS_ATTACHMENT_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA. The data for the issue itself is part of other search and analytics models: Issue Defect Effect Cause

Default Request (All Response Attributes) Technical Name Use

DEFAULT Attribute search

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 86 of 106

Input help

Root Node: Attachment Extraction Technical Name for Root Node

QAM_S_ESO_ATT

DDIC Structure

/IAM/S_ESO_ATT

Authorization Checks Check ID

ABAP Authorization Object

Description

QAM_ATTMT

/IAM/ATTMT

Authorization object for attachments for issue/activity

Logical Conjunction Authorization Type

Logical Conjunction

Search

QAM_ATTMT

Analytics

QAM_ATTMT

Analytics result filter

QAM_ATTMT

Navigation Targets Navigation Target

Description

Details

UI Technology

DISPLAYDOCUMENT

Display document

Displays the attachment

General URL

DISPLAYISSUE

Display issue

Displays the issue to which the attachment General URL belongs

Node: Attachment Extraction – Text Technical Name for Node

QAM_S_ESO_ATT_T

DDIC Structure

/IAM/S_ESO_ATT_T

Node Relationships The node relationships listed in the following table are used to read language-specific texts. Node

Node Description

Relationship Type

Cardinality

Reverse Cardinality

Subquery

QAM_S_ESO_ATT_T

Attachment extraction – text

Composition

Arbitrary

Exactly one

Yes

0ISS_LCYC_STAT./IAM/

Lifecycle status

Association

Arbitrary

Exactly one

No

Effectiveness check status of Association an object

Arbitrary

Exactly one

No

/IAM/EFFECTIVENESS_C 0VALIDATION_STAT./IA

Validation status of an object Association

Arbitrary

Exactly one

No

Document type

Association

Arbitrary

Exactly one

No

Issue type and text

Association

Arbitrary

Exactly one

No

MIME code

Association

Arbitrary

Exactly one

No

ISSUE_LCYCLE_ST 0EFFECTIVENESS_STAT.

M/VALIDATION_CD 0DOC_TYPE./IAM/DOC_T YPE 0ISSUE_TYPE./IAM/ISS UE_TYPE 0MIMECODE./IAM/MIMEC ODE

1.13.1.6 Activity : 0QAM_A_ACT_T01

This search and analytics model is used to search for QIM activities. Technical Data Model Use

Application model

Software Component for Search and Analytics

QAM

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 87 of 106

Prerequisites To use the search and analytics model for Embedded Search, you must have made your settings in Customizing for QIM under Configure Search .

Search and Analytics

Integration The data is read from the DDIC by the BAdI implementation QAM_A_GEN_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA. To search for attachments to an activity, use the model Activity Attachment.

Default Request (All Response Attributes) Technical Name

DEFAULT

Use

Attribute search Input help

Overview of the Nodes in the Model In the following sections, you will find information about the nodes of the search and analytics model. For more technical information about the nodes, see the steps Model Nodes and Node Response in the system in the transaction ESH_MODELER.

Root Node: Header Technical Name for Root Node

QAM_A_ACT_ROOT

DDIC Structure

/IAM/S_ESO_A_ROOT

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Root node ROOT of business object /IAM/ACTIVITY.

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_A_ACT_AAUTH_T01

/IAM/AAUTH

Authorization object for activity

Logical Conjunction Authorization Type

Logical Conjunction

Search

0QAM_A_ACT_AAUTH_T01

Analytics

0QAM_A_ACT_AAUTH_T01

Analytics result filter

0QAM_A_ACT_AAUTH_T01

Navigation Target Navigation Target

Description

Details

UI Technology

0QAM_A_ACT_OVP_ACTIVITY_T01

Display activity

Displays the activity in the QIM Web Dynpro application

Web Dynpro (Application Server)

0QAM_A_ACT_OVP_ISSUE_T01

Display root issue

Displays the parent issue in the QIM Web Dynpro application

Web Dynpro (Application Server)

Node: Data Technical Name for Node

QAM_A_ACT_DATE

DDIC Structure

/IAM/S_ESO_A_DATE

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node DATE of business object /IAM/ACTIVITY.

Node: Descriptions Technical Name for Node

QAM_A_ACT_DESC

DDIC Structure

/IAM/S_ESO_A_DESC

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 88 of 106

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node DESCRIPTION of business object /IAM/ACTIVITY.

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_A_ACT_TXTTY_T01

/IAM/TXTTY

Authorization object for descriptions

Logical Conjunction Authorization Type

Logical Conjunction

Search

0QAM_A_ACT_TXTTY_T01

Analytics

0QAM_A_ACT_TXTTY_T01

Analytics result filter

0QAM_A_ACT_TXTTY_T01

Node: Reference Objects Technical Name for Node

QAM_A_ACT_OREF

DDIC Structure

/IAM/S_ESO_A_OREF

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node OBJECT_REFERENCE of business object /IAM/ACTIVITY.

Authorization Checks Check ID

ABAP Authorization Object

Description

0QAM_A_ACT_OREF_T01

/IAM/OREF

Authorization object for reference objects for issue/change request/activity

Logical Conjunction Authorization Type

Logical Conjunction

Search

0QAM_A_ACT_OREF_T01

Analytics

0QAM_A_ACT_OREF_T01

Analytics result filter

0QAM_A_ACT_OREF_T01

Node: Partners Technical Name for Node

QAM_A_ACT_PARTY

DDIC Structure

/IAM/S_ESO_A_PARTY

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node PARTY of business object /IAM/ACTIVITY.

Node: Quantities Technical Name for Node

QAM_A_ACT_QUANTITY

DDIC Structure

/IAM/S_ESO_A_QUANTITY

Generally, the data is read from the database table for the following node in the Business Object Processing Framework (BOPF) : Node QUANTITY of business object /IAM/ACTIVITY.

Overview of the Node Relationships in the Model In the following sections, you will find information about the node relationships of the search and analytics model. For more technical information about the nodes, see the step Node Relations in the system in the transaction ESH_MODELER.

Node Relationships: Data Node

QAM_A_ACT_DATE

Relationship Type

Composition

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 89 of 106

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Node Relationship: Descriptions Node

QAM_A_ACT_DESC

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Node Relationship: Code Node

0CODE./IAM/CODE

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_A_ACT_DESC. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

CODE

Value

Join Operator Equal

CODE

Node Relationship: Code Group Node

0CODE_GROUP./IAM/CODE_GROUP

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_A_ACT_DESC. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

CODE_GRP

CODEGROUP

Value

Join Operator Equal

Node Relationship: Reference Objects Node

QAM_A_ACT_OREF

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 90 of 106

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Node Relationship: Object Type Code Node

0OBJ_TYPE_CODE./IAM/OBJ_TYPE_CODE

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the node QAM_A_ACT_OREF. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

TYPE_CD

Value

Join Operator Equal

TYPE

Node Relationship: Partners Node

QAM_A_ACT_PARTY

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Node Relationship: Partner Role Code Node

0PARTY_ROLE_CODE./IAM/PARTY_ROLE_CODE

Relationship Type

Association

Cardinality

Arbitrary

Reverse Cardinality

Up to one

Subquery

No

This node is a subnode of the node QAM_A_ACT_PARTY. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

PARTY_ROLE_CODE

Value

APPLICATION

Join Operator Equal

PARTY_ROLE_CODE QIM

Node Relationship: Quantities Node

0QAM_A_ACT_QUANTITY

Relationship Type

Composition

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 91 of 106

Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Node Relationship: Quantity Role Code Node

0QUANTITY_ROLE_CODE./IAM/QUNTY_ROLE_CD

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_A_ACT_QUANTITY. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

ROLE_CD

Value

Join Operator Equal

QTY_ROLE_CD

Node Relationships: Data For the node 0QAM_A_ACT_T01.QAM_A_ACT_DATE there are multiple associations: one for each timepoint stored in Customizing. This section describes all these associations collectively. Node

0QAM_A_ACT_T01.QAM_A_ACT_DATE

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys, Same for All Associations Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Other Foreign Keys by Association Association

Description

Attributes of Child Node

Value

QAM_A_ACT_ROOT2QAM_A_DATE_301

Timepoint Expected start date

ROLE_CD

301

QAM_A_ACT_ROOT2QAM_A_DATE_302

Timepoint Expected end date

ROLE_CD

302

QAM_A_ACT_ROOT2QAM_A_DATE_303

Timepoint Effective date

ROLE_CD

303

QAM_A_ACT_ROOT2QAM_A_DATE_304

Timepoint Completion date

ROLE_CD

304

Node Relationship: Descriptions – Text Type Activity Description (ADESC) Node

0QAM_A_ACT_T01.QAM_A_ACT_DESC

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node DB_KEY

Value

Attributes of Child Node

Value

Equal

PARENT_KEY DESC_TYPE

Join Operator

ADESC

Node Relationship: Descriptions – Text Type Activity Response (ARESP) Node

0QAM_A_ACT_T01.QAM_A_ACT_DESC

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 92 of 106

0QAM_A_ACT_T01.QAM_A_ACT_DESC Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY DESC_TYPE

ARESP

Node Relationships: Reference Objects For the node 0QAM_A_ACT_T01.QAM_A_ACT_OREF there are multiple associations for the different object types. This section describes all these associations collectively. Node

0QAM_A_ACT_T01.QAM_A_ACT_OREF

Relationship Type

Association

Cardinality

Arbitrary

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys, Same for All Associations Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

Join Operator Equal

PARENT_KEY

Other Foreign Keys by Association Association

Description

Attributes of Child Node

Value

QAM_A_ACT_ROOT2QAM_A_OREF_CUS

Reference object customer

TYPE_CD

CUS

QAM_A_ACT_ROOT2QAM_A_OREF_PLA

Reference object plant

TYPE_CD

PLA

QAM_A_ACT_ROOT2QAM_A_OREF_MAT

Reference object material

TYPE_CD

MAT

QAM_A_ACT_ROOT2QAM_A_OREF_BAT

Reference object batch

TYPE_CD

BAT

QAM_A_ACT_ROOT2QAM_A_OREF_DLV

Reference object outbound delivery

TYPE_CD

DLV

QAM_A_ACT_ROOT2QAM_A_OREF_FL

Reference object functional location

TYPE_CD

FL

QAM_A_ACT_ROOT2QAM_A_OREF_VEN

Reference object vendor

TYPE_CD

VEN

Node Relationship: Partner – Responsible Node

0QAM_A_ACT_T01.QAM_A_ACT_PARTY

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Exactly one

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

DB_KEY

Value

RESPONSIBLE_IND

Join Operator Equal

PARENT_KEY X

Node Relationship: Activity Category and Text Node

0ACTIVITY_CATEGORY./IAM/ACT_CATEGORY

Relationship Type

Association

Cardinality

Exactly one

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 93 of 106

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

ACT_CATEGORY

Value

Join Operator Equal

ACT_CATEGORY

Node Relationship: Activity Template and Text Node

0ACTIVITY_TEMPLATE./IAM/ACT_TEMPLATE

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

APPLICATION

APPLICATION

Equal

ACT_TEMPLATE

ACTIVITY_TYPE

Equal

(contains the activity template despite the differing technical name)

Node Relationship: Activity Type and Text Node

0ACTIVITY_TYPE./IAM/ACT_TYPE

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

APPLICATION

APPLICATION

Equal

0ACTIVITY_TYPE

ACTTYPE

Equal

Node Relationship: Activity Lifecycle Status (Activity Status) Node

0ACT_LCYC_STAT./IAM/ACT_LCYCLE_ST

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

LCYCLE_CD

KEY1

Value

Join Operator Equal

Node Relationship: Activity Origin Code Node

0ACT_ORIGIN_CD./IAM/ACTIVITY_ORIGIN

Relationship Type

Association

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 94 of 106

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

ORIGIN_CD

Value

Join Operator Equal

KEY1

Node Relationship: Validation Status of an Object Node

0VALIDATION_STAT./IAM/VALIDATION_CD

Relationship Type

Association

Cardinality

Exactly one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

VALIDATION_CD

Value

Join Operator Equal

KEY1

Node Relationship: Issue Header Extraction Node

0QAM_I_QIM_T01.QAM_I_ROOT

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

APPLICATION

APPLICATION

Equal

ROOT_ISSUE_ID

ISSUE_ID

Equal

Node Relationship: Authorization Group Node

0AUTH_GROUP./IAM/AUTHORIZATION_G

Relationship Type

Association

Cardinality

Up to one

Reverse Cardinality

Arbitrary

Subquery

No

This node is a subnode of the root node QAM_A_ACT_ROOT. Foreign Keys Attributes of Parent Node

Value

Attributes of Child Node

Value

Join Operator

APPLICATION

APPLICATION

Equal

AUTH_GROUP

AUTH_GROUP

Equal

1.13.1.7 Activity Attachment : 0QAM_A_ATTM_T01

This search and analytics model is used to search for attachments to a quality activity in QIM.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 95 of 106

Technical Data Model Use

Application model

Software Component for Search and Analytics

QAM

Prerequisites To use the search and analytics model for Embedded Search, you must have made your settings in Customizing for QIM under Configure Search .

Search and Analytics

Integration The data is read from the DDIC by the BAdI implementation QAM_ACT_ATTACHMENT_OBJECT_DATA for the BAdI BADI_ESH_IF_OBJECT_DATA. The data for the activity itself is part of the search and analytics model Activity.

Default Request (All Response Attributes) Technical Name

DEFAULT

Use

Attribute search

Root Node: Attachment Extraction Technical Name for Root Node

QAM_S_A_ESO_ATT

DDIC Structure

/IAM/S_ESO_ATT

Authorization Checks Check ID

ABAP Authorization Object

Description

QAM_A_ATTMT

/IAM/ATTMT

Authorization object for attachments for issue/activity

Logical Conjunction Authorization Type

Logical Conjunction

Search

QAM_A_ATTMT

Analytics

QAM_A_ATTMT

Analytics result filter

QAM_A_ATTMT

Navigation Targets Navigation Target

Description

Details

UI Technology

DISPLAYDOCUMENT

Display document

Displays the attachment

Web Dynpro

DISPLAYACTIVITY

Display activity

Displays the activity to which the attachment belongs

Web Dynpro

DISPLAYISSUE

Display issue

Displays the issue to which the activity belongs

Web Dynpro

Node: Attachment Extraction – Text Technical Name for Node

QAM_S_A_ESO_ATT_T

DDIC Structure

/IAM/S_ESO_ATT_T

Node Relationships The node relationships listed in the following table are used to read language-specific texts. Node

Node Description

Relationship Type

Cardinality

Reverse Cardinality

Subquery

QAM_S_A_ESO_ATT_T

Attachment extraction – text

Composition

Arbitrary

Exactly one

No

0DOC_TYPE./IAM/DOC_T

Document type

Association

Up to one

Arbitrary

No

MIME code

Association

Up to one

Arbitrary

No

YPE 0MIMECODE./IAM/MIMEC

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 96 of 106

ODE 0ISSUE_TYPE./IAM/ISS

Issue type and text

Association

Up to one

Arbitrary

No

Activity type and text

Association

Up to one

Arbitrary

No

Activity lifecycle status

Association

Up to one

Arbitrary

No

Validation status of an object Association

Up to one

Up to one

No

UE_TYPE 0ACTIVITY_TYPE./IAM/ ACT_TYPE 0ACT_LCYC_STAT./IAM/ ACT_LCYCLE_ST 0VALIDATION_STAT./IA M/VALIDATION_CD

1.13.1.8 ODP for Issue and Subissue : 0QAM_ISSUES

On the basis of this model, you can run analyses for QIM issues by defining queries for the TransientProvider QIM Issues. Technical Data Model Use

Application model

Software Component for Search and Analytics

QAM

Root Node: Quality Issues Technical Name for Root Node

QAM_ISSUES

DataSource

0QAM_ISSUES

Operational Data Provider: Quality Issues Technical Name

0QAM_ISSUES

ODP Semantics

Transaction data

Direct Access Activated

Yes

Authorization Checks Check ID

ABAP Authorization Object

Description

QAM_ISSUES_CHECK

/IAM/IAUTH

Authorization object for issue/change request

Logical Conjunction Authorization Type

Logical Conjunction

Search

QAM_ISSUE_CHECK

Analytics

QAM_ISSUE_CHECK

Analytics result filter

QAM_ISSUE_CHECK

Node Relationships The node relationships listed in the following table are used to read language-specific texts. Node

Node Description

Relationship Type

Cardinality

Reverse Cardinality

Subquery

0PRIORITY./IAM/PRIOR

Priority

Association

Arbitrary

Exactly one

No

Issue type and text

Association

Arbitrary

Exactly one

No

0CODE./IAM/CODE

Code

Association

Arbitrary

Exactly one

No

0ISS_LCYC_STAT./IAM/

Lifecycle status

Association

Arbitrary

Exactly one

No

Authorization group

Association

Arbitrary

Exactly one

No

Issue category

Association

Arbitrary

Exactly one

No

Criticality

Association

Arbitrary

Exactly one

No

ITY 0ISSUE_TYPE./IAM/ISS UE_TYPE

ISSUE_LCYCLE_ST 0AUTH_GROUP./IAM/AUT HORIZATION_G 0ISSUE_CATEGORY./IAM /ISSUE_CATEGORY 0CRITICALITY./IAM/CR ITICALITY

1.13.2 TransientProviders

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 97 of 106

1.13.2 TransientProviders 1.13.3.1 QIM Issues : 2O0QAM_ISSUES

On the basis of this TransientProvider, you can define analytical queries for evaluating QIM issues.

Prerequisites The connector for the search and analytics model ODP for Issue and Subissue is active.

Structure Data Modeling Requires Object Type

Name

Technical Name

Operational Data Provider (ESH-Based)

Quality Issues

0QAM_ISSUES

InfoObject

Default Quantity Unit

2O-DEF_QUANT_UN

InfoObject

Number of issues

2O-ISSUE_COUNT-INT4

InfoObject

Complaint Quantity

2O-Q_COMSUM-DEC

InfoObject

Complaint divided by Reference Quantity

2O-Q_COM_D_Q007-DEC

InfoObject

Issues for Complaint divided by Reference Quantity

2O-Q_COM_D_Q008-INT4

InfoObject

Number of Occurrences

2O-Q_OCCSUM-INT4

InfoObject

Reference Quantity

2O-Q_REFSUM-DEC

InfoObject

Expected Start minus Expected End Date in seconds

2O-T_302_S_T009-DEC

InfoObject

Issues for Expected Start minus Expected End Date in

2O-T_302_S_T010-INT4

seconds InfoObject

Application

2O0APPLICATION

InfoObject

Authorization Group

2O0AUTH_GROUP

InfoObject

Code

2O0CODE

InfoObject

Criticality

2O0CRITICALITY

InfoObject

Lifecycle Status

2O0IAMISS_LCYC

InfoObject

Issue Category

2O0ISSUE_CATEG

InfoObject

Issue type and text

2O0ISSUE_TYPE

InfoObject

Priority

2O0PRIORITY

InfoObject

Approval Status

2O0QAM_ISSUES-APPROVAL_CD

InfoObject

Archiving Status

2O0QAM_ISSUES-ARCHIVING_CD

InfoObject

Cause Code

2O0QAM_ISSUES-CDESC_CD

InfoObject

Changed By

2O0QAM_ISSUES-CHANGED_BY

InfoObject

Batch Number

2O0QAM_ISSUES-CHA_REF_ID

InfoObject

Consistency

2O0QAM_ISSUES-CONSIST_CD

InfoObject

Country Key

2O0QAM_ISSUES-COUNTRY

InfoObject

Created By

2O0QAM_ISSUES-CREATED_BY

InfoObject

Customer

2O0QAM_ISSUES-CUSTOMER_REF

InfoObject

Defect Code

2O0QAM_ISSUES-DDESC_CD

InfoObject

Deferral Status

2O0QAM_ISSUES-DEFERRAL_CD

InfoObject

Digital Signature Status Code

2O0QAM_ISSUES-DIGSIGN_CD

InfoObject

Delivery Item

2O0QAM_ISSUES-DLI_REF_ID

InfoObject

Delivery

2O0QAM_ISSUES-DLV_REF_ID

InfoObject

Duration

2O0QAM_ISSUES-DURATION_CD

InfoObject

Effect Code

2O0QAM_ISSUES-EDESC_CD

InfoObject

Effectiveness Check Status of an Object

2O0QAM_ISSUES-EFFECTIVENES

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 98 of 106

InfoObject

Emergency Indicator

2O0QAM_ISSUES-EMERGENCY

InfoObject

Equipment

2O0QAM_ISSUES-EQ_REF_ID

InfoObject

Functional Location

2O0QAM_ISSUES-FL_REF_ID

InfoObject

Resolution Code

2O0QAM_ISSUES-ISOLU_CD

InfoObject

Issue ID

2O0QAM_ISSUES-ISSUE_ID

InfoObject

Issue Type Change Status

2O0QAM_ISSUES-ISSUE_TYPE_C

InfoObject

Reference Object ID

2O0QAM_ISSUES-MAIN_REF_ID

InfoObject

Material

2O0QAM_ISSUES-MATERIAL_REF

InfoObject

Plant

2O0QAM_ISSUES-PLA_REF_ID

InfoObject

Business Partner Number of Responsible

2O0QAM_ISSUES-RESPONSIBLE_

InfoObject

Validation

2O0QAM_ISSUES-VALIDATION_C

InfoObject

Vendor

2O0QAM_ISSUES-VENDOR_REF_I

1.13.3 DataSources 1.13.3.1 QIM Issues DataSource Transactional Data: 0QAM_ISSUES

You can use this DataSource for various analyses of issues in SAP QIM: Operational reporting with Search and Operational Analytics The search and analytics model ODP for Issue and Subissue is available for this purpose. Reports in Business Context Viewer (BCV) The DataSource supports direct access with preaggregation.

Technical Data Application Component

QAM

Available as of Release

SAP QIM 1.0 SP02

Shipment

n/a

Content Versions

QAM100

RemoteCube-Capable

n/a

Delta-Capable

No

Extraction from Archives

No

Verifiable

n/a

Data Modeling Fields of Origin for the Extract Structure Fields in the Extract Structure

Description of the Field in the Extract Structure

Table of Origin

Field in the Table of Origin

ISSUE_COUNT

Number of issues

/IAM/D_I_ROOT

N/A

KEY_MAX

Node ID

/IAM/D_I_ROOT

DB_KEY

Q_COMSUM

Complaint quantity

/IAM/D_I_QTY

QUANTITY

Q_OCCSUM

Number of occurrences

/IAM/D_I_QTY

QUANTITY

Q_REFSUM

Reference quantity

/IAM/D_I_QTY

QUANTITY

Q_COM_D_Q_REF

Complaint quantity / Reference quantity

/IAM/D_I_QTY

QUANTITY

Q_COM_D_Q_REF_CT

Number of issues for calculation

/IAM/D_I_QTY

N/A

T_302_S_T_301

UTC timestamp in short form (expected end date – expected start date)

/IAM/D_I_DATE

DATE_TIME

T_302_S_T_301_CT

Number of issues for calculation

/IAM/D_I_DATE

N/A

CUSTOMER_REF_ID

Customer

/IAM/D_I_OBJ_REF

ID

MATERIAL_REF_ID

Material

/IAM/D_I_OBJ_REF

ID

VENDOR_REF_ID

Vendor

/IAM/D_I_OBJ_REF

ID

CHA_REF_ID

Batch number

/IAM/D_I_OBJ_REF

ID

DLI_REF_ID

Delivery item

/IAM/D_I_OBJ_REF

ID

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 99 of 106

DLV_REF_ID

Delivery

/IAM/D_I_OBJ_REF

ID

EQ_REF_ID

Equipment

/IAM/D_I_OBJ_REF

ID

FL_REF_ID

Functional location

/IAM/D_I_OBJ_REF

ID

PLA_REF_ID

Plant

/IAM/D_I_OBJ_REF

ID

MAIN_REF_ID

Reference object ID (main reference object) /IAM/D_I_OBJ_REF

ID

IDESC_CD

Code

/IAM/S_I_DESC

CODE

CDESC_CD

Cause code

/IAM/S_I_DESC

CODE

DDESC_CD

Defect code

/IAM/S_I_DESC

CODE

EDESC_CD

Effect code

/IAM/S_I_DESC

CODE

ISOLU_CD

Resolution code

/IAM/S_I_DESC

CODE

LCYCLE_CD

Issue life cycle status

/IAM/D_I_ROOT

LCYCLE_CD

CONSIST_CD

Consistency status of an object

/IAM/D_I_ROOT

CONSIST_CD

DEFERRAL_CD

Deferral status of an object

/IAM/D_I_ROOT

DEFERRAL_CD

ARCHIVING_CD

Archiving status of an object

/IAM/D_I_ROOT

ARCHIVING_CD

VALIDATION_CD

Validation status of an object

/IAM/D_I_ROOT

VALIDATION_CD

EFFECTIVENESS_CD

Effectiveness check status of an object

/IAM/D_I_ROOT

EFFECTIVENESS_CD

APPROVAL_CD

Approval status of an object

/IAM/D_I_ROOT

APPROVAL_CD

ISSUE_TYPE_CD

Issue type status of an object

/IAM/D_I_ROOT

ISSUE_TYPE_CD

DIGSIGN_CD

Digital signature status code

/IAM/D_I_ROOT

DIGSIGN_CD

ISSUE_ID

Issue ID

/IAM/D_I_ROOT

ISSUE_ID

APPLICATION

Application in Issue and Activity Engine

/IAM/D_I_ROOT

APPLICATION

ISSUE_TYPE

Issue type

/IAM/D_I_ROOT

ISSUE_TYPE

ISSUE_CATEGORY

Issue category

/IAM/D_I_ROOT

ISSUE_CATEGORY

AUTH_GROUP

Authorization group

/IAM/D_I_ROOT

AUTH_GROUP

CRITICALITY

Criticality

/IAM/D_I_ROOT

CRITICALITY

PRIORITY

Priority

/IAM/D_I_ROOT

PRIORITY

EMERGENCY

Emergency indicator

/IAM/D_I_ROOT

EMERGENCY

DURATION_CD

Duration

/IAM/D_I_ROOT

DURATION_CD

COUNTRY

Country key

/IAM/D_I_ROOT

COUNTRY

DEF_QUANT_UNIT

Default quantity unit

/IAM/D_I_ROOT

DEF_QUANT_UNIT

CREATED_BY

Created by

/IAM/D_I_ROOT

CREATED_BY

CHANGED_BY

Changed by

/IAM/D_I_ROOT

CHANGED_BY

RESPONSIBLE_ID

Business partner number

/IAM/D_I_PARTY

PARTNER_ID

1.13.4 Content Objects in Software Component IAM 1.13.4.1 Content Objects for Customizing in IAM The following table displays the DataSources and technical search and analytics models relevant for SAP QIM in the software component IAM, which serve to extract texts for Customizing entries and make them available for searching or analytics.

Features Search and Analytics Model

DataSource

Text

0ACTIVITY_CATEGORY

/IAM/ACTIVITY_CATEGORY

Activity category

0ACTIVITY_TEMPLATE

/IAM/ACTIVITY_TEMPLATE

Activity template

0ACTIVITY_TYPE

/IAM/ACTIVITY_TYPE

Activity type

0ACT_LCYC_STAT

/IAM/ACTIVITY_LCYCLE_STAT_CD

Activity life cycle status (activity status)

0ACT_ORIGIN_CD

/IAM/ACTIVITY_ORIGIN_CD

Activity origin code

0ACT_RESP_VAL_BOOL

/IAM/ACT_RESPONSE_VALUE_BOOL

Activity response value - Boolean

0APPLICATION

/IAM/APPLICATION

Application

0APPROVAL_STAT

/IAM/APPROVAL_STATUS_CD

Approval status

0AUTH_GROUP

/IAM/AUTHORIZATION_GROUP

Authorization group

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 100 of 106

0CODE

/IAM/CODE

Code

0CODE_GROUP

/IAM/CODE_GROUP

Code group

0CRITICALITY

/IAM/CRITICALITY

Criticality

0DEFERRAL_STATUS

/IAM/DEFERRAL_STATUS_CD

Deferral status

0DIGIT_SIGN_CD

/IAM/DIGIT_SIGN_CD

Digital signature status

0DOC_TYPE

/IAM/DOC_TYPE

Document type

0DURATION

/IAM/DURATION

Duration

0EFFECTIVENESS_STAT

/IAM/EFFECTIVENESS_CD

Effectiveness check status

0ISSUE_CATEGORY

/IAM/ISSUE_CATEGORY

Issue category

0ISSUE_TYPE

/IAM/ISSUE_TYPE

Issue type

0ISS_LCYC_STAT

/IAM/ISSUE_LCYCLE_STAT_CD

Issue life cycle status (issue status)

0LOGICAL_SYSTEM

/IAM/LOGICAL_SYSTEM

Logical system

0MIMECODE

/IAM/MIMECODE

MIME code

0OBJ_SUBTYPE_CODE

/IAM/OBJ_SUBTYPE_CODE

Object subtype code

0OBJ_TYPE_CODE

/IAM/OBJ_TYPE_CODE

Object type code

0PARTY_ROLE_CODE

/IAM/PARTY_ROLE_CODE

Partner role code

0PRIORITY

/IAM/PRIORITY

Priority

0PROCESSING_CODE

/IAM/PROCESSING_CD

Processing status of an object

0QUANTITY_ROLE_CODE

/IAM/QUANTITY_ROLE_CODE

Quantity role code

0RESPONSIBLE_IND

/IAM/RESPONSIBLE_IND

Responsible indicator

0UNIT_OF_MEASURE

/IAM/UOM

Unit of measure

0VALIDATION_STAT

/IAM/VALIDATION_CD

Validation status

Activities To use the objects for SAP QIM, proceed as described in Customizing for QIM under

Search and Analytics

Configure Search

.

1.14 Archiving QIM Data SAP supports your data management by providing suitable functions for data archiving and for data retention and data destruction. Data archiving An efficient management of data includes the archiving of data belonging to completed business processes. Using data archiving, you can export data that you no longer require in the system, but need to retain for documentation purposes, for example, to an archive file. To reduce the load on the database, the archive file is stored in a file system or content repository and the data is deleted from the database. Data retention/data destruction With SAP NetWeaver Information Lifecycle Management (ILM), SAP provides suitable tools to fulfill legal requirements for the retention of data, and for the destruction of data. For example, you can store rules for retention in ILM Retention Management. These functions are available for QIM quality issues and QIM quality activities with the delivery of the following archiving objects: Activities: /IAM/ACT Issues: /IAM/ISSUE The archiving objects are based on the Archive Development Kit (ADK) and use functions of the BOPF archiving adapter. To support you with the destruction of personal data, an end of purpose check is possible for the following data: Business partners that are assigned to a QIM quality issue or a QIM quality activity Customers and vendors that are assigned as reference objects in QIM

Prerequisites To be able to use the functions of Information Lifecycle Management (ILM), you must have activated the business function ILM. You have made the required settings in Customizing for data archiving: SAP NetWeaver Application Server System Administration Archiving To use the archiving functions, users must have the authorizations provided by the authorization object S_ARCHIVE.

Data

Procedure 1. Familiarize yourself with the functions of the Archive Development Kit and ILM Retention Management: Data Archiving with Archive Development Kit (ADK) SAP NetWeaver Information Lifecycle Management 2. Archive the QIM objects (issues and activities) using the respective archiving object. 1. First archive the activities for an issue and its subissues (see Archiving Activities with /IAM/ACT). 2. Then archive the issue and the corresponding subissues (see Archiving Issues with /IAM/ISSUE).

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 101 of 106

3. If you want to store retention rules for business partners, customers, and vendors, proceed as described in Customizing for QIM under Define End of Purpose for Personal Data .

Environment

1.14.1 Archiving Activities with /IAM/ACT With the archiving object /IAM/ACT, you can archive activities and their corresponding information, such as reference objects, descriptions, partners, and attachments stored in the system. Which information is archived in detail is listed in archive administration (transaction SARA) under Database Tables and in the application for archiving object definition (transaction AOBJ) under Structure Definition . The following programs are available for this archiving object: Preprocessing program /IAM/ACT_ARCH_PRE The preprocessing program uses the activity status and the chosen selection criteria (for example, residence time) to check for which activities archiving is possible and then assigns them the archiving status Marked for Archiving . For more information, see Checks for /IAM/ACT. Write program /IAM/ACT_ARCH_WRI The write program creates archive files and stores the activities with the status Marked for Archiving in the file. The write program also sets the Activities Archived indicator in the parent issue or subissue.

Note When QIM data is archived, transient texts, such as the descriptions of codes stored in Customizing, are also archived in one specific language; if you perform the archiving in English, these texts will be shown in English when you display the archived data at a later stage, even if you are logged on to the system in another language. Delete program /IAM/ACT_ARCH_DEL The delete program reads the data from the archive file. If the read was successful, it sets the status to Archived and deletes the data from the database. If you want to extend the archivability checks, archive additional data, or register other archiving classes, you can use the options in the BOPF Enhancement Workbench (transaction /BOBF/CUST_UI). For more information, see Business Object Builder.

Usage in ILM Retention Management To be able to use the archiving object /IAM/ACT in Information Lifecycle Management (ILM), the ILM object IAM_ACTIVITY is delivered. Settings in ILM object Customizing (transaction IRM_CUST) for IAM_ACTIVITY: Available Time References: Created On (CREATION_DATE) Last Changed On (LAST_CHANGE_DATE) Available Condition Fields: IAM Application (APPLICATION) IAM Authorization Group (AUTH_GROUP) Available Policy Categories: Retention Rules (RTP) Assigned BOR Object: /IAM/ACT

Prerequisites You have authorization for the activity 12 Archive in the authorization object IAM/A_STAT Authorization Object for Lifecycle Status (Activity) , field /IAM/A_ACT Authorization to Perform Activity-Related Activities .

Procedure 1. In the transaction SARA, create a variant for the preprocessing program and schedule it. For more information, see Creating Preprocessing Variants for /IAM/ACT 2. In the transaction SARA, create a variant for the write program and schedule it. 3. The delete program is executed automatically after the write program. You can change this setting in Customizing for the archiving object (in the transaction SARA under Goto Customizing Archiving Object-Specific Customizing Technical Settings ).

Result The archived data is deleted from the database but can still be displayed. For more information, see Displaying Archived QIM Data.

1.14.1.1 Checks for /IAM/ACT The preprocessing program checks whether archiving can run for the selected activities based on the lifecycle status.

Note The residence time is already taken into account in the selection criteria for the preprocessing program (see Creating Preprocessing Variants for /IAM/ACT). If the check was successful, the program sets the archiving status Marked for Archiving .

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 102 of 106

Since, for reasons of consistency, only complete activity hierarchies for an issue or subissue (defects, effects, causes) can be archived, the preprocessing program checks whether all activities that belong to one activity branch beneath an issue, defect, cause, or effect are archivable.

Features Basic and extended activities and questions can only be archived if they have one of the following lifecycle statuses: Completed (09) Canceled (10) Flagged for Deletion (64) Activities of the category Information can be archived regardless of their lifecycle status if the parent activity has the archiving status Marked for Archiving . If an activity has further subactivities, these must also have the archiving status Marked for Archiving .

1.14.1.2 Creating Preprocessing Variants for /IAM/ACT The preprocessing program selects the activities based on your specified selection criteria and checks whether they can be archived (see Checks for /IAM/ACT). If the check was successful, the preprocessing program sets the archiving status Marked for Archiving . Activities with the status Marked for Archiving can then only be displayed in the application but no longer changed. You can execute the preprocessing program in test mode or production mode. Independent of this, you must always use a variant and schedule it. There are various selection criteria and options available for you to create a variant: Application First, you must specify the application QIM to archive QIM data. Only then are the other application-specific selection criteria visible.

Recommendation You can store the application QIM in your user profile as the value for the parameter /IAM/APPLICATION, then the value is entered automatically in the selection criteria. Activity selection To determine the activities to be archived, you can, for example, specify the activity ID, activity category, activity type, and lifecycle status. Residence time You can enter the residence time for activities in the QIM system (in days, relating to the date of the last change). For example, if the residence time is 365 days, only those activities are selected that were last changed at least a year ago.

Recommendation You can store a default value for the residence time in application-specific Customizing (see Setting Up Application-Specific Customizing). Note that with the following lifecycle statuses, immediate archiving is possible: Canceled (10) Flagged for Deletion (64) If you want to archive the respective activities immediately, you can define an additional variant that incorporates the relevant lifecycle statuses and a residence time of 0 days. Logging You can specify in which form and with which level of detail the log is to be displayed.

Procedure 1. Open archive administration (transaction SARA). 2. 3. 4. 5. 6.

Enter the technical name of the archiving object and choose Preproc . Enter a name for the variant and choose Maintain . Enter the required data for the selection criteria and the variant attributes. Save the variant. Enter the start date and the spool parameters.

Result You have now entered all the data required for the background job. To create the job, choose Execute . Following this, you can then schedule the write program analogously. The selection criteria for the preprocessing program and the write program do not have to match.

1.14.2 Archiving Issues with /IAM/ISSUE With the archiving object /IAM/ISSUE, you can archive issues and their corresponding information, such as reference objects, descriptions, partners, and attachments stored in the system. Which information is archived in detail is listed in archive administration (transaction SARA) under Database Tables and in the application for archiving object definition (transaction AOBJ) under Structure Definition . The following programs are available for this archiving object: Preprocessing program /IAM/ISSUE_ARCH_PRE The preprocessing program uses the issue status and the chosen selection criteria (for example, residence time) to check for which issues archiving is

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 103 of 106

possible and then assigns them the archiving status Marked for Archiving . For more information, see Checks for /IAM/ISSUE Write program /IAM/ISSUE_ARCH_WRI The write program creates archive files and stores the issues with the status Marked for Archiving in the file.

Note When QIM data is archived, transient texts, such as the descriptions of codes stored in Customizing, are also archived in one specific language; if you perform the archiving in English, these texts will be shown in English when you display the archived data at a later stage, even if you are logged on to the system in another language. Delete program /IAM/ISSUE_ARCH_DEL The delete program reads the data from the archive file. If the read was successful, it sets the status to Archived and deletes the data from the database. If you want to extend the archivability checks, archive additional data, or register other archiving classes, you can use the options in the BOPF Enhancement Workbench (transaction /BOBF/CUST_UI). For more information, see Business Object Builder.

Usage in ILM Retention Management To be able to use the archiving object /IAM/ISSUE in Information Lifecycle Management (ILM), the ILM object IAM_ISSUE is delivered. Settings in ILM object Customizing (transaction IRM_CUST) for IAM_ISSUE: Available Time References: Created On (CREATION_DATE) Last Changed On (LAST_CHANGE_DATE) Available Condition Fields: IAM Application (APPLICATION) IAM Authorization Group (AUTH_GROUP) Available Policy Categories: Retention Rules (RTP) Assigned BOR Object: /IAM/ISSUE

Prerequisites You have authorization for the activity 14 Archive in the authorization object IAM/I_STAT Authorization Object for Lifecycle Status (Issue) , field /IAM/I_ACT Authorization to Perform Issue-Related Activities . You have already activated the activities that belong to the issue and its subissues or marked them for archiving.

Procedure 1. In the transaction SARA, create a variant for the preprocessing program and schedule it. For more information, see Creating Preprocessing Variants for /IAM/ISSUE 2. In the transaction SARA, create a variant for the write program and schedule it. 3. The delete program is executed automatically after the write program. You can change this setting in Customizing for the archiving object (in the transaction SARA under Goto Customizing Archiving Object-Specific Customizing Technical Settings ).

Result The archived data is deleted from the database but can still be displayed. For more information, see Displaying Archived QIM Data.

1.14.2.1 Checks for /IAM/ISSUE The preprocessing program checks whether archiving can run for the selected issues based on the lifecycle status.

Note The residence time is already taken into account in the selection criteria for the preprocessing program (see Creating Preprocessing Variants for /IAM/ISSUE). If the check was successful, the program sets the archiving status Marked for Archiving . For reasons of consistency, only complete issue hierarchy branches can be archived when archiving issues. That means, all subissues (defects, effects, causes) belonging to an issue must be archived as well. The assigned activities must already have been archived or be marked for archiving (see also Archiving Activities with /IAM/ACT).

Features Issues can only be archived if they have one of the following lifecycle statuses: Completed (09) Canceled (10) Flagged for Deletion (64) The corresponding defects, effects, and causes are archived as well, regardless of their lifecycle status.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 104 of 106

The activities belonging to the issue or subissue must have one of the following archiving statuses: Marked for Archiving (02) Archived (03)

1.14.2.2 Creating Preprocessing Variants for /IAM/ISSUE The preprocessing program selects the issues based on your specified selection criteria and checks whether they can be archived (see Checks for /IAM/ISSUE). If the check was successful, the preprocessing program sets the archiving status Marked for Archiving . Issues with the status Marked for Archiving can then only be displayed in the application but no longer changed. You can execute the preprocessing program in test mode or production mode. Independent of this, you must always use a variant and schedule it. There are various selection criteria and options available for you to define a variant: Application First, you must specify the application QIM to archive QIM data. Only then are the other application-specific selection criteria visible.

Recommendation You can store the application QIM in your user profile as the value for the parameter /IAM/APPLICATION, then the value is entered automatically in the selection criteria. Issue selection To determine the issue to be archived, you can, for example, specify the issue type and the lifecycle status. To ensure data consistency, for all issues selected their subissues (defects, effects, and causes) are automatically selected as well, regardless of their status. Residence time You can enter the residence time for issues in the QIM system (in days, relating to the date of the last change). For example, if the residence time is 365 days, only those issues (and their subissues) are selected that were last changed at least a year ago.

Recommendation You can store a default value for the residence time in application-specific Customizing (see Setting Up Application-Specific Customizing). Note that with the following lifecycle statuses, immediate archiving is possible: Canceled (10) Flagged for Deletion (64) If you want to archive the respective issues immediately, you can define an additional variant that incorporates the relevant lifecycle statuses and a residence time of 0 days. Logging You can specify in which form and with which level of detail the log is to be displayed.

Procedure 1. Open archive administration (transaction SARA). 2. 3. 4. 5. 6.

Enter the technical name of the archiving object and choose Preproc . Enter a name for the variant and choose Maintain . Enter the required data for the selection criteria and the variant attributes. Save the variant. Enter the start date and the spool parameters.

Result You have now entered all the data required for the background job. To create the job, choose Execute . Following this, you can then schedule the write program analogously. The selection criteria for the preprocessing program and the write program do not have to match.

1.14.3 Setting Up Application-Specific Customizing You can store a default value for the response time of a business object in Customizing.

Procedure 1. Open the Customizing activity. You have two options for doing this: Transaction SARA: First, enter the technical name of the archiving object and then choose

Goto

Customizing

Application-Specific

Customizing: Maintain BO-Specific Residence Time . SAP Customizing Implementation Guide: Choose Cross-Application Components Processes and Tools for Enterprise Applications Objects and Functions for BOPF Environment Archiving Adapter Maintain BO-Specific Residence Periods . 2. Create a new entry if required. 3. Enter the following data: Business Object : Enter /IAM/ACT for activities or /IAM/ISSUE for issues.

Reusable

BO Usage (corresponds to the application in the component IAM): Enter QIM. BO Node Name : Leave the field blank. Residence Period : Enter your required residence period for the business object in days.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 105 of 106

Result The residence period stored in Customizing is displayed as the default value when you create the preprocessing variant.

1.14.4 Displaying Archived QIM Data You have various options for displaying archived issues and activities: Quick access via the QIM user interface Here, you can only call individual objects via their ID. Archive information system (transaction SARI) Here, you can use various selection criteria. Various infostructures and field catalogs are delivered for display in the archive information system. For activities: Infostructure /IAM/ACT Field catalog /IAM/ACT For issues: Infostructure /IAM/ISSUE Field catalog /IAM/ISSUE

Procedure To display specific individual objects, enter the ID in the relevant quick access CHIP. In the search help for the quick access, archived objects are not taken into account. To display objects via the archive information system, proceed as follows: 1. In archive administration (transaction SARA), choose

Information System

Archive Explorer

.

2. Specify the archiving object and the archive infostructure. 3. Enter the selection criteria for the objects that you want to display. 4. In the results list, you can display the object in the QIM Web application by double-clicking the node ID.

PUBLIC © 2014 SAP SE or an SAP affiliate company. All rights reserved.

Page 106 of 106